Android P, failed to mount /vendor, /dev/block/dm-5 is read only

解决Android P dm-verity问题
最新推荐文章于 2024-11-08 11:50:18 发布
原创 最新推荐文章于 2024-11-08 11:50:18 发布 · 3.1k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了在Android P设备上遇到dm-verity导致无法读写vendor分区的问题及解决方案。作者尝试了adb disable-verity命令，但在某些情况下需要进入fastboot模式解锁设备。最终通过在u-boot中禁用SELinux成功解决了问题。
AI助手已提取文章相关产品：

I tried to mount -o remount,rw /vendor on android P with user-debug build, and I got the feedback 'failed to mount /vendor, /dev/block/dm-5 is read only'.

I searched and it looks like dm-verity is in effect, so I tried the following cmd:

adb root

adb disable-verity  //if this cmd failed, you need try 'adb reboot bootloader->fastboot flashing unlock' 

adb reboot

adb disable-verity

adb reboot

Now, it still didn't work.

Then I tried to disable selinux in uboot. It worked.

您可能感兴趣的与本文相关内容

twrp显示 failed to mount system
yy的博客
08-25 1万+
环境介绍: 安卓9 twrp3.3.1 安装错误显示解决方法: 进入data清除 就是第一行第二个按钮; 然后选择高级 勾选除了外部存储之外所有 如果你想保留内部存储请对应勾选 之后就能够重新输入新的镜像了. 我刷的魔趣: https://www.mokeedev.com/ ...
Android dm设备和分区关系以及文件系统介绍
最新发布
a2591748032的博客
09-30 254
Android dm设备和分区关系以及文件系统介绍
Android O, failed to mount /system, /dev/block/dm-0 is read only 解决
PeterLocas的博客
07-05 3167
adb shell进入命令模式 mkdir /data/tmpfs mount -t tmpfs -o size=100M tmpfs /data/tmpfs
Android O, failed to mount /system, /dev/block/dm-0 is read only
houxn22的专栏
08-21 9640
from:https://android.stackexchange.com/questions/186630/android-o-failed-to-mount-system-dev-block-dm-0-is-read-only I try to mount /system in Android O to RW using the command mount -o rw,remount /s...
Linux文件系统只读Read-only file system的解决方法
热门推荐
TH_NUM的博客
03-27 2万+
df -h df -T 命令查看 这个是最简单的命令，文件系统类型在Type列输出。只可以查看已经挂载的分区和文件系统类型。如下所示： df -T /dev/sda1 设备unmount 面两条命令分别通过设备名和挂载点卸载文件系统，同时输出详细信息： umount -v /dev/sda1 通过设备名卸载 或者 umount -v /data2 通过挂载点卸载 第一步： 执行以下命令，查看删除文件所在目录的挂载方式: 如果结果显示挂载方式为ro，则根因
【原创】Android获得Root权限后文件系统仍然报Read-Only的问题
ddna的专栏
11-05 1万+
获得了Root权限后，adb shell进入文件系统，有时仍然不能对系统文件夹进行写操作，典型的如删除/system/app下的Apk，       例如系统报：rm failed for xxx.apk, Read-only file system       只要执行命令：mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
remount of /vendor failed: Read-only file system remount failed 解决报错
09-19
### **解决 `remount of /vendor failed: Read-only file system` 问题** 当尝试 `mount -o remount,rw /vendor` 时遇到该错误，通常由以下原因导致： 1. **文件系统损坏**（EXT4 错误触发只读保护）。 2. **`dm-...
9.687656][ T9] device-mapper: verity: 179:7: metadata block 65535 is corrupted [ 9.687703][ T1] EXT4-fs (dm-1): unable to read superblock [ 9.687726][ T1] [pid=1][BEGET][ERROR][fstab_mount.c:418]Mount device /dev/block/dm-1 to /vendor failed, err = 5, retry [ 9.687941][ T9] device-mapper: verity: 179:7: metadata block 65535 is corrupted [ 9.688000][ T1] EXT4-fs (dm-1): unable to read superblock [ 9.688010][ T1] [pid=1][BEGET][ERROR][fstab_mount.c:418]Mount device /dev/block/dm-1 to /vendor failed, err = 5, retry [ 9.688224][ T9] device-mapper: verity: 179:7: metadata block 65535 is corrupted [ 9.688283][ T1] EXT4-fs (dm-1): unable to read superblock [ 9.688292][ T1] [pid=1][BEGET][ERROR][fstab_mount.c:418]Mount device /dev/block/dm-1 to /vendor failed, err = 5, retry [ 9.939611][ T1] [pid=1][BEGET][ERROR][fstab_mount.c:381]Unsupported file system " none " [ 10.121327][ T1] [pid=1][Init][ERROR][switch_root.c:121]Failed to mount moving /mnt/data to /usr/mnt/data, err = 2 [ 10.199560][ T1] [pid=1][BEGET][ERROR][fstab.c:334]Failed to get fstab item from mount point " /misc " [ 10.200180][ T1] [pid=1][PARAM][ERROR][param_include.h:75]Invalid current param const.cust.config_dir_layer [ 10.200271][ T1] [pid=1][PARAM][ERROR][param_manager.c:673]Forbid to access const.cust.config_dir_layer label 0 0 [ 10.200285][ T1] [pid=1][PARAM][ERROR][param_manager.c:724]SystemReadParam failed! name is:const.cust.config_dir_layer, errNum is:1002! [ 10.200297][ T1] [pid=1][PARAM][ERROR][param_include.h:75]Invalid current param const.cust.follow_x_rules [ 10.200371][ T1] [pid=1][PARAM][ERROR][param_manager.c:673]Forbid to access const.cust.follow_x_rules label 0 0 [ 10.200383][ T1] [pid=1][PARAM][ERROR][param_manager.c:724]SystemReadParam failed! name is:const.cust.follow_x_rules, errNum is:1002! [ 10.202931][ T1] [pid=1][PARAM][ERROR][param_include.h:75]Invalid current param const.cust.config_dir_layer [ 10.203010][ T1] [pid=1][PARAM][ERROR][param_manager.c:673]Forbid to access const.cust.config_dir_layer label 0 0 [ 10.203023][ T1] [pid=1][PARAM][ERROR][param_manager.c:724]SystemReadParam failed! name is:const.cust.config_dir_layer, errNum is:1002! [ 10.203034][ T1] [pid=1][PARAM][ERROR][param_include.h:75]Invalid current param const.cust.follow_x_rules [ 10.203111][ T1] [pid=1][PARAM][ERROR][param_manager.c:673]Forbid to access const.cust.follow_x_rules label 0 0 [ 10.203122][ T1] [pid=1][PARAM][ERROR][param_manager.c:724]SystemReadParam failed! name is:const.cust.follow_x_rules, errNum is:1002! [ 10.207896][ T1] [pid=1][PARAM][ERROR][param_base.c:390]Invalid workSpace for musl.log.enable [ 10.207902][ T1] [pid=1][PARAM][ERROR][param_base.c:620]Forbid to access parameter musl.log.enable [ 10.207913][ T1] [pid=1][PARAM][ERROR][param_base.c:390]Invalid workSpace for musl.ld.debug.dlclose [ 10.207922][ T1] [pid=1][PARAM][ERROR][param_base.c:620]Forbid to access parameter musl.ld.debug.dlclose [ 10.207932][ T1] [pid=1][PARAM][ERROR][param_base.c:390]Invalid workSpace for debug.hitrace.tags.enableflags [ 10.207942][ T1] [pid=1][PARAM][ERROR][param_base.c:620]Forbid to access parameter debug.hitrace.tags.enableflags [ 10.307640][ T54] bbox:[info][blackbox_core.c:267] wait for log part [/data] end!
08-19
首先，用户的问题是关于Android设备启动日志中的错误："device-mapper verity metadata block corrupted EXT4-fs unable to read superblock" 和 "param_manager.c Forbid to access parameter"。我需要参考提供的...
Android存储系统-MountService 和vold 对外置存储的管理（1）
woai110120130的专栏
07-30 4928
现状介绍 PIXEL举例 sailfish:/ # df /dev/root 1999708 782936 1216772 40% / tmpfs 1898544 436 1898108 1% /dev tmpfs 1898544 0 1898544 0% /mnt /dev/block/sda31 292868 224200 68668 77% /vendor /dev/bl
rk3568 Android11/12 文件系统加载失败
weixin_35723192的博客
08-03 1058
Android系统的启动流程可以分为以下几个主要阶段：引导程序加载阶段、内核启动阶段、init进程启动和系统初始化阶段和Zygote进程启动和应用程序启动阶段。文件系统（system）加载异常通常存在于启动内核之后，init进程启动时。
4.271867] .(1)[7:kworker/u16:0][ST MSG] Sitronix TDDI Touch Driver v43.00.250117 [ 4.272712] .(6)[1:swapper/0]use default pe40_max_ibus:3000 [ 4.273693] .(1)[7:kworker/u16:0][ST MSG] i2c addr: 0x55 [ 4.274480] .(6)[1:swapper/0]use default CHG2_EFF:90 [ 4.275652] .(1)[7:kworker/u16:0][ST MSG] sitronix_ts_i2c_parse_dt: Interrupt GPIO = 214. (flag=0) , request ret = 0 [ 4.276373] .(6)[1:swapper/0]use default MAX_CHARGING_TIME:43200 [ 4.277358] .(1)[7:kworker/u16:0][ST MSG] sitronix_ts_i2c_parse_dt: Reset GPIO = 215. (flag=0), request ret = 0 [ 4.278080] .(6)[1:swapper/0]use default BC12_CHARGER:0 [ 4.278794] .(1)[7:kworker/u16:0][ST MSG] sitronix_ts_i2c_parse_dt: irq_gpio = 214, rst_gpio = 215 [ 4.279466] .(5)[1:swapper/0]use default sc_battery_size:3000 [ 4.281424] .(1)[7:kworker/u16:0][ST MSG] sitronix_ts_probe:818 [ 4.281587] .(5)[1:swapper/0]use default sc_cv_time:3600 [ 4.282898] .(1)[7:kworker/u16:0][ST MSG] start of sitronix_ts_probe [ 4.283585] .(5)[1:swapper/0]use default sc_current_limit:2000 [ 4.284214] -(2)[0:swapper/2][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=172 [ 4.284217] -(2)[0:swapper/2][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.284745] .(1)[7:kworker/u16:0][ST MSG] sitronix_ts_reset_device: Hardware Reset device. [ 4.285491] .(5)[1:swapper/0]algorithm name:SwitchCharging [ 4.285523] .(5)[1:swapper/0]mtk_charger_start_timer: alarm timer start:0, 14 242917768 [ 4.293167] -(5)[1:swapper/0]alarmtimer_enqueue, 14242917768 [ 4.294033] .(6)[1:swapper/0]*** Error : can't find PD adapter *** [ 4.294896] .(6)[1:swapper/0]mtk_charger_get_atm_mode: atm_enabled = 0 [ 4.295764] .(6)[1:swapper/0]sc_netlink_kernel_create success id:28 [ 4.296584] .(6)[1:swapper/0]sc_init: en:0 time:0,80000 tsoc:80 3000 3600 2000 [ 4.297551] .(6)[1:swapper/0]BOOTPROF: 4297.549470:probe: probe=platform_drv_probe drv=charger(0xffffff96bd5a0290) 35.150461ms [ 4.299284] .(6)[1:swapper/0]BOOTPROF: 4299.281778:initcall: mtk_charger_init 37.320923ms [ 4.299594] -(4)[292:dc_trim_thread][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=173 [ 4.300674] .(6)[1:swapper/0]cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 4.301444] -(4)[292:dc_trim_thread][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.303684] .(5)[1:swapper/0]cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 4.304732] .(5)[1:swapper/0]clk: Not disabling unused clocks [ 4.305514] .(5)[1:swapper/0][SWPM] phy_addr = 0x9cef3b00, virt_addr=0xffffff8008b03b00, size = 3072 [ 4.306091] .(2)[319:charger_thread]vbat_out_old=36410, vthr=682, T_curr=415, vbat_out=36447 [ 4.306722] .(6)[1:swapper/0][SWPM] copy pwr data (size: aphy/dram = 672/84) done! [ 4.306757] .(5)[125:kworker/5:1]platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 4.306760] .(5)[125:kworker/5:1]cfg80211: failed to load regulatory.db [ 4.308412] .(2)[319:charger_thread][CH3_DBG] bat_cur = -5226 [ 4.309125] .(6)[1:swapper/0]helio-dvfsrc 10012000.dvfsrc_top: Linked as a consumer to regulator.2 [ 4.310829] .(2)[319:charger_thread]mtk_bif_is_hw_exist: do not have bif driver [ 4.311610] .(6)[1:swapper/0]ALSA device list: [ 4.311759] .(2)[319:charger_thread][force_get_tbat] ntc_disable_nafg -40 25 [ 4.312904] .(6)[1:swapper/0] #0: mt-snd-card [ 4.313864] .(2)[319:charger_thread]Vbat=3645,Ibat=-4028,I=0,VChr=4494,T=25,Soc=-1:-1,CT:0:0 hv:1 pd:0:0 [ 4.314981] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=174 [ 4.315391] -(2)[319:charger_thread]CPU: 2 PID: 319 Comm: charger_thread Tainted: G W 4.19.191-svn1452 #1 [ 4.315964] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.317186] -(2)[319:charger_thread]Hardware name: MT8788 (DT) [ 4.321121] -(2)[319:charger_thread]Call trace: [ 4.321137] -(2)[319:charger_thread] dump_backtrace+0x0/0x164 [ 4.321146] -(2)[319:charger_thread] show_stack+0x20/0x2c [ 4.323223] -(2)[319:charger_thread] dump_stack+0xb8/0xf0 [ 4.324654] -(2)[319:charger_thread] charger_routine_thread+0x1a0/0xa48 [ 4.325527] -(2)[319:charger_thread] kthread+0x13c/0x14c [ 4.326238] -(2)[319:charger_thread] ret_from_fork+0x10/0x18 [ 4.326837] .(5)[1:swapper/0]Freeing unused kernel memory: 1728K [ 4.327215] .(2)[319:charger_thread][CH3_DBG] bat_cur = -3584 [ 4.327821] .(5)[1:swapper/0]BOOTPROF: 4327.818470:Kernel_init_done [ 4.329411] .(5)[1:swapper/0]Run /init as init process [ 4.329633] .(2)[319:charger_thread][force_get_tbat] ntc_disable_nafg -40 25 [ 4.330361] -(3)[0:swapper/3][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=175 [ 4.331961] -(3)[0:swapper/3][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.333708] .(2)[319:charger_thread]vbat_out_old=36390, vthr=681, T_curr=421, vbat_out=36428 [ 4.345737] -(5)[0:swapper/5][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=176 [ 4.346679] -(5)[0:swapper/5][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.361126] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=177 [ 4.362078] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.365048] .(6)[1:init]init 3: init first stage started! [ 4.365822] .(6)[1:init]init 3: Unable to open /lib/modules, skipping module loading. [ 4.367035] .(6)[1:init]init 3: Copied ramdisk prop to /second_stage_resources/system/etc/ramdisk/build.prop [ 4.368461] .(6)[1:init]init 3: Switching root to '/first_stage_ramdisk' [ 4.369638] .(6)[1:init]init 3: [libfs_mgr]ReadFstabFromDt(): failed to read fstab from dt [ 4.371835] .(6)[1:init]init 3: Using Android DT directory /proc/device-tree/firmware/android/ [ 4.375621] .(6)[1:init]zwj get_battery_status 374 status = 2 [ 4.376506] -(6)[1:init][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=178 [ 4.377391] -(6)[1:init][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.391877] -(7)[0:swapper/7][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=179 [ 4.392819] -(7)[0:swapper/7][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.403592] .(1)[7:kworker/u16:0][ST MSG] IC Chip ID = 0x85 [ 4.405262] .(1)[7:kworker/u16:0][ST MSG] IC SFR VER = 0x46 [ 4.406006] .(1)[7:kworker/u16:0][ST MSG] sitronix_ts_reset_device: Hardware Reset device. [ 4.407255] -(5)[0:swapper/5][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=180 [ 4.408196] -(5)[0:swapper/5][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.411422] .(6)[1:init]power_supply sy6982e: driver reporting unsupported connected type [ 4.412484] .(6)[1:init]synth uevent: /devices/platform/odm/odm:sy6892e/power_supply/sy6982e: failed to send uevent [ 4.412488] .(6)[1:init]power_supply sy6982e: uevent: failed to send synthetic uevent [ 4.422636] -(5)[0:swapper/5][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=181 [ 4.423576] -(5)[0:swapper/5][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.426160] .(5)[1:init]init 3: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/by-name/md_udc [ 4.428247] .(5)[1:init]EXT4-fs (mmcblk0p7): Ignoring removed nomblk_io_submit option [ 4.432276] .(5)[1:init]EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit [ 4.433853] .(5)[1:init]init 3: [libfs_mgr]check_fs(): mount(/dev/block/by-name/md_udc,/metadata,ext4)=0: Success [ 4.438022] -(3)[0:swapper/3][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=182 [ 4.438973] -(3)[0:swapper/3][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.453406] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=183 [ 4.454356] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.456387] .(4)[1:init]init 3: [libfs_mgr]check_fs(): unmount(/metadata) succeeded [ 4.457539] .(4)[1:init]init 6: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/mmcblk0p7 [ 4.459268] .(4)[1:init]logwrapper 6: Cannot log to file /dev/fscklogs/log [ 4.460180] .(4)[1:init]logwrapper 6: [ 4.460813] .(4)[1:init]e2fsck: e2fsck 1.45.4 (23-Sep-2019) [ 4.462449] .(4)[1:init]e2fsck: /dev/block/by-name/md_udc: clean, 34/5792 files, 1783/5786 blocks [ 4.467588] .(4)[1:init]EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: discard [ 4.468774] -(7)[0:swapper/7][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=184 [ 4.468891] .(4)[1:init]init 6: [libfs_mgr]__mount(source=/dev/block/by-name/md_udc,target=/metadata,type=ext4)=0: Success [ 4.469717] -(7)[0:swapper/7][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.472662] .(4)[1:init]init 6: Failed to copy /avb into /metadata/gsi/dsu/avb/: No such file or directory [ 4.475713] .(4)[1:init]init 6: [libfs_mgr]Created logical partition product_a on device /dev/block/dm-0 [ 4.476956] .(4)[1:init]init 6: [libfs_mgr]Skipping zero-length logical partition: product_b [ 4.478529] .(4)[1:init]init 6: [libfs_mgr]Created logical partition system_a on device /dev/block/dm-1 [ 4.480210] .(4)[1:init]init 6: [libfs_mgr]Created logical partition system_b on device /dev/block/dm-2 [ 4.481830] .(4)[1:init]init 9: [libfs_mgr]Created logical partition vendor_a on device /dev/block/dm-3 [ 4.483081] .(4)[1:init]init 9: [libfs_mgr]Skipping zero-length logical partition: vendor_b [ 4.484162] -(2)[0:swapper/2][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=185 [ 4.484168] -(2)[0:swapper/2][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.485182] .(4)[1:init]init 9: DSU not detected, proceeding with normal boot [ 4.492594] .(4)[1:init]init 9: [libfs_avb]Invalid hash size: [ 4.493377] .(4)[1:init]init 9: [libfs_avb]Failed to verify vbmeta digest [ 4.494277] .(4)[1:init]init 9: [libfs_avb]Returning avb_handle with status: VerificationDisabled [ 4.495468] .(4)[1:init]init 9: Top-level vbmeta is disabled, skip Hashtree setup for /system [ 4.497079] .(4)[1:init]init 9: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-1 [ 4.499543] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=186 [ 4.500107] .(4)[1:init]EXT4-fs (dm-1): mounted filesystem without journal. Opts: [ 4.500493] -(1)[0:swapper/1][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.501512] .(4)[1:init]init 9: [libfs_mgr]__mount(source=/dev/block/dm-1,target=/system,type=ext4)=0: Success [ 4.503839] .(4)[1:init]init 6: Switching root to '/system' [ 4.509219] .(4)[1:init]init 6: [libfs_avb]AVB HASHTREE disabled on: /vendor [ 4.510594] .(4)[1:init]init 6: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-3 [ 4.513648] .(4)[1:init]EXT4-fs (dm-3): mounted filesystem without journal. Opts: [ 4.514681] .(4)[1:init]init 6: [libfs_mgr]__mount(source=/dev/block/dm-3,target=/vendor,type=ext4)=0: Success [ 4.514920] -(2)[0:swapper/2][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=187 [ 4.516417] .(4)[1:init]init 6: [libfs_avb]AVB HASHTREE disabled on: /product [ 4.516914] -(2)[0:swapper/2][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.518141] .(4)[1:init]init 6: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-0 [ 4.521237] .(4)[1:init]EXT4-fs (dm-0): mounted filesystem without journal. Opts: [ 4.522253] .(4)[1:init]init 6: [libfs_mgr]__mount(source=/dev/block/dm-0,target=/product,type=ext4)=0: Success [ 4.527011] .(1)[7:kworker/u16:0][ST MSG] buf = 0, 0, 0, 0, 2, D0, 6, 4C [ 4.527893] .(1)[7:kworker/u16:0][ST MSG] Status register = 0. [ 4.528855] .(1)[7:kworker/u16:0][ST MSG] FW Version (hex) = 1 [ 4.529904] .(1)[7:kworker/u16:0][ST MSG] FW revision (hex) = 1 47 1 7 [ 4.530295] -(5)[292:dc_trim_thread][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=188 [ 4.531438] .(1)[7:kworker/u16:0][ST MSG] Customer Info (hex) = 7 5 4 7 [ 4.531782] -(5)[292:dc_trim_thread][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.533073] .(1)[7:kworker/u16:0][ST MSG] Resolution = 720 x 1612 [ 4.534541] .(1)[7:kworker/u16:0][ST MSG] Max touches = 10. [ 4.535291] .(4)[1:init]init 6: Skipped setting INIT_AVB_VERSION (not in recovery mode) [ 4.536563] .(1)[7:kworker/u16:0][ST MSG] Chip ID = 0x85. [ 4.545677] -(6)[0:swapper/6][DDP/IRQ]error:IRQ: ovl0 frame underflow! cnt=189 [ 4.546620] -(6)[0:swapper/6][DDP/IRQ]error:IRQ: ovl0 hw reset done [ 4.547846] .(1)[7:kworker/u16:0][ST MSG] X_chs = 18. [ 4.548540] .(1)[7:kworker/u16:0][ST MSG] Y_chs = 32. [ 4.549217] .(1)[7:kworker/u16:0][ST MSG] K_chs = 0. [ 4.549923] .(1)[7:kworker/u16:0][ST MSG] swk_num = 0. [ 4.550910] .(1)[7:kworker/u16:0][ST MSG] Misc. Info = 0xFF. [ 4.551869] .(1)[7:kworker/u16:0]input: sitronix_ts_i2c as /devices/platform/11007000.i2c/i2c-0/0-0055/input/input4 [ 4.553312] .(1)[7:kworker/u16:0][ST MSG] [JH]sitronix_ts_probe: irq = 302 [ 4.554459] .(1)[7:kworker/u16:0]gpio gpiochip0: (pinctrl_paris): gpiochip_lock_as_irq: tried to flag a GPIO set as output for IRQ [ 4.556005] .(1)[7:kworker/u16:0]mt6771-pinctrl 1000b000.pinctrl: unable to lock HW IRQ 150 for IRQ [ 4.557202] .(1)[7:kworker/u16:0]genirq: Failed to request resources for sitronix_ts_i2c (irq 302) on irqchip mt-eint [ 4.558736] .(1)[7:kworker/u16:0][ST ERR] sitronix_ts_probe: request_irq failed! ret=-5 [ 4.559810] .(1)[7:kworker/u16:0][ST MSG] [JH]sitronix_ts_probe: request_irq failed! ret=-5 [ 4.560919] .(1)[7:kworker/u16:0][ST MSG] sitronix_mt_stop 目前状态位gpio为输出
09-30
dev_err(dev, "Failed to set GPIO%d as input\n", gpio_int); return ret; } ``` **步骤2：确保中断注册正确** ```c ts->irq = gpio_to_irq(gpio_int); // GPIO转IRQ号 ret = devm_request_irq(dev, ts->...
adb remount mount: ‘/dev/block/dm-0′-＞’/system’: Device or resource busy
PixelColor的博客
10-02 6056
Android 7.1之后出现无法正常adb remount的问题，一般会出现以下打印信息 mount -o remount,rw /system 出现以下打印： mount: '/dev/block/dm-0'->'/system': Device or resource busy adb remount 出现以下： remount of /system failed: Read-only file system remount failed 可以尝试以下指令来实现： adb root adb
在 Android 5.1.1 执行 remount system failed 解决方法
快乐&&平凡
12-11 1万+
shanshanx@shanshanx:~$ adb root adbd is already running as root shanshanx@shanshanx:~$ adb remount dm_verity is enabled on the system partition. Use "adb disable-verity" to disable verity. If you
vagrant up报错mounting failed with the error: No such device 挂载目录失败
weixin_30856725的博客
07-12 547
vagrant up报以下错误： 解决方法一 vagrant plugin install vagrant-vbguest vagrant vbguest 解决方法二 vagrant plugin install vagrant-winnfsd vagrant plugin install vagrant-vbguest 转载于:https://www.cnblogs.com...
U盘挂载错误：只读文件系统（Read-only file system）
zy13131313的博客
11-08 2754
在一次日常工作中，我将U盘插入Ubuntu系统后，系统自动挂载了U盘。但是，当我尝试对U盘内的文件进行修改或删除操作时，系统却提示“只读文件系统”。这让我意识到，U盘被挂载为只读模式，无法进行写入操作。是一个用于Linux的NTFS文件系统驱动程序，支持读写NTFS文件系统。我决定尝试安装这个驱动程序。驱动程序后，U盘成功挂载为读写模式，我能够正常对U盘内的文件进行修改和删除操作。问题得到了圆满解决。遇到问题后，我首先想到的是上网搜索解决方案。在我几乎要放弃的时候，我偶然间看到了一个关于。
failed Read-only file system 问题！解决方案
一只攻城的柿子
08-31 1万+
当adb push *.apk /system/app的时候出现Read-only file system的时候adb shell mount -o remount / / android adb shell命令使用   当运行一个命令的时候出现 rm failed for CoeeRoat.apk, Read-only file system adb shell m
verity cannot ... ‘/dev/block/dm-4‘ is read-only/ 证书cacerts系统目录
leaon的博客
08-09 2643
android 证书放进系统目录
【解决】模拟器设置system读写报错‘/dev/block/sda6‘ is read-only mount: ‘/system‘ not in /proc/mounts adb disable-v
yunmuq的博客
12-01 4692
remount 失败 '/dev/block/sda6' is read-only adb disable-verity failed to read fstab '/dev/root' is read-only mount -o remount,rw /system mount: '/system' not in /proc/mounts mount -o rw,remount -t auto / 主要是设置没调好
如何解决linux文件系统read-only的状况。
河马的BLOG
08-25 7566
当你把一个根目录挂载到别的分区上的时候，如果不进行umount动作，这个文件系统很可能成为一个read-only系统，不能进行任何的写和读的动作。显示为Read-only file system,可以使用如下的命令解决这个问题。 mount -o remount,rw /
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值