Hello all,
I'm afraid I've just done a STUPID THING (TM) with my phone. In adb shell (root) I wanted to reformat the second partition of the *external* sd card, and I typed mmcblk0p2 instead of mmcblk1p2. I'm not sure I have broken anything, because fdisk does not show any mmcblk0p2 partition (see below), but the mkfs command somehow succeded:
Code:
# mkfs.ext2 /dev/block/mmcblk0p2
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
128 inodes, 1024 blocks
51 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
1 block groups
8192 blocks per group, 8192 fragments per group
128 inodes per group
and here is fdisk output:
Code:
# fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
256 heads, 63 sectors/track, 473 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 266306 2147483647+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(266305, 4, 4)
and the output of the mount command:
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=469568k,nr_inodes=117392,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,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,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=469568k,nr_inodes=117392,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=469568k,nr_inodes=117392,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/lysesoft.andsmb-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=469568k,nr_inodes=117392,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/vold/179:66 /data/sdext2 ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=469568k,nr_inodes=117392,mode=050,gid=1028 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/block/vold/179:65 /mnt/media_rw/external_SD vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/external_SD 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
/dev/block/vold/179:65 /data/media/0/WhatsApp vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Now the phone is still powered on, working ok, and connected with adb shell. I'm not rebooting it until I have some confidence I've not wiped essential system stuff. The phone has the LG stock ROM. Have I wiped any system partition? Will the phone boot again?
Since there is no partition by that name, you have not done any damage to your phone
Plus as it is your external SD card, nothing will happen to the ROM on your phone, as all of that is on the Device Memory!
Cheer up mate, all's well!:thumbup:
Sent from my SM-G530H using XDA Free mobile app
I know I can't blame you, but, just to let you know, the phone is actually bricked. I turned it off after I read your reply, and it never resurrected. No power+volume down tricks. Nothing. Black screen.
Rest in peace.
Oh! I'm so sorry buddy. Your phone may still get back to life. Try a senior on XDA. He may help you.
I guess you don't have access to your recovery as well?
I still don't get it, how can your phone get bricked when you did stuff with the External SD card?
Sent from my SM-G530H using XDA Free mobile app
heinrich.himmler said:
Oh! I'm so sorry buddy. Your phone may still get back to life. Try a senior on XDA. He may help you.
I guess you don't have access to your recovery as well?
Click to expand...
Click to collapse
This story's had a happy ending. Last month I brought my phone back to the lab (the warranty period isn't over yet) and I told them that one day it suddendly died with no reason. I know, Beelzebub has a devil put aside for me...
They phone was so bricked they didn't even dare to check why. They simply replaced the system board and handed me it back fixed after a few days, for free.
heinrich.himmler said:
I still don't get it, how can your phone get bricked when you did stuff with the External SD card?
Click to expand...
Click to collapse
Please note that /dev/block/mmcblk0 is not the external SD. I should have typed /dev/block/mmcblk1 for the external SD, see my first post.
Related
I have no idea if this belongs here, so feel free to move this thread.
I have a Qualcomm MDP MSM8660, which, frankly, I am way too much of a noob to use. I, with the help of someone, finally managed to install gapps and am able to use the market. The problem is, the Market claims that there is no room to install apps, even though the phone says that there is 888MB free. So I presume that the market sees some other partition which is full. If this is the case, how can I make it see the other partition, or alternatively expand the partition. I don't even know how to view the partitions to see if the above theory is correct.
EDIT: I checked using Android System Information, and the Data partition is nearly a Gigabyte. So any suggestions on why the Market thinks that there is no room. When I used ADB to push the gapps to /system there also wasn't any room, so I had to clear some apps. But I believe that's a different partition.
Any ideas?
Thanks
To view the partitions on your device you should run mount through adb shell. Post the output here.
Here it is:
>adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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/mmcblk0p12 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.estrongs.android.pop-1 vfat ro,dirsync,nosuid,node
v,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,utf8,errors=remount-ro 0 0
EDIT: Not really related, but I even though this is supposed to be rooted, and through ADB it does seem so , after remount, Superuser says it's not and in Terminal it shows "$" and when I type "su" it says uid 10006 not allowed to su". Any ideas?
Does anyone have any ideas? Also how to symlinks?
Thanks.
Hi,
I have very limited space on the system partition, so I can't install any apps larger than 2MB. I do have plenty of room on the data partition, so if I download the APK myself, I can install it. It appears that the Market uses the system partition as a download cache, until it installs the app. Therefore, I can install several apps summing up more than 2MB, however not a single app bigger than 2MB.
My question is, how to grow the system partition to use the space in the data partition.
Here is the output of adb mount:
>adb shell mount rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,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/mmcblk0p12 /system ext4 ro,relatime,barrier=1,data=ordered 0 0 /dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered ,noauto_da_alloc 0 0 /dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde red 0 0 /dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere d 0 0 /dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o rdered 0 0 /dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0 /dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime, uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharse t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow _utime=0020,codepage=cp437,ioc harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/block/dm-0 /mnt/asec/com.estrongs.android.pop-1 vfat ro,dirsync,nosuid,node v,relatime,uid=1000,fmask=0222,dmask=0222,codepage =cp437,iocharset=iso8859-1,sho rtname=mixed,utf8,errors=remount-ro 0 0
There is a limit, but I never heard of one being so low. Have you checked to see if there were any junk files there (/cache/download)?
None that I see. There is 48MB of. so files, though.
yelped said:
None that I see. There is 48MB of. so files, though.
Click to expand...
Click to collapse
Are you sure you are in the right folder? Those files should not be there.
Those files are there. Should I provide you with a list of all the files. If so, what's the easiest way?
Thanks!
I would suggest making a nandroid backup, then deleting all the files in that folder (make sure you're the right one). It should not affect your system since that folder is usually safe to delete files from, but ".so" files are driver files, so it would be safer to make the backup (just in case).
Nothing on the device would work if I did that. I tried to remove it already. Do you have any other suggestions?
Thanks!
Hello, i have a new tablet from Arnova (little brother of Archos)
Spec of the tablet
1.4 ghz msm 8255 processor
512 ram
ICS operating system
What is the case, i managed to root the tablet, and dump the system partition, but romdump is not able to dump the boot and recovery, so i asked myself why
These are some results
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
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/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,d
ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,
data=ordered 0 0
/dev/block/mmcblk0p17 /content ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:97 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 194M 48K 194M 4096
/mnt/asec 194M 0K 194M 4096
/mnt/obb 194M 0K 194M 4096
/system 295M 223M 71M 4096
/data 393M 73M 320M 4096
/persist 4M 1M 3M 1024
/cache 196M 4M 192M 4096
/content 17M 13M 3M 4096
/mnt/sdcard 2G 1M 2G 4096
/mnt/secure/asec 2G 1M 2G 4096
/mnt/external_sd 3G 2G 1G 32768
[email protected]:/ # ls /dev/block/mmcblk*
ls /dev/block/mmcblk*
/dev/block/mmcblk0
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p1
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12
/dev/block/mmcblk0p13
/dev/block/mmcblk0p14
/dev/block/mmcblk0p15
/dev/block/mmcblk0p16
/dev/block/mmcblk0p17
/dev/block/mmcblk0p18
/dev/block/mmcblk0p19
/dev/block/mmcblk0p2
/dev/block/mmcblk0p20
/dev/block/mmcblk0p3
/dev/block/mmcblk0p4
/dev/block/mmcblk0p5
/dev/block/mmcblk0p6
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8
/dev/block/mmcblk0p9
/dev/block/mmcblk1
/dev/block/mmcblk1p1
[email protected]:/ # cat proc/mtd
cat proc/mtd
dev: size erasesize name
I am asking for some help.
How can i dump the boot and recovery ?
It is posibile considering the fact that there is no mtd ?
I am not an expert in this, so if i got something wrong show me what i dit.
Thx for any help.
Bump
Hmmm....
Code:
cat /proc/mtd
should give you the infos you need (I can't see which MTD is the recovery). Else you may want to provide me the system image?
There is no MTD on the 7c g3 only on the 7c g2 is a mtd, on the 7c g3 it is emcc which is used also on the htc phones and samsung phones.
This is the 7C G2
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock1 on /system type yaffs2 (rw,relatime)
/dev/block/mtdblock4 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock5 on /persist type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock7 on /content type yaffs2 (rw,nosuid,nodev,relatime
And this one is the 7C G3
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
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/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,d
ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,
data=ordered 0 0
/dev/block/mmcblk0p17 /content ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow _utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:97 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow _utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I forgot to say that the 7C G3 has also a 4gb Internal space which is showd in the first post (how is partitioned)
This is the boot image that i have just dumped using the command :
[email protected]:/ # dd if=/dev/block/mmcblk0p8 of=/sdcard/bootmmc8.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/bootmmc8.img bs=4096
2560+0 records in
2560+0 records out
10485760 bytes transferred in 0.461 secs (22745683 bytes/sec)
this was the block where i found this image
http://depositfiles.com/files/qd34j4fkl
Now i am not sure if i can flash this image without breaking the tablet, and i can not find the recovery.
basicaly those mmc blocks are similar with the mtd blocks
I see. I have such device, too. Though I never did anything around hacking it, I'll see if I can find some usefull infos and write back then.
i just tried the boot.img and it works
now i just need to find the recovery partition, it must be one from this 22 mmc blocks
i will upload the system.tar dump, maybe you can make a system.img (i don`t know how) for backup to stock rom
Done, found also the recovery it was in the block16, i can see a link, boot in block8 and recovery in block16 ,system in block12
i will try to learn now about creating a cwm
http://www.mediafire.com/?rn9uppve8569ffn
system image
had problems finding my boot and recovery blocks on my device and ran into this thread and someone mentioned that there's no mtd but emmc so i tried cat proc/emmc and boom! that got me what i needed
Hi.. I need to run a script AFTER the sdcard is mounted. However, it seems that my script is always run before or when the sdcard is not mounted yet. My phone is rooted already.
This is my script, located at /etc/init.d/myscript.sh
Code:
#!system/bin/sh
#this is to show that my script is run properly as root.
chmod 777 /cache
mkdir /cache/foo
### and it runs without any problem. So far so good.
#now I want to check if there is file "foo.img" at my external sd card "/storage/0764-8617"
#of course, there IS the file at /storage/0764-8617
#i tried all "wait", "loop" below to make sure sdcard is loaded before the "if" block below..
wait /dev/block/loop1
count=10
until [ -d /storage/0764-8617 ] || [ $count -lt 1 ];
do
sleep 1
count=$((count-1));
done;
sleep 10
if [ -f /storage/0764-8617/foo.img ] ; then
echo "File existed
else
echo "File not found"
fi
#but it always spits out that "File not found!"
How should I fix this code so that the script can always find /storage/0764-8617/foo.img
this is what mounted in my phone:
cat /proc/mounts
rootfs / rootfs rw,seclabel 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
proc /proc proc rw,relatime 0 0
tmpfs /proc/cmdline tmpfs rw,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/public:179,129 /mnt/media_rw/0764-8617 vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/public:179,129 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /mnt/runtime/default/0764-8617 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/0764-8617 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/0764-8617 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.UCMobile.intl-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
/[email protected] /system ext4 ro,seclabel,relatime,data=ordered 0 0
/[email protected] /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop101 /cache/QQdata ext4 rw,seclabel,relatime,data=ordered 0 0
/[email protected] /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered 0 0
/[email protected] /data/sdext2 ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /cust ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_lg /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /mpt ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/0764-8617 fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/loop1 /su ext4 rw,seclabel,noatime,data=ordered 0 0
p/s: I have found a way quite simple, but crazy solution to my problem by directly check and wait for the file and IT WORKS.
Code:
until [ [COLOR="Red"]-f /storage/0764-8617/foo.img[/COLOR]] || [ $count -lt 1 ];
but my question is still open: I link some app from foo.img, (that is mounted to /dev/block/loop1), to /data/app but it is not shown in the app drawer, even after reboot. However if I put the image in internal storage, then the app can be shown.
Hello,
i have wd disks that dont support apm so i need sleep them manually, in ubuntu this works fine, every commands works, disks goes sleep without problem.
in android (lolipop 5.1) display
Code:
hdparm: ioctl 0x304 failed: Invalid argument
hdparm: HDIO_GET_IDENTITY: Invalid argument
Is there any possibility to workaround this ? I was trying even hd-idle, but without success...
Code:
mount
rootfs / rootfs rw 0 0
/dev/root / ext4 ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,seclabel,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:50 /data/sdext2 ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:1 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/8:1 /mnt/media_rw/usbdisk vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/8:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/8:1 /mnt/media_rw/sdcard0/.android_secure vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/usbdisk fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:49 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:49 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:49 /mnt/media_rw/sdcard0/.android_secure vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:49 /mnt/media_rw/usbdisk/.android_secure vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
fdisk -l /dev/block/sda
Disk /dev/block/sda: 160.0 GB, 160041885696 bytes
256 heads, 63 sectors/track, 19381 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/sda1 * 1 19382 156289880 c Win95 FAT32 (LBA)
I have the exact same issue