[q] wildfire rom size - Wildfire Q&A, Help & Troubleshooting

After doing an MTD Partition of 180 20, I found out I am having just 265MB left on me Wildy (i.e 465MB total space). Is this correct or should I have more?
Thank you.

I think thats okay. Total size and available size are two different things like if you see a hard drive lets say 80gb.. This 80gb is the total space but the available space should b around 76gb..
Sent from my HTC Wildfire using XDA

This is a df -h in a fresh CM 7.2
Filesystem Size Used Available Use% Mounted on
tmpfs 156.3M 32.0K 156.2M 0% /dev
tmpfs 156.3M 0 156.3M 0% /mnt/asec
tmpfs 156.3M 0 156.3M 0% /mnt/obb
/dev/block/mtdblock3 250.0M 116.5M 133.5M 47% /system
/dev/block/mtdblock5 175.1M 38.5M 136.7M 22% /data
/dev/block/mtdblock4 40.0M 1.2M 38.8M 3% /cache
/dev/block/mtdblock5 175.1M 38.5M 136.7M 22% /cache/download
/dev/block/vold/179:1 3.7G 557.1M 3.2G 15% /mnt/sdcard
/dev/block/vold/179:1 3.7G 557.1M 3.2G 15% /mnt/secure/asec
And after apply mtd 150 40
Filesystem Size Used Available Use% Mounted on
tmpfs 156.3M 32.0K 156.2M 0% /dev
tmpfs 156.3M 0 156.3M 0% /mnt/asec
tmpfs 156.3M 0 156.3M 0% /mnt/obb
/dev/block/mtdblock3 150.0M 116.7M 33.3M 78% /system
/dev/block/mtdblock5 275.1M 149.5M 125.6M 54% /data
/dev/block/mtdblock4 40.0M 1.2M 38.8M 3% /cache
/dev/block/mtdblock5 275.1M 149.5M 125.6M 54% /cache/download
/dev/block/vold/179:1 3.7G 1.5G 2.3G 39% /mnt/sdcard
As you can see in both configs 250+171.1+40 = 150+275.1+40=465,1 MB

Related

[Q] apps2sd - not working... ?

hi,
i am not sure what i am doing wrong here, I am using pinky's ROM and I have the default and used ROM manager to partition the SD card to a 512 MB ext3 and the remainder 14 GB as FAT32.
I have set the EXT4 module is enabled and App2SD is set to external.
But I still cant get the apps to install to SD, using the method above to check it. The Ext3 partition is being seen, but the symlinks are correct.
Any ideas?
Heres a dump from my CMD prompt
C:\android\tools>adb shell
sh-3.2# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.6M 0 207.6M 0% /dev
tmpfs 207.6M 0 207.6M 0% /mnt/asec
/dev/block/mtdblock3 250.0M 181.6M 68.4M 73% /system
/dev/block/mtdblock5 147.6M 12.0M 135.6M 8% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mtdblock5 147.6M 12.0M 135.6M 8% /system/mnt/data
/dev/block/mmcblk0p2 457.4M 70.1M 362.9M 16% /system/sd
/dev/block/vold/179:1
14.6G 158.4M 14.5G 1% /mnt/sdcard
/dev/block/vold/179:1
14.6G 158.4M 14.5G 1% /mnt/secure/asec
sh-3.2# cd /data/app
cd /data/app
sh-3.2# pwd
pwd
/data/app
help anyone???
The native apps2sd option has nothing to do with apps2sd+, set it to internal. To see if apps2sd+ is working proply use a file explorer to navigate to the /data/app directory and look at the availible space, if its the same as your ext partition. Its working
Sent from my HTC Desire using Tapatalk

[Q] Not enough space left in data with this table

I have some trouble with my newly installed ROM (RCMixHD)
Filesystem Size Used Available Use% Mounted on
tmpfs 206.5M 0 206.5M 0% /dev
/dev/block/mtdblock4 40.0M 1.4M 38.6M 3% /cache
/dev/block/mtdblock3 250.0M 125.9M 124.1M 50% /system
/dev/block/mtdblock5 147.6M 147.4M 188.0K 100% /data
/dev/block/mmcblk0p1 3.2G 232.9M 2.9G 7% /sdcard
/dev/block/mmcblk0p2 458.5M 181.9M 252.1M 42% /sd-ext
Obviously I can't seem to boot up because it can't load the system data in the dalvik-cache, so I just thought I could clear up the dalvik-cache and give it a reboot, now I'm like this but still it doesn't seem to boot up:
Filesystem 1K-blocks Used Available Use% Mounted
tmpfs 211420 0 211420 0% /dev
/dev/block/mtdblock4 40960 1428 39532 3% /cache
/dev/block/mtdblock3 256000 128924 127076 50% /system
/dev/block/mtdblock5 151168 70296 80872 47% /data
/dev/block/mmcblk0p1 3310900 238440 3072460 7% /sdcard
/dev/block/mmcblk0p2 469475 186257 258172 42% /sd-ext
Did I miss something? Or maybe I was just unpatient?
looks like after all it wasn't a good idea... do I really need to flash back up the rom from scratch and not sync contacts and anything like that?
c:\android-sdk-windows\platform-tools>adb shell logcat
--------- beginning of /dev/log/main
I//system/xbin/busybox( 64): run-parts: applet not found
I/logwrapper( 64): /system/xbin/busybox terminated by exit(1)
after all it looks like a bug in the contacts list...

