[MOD][15-NOV-2016] MultiROM 33 + MultiROM_TWRP_3.0.2-0_20161115 [TestBuild]

[nkk71]

Introduction

MultiROM is one-of-a-kind multi-boot mod for Htc One (m7). It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port. 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, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable

​

Warning!

It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. 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 the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/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 the Install/Update card to start the installation.
​

2. Manual installation
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).

MultiROM has 3 parts you need to install:

• MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-m7.zip) - download the ZIP file from second post and flash it in recovery.
  
• Modified recovery (TWRP_multirom_m7_YYYYMMDD.img) - download the IMG file from second post and use
  "fastboot flash recovery TWRP-multirom-20150619-v32e-UNOFFICIAL-m7univ.img"
  
• 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 this is NOT SUPPORTED AS MOST OTHER PORTS, IF YOU CARE TO ADD SUPPORT, PLEASE DO SO. THANK YOU
Use the MultiROM 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.​

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 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 Advanced -> MultiROM -> 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 coresponding 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.​

Source code

MultiROM - https://github.com/Tasssadar/multirom (branch master)
............... - https://github.com/nkk71/multirom/tree/multirom-m7univ (m7-universal branch)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device files - https://github.com/nkk71/twrp-htc-m7univ​

XDA:DevDB Information
MultiROM, Tool/Utility for the HTC One (m7)

Contributors
nkk71, ljjehl, Captain_Throwback, Beta Testers: @mitchst2

Version Information
Status: Stable
Current Stable Version: 33testbuild
Stable Release Date: 2016-11-15

Created 2015-06-19
Last Updated 2016-11-15

 

[nkk71]

Downloads

Current Test Builds

All Current Test Builds can be found on androidfilehost under MultiROM TEST BUILDS

You should be using these, not the ones mentioned below!

Definition of Test Builds: These are stable builds which I have and am using (and testing). They contain the most up to date fixes as mentioned in the changelog under <tba>.

• The main reason I'm calling them "Test Builds", is because they have not gone through extensive testing as what I would usually do for a "release version". I think most people would call them release versions, but I tend to be more conservative.
  .
• The second reason, they get uploaded to AFH instead of directly here, is two fold:
  1. I'm maintaining the M7, M8, M9 and HTC 10 MultiROM versions, and uploading to AFH is easier and faster for me.
  2. Updating the actual threads and posts, is too time consuming every time I want to push an update.

Changelog and NO_KEXEC 4.1 Information can be found in the HTC 10 MultiROM thread.
​

1. Main downloads

MultiROM Main ZIP: multirom-20160409-v33b-UNOFFICIAL-m7univ.zip
MD5: 115172f7823ef1b93126aa845b7bd3fa

Modified recovery (based on TWRP): TWRP_3.0.2-0_multirom_m7univ_20160409-03.img
MD5: 2ba0c67c2ec1522b278a3996b5b4e814


MultiROM Manager Android app: Google Play or link to APK


You need to have kernel with kexec-hardboot patch only in your primary ROM!
Or you can use the no-kexec workaround v2


AndroidFileHost (mirror & old versions): https://www.androidfilehost.com/?w=files&flid=33970
​

2. third-party kernels with kexec-hardboot patch

You need a kernel that supports kexec-hardboot in the primary ROM.
Note that although MultiROM, it's recovery, and app are HTC One M7 universal build - they support M7_U/UL (GSM), M7_WLS (Sprint) and M7_WLV) - you need to make sure the kernel you choose/select is for your particular device!!

Some examples for M7_U/UL kernels:
ElementalX - http://forum.xda-developers.com/showthread.php?t=2249774
teaMSeven - http://forum.xda-developers.com/showthread.php?t=2307371
Make sure to flash the proper version for your Android and HTC Sense or GPE version.

More kernels here: http://forum.xda-developers.com/htc-one/#kernels
Make sure the the features of your kernel include "kexec-hardboot (for multirom support)"​

3. Uninstaller

MultiROM uninstaller: multirom_uninstaller-20160409-v33b-UNOFFICIAL-m7univ.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-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
​

