Database Users

[ROM] Dual Rom V1.2 | 2.2CM/AOSP 2.1 Sense in one.... [11/19/2010]

Dual Rom by TEAM ADX
Who is Team ADX....a few of us here on xda have been working on some projects together including this one. Workshed, Conap, and Gnarlyc.
What is Dual Rom....Dual Rom is the first rom on the eris that will install a 2.1 Sense based rom on your phone and at the same time it will install a 2.2 CM/AOSP mix rom onto your sd card. You will then be able to boot back and forth between the two rom by using pre-written scripts in gscipt app. No need to go into recovery.
EDIT: As of V1.2 We've changed it up a little. Both roms are half on phone and half on sd. We found this to be more stable with easier updates and a quicker install time. It also gave us the speed boost we saw with the sd rom on both roms.
What are the requirements....You will not need any special recovery's or need to make any changes to the phone. You will need to partition your sd card. Instructions for partitioning sd card are below.
Credit other then ADX team members:
unCoRrUpTeD from the cdma hero forums for all the work here http://forum.xda-developers.com/showthread.php?t=803302
Jcase for his stock sense build
CyanogenMod for the ton of work they have done to make Android better for everyone
TO PARTITION SD CARD:
NOTE THAT THIS WILL ERASE ALL CONTENTS OF YOUR SD CARD. PLEASE BACKUP YOUR SD CARD FILES.
Plug phone into pc and reboot phone into recovery. Open a command prompt or terminal and copy/paste the following commands:
adb shell
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3
rm 4 (these are removing your partitions. if you only have 1 partition it will just give you an error after deleting the first one. Just ignore these errors)
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
mkpartfs primary ext2 3501 3750 (this will be the data partition for the 2.2 rom. You can make it bigger or smaller depending on the number of apps you use. Make it no smaller then 200mb)
mkpartfs primary ext2 3751 4100 (this will be the data partition used by the 2.1 rom. You can make it bigger or smaller depending on the number of apps you use. Make it no smaller then 200mb)
mkpart extended 4101 7948 (this is needed because you can only make 4 primary partitions and we need 5 so we make an extended partition that will allow us to make 2 more partitoins inside of the extended partition)
mkpartfs logical ext2 4101 4150 (this is the cache partition for the sd rom)
mkpartfs logical fat32 4151 7948 (this will be used by the sd rom which is the 2.2 rom. You can make first partition larger and this one smaller or vice versa depending on which rom you may need more space for)
Your card should now be partitioned.
Once your sd card is partitioned correctly you can install Dual Rom. Download the zip file from the link below and put it on your sd card. Flash it like you would any other rom. The install takes about 3 times as long as a regular rom flash. The phone will reboot itself one time between installing the roms. This is normal behavior. It will automatically start the second part of the install after the phone reboots itself. Once Dual Rom is done installing reboot your phone as normal. It will boot into the 2.1 Sense Rom. Do the normal setups. Once 2.1 is set up then you will want to open gscripts, hit menu/add script. On the add script page chose load file. A list will pop up with some available scripts. For 2.1 rom you will only need to add the BootToSd script. Choose that and save it. Now in gscripts you can choose the BootToSd and it will automatically reboot your phone into the 2.2 rom. You will only have to load the BootToSd script once. In the future you will just open gscripts and choose boottosd to switch roms.
After running the boottosd script in gscripts your phone will boot into the 2.2 rom. It will take a little longer then normal for this rom on it's first boot to load since it's on the sd card. When it loads go through the setup like a normal rom. You may have a few messages pop up about things being unresponsive. Do NOT force close these. Choose the wait option. This rom will be laggy when doing the initial setup and very laggy while reinstalling all your apps. Be patient during this part. 2.2 runs pretty good on sd once it's all loaded up. Give it a while to get going. I actually hit a quadrant score of 615 with 2.2 on sd. Once 2.2 is done with setup and all apps are redownloaded you can open gscript. Again choose menu/add script. From there choose load file. You will want to add the boottophone script and the mountsd and unmountsd scripts. I think you probably know what these scripts do. BootToPhone will boot back to the 2.1 rom. Use the mountsd and unmountsd scripts to mount your sd card if you are using windows. If using linux the normal mount sd procedures should work fine.
If for some reason you can not boot into one rom or another there will also be zip files on your card that you can flash from recovery that will boot the rom that you want. We attempted to make this process as simple and user friendly as possible.
2.1 Sense rom
Based on Jcase's Sense 2.1 rom
Simple solid base stock sense.
Uses CFSv8 Kernel
Wired and Wireless tether added
2.2 CM/AOSP Rom
This is Workshed's Froshedyo rom, you can get the solo version of it HERE.
Built from cm source with some minor theme changes.
Also uses CFSv8 Kernel
Built using Conap's vendor tree
Also has wireless and wired tether.
{
"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"
}
Neither roms should really have any major bugs. Unfortunatley there is no way currently to Nand Backup the rom on the sd card. We will work on a solution to that. Hope you all enjoy!!!
NOTE: If using clockwork you need to flash package2.zip after flashing dualrom
Please wipe data and dalvik before flashing.
------------------------------------------------------------------------------------------------------------------------------------------
<<<CHANGE LOG>>>
DualRom v1.2
Moved both roms so that half of each rom is on phone and half is on sd card. The 2.2 rom system files are installed on the system partition of phone and uses the second partition of the sdcard as the data partition. The 2.1 rom now installs the system files on to the data partition of the phone and uses the 3rd partition of sdcard for data. This gives us many advantages including future no-wipe updates, quicker install, speed bonus for both roms, unlimited app space for either rom by making the data partitions of sdcard bigger so no apps2sd are needed, more stability from the roms.
Removed some bloat apps from 2.1 rom such as amazonmp3 and some stock apps.
updated the shedfroyo to v5 (ChangeLog Here)
updated kernel to Decafuct CFSv8 with loop support, speed increases, better memory management, new "smartass" governor. (upgraded for both roms)
Added some flashable zips that will be pushed to your sdcard during install that will allow you to wipe data or dalvik for either rom.(Please use the zips. Wipeing Data or Dalvik-cache the normal way in recovery will not remove the right files and will mess up and you will need to reinstall. Zips are named so you will know what they do.)
DualRom v1.1...
Added new superuser
Added Gscript lite to the 2.2 rom on sdcard
Removed Gscript from 2.1 rom, gscript lite is still there
Added correct bootanimation
Install as you would a normal rom. You can do the normal wipes in recovery then flash the rom zip from your sd card. Installation should not take near as long as it did for the last version. Your phone will still reboot once inbetween installing the 2 roms.
Download Dual Rom v1.2
Download Dual Rom v1.1
Here are zips to flash in recovery to wipe data or dalvik-cache for the sd rom. You can wipe the phone rom like you do a normal rom..
(These are already included in v1.2)
WipeDalvik-Cache
WipeData
New superuser if anyone still needs it, included in v1.1 - SuperuserUpdate

