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.
Related
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!
Hmm... this is quite interesting which i taught i want to show you guys this... screenshots taken from my streak 5 of course
When you guys see the red arrow pointing to what... you guys will know what i mean :victory:
{
"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"
}
-----------------------------------------------------------
UPDATE:
While i was playing around today, i managed to get it like in the image below. See where the red arrow pointing at? Neat isnt it?
-----------------------------------------------------------
p/s: Using 16GB Kingmax class 10 microSDHC for internal and external sd
Now you guys are curious how i managed to do that?
FIRST OF ALL:
You need to open the streak housing ... follow the link below and good luck.. be gentle and be careful .. just do it slow and steady and you will be ok ... no need to rush anything there ... :good:
http://www.ifixit.com/Teardown/Dell-Streak-Teardown/3512/1
------------------------------------------------------
NEXT - SELECT APPROPRIATE USER TYPE:-
LINUX USERS:
Just follow this link > http://forum.xda-developers.com/showpost.php?p=24799755&postcount=65
WINDOWS USERS:
first.. get this... http://www.alexpage.de/usb-image-tool/
make sure it is USB Image Tool 1.59 when you download...
next get gparted-live-0.13.1-2.iso
burn it to the CD...
- after you have extracted the usb image tool... open USB Image Tool.exe
- select the corresponding usb drive and click backup, save it something like streakinternal.img
- it will take some time to complete ( have instant noodle for the time being )
- once done... replace the sd card that you want to transfer the image to and click restore and select the earlier streakinternal.img
- again.. it will take some time to complete (you can have snack this time )
note: make sure the target sdcard is the same or bigger in size (obviously)...
- once completed...
- reboot your pc and insert the burned CD earlier... let it boot from it... just press enter to everything it ask until it fully loaded into linux environment
- gparted should already show your sdcard drive there... it should show /dev/sda1 and below it got two more partition /dev/sda5 (ext3) and /dev/sda6 (ext3)
- select /dev/sda1 and right click it and select move/resize
- there should be visual displaying the drive structure and on the right, there should be arrow, drag it to the most right, click ok
- now, select /dev/sda6 and right click it and select move/resize
- again, on it, there should be arrow on the right, drag it to the most right and click ok
- once all that done, click apply and it will start to do its work..
- let it completes it work and your sd card now should be able to be use as internal sd...
- your streak should be able to boot straight away.. no need to wipe cache or something like that...
- have fun having big internal sd
p/s: i wrote this based on my memory, i hope i dont messed it up
------------------------------------------------------
POSSIBLE FAQ:
-- 01 --
Q - Will the method used gone if i do factory reset?
A - Nope. You can safely do it and the structure will be maintained.
-- 02 --
Q - Can i use more than 16gb card?
A - Theoretically, yes.
-- 03 --
Q - Can we use this as sd storage as well?
A - Sorry. We cant because it is formated in ext3, so windows see it as unformatted medium.
-- 04 --
Q - Cant we create shortcut in external sd to access it?
A - Sorry. We cant because symlink does not work on any windows formatted medium since external sd usually formatted in fat32
-- 05 --
Q - Cant we mount this at all?
A - Somebody has tried it before but since the internal sd never meant to be accessed externally, the support is pretty much impossible.
-- 06 --
Q - How can we access it and where is it located?
A - To access the space, you can use root explorer and wifi file explorer (anything similar will do) and it is located at /data from /
Therefore, you must be rooted to access it.
-- 07 --
Q - So, what the hell am i supposed to do with those huge extra GBs?
A - Well, you can brag bout it to your friends, saying it got this huge internal sd space and can install hundreds of applications or games and still got space left for more.
------------------------------------------------------
MORE ADVANCED MODS.:
If you think having large innerSD is not enough, we could have larger /system dir and possible dual usb mount support by default (in the near future hopefully) for our streak 5.
Have a visit to the link below...
http://forum.xda-developers.com/showpost.php?p=31643924&postcount=98
-------------------------------------------------------
Our streak 5 might be old but it is still competitive regardless
.
Did u change internal storage?we can use that as sd storage or not?
Sent from my Dell Streak using Tapatalk 2
Which SD card is this? I mean make and class...
Sent from my Dell Streak using xda premium
details please..!!!
BEEN TRYING WITH 16GB CARD...REIMAGED THE CARD WITH EXT3 AND ALL BUT IT WOULD NOT ACCEPT 16GB CARD......PLEASE GIVE US MORE DETAIL ON HOW TOs....THANKS IN ADVANCED..
He just installed a 16gb card and formatted it properly.
You must use extended partitions and not primary ones, at least that's what the stock card is set up as
TheManii said:
He just installed a 16gb card and formatted it properly.
You must use extended partitions and not primary ones, at least that's what the stock card is set up as
Click to expand...
Click to collapse
Does the benefit come from the class of the sd card or the size? or is it the format (ext3vs4 or some such thing)?
ellisna said:
Does the benefit come from the class of the sd card or the size?
Click to expand...
Click to collapse
class for sd card means speed... so the higher the better..
Speed class determines it's actual read and write speed, FS is important as ext4 is the most efficient fs currently available.
It's supposed to be a good deal faster then yaffs2 and more efficient then ext3
TheManii said:
Speed class determines it's actual read and write speed, FS is important as ext4 is the most efficient fs currently available.
It's supposed to be a good deal faster then yaffs2 and more efficient then ext3
Click to expand...
Click to collapse
i go on and make it ext4 both for cache and data for the internal sd.. boots up normally and yes... you can see something faster...
its a shame that the CWM 6 not supported ext4 and therefore nandroid backup is impossible for now...
i also tried and make both internal and external sd not in the slot... and see if streak manages to boot up or not.. well... it stuck at dell logo.. lol
so internal sd is a must so that phone can boot due to the needs of use cache and data dir...
I can easily make a build that supports it, it's just that the rom must also support it.
The rom could likely be modified to mount /firstboot as /data, but there's not enough partitions to also have /cache on the nand.
TheManii said:
I can easily make a build that supports it, it's just that the rom must also support it.
The rom could likely be modified to mount /firstboot as /data, but there's not enough partitions to also have /cache on the nand.
Click to expand...
Click to collapse
i see...
well i am using longhorn 2.9.3...
CWM 6 cant read ext4 because how the script work? i really thought it could since it is newer and i know streakmod had issues with ext4...
but when i am thinking back.. it seems it have same baseworks...
It's turned off on the normal S5 build as ext4 requires additional modules, as it normally doesnt use ext4 I simply built it with them off.
I dont recall of CWM 1.8/2.5 (which streakmod is based off of) even supports ext4, the earliest one I can confirm it does is 4.0 as that was the 1st version built against the stock GB recovery. GB was the 1st rom that uses ext4 by default (on devices that launched with GB or newer)
Themanni.
Can we have a third partition on the inner sdcard??? To use as external storage. If so can you help/guide how to!
Sent from my ST25i using xda premium
I havnt actually tried it (but I plan to some day in the future): just manually make the partitions and add an extra one onto the end for /system.
At that point: unless you follow a standardized layout, you're going to need to manually build CWM as CWM needs to know ahead of time the layout and size of the partitions it's going to deal with. If it doesnt it could lead to corrupt filesystems on flashes/nandroids.
If I ever do build it, it'll either be for a 8 or 16 gb card with a defined set of partitions.
You'll also need to modify the rom to actually boot from innerSDx too.
TheManii said:
It's turned off on the normal S5 build as ext4 requires additional modules, as it normally doesnt use ext4 I simply built it with them off.
I dont recall of CWM 1.8/2.5 (which streakmod is based off of) even supports ext4, the earliest one I can confirm it does is 4.0 as that was the 1st version built against the stock GB recovery. GB was the 1st rom that uses ext4 by default (on devices that launched with GB or newer)
Click to expand...
Click to collapse
well... i would appreciate if you could make it support by default of ext4... no harm to it right?
lol.. i really thought streakmod comes from 4.0 but it seems i missed that... man ... streakmod really so obselete..
TheManii said:
I havnt actually tried it (but I plan to some day in the future): just manually make the partitions and add an extra one onto the end for /system.
At that point: unless you follow a standardized layout, you're going to need to manually build CWM as CWM needs to know ahead of time the layout and size of the partitions it's going to deal with. If it doesnt it could lead to corrupt filesystems on flashes/nandroids.
If I ever do build it, it'll either be for a 8 or 16 gb card with a defined set of partitions.
You'll also need to modify the rom to actually boot from innerSDx too.
Click to expand...
Click to collapse
although i really welcome additional 3rd partition.. dont it have issues with mounting? because how streak works and meant to be, it never have one such as sd-ext ... i mean... some have tried to make it appear on windows but failed miserably.. and thus gave up on it.. and since the fs is ext type, we do need to install driver for it such as Ext2Fsd to make it able to read and write on windows... also.. for media file, it may not detect it unless we explicitly want the third partition to be used only for storage .... but if we can make it able to detect media.. that would be even better...
currently that work wonder is by using wifi file browser for now... for storing file inside /data
sd-ext is/was rather redundant as the S5 has a very large (for it's time) /data.
If anything you'd be better off making a large partition to mount as /sdcard and chainmount the real sdcard as /sdcard/sdcard2 or just /sdcard2 on ICS.
I have no idea how easy/hard all this is, I havnt tried any of it.
It really depends on if the kernal can detect additional partitions beyond innerSD0p6
I've bugged n0p about adding MTP into the ICS kernal so you can simply have a very large /data + /data/media, but he's not interested.
(though like it sounds, it only works on ICS or newer, it was introduced in HC 3.2, but we dont have a rom for that)
TheManii said:
sd-ext is/was rather redundant as the S5 has a very large (for it's time) /data.
If anything you'd be better off making a large partition to mount as /sdcard and chainmount the real sdcard as /sdcard/sdcard2 or just /sdcard2 on ICS.
I have no idea how easy/hard all this is, I havnt tried any of it.
It really depends on if the kernal can detect additional partitions beyond innerSD0p6
I've bugged n0p about adding MTP into the ICS kernal so you can simply have a very large /data + /data/media, but he's not interested.
(though like it sounds, it only works on ICS or newer, it was introduced in HC 3.2, but we dont have a rom for that)
Click to expand...
Click to collapse
thats what i have been trying to do this past weeks.. making it /sdcard and chainmount the real sdcard as /sdcard/sdcard2 but to no avail... as it has no real solution to it...
mtp support is a huge leap since many says it has better file handling protocol but if its get added to ics that we have here.. wow.. that one is a huge plus for us.. :good:
have you edited your vold.fstab?
You need to edit that and change the mounts in your ramdisk at the minimum to do so
Note from the Author -
I am moving on to the N5 now and ditching my S3. I will continue to maintain this thread, however - please do PM me if you think that something needs to be changed or updated in this thread as I doubt I will be answering questions within the thread as much. Please don't PM support questions to me. Only PM updates that need to be made in the thread.
It's been a blast!
Regards
Dan
I see this question / problem comes up a lot. Rather than retype my answer every time, I have created this thread so I can easily just give people a link to it.
Scenario
You've flashed a 4.2 ROM for the first time coming from 4.1 but Titanium Backup cannot see previous backups on /sdcard and file managers cannot see your /sdcard data. You are concerned you have lost your data.
Or.... You're looking in the storage menu and you notice the total of the "used" should leave you more "free" space
Yes! Have I lost my data?
No
Background info
Older android devices have the below (simplified) layout.
/system - Where the ROM goes (internal memory)
/data - where your apps and app data goes (internal memory)
/sdcard - your sd card (removable media)
The S3 works differently
/system - Where the ROM goes (internal memory)
/data - where your apps and app data goes (internal memory)
/sdcard - your sd card (internal memory)
See that last part? The /sdcard is now on internal memory too. Samsung have actually used the clever FUSE file system, to create the /sdcard mount point (exFAT) inside /data (EXT4). So /sdcard is actually mounted to /data/media. That's how "internal storage" goes down if you install an app or if you take a photo. It all goes into /data at the end of the day.
Back to the problem
With 4.2, /sdcard is no longer mounted to /data/media
Now, It is mounted to /data/media/0
When you use a file manager (or titanium backup) to look in /sdcard, it looks pretty much empty (which it is). Because you're looking in /data/media/0 but all your data is in /data/media
So what to do?
Quite simple and very easy.
Use a file manager with root explorer capabilities. I prefer root explorer but ES* and Solid should manage this too.
Go to /data/media
You should see:
0
legacy
obb
Along with all your other folders. Legacy and 0 are the same. Leaving 0, legacy and obb UNTOUCHED, MOVE all the other folders (which you will notice are all your missing folders and files) into the 0 folder. The only folders that should be left behind are the 3 mentioned above.
That's it. Done.
Anything else to be aware of?
Yes actually, many older recoveries still probably see /data/media as the location of /sdcard, so nandroid backups may end up there instead of /0. For example, often you end up with /data/media/clockworkmod instead of /data/media/0/clockworkmod. Some recoveries have a setting to change the location to /data/media/0 (Such as Philz recovery)
Because the Settings > Storage > sdcard shows the space free and used for /data as "sdcard" but only looks in /data/app, /data/data and /data/media/0 to get the breakdown of what is using the space, you will find that anything just in /data/media will show aup s used space, but the breakdown of apps, pictures, media etc will not show these files so it appears that they do not add up.
Example...
You have:
1 GB apps
1 GB Pictures and Video
4 GB Nandroid (Misc) - but this is in wrong place /data/media
Used space will show 6 GB
But breakdown will show
1 GB apps
1 GB Pictures and Video
0 GB Misc
So it looks like you lost 4 GB. It's a good idea to check /data/media every now and again to ensure nothing goes there by accident.
I hope this helps.
*Since ES have changed their UI a bit, here is a little "How To" locate /data/media using ES.
Open ES File explorer and press the phone with a globe icon in the top left corner.
{
"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"
}
Under "Tools" choose "Root explorer" and accept the SuperUser access prompt.
At this pop-up, press back
Press the "/" button (Which means "root directory" in Linux world)
You will now be able to see /data and within there, /media
Here you see the 0, Legacy and Obb folders that I should have and also a ClockworkMod fodler which I shouldn't. You will see otehrs... Move everything except Legacy and Obb into "0".
Click to expand...
Click to collapse
Thank you!
Quite interesting, but it raises some small questions.
1) How are things mounted in alternative 4.2.x ROMs ? CM 10.1 ? Is the same problem present ?
2) For a way to dual-boot 4.1.2 and 4.2.2 what would be the best / simplest approach expected from a kernel like Siyah or GoogyMax ?
Thanks for this how-to/information! I hope someone will read it and the repeating questions will, maybe not disappear, but getting less.
xclub_101 said:
2) For a way to dual-boot 4.1.2 and 4.2.2 what would be the best / simplest approach expected from a kernel like Siyah or GoogyMax ?
Click to expand...
Click to collapse
I assume there will be no issue for dual booting as Siyah for instance creates a new folder in which the 2nd rom is placed. The kernel just has to know where to put this 2nd rom folder (not sure if it makes any difference at all). The only tricky thing will be to link the data for both roms as done by a plugin.
I see this question / problem comes up a lot. Rather than retype my answer every time, I have created this thread so I can easily just give people a link to it.
Scenario
You've flashed a 4.2 ROM for the first time coming from 4.1 but Titanium Backup cannot see previous backups on /sdcard and file managers cannot see your /sdcard data. You are concerned you have lost your data.
Or.... You're looking in the storage menu and you notice the total of the "used" should leave you more "free" space
Yes! Have I lost my data?
No
Background info
Older android devices have the below (simplified) layout.
/system - Where the ROM goes (internal memory)
/data - where your apps and app data goes (internal memory)
/sdcard - your sd card (removable media)
The S3 works differently
/system - Where the ROM goes (internal memory)
/data - where your apps and app data goes (internal memory)
/sdcard - your sd card (internal memory)
See that last part? The /sdcard is now on internal memory too. Samsung have actually used the clever FUSE file system, to create the /sdcard mount point (exFAT) inside /data (EXT4). So /sdcard is actually mounted to /data/media. That's how "internal storage" goes down if you install an app or if you take a photo. It all goes into /data at the end of the day.
Back to the problem
With 4.2, /sdcard is no longer mounted to /data/media
Now, It is mounted to /data/media/0
When you use a file manager (or titanium backup) to look in /sdcard, it looks pretty much empty (which it is). Because you're looking in /data/media/0 but all your data is in /data/media
So what to do?
Quite simple and very easy.
Use a file manager with root explorer capabilities. I prefer root explorer but ES* and Solid should manage this too.
Go to /data/media
You should see:
0
legacy
obb
Along with all your other folders. Legacy and 0 are the same. Leaving 0, legacy and obb UNTOUCHED, MOVE all the other folders (which you will notice are all your missing folders and files) into the 0 folder. The only folders that should be left behind are the 3 mentioned above.
That's it. Done.
Anything else to be aware of?
Yes actually, many older recoveries still probably see /data/media as the location of /sdcard, so nandroid backups may end up there instead of /0. For example, often you end up with /data/media/clockworkmod instead of /data/media/0/clockworkmod. Some recoveries have a setting to change the location to /data/media/0 (Such as Philz recovery)
Because the Settings > Storage > sdcard shows the space free and used for /data as "sdcard" but only looks in /data/app, /data/data and /data/media/0 to get the breakdown of what is using the space, you will find that anything just in /data/media will show aup s used space, but the breakdown of apps, pictures, media etc will not show these files so it appears that they do not add up.
Example...
You have:
1 GB apps
1 GB Pictures and Video
4 GB Nandroid (Misc) - but this is in wrong place /data/media
Used space will show 6 GB
But breakdown will show
1 GB apps
1 GB Pictures and Video
0 GB Misc
So it looks like you lost 4 GB. It's a good idea to check /data/media every now and again to ensure nothing goes there by accident.
I hope this helps.
*ES has updated it's UI and isn't as obvious as before how to get to /data/media so see below:
Open ES > menu > tools > root explorer
When prompted, accept root access request
At the top of the screen (you've probably defaulted to sdcard) press the "/" button to get to the root of your device. From here you can browse to /data/media
Just wanting to check I've got it right before I flash sentinel 4.6
I can use megawipe to clean up the internal memory.
Install the rom from external sd card
Copy everything from data/media in to data/media/0 and I should end up with just 3 folders with 0 my external sd card
Sent from my GT-I9300 using xda app-developers app
no, 0 will be your internal SD, not external
Glebun said:
no, 0 will be your internal SD, not external
Click to expand...
Click to collapse
But it was the external previously ???
Sent from my GT-I9300 using xda app-developers app
KingAzzA said:
But it was the external previously ???
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No, never.
/data/media has always been /sdcard. The 0 comes from 4.2 because it adds multi-user support and 0 is the default user. So /data/media/0 becomes /sdcard
/extSdCard is not affected by this at all.
So if I'm using megawipe to wipe everything off my internal sd card I don't need to move anything about once the rom is flashed
Sent from my GT-I9300 using xda app-developers app
KingAzzA said:
So if I'm using megawipe to wipe everything off my internal sd card I don't need to move anything about once the rom is flashed
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
There would be nothing to move. Just ensure you back up photos etc to your computer first.
Make sure you have a rom to flash on your external sd too. I think megawipe wipes the ROM too.
Although personally I think its easier just to move the files
Reason I'm planning on using mega wipe is because everytime I uninstall an app it still leaves folders behind. Not sure which ones to delete so gonna go for a fresh start and reinstall the apps from titanium
Thanks for the help anyways.
It makes sense now
Sent from my GT-I9300 using xda app-developers app
Hmm...Seeing as someone is finally concerned about issues with the storage in 4.2,I'll first ask my question here before I move on to creating another thread,as I can't find anything no matter how much I search.
So,I was on UltimaROM 12 and,well,it freaked out some day (Dunno why,but it hadn't been working 100% well for quite a few days in addition to being slow like any Samsung ROM-The blame is on Samsung,not Kryten) and I thought I'd give AOSP another chance.So I installed Carbon ROM with Temasek's kernel and fell in love.The phone puts stock S3s to shame now.However,seeing as converting a 32gb microSD to FAT32 from exFAT is a loooooong process,I found this beauty and thought I could finally enjoy AOSP on the S3.However,now no music player finds my music,which is in the external SD card.PowerAmp for example (And any other I tried in fact) searches only in /storage/sdcard0 and /storage/emulated/0,without caring about what's in /storage/sdcard1.So that's about it,but as I listen to A LOT of music on the go,this drives me crazy.What's strange is that file managers and any other media application see the data in my external storage just fine,so eg in Gallery all my photos/videos are there.
Can anyone help before I resort to using binding commands (Or apps like FolderMount) to try and fix it?I just hope I won't have to format to FAT32,because I tend to watch HD movies on the phone and,well,i would kiss the movies bye-bye.
Thanks in advance guys!
Its not really related to this thread but most aosp rom / kernel combinations do not support exFAT so you may have to go to FAT32
Since exFAT is closed source, I would prefer to stay away from add on support modules
Its not long process to go to fat32. Copy data off. Format. Copy data back
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Its not really related to this thread but most aosp rom / kernel combinations do not support exFAT so you may have to go to FAT32
Since exFAT is closed source, I would prefer to stay away from add on support modules
Its not long process to go to fat32. Copy data off. Format. Copy data back
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
First off,thanks for replying.Secondly,it's not exFAT as it turns out.I tried an old microSD formatted to FAT32 and it had the same behaviour.Anyway...Thanks,I'll see what I'll do.
Sent from my GT-I9300 using xda premium
Odd stuff!
how can I fix this ? I have 4.86gb free storage for my device storage... but it said that I habe no free memory...
*this is happened when I open the GALLERY
babyyeobo14 said:
how can I fix this ? I have 4.86gb free storage for my device storage... but it said that I habe no free memory...
*this is happened when I open the GALLERY
Click to expand...
Click to collapse
can you provide details?
ROM
Screenshots of storage menu
rootSU said:
can you provide details?
ROM
Screenshots of storage menu
Click to expand...
Click to collapse
my Rom is wannam lite v7.0 (leaked firmware 4.2.2)
babyyeobo14 said:
my Rom is wannam lite v7.0 (leaked firmware 4.2.2)
Click to expand...
Click to collapse
Please now provide a screenshot of /data/media from a file manager please.
rootSU said:
Please now provide a screenshot of /data/media from a file manager please.
Click to expand...
Click to collapse
here sir.
Internal Memory Repartition
Hey guys, after a very long time I show you the way to repartition your internal memory (EMMC).
You can modify partitions as you want, increase data partition to install more apps, increase internal storage for media files...
It's based on a little Linux binary called Parted, it's a part of CWM/TWRP recovery ramdisk.
This means that you can repartition in any recovery of any 4.2/4.3/4.4 ROM.
==========WARNING==========
Operations on EMMC partitions could be EXTREMELY DANGEROUS if you don't understand well what you do.
If you touch wrong partitions (CSPSA, EFS, SBLs...) you can lose your IMEI or hardbrick your device (in this case only JTAG can save you) so...
READ CAREFULLY!!!!!
Responsibility is all yours, but if you follow well this guide you will not risk anything.
Stock partition table is designed to be used in stock ROM, since it uses preload partition to store some system apps and needs bigger system (ROM is heavier than CM-based ones) and bigger cache partitions (more system apps=more dalvik-cache).
This mod is compatible with any ROM except stock and stock-based.
This is the stock partition table:
{
"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"
}
You can touch ONLY:
Kernel2
SYSTEM
DATAFS
CACHEFS
HIDDEN
FOTA
UMS
Kernel2 is the backup of stock kernel, we don't need it.
SYSTEM is the /system partition (where the ROM is installed/stored).
DATAFS is /data partition (default 1.97 GB where are stored installed apps, Android settings, contacts, messages... User data).
CACHEFS is /cache partition (art/dalvik-cache is stored here, together with recovery logs/temporary files. In stock ROM here is stored also CSC. If you repartition to the minimum (at least 5 MB needed for recovery) you need to put dalvik.vm.dexopt.data-only=1 flag in system/build.prop
HIDDEN is /preload partition (some Samsung TouchWiz system apps are stored here and symlinked with /system/app. This is a swap partition on MIUI v5, CM10.2 and all CM11/Omni 4.4 builds (these 4.4 before 15 June), also every custom ROM based on Canjica device tree 4.3/4.4 (always before 15 June), resize it to the minimum (128 KB to format it as EXT2).
FOTA is Firmware Over The Air, so is needed to get OTA updates while on stock ROM, can be directly deleted.
UMS is the internal storage (3.96 GB one), you can repartition this to have less/more space, or repartition to the minimum (8 MB or less, you will need to swap internal/external storages).
Parted commands useful for us:
rm (to delete a partition)
mkpart primary (to make a partition)
format (to format a partition, only in ext2)
name (to rename a partition)
For an extended list/explanation of commands, type "help" without quotes
Let's go!
First make a nandroid backup of your current ROM, to be restored after repartition
If you touch UMS you will lose all the content of /sdcard (internal storage), so make a backup first!
You need a Linux distro or Windows with ADB configured.
Reboot device in recovery and connect to USB, then open ADB and write:
Code:
adb shell
parted /dev/block/mmcblk0
You can choose to display partitions as Gigabytes, Megabytes, Kilobytes (suggested), or Bytes by "unit **" command, where ** can be gb/mb/kb or b
Now type "print" to display partition table.
Parted create new partitions by following "Number", for example SYSTEM is 3, CACHEFS is 4 and DATAFS is 5 (for other partitions is the same), so when you create new partitions, you need to make them in order!! For example:
SYSTEM is 3 and its size is from 105906KB to 747635KB
CACHEFS is 4 and its size is from 2895118KB to 3215983KB
DATAFS is 5 and its size is from 747635KB to 2895118KB
The "end" of a partition is the "start" of the next partition
As you can see, DATAFS is between SYSTEM and CACHEFS. This means that after you create SYSTEM, you need to calculate new DATAFS size that you want and then first create CACHEFS (at the end of calculated DATAFS size) then create DATAFS from the end of SYSTEM to the start of CACHEFS.
To understand more:
We will resize now CACHEFS from 320864 KB to 5000 KB gaining 315864 KB for DATAFS:
Unmount /cache from recovery first!
Code:
rm 4 (to delete CACHEFS)
rm 5 (to delete DATAFS)
calculate now the new size of DATAFS, in this case add 315864 KB to DATAFS end: 2895118+315864=3210982 KB
calculate now the new end of CACHEFS, in this case add 5000 KB to 3210982 KB: 3210982+5000=3260982 KB
mkpart primary 3210982 (end of DATAFS and start of CACHEFS) 3260982 (end of CACHEFS, start of the next partition)
Now we made a new partition, its number is 4. Do: name 4 CACHEFS
It's time to make new DATAFS partition: from the end of SYSTEM to the start of CACHEFS
mkpart primary 747635 (end of SYSTEM and start of DATAFS) 3210982 (end of DATAFS and start of CACHEFS)
New partition has number 5, name it DATAFS by name 5 DATAFS
Basically the method is this, you can apply it to partitions listed above.
Remember to reboot recovery, go in Mounts and storage then (depending on what partitions you touched in Parted, excluding /preload) do the appropriate formats after repartition. Now you're ready to restore your nandroid backup (needs to have less size than new partitions) or install a ROM.
I suggest an useful program to check partition size on Android, Partition Table
If you touch HIDDEN partition and you are on 4.2 ROM or 4.4 builds after 15 June:
Code:
format
y
9
ext2
If you repartition UMS to the minimum, you will need to swap internal and external storages (MicroSD card will be the new internal storage):
On 4.2 open system/etc/vold.fstab and replace the content with this:
Code:
# MicroSD as internal storage
dev_mount sdcard0 /storage/sdcard0 auto /devices/sdi0/mmc_host/mmc1/mmc1
# UMS as external storage
dev_mount sdcard1 /storage/sdcard1 8 /devices/sdi2/mmc_host/mmc0/mmc0 nonremovable,encryptable
# usbdisk
dev_mount usbdisk0 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host.0
On 4.3 ROMs open system/build.prop and add these lines at the end of the file:
Code:
persist.sys.vold.switchexternal=1
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
On 4.4 ROMs just open NovaThor Settings and enable "Swap Storages"
To restore original partition table flash stock ROM through Odin with "Repartition" enabled and correct PIT file for your model, in attachment (extract zip), soon CHN pits too
I know that it's difficult to understand well the first times, but think at me that I developed this method, a lot of testing and bricks on bricks
If you found this useful, you can support me at least by pressing "Thanks" or considering to offer me a beer, a coffee... Any kind of support will be very appreciated
Reserved for "The PIT Zone" (soon available!)
Reserved
Another reserved just in case!!
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
tasosf said:
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
Click to expand...
Click to collapse
All what you should know it's wrote in the OP.
You can make our way... rm anything after Kernel2, calculate datafs+1024MB more and make again all partitions, name and format them. Read again and well the OP for clarifications, it's all wrote there
Inviato dal mio GT-I9505
I didnt found any info about it in OP so i ask:
Every partition made using this guide will be formatted as ext2? Ext2 is worse than ext4 so probably it will affect performance, am i right about it?
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
ch3mn3y said:
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
Click to expand...
Click to collapse
Format didn't work for me either. I formatted everything through TWRP to ext4.
So, this method works! I now have 3GB for data so to have all the apps installed in the internal storage and not the internal sd card (ums). This way all apps are faster because ums is formatted as fat 32 in order to be recognised on Windows.
One tricky thing was that you have to mkpart from low numbers to high, regardless if you leave for a moment organ intermediate megabytes. The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Sent from my GT-I9070 using XDA Free mobile app
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
tasosf said:
The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Click to expand...
Click to collapse
Yep, its important to not make mistakes, coz who wants to do something few times?
ch3mn3y said:
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
Click to expand...
Click to collapse
How come you want to have bigger UMS? Not all apps can be installed there and DATAFS gets full very easily. Also, it's fat32 which creates some problems by itself.
Sent from my GT-I9070 using XDA Free mobile app
I just dont use this phone as my primary and as i have xplay for games i dont need to have lots of apps on it. Additionaly i have only 4gb sdcard for it, so my internal memory is now bigger than external
Sent using TF300T - CyanogenMod 11.0/GRIMLOCK (F2FS)
i'd really like to repartition my phone's memory but i fear i'm gonna screw everything up
i see a coming soon "pit zone" in the second post, does that mean that there is an automatic way to repartition the internal memory without directly using commands?
If u knows how to make pit file after repartitioning its probably possible to use odin to repartition
Sent using GT-i9070 - VanirAOSP
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
AntaresOne said:
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
TheSteve87 said:
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
Click to expand...
Click to collapse
Completely agree mate. Also HIDDEN, you don't need it on CM/CM-based custom ROMs
Inviato dal mio GT-I9505
I really have to say this guide is just A-W-E-S-O-M-E
The process is not that easy but very well explained
A complicated by well explained method for partition........But i am a bit afraid to use .... Can u help out with the step for my issue...?
My Phone: S Advance
(Rooted with the help of http://forum.xda-developers.com/showthread.php?t=2087424)
RAM= 768 MB RAM,
ROM= 2 GB //*Note phone shows this as device storage, Pl correct if I am wrong*//
Internal=16 GB (user available=11.31 GB), //*Note phone shows this as USB storage, Pl correct if I am wrong*//
external micro SD card = Nil
I want to increase the RAM Or ROM so that my mobile should not lags/hangs
I feel that mobile is slow mainly due to less RAM......pl correct if I am wrong
I want to use the the 1GB/2GB/3GB/4GB out of Internal 16 GB to increase the size of ROM from 2GB to 3GB/4GB or RAM from 768 MB to 1GB/2GB/3GB/4GB more.....
Pl help me out with the specific steps.....
Thanks a lot @AntaresOne
@anil.xda
Yes, just 768 MB of RAM is one of the biggest performance limiting factors of this phone but sadly you can't just "increase it". You'll have to use something like a zRAM or a SWAP script. But this is just a workaround - and it too has some drawbacks I think.
Sent from my GT-I9070
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?