Movatterモバイル変換


[0]ホーム

URL:


XDA Forums
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use analternative browser.

[MOD][FEB 10] MultiROM v33

Search This thread
By:

fehhner

New member
May 23, 2017
3
1
I have a problem with Multirom on my Nexus 5. Can't swap primary and secondary ROMs:(
  1. I had simple TWRP recovery & Installed latest LinageOS (w/o kexec-hardbootl patch)
  2. Flashed Multirom TWRP version
  3. Installed Multirom Manager app & Updated Multirom TWRP
  4. Flashed patched kernel in TWRP & Rebooted. In Manager app everything became OK.
  5. Flashed Sailfish (w CM 13.1 base) as secondary ROM.
Everything is installed in internal storage now. When I try to boot, I can choose Linage or Sailfish in boot menu and everything works. I've succesfully renamed menu items in Multirom Manager. But there is no inbuilt ability to swap roms in app. And when I boot into recovery and choose Multirom -> Swap ROMs, I see theempty list "Select Secondary ROM to swap with:" and Linageprimary rom name under the list. If i Choose Multirom -> List ROMs, I can see only Sailfishsecondary ROM in "Tap ROM to manage it" list in v2.8.7. When I've updated to latest v.3.0.0 Multirom TWRP app via the app I still have no success. I press Manage Roms, can see only the secondary rom in the list (Sailfish). If I click on it, I event can't flash ZIP (it was possible flash in 2.8.7). If I press swap, thereis Linage name and empty "Secondary ROM to swap with" menu.

I wan't to normally automatically boot to Sailfish and have Android (Linage) as emergency backup. Is there any possibility to do this, or at least disable automatic boot timer (5s) in the boot menu?
 
Here is a screenshot
 

Attachments

  • Screenshot_2018-01-03-16-59-56.png
    Screenshot_2018-01-03-16-59-56.png
    181 KB · Views: 865
No, it has definitively to do with the twrp version.
We need a multirom twrp version later than 3.2.0.0
https://xdaforums.com/google-nexus-...nlegacy-android-project-t3593425/post75066496
Edit: I modified the flashing script and deleted the device check. Now it flashing correctly, but doesn't boot as a secondary. Hangs at Google logo.
When you flash it without multirom and with latest TWRP, it works as it should.:confused:
 
Last edited:
BIade

BIade

Senior Member
Apr 11, 2013
693
545
Cologne
Can anyone help me. Why can I download Ubuntu touch?
View attachment 4402874

I think the repo changed. Which (exact) version/apk are you using?
You should try Captain Throwback's files. They are posted some posts/pages before - here in this thread.
 
  • Like
Reactions:lakija

drmuruga

Senior Member
Extract rom and go to updater script delete from assert to ui print , the updater script start from ui print now compress and flash in twrp.
 
  • Like
Reactions:physwizz
physwizz

physwizz

Senior Member
Sep 16, 2013
5,273
1,172
Sydney
Extract rom and go to updater script delete from assert to ui print , the updater script start from ui print now compress and flash in twrp.

I might try this with Lineage Oreo.
 
physwizz

physwizz

Senior Member
Sep 16, 2013
5,273
1,172
Sydney
I everyone. Just try to install Dark Rom 7 on the latest MultiROM v33 and Recovery 2016-02-10 (0) (down&install via PlayStore), but i got this issue:
E1001: Failed to update system image
Updater process ended with ERROR: 7

I read in this thread a post that suggests to try remove a string in the updater-script, i try follow the "instruction" in the post (without pc, i do everything on smartphone), but i got this issue:
Failed to find entry /META-INF/com/google/android/updater-script in ZIP file /sdcard/rom/bla bla bla
Need help, thanks in advice :fingers-crossed:

EDIT: i'm quite a noob, please be patience;)

Try using zarchiver on the android
 

losl1946