Reserved 10 chars

delted post

well done team STUD!
Sent from my ERIS using XDA App

wow sounds cool

ok illl go ahead and ask if we partition and flash this then decide to go back to unpartitioned normal running one rom how do we do that

jdog94 said:
ok illl go ahead and ask if we partition and flash this then decide to go back to unpartitioned normal running one rom how do we do that
Click to expand...
Click to collapse
you can use the option in recovery to partition the sd card...just choose 0 for swap and 0 for ext2 and it will make one fat32 partition for you....

jdog94 said:
ok illl go ahead and ask if we partition and flash this then decide to go back to unpartitioned normal running one rom how do we do that
Click to expand...
Click to collapse
nevermind... conap got it.

cool deal guess ill try it
looks like the only way to get newest FROshedYO............lol

jdog94 said:
cool deal guess ill try it
looks like the only way to get newest FROshedYO............lol
Click to expand...
Click to collapse
LOL, right now, yes, it's the only way till I open up a thread for that and the pink rom... sorry bro. ... as you can tell I've been busy with the Team.

i see that shed looks like yall have been working hard
so is the stock SD card big enough for all this ?
will the phone be just as quick as it is now????

jdog94 said:
i see that shed looks like yall have been working hard
so is the stock SD card big enough for all this ?
will the phone be just as quick as it is now????
Click to expand...
Click to collapse
yes and yes... if you buy a class6 sdcard it'll be even better. But all of this was dev'd on the stock 8gig sdcards and it's not slow for me at all.

