Whatever i tried to flash are phhuson's AOSP Squeak GSI, Lineage 19.1 GSI, and LeOSS GSI on specifically only the system image, but that error message isn't disappearing at all
Another error message also never disappears ...
Code:
E: unable to open or mount /system_root, /vendor, /odm, or /product (Block devices required)
Device: Samsung A125F; TWRP 3.6.11-Edward0181-DEV-RC4
But when trying to mount manuallly with mount -o rw,remount /system_root, it still reports ...
Code:
mount: '/system_root' not in /proc/mounts
Code:
E: error creating fstab
Then recreating dirs like /system_root, /system_image, /vendor, /odm, /product
Afterwards also running mount -o rw /system_root and mount -o rw system /system_image both reports ...
Code:
mount: 'system'->'/system_root': No such file or directory
mount: 'system'->'/system_image': No such file or directory
mount: 'vendor'->'/vendor': No such file or directory
mount: 'odm'->'/odm': No such file or directory
mount: 'product'->'/product': No such file or directory
Really everything missing? I'm quite unsure why it reports like those
Also, in Mount menu i'm also unable to remount System partition at all somewhy
Finally, mounting on /vendor, /odm, and /product also reports "no such files or directories"
symlinks missing - claim it to the maintainer (or fix fstab yourself)
https://github.com/edward0181/android_device_samsung_a12/tree/twrp-11.0/recovery/root/system/etc
Solved by last version of twrp.
https://github.com/edward0181/android_device_samsung_a12/releases
Related
I've just used a NBH witch is incompatible with the android ROM i'm using.
This is the NBH i used:
polaimg-panel3-240x320-2.6.32-froyo-06-09-10_22
The ROM i'm trying to boot:
Incubus26Jc's Super FroYo 2.2.1 [Deodexed] [RLS16] [10/2/10] All Languages
Tried reformatting my SD to FAT32, making a andboot folder on the sd, and extracting all the files in the androidinstall.tgz intro the andboot folder. Also tried the androidinstall.tgz in andboot.
Errorlog:
** /dev/block/mmcblk0p1
** Phase 1 - Read and Compare FATs
Attempting to allocate 120 KB for FAT
Attempting to allocate 120 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
537 files, 1854272 free (57946 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argument
Any ideas?
Thanks
Bump. Msgtoshort
Gixy said:
Bump. Msgtoshort
Click to expand...
Click to collapse
What? NBH, android? Whats the link from here for what you are trying to do?
but, in /etc/ there has two files i think are in conflict:
the first is fstab:
Code:
/dev/block/mtd/by-name/cache /cache ext4 rw
/dev/block/mtd/by-name/userdata /data ext4 rw
/dev/block/mtd/by-name/system /system ext4 rw
/dev/block/mtd/by-name/user /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
/dev/block/mmcblk0p1 /external_sd vfat rw
second is recovery.fstab:
Code:
/boot mtd boot
/cache ext4 /dev/block/mtd/by-name/cache
/data ext4 /dev/block/mtd/by-name/userdata
/kernel mtd kernel
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mtd/by-name/user lun=/sys/class/android_usb/android0/f_mass_storage/lun/file
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 lun=/sys/class/android_usb/android0/f_mass_storage/lun1/file
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/mtd/by-name/system
so, if there is 2 files that would to mount the paths, one of them are blocking other.
i say this cause i think "recovery.fstab" is the correct to mount in recovery mode.
but in this recovery mode isn't! /etc/fstab is mounting!
see like this.
i am in CWM and there a log in bottom with:
Code:
CWM-based Recovery modified by androtab.info v6.0.3.1
E:Can't find misc
E:Can't mount /cache/recovery/command
E:Can't find misc
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
and when i go to install zip from sdcard>choose zip from sdcard(internal storage, not is the removable sdcard):
E:Can't mount /sdcard/
but external sdcard (removable) it mount and open!
and when i go to mount /sdcard, or /cache, /data, /sd-ext, /system, it says: Error mounting /cache!, Error mounting /data!...
i don't know what can i do, cause, even sdcard can mount, /system cannot, and install a custom ROM cannot be done, even not backup the actual rom!
to finish, i say that i think is a conflict cause in ADB i go to mount /mnt (that is the path of sdcard, external_sd (...)) and it return:
mount: can't find /mnt in /etc/fstab
but if i am in recovery mode i would be in /etc/recovery.fstab
can someone help me?
my device is a DL 3003 (RK30x) is a brazilian product. and sorry for my bad english!
Solution: https://forum.xda-developers.com/moto-g6/help/mount-oem-t3818446
How I can mount /oem directory that I can uninstall system apps from there? I have tried mount -o rw,remount /oem from terminal but it didn't worked. TWRP can't mount that too. When i try this adb command: "mount -o rw,remount /oem" I will get this error: '/dev/block/dm-0' is read-only
Phone is Moto G6 Plus and rooted with Magisk.
I try to mount system and vendor partitions by using command below
Code:
sudo mount -o loop -t ext4 vendor.img vendor
got this error message
Code:
mount: xxx/xxx/vendor: wrong fs type, bad option, bad superblock on /dev/loop20, missing codepage or helper program, or other error
This command use to work on system image on different phone with same android version.
But I'm able to mount as RO using achieve mounter on Ubuntu.
Is there any way that I can mount those image as RW then edit some file in there?
OOS locks the system partition. No way in as of yet.
BeardKing said:
OOS locks the system partition. No way in as of yet.
Click to expand...
Click to collapse
Thank you
I am trying to edit my gps.conf because of some accuracy problems but before I can push the new one I need to make the system rw first. When I try to remount it I get the following errors:
FP4:/ # su
FP4:/ # mount -o remount,rw /system
mount: '/system' not in /proc/mounts
FP4:/ # mount -o rw,remount /
mount: '/dev/block/dm-8'->'/': I/O error
When I try just remount the following happens:
C:\platform-tools>adb remount
Skipping /system for remount
Skipping /system_ext for remount
Skipping /product for remount
Skipping /vendor for remount
Skipping /odm for remount
remount failed
disabling verity ends in the error "Device is locked. Please unlock the device first" - Even though that is not the case.
I read somewhere that this is bad news but I am unsure. I cant even install busybox apk because it fails to write to system.
I have never tried to touch the system partition before so I am unsure how I killed something, if that is actually the case.
Do you guys have any idea how to fix this? Thank you!