Is this how A2SD supposed to work?
I have MCR R8 with old school A2SD installed, and have a 512MB ext2 partition on my SD card. Lately I have been getting the "low on space" warning all the time when I install new apps, and have to uninstall some apps in order to put some new apps on.
Upon checking, all my apps are only using about 70MB of my ext2 partition, and there is still 400MB+ space left there. On the other hand, there is only about 20MB left on my phone storage, causing the "low on space" warning popping up whenever I put new apps onto my phone. I've noticed that when a new app is installed, only part of it goes to my ext2 partition, while the remaining goes to my phone storage.
For example, this is some partial output of "adb shell df -h" before and after Google Earth is installed:
Before:
/dev/block/mtdblock5 147.6M 126.3M 21.3M 86% /data
/dev/block/mtdblock4 40.0M 22.4M 17.6M 56% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mmcblk0p2 457.4M 67.4M 365.6M 16% /system/sd
Click to expand...
Click to collapse
After:
/dev/block/mtdblock5 147.6M 141.4M 6.3M 96% /data
/dev/block/mtdblock4 40.0M 22.4M 17.6M 56% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mmcblk0p2 457.4M 72.8M 360.2M 17% /system/sd
Click to expand...
Click to collapse
i.e. only about 5MB of Google Earth installation went to the SD card, while the other 15MB was installed on the phone storage.
I'm up to the point that I always have to remove apps in order to installed new ones... which is kind of frustrating...
Additional information (is this how a properly installed A2SD supposed to look?):
C:\AndroidSDK\android-sdk-windows\tools>adb shell ls -l /data
drwxrwxr-x 1 1000 1000 2048 Aug 8 19:06 ←[1;34manr←[0m
lrwxrwxrwx 1 0 0 14 Aug 18 14:47 ←[1;36mapp←[0m -> ←[1;34m/system/sd/app←[0m
lrwxrwxrwx 1 0 0 22 Aug 5 14:51 ←[1;36mapp-private←[0m -> ←[1;34m/system/sd/app-private←[0m
drwxr-xr-x 1 0 0 2048 Aug 5 14:47 ←[1;34mase←[0m
drwx------ 1 1000 1000 2048 Aug 5 14:53 ←[1;34mbackup←[0m
drwxrwx--x 1 1000 1000 2048 Aug 25 12:43 ←[1;34mdalvik-cache←[0m
drwxrwx--x 1 1000 1000 2048 Aug 25 12:43 ←[1;34mdata←[0m
drwxr-x--- 1 0 1007 2048 Aug 5 14:51 ←[1;34mdontpanic←[0m
lrwxrwxrwx 1 0 0 11 Aug 5 14:51 ←[1;36mdrm←[0m -> ←[1;34m/data/local←[0m
drwxr-xr-x 1 0 0 2048 Aug 5 14:47 ←[1;34metc←[0m
drwxrwx--x 1 2000 2000 2048 Aug 18 14:38 ←[1;34mlocal←[0m
drwxrwx--- 1 0 0 2048 Aug 5 14:51 ←[1;34mlost+found←[0m
drwxrwx--t 1 1000 9998 2048 Aug 25 17:14 ←[1;34mmisc←[0m
drwx------ 1 0 0 2048 Aug 25 12:17 ←[1;34mproperty←[0m
drwxrwxr-x 1 1000 1000 2048 Aug 25 18:24 ←[1;34msystem←[0m
Click to expand...
Click to collapse
How many apps have you got installed? A simple cache clear could sort your issues as I had the same on Pays rom.
Sent from my HTC Desire using XDA App
cache or dalvik-cache?
I tried "wipe cache" using Amon-RA and it didn't help. Going to try "wipe dalvik-cache" next...
EDIT: ok, wiping dalvik cache didn't help either
Is it normal that when you install Google Earth, 15MB goes to phone storage and 5 MB goes to ext partition?
anyone????
tsekh501 said:
Is it normal that when you install Google Earth, 15MB goes to phone storage and 5 MB goes to ext partition?
Click to expand...
Click to collapse
yes...its one of the app´s...some app´s still need this
Depending on the ROM you're using, if it has bulitin aufs capability, you can modify the script i posted a while ago (in the aufs writeable /system thread) to overlay /data/data and /data/app with the writeable partition. Then you really don't need a2sd/app2sd or any 'move to sdcard' froyo support as your apps magically have lots more storage to write to.
I'm currently using this on CM6 and have been installing huge apps like Fennec and Asphalt with no issues.
Hi guys!
I'm here to ask for help ^^
I have my HTC Desire root and S-OFF with the CM7-R2 Hboot.
But I'm struggling with the A2SD script installed by default on the LeeDrOiD HD V3.3.3-Port-R5.
Everything works great except that the A2SD can't be managed manually.
I explain :
I have about 80 apps and the ROM is DATA++ on the CM7-R2 Hboot
So, I have a 288 MB of internal memory and 0.94 MB of A2SD memory
The thing is that, little by little, when I install apps both internal and sd-ext memory decrease... By now, I only have 25 MB left on the internal memory whereas it remains 484 MB on the sd-ext one!...
And it comes a moment where I have under 15 MB free on the internal memory and I no longer can install apps...
My question is : Is it possible to manage the memories and move some apps on the internal memory to the sd-ext? (because I think the point of such a script is to free some internal memory right?)
Thanks in advance for your answers
Bye!
PS: excuse my language, I'm not a native english speaker
If you installed A2SD correctly, all apps you install will be moved to EXT partition automatically. So to make sure A2SD is working, do the following:
Get a terminal emulator, open it and enter
Code:
su
ls -l /data
Now post the output here.
SwiftKeyed from dGB with Transparent XDA App
Hi!
This is what I get:
# export PATH=/data/local/bin:$PATH
# ls -l data
total 30
lrwxrwxrwx 1 0 0 14 Oct 31 20:47 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 Oct 31 20:47 app-private -> /system/sd/app-private
drwx------ 1 1000 1000 2048 Oct 31 22:55 backup
drwxrwx--x 1 1000 1000 2048 Oct 31 20:47 dalvik-cache
drwxr-xr-x 1 0 0 2048 Oct 31 20:39 data
drwxr-x--- 1 0 1007 2048 Oct 31 20:47 dontpanic
lrwxrwxrwx 1 0 0 11 Oct 31 20:47 drm -> /data/local
drwxr-xr-x 1 0 0 2048 Oct 31 20:39 etc
drwxr-xr-x 15 0 0 0 Oct 31 22:54 htcfs
drwxr-xr-x 1 2000 2000 2048 Oct 31 20:47 local
drwxrwx--- 1 0 0 2048 Oct 31 20:47 lost+found
drwxrwx--t 1 1000 9998 2048 Nov 1 00:06 misc
drwxr-xr-x 1 0 0 2048 Oct 31 22:56 property
drwx------ 1 1000 1000 2048 Oct 31 20:47 secure
drwxrwxr-x 1 1000 1000 2048 Nov 1 00:03 system
-rw-r--r-- 1 0 0 5943 Oct 31 22:55 zipalign.log
#
The app data seems to be linked to the EXT partition but my internal memory keeps decreasing...
Hope it'll help to solve my problem
Thank you
Cheers!
anyone encountered this issue?
Output shows A2SD is working correctly.
lrwxrwxrwx 1 0 0 14 Oct 31 20:47 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 Oct 31 20:47 app-private -> /system/sd/app-privat
Click to expand...
Click to collapse
The reason why your internal memory decreases are:
1.) Dalvik cache is on internal memory
2.) Even if one is using A2SD, some app data is still stored on /data. That's how it is.
But it will help a lot when you move dalvik cache to ext. You do this by flashing this script from leedroid's thread page in recovery:
http://leedroid.ftp.rshost.eu/Bravo_Addons/Move-Dalvik-to-sdext.zip
This will minimise the decreasing of your internal memory very much.
Ok thank you
I have used the move-dalvik-2-ext script and I now have 190 MB free on the internal !! thank you
But I will try someday to install the sibere's DATA2SD script :
http://forum.xda-developers.com/showthread.php?t=852219
Thanks again ^^
cheers!
No problem. Press the thanks-button.
MatDrOiD said:
Output shows A2SD is working correctly.
The reason why your internal memory decreases are:
1.) Dalvik cache is on internal memory
2.) Even if one is using A2SD, some app data is still stored on /data. That's how it is.
But it will help a lot when you move dalvik cache to ext. You do this by flashing this script from leedroid's thread page in recovery:
http://leedroid.ftp.rshost.eu/Bravo_Addons/Move-Dalvik-to-sdext.zip
This will minimise the decreasing of your internal memory very much.
Click to expand...
Click to collapse
I've to flash the .zip before or after flashing the rom and it's radio?
Bobbi lim said:
I've to flash the .zip before or after flashing the rom and it's radio?
Click to expand...
Click to collapse
after... if u flash it before the rom then whats it going to move?
Sent from my HTC Desire
Bobbi lim said:
I've to flash the .zip before or after flashing the rom and it's radio?
Click to expand...
Click to collapse
Of course after , if u do it before nothing gonna move cuz u've no ROM installed bro
Sent from my HTC Desire using xda app-developers app
I have an Epic4G running
Code:
Marcusant Revival v1 ROM
Samurai 3.0.1 Kernel
ClockworkMod 5.0.2.7
ROM Manager Premium v4.8.0.6
I've installed
Code:
Titanium Backup Pro v4.6.5.1
App 2 SD Pro v2.42 (http://android.a0soft.com)
I've moved all movable apps to the /sdcard, except for "ROM Manager".
I've backed up "all apps & data" with TitaniumBackup.
This is all 'on' the current /sdcard, which is the stock, out-of-the-box 8GB card:
Code:
adb devices
List of devices attached
393071F74C1D00EC device
adb shell
#
# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 181.4M 32.0K 181.3M 0% /dev
tmpfs 181.4M 0 181.4M 0% /mnt/asec
tmpfs 181.4M 0 181.4M 0% /mnt/obb
/dev/block/stl9 251.8M 211.9M 40.0M 84% /system
/dev/block/stl10 484.8M 332.8M 152.0M 69% /data
/dev/block/stl11 163.2M 112.0K 163.1M 0% /cache
df: /mnt/.lfs: Function not implemented
/dev/block/vold/179:1
14.7G 13.3G 1.4G 91% /mnt/sdcard
/dev/block/vold/179:1
14.7G 13.3G 1.4G 91% /mnt/secure/asec
/dev/block/dm-1 4.1M 2.6M 1.5M 64% /mnt/asec/com.hcom.android-1
/dev/block/dm-2 2.0M 108.0K 1.9M 5% /mnt/asec/com.HexPlus-1
...
/dev/block/dm-88 5.1M 3.2M 1.8M 64% /mnt/asec/com.amazon.kindle-1
# ls -a /mnt
.lfs
obb
asec
secure
sdcard
I've purchased a new 32GB Class10 sdcard.
I've formatted it @linux desktop to a map of:
Code:
/dev/sde1 -> 29.25 GB FAT23
/dev/sde2 -> 1.5 GB ext4
/dev/sde3 -> * (~62 MB) swap
checking,
Code:
fdisk -l /dev/sde
Disk /dev/sde: 32.0 GB, 32018268160 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62535680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d58e8
Device Boot Start End Blocks Id System
/dev/sde1 2048 59248639 29623296 c W95 FAT32 (LBA)
/dev/sde2 59248640 62396415 1573888 83 Linux
/dev/sde3 62396416 62535679 69632 82 Linux swap / Solaris
I clearly need to move data from the 'old' sdcard to the 'new' one.
I've read a bunch of sources online, and they mention "/system/sd" directory, which I do *NOT* seem to have, and they fail to make any mention of "/mnt/asec", which I *DO* have ...
Since there's a different partition map, and I'm guessing a different directory structure that'll be used (?), what -- exactly -- needs to get copied to what?
The goal is to copy correctly/completely, swap in the new card, and boot successfully.
Better safe than sorry ...
Honestly, I just did an sdcard swap...and all I did; make a folder on my PC desktop, drag all files to folder from phone, unmount and insert new SD in phone, drag and drop files on new SD. No problems.
sent from my EPICally transmogrified EI22: Thunderhawk III- adrenaline injected, SUPERCHARGED
and how did you partition your new sdcard? single partition, FAT32?
[email protected] said:
and how did you partition your new sdcard? single partition, FAT32?
Click to expand...
Click to collapse
I didn't- just moved the files. However, it was just a couple of days before I Odined- went to EC05, rerooted, and then to EI22- so it may have been buggy and I never even had time to notice
- I considered repartition, but wanted to see what would happen if I just dropped the files. Everything seemed to have run smoothly for a couple of days, but like I said, I rerooted and moved to EI22 shortly after
> I didn't
Then that's likely a different case altogether. I'm specifically asking about what-goes-where? in the multiple-partition case.
List of devices by name:
Code:
su
ls -l/dev/block/platform/omap/omap_hsmmc.0/by-name/
lrwxrwxrwx root root 2012-07-01 01:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-01 01:03 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-07-01 01:03 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-01 01:03 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-01 01:03 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-07-01 01:03 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-01 01:03 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-01 01:03 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-01 01:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-07-01 01:03 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-01 01:03 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-01 01:03 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-07-01 01:03 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
Code:
su
find /dev/block/platform/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_gnex_partitions.txt
Code:
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot0: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot0 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot1: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p13: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p12: 14.5 GB, 14539537408 bytes
4 heads, 16 sectors/track, 443711 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p11: 452 MB, 452984832 bytes
4 heads, 16 sectors/track, 13824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p10: 685 MB, 685768704 bytes
4 heads, 16 sectors/track, 20928 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p9: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p8: 12 MB, 12517376 bytes
4 heads, 16 sectors/track, 382 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p7: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p6: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p5: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p3: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p2: 3 MB, 3670016 bytes
4 heads, 16 sectors/track, 112 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p1: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/omap/omap_hsmmc.0/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Mounted filesystems:
Code:
su
df
Code:
Filesystem Size Used Free Blksize
/dev 347M 32K 347M 4096
/mnt/asec 347M 0K 347M 4096
/mnt/obb 347M 0K 347M 4096
/system 643M 347M 295M 4096
/factory 19M 8M 11M 4096
/cache 425M 7M 418M 4096
/data 13G 773M 12G 4096
/storage/sdcard0 13G 773M 12G 4096
Temporary fstab:
Code:
su
mount
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
ytwytw said:
Hi
Here is my copy of Partition Table
It's Samsung Galaxy Nexus (GSM) and its Bootloader PRIMEKL01
Code:
(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
hope to be useful to whoever stuck
cheers
Click to expand...
Click to collapse
Links:
How to install Jelly Bean 4.1 on Galaxy Nexus GSM edition
[GUIDE] Making Dump Files Out of Android Device Partitions
I run df on my Nexus and see in the last line:
/mnt/asec/com.meteonova.markersoft-1 13M 11M 1M 4096
What's this?
Is it possible to repartition my nexus ?
Sent from my Galaxy Nexus using xda premium
siealex said:
I run df on my Nexus and see in the last line:
/mnt/asec/com.meteonova.markersoft-1 13M 11M 1M 4096
What's this?
Click to expand...
Click to collapse
/mnt/asec/ is used when an application uses encryption
http://www.androidpolice.com/2012/0...n-the-play-store-google-disables-drm-for-now/
http://nelenkov.blogspot.com/2012/07/using-app-encryption-in-jelly-bean.html
seriousia said:
Is it possible to repartition my nexus ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Probably, you'll have to generate a valid pit file.
Hi! Sorry for this very noob question but I just want to ask how did you do this? I really really wanted to know what my device's memory block/partition is because I wanted to recover some files.. I have a sony xperia J phone with me btw.. Thanks!
shael1992 said:
Hi! Sorry for this very noob question but I just want to ask how did you do this? I really really wanted to know what my device's memory block/partition is because I wanted to recover some files.. I have a sony xperia J phone with me btw.. Thanks!
Click to expand...
Click to collapse
There's no exact procedure. The best way is to check under /dev/block of there is any block device listed. You can use adb shell to list all mount points and see if something coherent comes out.
scandiun said:
There's no exact procedure. The best way is to check under /dev/block of there is any block device listed. You can use adb shell to list all mount points and see if something coherent comes out.
Click to expand...
Click to collapse
I'm sorry again for this second noob question but how do you check "under /dev/block".. or "adb shell" Is it by using the command prompt or cygwin terminal? really confused with all these stuffs. sorry :/ just new to this.
shael1992 said:
I'm sorry again for this second noob question but how do you check "under /dev/block".. or "adb shell" Is it by using the command prompt or cygwin terminal? really confused with all these stuffs. sorry :/ just new to this.
Click to expand...
Click to collapse
You need to have adb installed on the computer and then enable USB debugging on the phone, and connect it via USB to the computer. That's basic stuff you should learn first.
The other are basic unix commands.
scandiun said:
You need to have adb installed on the computer and then enable USB debugging on the phone, and connect it via USB to the computer. That's basic stuff you should learn first.
The other are basic unix commands.
Click to expand...
Click to collapse
Yes. I already have adb installed on my pc and I already enabled USB debugging.. what's next?
shael1992 said:
Yes. I already have adb installed on my pc and I already enabled USB debugging.. what's next?
Click to expand...
Click to collapse
Run adb shell from Windows Command Prompt and then you have some examples on the first post.
scandiun said:
Run adb shell from Windows Command Prompt and then you have some examples on the first post.
Click to expand...
Click to collapse
Thank you so much for your help. I now get it. This happened when I tried to do the first code you posted on the first post:
shael1992 said:
Thank you so much for your help. I now get it. This happened when I tried to do the first code you posted on the first post:
Click to expand...
Click to collapse
There is an space after the l. Try this other command:
Code:
ls -lR /dev
scandiun said:
There is an space after the l. Try this other command:
Code:
ls -lR /dev
Click to expand...
Click to collapse
Hi! Just wanna say thanks a lot for answering all my questions, you really helped me and I got the whole thing running and successfully retrieved some files, which is my purpose in going all these hassle. :good:
pictures partition?
Hi!
This guide really helped my to identify some partitions, but some questions came to my mind. I hope you can help me.
Do you have any idea where are the photos saved by default in the Galaxy S3 (i9300)?
I'm trying to recover my girlfriend's photos that I accidentally deleted
Thanks a lot!:victory:
supermaton said:
Hi!
This guide really helped my to identify some partitions, but some questions came to my mind. I hope you can help me.
Do you have any idea where are the photos saved by default in the Galaxy S3 (i9300)?
I'm trying to recover my girlfriend's photos that I accidentally deleted
Thanks a lot!:victory:
Click to expand...
Click to collapse
They are in data partition, where the sdcard is.
scandiun said:
They are in data partition, where the sdcard is.
Click to expand...
Click to collapse
Thanks a lot.
So I mount the partition and I'm able to see a lot of files but none of them are photos taken with the camera.
As soon as I noticed that the photos were gone I rooted the phone, installed CM10.1, then installed CM9, then I started to pull out the partitions,I know this may affect the data and some photos may not be recovered, but I was hoping to recover at least some of them.
--My mmcblkop12 partition (userdata) is about 11.5gb, is it possible that I did something wrong when pulling the .raw of the partition file out of the phone?
Should I pull out the raw file again from the phone?
Should I try another recovery software?
Thanks in advance
supermaton said:
Thanks a lot.
So I mount the partition and I'm able to see a lot of files but none of them are photos taken with the camera.
As soon as I noticed that the photos were gone I rooted the phone, installed CM10.1, then installed CM9, then I started to pull out the partitions,I know this may affect the data and some photos may not be recovered, but I was hoping to recover at least some of them.
--My mmcblkop12 partition (userdata) is about 11.5gb, is it possible that I did something wrong when pulling the .raw of the partition file out of the phone?
Should I pull out the raw file again from the phone?
Should I try another recovery software?
Thanks in advance
Click to expand...
Click to collapse
On Nexus devices the internal sdcard is just a folder inside userdata, so if you formatted userdata is probably that they got affected.
Try here
http://forum.xda-developers.com/showthread.php?t=1994705
scandiun said:
On Nexus devices the internal sdcard is just a folder inside userdata, so if you formatted userdata is probably that they got affected.
Try here
http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
Yep, that's the guide I'm following, the problem is that I can't find a single photo taken with the camera .. just old images of apps installed or cache files
scandiun said:
List of devices by name:
Code:
su
ls -l/dev/block/platform/omap/omap_hsmmc.0/by-name/
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
Code:
su
find /dev/block/platform/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_gnex_partitions.txt
Click to expand...
Click to collapse
Hi,
I tried this command but get an error. "Permission denied"
I have SU & busybox installed. Running PSX custom rom.
How can I fix it.
Hello all,
I have an s4 mini 8 GB, and it seems a lot of free space is unusable:
Code:
[email protected]:/data/data/berserker.android.apps.sshdroid/home # df
Filesystem Size Used Free Blksize
/dev 673.6M 48K 673.5M 4096
/storage 673.6M 0K 673.6M 4096
/storage/emulated 673.6M 0K 673.6M 4096
/storage/sdcard1 14.5G 7.3M 14.5G 32768
/mnt/secure 673.6M 0K 673.6M 4096
/mnt/asec 673.6M 0K 673.6M 4096
/mnt/obb 673.6M 0K 673.6M 4096
/mnt/fuse 673.6M 0K 673.6M 4096
/persdata/absolute 11.8M 4.1M 7.8M 4096
/system 1.4G 435.9M 1G 4096
/data 5.2G 4.1G 1.1G 4096
/cache 197M 87.1M 109.9M 4096
/persist 7.9M 4M 3.8M 4096
/efs 13.4M 4.2M 9.3M 4096
/firmware 64M 47.8M 16.1M 16384
/mnt/shell/emulated 5.2G 4.1G 1.1G 4096
/storage/emulated/0 5.2G 4.1G 1.1G 4096
/storage/emulated/0/Android/obb 5.2G 4.1G 1.1G 4096
/storage/emulated/legacy 5.2G 4.1G 1.1G 4096
/storage/emulated/legacy/Android/obb 5.2G 4.1G 1.1G 4096
[email protected]:/data/data/berserker.android.apps.sshdroid/home # uname -a
Linux localhost 3.4.0-cyanogenmod-g7ce908f #1 SMP PREEMPT Mon Sep 23 19:38:58 PDT 2013 armv7l GNU/Linux
Is there any way to shrink the /system partition and make /data larger?
I am aware that there are tools like link2sd (and I used them in the past) but this is not what I want.
Any comments welcome.
Regards,
George
papalexo said:
Hello all,
Is there any way to shrink the /system partition and make /data larger?
Any comments welcome.
Regards,
George
Click to expand...
Click to collapse
To repartition the emmc chip you need a pit file. But i strongly recommend against that procedure. There is a chance that ur device hard bricks.
And moreover no one has ever tried that on our device.
Instead u can root ur device and use xposed + obbonsd module. It will help with moving big apps and games to sd card.
Use a class 10 sd card. good luvk
Hi sasank360,
sasank360 said:
Instead u can root ur device and use xposed + obbonsd module. It will help with moving big apps and games to sd card.
Click to expand...
Click to collapse
yes, but this is not what I want.... link2sd can do the same thing...
I think no one has tried that hack, it's just too risky
Don't like link2sd try Folder mount
sasank360 said:
To repartition the emmc chip you need a pit file. But i strongly recommend against that procedure. There is a chance that ur device hard bricks.
And moreover no one has ever tried that on our device.
Click to expand...
Click to collapse
I did.
You don't need to change PIT. GPT is sufficient in most cases as ROMs and recoveries use GPT.
system & data partitions are quite at the end of the emmc, so you can resize them w/o having to interfere with eg boot or recovery partitions. Their PIT references would still be vaiid should you need to re flash those in download mode.
Instead of repartitioning you could just use an external sdcard as /data. This just requires modification of ramdisk.
Anyway you should understand what you are doing before trying any of this..