I've already tried my class 10 sdcard ext3 + swap partitioned but it was not accepted by formerly unrooted htc genuine firmware.
Other threads say partition order and a vfat 1. partition is mandatory?
http://forum.xda-developers.com/showthread.php?t=1229030&highlight=swap+file
http://forum.xda-developers.com/showthread.php?t=699776
I would prefer the swapfile way before repartition the sdcard.
Swap could be enabled, but in which config file /.rc are fstab and mount cmds?
I need to remount /system rw to access system configs and make changes permanent?
Code:
# free
total used free shared buffers
Mem: 428420 418192 10228 0 32
-/+ buffers: 418160 10260
Swap: 0 0 0
#
# ./ls -ltrh /system/etc
...
-rw-r--r-- 1 0 0 613 Mar 26 02:45 vold.fstab
# ./cat /etc/vold.fstab
## Vold 2.0 fstab for HTC Passion
#
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# ./cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
nodev ramfs
vfat
nodev fuse
fuseblk
nodev fusectl
yaffs
yaffs2
THIS IS FOR DEVELOPMENT ONLY!!!! THIS IS ONLY A CONCEPt FORGETTING THE 1GB SYSTEM PARTITION.
30-Jan-13 update
Ok so using this method I now have a ported rom from the Samsung Galaxy S3 that has a 680+mb system booting on my G2. If any of you feel like helping me get it up and running PM me or you can download it from here http://sourceforge.net/projects/sgs3forg2/files/FJB4G2-orig-runtime.zip/download and see for yourself...
MAJOR EDIT: SO THE UPLOAD MUST HAVE BEEN CORRUPTED FOR THE EM1.zip. IT IS NON FUNCTIONAL. ALL CREDIT TO THE ONE I WILL PUT UP GOES TO FLINNY. I IN NO WAY DID ANYTHING TO CREATE THIS ROM JUST ALTERED THE MOUNTS TO GET THE 1GB SYSTEM PARTITION. THE FILE IS NAMED f10.zip. it is his 10.1 base.
Ok so I know its been a while but I have something I can not keep away from the community. Anyone want to get a 1GB System and 549MB Data partition??? Yes thats right we can swap the partitions. here is a link to some screen shots and another to, with the permission of nik3r, the modified Elitemod Rom. just go into recovery, format all partitions(sorry you will have to start over in order to swap the partitions, well for now that is), and flash the EM1.zip
http://www.mediafire.com/?ka8yq4hzs6upj
Ok so this all started after my wife got her new phone the samsung galaxy s3. in love with the phone and what it could do but unable to, due to financial constraints and TMobiles unwillingness to give me one for free like they did my wife, I set forth trying to find a way to port its OS to our G2. finally i have found a way, or at least now the space in which to put it. now will begin the porting phase. hence this thread, I bring you this solution to our space issue cause really is 1.3GB for G2 or 1GB for DZ partition for data really needed???
So here is what I did...
1. First I got android sdk all setup
2. Then I downloaded the android kitchen
3. Also downloaded the Elitemod Rom from nik3r's thread and set it up in the android kitchen
4. In the android kitchen I extracted the kernel and ramdisk from the boot.img
5. I editted all the init files in the BOOT-EXTRACTED/boot.img-ramdisk directory and changed the mount section of the init.rc to
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 /dev/block/mmcblk0p26 /system
mount yaffs2 /dev/block/mmcblk0p26 /system ro remount
mount yaffs2 /dev/block/mmcblk0p25 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
and the init.vision.rc mounts i also swapped
on early-fs
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
mount ext4 /dev/block/mmcblk0p26 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 /dev/block/mmcblk0p25 /data wait noatime nosuid nodev barrier=1 noauto_da_alloc
mount ext4 /dev/block/mmcblk0p27 /cache wait noatime nosuid nodev barrier=1
mount ext4 /dev/block/mmcblk0p28 /devlog wait noatime nosuid nodev barrier=1
6. now in order for it to boot right i had to get the files to go to the right place so i editted the updater-script and changed the mount for system to /dev/block/mmcblk0p26 (which as you know is the normal data partition) and the data mount to /dev/block/mmcblk0p25( normally system) now the files are going to places we want and the init files on boot remount the system on 0p26 and data on 0p25 (in reverse from normal) but it boots. so here we go lets get the life put back in this phone now we have the space.
Mad props to nik3r for his rom and permission to use it
UPDATE: For some reason the wifi got broken but to fix there is the MOD_Elitekernel zip found in the link at the top of this post that will fix that. I also put EdKeys wifi calling as well, have it running now on my phone so let me know if you find anything else.
UPDATE 2: I have put a hacked version of S Voice from the galaxy S3 in the link for the G2 *TO BE USED WITH THIS PROJECT ONLY*.
UPDATE 3: there must be some confusion with this. This is not a new rom with some timeframe to get it working. I have a fully opperational rom with no problems with apps or anything right now. This is about a mod that can be adapted to any rom or as brought up gapps which will be uploaded here tomorrow. My point is that any rom should be able to be altered this way.
So this means you're giving us Nature UX in the near future? Good luck :good: also does this open up multi booting possibilities (proper multi booting, not anything like Boot Manager)? 'Cause that'd be awesome, but would there need to be a special kernel?
WOW, Congrats man! Looking forward to this! As if the G2 will ever die! Pffft! And Kudos To nik3r for all his work towards this community!
BUT COME BACKKKKKK nik3r, we miss you!!
HTCDreamOn said:
So this means you're giving us Nature UX in the near future? Good luck :good: also does this open up multi booting possibilities (proper multi booting, not anything like Boot Manager)? 'Cause that'd be awesome, but would there need to be a special kernel?
Click to expand...
Click to collapse
working on one of those... not sure what it would take for multiboot... could look into it once my main task is done -> SGS3 to G2
So, this would allow me to install more apps and less moving apps to sd card? Noob question, but I really do not know the answer.
Sent from my HTC Vision using xda app-developers app
Less apps, lager rom, kinda like custom mtd partions for older devices. Probably would need to have an ext partition to hold apps if you need a lot... gotta say I've been waiting for something like this!
Sent from my HTC Vision using xda premium
So all roms need to be modefied in order to get this to work? I can go back to my previous rom without problems cause partitions are only mounted in different order by this rom? Just to be shure...
And multitasking wil benefit a lot of this?
Yes, the updater script just writes system to the data partition and since the init files are in the boot.img.they mount the "data" partition as /system and "system" partition as /data. Minor alterations to any rom would take advantage of this work around. And yes you can swap back and forth between a bacckup and this or any other altered rom but just remember in recovery(for now) formating system clears data and factory reset (clearing data) deletes the rom.
ineedone said:
So all roms need to be modefied in order to get this to work? I can go back to my previous rom without problems cause partitions are only mounted in different order by this rom? Just to be shure...
And multitasking wil benefit a lot of this?
Click to expand...
Click to collapse
Oke i wiped all partitions with 4ext, installed rom, rebooted, but now it hangs on bootlogo?
It does take a min to boot... remember there's no cache. What does logcat say????
ineedone said:
Oke i wiped all partitions with 4ext, installed rom, rebooted, but now it hangs on bootlogo?
Click to expand...
Click to collapse
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
ineedone said:
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
Click to expand...
Click to collapse
Did you do changes in ramdisk?
Sent from my HTC Vision using xda app-developers app
EnZl said:
Did you do changes in ramdisk?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
as i stated in the OP... yes i did change the mounting in the init.rc and init.vision.rc in the ramdisk. once the updater script sends the info tho the partitions i needed to edit those to make it boot with it making /dev/block/mmcblk0p26(originally data) the system mount. same for data mount is now the 0p25 partition
ineedone said:
I really mean the htc bootlogo. I can boot into recovery and when i take a look at the partition table, i see systeem is still 549 and there is a 500mb swap partition.. have no knowledge of logcat but i can try and see later tonight when I'm home.
Edit: data partition is now 549
Click to expand...
Click to collapse
Oke forget this post, I had the wrong partition info, and forgot about the 500mb swap on my sd because i don't use it, sorry
This is the partition table after installing this rom:
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 539.3MiB
data ext4 1.0GiB 792.8MiB
cache ext4 295.3MiB 290.5MiB
sdcard fat32 28.7GiB 12.8GiB
sd-ext ext4 129MiB 108.9MiB
swap swap 513MiB -
Current Rom: unknown
There are some errors in the recover.log of 4ext touch recovery, which i included. Maybe someone can help me out
ineedone said:
Oke forget this post, I had the wrong partition info, and forgot about the 500mb swap on my sd because i don't use it, sorry
This is the partition table after installing this rom:
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 539.3MiB
data ext4 1.0GiB 792.8MiB
cache ext4 295.3MiB 290.5MiB
sdcard fat32 28.7GiB 12.8GiB
sd-ext ext4 129MiB 108.9MiB
swap swap 513MiB -
Current Rom: unknown
There are some errors in the recover.log of 4ext touch recovery, which i included. Maybe someone can help me out
Click to expand...
Click to collapse
you have to remember that recoveries still look to the 0p25 as system but i have a way to show you if it is installing right.
reboot into recovery
plug phone into usb and usb into computer - make sure adb works... type in a terminal or command prompt "adb shell" and hit enter
you should be in an android shell... you should see this ~ #
then type df and hit enter - this will show the partitions and how they are mounted
select to install the rom and as soon as it starts press the up arrow and hit enter (if the up arrow does not bring up the df command just type it)
do this repeatedly and you will watch as the rom is installed, the space on and which partition is what.
let me know
ok so an update I have gotten Flinny's latest 10.1 to work also but I will not put it out until/ if I get his permission to do so
[/SIZE]
OdiemanSAM said:
you have to remember that recoveries still look to the 0p25 as system but i have a way to show you if it is installing right.
reboot into recovery
plug phone into usb and usb into computer - make sure adb works... type in a terminal or command prompt "adb shell" and hit enter
you should be in an android shell... you should see this ~ #
then type df and hit enter - this will show the partitions and how they are mounted
select to install the rom and as soon as it starts press the up arrow and hit enter (if the up arrow does not bring up the df command just type it)
do this repeatedly and you will watch as the rom is installed, the space on and which partition is what
Click to expand...
Click to collapse
Here is the output:
Partitions seem to change and i lose 500MB some how
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk0p25
1099608 18840 1080768 2% /system
/dev/block/mmcblk0p26
1099608 18840 1080768 2% /data
/dev/block/mmcblk1p2 127936 16404 111532 13% /sd-ext
/dev/block/mmcblk1p1 30102144 16812160 13289984 56% /sdcard
/dev/block/mmcblk0p26
562384 10216 552168 2% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk0p25
562384 10216 552168 2% /system
/dev/block/mmcblk0p26
562384 10216 552168 2% /data
/dev/block/mmcblk1p2 127936 16404 111532 13% /sd-ext
/dev/block/mmcblk1p1 30102144 16815296 13286848 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # df
also from previous recovery.log:
About to install:
EM1-1.zip
Continue install?
-- Installing: /sdcard/Download/EM1-1.zip
Finding update package...
I:Update location: /sdcard/Download/EM1-1.zip
Opening update package...
Installing update...
package_extract_file: no system/bin/backuptool.sh in package
set_perm: chown of /tmp/backuptool.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backuptool.sh to 777 failed: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
Creating filesystem with parameters:
Size: 1143992320
Block size: 4096
Blocks per group: 32768
Inodes per group: 7760
Inode size: 256
Journal blocks: 4363
Label:
Blocks: 279295
Block groups: 9
Reserved block group size: 71
Created filesystem with 11/69840 inodes and 9114/279295 blocks
warning: wipe_block_device: Discard failed
Initiating EliteMod ICS 120728
================================
Designed for HTC Desire Z/G2
Applying AOKP m6 and gapps...
minzip: Extracted file "/...........................................
.....................................................snip
minzip: Extracted file "/system/xbin/su"
package_extract_file: no system/bin/backuptool.sh in package
set_perm: chown of /tmp/backuptool.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/backuptool.sh to 777 failed: No such file or directory
about to run program [/tmp/backuptool.sh] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
package_extract_file: no system/bin/modelid_cfg.sh in package
set_perm: chown of /tmp/modelid_cfg.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/modelid_cfg.sh to 777 failed: No such file or directory
about to run program [/tmp/modelid_cfg.sh] with 2 args
run_program: execv failed: No such file or directory..............................................
.......................
minzip: Extracted file "/data/local/postsetup/undervolt.txt"
Applying EliteKernel 120728...
set_perm: chown of /system/etc/init.d/04mountsddl to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/04mountsddl to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/11apps2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/11apps2sd to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/61swap2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/61swap2sd to 775 failed: No such file or directory
set_perm: chown of /system/etc/init.d/64swapmarker to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/64swapmarker to 775 failed: No such file or directory
set_perm: chown of /system/xbin/virtuous_oc to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/virtuous_oc to 775 failed: No such file or directory
about to run program [/sbin/busybox] with 3 args
minzip: Extracted file "/tmp/dump_image"
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/mkbootimg.sh"
Extracting Kernel files...
minzip: Extracted file "/tmp/unpackbootimg"
minzip: Extracted file "/tmp/zImage"
Installing kernel...
about to run program [/tmp/dump_image] with 3 args
about to run program [/tmp/unpackbootimg] with 3 args
BOARD_KERNEL_CMDLINE no_console_suspend=1
BOARD_KERNEL_BASE 4000000
about to run program [/tmp/mkbootimg.sh] with 1 args
minzip: Extracted file "/tmp/vision_wipe_efs"
about to run program [/tmp/vision_wipe_efs] with 1 args
Backing up partition /dev/block/mmcblk0p13 to /sdcard/part13backup-1358877146.bin ...
Backing up partition /dev/block/mmcblk0p14 to /sdcard/part14backup-1358877146.bin ...
Wiping partition /dev/block/mmcblk0p13...
Wiping partition /dev/block/mmcblk0p14...
Successfully wiped partitions 13 and 14.script result was []
EliteMod ICS installed successfully!
Credits to all the amazing devs that made this possible! Thank You!
Install from sdcard complete.
..................................................................
it also seems like only some files get written to data partition around 200mb, nothing to system...
you have dual mounts!!!! system and data are both mounted to both partitions. go into mounts windows in recovery and unmount both system and data partitions... then try again.
OdiemanSAM said:
you have dual mounts!!!! system and data are both mounted to both partitions. go into mounts windows in recovery and unmount both system and data partitions... then try again.[/QUOTE
mounted them last time because they didn't show up in fist instance :silly:
output:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 31892 1067716 3% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 136220 963388 12% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 288248 811360 26% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16827968 13274176 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # dfFilesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 31892 1067716 3% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 136220 963388 12% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16824752 13277392 56% /sdcard
/dev/block/mmcblk0p26
1099608 288248 811360 26% /system
~ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 188504 32 188472 0% /dev
/dev/block/mmcblk0p27
302356 4804 297552 2% /cache
/dev/block/mmcblk1p1 30102144 16827968 13274176 56% /sdcard
/dev/block/mmcblk0p25
562384 10216 552168 2% /data
~ # df
Click to expand...
Click to collapse
so is it working for you now???
UPDATED OP
Sorry , still on htc bootlogo
Only files seems to be written to data
Is there a way to view if/what data is written to the different partitions or boot ? Or do i need to install aditional gapps?
I am getting the following error while checking the internal memory of my phone. Any help will be highly appreciated
C:\android-sdk-windows\sdk\platform-tools>adb shell
~ # cat etc/fstab
cat etc/fstab
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw
~ # e2fsck -fv dev/block/mmcblk0p01
e2fsck -fv dev/block/mmcblk0p01
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open dev/block/mmcblk0p01
Possibly non-existent device?
~ # e2fsck -fv dev/block/mmcblk0p
e2fsck -fv dev/block/mmcblk0p
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open dev/block/mmcblk0p
Possibly non-existent device?
~ # cat etc/fstab
cat etc/fstab
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw
~ # e2fsck /dev/block/mmcblk0p2
e2fsck /dev/block/mmcblk0p2
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I'm trying to follow this post: https://forum.xda-developers.com/showpost.php?p=59166089&postcount=124 to try to get link2sd up and running, I've followed the instructions until I encountered an issue:
mount -t ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
Click to expand...
Click to collapse
The device's name is valid, I've even tried umounting the usb drive in /storage, but it still gives me that error. Have I missed something? The post is quite old and some things might have changed since then.
/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb
Child's Play said:
/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb
Click to expand...
Click to collapse
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.
dictorclef said:
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.
Click to expand...
Click to collapse
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.
dcarvil said:
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.
Click to expand...
Click to collapse
they do
ls -l /dev/block/sda1
brw------- 1 root root 8, 1 1969-12-31 19:00 /dev/block/sda1
ls -l /storage/usb
total 0
Click to expand...
Click to collapse
Should have tried this already:
/system/bin/mount -vt ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
try '/dev/block/sda1' type 'ext4' on '/storage/usb'
Click to expand...
Click to collapse
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981
dictorclef said:
Should have tried this already:
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981
Click to expand...
Click to collapse
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.
dcarvil said:
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.
Click to expand...
Click to collapse
Device does have ext4 support:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev configfs
nodev debugfs
nodev tracefs
nodev sockfs
nodev pipefs
nodev devpts
ext3
ext2
ext4
vfat
msdos
iso9660
fuseblk
nodev fuse
nodev fusectl
nodev selinuxfs
nodev functionfs
Click to expand...
Click to collapse
And I did try to format the drive using aparted on my firestick, still no luck.
I think I might actually be an idiot, /dev/block/sda1 was already mounted to /mnt/media_rw/[a bunch of numbers and letters]. Unmounted it and it will now mount where I want. Link2sd detects the partition just fine.
Hey
I'm trying to install LineageOS 17.1 (or actually anything…) on my RM5G. But no matter what I do, it fails. Even directly directly after starting unofficial TWRP 3.4.1b-0324, I get an error message:
Code:
Updating partition details...
Failed to mount '/odm' (Invalid argument)
...done
Is it because of the broken (?) /odm line in /etc/fstab?
Code:
$ adb shell cat /etc/fstab
/dev/block/sda17 /data f2fs rw 0 0
/dev/block/sda10 /cache ext4 rw 0 0
/dev/block/dm-2 /system_root ext4 rw 0 0
/dev/block/dm-1 /vendor ext4 rw 0 0
/dev/block/dm-0 /product ext4 rw 0 0
/odm ext4 rw 0 0
/dev/block/sde4 /firmware vfat rw 0 0
/dev/block/sda2 /persist ext4 rw 0 0
/dev/block/sde5 /bt_firmware vfat rw 0 0
/dev/block/sde9 /dsp ext4 rw 0 0
/dev/block/sda13 /metadata ext4 rw 0 0
/dev/block/sde51 /spunvm vfat rw 0 0
/usb-otg vfat rw 0 0
I get that "Failed to mount '/odm' (Invalid argument)" all the time… Even after deleting /data or after a wipe and so also when trying to install a ROM.
I'm also attaching my "recovery.log" after I tried to install LineageOS.
Thx.
I get the failed to mount /odm but everything still flashes. I'm on Pixel Experience Plus ROM right now.
same here
i got the same error on RM5S for installing resurrection remix. It is not working. Anyone know what to do?
i fixed, i don't know how but i still try to root