Team ADX said:
Dual Rom by TEAM ADX
Who is Team ADX....a few of us here on xda have been working on some projects together including this one. Worshed, Conap, , and Gnarlyc.
What is Dual Rom....Dual Rom is the first rom on the eris that will install a 2.1 Sense based rom on your phone and at the same time it will install a 2.2 CM/AOSP mix rom onto your sd card. You will then be able to boot back and forth between the two rom by using pre-written scripts in gscipt app. No need to go into recovery.
What are the requirements....You will not need any special recovery's or need to make any changes to the phone. You will need to partition your sd card. Instructions for partitioning sd card are below.
Credit other then ADX team members:
unCoRrUpTeD from the cdma hero forums for all the work here http://forum.xda-developers.com/showthread.php?t=803302
Jcase for his stock sense build
CyanogenMod for the ton of work they have done to make Android better for everyone
TO PARTITION SD CARD:
NOTE THAT THIS WILL ERASE ALL CONTENTS OF YOUR SD CARD. PLEASE BACKUP YOUR SD CARD FILES.
Plug phone into pc and reboot phone into recovery. Open a command prompt or terminal and copy/paste the following commands:
adb shell
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3
rm 4 (these are removing your partitions. if you only have 1 partition it will just give you an error after deleting the first one. Just ignore these errors.
mkpartfs primary fat32 0 3500
mkpartfs primary ext2 3501 3750
mkpartfs primary ext2 3751 4100
mkpart extended 4101 7948
mkpartfs logical ext2 4101 4150
mkpartfs logical fat32 4151 7948
Your card should now be partitioned. The first partition will be used by recovery and the 2.1 rom. The last partition will be used by the 2.2 rom. The other partitions will hold the file system for 2.2 rom. You can adjust the size of the first and last partitions if you think you will need more room on one rom or the other.
Once your sd card is partitioned correctly you can install Dual Rom. Download the zip file from and put it on your sd card. Flash it like you would any other rom. The install takes about 3 times as long as a regular rom flash. The phone will reboot itself one time between installing the roms. This is normal behavior. It will automatically start the second part of the install after the phone reboots itself. Once Dual Rom is done installing reboot your phone as normal. It will boot into the 2.1 Sense Rom. Do the normal setups. Once 2.1 is set up then you will want to open gscripts, hit menu/add script. On the add script page chose load file. A list will pop up with some available scripts. For 2.1 rom you will only need to add the BootToSd script. Choose that and save it. Now in gscripts you can choose the BootToSd and it will automatically reboot your phone into the 2.2 rom. You will only have to load the BootToSd script once. In the future you will just open gscripts and choose boottosd to switch roms.
After running the boottosd script in gscripts your phone will boot into the 2.2 rom. It will take a little longer then normal for this rom on it's first boot to load since it's on the sd card. When it loads go through the setup like a normal rom. You may have a few messages pop up about things being unresponsive. Do NOT force close these. Choose the wait option. This rom will be laggy when doing the initial setup and very laggy while reinstalling all your apps. Be patient during this part. 2.2 runs pretty good on sd once it's all loaded up. Give it a while to get going. I actually hit a quadrant score of 615 with 2.2 on sd. Once 2.2 is done with setup and all apps are redownloaded you can open gscript. Again choose menu/add script. From there choose load file. You will want to add the boottophone script and the mountsd and unmountsd scripts. I thing you probably know what these scripts do. BootToPhone will boot back to the 2.1 rom. Use the mountsd and unmountsd scripts to mount your sd card if you are using windows. If using linux the normal mount sd procedures should work fine.
If for some reason you can not boot into one rom or another there will also be zip files on your card that you can flash from recovery that will boot the rom that you want. We attempted to make this process as simple and user friendly as possible.
2.1 Sense rom
Based on Jcase's Sense 2.1 rom
Simple solid base stock sense.
Uses CFSv6 Kernel
Wired and Wireless tether added
2.2 CM/AOSP Rom
This is Workshed's Froshedyo rom which you will be able to get in solo version soon if you don't want to dual boot.
Built from cm source with some minor theme changes.
Also uses CFSv6 Kernel
Built using Conap's vendor tree
Also has wireless and wired tether.
Neither roms should really have any major bugs. Unfortunatley there is no way currently to Nand Backup the rom on the sd card. We will work on a solution to that. Hope you all enjoy!!!
Download Dual Rom 1.0 Here
Click to expand...
Click to collapse
Froshedyo rom sux

workshed said:
yes and yes... if you buy a class6 sdcard it'll be even better. But all of this was dev'd on the stock 8gig sdcards and it's not slow for me at all.
Click to expand...
Click to collapse
I second that. The ROMs that get installed are plenty fast.

Seriously our devs are the sh*t!
The OP says that there is no way to nandroid on the sdcard, so is there no way to nandroid at all?

wow i thought i was the only NC person on here and now i see 2 more

UNCbassbone said:
Seriously our devs are the sh*t!
The OP says that there is no way to nandroid on the sdcard, so is there no way to nandroid at all?
Click to expand...
Click to collapse
currently, no. you'll definitely want to backup your nandroid folder before you partition the sdcard. That way if you want to go back to something you had a nand for, you can just repartition with one big fat32, throw the nandroid folder back on the sdcard and nand restore away
We'll be working on getting that straight in the next releases, we just wanted to get this out to all of you to try.

UNCbassbone said:
Seriously our devs are the sh*t!
The OP says that there is no way to nandroid on the sdcard, so is there no way to nandroid at all?
Click to expand...
Click to collapse
If you flash a different ROM (not DualROM), you can still Nandroid it.

while the card is partitioned this way can we flash different roms or are we just on dual rom till we unpartition?

So with the multiple filesystems, will you have more than one set of apps (more than one /system/app and /data/app)? If not, then what will the 2.1 ROM do with apps meant for 2.2?

2gb sd ext?!

So, I recently received my replacement and immediately got it rooted. Since I have tons of apps, I rely on transfering some apps to my SD to get me by. I read that EXT3 would be more appropriate for Myn's 2.2, so I formatted my SD EXT with 0MB swap size and 2GB space with the EXT3 format. Everything seems to have worked fine. I use 'App 2 SD Pro' to notify me of apps that are capable of transferring over and it still shows that I have 22.7GB available on my SD Card. Shouldn't it limit it to the 2GB I dedicated?

There are different kinds of apps2sd. There's the old way, where you format part of your SD card to ext2/3/4 and you have symlinks from your /data/apps directory to that partition. Then there's the new way, where Google let's you put your apps on the FAT32 partition (normal) of your SD card in the .android_secure folder.
If you're doing it with Android's built-in apps2sd functionality, then you don't need to partition your card for ext2/3/4 to put your apps on your SD card.

I run a 500mb ext4 partition, I am using dark tremors a2sd. I use a2sd from the market and it also tells me how much free space is left on the whole SD instead of how much free space is left on the ext partition.
Here's what mine looks like.
{
"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"
}

sultan.of.swing said:
I run a 500mb ext4 partition, I am using dark tremors a2sd. I use a2sd from the market and it also tells me how much free space is left on the whole SD instead of how much free space is left on the ext partition.
Click to expand...
Click to collapse
In your first pic, you have a2sd+, 384 of 457 available... That's your ext partition, no???
Edit: Bold quoted text... Still confused...

gpz1100 said:
In your first pic, you have a2sd+, 384 of 457 available... That's your ext partition, no???
Click to expand...
Click to collapse
Correct. That's the ext partition.

its just the space on the extened partion of the memory.

What's the difference between using Dark Tremor's and Google's built-in? I'm on Myn's 2.2 btw.

Also, how do I get the remaining A2SD+ ext space I have? Can't find it anywhere.

sultan.of.swing said:
Correct. That's the ext partition.
Click to expand...
Click to collapse
I don't understand?? Edit, disregard. I think your pic is showing the contents of both partitions individually.
@akarol, a little searching goes A LONG way. All your questions are answered in the first post.
http://forum.xda-developers.com/showthread.php?t=715938

Well, ok... that clarifies things a bit. However, I seem to not even know which version I am currently using. I am running Myn's 2.2 RLS 5 atm which I think might just use Froyo's method. For example, App 2 SD Pro guides me to the Manage Application screen for that specific app to move to/from SD. Does this mean I am using Froyo's method? If I am, then I don't need any EXT on my SD card right? If so, how do I remove it in Amon RA's recovery and will I need to wipe my ROM and start from scratch?

akarol said:
Well, ok... that clarifies things a bit. However, I seem to not even know which version I am currently using. I am running Myn's 2.2 RLS 5 atm which I think might just use Froyo's method. For example, App 2 SD Pro guides me to the Manage Application screen for that specific app to move to/from SD. Does this mean I am using Froyo's method? If I am, then I don't need any EXT on my SD card right? If so, how do I remove it in Amon RA's recovery and will I need to wipe my ROM and start from scratch?
Click to expand...
Click to collapse
I am not familiar with Myn's roms, but a quick look at the main thread ( http://forum.xda-developers.com/showthread.php?t=793471), seven bullets down from "Some of the features in RLS 5 (01-07-2011) include:", it clearly says, "Updated Darktremor Apps2SD (2.7.5.2)".
Then, in post #3 (http://forum.xda-developers.com/showpost.php?p=8341836&postcount=3), in the FAQ section, there's a link to more info on the apps2sd function.
Personally, I think the write up in the DT thread is more than sufficient at explaining what it is, and how to set it up. What you are probably missing is that by having DT installed, your apps are automatically installed to the ext partition, transparent to the system. If, you now use the move2sd function in settings/applications, you are in essence, moving them from the ext3 partition (on the sd card) to the main partition (also on the sd card). I see little benefit to do this. Either use one method or the other.
This brings up the point, that with the DT method, even apps that traditionally can not reside on the SD card can do so (usually) without issue. I forget the criteria for being able to be moved, but suspect it has something to do with the fact that the main /sdcard partition can be unmounted from the system's view when connected via usb. DT's method secures the ext partition from such actions.

gpz1100 said:
I am not familiar with Myn's roms, but a quick look at the main thread ( http://forum.xda-developers.com/showthread.php?t=793471), seven bullets down from "Some of the features in RLS 5 (01-07-2011) include:", it clearly says, "Updated Darktremor Apps2SD (2.7.5.2)".
Then, in post #3 (http://forum.xda-developers.com/showpost.php?p=8341836&postcount=3), in the FAQ section, there's a link to more info on the apps2sd function.
Personally, I think the write up in the DT thread is more than sufficient at explaining what it is, and how to set it up. What you are probably missing is that by having DT installed, your apps are automatically installed to the ext partition, transparent to the system. If, you now use the move2sd function in settings/applications, you are in essence, moving them from the ext3 partition (on the sd card) to the main partition (also on the sd card). I see little benefit to do this. Either use one method or the other.
This brings up the point, that with the DT method, even apps that traditionally can not reside on the SD card can do so (usually) without issue. I forget the criteria for being able to be moved, but suspect it has something to do with the fact that the main /sdcard partition can be unmounted from the system's view when connected via usb. DT's method secures the ext partition from such actions.
Click to expand...
Click to collapse
Wow, thanks! I customized my a2sd settings as instructured in post #3. However, I still cannot verify that my apps are placed on the EXT partition or in the main partition of the SD card. Any way to do this?

[GUIDE] External2Internal Ultimate

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.

[Q] How much space is actually usable on Nexus 10?

Google advertizes that I can get up to 32GB of internal memory on the Nexus 10.
I am thinking about getting this tablet, but it doesn't have a MicroSD card slot, so I need to know this:
How much of the internal 32GB can I actually use?
Does the ROM take up some of that space, and how much?

isaacwg said:
Google advertizes that I can get up to 32GB of internal memory on the Nexus 10.
I am thinking about getting this tablet, but it doesn't have a MicroSD card slot, so I need to know this:
How much of the internal 32GB can I actually use?
Does the ROM take up some of that space, and how much?
Click to expand...
Click to collapse
29.71 GB of free space + you can get more via usb otg.

Not bad...
lKBZl said:
29.71 GB of free space + you can get more via usb otg.
Click to expand...
Click to collapse
Well, that's not too bad. And USB OTG looks quite interesting.
Thanks for the quick reply.

isaacwg said:
Well, that's not too bad. And USB OTG looks quite interesting.
Thanks for the quick reply.
Click to expand...
Click to collapse
I ordered a USB OTG from Amazon but it's coming from China is there a USA source?

This may help you...
ClutchKargo said:
I ordered a USB OTG from Amazon but it's coming from China is there a USA source?
Click to expand...
Click to collapse
On Amazon's website, when looking at a product, under the "add to cart" box, there is another box labeled "More Buying Choices".
That is probably what you want.

So what about the ROM?
OK, here is one thing that is not quite clear to me.
lKBZl, you said that the Nexus 10 has 29.71 GB of free space, but where is the ROM stored?
Am I right in assuming the ROM is stored on a separate partition, and the usable partition is 32GB?
So wouldn't that make the internal memory's real capacity larger than 32GB?

16gig
What about 16gig version ?

Ashirmittal said:
What about 16gig version ?
Click to expand...
Click to collapse
13.05gb on my 16gig, but I have an USB otg so no worries for me as I have plenty micro SD cards for storage.
Sent from my Nexus 10 using XDA Premium HD app

isaacwg said:
OK, here is one thing that is not quite clear to me.
lKBZl, you said that the Nexus 10 has 29.71 GB of free space, but where is the ROM stored?
Am I right in assuming the ROM is stored on a separate partition, and the usable partition is 32GB?
So wouldn't that make the internal memory's real capacity larger than 32GB?
Click to expand...
Click to collapse
32 gb is the total size of the storage capacity.
29.71gb is what is left for you to use as you wish.
Of the 3 or so gb missing, part of that is the os partition (/system) that contains the rom, kernel, etc.
And a smaller portion of that is strictly from the format process, small files that allow the memory to work.

trickster2369 said:
32 gb is the total size of the storage capacity.
29.71gb is what is left for you to use as you wish.
Of the 3 or so gb missing, part of that is the os partition (/system) that contains the rom, kernel, etc.
And a smaller portion of that is strictly from the format process, small files that allow the memory to work.
Click to expand...
Click to collapse
OK, thanks. That clears things up for me.

isaacwg said:
OK, thanks. That clears things up for me.
Click to expand...
Click to collapse
Lol I though you'd have understood that with the space left from the 29,71 to 32, it means that there is rom and etc.
If you guys want to buy an otg adapter, I recommend not to buy a cable like this: http://www.amazon.com/T-Flash-Adapt..._2?ie=UTF8&qid=1357413912&sr=8-2&keywords=otg
since then you won't be able to use a pendrive and a headphones. Something like this is better (in my opinion):
http://www.amazon.com/SANOXY-Micro-...F8&qid=1357413953&sr=8-7&keywords=otg+adapter

I looked at afew of the otg cables when I ordered my case, but none of them get any really good reviews. Maybe I am to picky dunno I will look to see if I can find any around where I live.

Can someone with a Nexus 10 tell me how much total space is on the /system partition, how much on the /data partition and how much on the mnt/sdcard partition. Also of which how much of that is available on a clean phone on each partition. Thanks

Gizmotech said:
Can someone with a Nexus 10 tell me how much total space is on the /system partition, how much on the /data partition and how much on the mnt/sdcard partition. Also of which how much of that is available on a clean phone on each partition. Thanks
Click to expand...
Click to collapse
Total values are what you're looking for.
{
"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"
}

Thanks. And this is for a clean rom with nothing installed yet right?
It looks like /data and /sdcard are not separate partitions instead directories on the same partition unless you have binded the 2 directories Can someone confirm this please?

I'm a little late to the party but a 32GB once formated usually lose ~7% once formated as FAT/NTFS.
EXT4 should probavbly be no difference.
MB
->
300GB=279GB
320GB=297GB
400GB=372GB
500GB=465GB
1TB=0.931TB
2TB=1.86TB
3TB=279TB
->
PB
So the 32GB without any files* should have 29.7GB
*No OS or boot files etc.
It's not exactly 7% but it's close and easier to calculate than the "1024^1000=banana/shoe+cat=value".

Thank you but I was more concerned with the partition sizes as if /system partition is full, it doesn't matter how much space you have available in /data or /sdcard, it won't allow to install apps or games. I can't understand why they didn't have one partition with directories instead of partitions. That way we wouldn't have issues such as free space on one directory/partition and full up on another. I think in this sense, the iphone storage management is better.

Gizmotech said:
Thank you but I was more concerned with the partition sizes as if /system partition is full, it doesn't matter how much space you have available in /data or /sdcard, it won't allow to install apps or games. I can't understand why they didn't have one partition with directories instead of partitions. That way we wouldn't have issues such as free space on one directory/partition and full up on another. I think in this sense, the iphone storage management is better.
Click to expand...
Click to collapse
Apps (end user installed) aren't stored in the /system partition the OS is. Apps go in /data.. It would be insanely hard, and nearly impossible to fill up the /system partition.
The only phone I know (probably more) that has ever ran out of useful /system space is the Nexus One which is the reason Google stopped upgrading it because ICS wouldn't fit on the /system partition. End users got crafty though and figured out a way around the limitation by crafty partitioning magic with the Micro SDCard slot.

Yes, but the Nexus 10 does not have an SD Card slot so there won't be any other way of expanding storage once the internal storage fills up. But I see what you mean about the /system partition.
Could never get my head around this Android partitions. So am I correct to say the APK and App data are stored in the /data partition? And Game that require additional download able content is stored in the /Sdcard partition?
Now my question is, is the /data partition and /sdcard partition two separate partitions or two directories on a single partition on the nexus 10? The reason why I am asking is because if you look at the storage info of my phone (screenshot below) /data partitiom and /sdcard partition are showing different storage capacity and usage whereas your nexus 10 shows those two to have identical capacity and usage.
My concern is if one partition is full up, and you may have useless space on the other partition where as if they were directories, either they will share the space on demand. Not sure if I am explaining it correctly but for example I have a Galaxy Ace 2 which if I was to fill up the /sdcard partition, and have a adequately free /data partition, then often that free space is useless for some apps as it requires available space on the /sdcard partition. Now if they weren't partitions and instead directories, which I think the configuration is on the nexus 10, it would still show available space as both directories combined would make one partition. Which would then leave me to wonder why didn't they do the same for my Galaxy Ace 2
Ignore sdcard 2nd part, this is created on removable sdcard for purposes of Link2SD app.

Gizmotech said:
Yes, but the Nexus 10 does not have an SD Card slot so there won't be any other way of expanding storage once the internal storage fills up. But I see what you mean about the /system partition.
Could never get my head around this Android partitions. So am I correct to say the APK and App data are stored in the /data partition? And Game that require additional download able content is stored in the /Sdcard partition?
Now my question is, is the /data partition and /sdcard partition two separate partitions or two directories on a single partition on the nexus 10? The reason why I am asking is if one partition is full up, and you may have useless space on the other partition where as if they were directories, either they will share the space on demand. Not sure if I am explaining it correctly but for example I have a Galaxy Ace 2 which if I was to fill up the /sdcard partition, and have a adequately free /data partition, then often that free space is useless for some apps as it requires available space on the /sdcard partition. Now if they weren't partitions and instead directories, it would still show available space as both directories combined would make one partition.
Click to expand...
Click to collapse
They are essentially in the simplest terms exactly as you described. Two folders pointing to the same partition. That is why you can wipe your "sdcard" but all your apps remain intact in /data even though it's the same partition.
The reason your Galaxy Ace is like that is because you have a legit removable SDCard storage and it isn't part of the internal storage.. This complication in partitions w/ real sdcards is why Google refuses to put SDCard slots on any of their devices.

[REF] S3 Storage (Data Loss Recovery / Prevention / Info)

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
S3 Storage (Data Loss Recovery / Prevention / Info)
This thread is intended to give you an overview of some of the Storage of the S3 from a Data Loss and recovery perspective. It is not intended to cover USB sticks or mods to Swap / Mount other storage. It is solely to cover day-to-day data concerns and give a background to how these things work
Please note, if you have recently swapped between Android 4.1 and 4.2 and cannot find your sdcard data, you need to read [Info] Flashed 4.2? Can't find your /sdcard data?
{
"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"
}
Before we get started...
Here are a couple of threads you should get familiar with before posting on XDA.
Forum Rules - use Search before posting
Post Questions or Support queries in Q&A, NOT General
Backround of Android storage (Pre-S3)
Firstly, I think we need to understand how Android worked historically as this will help us to understand how the S3 works now.
A legacy android device, lets pretend the HTC desire on Android 2.2 as this was a standard configuration at the time. It had 2 major partitions (and several minor ones which are irrelevant to this topic). It has the /system partition and the /data partition. These were partitions of the internal NAND flash memory.
/system is where the Android operating system lives. The user could not delete or change anything in here (unless you were rooted). All the software that came with the phone was installed in the /system partition
/data is where all the userdata goes. Whenever you installed an app from the market, it installed to /data/app and it put all it's important data into /data/data. Also any system settings you changed (Wallpaper, ringtones etc) all were stored in /data/data. When you did a factory reset, it wiped /data and everything in it.
Of course, having these 2 partitions was not enough for everyday use. There was no where to store your music, photos, documents etc. /data is just for app data and settings. So this is where /sdcard comes in
/sdcard is the Android mount point for the External SD card in this legacy android device. This means that when you inserted a Micro SD card, Android used /sdcard as it's internal reference to where the card's storage is. The /sdcard was a necessity before you could take photos. Over time, bigger apps started to put other data here. For example, a GPS / Map application would store its apk (application package) in /data/app and store your personal configuration settings in /data/data but it may download and store offline maps somewhere on the /sdcard. In older devices, the internal Memory (NAND Flash) was usually too small to allow much data on it. Many users would have to root to get more storage space or keep uninstalling apps to keep the "low on space" warnings at bay
How the S3 is different
Well, the S3 is substantially different. There are of course SOME similarities. For example, the S3 still has internal NAND Flash Memory. This is often referred to as the eMMC (Embedded MultiMedia Card) - which still contains the /system and /data partitions, used in exactly the same way.
The main difference is /sdcard. The S3 is designed specifically so using an external micro sd card is NOT a necessity. It has a larger NAND Flash internal memory (eMMC) so it can also have an "internal SD card". This is where people start to get confused. The entire internal memory is an eMMC which is essentially an internal SD card, however a partition of that internal memory is /sdcard.
OK, I know - let me explain. /sdcard is a mount point that Android uses to know where to store /sdcard data. But on the S3, instead of storing it on a required external sd card, it points to an internal memory partition. Now here is the clever bit. The /sdcard actually points to /data/media (or /data/media/0 in Android 4.2 onwards). So you continue to have your /data partition, but within /data you have:
/data/app
/data/data
/data/media
The clever thing is that the file system that android uses for /system and /data is a Linux file system called Extended FS. In our case, we use the Ext 4 file system. This is important to understand because these file systems do not work with Windows so an external SD card would usually be Fat 32 file system, or exFAT so we could plug it into our windows computers and read the contents. What Samsung have had to do is use the FUSE file system to allow /sdcard (or /data/media) to exist as a FAT file system within the EXT 4 file system. Clever stuff. But it has it's pro's and cons...
You lost me at file system
All electronic systems that have an operating system and store data use a file system. Think of it in it's simplest form. Imagine a school text book. It has lots of chapters about different things. It has a "Table of Contents" in the first few pages, telling you where each chapter in the book is so if you want to know what page chapter 13 is on, you look in the contents and find the page and go straight there - The alternative is looking through each page individually to find the chapter. Not a quick process.
Well data storage works the same. When you put a file on a hard drive, sdcard, USB stick (or whatever) it is written to a specific location. When it is written to this location, the location is added to the file system. So when you put word.doc onto the drive, The file system is informed of the (very complicated) location of the file. When you tell Windows, Android (or whatever) that you want to open word.doc, the operating system consults the File system and goes to retrieve the data from its true and real (yet very complicated) location on the drive.
There are many file system types still in use today. Usually they are operating system specific. For example, Ext 4 is a Linux file system (and Android by Proxy as it is Linux kernel based) and Windows cannot read Ext file systems. Similarly, exFAT is a Microsoft file system (also used for sdcards on the S3) and cannot be used (easily) on Linux machines. Since most everyday users of the S3 are Windows users, you can see now hopefully why it was important for Sasmung to use "magic" and implement FUSE to allow an exFAT file system to be used for /sdcard, within the Ext 4 partition of /data
Did I REALLY need to know ALL that?
You know what? Probably not but it may go some way to help understand the limitations we will cover later on.
A bit more info for the S3
Obviously, the internal memory supplied with the S3 may not be enough for all users so they added the ability to add expanded memory in the form of the Micro SD card. Android uses the Mount point of /extSdCard now, instead of /sdcard like it used for legacy devices - because /sdcard is already in use elsewhere.
One thing many of you have probably noticed is that with the S3, there is no option to mount the /sdcard or /extSdCard as USB Mass storage on your computer. You must use MTP or PTP.
PTP - Photo Transfer Protocol. When you connect your S3 to your computer using PTP, Your computer sees it as a camera. It will show photos on your "camera" and will set about implementing the default camera options (such as suggesting you import your photos) etc. It won't show documents or other media necessarily.
MTP - Media Transfer Protocol. When you connect your S3 to your computer, it will be seen as a media player. This should allow you full access to all the files on there, including word documents and the such like.
One of the reasons for this is that because /sdcard points to something using the FUSE file system and is not a true partition, it would be difficult to allow it to be used as USB Mass Storage. It may or may not be possible but the biggest advantage of using MTP / PTP is that the computer and the S3 can both access the internal memory at the same time. With USB Mass Storage (UMS) this is quite awkward and can result in errors.
Deleting data
This is partially why we needed to understand a little about file systems. So I could explain to you how data is handled when it is deleted.
As I explained earlier, when you write a file to memory, a corresponding entry is written to the file system to advise the OS where the data is. Sure, you may think you are writing the file to /sdcard/documents/work directory on the internal memory, but in reality these directories or folders do not actually exist at a memory hardware level. The data is written to a block and the file system is informed where that block is, how big the file is, what directory it should appear in to the OS etc. When a file is written the memory, the OS see's the available space go down and the used space go up. All this information comes from the file system.
When you delete the file, the actual data is NOT deleted. It remains where it is on the memory. The block is not overwritten. When the OS is told by the user to delete the file, the File system entry is deleted. This changes the free/used space as the file system is no longer accounting for the data, however the truth is the data still exists. When the next request to write a file to the memory comes from the OS, the file system will think the block where the old data was is empty and will overwrite it.
It is this difference between the file system and reality that allows data to be recovered by external software. if you do not write any data to the memory, external software can scan the memory for data whilst bypassing the file system all together. Ff course the window is small. You only have a very limited time to recover data before the file system allows the data to be overwritten with a new entry.
This is not just true of a deleted file. Even formatting the memory (which is actually just re-creating a new, blank file system) leaves all the data in tact behind-the-scenes and can all still be recovered until you start writing data to the memory. Cool huh?
Wow, all this time I've been stressing, is it really that simple?
Awwww snap! You got me. No it is not that simple. All this PC software, example: Piriform recuva only works on a computer drive. In windows, imagine this is anything with a Drive Letter. C: drive etc.
The only way to get a drive letter on your sdcard is to use USB Mass Storage mode, which as previously discussed - is not possible on your S3 (unless you are rooted, you can mount USB mass storage in custom recovery or use a UMS app from Play). The alternative is to use a card reader on your PC and put the sdcard in it.
There are also apps like Undelete for root users - which again, you guessed it - requires root. So if you're not rooted, it's simplest to use a card reader which can be bought for peanuts.
It's worth mentioning, NONE OF THE ABOVE will work with /sdcard on internal memory. It is not possible to get your data back once deleted from internal memory. Once gone, it's gone forever. You can only restore from /extSdCard (removable, external SDcard)
Phone won't boot, can I get my data back from internal memory?
Let's start by saying, it depends why your phone won't boot. If it's an SDS (Sudden Death Syndrome) type issue, where your internal eMMC (NAND FLash memory) has failed, then no. However, if you believe this is not the case then you can get your /sdcard data using adb BUT you need a custom recovery to be flashed via Odin before you do this. Read [REF] Understanding the basics before rooting your S3
However, if out of curiosity - you do still want to get your data off, using adb , read below:
Pre requisite is having adb "installed" on your windows PC. Download THIS file and follow the instructions in the readme.
You need to observe the following. For android 4.1.x and earlier, /data/media for android 4.2.x and newer, /data/media/0 - I will assume 4.2.2 for this guide,.
1) Boot into recovery, connect usb and go to "mounts and storage". Toggle the "mount data" options to mount these partitions. Tip, when mounted, the option then becomes "unmount data"
2) Open "cmd" in Windows and type the below code, which will copy all your data to a folder called sdcard on your windows desktop
Code:
adb pull /data/media/0/ c:\users\rootsu\desktop\sdcard
Also note, this assumes you have windows vista or newer. Also, it assumes your windows username is rootsu.
That's it, simple.
Display and Digitiser won't work, can I get my data back from internal memory?
You can use adb and a custom recovery to pull data from your /sdcard or even app data from /data/data
Pre requisite is having adb "installed" on your windows PC. Download THIS file and follow the instructions in the readme.
You need to observe the following. For android 4.1.x and earlier, /data/media for android 4.2.x and newer, /data/media/0 - I will assume 4.2.2 for this guide,.
1) Boot into recovery, connect usb and go to "mounts and storage". Toggle the "mount data" options to mount these partitions. Tip, when mounted, the option then becomes "unmount data"
2) Open "cmd" in Windows and type the below code, which will copy all your data to a folder called sdcard on your windows desktop
Code:
adb pull /data/media/0/ c:\users\rootsu\desktop\sdcard
Other things you may want to pull.....
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db c:\users\rootsu\desktop\sdcard
Code:
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db c:\users\rootsu\desktop\sdcard
Also note, this assumes you have windows vista or newer. Also, it assumes your windows username is rootsu.
That's it, simple.
Data corruption
When data becomes corrupt, there's really not a lot you can do. The file system knows where the data is already. If it's corrupt, you're stuck. Most common causes of corruption are:
1) Dirty unmount of /sdcard. SD card pulled out whilst it is being written to / phone shuts off whilst being written to. SOMETIMES - Plugging the card into a card reader in windows, Windows will ask to fix it and MAY fix it.
2) Fake SD card. This is really the MOST common. Get a card reader ans use:
h2testw.exe for windows to test your card in a card reader. Set it to read the full size of the card, which will take hours but well worth it.
If you get a result like this:
Code:
Warning: Only 63995 of 63996 MByte tested.
The media is likely to be defective.
3.8 GByte OK (8072512 sectors)
58.6 GByte DATA LOST (122989248 sectors)
Details:2 MByte overwritten (4096 sectors)
...Then you have a fake card, that is really 4 GB. I'll explain this.
Commonly, fake cards are reprogrammed to "think" they are high capacity cards, such as 32 GB or 64 GB to defraud buyers out of money. This is common on eBay (Never buy cards from eBay).
When these cards are formatted, the file system also thinks it is this fake capacity. Normally, when a card is full, the file system will report to the OS there is no more space and this prevents additional writes to the card. However, in the case where the card is 4GB and the File system thinks it is 64 GB, the tricked file system doesn't know the card is full. The file system keeps allowing data to be written to the card, over writing the existing data but without replacing the file system entries. The file system thinks data that has been overwritten hasn't been overwritten so when you try to open one of these files, it is essentially "corrupt" or non-existent.
Preventing data loss
Time to wise up guys. It is possible to recover data off your removable media, but internal memory - very unlikely. No apps on your PC or Android will help with deleted data. So you need to backup.
Dropbox - Use dropbox to automatically upload your photos to online storage.
Foldersync - Use FolderSync to upload important sdcard files to your dropbox account, or better yet - got a computer thats always on at home? Set foldersync to schedule a sync over wifi whilst you're asleep.
Other info
Interesting tidbits