[Q] mount, sdcard1 on cyanogenmond 10.1

Hi, I'm new on Andoird and I use a nighlty Cyanogenmod 10.1
I want to have my microsd mounted to be used for DCIM, Download and so on (looks to be /storage/emulated/0 or /storage/emulated/legacy : they looked to be the same...).
I try to do it with a "mont -o bond /storage/sdcard1 /storage/emulated/0". It was working but no way to keep it permanent after a reboot (I try to use a script in init which wasn't working and I find that dirty). I try a symlink which freezed cyanogenmod during the boot.
I find the vold.fstab but no doc to enter properly the parameters for a bind mount.
My few questions if you can help me are:
- is there a good doc like the man/info on linux for the configuration files like vold.fstab and about all the mounted volumes?
- how to get my storage1 be mount properly in the configurations files?
- what is fuse used for and where is it called to do the mounts?
Thank you for your help.
Here is a copy/paste of a mount and a df
Code:
# mount
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:49 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
/dev/block/mmcblk0p13 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
# df
Filesystem Size Used Free Blksize
/dev 903.6M 52K 903.6M 4096
/storage 903.6M 0K 903.6M 4096
/storage/emulated 903.6M 0K 903.6M 4096
/storage/sdcard1 29.7G 12.1G 17.6G 16384
/mnt/secure 903.6M 0K 903.6M 4096
/mnt/asec 903.6M 0K 903.6M 4096
/mnt/obb 903.6M 0K 903.6M 4096
/system 2G 388.4M 1.6G 4096
/efs 19.7M 9.4M 10.3M 4096
/cache 1.3G 23.7M 1.3G 4096
/data 10.5G 7.6G 2.8G 4096
/mnt/shell/emulated 10.5G 7.6G 2.8G 4096
/storage/emulated/0 10.5G 7.6G 2.8G 4096
/storage/emulated/0/Android/obb 10.5G 7.6G 2.8G 4096
/storage/emulated/legacy 10.5G 7.6G 2.8G 4096
/storage/emulated/legacy/Android/obb 10.5G 7.6G 2.8G 4096

[Q] formating encrypted internal sd ccard

The phone is stuckk in the bootloop. Try falshig the stock rom , with heimdall, odin, but cannot make the phone work :
after encryption the SD card has :
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 925220 48 925172 0% /dev
tmpfs 925220 0 925220 0% /storage
tmpfs 925220 0 925220 0% /mnt/secure
tmpfs 925220 0 925220 0% /mnt/fuse
I am not sure how to format this and reload with new parition.. and where can I get the partition for N7100 international. and steps to create the partition.
parted /dev/block/mmcblk0 does not execute as the mem blk is not found
Please help

adb push through TWRP sideload saying I'm out of space

I couldn't get TWRP to discover my OTG device, so I tried to sideload my custom ROM. I couldn't get that to work either. So then I attempted to push Magisk and ROM zip files onto the device. I was able to successfully push Magisk onto my Pixel 3XL, but when I tried to push the ROM, it told me I was out of space. Any idea how I can push to my /dev/block/dm-4 which has 109GB of free space?
C:\Users\Admin\Desktop\Pixel 3XL - 2022-02-27\platform-tools>adb shell df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.5G 79M 1.5G 5% /
tmpfs 1.7G 896K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
tmpfs 1.7G 0 1.7G 0% /apex
tmpfs 1.7G 4.0K 1.7G 1% /linkerconfig
tmpfs 1.7G 41M 1.6G 3% /tmp
/dev/block/loop0 232K 88K 144K 38% /apex/com.android.cts.shim
/dev/block/loop1 18M 18M 28K 100% /apex/com.google.android.media.swcodec
/dev/block/sda20 11M 172K 11M 2% /metadata
/dev/block/dm-4 111G 2.6G 109G 3% /data
C:\Users\Admin\Desktop\Pixel 3XL - 2022-02-27\platform-tools>adb push Magisk-v24 .2.zip /sdcard
Magisk-v24.2.zip: 1 file pushed, 0 ski.... 29.5 MB/s (10871119 bytes in 0.352s)
C:\Users\Admin\Desktop\Pixel 3XL - 2022-02-27\platform-tools>adb push PixelExperience_crosshatch-12.0-20220222-0057-OFFICIAL.zip /sdcard
adb: error: failed to copy 'PixelExperience_crosshatch-12.0-20220222-0057-OFFICIAL.zip' to '/sdcard/PixelExperience_crosshatch-12.0-20220222-0057-OFFICIAL.zip':
remote write failed: No space left on device
PixelExperience_crosshatch-12.0-202202...6.0 MB/s (1656509726 bytes in 60.845s)

Categories

Resources