Related
Hi,
Can anyone please share/post ext3.ko or ext4.ko for kernel of XT720? The optimizer script has a ext2.ko, but problem is, with a class 2 or 4 SD card, which is very slow, non-journalled filesystem is a big headache. Several times I managed to corrupt the ext2 filesystem -- and though later repaired by linux, it resulted in lost files. So if I get a ext3.ko I'll format the other partition of SD card in ext3 minimizing the risk of filesystem corruption.
Kousik
but performance wise might be slowed down in the phone as it'll need to do extra processing.
you'll definitely need to keep the phone OCed at 1000 for it to work smoothly
i don't know who might have compiled ext3/ext4.ko files, the one that we see all the time is the ext2.ko included with most of the scripts for apps2sd
AllGamer said:
but performance wise might be slowed down in the phone as it'll need to do extra processing.
you'll definitely need to keep the phone OCed at 1000 for it to work smoothly
Click to expand...
Click to collapse
So the idea is to use something like link2sd, where space hogging games like angry birds, talking tom apk will be kept in the sd card and symbolic links are made (to save space). When these games are on, anyway I crank up the CPU to 1GHz (actually ondemand setting of setcpu will do it automatically). Other 'regular' apps will stay in internal memory for performance with lower CPU speed. So the bottom line is, infrequently used apps will stay in ext3 and we'll allow high overclock for them anyway.
i don't know who might have compiled ext3/ext4.ko files, the one that we see all the time is the ext2.ko included with most of the scripts for apps2sd
Click to expand...
Click to collapse
I did my due search in google for a ext3.ko for kernel 2.6.29-omap1 but failed to find one. Hopefully someone in this forum knows. I might try posting the query in general android development forum for an wider audience.
I don't really understand what is your problem but I have partitioned my memory card as ext3 for apps2sd. It works well. I have over 90 apps and still left with 75MB of memory.
jackfrost3821 said:
I don't really understand what is your problem but I have partitioned my memory card as ext3 for apps2sd. It works well. I have over 90 apps and still left with 75MB of memory.
Click to expand...
Click to collapse
Fantastic, can you please post the kernel module? If you didn't do anything other than apps2sd, then the kernel module will be distributed alongwith. You can post the link to apk or zip, from which I can extract ext3.ko.
I have partitioned my memory card as ext3 for apps2sd.
Click to expand...
Click to collapse
Are you certain it's mounted ext3? ext3 is backwards compatible with ext2. After ext3 partitions have been safely shutdown (i.e. the journal has been committed) they can be mounted as ext2 without problems. I suspect you partitioned it ext3, but the phone mounts it ext2.
You can check this by going to shell and running "mount" (no options). That will list the partitions and the driver that is currently used for them. For example the output on my phone includes:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
which means that /system/sd is ext2.
kousik said:
I did my due search in google for a ext3.ko for kernel 2.6.29-omap1 but failed to find one. Hopefully someone in this forum knows. I might try posting the query in general android development forum for an wider audience.
Click to expand...
Click to collapse
Well someone did know, and I discovered it on *another* thread. Including it for reference:
dateno1 said:
modules for it (also you can install it use clockworkmod) from http://dateno1.egloos.com/category/%EB%A1%AC%ED%82%A4%EC%B9%9C%20for%20motoroi
also it support ext3 if you copy jbd.ko and ext3.ko on /system/lib/modules
Click to expand...
Click to collapse
So I copied the .ko files and loaded them. Already I had my SD partitioned, and second partition is ext3 already, and I could successfully mount the same:
Code:
insmod jbd.ko
insmod ext3.ko
mount -t ext3 /dev/block/mmcblk0p2 /data/sdext
Thanks goes to dateno1!
THANK YOU!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kousik said:
Well someone did know, and I discovered it on *another* thread. Including it for reference:
So I copied the .ko files and loaded them. Already I had my SD partitioned, and second partition is ext3 already, and I could successfully mount the same:
Code:
insmod jbd.ko
insmod ext3.ko
mount -t ext3 /dev/block/mmcblk0p2 /data/sdext
Thanks goes to dateno1!
Click to expand...
Click to collapse
kousik said:
Hi,
Can anyone please share/post ext3.ko or ext4.ko for kernel of XT720? The optimizer script has a ext2.ko, but problem is, with a class 2 or 4 SD card, which is very slow, non-journalled filesystem is a big headache. Several times I managed to corrupt the ext2 filesystem -- and though later repaired by linux, it resulted in lost files. So if I get a ext3.ko I'll format the other partition of SD card in ext3 minimizing the risk of filesystem corruption.
Kousik
Click to expand...
Click to collapse
Can You explain this: is, with a class 2 or 4 SD card, which is very slow, non-journalled filesystem is a big headache.
regarding corruption of the filesystem, why dont you check it before mount?
for example my relevant entries in mot_boot_mode are:
Code:
#load ext and mount sdcard
insmod /system/lib/modules/ext2.ko
/system/xbin/e2fsck-or -p /dev/block/mmcblk0p2 > /cache/dalvik-cache/ext2check.log
/system/xbin/busybox mount -t ext2 -o noatime,nodiratime /dev/block/mmcblk0p2 /system/sd
/system/sdremount.sh
as far as i remember i get the e2fsck-or from some openrecovery
if you are curious here is the /system/sdremount.sh
Code:
/system/bin/mount -o remount,noatime /dev/block/mtdblock9 /data
/system/bin/mount -o remount,noatime tmpfs /tmp
echo 0 > /sys/block/mtdblock9/queue/rotational
echo 0 > /sys/block/mtdblock7/queue/rotational
i tried to mod apps2sd to use the ko files in order to use ext3. mission failed. hung on the white M. zz.
peshovec said:
Can You explain this: is, with a class 2 or 4 SD card, which is very slow, non-journalled filesystem is a big headache.
regarding corruption of the filesystem, why dont you check it before mount?
Click to expand...
Click to collapse
I agree, checking filesystem before mount is A Good Thing. Unfortunately once a corruption happened, the repair tend to lose files. When I suspected corruption, I mounted the card from Linux and e2fsck always found orphaned inodes I can tolerate some slowness (may try to compensate with overclock), but weekly once repairing filesystem is very boring!
darren_soh86 said:
i tried to mod apps2sd to use the ko files in order to use ext3. mission failed. hung on the white M. zz.
Click to expand...
Click to collapse
Can you please post what exactly you have done? I edited mot_boot_mode (original is renamed with .bin) to append insmod jbd.ko; insmod ext3.ko; mount ... and that works!
this is wat i tried
#!/system/bin/sh
export PATH=/system/bin:$PATH
#run original script
mot_boot_mode.bin
#mount ext3
insmod /system/lib/modules/ext3.ko
insmod /system/lib/modules/jbd.ko
mount -t ext3 /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
darren_soh86 said:
this is wat i tried
#mount ext3
insmod /system/lib/modules/ext3.ko
insmod /system/lib/modules/jbd.ko
Click to expand...
Click to collapse
AFAIK you have to insert them in the 'other' order to resolve dependency. ext3 needs jbd to work. Swap these 2 lines and you should be good.
OH. i see. haha. thank for the tip pal.
i edited it accordingly and it worked! woo hoo!
Force fsck on reboot
Maybe we can tweak the script to do a force fsck on startup. It may slow down bootup time a bit but at least you start out fresh everytime.
trajano said:
Maybe we can tweak the script to do a force fsck on startup. It may slow down bootup time a bit but at least you start out fresh everytime.
Click to expand...
Click to collapse
Yes but as I said before, if the filesystem is corrupted already for a damage, fsck will bring sanity back but will lose files. You can see orphaned inodes dumped into lost+found. Then you have to manually re-instate the lost files.
BTW I found that in Link2SD way, where you just keep the apk files in ext partition of SD card, you can mount the partition read-only. There is no chance of corruption. Only during moving packages around you need a remount.
i found this link here with ext4.ko! but i am not sure if it works. wana check it out?
http://www.beagleboard.org/~arago/esc-boston-2009/lib/modules/2.6.29-omap1/kernel/fs/ext4/ext4.ko
this is the source.
http://www.beagleboard.org/~arago/esc-boston-2009/lib/modules/2.6.29-omap1/kernel/fs/ext4/
i have nilfs2, ext2,3,4 modules for 29 kernel
you can download from here
warning : if you want to use ext4 you will need to add it on your boot(mount) script
mount -t yaffs2 -o rw,remount /dev/block/mtdblock6 /
add to top of script
Gotten ext3.ko working
I got ext3.ko working on my XT720. I don't notice any slowdown compared to the ext2.ko version. Though during a phone crash the boot up time is seems to be slightly slower than the ext2. Hopefully it means that it is keeping things more stable and I won't have as many file system errors when I try to do an fsck on the drive.
ext4
dateno1 said:
i have nilfs2, ext2,3,4 modules for 29 kernel
you can download from URL
warning : if you want to use ext4 you will need to add it on your boot(mount) script
mount -t yaffs2 -o rw,remount /dev/block/mtdblock6 /
add to top of script
Click to expand...
Click to collapse
You can use a ext4 module(ext4.ko) but have to do following command on linux PC (or maybe xt720 recovery mode)
Code:
tune2fs -O ^huge_file [I]EXT4_PARTITION_OF_SDCARD[/I]
Because ext4 starts to support for large single file feature, and it must be included in kernel.
But kernel on XT720 not supports this feature, so mounting a ext4 partition would be failure.
Removing this feature supporting, you can mount the partition.
(And I think last code mounting mtdblock6 is useless, it is cdrom partition, and I have used ext4 without that command
Note: This guide is geared toward the Samsung Captivate. If you have a different device, try your device's forum, or search this thread.
Are you using ICS and pulled your phone out of your pocket only to find that it had this screen, saying "Encryption unsuccessful" and your only option a button that said "Reset Phone"? Don't press it! Try rebooting a few times with your external sdcard out first. Sometimes that will fix the issue. If not, take a deep breath and follow the guide below to get your phone usable again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Too late? Already hit the button? Then you know this screen:
Here's the bad news:
Your partitions for /data and /sdcard are no longer accessible. Latest news points to a bug in the firmware for the memory card in your phone. ICS uses a new function that doesn't work correctly with the affected phones.
Good news:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9-11 every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Here were my steps to get your phone working again:
Realize that you may have just lost whatever was on your sdcard and it's your own fault. For me, this was acceptance that *I* installed ICS on my phone and now CWM backups, photos, and more were gone. Once your realization has set in, move forward.
Acquire an micro SD card that you will put into your phone. This will contain your new /data partition as well as your new /sdcard partition. I recommend at least 8GB. If you already have a card, backup whatever is currently on your micro SD card - you *WILL LOSE* everything on this card in the next few steps.
Boot into clockwork mod, using either 'adb reboot recovery', or some other combination of buttons.
Partition your mircosd card through CWM. This will be 'advanced' then 'Partition SD Card'. The first size you choose will be the size of your /data partition. I have a 16GB card and chose 2GB for /data. This will leave me with (16GB-2GB) 14GB for /sdcard. You can choose a different size if you like, depending on how big you want your internal data partition to be. Choose 0M for swap. This process will take a few minutes, so keep waiting, you impatient jerk.
Download the latest build of ICS for your phone and put it on your micro SD card. (You can mount it to your computer at this point in CWM with 'mounts and storage' 'Mount USB storage')
Create a full backup. Just in case. Put it on a computer, dropbox, whatever. Your phone isn't a safe place for backups.
Wipe user data, cache, & system. Now install the ICS package you just put on your card and reboot.
The first boot will take a while, as all first boots do, but after a while you should be back in ICS. Exhale (If you're not exhaling at this point, post something in this thread and I or someone else will help get you running)
Check Settings > Storage and see if your new /sdcard partition (For me it was about 14GB) shows up as 'USB Storage' or 'SD Card' If it's USB storage, then your micro sd mounted to /sdcard successfully and you're done. You should be able to take a picture and have it save. If not...
Edit etc/vold.fstab with whatever you use personally (root explorer for me) and swap paths for /emmc and /sdcard (the part that starts with /devices/platform...). Someone more intelligent than me can probably make this a CWM zip. This step is telling ICS to swap your /sdcard (broken internal sdcard) and your /emmc (working external sdcard). It will probably look like this when you're done:
Code:
# internal sdcard that is no longer working
dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Reboot with your new vold.fstab and check your storage amount in ICS and test your camera (easy test to see if Android can write to the sdcard). Hopefully now this is working for you.
Let me know if you have any questions or (hopefully not) problems!
Notes for myself and devs:
ICS is a lot pickier about mounting filesystems, and if it can't mount /data correctly, it assumes it is encrypted. It really isn't, firing off https://source.android.com/tech/encryption/android_crypto_implementation.html an misleading encryption message.
In ICS and in CWM, when I look at /dev/block/platform/ I only see s3c-sdhci.2 and s5pc110-onenand. The s3c-sdhci.0 block is missing completely. I'm not sure how to even touch the /data or /sdcard filesystem at *ALL*
Oh well.
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.
edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
chmod 644 /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot
TRusselo said:
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.
Click to expand...
Click to collapse
Actually, the question he asked is extremely relevant to my post, specifically step 9. I agree with you #1, though.
cgugino said:
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot
Click to expand...
Click to collapse
Thank you! Everything is working now thank you.
ICS currently using 4.0.3 version of the Onecosmic's ROM version 2.1.
I want to use version 3.1 or CM9 KANG, this time when the boot screen remains. Have his solution
when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot
kwhee07 said:
when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot
Click to expand...
Click to collapse
Make sure you're using vold and not void, as in VOLume Daemon.
OR
Make sure you're remounting the file system with Root Explorer (press the button to change R/O to R/W)
roms kernel glitch does not work.
Boot screen does not turn on the device remains.
edecan said:
roms kernel glitch does not work.
Boot screen does not turn on the device remains.
Click to expand...
Click to collapse
What ROM are you on?
Did you flash a ROM update? If so, this overwrites the vold.fstab and you'll have to fix it. If you're on CM9, try reinstalling the latest update package, then perform steps 9 and on from the first post.
cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb
kwhee07 said:
cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb
Click to expand...
Click to collapse
Let me know if it doesn't work. Did you partition your external sd card?
no, have not understood me.
Just set up onescomics rom. Install another rom.
Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.
edecan said:
no, have not understood me.
Just set up onescomics rom. Install another rom.
Click to expand...
Click to collapse
The only way I know how to make this work is with the CM9 ROM -- I don't know what onescomics is and if you can't get your phone working, I would recommend staying on ICS.
iperezru said:
Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.
Click to expand...
Click to collapse
That is the case for me where the internal sdcard and data partition is totally lost.
I cannot say for sure how the guide would affect you if you followed it. If CWM thinks that your partitioned external sdcard has the /data partition on it (you could use the mount command and see), when you install ICS, it would install to your actual external sdcard. You may have to edit the vold.fstab in the installer zip file before you install, so that on the first boot, the phone won't try to boot to your internal partitions. Honestly, if you're still under warranty, I'd just flash to stock and try and exchange it.
I know that the 'Encryption unsuccessful' message is triggered because the phone has trouble mounting the /sdcard partition, and with ICS, it assumes that the partition is encrypted. It may be that your partition is taking too long to load, or that it is having issues reading. Either way, I'd make regular backups of *everything* onto your computer, in case one day the whole thing craps out.
As for me, even after I went back to stock Eclair, up to Froyo, and up to GB, I could never get the /sdcard or /data partitions to recognize.
See the section on 'Booting an encrypted system' here for more about how ICS detects 'encrypted' filesystems: https://source.android.com/tech/encryption/android_crypto_implementation.html
cgugino said:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9 and on every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Click to expand...
Click to collapse
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?
raz123 said:
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?
Click to expand...
Click to collapse
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.
cgugino said:
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.
Click to expand...
Click to collapse
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466
raz123 said:
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466
Click to expand...
Click to collapse
I agree with you on the strangeness! I wish I could offer a solution to get your internal sdcard files back, but there doesn't seem to be one at the moment. The other interesting thing is that the encryption guide for 3.0 says that encryption isn't even usable with the YAFFS file system, which I believe the Captivate uses.
If your phone is under warranty...there may be another option for you. I contacted about 3 other people that had threads related to this issue and everyone that responded said that Samsung replaced the motherboard.
What's your phone build? Mine is 1012 Rev 0.4
Edit: I haven't tried Adam's unbricking mod, and don't think I will. For me, the phone is now working perfectly and has full functionality, outside of the loss of the original /data and /sdcard partitions. I'm not going to crack it open and start soldering. However, if you do try his mod, please let us know the results!
I thought about this idea more than a month ago when i came to know that the partitions could freely be altered, but i could not put into practice until i got my 32 gb card yesterday.
so basically, after following my guide you will have:
* supersized data partition (12 gigs): no more move to sd needed unless for huge games (i'm thinking fifa12 and asphalt7) and then again the stock move to sd feature will work as expected (it will move data to the actual external sd card)
* external sd card mounted as internal sd card: nothing to say here, just does what is expected
* real internal sd (ums partition) shrinked to minimum (half gig) because it needs to stay present: used to mount a swap file (optional)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What you will need:
* g.lewarne hydracore 4.3b kernel: you don't need it for anything special, but it's the most amazing kernel, and gavin is the most devoted developer ive seen on the n7000. cheers gavin and keep up the good work :good:
* swapper2: if you want to use the swap file (see at the end)
so be warned, i'm no real specialist here, so i'm not aware of the no dos, i just got my guide to work through trial and error and getting information from other threads.
so if you follow my guide you're almost good, if not you may cause an atomic bomb to fall over your city, not my problem :silly:
enough chit chat for now let's head directly for the guide:
1. reboot to recovery, and connect your phone to your pc
2. run a command prompt and type the following (wait a little bit until the adb server starts on the phone, you can verify it by typing "adb devices" if you get a serie of digits then you're good to go.
Code:
adb shell
parted /dev/block/mmcblock0
you'll get into the parted interactive shell, this is where serious work done
Code:
did i remind you to backup your system,
this is your last stop before the no back point
so you just might wanna "move" all your internal sd stuff to the external sd,
and backup your system to the external sd also
(you just need to restore the data partition afterwards the rest of the system is safe but who knows :p)
ps: you can do your backup on cwm without leaving adb shell on the pc just like you will do the format later thanks to cwm
remove the partitions
Code:
rm 10
rm 11
make the new changed size partitions
Code:
unit b
mkpart primary 1174405120 14680064511
mkpart primary 14680064512 15216934911
name 10 DATAFS
name 11 UMS
now in cwm go to mounts and storage and select "format /emmc" and "format /data"
in parted type "print" and you should see this output
Code:
Number Start End Size File system Name Flags
1 4194304B 25165823B 20971520B ext4 EFS
2 25165824B 26476543B 1310720B SBL1
3 27262976B 28573695B 1310720B SBL2
4 29360128B 37748735B 8388608B PARAM
5 37748736B 46137343B 8388608B KERNEL
6 46137344B 54525951B 8388608B RECOVERY
7 54525952B 264241151B 209715200B ext4 CACHE
8 264241152B 281018367B 16777216B MODEM
9 281018368B 1174405119B 893386752B ext4 FACTORYFS
10 1174405120B 14680064511B 13505659392B ext4 DATAFS
11 14680064512B 15216934911B 536870400B fat32 UMS
12 15216934912B 15753805823B 536870912B ext4 HIDDEN
now the hardest part is over, restore your data partition and you will be able to boot you system normally. and you go to your storage information you will find that your app storage is now 13gigs and the usb storage is just 500 megs yay
to switch the sd with the internal you will have to modify vold.fstab file(thanks to ciphray for his guide on how to do so)
you can use the modified file from ciphray thread here which i didn't beacuse his file was smaller
so i just pulled the file to my pc
Code:
adb pull /etc/vold.fstab vold.fstab
modified it with notepad++ or any dev text editor (don't use windows notepad it will mess the file)
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
and push it back to phone + change permissions
Code:
adb push vold.fstab /etc/vold.fstab
chmod 644 /etc/vold.fstab
restart your phone and voila
as a final step you can use the now pretty useless internal space (500megs remember) as a swap sapce
download swapper2 from the play store here https://play.google.com/store/apps/details?id=lv.n3o.swapper2
run it and go to settings
set swap place as /sdcard/external_sd/swapfile.swp
set swap size to the max
set the swappiness to 20 ( you can rise the value a little but don't put a high value or the system will do much swapping all the time -value of 100 means any memory not used actively will be swapped- )
wait until the process finishes then reboot your phone
you can verify that swap is working by typing "free" in the shell if the line beginning with swap is not all zeros then you're swap is working.
hope my guide will be usefull, and don't hesitate to ask me any question
Awesome, thanks! Will try it out when I get some time
If you want more app space you can erase the hidden partition and get more space.
Sent from my GT-N7000 using Tapatalk 2
Okay, I've performed the whole thing, and just a few remarks on my experience
If you want to modify the vold.fstab straight from recovery without having to reboot first, you can simply mount the system partition, and retrieve the file from /system/etc/vold.fstab instead of /etc/fstab
More importantly, following your instructions, I ended up in a situation where my apps previously moved to the sd card weren't recognized. I've solved this by modifying my vold.fstab as follows:
Code:
# internal sdcard
{
storage_struct = cover, "/mnt/sdcard/external_sd","/mnt/sdcard/usbStorage"
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun1/file
android_secure_containers = enable
}
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# external sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
discard = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
That way, all my apps were properly recognized without issues. I'll probably be moving them back to phone now though.
Will be trying this setup over the next few days and see how it performs, but one caveat I missed is that you may not be able to install the whole of some apps on the data partition, as some the data will always be stored in the sdcard/Android folder, which would make the 12GB on /data less useful than I initially thought, unless I'm missing something of course
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
zongamin said:
Hi
Could you post a screenshot of the Storage page (under Settings)?
I'm interested to see what these look like after this mod.
Internal
USB Storage
SD Storage
Thanks!
Click to expand...
Click to collapse
here you are, look at the OP
i didn't realize the screenshot like was corrupt
if you read the op i mentioned the resulting sizes after the mod
sd storage will be mentioned as 500 megs (actually taken from the internal emmc) that i use for swap space
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
As far as I know, the HydraCore kernel doesn't allow swap, so it's unuseful to setup a swap file with swapper. Also, presently no Note kernel has swap enabled.
Carefully crafted on my Galaxy Note, for your eyes only
Hydracore 4.1 since has swap enabled in its kernel.
Sent from my GT-N7000 using Tapatalk 2
I'm sorry, I didn't know Gavin had listened to what I had asked oh so many times
Carefully crafted on my Galaxy Note, for your eyes only
travis82 said:
Why isn't it possible to use the rest of the space for apps and reroute the ums to the ext sdcard so it reads it as the internal?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
i was fearing that the phone won't boot if the partition isn't available after a clean setup.
so i decided to leave the small size partition and make it useful for swap instead.
btw does anyone know how to use a bigger swap file with swapper2?
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
antique_sonic said:
I guess, this method is only working for a "healthy" note, which never got a mmc cap bricks, right ?
And if a note got brick before, and recovered by hg42 pit revival method, I think the repartition command for the start-end of the DATA and UMS will be different.
Hmmpppfff... Do you have a way on how to read the partition setting of the note ? :fingers-crossed:
Send from the corner of this rounded earth
Click to expand...
Click to collapse
just type print on the parted shell
and then you can recalculate new sizes for the data partitions, it should work like a charm
So... Im a USER, and there are part I am a bit confused about... BUT ill ask anyway!
It seems that if I wanted to resetup the partitions, I wouldnt need to mess with the pit files correct?
OR, because I want to totally KILL USB Storage, dedicate the entire internal memory to /data, and make /sdcard TRULY my sdcard, would I truly need to mess with the pit file?
Has anyone tried with killing off /ums completely?
Any help is appreciated. Also, I am using the i717 (AT&T GNote version), but my desire is the same so I figured Id post here...
EDIT: im not too worried about rom flashing, I normally slim down ROM's before I flash them, so Im not afraid of changes that have to be made (in txt files) in order to have them work properly on a UMS'less modded device. However, I do need to find out how to properly backup the pit file before I even THINK Of messing with it.
do i have to redo the whole procedure if i flashing nightly every time?
Anyone tried this on JB roms?
Hello?
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Anyone tried this on JB roms?
Click to expand...
Click to collapse
+1
I get 64 gb sandisk microsd card. I want to use this mod on jb stock LSC rom.
Can we use on jb roms?
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
Helpppppp
Envoyé depuis mon GT-N7000 avec Tapatalk
JB ready
I've tried it worked fine on Ultimate and Alliance ROM. Just edit vold.fstab in /etc after install new ROM. Replace 11 to auto and { } to { }. Now I need help if anyone have the original partition info, incase I wanted to restore.
Hi,
I have a big problem with my Sony Xperia Z5,
I can't move files on the phone with the ES or EZ file manager from
the internal space to the external micro SD card.
It' s confusing me, every time I want to load something from pc to the
phone I have the same problem, Airdroid only writes to the internal space.
The only way tosend files to the SD card is to remove it from the phone
put it into an SD card reader and write the files from the pc to the reader,
this works.
O.K. I did not used an empty new card, I'm using my old 32GB card which was in
my HTC Sensation and in the Samsung S6, but on this both phones there was no
problem to exchange files.
What is the problem, could someone give me a hint?
Oh, I'm using Android Lollipop 5.1.1
Kernel 3.10.49-perf-g75e6207
Thank you, for any help!
Problem is that apps now need permissions to write to the sd card. When you select the SD card in ES or EZ it should tell you you need to select SD card from a popup
picrard said:
Hi,
I have a big problem with my Sony Xperia Z5,
I can't move files on the phone with the ES or EZ file manager from
the internal space to the external micro SD card.
It' s confusing me, every time I want to load something from pc to the
phone I have the same problem, Airdroid only writes to the internal space.
The only way tosend files to the SD card is to remove it from the phone
put it into an SD card reader and write the files from the pc to the reader,
this works.
O.K. I did not used an empty new card, I'm using my old 32GB card which was in
my HTC Sensation and in the Samsung S6, but on this both phones there was no
problem to exchange files.
What is the problem, could someone give me a hint?
Oh, I'm using Android Lollipop 5.1.1
Kernel 3.10.49-perf-g75e6207
Thank you, for any help!
Click to expand...
Click to collapse
there is an app on play store [LINK]https://play.google.com/store/apps/details?id=nextapp.sdfix[/LINK] that can make your life easier ( works on lollipop too ) . another option is to add the Android UNIX group "media_rw" to the WRITE_EXTERNAL_STORAGE permission's configuration on the platform.xml file ( /system/etc/permissions/platform.xml )
arismelachrinos said:
there is an app on play store [LINK]https://play.google.com/store/apps/details?id=nextapp.sdfix[/LINK] that can make your life easier ( works on lollipop too ) . another option is to add the Android UNIX group "media_rw" to the WRITE_EXTERNAL_STORAGE permission's configuration on the platform.xml file ( /system/etc/permissions/platform.xml )
Click to expand...
Click to collapse
Yes but you need root for both methods. Out of the box, sdcard support is pretty much useless on Z5.
Only way is to connect to pc and move files from internal to external.
langeveld024 said:
Yes but you need root for both methods. Out of the box, sdcard support is pretty much useless on Z5.
Only way is to connect to pc and move files from internal to external.
Click to expand...
Click to collapse
I have seen similar comments several places and often remained puzzled.
Premise: I have a Z5 Compact. Perhaps that is different from the Z5 in this regard, but that seems unlikely?
I can write to the ext. SD card just fine, from within phone as well as from a pc connected via usb cable (with card still inside phone). The first time you try you will be sent to a screen where you will be asked to give permission to write to the card, "select SD card" or similar, I cannot remember the exact phrases or procedure and don't have a screenshot. I did that with ES file explorer when phone was brand new two months ago, then again a week back when I ditched ES and installed X-plore. EDIT: after doing this once I could then write to the card without any issues.
Stock ROM, no root, latest firmware, 5.1.1
Only way is to connect to pc and move files from internal to external.
Click to expand...
Click to collapse
....oh...wtf....who did I bought this f#@@# phone...
and there is no other way to fix it???...without this option,
to write on the Sd card... it's a bad thing.... It's on all devices with Lollipop 5.1.1 or is it
a damn Sony option?
Yes, when there would be a chance to give root to the Xperia Z5
the Z3 does have root already, or not?
@E5832 Ooops...I was to slow
picrard said:
....oh...wtf....who did I bought this f#@@# phone...
and there is no other way to fix it???...without this option,
to write on the Sd card... it's a bad thing.... It's on all devices with Lollipop 5.1.1 or is it
a damn Sony option?
Yes, when there would be a chance to give root to the Xperia Z5
the Z3 does have root already, or not?
@E5832 Ooops...I was to slow
Click to expand...
Click to collapse
Developer Mode + Usb Debugging should work
adb push
Code:
adb push /mypreciousfiles/precious /mnt/storage/sdcard1/precious
or something like that - the phone is currently off and charging - so can't write the exact path ...
langeveld024 said:
Yes but you need root for both methods. Out of the box, sdcard support is pretty much useless on Z5.
Only way is to connect to pc and move files from internal to external.
Click to expand...
Click to collapse
oh , you didnt mention you are not rooted , thats why i told you that
E5823 said:
I have seen similar comments several places and often remained puzzled.
Premise: I have a Z5 Compact. Perhaps that is different from the Z5 in this regard, but that seems unlikely?
I can write to the ext. SD card just fine, from within phone as well as from a pc connected via usb cable (with card still inside phone). The first time you try you will be sent to a screen where you will be asked to give permission to write to the card, "select SD card" or similar, I cannot remember the exact phrases or procedure and don't have a screenshot. I did that with ES file explorer when phone was brand new two months ago, then again a week back when I ditched ES and installed X-plore. EDIT: after doing this once I could then write to the card without any issues.
Stock ROM, no root, latest firmware, 5.1.1
Click to expand...
Click to collapse
It has something to do with the new storage framework since kk. Es Explorer adapted to work with it but most file explorers not. Just tested, your method works indeed. Thank you
zacharias.maladroit said:
Developer Mode + Usb Debugging should work
adb push
Code:
adb push /mypreciousfiles/precious /mnt/storage/sdcard1/precious
or something like that - the phone is currently off and charging - so can't write the exact path ...
Click to expand...
Click to collapse
what does that command do? Enable 1 folder to write to or something?
arismelachrinos said:
oh , you didnt mention you are not rooted , thats why i told you that
Click to expand...
Click to collapse
It's okay, I'm waiting to see if the drm fix still works on MM. if it works, I'm unlocking this b!tch instantly lol
O.k.
So.... The internal storage is mounted under /mnt/sdcard and under root /sdcard
the external is just under /sdcard1
I hope I understand, that means I have to mount with the adb push command
the external card into mount?
So I maybe have to enter the command
Code:
adb push /sdcard1 /mnt/sdcard1
Do I have permission to exchange files under /mnt ???
Is that right? Thank you!
E5823 said:
.....I did that with ES file explorer
Click to expand...
Click to collapse
... oh my god, yes ... that was easy, and it has confused my now for about 2 month
yes I did it also with the ES File Explorer,
how easy .... :highfive: thank you...
I've did it that way ...:
I've tried to create a folder under /sdcard1
ES showed me than a popup where I have to select the SD card
and so on... you push the ok(it was the button on the left I think??!?!?)
than you will enter another surface or so?!? looks not like the ES Explorer,
there you have to slelect the SD card on the left menu, I think !?!?....
I was to quick now to recreate it, and I can not reproduce it,
because I have now permission....
it will set a link or sets a mount point to /storage/sdcard1
and then you can really use copy create rename use the !
so I did not had to use the adb command, but maybe it works also??!?!
I will make it tomorrow on the XPERIA Z5 COMPACT from my wife
and this time I will make screenshots and will show them here if someone want
to see it... she has the same issue, and the surface looks like the big Z5....
oh no, now I have some pictures for you I hope this helps(sorry it's german):
first this, select your external storage:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you have to select it on the lower field
Exactly, that's also the way it works with e.g. AirDroid
glad you got it working
Still for reference below how to do it via adb push
Hi,
no, everything should already be (automatically) be mounted.
Unless the custom ROM I'm in does things differently you should get the following:
(first take a look around)
Code:
adb shell
Code:
mount | grep sdcard
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 texfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,umask=0007,allow_utime=0020,iocharset=utf8,min_prealloc_size=64k,max_prealloc_size=122598k,readahead=128k,fail_safe,discard,hidden=show,errors=continue 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
Click to expand...
Click to collapse
then see where you got some storage left to store data
Code:
df
Filesystem Size Used Free Blksize
/dev 1.3G 80.0K 1.3G 4096
/sys/fs/cgroup 1.3G 0.0K 1.3G 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 1.3G 0.0K 1.3G 4096
/mnt/obb 1.3G 0.0K 1.3G 4096
/tmp 1.3G 0.0K 1.3G 4096
/system 5.0G 1.5G 3.5G 4096
/data 22.6G 5.9G 16.6G 4096
/cache 192.8M 1.9M 190.9M 4096
/persist 27.5M 736.0K 26.8M 4096
/firmware 80.0M 56.2M 23.8M 16384
/lta-label 11.7M 1.5M 10.2M 4096
/oem 290.6M 135.4M 155.2M 4096
/mnt/idd 14.0M 149.0K 13.8M 1024
/mnt/rca 8.4M 338.0K 8.0M 1024
/mnt/shell/emulated 22.6G 5.9G 16.6G 4096
/mnt/media_rw/sdcard1: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard1 119.7G 108.4G 11.3G 131072
Click to expand...
Click to collapse
this means you can't write to /mnt/media_rw/sdcard1
but you can to /storage/sdcard1 from above, remember ?
example:
Code:
adb push XposedInstaller_3.0_alpha4.apk /storage/sdcard1/
or this also works with folders
Code:
adb push bigassfolder /storage/sdcard1/bigassfolder
arismelachrinos said:
there is an app on play store [LINK]https://play.google.com/store/apps/details?id=nextapp.sdfix[/LINK] that can make your life easier ( works on lollipop too ) . another option is to add the Android UNIX group "media_rw" to the WRITE_EXTERNAL_STORAGE permission's configuration on the platform.xml file ( /system/etc/permissions/platform.xml )
Click to expand...
Click to collapse
btw, i cant seem to find the line ''WRITE_EXTERNAL_STORAGE'' in the platform.xml on Marshmallow.
only ''WRITE_MEDIA_STORAGE'' (which is internal memory i think) and ''WRITE_PERSISTENT_STORAGE''
do u know if its moved or?
[edit] nevermind. theres no need to edit anymore. it works on marshmallow, though im rooted so i cant speak for nonrooted users.
No methods available up to now worked for me.
GLOBAL MIUI 11.0.7 Rooted with Magisk -> Apps2SD presents various errors while creating mount script. Simply won't work. Link2SD either.
Tried forcing via adb "pm set-install-location 2", nope.
Tried formatting as adoptable using activity manager to open files activity (the only way to enable it on 7A) - sd card disappears, doesn't add up any memory.
So... any ideas? Xposed modules or any other simpler solutions are welcome!
Tips of using SD Card as Internal Storage.
This is my Internal Storage after applying this method
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let's do it!
Download this app
https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher
Now follow the steps,
Install downloaded app.
Put SD Card in your phone.
Go to the top bar, select All Activities.
Search for Downloads and select it.
Now Select your SD Card in the top left bar option.
Tap on three dots in the top right and go to storage settings.
Select Format as Internal Storage.
Now format and reboot. All done. Enjoy!
Learn how to Revert back/Use SD Card as External Storage.
Just Remove SD Card from your phone.
Tap on the notification which will come.
Select Forget SD Card.
I AM NOT RESPONSIBLE FOR ANY HARM OF YOUR SD CARD, DEVICE, DATA. DO AT YOUR OWN RISK.
Click to expand...
Click to collapse
Sorry friend that doesn't work. After formatting sd card disappears and render unusable on 7A (at least in my version).
Disclaimer: In this article I tested using Redmi 7A MIUI 2020.11.0.7 Stable, I cannot guarantee this method works on all Xiaomi phones. This method runs the risk of deleting data on your cellphone and SD Card, so you MUST Backup Your Data. Do With Your Own Risk.
Click to expand...
Click to collapse
Prepare Tools and Materials
1. Good quality microSD 128GB, Reading speed: 100 MB/s - Write speed: 90 MB/s (don't use the cheap ones)
2. Download Activity Launcher (old version) Here
Step By Steps
Open the Activity Launcher application. Tap on the "Recent activities"> select "All activities". Then wait until loading is complete.
Look for the "Files" menu, just tap it and choose one of the ones I like as shown below
Then select "SD Card", after that in the upper right corner tap the three point icon, select "Storage Settings".
Then select "Format as Internal".
Then select "Erase & format". Wait until the SD card formatting process is complete.
After the format process is complete, select the "Move now" option, then click "Next".
Next, click "Move". Wait until the file transfer process is complete, whether or not long depends on how much data is transferred.
When done, the SD Card is ready notification will appear.
Finally, reboot / restart :fingers-crossed:
jurubebaamarga said:
No methods available up to now worked for me.
GLOBAL MIUI 11.0.7 Rooted with Magisk -> Apps2SD presents various errors while creating mount script. Simply won't work. Link2SD either.
Tried forcing via adb "pm set-install-location 2", nope.
Tried formatting as adoptable using activity manager to open files activity (the only way to enable it on 7A) - sd card disappears, doesn't add up any memory.
So... any ideas? Xposed modules or any other simpler solutions are welcome!
Click to expand...
Click to collapse
After some manipulations with the mount script, Link2SD still worked.
1. I Have a Magisk, so first I mounted the system for reading and writing.
2. Next in the app, I will re-create the mount script.
3. now you need to copy the init-link2sd file.sh from the /data/data/com.buak.Link2SD/ folder to the /data/adb/service.d/ folder.
Now rename the script from init-link2sd.sh in 11link2sd.sh.
4. There is not much to edit.
it was like this:
echo "$(date) mounting..." > $LOG
sleep 2
mount -t ext4 -o rw,noatime /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG
mount -t ext4 -o rw,noatime /dev/block/vold/public:179_66 /data/sdext2 1>>$LOG 2>>$LOG
mount >> $LOG
chmod 773 /data/dalvik-cache
it became so:
echo "$(date) mounting..." > $LOG
sleep 2
mount -t ext4 -o rw, /dev/block/mmcblk1p2 /data/sdext2
mount >> $LOG
chmod 773 /data/dalvik-cache
Hi guys.
Updated to miui 12.
I was able to use this adoptable storage method with a class 10 sdcard.
After updating this method leads to success, but not working at all in reality. It shows my total storage in device information as my sd card, but when I touch it to see details of my storage use it shows just the same way as it was before, without the sd card caapcity. Also it doesn't let me use my sd card capacity moving files from pc to phone, does not show on pc file manager the sd card either. Always have problems with storage capacity. Deep regrets buying this 16gb redmi, seller did not tell me it would not let me use sd card as expansion...
Aha!
Just giving up and voila.
Was doing the forget adoptable sd card steps and when rebooted to format ir again the system default format tool gives the adoptable sd card formatting, just touch back and slide down the message and choose wheter you want the adoptable or media sd card.
Works fine now, without the activity launcher method, aparently outdated for miui 12.