I used Amon-Ra's recovery to create a 1 GB ext3 partition on my SD card.
When I look at the card in a UNIX like OS the partition is there.
Ideally, I'd like to have partition's file system mount & unmount at /sd-ext
or /mnt/sd-ext programaticly. I've been trying to figure out what its /dev name is.
ADB's shell says partition 1 is /dev/block/vold/179:9 mounted on /mnt/sdcard.
There are 12 /dev/block/vold/179:?? (0-11) how do I find out which is
associated with partition 2?
Or is there another way to reach it? Is there a root app to mount / unmount
a file system? Do I need to use ADB or a local shell?
mouting and using tune2fs -l /dev/block/mmcblk0p2
tune2fs -l /dev/block/mmcblk0p2
you can use tune2fs -l and the block name to get the nitty gritty details of the partition or disk.
you can use df and or mount commands to get the details of your system
you can also cd into /dev/block/ and use ls to see all the files in there: below is my output with is use ls in /dev/block/
[email protected]_targa:/dev/block# ls
ls
dm-0
vold
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
mmcblk1p27
emstorage
mmcblk1p26
userdata
mmcblk1p25
webtop
mmcblk1p24
preinstall
mmcblk1p23
cache
mmcblk1p22
system
mmcblk1p21
kpanic
mmcblk1p20
cid
mmcblk1p19
misc
mmcblk1p18
cdrom
mmcblk1p17
recovery
mmcblk1p16
boot
mmcblk1p15
mmcblk1p14
mmcblk1p13
mmcblk1p12
mmcblk1p11
mmcblk1p10
mmcblk1p9
mmcblk1p8
pds
mmcblk1p7
mmcblk1p6
mmcblk1p5
mmcblk1p4
mmcblk1p3
mmcblk1p2
mmcblk1p1
mmcblk1
mmcblk0p3
mmcblk0p2
mmcblk0p1
platform
mmcblk0
[email protected]_targa:/dev/block#
mmcblk0... is my external sd card, it has 3 partitions, mmcblk0p1 is the one recognized and mounted by android, mmcblk0p2 is the ext3fs, and mmcblk0p3 is a linuxswap file
This should mount the ext3 partition to /data/sd-ext. You will need to create the sd-ect folder before running the command in the terminal.
mount -t ext3 -o rw /dev/block/vold/179:10 /data/sd-ext
cmlusco said:
This should mount the ext3 partition to /data/sd-ext. You will need to create the sd-ect folder before running the command in the terminal.
mount -t ext3 -o rw /dev/block/vold/179:10 /data/sd-ext
Click to expand...
Click to collapse
and than how to use it with vold to mount to PC via USB?
purportex said:
and than how to use it with vold to mount to PC via USB?
Click to expand...
Click to collapse
I dont believe that is possible, at least as far as i know. It would probably require a modified ramdisk which is over my head, i wouldnt know where to begin.
So, where to start...
I rooted my Samsung Note II, and installed Frosty Jellybean. I was really hoping for the longpress back -> app kill like on cyanogen mod, and started switching roms, till I came across Omega. Not realizing how incompatible it was, I flashed anyway and lost radio. I immediately Odin'd back to stock and got radio back (efs / iemi fine). Then moved on to MyRom. Loved it, it was great, but then noticed duplications on my internal sd card....
the whole /0/ dir for 4.1.2, which at the time I thought was an error on my part from modding.... this is where I take a series of stupid moves
1) formatted the internal sd card with cwm.
2) reflashed odin using the pit file from SGH-t889V from this thread
This significantly hosed my phone, so I spent the weekend trying to understand how I could fix it without paying the warrenty deductible. I did a nandriod restore to a point right before I started modding, and finally got 4.1.1 to come up and not endlessly bootcycle. However, my internal SD card isn't mounting correctly (really at all), and I couldn't figure out how to use the fuse thing to get the vfat partition back and pointed to the right point in /dev/block/mmcblk3p?
So, I've triangled-away, now its a stock piece that
1) has no bluetooth
2) has no radio
3) will not come up as a usb device - the usb doesn't even see its there
-- UNLESS its in download mode, then comes up as a serial device
This leads me to believe that all the instancing scripts / settings that are supposed to run when the device powers on aren't coming up, though the init.d and fstab thingie look right(ish)
So, is this a lost cause - should I just make my claim, or is there some easy Heres-a-raw-dump-of-the-phone thing I have missed, that could get me back up and running?
Thanks,
** UPDATE **
I ran the firmware update through KIES and resolved this.,
So you have tried restoring the stock image?
Carbon 1.5 | Kroz Hue Brown Theme | Crack Flasher
odin restore
RonnieRuff said:
So you have tried restoring the stock image?
Carbon 1.5 | Kroz Hue Brown Theme | Crack Flasher
Click to expand...
Click to collapse
if I flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user_low_ship.tar.md5
it gets caught in a bootloop, I have to flash cwm to do a nandriod restore to before I started modding. that's where its at now.
fireupFront said:
if I flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user_low_ship.tar.md5
it gets caught in a bootloop, I have to flash cwm to do a nandriod restore to before I started modding. that's where its at now.
Click to expand...
Click to collapse
Try flashing that rom and then going into recovery mode [stock] and factory resetting before you boot into Android
Sent from my SGH-T889 using xda premium
ktetreault14 said:
Try flashing that rom and then going into recovery mode [stock] and factory resetting before you boot into Android
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Tried that as well...
if you went from a 4.2.x rom back to a 4.1.x rom u might need to flash the "restore sdcard after downgrade.zip" script. its a mandatory step
from reading your post it doesn't seem you have tried flashing that yet.
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
restore sdcard after downgrade.zip link
look at the very bottom of the post under ATTACHED FILES
script
rlee008 said:
if you went from a 4.2.x rom back to a 4.1.x rom u might need to flash the "restore sdcard after downgrade.zip" script. its a mandatory step
from reading your post it doesn't seem you have tried flashing that yet.
---------- Post added at 08:24 PM ---------- Previous post was at 08:16 PM ----------
restore sdcard after downgrade.zip link
look at the very bottom of the post under ATTACHED FILES
Click to expand...
Click to collapse
You're right, I should have run that script then, but now... not so helpful:
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/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/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:17 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/dev/block #
>> no ramdisk <<
wifi
Keep in mind, I can't actually get to the device via usb, the only way I've even been able to adb to the device is wirelessly over wifi...
fireupFront said:
Keep in mind, I can't actually get to the device via usb, the only way I've even been able to adb to the device is wirelessly over wifi...
Click to expand...
Click to collapse
can you mount via recovery?
you said you were able to nandroid back to 4.1.1, but your internal sdcard wasn't mounting correctly ... try flashing the restore-sdcard. zip first, then nandroid back to your working 4.1.1 then flash the restore-sdcard.zip again and boot...
script
rlee008 said:
can you mount via recovery?
you said you were able to nandroid back to 4.1.1, but your internal sdcard wasn't mounting correctly ... try flashing the restore-sdcard. zip first, then nandroid back to your working 4.1.1 then flash the restore-sdcard.zip again and boot...
Click to expand...
Click to collapse
THe script can't run, /data/media is not writeable
I was able to get parted on the device and got this info:
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
the closest thing to this I've found on the web is here:
Model: MMC MAG4FB (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 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1774MB 1342MB ext4 CACHE
13 1774MB 3653MB 1879MB ext4 SYSTEM
14 3653MB 3674MB 21.0MB ext4 HIDDEN
15 3674MB 3683MB 8389kB OTA
16 3683MB 15.8GB 12.1GB ext4 USERDATA
so it looks like my tombstones are messed up, which makes these logcat msgs make sense
Error kickstart 2029 Requested ID 16, file "/tombstones/qcks/efs1.bin"
39:35.2 Error kickstart 2029 ERROR: function: open_file:80 Unable to open input file /tombstones/
So I re partition ed the tombstone drive and got the vfat back up, but still no radio or bluetooth
Sent from my SGH-T889 using xda app-developers app
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..