Senior Member
Dec 9, 2012
111
16
Vancouver
My Nexus5 (hammerhead) was flashed with Multirom:
Primart rom:
Darkrom (darkrom-15.1-20180416-NIGHTLY-hammerhead.zip" (from a link in "https://xdaforums.com/sho...postcount=6431)
Multirom/TWRP:
multirom-20170314-v33a-UNOFFICIAL-hammerhead.zip/TWRP_3.1.0.0_multirom_hammerhead_20170314-03.img both from CaptainThrowback.
Since i could not find the suitable patched kernel or the kexec-hardboot patch i enabled the "No Kexec Workaround" in TWRP.
The primary rom works perfectly OK. Then i flashed "lineage-14.1-20180531-nightly-hammerhead-signed.zip " (from
https://download.lineageos.org/hammerhead) as the secondary rom.The initial boot and setup was no problem at all on the secondary rom. Then I rebooted the primary it also works fine. After that i booted the system back the secondary, problem occurred. The secondary failed to boot, it stuck at the boot animation forever and did nothing. I searched all the keywords but found nothing for Nexus 5. If you have any suggestions please help. Thank you.

SLo
 

kmem

Senior Member
May 23, 2011
234
72
My Nexus5 (hammerhead) was flashed with Multirom:
Primart rom:
Darkrom (darkrom-15.1-20180416-NIGHTLY-hammerhead.zip" (from a link in "https://xdaforums.com/sho...postcount=6431)
Multirom/TWRP:
multirom-20170314-v33a-UNOFFICIAL-hammerhead.zip/TWRP_3.1.0.0_multirom_hammerhead_20170314-03.img both from CaptainThrowback.
Since i could not find the suitable patched kernel or the kexec-hardboot patch i enabled the "No Kexec Workaround" in TWRP.
The primary rom works perfectly OK. Then i flashed "lineage-14.1-20180531-nightly-hammerhead-signed.zip " (fromhttps://download.lineageos.org/hammerhead) as the secondary rom.The initial boot and setup was no problem at all on the secondary rom. Then I rebooted the primary it also works fine. After that i booted the system back the secondary, problem occurred. The secondary failed to boot, it stuck at the boot animation forever and did nothing. I searched all the keywords but found nothing for Nexus 5. If you have any suggestions please help. Thank you.

SLo

In my experience, the workaround is a bit buggy, not to mention it reflashes your nand every time you boot which can't be good for longevity. I suggest you try a patched kernel for your primary. Both common nougat kernels (elementalx and bluspark) are patched. Another issue is that since multirom support is dead and the recovery so generously provided by captain throwback is pretty outdated, many secondary ROMs fail to install or boot.

There is an alternative to multirom which doesn't require patching called efidroid which shows a lot of promise but its development appears to be stalled as well. One should note that efidroid's interface is not touch based and requires the use of the hammerhead's aging physical buttons to function.

Hope this helps.
 

losl1946

Senior Member
Dec 9, 2012
111
16
Vancouver
In my experience, the workaround is a bit buggy, not to mention it reflashes your nand every time you boot which can't be good for longevity. I suggest you try a patched kernel for your primary. Both common nougat kernels (elementalx and bluspark) are patched. Another issue is that since multirom support is dead and the recovery so generously provided by captain throwback is pretty outdated, many secondary ROMs fail to install or boot.

There is an alternative to multirom which doesn't require patching called efidroid which shows a lot of promise but its development appears to be stalled as well. One should note that efidroid's interface is not touch based and requires the use of the hammerhead's aging physical buttons to function.

Hope this helps.

Thank you very much.
In my previous multirom setup. My primary rom was Darkrom 14.1 android 7.1.2 (darkrom-14.1-20171102-NIGHTLY-hammerhead.zip) with blu_spark Kernel (blu_sparkKernel_Kernel_r140_hammerhead_ce06f36.zip). It worked without any problem for months. Now i upgrade to Android 8.1 (Darkrom 15.1) and the blu-spark kernel stopped working and I could not find kernels good for Nexus5/ Android 8.1 /Multirom/Darkrom 8.1. So i opted for "No-Kexec workaround". It seems that i have to abandon Multirom on Nexus 5.
Any further advice is welcome, thank you.

Have a nice day.

SLo
 

kmem

Senior Member
May 23, 2011
234
72
Thank you very much.
In my previous multirom setup. My primary rom was Darkrom 14.1 android 7.1.2 (darkrom-14.1-20171102-NIGHTLY-hammerhead.zip) with blu_spark Kernel (blu_sparkKernel_Kernel_r140_hammerhead_ce06f36.zip). It worked without any problem for months. Now i upgrade to Android 8.1 (Darkrom 15.1) and the blu-spark kernel stopped working and I could not find kernels good for Nexus5/ Android 8.1 /Multirom/Darkrom 8.1. So i opted for "No-Kexec workaround". It seems that i have to abandon Multirom on Nexus 5.
Any further advice is welcome, thank you.

Have a nice day.

SLo
I too used darkROM Nougat for a long time with multiROM. You need an Oreo kernel to work with 15.x. I dont think Bluspark has an Oreo kernel but I could be mistaken. You could try ElementalX 9.02. It has the kexec patch. I don't know if it works with darkROM Oreo but it seems to work fine with AEX Oreo as a primary. Getting other Oreo ROMs to work as secondaries won't be easy though!

For what it's worth I am still using multiROM but it seems kind of silly since so few new ROMs work with it.
 
  • Like
Reactions:losl1946
Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
6,804
8,918
Google Nexus 5
Huawei Nexus 6P
hello i have a serious question, so if i have 2 roms, and root and also flash xposed on my primary does that mean that my second rom will automatically have xposed aswell or is it up to me to decide whether i want to have it on secondary aswell, because i want to have my primary one with root and xposed but my secondary i want without root or xposed, so is that possible please?

Your secondary rom will only have what you put on it, so yes, you decide.
 
  • Like
Reactions:driton.talinoci

Top Liked Posts

  • There are no posts matching your filters.
  • 425
    vh3puLb.png
    Introduction

    MultiROM is one-of-a-kind multi-boot mod for Nexus 5. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. 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 and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.

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

    You can also watch a video which shows it in action.



    Warning!

    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 or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​



    Installation
    1. Via MultiROM Manager app
    This is the easiest way to install everything MultiROM needs.Install the app and select MultiROM and recovery on theInstall/Update card. If theStatus card saysKernel:doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on theInstall/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM,not any of your (future) secondary ROMs, so select the version accordingly.
    Press "Install" on theInstall/Update card to start the installation.

    2.Manual installation
    Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also anawesome article on Linux Journal.

    MultiROM has 3 parts you need to install:
    • MultiROM (multirom-YYYYMMDD-vXX-hammerhead.zip) - download the ZIP file from second post and flash it in recovery.
    • Modified recovery (TWRP_multirom_hammerhead_YYYYMMDD.img) - download the IMG file from second post and use fastboot orFlashify app to flash it.
    • Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
    You current rom will not be erased by the installation.
    Download links are in the second post.



    Adding ROMs
    1. Android
    Go to recovery, select Advanced -> MultiROM -> 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.​

    2. Ubuntu Touch
    Use theMultiROM Manager app to install Ubuntu Touch.

    Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.

    3. Firefox OS
    Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file fromFirefox OS' thread and add it as if it were Android​

    4. SailfishOS
    • Download CyanogenMod and SailfishOS ZIPas described on Sailfish wiki page.You need alpha2 (20140810) or newer!
    • Put both CM and SailfishZIP on your device.
    • Reboot into recovery
    • Advanced -> MultiROM -> Add ROM
    • Choose "SailfishOS" as ROM type.Installation to USB drive is not supported, so leaveinstall location as is. Click Next.
    • Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
    Head to SailfishOS thread for more info:http://xdaforums.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266



    Using USB drive
    During 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 Advanced -> MultiROM in recovery and doInject 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 Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
    • Select "Flash ZIP" and flash ROM's ZIP file.



    Source code



    Donations
    I'd be glad if you could spare a few bucks. You can use eitherpaypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
    Thanks to all donors, it is much appreciated:)
    169
    Downloads

    1. Main downloads

    MultiROM:multirom-20160207-v33-hammerhead.zip
    Modified recovery (based on TWRP):TWRP_multirom_hammerhead_20160210.img
    MultiROM Manager Android app:Google Play orlink to APK

    Kernel w/ kexec-hardboot patch (Stock 4.4):kernel_kexec_hammerhead_440.zip
    Kernel w/ kexec-hardboot patch (Stock 4.4.1 and 4.4.2):kernel_kexec_hammerhead_441.zip
    Kernel w/ kexec-hardboot patch (Stock 4.4.3 and 4.4.4):kernel_kexec_hammerhead_443.zip
    Kernel w/ kexec-hardboot patch (Stock L preview):kernel_kexec_hammerhead_L.zip
    Kernel w/ kexec-hardboot patch (Stock 5.0 preview (LPX13D)):kernel_kexec_hammerhead_50_lpx13d.zip
    Kernel w/ kexec-hardboot patch (Stock 5.0 and 5.0.1):kernel_kexec_hammerhead_50_final.zip
    Kernel w/ kexec-hardboot patch (Stock 5.1):kernel_kexec_hammerhead_510.zip
    Kernel w/ kexec-hardboot patch (Stock 5.1.1):kernel_kexec_hammerhead_511-2.zip
    Kernel w/ kexec-hardboot patch (Stock 6.0 and 6.0.1):kernel_kexec_hammerhead_601.zip
    Kernel w/ kexec-hardboot patch (CM 11 (4.4 - 4.4.2)):kernel_kexec_hammerhead_cm11-9-3d91a2d569.zip
    Kernel w/ kexec-hardboot patch (CM 11 (4.4.3 - 4.4.4)):kernel_kexec_hammerhead_cm11-12-7d4eef09ee.zip
    Kernel w/ kexec-hardboot patch (CM 12.0):kernel_kexec_hammerhead_cm12-1-10f4294a6b.zip
    Kernel w/ kexec-hardboot patch (CM 12.1):kernel_kexec_hammerhead_cm121-01-47b35a93b8.zip
    Kernel w/ kexec-hardboot patch (CM 13.0):kernel_kexec_hammerhead_cm13-01-2c39db662.zip
    You need to have kernel with kexec-hardboot patch only in your primary ROM!

    Mirror:http://d-h.st/users/tassadar

    2. third-party kernels with kexec-hardboot patch
    franco.Kernel (r21 and newer) -http://xdaforums.com/showthread.php?t=2508284
    Chaos -http://xdaforums.com/showthread.php?t=2551441
    ElementalX -http://xdaforums.com/showthread.php?t=2519607

    Nicely ask your kernel developer to mergekexec-hardboot patch.​

    3. Uninstaller

    MultiROM uninstaller:multirom_uninstaller-hammerhead-2.zip
    Flash this ZIP file to remove MultiROM from your device.It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flashclean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.

    4. Flashable factory images ZIPs
    I usually release flashable ZIP files based on new factory images from Google, so that you can have clean stock ROM as a secondary system in MultiROM. They are not rooted, no anything, except for occasional small tweaks to make rooting with SuperSU possible. You can find them in this folderon basketbuild ordev-host.


    Changelog
    Code:
    MultiROM v33=====================* Updates for Android 6.0 compatibilityMultiROM v32c=====================* Add support for Android M preview (MPZ44Q). SuperSU 2.46 doesn't work on M  and breaks boot - don't flash it!MultiROM v32b=====================* Fix pattern encryption password incorrectly reporting "invalid password"  when the pattern overlaps itselfMultiROM v32a=====================* Fix support for separate radio.img with secondary kitkat ROMsMultiROM v32=====================* Minor GUI improvements* Support for device encryption (with Android-based secondary ROMs only, for  AOSP encryption only - does not work with CAF-based CyanogenMod as primary  ROM). See FAQ in this device's XDA thread for more info.* Bunch of ROM compatibility fixesMultiROM v31=====================* Add support for "multimount" fstabs* Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.  the L icon)MultiROM v30=====================* Fix logs generated by the "emergency reboot" screen, they were incompleteMultiROM v29=====================* Implement "autoboot if no key pressed" mode - the boot manager won't show up  unless you hold down a volume down button during boot. Must be enabled in  recovery.* Android 5.0 preview related tweaksMultiROM v28=====================* You can now swipe between the tabs in the boot manager* Minor UI adjustmentsMultiROM v27a=====================* Fix freezes in the boot manager* Add support for SailfishOSMultiROM v27=====================* Redesign the boot manager GUI. Looks much better now.* Fix separate radio.img not working on Android L preview ROMs* Fix issues with unaccessible /sdcard on Android L preview. Do NOT run  restorecon manually on /data/media, ever - it breaks MultiROM!* Workaround bug which caused franco.Kernel on N5 to break secondary ROM's  boot* Update Ubuntu Touch init scripts* Use power+volume down (you have to press power first!) to save screenshots.  They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.MultiROM v26=====================* Fix boot into secondary ROM from the MultiROM Manager app broken in v25MultiROM v25=====================* Add support for the Android L previewMultiROM v24=====================* Add F2FS support* Show icons in ROM list, configurable via MultiROM Manager app* Improve compatibility with different ROMs and kernels when booting a ROM  from the Android appMultiROM v23=====================* Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu  installation won't boot, go to recovery and use "Re-patch init" option in  Advanced -> MultiROM -> List ROMs -> *ubuntu*.MultiROM v22c=====================* Fix graphics corruption with some custom kernelsMultiROM v22b=====================* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,  enabling sharing data between Android and Ubuntu Touch. See  [url]http://bit.ly/ut_sharing[/url] for more info.MultiROM v22a=====================* Add support for ROMs with DTB only as separate blob in boot.img (AOKP)MultiROM v22=====================* Fix Ubuntu Touch boot taking long time* Fix Ubuntu Touch freezing on Google logo for some usersMultiROM v21a=====================* Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)MultiROM v21=====================* Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU  breaks the boot.MultiROM v20=====================* Support booting ROMs directly from Manager App* Fix FCs on CyanogenMod-based ROMs* Fix support for USB drives formatted with NTFS, broken in v17* Mount /system in secondary ROMs read-onlyMultiROM v19=====================* Initial version


    Recoveries:
    Code:
    10.2.2016=====================* Fix ZIP selector being set to wrong storage after flashing ZIP to a  secondary ROM9.2.2016=====================* Update to TWRP 3.0.0 (big thanks to nkk71 for doing most of the work)* Use Material theme made by z31s1g - thanks!* Fixes for 6.0 compatibility* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (  [url]http://bit.ly/m_su[/url] ) or newer!30.6.2015=====================* Update to TWRP 2.8.7* Add option to duplicate secondary ROM into "Swap ROMs" section10.4.2015=====================* Fix Ubuntu Touch installation broken in previous update6.4.2015=====================* Fix support for SuperSU 2.47 Beta and higher28.3.2015=====================* Update to TWRP 2.8.6* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),  should be used to fix broken SELinux contexts, which can be causing  bootloops of secondary ROMs* Bunch of ROM compatibility fixes - recovery now uses entirely new way to  inject ZIP installation files, which should be much more robust and reliable* Big ZIPs (> 450MB) are no longer permanently modified when flashed as  secondary ROMs* Fix sideloading of big ZIP files (> 450MB) into secondary ROMs12.2.2015=====================* Update to TWRP 2.8.5* Fix support for ROMs containing a supersu.zip in their installation file  (e.g. AICP)15.1.2015=====================* Fix "Swap ROMs" feature after the last update14.1.2015=====================* Update to TWRP 2.8.4* Lots of ZIP compatibility fixes (e.g. for CM 12)15.11.2014=====================* Support for ZIP files which are using the new 'block_image_update' command  (e.g. SimpleAOSP ROM)29.10.2014=====================* Update to TWRP 2.8.121.10.2014=====================* Update autoboot settings for MultiROM v2914.9.2014=====================* Update with changes from 2.8.0.1 upstream version: fix a bug that causes  weird graphics glitches and touch issues11.9.2014=====================* Update to TWRP 2.8.0* Fix adding ROMs from backup to a FAT32 USB drives* Remove "share kernel with internal?" from "Add ROM" page, there is usually  no reason to use it anymore and it might be confusing to figure out what it  actually does. You can still get the same behavior by clicking "Remove  boot.img" on the List ROMs -> *rom name* page.12.8.2014 - 1=====================* Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous  version11.8.2014=====================* Remove Ubuntu Touch installation, installing via recovery is deprecated* Add SailfishOS installation8.8.2014=====================* Show secondary ROM's name in the title bar while executing it's script (e.g.  during OTA update)* Update Ubuntu Touch updater* Fix failure to swap ROMs if it contains filenames starting with a dot* Fix add ROM from a backup producing unbootable ROM with Android L preview* Add option to remove radio.img from secondary ROMs* Add config options for MultiROM v275.6.2014=====================* Update to TWRP 2.7.1* Hide misleading "Mount: Unable to find partition for path '/data'" message  which appeared during secondary ROM installation, it is not _actually_ an  error.4.6.2014=====================* Fix installation of bigger (>350MB) ZIPs as secondary ROMs12.5.2014=====================* Fix crash during settings loading, causing a bootloop with certain settings11.5.2014=====================* Add F2FS support* Add tool to switch F2FS<->ext4 to Advanced menu* Fix problems with backups introduced by TWRP 2.7.08.3.2014=====================* Update to TWRP 2.7.0* Remove "save" button from MultiROM settings page, it is saved automatically  now27.2.2014=====================* Support for system-image based (from the Manager app) Ubuntu Touch  installation* Fix time in recovery* Some rendering optimizations, resulting in noticeably higher FPS in recovery4.2.2014=====================* Update to support latest Ubuntu Touch testing builds* Fix date and time in recovery* Add support for mice connected via USB-OTG* Fixup scrollbar behaviour in file list26.1.2014=====================* Fix radio in Ubuntu Touch24.12.2013=====================* Fix installing ROMs to USB drive* Fix ZIP verification* Support ZIP verification for secondary ROMs15.12.2013=====================* Initial hammerhead release
    110
    FAQ and other notes
    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, onsecondary 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.

    Can I have different versions of Android working alongside
    Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.​

    MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
    It is, it just shows wrong version.​

    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.


    Will you port MultiROM to device X?
    No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of timefor free into it, and then I can't even see it running on the device, so...why..bother..?
    I'llprobably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
    But, you can port it yourself, the wiki should give you at least some idea how to do that:https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
    87
    MultiROM v25 adds support for the Android L preview. I've also made flashable ZIP images which you can use to flash the preview as secondary ROM to MultiROM. These are also slightly modified to fix SuperSU - you still have to flash it separately (the zip is not pre-rooted), but it will work. You also needSuperSU 2.00. Also, the first boot takes ages because ART.

    The Android L preview is not as smooth as current stable 4.4.4. I'm not sure if it is because it is preview or because MultiROM is messing up something - can somebody who installed it without MultiROM confirm or deny that? Thanks.

    The MultiROM Manager android app doesn't work on the L preview because of the SELinux changes - I know about it and will fix it...soon.

    MultiROM v25:http://tasemnice.eu/multirom/multirom-20140627-v25-hammerhead.zip
    Flashable ZIP with Android L (LPV79):https://mega.co.nz/#!ZgU1EQBI!czQcw5k_eHWfq7ylEFCivdRNTnRceSX_gM1yjNh1AFM

    GoddammitbothdevhostandgooimarenotworkingsoIhavetousemega.
    56
    The L image was released. I'm working on it, if anybody else releases ZIP first,DO NOT FLASH IT TO MULTIROM, booting it will break stuff. Link this post to anybody who seems like he wants to flash the L to multirom.

[8]ページ先頭

©2009-2025 Movatter.jp