[One (M7) Original Android Development] nkk71:
FAQ and other notes

HTC One M7 - Peculiarities / Bugs

You need to be on hboot 1.57 or higher for MultiROM menu to show up at boot time... otherwise it will always boot to primary

.

A few notes about F2FS support

: yes the TWRP recovery and MultiROM now do support F2FS,

however

for that to work "properly" you need a kernel that supports both F2FS

and

kexec-hardboot in the primary slot and secondary slots

So let's say you formatted your data partition to f2fs, a kernel in primary such as ElementalX (which doesn't support f2fs) won't work (neither in primary nor secondary) and wouldn't even show the boot menu; and a kernel (such as included in CM12.1) that does support f2fs would show the boot menu, but has no kexec-hardboot support, so you won't be able to boot any secondary ROM.

Also, even if you have a kernel that supports both f2fs and kexec-hardboot, remember that it will break any ROM/kernel that don't support f2fs.

Basically, I recommend sticking with ext4

.

A few notes about enabled adb in MultiROM boot menu

: later, in the meantime, I still recommend having that disabled.

.

A few notes about the sha1 checks in the installer-script

: also later.

.

Something not working, or you need help debugging

Please provide the following information:

a detailed explanation of the problem

.

the recovery.log (found in /tmp/recovery.log or by copying it to the sdcard and then copying it to PC)

.

the link to the thread

and

name of file (+ which version) you are having problems with

.

due to the large size of some of these ROMs, I may not have time to download and test them, so please also upload the updater-script (found in ROM.ZIP under /META-INF/com/google/android/)

Device encryption

Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.

I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.​

About security

In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​

What do the ROMs share?

All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​

How many ROMs can I have?/Where are the ROMs stored?

You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
​

The menu with all the ROMs won't show up during boot, how to fix it?

Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.

The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
​