• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL] TWRP 3.0.3-2 + MultiROM v33 for OnePlus 3/3T

Search This thread

bird333

Senior Member
Jul 19, 2010
476
18
Yeah just noticed that restorecon after spending a considerable amount of time trying many different combinations lol and after restorecon I reflashed DU and all is fine again.....

Guessing something did get corrupted, but daaaaaaaam the 3 & 3T are fickle devices for being dev friendly :p

Thanks for your appreciated & considerate input.....:good:

What is 'DU'?
 

TweaknFreak

Senior Member
Dec 22, 2014
91
22
Xiaomi Poco F3
I flashed with on top of my OOS 4.0.2. But it kept booting to TWRP, then tried flashing custom ROM yet boots only to TWRP.

Now I started fresh with RR as my ROM. I need steps how to proceed to add OOS as secondary ROM. Any thoughts are appreciated, TIA
 

acultr

Senior Member
Jan 29, 2012
1,034
267
Google Pixel 5
I need help.
wenn I booted in multirom the touch screen is not responding.the cancel and the bootnow buttons not responding.
I set on time based boot.
TWRP version 3.0.3-2 2017.01.31.
Thank you for your help.
 
Last edited:

dreezz

Senior Member
Feb 24, 2011
660
122
I need help.
wenn I booted in multirom the touch screen is not responding.the cancel and the bootnow buttons not responding.
I set on time based boot.
TWRP version 3.0.3-2 2017.01.31.
Thank you for your help.

same here.
so i have to choose the rom to boot from first, from twrp multirom settings.
currently happy with RR official, so no big deal, but touch screen is not working (for me), that's right.
 
Last edited:
  • Like
Reactions: acultr

BitOBSessiOn

Senior Member
Last edited:

xanthrax

Sr. Mod / Mod Committee Lead / RC-RT Com - Vampire
Staff member
How would one go about updating firmware to 4.0.3 from 4.0.2 if you are using multirom? With keeping all your other ROMs?


I mean updating a ROM is straight forward.. The internal not so which I found.

Sent from my ONEPLUS A3003 using Tapatalk

just dirty flash