Changelog

MultiROM v33b
=====================
* Updates for Android 6.0 compatibility
* New kernel logging + history (needs to be enabled in TWRP)
* Added no kexec-hardboot workaround version 2
  (needs to be enabled in TWRP)

MultiROM v32g
=====================
* F2FS support (requires kernel that supports F2FS)
  [I]please check the FAQs about more info[/I]
* fix MTP not working in primary ROM when
  adb is enabled in MultiROM recovery settings
[I]  Note: I still recommend you keep this disabled
        as different kernels react differently to the
        workaround.[/I]

MultiROM v32f
=====================
* minor changes in updater script

MultiROM v32e
=====================
* initial port of v32 to HTC One M7
[B]* Note: encryption not supported at this time[/B]


[SIZE="1"][U]Previous chagelogs from Tasssadar and domicq[/U][/SIZE]
[I][U]Changelog from Tasssadar[/U][/I]
MultiROM v32a
=====================
* Fix pattern encryption password incorrectly reporting "invalid password"
  when the pattern overlaps itself

MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
  FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes

MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* 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 incomplete


[I][U]Previous changelog from domiq [URL="http://forum.xda-developers.com/htc-one/orig-development/mod-multirom-v28-redesigned-gui-t2880887"]here[/URL][/U][/I]
MultiROM 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.
* Sense-based ROMs (hopefully) with working storage
* Android 5.0 preview related tweaks

MultiROM v28b
=====================
* Now working Sense-based ROM as secondary.

MultiROM v28a
=====================
* Some edits in device files

MultiROM v28
=====================
* Fix freezes in the boot manager
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
* SailfishOS support (for certain devices)

MultiROM 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 v25

MultiROM v25
=====================
* Add support for the Android L preview
* Misc F2FS fixes

MultiROM 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 app

MultiROM 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 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
=====================
* Fix hardware keys not working for some users
* Update Ubuntu Touch patches

MultiROM v22
=====================
* Fix linux-type ROMs (Ubuntu Touch) failing to boot for some users

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-only

MultiROM v19
=====================
* Implement "boot the last ROM" auto-boot type

MultiROM v18
=====================
* Fix silent-but-unpleasant crash with exFAT

MultiROM v17
=====================
* Changes to support MultiROM Manager app
* Add support for exFAT

MultiROM v16a
=====================
* Fix kexec not working on some kernels

MultiROM v16
=====================
* Add overscroll bounceback effect to rom list
* Add support for controling via physical keys
* Bunch of under-the-hood changes for mako and m7 support

MultiROM v15
=====================
* Fix cmdline handling for kexec, doesn't change anything for grouper, just to
  have the same version for both flo and grouper (no need to update)

MultiROM v14
=====================
* Find and change correct fstab (fixes freezes on boot)
* Mount /realdata without nosuid (fixes no root on 4.1 and 4.2 ROMs)
* Use libbootimg to work with boot.img files