Quite an exhaustive reference guide you got here rootSU thanks this will sure come handy for all of us :good:

Cheers

Thank you very much for taking the time to write this. It's a non academic approach to a sum of keywords and all of them are explained in such a manner that it would be almost impossible to misunderstand

Nice!
Nice post!
There are a few other interesting tidbits of info that might be worth mentioning:
- eMMC has an internal micro-controller that runs very specific firmware (and SDS was mainly caused by a bug in that firmware)
- eMMC (just like SSD) has specific writing/erasing limits and commands to deal with that - as a very general idea it can write about 4k at a time but can only erase in much larger blocks - like 64k (at least, but a 16GB model could have a much bigger block); normally on the same erase-size block there is very special list maintained, and based on that list wear leveling is implemented;
- all flash-based memory AGES - there is only a limited amount of erase/writes cycles possible before a point where the info is no longer reliably-stored; in some models that value can be incredibly small! to avoid writing more to some regions than other a mechanism call wear leveling is implemented; that one can have a big impact on both speed and reliability (but really don't expect it to create miracles)
- since it is very important for the speed and reliability of the flash memory to return unused blocks to this internal lists there are special TRIM commands that informs the firmware that the block can be garbage-collected; with an OS that supports TRIM, when a file is erased the blocks are also TRIMmed; this is one extra level that makes recovery basically impossible under normal circumstances
- this does not really mean that things are completely impossible to recover, just that you might need to spend so much on it that recovery would be impractical for any item worth less than 100000 US$ to 1 million US$
EDIT
- also just as with SSD it is not a bad idea to keep a good percentage of the flash memory free - IMHO at least 4GB for 16GB models, 6-8GB for 32GB models - that will improve performance since fragmentation (CLARIFICATION - free-space fragmentation) will grow much slower
- unfortunately there is no program for eMMC similar to smartctl (or any other SMART-data reading program) on normal SATA/IDE/SCSI disks - there seem to be some proprietary commands that are somehow similar but those are generally undocumented.

xclub_101 said:
Nice post!
Click to expand...
Click to collapse
I've put a link to your post in post 1. Where as it's not strictly relevant to my point, it is interesting stuff....
Fragmentation isn't an issue on ssd's. Its an issue on hdd because the head must physically move to another area of the Platter to get the data. That's the slow down. Defrag of a hdd moves all the used blocks (data) together so the actuator doesn't need to move much.
Performance degrades over time on ssds because every write, if data already exists must be erased too. But this hasn't really been an issue so much since TRIM became widely available.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
...
Fragmentation isn't an issue on ssd's.
...
Click to expand...
Click to collapse
Thank you.
Also sorry for the misunderstanding with my contraction - what I wanted to say was free space fragmentation - that one does matter a lot on solid-state memory because of the garbage collection and some controllers have been famous for having a huge drop in performance with little free space - I will try to also correct that post.

xclub_101 said:
Sorry, I used a misleading contraction - what I wanted to say was free space fragmentation - that one does matter a lot on solid-state memory because of the garbage collection and some controllers have been famous for having a huge drop in performance with little free space - I will try to also correct that post.
Click to expand...
Click to collapse
Yep, it's true about Garbage collection, but TRIM *should* handle this nicely as should "over provisioning" although probably, some cheap SSD's may not over provision.
EDIT> Actually (sorry everyone for off topic) if you're interested in SSD's, these articles are a "fun" read... (I put fun in speech marks as it depends how geeky you are )
http://en.wikipedia.org/wiki/Trim_(computing)
http://www.pcworld.com/article/2038...-ssds-what-makes-these-speedy-drives-hum.html

Update to post 1:
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

Awesome bits of info. This is the game changer. I learned a whole lot just by reading here in XDA. I've only been using Android for a few weeks but thanks to XDA, I've already rooted, installed a bunch of apps and kept my OCD in check.

my device memory has corrupted and when i start recovery mode i get "E: faild to mount /cash (invalid argument) "