Related
Does this device have a boot.img file that is accessible and editable?
I have the following details from the system files:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 1931264 mmcblk1
179 9 1930240 mmcblk1p1
# grep "mmcblk0" init.rc
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system check=no
mount rfs /dev/block/mmcblk0p13 /system ro remount
mount rfs /dev/block/mmcblk0p10 /efs nosuid nodev check=no
# mount rfs /dev/block/mmcblk0p16 /data nosuid nodev check=no
mount rfs /dev/block/mmcblk0p16 /data nosuid nodev crypt check=no
mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev crypt check=no
#mount rfs /dev/block/mmcblk0p14 /dbdata nosuid nodev check=no
mount rfs /dev/block/mmcblk0p15 /cache nosuid nodev check=no
mount j4fs /dev/block/mmcblk0p9 /mnt/.lfs
# cat /proc/mounts
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/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
no mtd in /proc
I also found that there is no /proc/mtd which makes it hard to figure out which mount points are the boot and recovery images.
Code:
# ls /proc/
param
rfs
last_kmsg
batt_info_proc
uid_stat
pvr
apm
sysrq-trigger
partitions
diskstats
crypto
kpageflags
kpagecount
kmsg
softirqs
version
uptime
stat
meminfo
loadavg
interrupts
devices
cpuinfo
cmdline
locks
filesystems
vmallocinfo
zoneinfo
vmstat
pagetypeinfo
buddyinfo
kallsyms
modules
timer_list
iomem
ioports
execdomains
sched_debug
cpu
asound
scsi
misc
fb
wakelocks
irq
cgroups
sys
bus
tty
driver
fs
sysvipc
net
mounts
self
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
37
38
39
40
41
42
49
51
52
53
54
55
56
57
58
59
60
61
62
64
67
68
69
71
72
73
74
75
76
77
78
79
80
84
86
87
91
93
100
120
199
207
212
213
217
234
276
309
419
557
566
574
695
995
1391
1409
2159
5135
5769
8293
8301
9704
10957
10959
10973
14462
14493
21343
32673
YP-G70 - 3 boot logos... wtf?
I successfully flashed the boot logo and replaced the animated boot logo but there is still a samsung boot logo showing up on this device.
When I boot I see my custom boot logo which is written to param.lfs after modifying the name of the original logo.jpg to l0g0.jpg and reflashing via odin. Heimdell won't successfully flash this device although it can extract the pit file without problems.
The custom logo in /mnt/.lfs displays for about 2 seconds then I see the original "samsung" logo for about 5 seconds then I see the custom boot animation.
I replaced the boot animation like this:
# cd /system/bin
# mv samsungani samsungloopani
# mv bootanimation samsungani
# reboot
I added my own custom boot animation "sanim.zip" to /system/media which plays just fine. Samsung have renamed bootanimation.zip to sanim.zip for no apparent reason.
I can't find any info anywhere about this mysterious third logo that shows up between the boot logo and the boot animation.
I found a logo file in /sbin/ called fota.png but it seems that it is not possible or at least undocumented on how to retrieve and edit the samsung "boot.img" to replace /sbin/fota.png with my own logo. Even if I did that I am not certain that it would solve the problem.
no one has any hints?
Turns out the "zImage" partition is located on /dev/block/mmcblk0p12
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/zImage
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/factoryfs.rfs
dd if=/dev/block/mmcblk0p9 of=/mnt/sdcard/param.lfs
hi i like ur thread
so can i change the
GT-S7500 Logo before boot animation
Hey everyone,
I'm having trouble extracting a recovery.img from my phone. More specific I can't seem to find which file I have to 'dd' to create the img file.
Some commands with the output
Code:
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
Code:
[email protected]:/ # 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
/[email protected] /system ext4 ro,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:97 /mnt/sdcard 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
/dev/block/vold/179:97 /mnt/secure/asec 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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:6 /mnt/sdcard2 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
Code:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2621440 mmcblk0p5
179 6 85216 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15110144 mmcblk1
179 97 15106048 mmcblk1p1
Code:
[email protected]:/ # cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0000ac40 00002800 "sec_ro"
emmc_p3: 00010740 00100000 "android"
emmc_p4: 00110f40 00100000 "cache"
emmc_p5: 00211740 00500000 "usrdata"
emmc_p6: 00711f40 000299c0 "fat"
Even by running the commands above I'm still not able to determine where I can extract a recovery.img.
Ive been looking around and can't seem to find anything so I hope someone can point me in the right direction.
PS: Phone in question is a Star B92M (chinaphone)
Thanks for the help!
~Whookid
EDIT: I'm looking for a way to do this without SP Flash tool
Is your phone rooted? If so, you can create a backup by using a script made available by our fellow Russian users from forum.china-iphone.ru. Give it a shot... here.
I've just remembered that you can also use MTK Droid Root & Tools for that.
LG Optimus 2x (P990), Stock ROM, Android 2.3.4, rooted, ROM Manager and CWM Recovery installed.
My phone seemed to be getting rather slow so I decided to clear the cache and the Dalvik cache, from the recovery menu, to see if it would speed up the phone a little. Both processes completed without errors and I rebooted the phone.
The phone now works faster and is completely normal except for one thing. I find that I cannot now download any apps from Google Play as I get an error 498. If I look at a DF listing in a terminal there is no /cache listed. If I look at the results of 'mount' in the terminal I cannot see a cache partition either.
I have tried clearing the cache 3 times now with no success. I have also tried Cache Fixer but that gives errors if I try to move the cache 'Cache has NOT been moved'. I assume that may be because there isn't a cache partition now. I also tried restoring the cache using a partial restore from a nandroid backup which completed successfully but hasn't cured the problem - I still don't seem to have a cache.
EDIT: I've just had a look at the partition using fdisk and this is what I see:
Disk /dev/block/mmcblk0p2: 4 heads, 16 sectors, 2048 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 00 0 0 0 0 0 0 0 0 00
2 00 0 0 0 0 0 0 0 0 00
3 00 0 0 0 0 0 0 0 0 00
4 00 0 0 0 0 0 0 0 0 00
Doesn't look good!
FURTHER EDIT: That bit about fdisk above is wrong. I thought that I was looking at a device but it was a partition.
Using fdisk on the proper device I get:
Disk /dev/block/mmcblk0: 7996 MB, 7996440576 bytes
1 heads, 16 sectors/track, 976128 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 129 44928 358400 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 44929 53120 65536 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 53121 53376 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 53377 946432 7144448 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 53441 54464 8192 83 Linux
/dev/block/mmcblk0p6 54529 54848 2560 83 Linux
/dev/block/mmcblk0p7 54913 57472 20480 83 Linux
/dev/block/mmcblk0p8 57537 254144 1572864 83 Linux
/dev/block/mmcblk0p9 254209 946432 5537792 83 Linux
So the cache partition is still there (/dev/block/mmcblk0p2) but it doesn't appear in the mount list:
rootfs / rootfs ro,noatime 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,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext3 ro,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,data=ordered 0 0
tmpfs /mnt/extasec tmpfs rw,nodev,noatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p6 /lgdrm ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=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:17 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.MultitaskingDrawer-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/org.englishheritage.app-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/uk.agiletech.forestcomm-2 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.mxdata.tube.Market-1 vfat ro,dirsync,nosuid,nodev,noatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
If I try and unmount, mount or remount the cache partition I get 'Invalid argument'.
I have run a file system check on that partition and it shows 'clean'. So, to summarise, the cache partition is there, the file system is clean but it isn't being mounted and I can't mount it either. I'm baffled.
I would be really grateful for some suggestions.
I've made a correction and added some extra information under 'FURTHER EDIT' so I've bumped it.
I have the same problem on motorola defy (jordan)
BarrySamuels said:
I've made a correction and added some extra information under 'FURTHER EDIT' so I've bumped it.
Click to expand...
Click to collapse
Did you manage to solve it?
KfirSolomon said:
Did you manage to solve it?
Click to expand...
Click to collapse
Sorry for the very late reply but I've only just seen your post.
Yes I did solve it. It was because the partition had been formatted ext4 which my current OS didn't recognise. It used ext3 so I reformatted it manually via a terminal and all was well.
A Chairde
Having a problem extracting partitions using DD ....
Start of the process involves either CAT /PROC/MTD or /PROC/EMMC , but neither command works .. they are not in /PROC directory , and no CAT commands I ran there give a similar output to types I got off different phones ...
Ran these commands, outputs below ... ls /dev/mtd/mtd* is not working ..... no such files ... anyone give me some help on this ?
[email protected]:/system/media # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 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/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:1 /mnt/extsd fuseblk rw,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=asci
i,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/system/media # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd
93 32 819200 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 131072 nandi
93 72 13762560 nandj
179 0 31166976 mmcblk0
179 1 31162880 mmcblk0p1
[email protected]:/system/media #
I have purchased a new Honda Pilot and it has an android head unit. https://forum.xda-developers.com/android/help/heard-2016-honda-pilot-android-based-t3141346
Some very cleaver people have enabled root. https://forum.xda-developers.com/android/general/guide-how-to-gain-root-shell-2016-honda-t3487644
I want to install a navigation application, that does not use the internet to grab maps, but stores them locally but there is only 800 MB of space left on the device. I am looking to increase the amount of usable space (ext4 filesystem of course) so I can use a tool such as fmount to move the data directory of any application to a different device.
I have purchased a USB stick and Partitioned it as follows:
Device Boot Start End Sectors Size Id Type
/dev/sdg1 8064 47729114 47721051 22.8G c W95 FAT32 (LBA)
/dev/sdg2 47729115 60500789 12771675 6.1G 83 Linux
The first part for music and the second for storage!
When android starts up I have the follows mounts:
[email protected]:/ $ mount
rootfs / rootfs rw 0 0
/dev/root / ext4 ro,relatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=401076k,nr_inodes=100269,mode=755 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
tmpfs /acct tmpfs rw,relatime 0 0
tmpfs /cache tmpfs rw,relatime 0 0
tmpfs /config tmpfs rw,relatime 0 0
tmpfs /mnt tmpfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/root /system ext4 ro,relatime,data=ordered 0 0
tmpfs /tmp_database tmpfs rw,nosuid,nodev,noatime,nodiratime,size=65536k 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 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/mmcblk0p5 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p6 /var/log ext4 rw,nosuid,nodev,noatime,nodiratime,nomblk_io_submit,noauto_da_alloc,errors=remount-ro,data=ordered 0 0
/dev/block/mmcblk0p7 /vrdata ext4 rw,nosuid,nodev,noatime,nodiratime,nomblk_io_submit,noauto_da_alloc,errors=remount-ro,data=ordered 0 0
/dev/block/vold/8:1 /mnt/usb3 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/8:2 /mnt/shell/emulated/0 ext4 rw,relatime,data=ordered 0 0
Note that my primary partition is mounted as /mnt/usb3 and the second part is mounted as /mnt/shell/emulated/0 which is GREAT! But as you can see from the mount command there are no options on the mount so it is completely unusable. The other oddity is the directory "Android" is created on the /mnt/shell/emulated/0 file system every time I start up (boot process is creating this directory). I have tried to install some tools to allow me to automatically mount the partition such as scriptmanager and universal init.d but the unit is over writing something in the boot process and disabling any method to auto start scripts.
I don't need to modify the kernel, but I believe I do need to modify the init process. I have some experience with other ARM android devices but would like a little direction here.
I don't have it handy (from memory here) but /dev/block contains the following filesystems:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
31 0 256 mtdblock0
31 1 256 mtdblock1
31 2 256 mtdblock2
31 3 256 mtdblock3
31 4 256 mtdblock4
31 5 4096 mtdblock5
31 6 64 mtdblock6
31 7 64 mtdblock7
31 8 64 mtdblock8
31 9 64 mtdblock9
31 10 4096 mtdblock10
31 11 4096 mtdblock11
31 12 256 mtdblock12
31 13 512 mtdblock13
31 14 64 mtdblock14
31 15 64 mtdblock15
31 16 64 mtdblock16
31 17 256 mtdblock17
31 18 64 mtdblock18
31 19 64 mtdblock19
31 20 64 mtdblock20
31 21 64 mtdblock21
31 22 64 mtdblock22
31 23 64 mtdblock23
31 24 64 mtdblock24
31 25 64 mtdblock25
31 26 64 mtdblock26
31 27 64 mtdblock27
31 28 64 mtdblock28
31 29 64 mtdblock29
31 30 576 mtdblock30
179 0 3842048 mmcblk0
179 1 257008 mmcblk0p1
179 2 899640 mmcblk0p2
179 3 257040 mmcblk0p3
179 4 1 mmcblk0p4
179 5 771088 mmcblk0p5
179 6 257008 mmcblk0p6
179 7 1204843 mmcblk0p7
259 0 128488 mmcblk0p8
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
Domenic
edit: updated list of filesystems in /dev/block
maybe you need to look at the ramdisk to find the culprit command.
Sent from my Redmi Note 2 using Tapatalk
acestars said:
maybe you need to look at the ramdisk to find the culprit command.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
Yes, but first I need to discover which partition contains the kernel and init scripts. So that being said here is more information:
lets start with uname:
127|[email protected]:/ # busybox uname -a
Linux localhost 3.4.67-ltsi #1 SMP PREEMPT Mon Oct 24 10:08:15 JST 2016 armv7l GNU/Linux
self mount:
ID PARENT BLOCK ROOT MOUNT OPTIONS - TYPE SOURCE SUPEROPTS
14 1 179:2 / / ro,relatime shared:1 - ext4 /dev/root ro,data=ordered
15 14 0:5 / /dev rw,relatime shared:2 - devtmpfs devtmpfs rw,size=401076k,nr_inodes=100269,mode=755
16 15 0:13 / /dev rw,nosuid,relatime shared:3 - tmpfs tmpfs rw,mode=755
17 16 0:10 / /dev/pts rw,relatime shared:4 - devpts devpts rw,mode=600
18 14 0:3 / /proc rw,relatime shared:6 - proc proc rw
19 14 0:14 / /sys rw,relatime shared:7 - sysfs sysfs rw
20 14 0:15 / /acct rw,relatime shared:8 - tmpfs tmpfs rw
21 14 0:16 / /cache rw,relatime shared:10 - tmpfs tmpfs rw
22 14 0:17 / /config rw,relatime shared:1 - tmpfs tmpfs rw
23 14 0:18 / /mnt rw,relatime shared:12 - tmpfs tmpfs rw
24 14 0:19 / /storage rw,relatime shared:16 - tmpfs tmpfs rw
25 20 0:20 / /acct rw,relatime shared:9 - cgroup none rw,cpuacct
26 23 0:21 / /mnt/secure rw,relatime - tmpfs tmpfs rw,mode=700
27 23 0:22 / /mnt/asec rw,relatime shared:14 - tmpfs tmpfs rw,mode=755,gid=1000
28 23 0:23 / /mnt/obb rw,relatime shared:15 - tmpfs tmpfs rw,mode=755,gid=1000
29 16 0:24 / /dev/cpuctl rw,relatime shared:5 - cgroup none rw,cpu
30 14 179:2 /system /system ro,relatime shared:17 - ext4 /dev/root ro,data=ordered
34 14 0:25 / /tmp_database rw,nosuid,nodev,noatime,nodiratime shared:21 - tmpfs tmpfs rw,size=65536k
35 14 0:26 / /tmp rw,relatime shared:13 - tmpfs tmpfs rw
36 19 0:6 / /sys/kernel/debug rw,relatime shared:22 - debugfs /sys/kernel/debug rw
37 23 0:27 / /mnt/shell/emulated rw,nosuid,nodev,relatime shared:23 - fuse /dev/fuse rw,user_id=1023,group_id=1023,default_permissions, allow_other
31 14 179:5 / /data rw,nosuid,nodev,noatime,nodiratime shared:18 - ext4 /dev/block/mmcblk0p5 rw,nomblk_io_submit,noauto_da_alloc,errors=panic,d ata=ordered
982 14 179:6 / /var/log rw,nosuid,nodev,noatime,nodiratime shared:19 - ext4 /dev/block/mmcblk0p6 rw,nomblk_io_submit,noauto_da_alloc,errors=remount-ro,data=ordered
1947 14 179:7 / /vrdata rw,nosuid,nodev,noatime,nodiratime shared:20 - ext4 /dev/block/mmcblk0p7 rw,nomblk_io_submit,noauto_da_alloc,errors=remount-ro,data=ordered
2423 37 8:2 / /mnt/shell/emulated/0 rw,relatime shared:25 - ext4 /dev/block/vold/8:2 rw,data=ordered
1268 23 8:17 / /mnt/usb3 rw,nosuid,nodev,noexec,relatime shared:24 - vfat /dev/block/vold/8:17 rw,dirsync,uid=1000,gid=1023,fmask=0702,dmask=0702 ,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
2506 31 8:18 / /data/sdext2 rw,relatime shared:26 - ext4 /dev/block/sdb2 rw,data=ordered
and the mtd definitions
[email protected]:/proc # cat mtd
dev: size erasesize name
mtd0: 00040000 00010000 "spibooloader"
mtd1: 00040000 00010000 "uboot_recovery"
mtd2: 00040000 00010000 "uboot"
mtd3: 00040000 00010000 "uboot_env"
mtd4: 00040000 00010000 "kernel_dtb"
mtd5: 00400000 00010000 "kernel"
mtd6: 00010000 00010000 "vcom_paramater"
mtd7: 00010000 00010000 "target_infomation"
mtd8: 00010000 00010000 "product_test_data"
mtd9: 00010000 00010000 "sh4a_configuration"
mtd10: 00400000 00010000 "opening_image"
mtd11: 00400000 00010000 "sh4a_program"
mtd12: 00040000 00010000 "application_private"
mtd13: 00080000 00010000 "backup_data"
mtd14: 00010000 00010000 "startup_error_image1"
mtd15: 00010000 00010000 "startup_error_image2"
mtd16: 00010000 00010000 "startup_error_info"
mtd17: 00040000 00010000 "exception_info"
mtd18: 00010000 00010000 "dealer_management_area"
mtd19: 00010000 00010000 "unti_theft"
mtd20: 00010000 00010000 "update_table"
mtd21: 00010000 00010000 "versionup_information"
mtd22: 00010000 00010000 "fastboot_management_area"
mtd23: 00010000 00010000 "fastboot_program"
mtd24: 00010000 00010000 "inline_diag"
mtd25: 00010000 00010000 "tp_ic_configuration"
mtd26: 00010000 00010000 "factory_tuning_data"
mtd27: 00010000 00010000 "E.C_parameter"
mtd28: 00010000 00010000 "DSP_tuner_parameter"
mtd29: 00010000 00010000 "master_snapshot_area"
mtd30: 00090000 00010000 "Reserve"
fdisk does not look promising:
[email protected]:/ # busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3934 MB, 3934257152 bytes
255 heads, 63 sectors/track, 478 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 32 257008+ a0 Thinkpad hibernation
/dev/block/mmcblk0p2 33 144 899640 83 Linux
/dev/block/mmcblk0p3 145 176 257040 83 Linux
/dev/block/mmcblk0p4 177 470 2361555 5 Extended
/dev/block/mmcblk0p5 177 272 771088+ 83 Linux
/dev/block/mmcblk0p6 273 304 257008+ 83 Linux
/dev/block/mmcblk0p7 305 454 1204843+ 83 Linux
/dev/block/mmcblk0p8 455 470 128488+ 83 Linux
Unfortunatly /dev/block/platform does not contain any "by-name" data
Domenic