flash the 4.0.3 on top of 4.0.2 , flash supersu ( don`t boot after update !!!)
 

knpk13

Senior Member
Dec 11, 2015
2,115
1,231
OnePlus 3
OnePlus 3T
Tested on OP3T with latest firmware 4.0.3 (it should work on OP3, but not tested)

Downloads:
TWRP_3.0.3-2_multirom_oneplus3_20170212-01.img
multirom-20170212-v33-UNOFFICIAL-oneplus3.zip

Yay, new update!

Does it have all the fixes from 3.0.4-1? Also which Roms did you test? Do Roms with the new and old f2fs work fine with multirom? I still don't understand this new and old f2fs thing, it'd be helpful if someone could explain it in detail.

I'm assuming the old multirom uninstaller still works with this?

I asked this before, and xanthrax gave me an answer.. but can you confirm that any zips (that contain firmware) installed as secondary Roms won't overwrite the actual firmware of the device? Like for example if I flash OOS 4.0.2 as secondary (or a custom rom that ships with firmware), it won't overwrite my primary OOS 4.0.3 firmware?

Edit: MultiROM working with OOS 4.0.3, Lineage, Omni, and Slim so far.
 
Last edited:
  • Like
Reactions: michelD

BitOBSessiOn

Senior Member
Yay, new update!

Does it have all the fixes from 3.0.4-1? Also which Roms did you test? Do Roms with the new and old f2fs work fine with multirom? I still don't understand this new and old f2fs thing, it'd be helpful if someone could explain it in detail.

I'm assuming the old multirom uninstaller still works with this?

I asked this before, and xanthrax gave me an answer.. but can you confirm that any zips (that contain firmware) installed as secondary Roms won't overwrite the actual firmware of the device? Like for example if I flash OOS 4.0.2 as secondary (or a custom rom that ships with firmware), it won't overwrite my primary OOS 4.0.3 firmware?

You shouldn't get any problem about F2FS with this (unified) build. Using same kernel thx to @jcadduono (used for official unified TWRP). More info about F2FS in his official thread in OP3 dev section.

This is almost the same TWRP 3.0.4. @nkk71 working on merging latest commits and some other stuff for TWRP-MROM. Big thx to him.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    ***

    We're moving...

    From now on we move officially to :
    MultiROM v33 for OP3/3T trhread.


    ***​

    As you know, to be able to run multiple ROMs on our system we need a Modded TWRP version (for flashing ROMs as secondary systems) and MultriROM utility to choose which ROM we want to boot, in this case, the NO-KEXEC version (no patched kernel needed). System must be not encrypted.

    Disclaimer:
    • Remember: You use this under your own risk!

    Notes:
    • Tested with Stock 3.5.3 as secondary, CM, RR, etc...

    Download (Latest TWRP and MultiROM for 3T - DEPRECATED, see below unified version):

    Download Unified version (3/3T)


    Guide (short version....):
    • Remember: Your device must be unencrypted or MultiROM won't work...
    • Flash TWRP-MROM modded and reboot in recovery mode (you need to unlock bootloader, etc...)
    • Flash MultiROM ZIP
    • Set No-Kexec option in settings for MultiROM from TWRP
    • Inject boot sector
    • Flash your favorite ROM as secondary from MultiROM menu (Add ROM...)
    • Reboot
    • Select ROM to boot from MultiROM menu

    For Kernels Devs
    • If you want to support MultiROM, you must enable CONFIG_INPUT_HBTP_INPUT option in Kernel config file to properly support its touch screen menu, please. Thx.

    All feedback is welcome. I have no much time, but I will try to keep it as well as possible.

    Known Bugs:
    • You tell me...

    Thanks:
    • To @Tasssadar for all awesome MultiROM dev
    • To @nkk71 for NO_KEXEC work
    • To TeamWin for TWRP (Specially @jcadduono for his initial port for OnePlus 3T)
    • To @martinusbe for his MultiROM port for OnePlus 3


    XDA:DevDB Information
    MutiROM, Tool/Utility for the OnePlus 3T

    Contributors
    BitOBSessiOn
    Source Code: https://github.com/BitOBSessiOn/android_device_oneplus_oneplus3t/commits/mm6.0-twrp-mrom


    Version Information
    Status: Testing
    Current Stable Version: 3.0.3-1
    Stable Release Date: 2017-01-18
    Current Beta Version: 3.0.3-2
    Beta Release Date: 2017-02-12

    Created 2016-12-01
    Last Updated 2017-02-17
    12
    TWRP 3.0.3-2 / MultiROM v33 for OP3/3T (2017.02.12)

    Tested on OP3T with latest firmware 4.0.3 (it should work on OP3, but not tested)

    Downloads:

    EDIT: It seems to work fine also for OP3. Thx to @deeplyyoung for testing
    11
    TWRP 3.0.3-1 + MultiROM v33 (20170118)

    Downloads:
    • TWRP 3.0.3-1 available here.
    • MultiROM v33 (20170118) available here.

    Changelog:

    Code:
    commit 53f72b7563c6cf358c5088246ad3af0899327df5
    Author: bigbiff bigbiff <[email protected]>
    Date:   Thu Dec 8 21:21:17 2016 -0500
    
        TWRP device version string
        
        For building through jenkins. Export a variable to the shell
        so that we don't monkey patch variables.h and keep the git tag
        clean in the version string.
        Jenkins will export the variable TW_DEVICE_VERSION=n where n > 0.
        The makefile will use this variable to show the device string
        in twrp startup. For mass production builds, omit the
        environment variable to default to 0.
        
        Change-Id: I0d6eb764255d7069c0fb4a378522a009cfe4054f
    
    commit 94e5a23dd2f12c2cfca8beb9dadbde92820b1d55
    Merge: 78f6699 7dde36d
    Author: nkk71 <[email protected]>
    Date:   Sat Jan 14 16:13:41 2017 +0200
    
        Merge remote-tracking branch 'upstream/android-7.1' into android-7.1-mrom
    
    commit 7dde36df119a1ed0089b999641b27dc2c2a5280d
    Author: sndnvaps <[email protected]>
    Date:   Tue Oct 4 18:09:37 2016 +0800
    
        updater: link libcrypto_utils_static if it exist
        
        Change-Id: I9bf238a3e29d88850a6cc69f07954949722c35d7
        Signed-off-by: sndnvaps <[email protected]>
    
    commit 1c28904749f5d0ae58b113b5b59901f7fc3731f6
    Author: D. Andrei Măceș <[email protected]>
    Date:   Fri Dec 16 16:01:56 2016 -0500
    
        libtar: Use relative path for crypto/ext4crypt include
        
        Don't assume path to be bootable/recovery (i.e., support CM's
        RECOVERY_VARIANT).
        
        Change-Id: Ib53cc919c5a9beb3beee71d7227a7c957a24b601
    
    commit 1021edf17ed57f193724a953dd159e7717e9553a
    Author: nailyk-fr <[email protected]>
    Date:   Sun Dec 18 14:32:25 2016 +0100
    
        bootloader_message: Allow TWRP to ignore wipe-data command into misc
        
         * Rebase of https://gerrit.omnirom.org/#/c/20750/ patch-set 3
         * Original commit message:
        
        fix: recently a change in AOSP causes a bootloop to TWRP
        (and therefore all ROM's based on it)
        Reason: AOSP enables use of /misc partition and normally the fstab in
        TWRP will not have /misc added. The problem is now when Android writes
        a wipe command to /misc it will force TWRP to boot but TWRP will do
        nothing - leaving the cmd in /misc. This results in a bootloop to TWRP.
        Solution: I added a new var TW_IGNORE_MISC_WIPE_DATA which can be
        set to "true" in Boardconfig.mk of a device requiring this which then
        ignores /misc commands like it would be when /misc would be just not in
        fstab BUT with this change TWRP clears the bit in /misc so a normal boot
        can happen.
        Besides that if the device do not have an own recovery key combo and
        /misc is enabled we want to open TWRP after walking through the factory
        reset screen - without actually doing a factory reset.
        kudos to nailyk (and DevUt) for the help with the C++ code!
        
        Change-Id: If6fed5872015f1a66304e3edbdb787c507236f69
    
    commit dcd1e440e009b7861f09e2b718ea489bdcea34b5
    Author: James Christopher Adduono <[email protected]>
    Date:   Sun Nov 6 13:17:34 2016 -0500
    
        Support theme width and height offsets
        
        Current use condition is LG V20, where the secondary screen is
        actually just a corner chunk of the main screen.
        In this case, we need to shift the UI down some pixels in order
        to see it all, but just using Y offsets resulted in losing
        the rest of the GUI below.
        
        Example in BoardConfig.mk:
          # Shift TWRP off the secondary screen
          TW_Y_OFFSET := 160
          TW_H_OFFSET := -160
        
        Change-Id: I5a06638ba0d05e5b9fd8a6245c630d6ea3394f78
    
    commit b29a5e27c33291f8134ea5f28e84e672a3c25199
    Author: D. Andrei Măceș <[email protected]>
    Date:   Thu Dec 22 06:19:44 2016 -0500
    
        build: Consolidate the crypto_utils presence tests
        
        No point checking filesystem repeatedly/check may change in future
        
        Change-Id: I0413b07b850f785eb5150c6ed18836cc56e94d6f
    
    commit 4767caf1f4cd08cdc7d58476bc017dca17870112
    Author: Ethan Yonker <[email protected]>
    Date:   Wed Jan 11 10:45:04 2017 -0600
    
        Fix compile error on 4.4 tree
        
        Change-Id: Id85fdf0f4dee02f8ee3ae50ec42423c6a154a3eb
    10
    https://forum.xda-developers.com/showthread.php?t=3543391

    TWRP 3.0.4 is out. I guess the MultiROM version will be updated soon to.

    Should I wait until I try this out, or I should go for it? I'm on OOS 4.0.2 and would like to have LineageOS as my second ROM.

    /Söder
    I would suggest to wait for a few days... F2FS is not working as expected... Although it works, we are getting too long TWRP booting times because FS checking, etc...

    I've moved my /data partition to encrypted EXT4 for testing.

    I hope we can enjoy latest TWRP-MultiROM soon... but no ETA, facing also some theme issues because theme engine has changed in 3.0.4.

    Next build should be an unified version for 3 and 3T.
    6
    We're moving...

    From now on we move officially to MultiROM v33 for OP3/3T trhread.

    All discussion should be placed there. This thread will become obsolete soon.

    Thx !