ROM COOK [MOD][15-NOV-2016] MultiROM 33 + TWRP_3.0.2-6_MultiROM_Edition_2016-11-15 [TestBuild]

Thảo luận trong 'HTC M10' bắt đầu bởi Sơn Hoài Paladin, 27/11/17.

  1. Sơn Hoài Paladin

    Sơn Hoài Paladin Administrator
    Quản Trị Viên

    Tham gia:
    Bài viết:
    Thích đã nhận:

    You use this tool at your own risk!!
    I have tried to put as many safeguards as I can,
    but I cannot be held accountable for any soft-bricks, hard-bricks, loss of data and/or information,
    or anything else going wrong.

    MultiROM is one-of-a-kind multi-boot mod for HTC 10. It can boot any Android ROM. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs

    * Multiboot any number of Android ROMs
    * Restore nandroid backup as secondary ROM
    * Boot from USB drive attached via OTG cable

    It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition (actually the no-kexec workaround is messing with your boot sector), but it is possible that something goes wrong and you will have to flash factory images again.
    Make backups. Always.
    Now seriously: HTC 10 Warnings!
    Beware of Dragons, Goblins, Gremlins and lingering primary_boot.img(RIP)
    Due to lack of kexec-hardboot kernel support, I am messing with your boot partition!

    Since we lack kernels with kexec-hardboot patch, I'm using a workaround to bypass that restriction, and although tested successfully on the HTC One M7, M8, M9, and HTC 10, as well as several other devices I'm not involved with, things can still go wrong, since I'm directly flashing your boot partition.

    I have yet to see any negative effect of that, and version 4 of the no-kexec workaround is much more robust, you should still be aware that I'm "temp-flashing" your real boot partition.

    If you are in doubt, either ask, or avoid it completely; MultiROM has always been a huge hack to begin with, and this is even more of a hack.

    Always have a backup ready. Possibly even RUU! ... I have not had to, I have also not encountered any loss whatsoever, but better be safe!

    Current problems on the HTC 10
    * OTG is untested and unsupported at the moment
    * exFAT partitions are not supported currently
    ^^ those haven't worked for quite a while, so it's not really HTC 10 specific

    Encrypted devices: Your secondary ROMs do not know your device is encrypted, do not (again: do not) try to encrypt your device while booted into a secondary ROM.
    Secure boot (ie require Password/Pattern/PIN on boot): Thanks to @Captain_Throwback who found out, that under certain circumstances (yet to be determined), your primary (possibly secondary as well) may loose the ability unlock your LockScreen using your Password/Pattern/PIN.

    Đăng nhập để thấy được liên kết, and although your password is correct and does decrypt your device, it breaks at the lockscreen for some reason.

    I recommend you disable Password/Pattern/PIN on boot until / IF the issue is resolved, but in case you do find yourself in that situation, please go ahead and follow the instruction posted in the TWRP thread:10. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
    • It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
      • Disable security in Android before making a backup of data.
      • After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone

    2. Manual installation
    MultiROM has 3 parts (well, it should, but in this case it only has 2) you need to install:
    • Modified recovery (TWRP_3.x.x-x_multirom_pme_YYYYDDMM-pp.img) - download the IMG file from second post and use
      • TWRP itself to flash newer TWRP to recovery partition:
        TWRP->Install-> select Images -> TWRP_3.x.x-x_multirom_pme_YYYYDDMM-pp.img -> to Recovery -> Reboot to Recovery
      • "fastboot flash recovery TWRP_3.x.x-x_multirom_pme_YYYYDDMM-pp.img"
        (in download mode, for example)

    • MultiROM ( - download the ZIP file from second post and flash it in the MultiROM Recovery.
      We don't have a patched kernel, so I'm using a workaround.
    You current rom will not be erased by the installation.
    Download links are in the third post.

    Adding ROMs
    1. Android
    Go to recovery, enter the MultiROM section of TWRP (by clicking the icon in to top right corner) -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
    Using USB driveDuring installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
    If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
    If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
    Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
    Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.

    Updating/changing ROMs
    1. Primary ROM (Internal)
    • Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
    • Go to the MultiROM section of TWRP (by clicking the icon in to top right corner) and do Inject curr. boot sector.
    2. Secondary Android ROMs
    If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
    • Go to the MultiROM section of TWRP (by clicking the icon in to top right corner) -> List ROMs and select the ROM you want to update.
    • Select "Flash ZIP" and flash ROM's ZIP file.
    • In some cases, you might need to flash patched kernel - get corresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.

    Explanation of recovery menus
    Main menu
    - Add ROM - add ROM to boot
    - List ROMs - list installed ROMs and manage them
    - Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
    - Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
    - Settings - well, settings.

    Manage ROM
    - Rename, delete - I believe these are obvious
    - Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
    - Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
    - Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.

    Special Thanks
    • @Tasssadar: Original author of MultiROM.
    • @Captain_Throwback: For testing, giving me a hard time, and warning you guys about the secure boot (ie require Password/Pattern/PIN on boot) issue.
    • Đăng nhập để thấy được liên kết: For the fake properties idea.

    Source codeMultiROM - Đăng nhập để thấy được liên kết (branch master)
    Modified TWRP - Đăng nhập để thấy được liên kết (branch master)
    Device files - ....

    Everything is here:
    Đăng nhập để thấy được liên kết
    Đăng nhập để thấy được liên kết

trang này