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
hello i flash my drivice mtk6592 ( star n3+ ocracore ) with a same rom.
is not first time to i flash rom, but dhis new phone worked just a 30 min
after flash my touch screen dont work . and imei ( imei fix ok)
i try so send a lots rom , rom accept never found error . same my touch screen dont work.
and factory rom no success.
maybe i need to edit scatter file?
maybe my touch screen is bricked?
maybe my touch screen have hardware problem?
dhis is my test
Code:
============ Memory Detection Report ===========
Internal RAM:
Size = 0x00020000 (128KB)
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000020000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000003a3e00000(14910MB)
============ RAM Test ============
Data Bus Test:
[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!
Address Bus Test:
[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
[A29]
OK!!
RAM Pattern Test :
Writing ...
OK!!
Increment/Decrement Test:
Writing...
OK!!
============ NAND Test ============
SKIP! NAND Flash was not detected!
============ EMMC Test ============
OK!!
Code:
?????????adb?fastboot?????,??:
??adb??:adb devices
??shell:adb shell
??????:adb logcat
???????SD?:adb push D:\myfile.pdf /sdcard/
???SD?????:adb pull /sdcard/myfile.pdf D:\
??fastboot??:fastboot devices
??adb????:adb help
??fastboot????:fastboot help
C:\Program Files (x86)\Shuame>adb shell
[email protected]_v92_zlh_hd:/ $ cat /proc/devices
cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
13 input
14 sound
29 fb
90 mtd
108 ppp
116 alsa
128 ptm
136 pts
141 mtk_stp_usktrk
153 mtk_wmt_WIFI_chrdev
160 Vcodec
166 ttyACM
168 MJC
180 usb
182 sec
184 ccci0
184 CCCI_IPC_DEV0
184 ccci1_fs
184 vir_chr0
184 ccci_tty_drv0
188 M4U_device
189 usb_device
190 mtk_stp_wmt
191 mtk_stp_GPS_chrdev
192 mtk_stp_BT_chrdev
193 fm
196 devmap
204 ttyMT
226 ttyGS
227 camera-pipemgr
228 mt3326-gps
229 camera-sysram
230 camera-isp
231 FM50AF
232 kd_camera_hw
233 DumChar
234 accdet
235 mtk-adc-cali
236 mtk_disp
237 MTK_SMI
238 dummy_eeprom
239 dummy_cam_cal
240 hall_dev
241 AGOLD_DRIVER
242 mtk_jpeg
243 pmt
244 kd_camera_flashlight
245 flash_info
246 btn
247 mtk_almk
248 btif
249 MT_pmic_adc_cali
250 mtkfb_vsync
251 mmp
252 sched
253 BOOT
254 rtc
Block devices:
259 blkext
7 loop
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 zram
254 device-mapper
[email protected]_v92_zlh_hd:/ $
C:\Program Files (x86)\Shuame>adb shell
[email protected]_v92_zlh_hd:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
253 0 1048576 zram0
179 0 15246336 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 819200 mmcblk0p5
179 6 131072 mmcblk0p6
179 7 1212416 mmcblk0p7
179 8 13001728 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 7764992 mmcblk1
179 97 7760896 mmcblk1p1
[email protected]_v92_zlh_hd:/ $ mount
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/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
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ord
ered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:8 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/sdcard0 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
/dev/block/vold/179:97 /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 /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]_v92_zlh_hd:/ $
BliNeR-KeY said:
hello i flash my drivice mtk6592 ( star n3+ ocracore ) with a same rom.
is not first time to i flash rom, but dhis new phone worked just a 30 min
after flash my touch screen dont work . and imei ( imei fix ok)
i try so send a lots rom , rom accept never found error . same my touch screen dont work.
and factory rom no success.
maybe i need to edit scatter file?
maybe my touch screen is bricked?
maybe my touch screen have hardware problem?
Click to expand...
Click to collapse
Same happened to me. Have you managed to fix this issue?
anyone found solution?
same happened to me too. i've tried removing the digitizer, but i don't think the problem is in digitizer. when it's connected i can see touchscreen: ili2113a in factory mode. when i disconnect the digitizer, i can see touchscreen: (null)
so digitizer should be working. i've tried flashing like 15 roms, but didn't manage to fix the problem.
anyone found a solution?
hello
you solved?
---------- Post added at 11:45 AM ---------- Previous post was at 11:34 AM ----------
maybe not yet solved
İ have same as your problem. My device is General Mobile etab5. Calibration failed it says invalid value: 165
Regarding Pixel 32GB, I want to know the size of each partition(boot, system etc).
Please show below via adb shell.
cat /proc/partitions
ls -l /dev/block/platform/soc/7824900.sdhci/by-name
notice: "7824900.sdhci" is diffirent name folder.
Sorry, the following path is correct.
ls -l /dev/block/bootdevice/by-name
Can't list the /dev directory due to lack of permissions. Best I can give you is /proc/partitions:
Code:
sailfish:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
8 0 31145984 sda
8 1 512 sda1
8 2 512 sda2
8 3 512 sda3
8 4 512 sda4
8 5 2048 sda5
8 6 2048 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 512 sda10
8 11 512 sda11
8 12 512 sda12
8 13 256 sda13
8 14 256 sda14
8 15 256 sda15
259 0 256 sda16
259 1 4096 sda17
259 2 4096 sda18
259 3 32768 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 32768 sda22
259 7 128 sda23
259 8 128 sda24
259 9 71680 sda25
259 10 71680 sda26
259 11 256 sda27
259 12 256 sda28
259 13 256 sda29
259 14 256 sda30
259 15 307200 sda31
259 16 307200 sda32
259 17 2097152 sda33
259 18 2097152 sda34
259 19 26038272 sda35
259 20 4820 sda36
8 32 4096 sdc
8 33 4052 sdc1
8 16 4096 sdb
8 17 4052 sdb1
8 48 49152 sdd
8 49 1024 sdd1
8 50 8 sdd2
8 51 32768 sdd3
8 52 128 sdd4
8 53 4 sdd5
8 54 4 sdd6
8 55 1024 sdd7
8 56 4 sdd8
8 57 2048 sdd9
8 58 2048 sdd10
8 59 1024 sdd11
8 60 4 sdd12
8 61 9020 sdd13
8 64 36864 sde
8 65 512 sde1
8 66 6144 sde2
8 67 4096 sde3
8 68 2048 sde4
8 69 16384 sde5
8 70 7636 sde6
8 80 8192 sdf
8 81 16 sdf1
8 82 256 sdf2
8 83 2048 sdf3
8 84 4 sdf4
8 85 5824 sdf5
253 0 2064396 dm-0
253 1 302360 dm-1
Thank you so much for reply!
I have a another request.
Please show below via adb shell.
df
mount
tatsu_vel said:
Thank you so much for reply!
I have a another request.
Please show below via adb shell.
df
mount
Click to expand...
Click to collapse
Here you go:
sailfish:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1999708 1484912 498412 75% /
tmpfs 1898468 440 1898028 1% /dev
tmpfs 1898468 0 1898468 0% /mnt
/dev/block/dm-1 292868 223040 63784 78% /vendor
/dev/block/bootdevice/by-name/userdata 25497924 8109564 17371976 32% /data
/dev/fuse 25497924 8109564 17371976 32% /storage/emulated
sailfish:/ $ mount
rootfs on / type rootfs (rw,seclabel)
/dev/root on / type ext4 (ro,seclabel,relatime,data=ordered)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1898468k,nr_inodes=474617,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1898468k,nr_inodes=474617,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/dm-1 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/modem_a on /firmware/radio type vfat (ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/bootdevice/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1898468k,nr_inodes=474617,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Click to expand...
Click to collapse
I've been reading through many threads on the subject, and it seems that we still don't have a reliable way to root this phone.
Is there any word yet on a TWRP build? Are there any viable alternatives to TWRP?
I'm really starting to miss some of the apps I use that require root.
There are very reliable methods that work..
Just look within this forum.
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
xichael said:
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
Click to expand...
Click to collapse
Root doesn't differ from model variants. It's not perfect but works most of the time.
xichael said:
Where? Pretty sure I've read through every thread on the subject, and all the options are half-baked in one way or another; no backup, designed for a different model, reports of bootloops, messed up file systems, etc.
Can you point me to a verifiably functioning technique for my FRD-L04?
Click to expand...
Click to collapse
Nothing bad will happen if you do the steps right. Head over to the bootloader unlock thread.
I'm not taking any chances. To quote from another thread:
evilpaul13 said:
The SuperSU's not the problem it's nobody's made a working TWRP for FRD-L04. I've seen lots of people who tried the Mondaco TWRP on L04 say they just got a bootloop with one guy saying it worked, but he couldn't make a backup and just install the root package.
Click to expand...
Click to collapse
Try philz touch recovery or other cwm recovery for rooting honor 8
xichael said:
I've been reading through many threads on the subject, and it seems that we still don't have a reliable way to root this phone.
Is there any word yet on a TWRP build? Are there any viable alternatives to TWRP?
I'm really starting to miss some of the apps I use that require root.
Click to expand...
Click to collapse
I am also hesitant to do this on my brand new L04. What are the steps to download and flash the stock ROM for this specific model in case it is bricked? I have not found anything about this yet.
I'd very much like to be able to root, but everything I've read makes it look less than promising at the moment. Honor has the B122 firmware from September on their site: http://www.hihonor.com/us/support/details/index.html?DOC_ID=89264
I'm running B150 though which I got OTA and don't really want to go back to an older version with broken auto-brightness if things don't go right. I had B144 when I got the thing.
So the initial release firmware is available for the L04? I guess we can flash it with Hisuite?
If we want to get TWRP working on L04 we need to send partition mount info to the developer that made TWRP work on the other Honor 8 models. I am not sure who that person would be. I have attached the info I am able to get without root. We may need `cat /proc/mtd`. But this virtual device can only be read by root. If anyone has working root on L04 please post here and share with TWRP developer for Honor 8.
Code:
1|[email protected]:/ $ cat /proc/partitions
major minor #blocks name
253 0 524288 zram0
179 0 30535680 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 12288 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 65536 mmcblk0p30
179 31 65536 mmcblk0p31
179 32 16384 mmcblk0p32
179 33 8192 mmcblk0p33
179 34 16384 mmcblk0p34
179 35 65536 mmcblk0p35
179 36 262144 mmcblk0p36
179 37 2048 mmcblk0p37
179 38 2048 mmcblk0p38
179 39 3670016 mmcblk0p39
179 40 524288 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 25255936 mmcblk0p42
179 96 4096 mmcblk0rpmb
179 48 4096 mmcblk0boot0
179 144 61259776 mmcblk1
179 145 61258752 mmcblk1p1
252 0 3641084 dm-0
252 1 520124 dm-1
252 2 25255920 dm-2
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1869360k,nr_inodes=467340,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,ionice,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/frz cgroup rw,relatime,freezer 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 /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=750,gid=1000 0 0
none /sys/fs/cgroup/pids cgroup rw,relatime,pids 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime,gid=1000,mode=755 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/block/vold/public:179:145 /mnt/media_rw/1EF6-36FE exfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,iocharset=utf8,namecase=0,errors=remount-ro 0 0
/dev/fuse /mnt/runtime/default/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/dm-1 /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/splash2 /splash2 ext4 rw,context=u:object_r:splash2_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodem /3rdmodem ext4 ro,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodemnvm /3rdmodemnvm ext4 rw,context=u:object_r:radio_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/3rdmodemnvmbkp /3rdmodemnvmbkp ext4 rw,context=u:object_r:radio_data_file:s0,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/secure_storage /sec_storage ext4 rw,context=u:object_r:teecd_data_file:s0,nosuid,nodev,noatime,discard,nodelalloc,data=journal 0 0
/dev/block/bootdevice/by-name/modemnvm_img /mnvm2:0 ext4 rw,context=u:object_r:modem_nv_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/modem_om /modem_log ext4 rw,context=u:object_r:modem_log_file:s0,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/dm-2 /data f2fs rw,seclabel,nosuid,nodev,noatime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,extent_cache,active_logs=6 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023,derive=legacy,reserved=20MB 0 0
/dev/fuse /storage/1EF6-36FE fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/self tmpfs rw,seclabel,relatime,size=1869360k,nr_inodes=467340,mode=755,gid=1000 0 0
[email protected]:/ $
Tk has a video. Watch it.
kevev said:
I am also hesitant to do this on my brand new L04. What are the steps to download and flash the stock ROM for this specific model in case it is bricked? I have not found anything about this yet.
Click to expand...
Click to collapse
It's pretty much like any Huawei. And I think the worst case is bootloop, except if you flash some other's model recovery or system.
Download stock full OTA
Extract boot.img, recovery.img, cust.img and system.img from update.app file with Huawei firmware extractor.
To go back to stock just flash boot and recovery partitions.
kevev said:
...we need to send partition mount info to the developer that made TWRP work on the other Honor 8 models. I am not sure who that person would be...
Click to expand...
Click to collapse
Here's the thread where it was originally posted: http://www.modaco.com/forums/topic/377647-twrp-recovery-3020-for-honor-8/
Here's the dev's xda acct: http://forum.xda-developers.com/member.php?u=220328
xichael said:
Here's the thread where it was originally posted: http://www.modaco.com/forums/topic/377647-twrp-recovery-3020-for-honor-8/
Here's the dev's xda acct: http://forum.xda-developers.com/member.php?u=220328
Click to expand...
Click to collapse
Thanks. I sent the dev a PM earlier today on XDA. No preply yet. I am not able to register on modaco. I never receive the registration email. Could someone ping him there for me?
Sent from my FRD-L04 using XDA Free mobile app
kevev said:
Thanks. I sent the dev a PM earlier today on XDA. No preply yet. I am not able to register on modaco. I never receive the registration email. Could someone ping him there for me?
Click to expand...
Click to collapse
Done!
Tmobilefan906 said:
Done!
Click to expand...
Click to collapse
Appreciated
Sent from my FRD-L04 using XDA Free mobile app
So there's finally a working copy of TWRP for the Honor 8: https://twrp.me/devices/huaweihonor8.html
And fortunately the backup/restore feature works properly, as I needed it after UPDATE-SuperSU-v2.46.zip threw my phone into a bootloop.
Is there a different SuperSU zip I could try flashing?
EDIT:
Found the current v2.78, which worked fine: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Google's top results were pointing to the old version on chainfire.eu. Shoulda checked here first...
xichael said:
So there's finally a working copy of TWRP for the Honor 8: https://twrp.me/devices/huaweihonor8.html
And fortunately the backup/restore feature works properly, as I needed it after UPDATE-SuperSU-v2.46.zip threw my phone into a bootloop.
Is there a different SuperSU zip I could try flashing?
Click to expand...
Click to collapse
46 is outdated. Try 78. If it's still giving you bootloop, try phh's SU.
Sent from my honor 5X using XDA Labs
GensTattu said:
I want somebody can help me finished it, it is too difficult for me .
Click to expand...
Click to collapse
What step are you on?
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