MM bring the ability to devices which support it to share SD card with system to install apps on SD card. But Sony disabled this on MM. Here is to Enable this functionality
(Be aware that your shared partition will be hidden on other devices)
You will need adb installed on your computer
If you doesn't have it :
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Then connect your phone with adb debugging enabled.
Type "adb shell"
Once you're connected to your device : "sm list-disks"
This will return the ID of your sd card.
Now, if you want the whole sd card to be shared type "sm partition disk:ID private"
If you want your sd to be partitionned type "sm partition disk:ID mixed:%"
(replace ID with your own card ID and % with the STANDARD stockage percent you want on your sd card)
You're done !
(Sizes of partitions are not reported as they should but it seems to work)
Before/After
Before :
{
"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"
}
After :
Source :
mocado.com
This is Mocado's work, not mine !
But they are testing it on S7 ........ anyone tried on our Sony?
@Elfeno
Is it possible to take and save screenshot after enabling adoptable storage and moved app with this way?
I couldn't access to internal storage in some apps when I enabled adoptable storage with other way (xposed)...
I have successfully done this and everything seems to work fine however when I migrate my data to the SD card so this becomes the default location for new apps and data, I get a memory error in the stock camera app. Is anyone else getting this issue? I haven't yet figured a way around it. This is the one and only issue but it would be a deal breaker
@AndroPlus Since this functionality is part of Android and the 2 memory become one It should not have this issue but will try @roland101 This issue happened to me also after upgrading to MM. Did a clean install wiping data resolved this issue
Hi @Elfeno. I tried a factory reset from the Backup and Restore menu but I still have the issue. How exactly did you do it? Did you already have the SD card private partitioned and data migrated when you did the factory reset? I did, but then my phone didn't recognize the SD card anyway so I had to re-apply the private partition via adoptable storage. I then check the camera, no error. I then migrated all data from internal to SD card from the storage section but after that and a reboot I still get the memory error in the camera app. What were your steps exactly? Thanks
Hello @roland101,
I met the same issue like you. But if your SD card is large enough (like 128GB), you can format it in mixed 25 (reserve 32GB standard storage, other some other value), and then you can use camera on that partition. But the new problem will be: Google Photos(if you use that for backup) cannot delete device copy on that partition (I dont't know why Google Photos didn't request external SD card permission).
@roland101 @fqj1994 Yes the partition created for apps cannot be use to store files. Mixed will create 1 partition for apps and 1 for files
About the Google Photos app I guess it store photos in app data and if we cannot write that partition it doesn't allow us to delete these files but should work using Google photo app since it's is own files. If Gphoto was baked with your rom maybe it have arlready the permision needed. You can also check in per apps permissions in settings Check if it delete the cloud backup when you delete local photo.
@Elfeno
Another problem is even get camera to work with a mixed partition. all apps externally calling camera to take photos are dead (like hangout/ telegram)
Elfeno said:
@roland101 @fqj1994 Yes the partition created for apps cannot be use to store files. Mixed will create 1 partition for apps and 1 for files
Click to expand...
Click to collapse
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Not sure it worked
fqj1994 said:
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Click to expand...
Click to collapse
Just tried this on a xperia z5 compact and the commands worked the sm partition returned in a few second, little too quick.
When I go into storage i just see a nagative number for both the internal and sd card.
a df from the adb shell shows the below
Filesystem Size Used Free Blksize
/dev 889.4M 96.0K 889.3M 4096
/sys/fs/cgroup 889.4M 0.0K 889.4M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt 889.4M 0.0K 889.4M 4096
/tmp 889.4M 4.0K 889.4M 4096
/system 4.9G 3.8G 1.1G 4096
/data 22.6G 5.0G 17.6G 4096
/oem 290.6M 117.6M 173.0M 4096
/cache 192.8M 260.0K 192.6M 4096
/persist 27.5M 804.0K 26.7M 4096
/firmware 80.0M 56.4M 23.5M 16384
/lta-label 11.7M 1.5M 10.2M 4096
/idd 14.0M 149.0K 13.8M 1024
/rca 8.4M 579.0K 7.8M 1024
/storage 889.4M 0.0K 889.4M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 22.6G 5.0G 17.6G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
/mnt/expand/f9e6c33e-fc2c-45c4-ac57-c6f40d9360d3 117.2G 60.0M 117.1G 4096
is this right 22GB for /storage/emulated ? I would have though it should have been approx 160GB (32+128 - used space)
Actually it's right.
Adoptive storage does not merge two partitions. Or removing sd card will completely disable all installed application of your phone rather than a partial. It just provide ability to Store applications and application data to external storage without applications-aware. And the in the storage settings. You can use migrate data to point which storage to be used for data stored on /sdcard.
Hello,
It work perfectly, but because the function is not officially supported by Sony, displayed size informations are quite strange
fqj1994 said:
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Click to expand...
Click to collapse
I am now a little confused. I have a 64GB SD card and originally plan to use the entire SD card for Adoptable Storage.
Based on what's said above, does it make a difference if I choose to
1) partition the SD card to 32GB data+ 32GB for Adoptable Storage, or
2) use the entire SD card for Adoptable Storage?
Seems that it doesnt make any difference !
How I can return my phone to normal can not recognize other memories sd
For me it worked, no problem with stock camera.
Spotify did bug out a little (offline songs were stored to SD card), but a reinstall fixed it. Ii had nothing else set to SD card to begin with anyway.
Thanks for the tip! although I did have to use the whole SD card as private, using it partially would cause popups of new SD-card inserted constantly >> starting to use it would wipe the entire SD.
Using the following firmware:
KPN Mobile NL (32.1.A.1.185 / R3C)
It didn't work =/
Hi I did it all corecly, set the 64gb sd card full private... and started to install many apps... what happend is after it reached the full 16 gb(real internal storage) it would not let me instaling anything else it would just say memory full any one had this?
PS. didn't had any problem with the camera our any other app.
Also applicable on Z3?
Is this workaround also applicable on the z3 with marshmallow
Guys is it Z5c only or applicable on Z3 too?
please help.
Related
Hey out there, I could use your help. As you'll see by the screen shots on my nexus storage space is running low but I have only half the space used.
I've done a factory data reset that didn't do the trick
{
"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"
}
Can someone please help?
Sent from my Obsession
Disconnect from the computer and let the SD reload. See what you have, then. Also, you might want to put your music in the Cloud and the songs you want to listen to for the day/time, have them play offline...
jamerican413 said:
Disconnect from the computer and let the SD reload. See what you have, then. Also, you might want to put your music in the Cloud and the songs you want to listen to for the day/time, have them play offline...
Click to expand...
Click to collapse
Thanks - I'll give it a shot
Did it do the trick?
hullbay said:
Did it do the trick?
Click to expand...
Click to collapse
Unfortunately not - but it's all good, I did a factory restore and the storage space is back, just gotta copy files/flash rom again etc. I'm just glad I figured it out.
So you did a factory reset twice?
adamhlj said:
So you did a factory reset twice?
Click to expand...
Click to collapse
The first time I did a factory reset from settings>backup & reset and that didn't work.
2nd: I followed this method to return to factory stock: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
3rd: I used the nexus root toolkit found here: http://forum.xda-developers.com/showthread.php?t=1766475
-Good times :cyclops:
I am having the same issue.. Also I was wondering why there was 13.24 available when the internal memory has its own ~half gig of storage.. shouldn't the SD card storage have 16 gigs altogether?
Anyhow does anyone know how I could retrieve my extra storage space without restoring factory defaults?
Sent from my Nexus 7 using xda app-developers app
Deazul said:
I am having the same issue.. Also I was wondering why there was 13.24 available when the internal memory has its own ~half gig of storage.. shouldn't the SD card storage have 16 gigs altogether?
Anyhow does anyone know how I could retrieve my extra storage space without restoring factory defaults?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi All
13.24GB is normal (16GB formated will around 15.2GB usable, Android OS requires around 2GB) - You can get more space is you flash custom slim line ROM
Nexus 7 has 1GB of RAM - this is not storage, RAM is used to running Applications on Android
I having any similar issue with this too. when i copy a 5GB 720p mkv to Nexus 7 split over 2 x 2.5GB after watching and deleting the files Andriod does not reclaim the free space. A reboot of the Nexus 7 is required for Andriod to see the space again.
Sweet dude, thank you. I actually discovered several GB of reclaimed space after a reboot earlier today. Bonus: I got stickmount running so now I have another 8gb to play with on my flash drive with an OTG cable!!
Thanks again
-deazul
Sent from my Nexus 7 using xda app-developers app
toker_X1 said:
A reboot of the Nexus 7 is required for Andriod to see the space again.
Click to expand...
Click to collapse
Just grab SDrescan app to refresh the media database rather then reboot.
I'm having a similar problem with the 8GB version. Had been happily using it and installing a few games, then the other day attempted to install a rather large game (which was a huge play download rather than a smaller one that then downloads game data). It was a 1.3GB download and my device reckoned it had about 1.4GB of space.
The install failed and despite not installing, my device was then reporting only 270MB of space instead of the 1.4GB I had before.
I am now getting a message in the system bar telling me: "Storage space running out", even though the Storage Settings page tells me I've got about 270MB. But this means that certain apps have stopped working (gmail and gtalk), I can't install or update any apps from the play store anymore (I have even tried uninstalling a couple of things but that hasn't helped).
If I adb shell into the device and run df I get:
Code:
Filesystem Size Used Free Blksize
/dev 487M 32K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 427M 212M 4096
/cache 436M 7M 428M 4096
/data 5G 5G 278M 4096
/storage/sdcard0 5G 5G 278M 4096
So the Android status message seems to be at odds with the actual storage space available. Plus I can't figure out where the extra 1GB+ I had before has gone.
Is there any way to fix this without resorting to a factory reset since I don't fancy having to start again. I wanted to ask google but the "Contact Us" link on their Nexus 7 support page is a bad link.
Dan
EDIT: My device is running completely unmodified/unrooted stock JB
See the attachment, it makes no sense.
The bar graph at the top suggests that I have about 25% free space, which is actually what I would expect since there was about 1.4GB free before things went wrong.
The available space listed at the bottom suggests that I only have 4.5% free space.
The messages tell me that I am running out and if I try and install anything it refuses which suggests I have 0% free space.
Is the Nexus 7 incapable of consistent maths?
Code:
df
Filesystem Size Used Free Blksize
/dev 486M 48K 486M 4096
/mnt/asec 486M 0K 486M 4096
/mnt/obb 486M 0K 486M 4096
/system 639M 306M 333M 4096
/cache 436M 71M 364M 4096
/data 13G 11G 1G 4096
I'm getting same "out of space" error now. got over 1.5gig free. Any idea's? I've cleared the database
It's really strange how the storage works out.
I have 16GB N7:
Total Space: 13.24GB
Apps: 1.97GB
Pictures, Videos: 2.25MB
Audio: 20.00KB
Downloads: 16.44MB
Available: 6.40GB
Really seems I should have more storage space then 6.40GB, I mean I'm using like 2GB total storage, no movie downloads, or music on the tablet. Anyone know whats happening?
My numbers don't add up also mine says 889mb for my apps but when I click it it says I'm using 3.9 GB I added it up and the storage doesn't add the cache space your apps uses for some reason at least after I got my calculator and did some math mine doesn't
Sent from my Nexus 7 using xda premium
If you made a cmw backup that could be the cause. That happened to me. Lost about a gig or so. Go to the clockwordmod folder and you should see two folders, backup and blobs. Cmw 6 changed some stuff up. Might wanna run a search on it but it is probably the blob folder in the clovkwordmod folder.
Sent from my Nexus 7 using xda premium
naveen94 said:
If you made a cmw backup that could be the cause. That happened to me. Lost about a gig or so. Go to the clockwordmod folder and you should see two folders, backup and blobs. Cmw 6 changed some stuff up. Might wanna run a search on it but it is probably the blob folder in the clovkwordmod folder.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Was about to post the same comment. If using Cwm you may loose a gig or more space not related to the actual backup file, that may not be reflected in the total free space for the SD drive. Also if you have down loaded the Transformers movie that will suck up an additional 2 gigs.
Sent from my Nexus 7 using Tapatalk 2
Well my Nexus 7 is completely unmodified, so no cwm and no root.
I had in fact downloaded the free Transformers film - that was accounted for in the Apps (app data & media content) section of the storage screen. Now that I've watched the film and deleted it I've taken another screenshot (see attached image). The report of free space has not really changed, but the bar graph at the top suggests I have plenty of room!
Having done some digging with the device mounted over MTP it seems that Android had removed the downloaded film from the library but had not physically deleted it from storage, so it still existed in Android/data/com.google.android.videos/files/Movies. Also the failed install of the large game had left a big file in Android/obb which had never been cleared up by the play store application after the failure.
Having deleted those things manually, the system now appears to be reporting the correct amount of storage available.
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.
The goal of this was to swap /data and /sdcard with usb storage so that i could install unlimited apps and games. Swapping them does come at the price of speed as the usb interface is not as fast as the internal storage. Bascially you could do the same thing with stickmount and link2SD, but then you have to deal with stickmount and link2SD....
This is based on croniccorey's "INT2EXT+" script located here: http://forum.xda-developers.com/showthread.php?t=1716124
Thanks to rbox for recovery and jocala for UUID idea.
Warning: This will make your fireTV run slower. This works best on a clean install, but should work either way. You may see a pixelated screen on first boot and it will take a few minutes while files are copied to USB, just be patient.
There are now 3 versions of the scirpt pick your poison:
1. the original MountDataToUSB which mounts your USB drive to /data (except /data/misc). This is the total solution for external usb drive hard drives plugged into powered hub only. External Hard Drives only, DO NOT USE WITH USB THUMB DRIVE.
2.. MountPartialDataToUSB Same as #1 except it leaves /data/misc /data/system and /data/data mounted to internal storage. The downside is when you install new apps some stuff does get installed to /data/data which takes up internal storage space. Tested with USB 2.0 thumb drive and UI seems as fast as stock.
3. MountMediaToUSB which mounts your USB drive to ONLY /data/media (and the fuse mount point /sdcard) expanding where game OBB files are stored (similiar to sticking an SD Card in your phone). This should be about as fast as stock fireTV except when accessing data off /data/media but this doesn't expand /data/app
I've made this into a CWM flashable now to simplify things. You need to have the following pre-requisites:
1. Rooted with rbox's CWM recovery installed
2. ext4 formatted usb drive I recommend using the full drive, but it should work as long as it's the first partition
(google how to do this).
3. This script won't work with multiple drives plugged in as it mounts /dev/block/sda1 which is the first drive detected Mounts by UUID now so you can use jocala's BusyMount script to mount other drives after.
4. The ext4 forrmatted drive must be the only drive plugged in when flashing the zip because it grabs the UUID off of it while flashing.
Click to expand...
Click to collapse
Instructions:
1. Plug in ext4 formatted USB Drive
2. adb reboot recovery
3. Factory Reset (optional but recommended, some users have reported errors if they don't. Also first boot will take longer while it copies all files from data). If you factory reset make sure you are blocking updates.
4. Flash zip in CWM. MAKE SURE THAT ONLY YOUR DRIVE YOU WANT AS DATA IS PLUGGED IN WHEN YOU FLASH v3.0 and newer zips THAT IS WHEN THE UUID IS READ and stored.
4. Reboot (first boot may take a few mins while files are copied, pixelated screen may display for couple minutes be patient). May be very laggy while it is downloading everything from the cloud to your usb drive, but should speed up a bit after it's done.
5. a. If using full data mount - Check System about for available disk space .
b. if using Media Mount only - run this command from shell and view available storage on media:
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 974M 48K 974M 4096
/mnt/secure 974M 0K 974M 4096
/mnt/asec 974M 0K 974M 4096
/mnt/obb 974M 0K 974M 4096
/storage/usb 974M 4K 974M 4096
/system 756M 723M 33M 4096
/data 5G 946M 4G 4096
/persist 7M 4M 3M 4096
/cache 756M 13M 742M 4096
/firmware 63M 7M 56M 16384
/data_fire 5G 946M 4G 4096
/data/media 15G 750M 14G 4096
/mnt/shell/emulated 15G 750M 14G 4096
/storage/emulated/legacy 15G 750M 14G 4096
{
"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"
}
Details: When the script first starts it waits up to 30 seconds for /dev/block/sda1 to come up. If it doesn't come up (or if the usb drive is not plugged in) then it boots from internal storage. It then checks for the folder "/data" on the usb drive, if it doesn't exists it copies the files from the internal storage to the USB drive. Everything under /data is mounted to usb storage with the following exceptions /data/dalvik-cache /data/misc and /data/resource-cache
IMPORTANT: The internal storage is mounted to /data_fire if you need to flash anything in CWM copy it to /data_fire/media/0/ as CWM does not see the ext4 usb storage
I've also included a revert script (REVERT_MountSDCARDtoUSB.zip) to undo the changes in case something doesn't work. Just flash with CWM.
If you have issues check/post the output of /storage/usb/moutUSB.log
Just be aware if you update the firetv image with one of rbox's pre-rooted roms you have to re-flash this zip after right after.
Change log:
Update 2014/11/18 - v3.1 - Recommended Added KhoaTon's fix for drives with a LABEL set. See post 163 in this thread for details.
Update 2014/11/03 - v3.0 - All versions now mount by UUID. Synced all version numbers. Fixed bug in MountMediaToUSB. MAKE SURE THAT ONLY YOUR DRIVE YOU WANT AS DATA IS PLUGGED IN WHEN YOU FLASH v3.0 zip THAT IS WHEN THE UUID IS READ.
MountPartialDataToUSB_v1.0.zip [For usb thumb drives or Hard drives] Same as MountDataToUSB_v2.5 except it leaves /data/misc /data/system and /data/data mounted to internal storage. See notes above for specifics.
MountMediaToUSB_v1.0zip [For usb thumb drives or Hard drives] - Mounts only /data/media to the USB drive. Should should keep most of everything at normal speed, and expand /data/meda and /sdcard storage. This is where OBB files for games are usually stored.
MountDataToUSB_v2.5.zip [For external hard drives ONLY]- Same as v2 except re-named zip to MountDataToUSB.zip and re-named script and log file to "mountUSB.sh" an "mountUSB.log". Also fixed permission on /data_fire/media/0 so it's easier to push files directly to it for flashing in CWM. Fixed bug with /data/media/0/0 folder.
v2.MountSDCARDtoUSB.zip - (originally posted on page 3) mounts everything except for /data/misc to the usb storage
REVERT_MountSDCARDtoUSB. - Flash this to revert back to normal.
Click to expand...
Click to collapse
jmandawg said:
I DO NOT RECOMMEND ATTEMPTING THIS UNLESS YOU ARE FAMILIAR WITH THE COMMAND LINE
Click to expand...
Click to collapse
I would also highly recommend making sure your recovery is working
good point
This is exactly what Ive been waiting for.. I want to attach a 1TB USB drive to my Fire and just call it a day. I dont even care about storing movies on it or anything.. I pull from my NAS and that has 12TB in it. I just want to be able to install as many apps as I want without running out of room.
I hope this finds its way into the AFTV Tool.. Im too lazy to do this on my own. When you do this kind of crap 50-60 hours a week, reading the forums is about as much as I want to do with computers when I get home.
Anyway, thank you for your hard work! Thats awesome!
so this essentially allows apps to be installed directly onto an external without using apps to foldermount :good:
Nice work.
This method works like a champ. I did a fresh install and started with the basic items i needed. After that, copied the files over to my usb, and finished the rest.
I have 29gb space showing up in my storage and have no errors or problems with operating. This is a great way to bypass the 5.45gb of free space on a firetv.
Not sure why this isnt more visible on the front page. Great work!
t3ch42 said:
This method works like a champ. I did a fresh install and started with the basic items i needed. After that, copied the files over to my usb, and finished the rest.
I have 29gb space showing up in my storage and have no errors or problems with operating. This is a great way to bypass the 5.45gb of free space on a firetv.
Not sure why this isnt more visible on the front page. Great work!
Click to expand...
Click to collapse
Just be aware if you update the firetv image with one of rbox's pre-rooted roms you have to re-copy over the install-recovery-3.sh script and add the line to start it back into /etc/init.bueller.sh.
Maybe I will put those 2 things into an update.zip when the next rom is release.
jmandawg said:
Just be aware if you update the firetv image with one of rbox's pre-rooted roms you have to re-copy over the install-recovery-3.sh script and add the line to start it back into /etc/init.bueller.sh.
Maybe I will put those 2 things into an update.zip when the next rom is release.
Click to expand...
Click to collapse
You should really just need to rename it install-recovery.sh.
rbox said:
You should really just need to rename it install-recovery.sh.
Click to expand...
Click to collapse
From my experience, It won't work, that script is called too late and sometimes not at all. But feel free to prove me wrong, once i got it working i kinda left it as it was.
jmandawg said:
From my experience, It won't work, that script is called too late and sometimes not at all. But feel free to prove me wrong, once i got it working i kinda left it as it was.
Click to expand...
Click to collapse
Oh I see, the original instructions included editing the init. I thought you were using the mechanism that was in the install-recovery that came from supersu.
rbox said:
Oh I see, the original instructions included editing the init. I thought you were using the mechanism that was in the install-recovery that came from supersu.
Click to expand...
Click to collapse
LOL, yeah, I originally tried that, hence the file name "install-recovery-3.sh" Maybe someone can clean this up and package it, it's a lot cleaner than trying to use stickmount/link2sd.
jmandawg said:
From my experience, It won't work, that script is called too late and sometimes not at all. But feel free to prove me wrong, once i got it working i kinda left it as it was.
Click to expand...
Click to collapse
I can attest to this in some degree. Prior to editing the bueller?.init file, i attempted to just call the script as i was hesitant to modify a system init script. It didnt work.
But then again, i was using scriptmanager to do so. Like the OP, when i got it working, i called it quits.
Maybe there are ways to make this a little less dangerous, but I've only got a single firetv and having it out of commision for a while would be bad...
Thanks again to everybody that works on it. Without the rooted fw, the firetv wouldn't be as cool.
t3ch42 said:
I can attest to this in some degree. Prior to editing the bueller?.init file, i attempted to just call the script as i was hesitant to modify a system init script. It didnt work.
But then again, i was using scriptmanager to do so. Like the OP, when i got it working, i called it quits.
Maybe there are ways to make this a little less dangerous, but I've only got a single firetv and having it out of commision for a while would be bad...
Thanks again to everybody that works on it. Without the rooted fw, the firetv wouldn't be as cool.
Click to expand...
Click to collapse
It's not really dangerous at all, if the script doesn't detect your drive (sda) after 30 seconds it will boot as normal. Also with rbox's CWM Recovery there is nothing to worry about.
It's only dangerous if you fudge up the bueller init script... that might be bad.
Lol, thats the dangerous part i mean. I messed up my init script on my pogoplug, had to get out the serial cable to fix it.
I'd like to keep it accessible with software if I can.
But, like you said, even if the init script gets broken, a backup is easy to recover from. Not as bad as the pogoplug at all.
LOL, i used to have a pogoplug too and a dockstar, i guess i still do but i don't use them anymore. You right, once something doesn't work you have to rip it apart and get out the serial... I ended up getting a chromebox loaded it up with linux and never looked back.
Really, as long as the kernel starts, the sysrq method will get you to recovery. And then from there you can fix anything wrong with the file.
Hey guys,
Any ideas how much space I need on my external drive? I wonder if I can use 16Gb flash drive...
Thanks.
gerikss said:
Hey guys,
Any ideas how much space I need on my external drive? I wonder if I can use 16Gb flash drive...
Thanks.
Click to expand...
Click to collapse
Well the /data partition on the firetv is 5gb... so... if the point is to give you more space... i'd say anything over 5.
rbox said:
Well the /data partition on the firetv is 5gb... so... if the point is to give you more space... i'd say anything over 5.
Click to expand...
Click to collapse
Thanks for the quick reply! The reason I am asking because of this reply:
t3ch42 said:
I have 29gb space showing up in my storage and have no errors or problems with operating. This is a great way to bypass the 5.45gb of free space on a firetv.
Click to expand...
Click to collapse
So if original free space is 5.45Gb and he got 29Gb - looks like he moved around 24Gb... Is my math wrong somewhere?
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.