MultiROM v13
=====================
* Partial rewrite of the codebase to make it compatible with multiple devices 
* Add run-on-boot scripts (for advanced users who know linux and bash, see
  [url]https://github.com/Tasssadar/multirom/wiki/run-on-boot-scripts[/url])
* Use libbootimg to work with boot.img files

MultiROM v12a
=====================
* Detect kexec-hardboot patch in kernel even if /proc/config.gz is not
  available

MultiROM v12
=====================
* Implement screen rotation and 1280x800 theme
* Fix auto-boot option
* Fix listview's fast scrollbar behavior

MultiROM v11
=====================
* Option to hide Internal ROM
* Option to rename Internal ROM
* Support for Ubuntu Touch

MultiROM v10
=====================
* Non-error message boxes aren't red now
* Add possibility to switch between several color themes, go to misc tab and
  try it out
* New MultiROM installer format
* Add "discard" option to /data mounting
* Add battery status to misc tab (bottom right corner)
* Add brightness setting
* Implement ADB

MultiROM v9
=====================
* Make it compatible with LZ4 ramdisk compression
* Improve touch-related code. You should not get anymore phantom button
  presses nor listview freezes

MultiROM v8
=====================
* Fix kexec-hardboot with new bootloader v4.18
* Search for already present USB drives on start
* Centre "MultiROM" title in main UI

MultiROM v7
=====================
* Correctly boot Ubuntu after recent kernel update. Read this post:
  [url]http://forum.xda-developers.com/showpost.php?p=37389003&postcount=1031[/url]
* Remove specific support for Ubuntu - it is now handled as "generic linux"
  (with rom_info.txt file). Nothing should change for the users
* Sort ROMs alphabetically
* Add "progress dots" to USB screen, so that user knows that it is doing
  something
* Recovery was also updated, don't forget to flash it

MultiROM v6
=====================
* Properly check for kexec-hardboot patch in kernel
* Internal" is always first in ROM list now, as originally intended
* Much more logging for kexec-related stuff
* Print last 50 lines of klog to "Emergency reboot" screen

MultiROM v5-2
=====================
* Fix ubuntu
* MultiROM still says it's v5. I did not change the version number because it
  is literally one character fix.

MultiROM v5
=====================
* Support for ROMs with configuration file. This makes porting
  Ubuntu/plasma/webos/anything much more easier. See the third post.
* MultiROM will no longer let you boot Ubuntu ROM if it's name contains
  spaces, because the boot would fail.

MultiROM v4
=====================
* Fix GPS on ROMs other than Internal
* Minor UI changes

MultiROM v3
=====================
* Switch to Ubuntu 13.04. Version 12.10 is no longer supported
* Switch to kexec-hardboot based multi-booting. Read the first post.
* Add support for booting from USB drive
* MediaScanner no longer scans /sdcard/multirom, which means no useless
  battery drain
* Recovery was updated, make sure to flash it, too.

MultiROM v2
=====================
* Add support for Ubuntu on 3G version of Nexus 7
* Fix some issues with 4.2 ROMs
* Recovery was updated, make sure to flash it, too.

MultiROM v1
=====================
* Initial version

Recoveries:

09.04.2016 (2016-04-09)
=====================
* Rebase to TWRP 3.0.2
* Use new stock theme made by z31s1g - thanks!!!
* New partition selector
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
  secondary ROM
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
  [URL="http://bit.ly/m_su"]http://bit.ly/m_su[/URL] ) or newer!
* Fixes for several installer scripts using non-conventional methods
  when installing systemless root
* Fix inject multriom checkmark not showing on startup
* New option to enable kernel logging + history for multirom
* New advanced options for no kexec-hardboot workaround version 2
  [I](yes the Info page is missing)[/I]
* Add progress tracking in multirom 'restore' install

16.11.2015
=====================
* fixed MTP upon entering recovery
* fixed USB-OTG not working properly
* add support for installer-scripts with sha1 checks
  (such as CM13 and other Marshmallow builds)
  to be flashed directly to secondary
  [I]please check the FAQs about more info[/I]

06.08.2015
=====================
* fixed Restorecon command in MultiROM

04.07.2015
=====================
* updated to TWRP 2.8.7

27.06.2015
=====================
* minor change in fstab to show data partition
  towards the lower part in the wipe menu

23.06.2015
=====================
* fix "off-mode" charging

19.06.2015
=====================
* new HTC One M7 release


[SIZE="1"][U]Previous chagelogs from Tasssadar and domicq[/U][/SIZE]
[I][U]Changelog from Tasssadar[/U][/I]
1.6.2015
=====================
* Fix installation of CM-based ZIP files
* Add "duplicate ROM" option to "Swap ROMs" page
* Running "restorecon -R /data" while in recovery will no longer break
  secondary ROMs

6.4.2015
=====================
* Fix support for SuperSU 2.47 Beta and higher

28.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 ROMs

12.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 update

14.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.1


[I][U]Previous changelog from domicq [URL="http://forum.xda-developers.com/htc-one/orig-development/mod-multirom-v28-redesigned-gui-t2880887"]here[/URL][/U][/I]
28.10.2014
=====================
*Update autoboot settings for MultiROM v29

[STRIKE]26.9.2014
=====================
* In app finally as MultiROM-Recovery.[/STRIKE]

22.9.2014
=====================
* Working USB-OTG

18.9.2014
=====================
* Initial version

 

[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:

1. a detailed explanation of the problem
   .
2. the recovery.log (found in /tmp/recovery.log or by copying it to the sdcard and then copying it to PC)
   .
3. the link to the thread and name of file (+ which version) you are having problems with
   .
4. 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.
​

 

[davidroid1]

Wreat work
V32 Working in my m7

Enviado desde mi One mediante Tapatalk

 

[nkk71]

Wreat work
V32 Working in my m7

Enviado desde mi One mediante Tapatalk

well the previous (dirty) version (that's why i needed to recompile to "e" so as not to cause confusion) has been out for a while, but I guess a new thread does help :laugh:

enjoy, and lemme know if all works well

.... in theory this should also work for Verizon and Sprint users, but I cant test that, since I only have GSM

and for me, the bugs are (always have been)
1- USB OTG doesnt work
2- MTP has to be toggled (on->off->on) for it to work

 

[mitchst2]

Thanks @oblikas then @domicq and now @nkk71

Without multirom I'd have been bored of the m7 by now. Thanks guys.

mitchst2

 

[mitchst2]

Got this error message?
If so flash the new recovery first then try again.



Now waiting for a new Rom I haven't flashed to test. Existing roms all grand.

mitchst2

 

[nkk71]

Got this error message?
If so flash the new recovery first then try again.

View attachment 3370368

mitchst2

hmm, lemme try again....it's a minor issue, just hope last build didnt mess any checks..... back in 10....

 

[mitchst2]

hmm, lemme try again....it's a minor issue, just hope last build didnt mess any checks..... back in 10....

Minor yes. Just flash new recovery first.

mitchst2

 

[nkk71]

Got this error message?
If so flash the new recovery first then try again.

View attachment 3370368

Now waiting for a new Rom I haven't flashed to test. Existing roms all grand.

mitchst2

okay, done... no issues

C:\ADB3>md5sum TWRP-multirom-20150619-v32e-UNOFFICIAL-m7univ.img
2b9ab7d04268ad13b05cd1a2a4d7a02e

C:\ADB3>fastboot flash recovery TWRP-multirom-20150619-v32e-UNOFFICIAL-m7univ.img
target reported max download size of 1514139648 bytes
sending 'recovery' (15470 KB)...
OKAY [  1.931s]
writing 'recovery'...
OKAY [  1.373s]
finished. total time: 3.304s


C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx    recovery


C:\ADB3>md5sum multirom-20150619-v32e-UNOFFICIAL-m7univ.zip
486a2e6a395283a03a603a336a93b03d

C:\ADB3>adb push multirom-20150619-v32e-UNOFFICIAL-m7univ.zip /sdcard/0NKK/
2420 KB/s (3925974 bytes in 1.584s)

......

Screenshot was saved to /data/media/0/Pictures/Screenshots/Screenshot_2015-06-20-01-02-50.png

C:\ADB3>adb pull /data/media/0/Pictures/Screenshots/Screenshot_2015-06-20-01-02-50.png
2419 KB/s (146185 bytes in 0.059s)

 

[mitchst2]

okay, done... no issues

C:\ADB3>md5sum TWRP-multirom-20150619-v32e-UNOFFICIAL-m7univ.img
2b9ab7d04268ad13b05cd1a2a4d7a02e

C:\ADB3>fastboot flash recovery TWRP-multirom-20150619-v32e-UNOFFICIAL-m7univ.img
target reported max download size of 1514139648 bytes
sending 'recovery' (15470 KB)...
OKAY [  1.931s]
writing 'recovery'...
OKAY [  1.373s]
finished. total time: 3.304s


C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx    recovery


C:\ADB3>md5sum multirom-20150619-v32e-UNOFFICIAL-m7univ.zip
486a2e6a395283a03a603a336a93b03d

C:\ADB3>adb push multirom-20150619-v32e-UNOFFICIAL-m7univ.zip /sdcard/0NKK/
2420 KB/s (3925974 bytes in 1.584s)

......

Screenshot was saved to /data/media/0/Pictures/Screenshots/Screenshot_2015-06-20-01-02-50.png

C:\ADB3>adb pull /data/media/0/Pictures/Screenshots/Screenshot_2015-06-20-01-02-50.png
2419 KB/s (146185 bytes in 0.059s)

What does all that mean?
Just flash the new recovery first as I said?

mitchst2

 

[nkk71]

What does all that mean?
Just flash the new recovery first as I said?

mitchst2

yes, sorry, i'll check into it more thoroughly tomorrow (1:25am for me) and it's just the installer script making sure what you are flashing is meant for your device

 

[nkk71]

What does all that mean?
Just flash the new recovery first as I said?

mitchst2

oh, you just wanna give me a hard time for opening a new thread..... i knew it :crying:

 

[mitchst2]

oh, you just wanna give me a hard time for opening a new thread..... i knew it :crying:

Not at all.
Hopefully you'll get some new users to multirom. Old threads got very confusing for newcomers I think.
Just wanted others to know the solution before reporting it doesn't work.

Also to be clear we don't need the contexts fix anymore? I.e. Just flash Rom, gapps and boot.

mitchst2

 

[nkk71]

Not at all.
Hopefully you'll get some new users to multirom. Old threads got very confusing for newcomers I think.
Just wanted others to know the solution before reporting it doesn't work.

Also to be clear we don't need the contexts fix anymore? I.e. Just flash Rom, gapps and boot.

mitchst2

nope,

file context fix no longer needed, was added here

layout_version fix (pull request) and (dirty) by-name support for the M7 was added here

only thing i'm aware of it that you'll need at least firmware 6.xx.xxx.x /hboot 1.57or higher
(from domiq's thread)

that will go into post 3, when i'm awake-ish

 

[Black_Eyes]

@mitchst2 can you please tell me which roms are currently supported as you are using it... ?????

 

[mitchst2]

@mitchst2 can you please tell me which roms are currently supported as you are using it... ?????

Them all. Sense, GPE, AOSP, MIUI.......

mitchst2

 

[rebel1699]

Tested OTG out pretty extensively. Although it wil not mount under the mounts menu, it is at least partially mounting it. I can get it to show up in add rom list. I can also get the multirom folder to be created on the usb disk. Install starts, but fails the instant that it attempts to create the data.img. However, after failure, it will show up in rom list on the usb stick. So, at least it has write ability to the usb. Just a bug somewhere now preventing a complete install.

ADDL: The new update gets a bit further. Just getting an error mounging mmcblk0p33 during the data.img deployment.

 

[Sebby]

never tryed it before ...this multirom

so i have quistions - maybe stupid quistion

- what do i need to erase before installing this,or can i leave the stock rom on it -and flash the multirom zip and recovery multi and flash then the second rom

-does it mess with the partitions

-where does it store the second rom (sdcard or data/media/)

-does the multirom zip erase somthing like system or sdcard

-how can i switch roms ,or does a menu come up at boot

really stupid quistions but i need to know

 

[Droidcore]

never tryed it before ...this multirom

so i have quistions - maybe stupid quistion

- what do i need to erase before installing this,or can i leave the stock rom on it -and flash the multirom zip and recovery multi and flash then the second rom

-does it mess with the partitions

-where does it store the second rom (sdcard or data/media/)

-does the multirom zip erase somthing like system or sdcard

-how can i switch roms ,or does a menu come up at boot

really stupid quistions but i need to know

I will try answer,

You can leave stock but need kernel support multirom,

As i know multirom not erase system or sdcard

For switch rom can download app multirom via google play

3 answer ,
Im use multirom

1 xenonhd, gpe 5.1, nosp, carbon all work normal :good: