• 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

martinusbe

Recognized Developer
Jun 18, 2011
2,193
6,115
53
Belgium / Flanders
martins-sclc.blogspot.com
Last edited:
  • Like
Reactions: deeplyyoung

bird333

Senior Member
Jul 19, 2010
476
18
I'd like to get a second opinion on this. My primary is the original OOS 3.5.3. Can I flash this 4.0.2 kernel (as posted here https://forum.xda-developers.com/showpost.php?p=70994161&postcount=486) on that and then flash RR (https://forum.xda-developers.com/oneplus-3t/development/rom-resurrection-remix-5-8-0-oms-t3527338) as a secondary? Also, the install instructions say to use TWRP 3.0.4. Is there a multirom version that can handle this install? Is there a way to backup my original kernel and modem from OOS 3.5.3 in case something goes wrong?
 

alesimula

Senior Member
Apr 2, 2016
327
501
@BitOBSessiOn OTA updatea like Lineage updates do not work: phone is rebooted in TWRP but update is not installed (oneplus 3)

EDIT: i think it might ne a problem of the OTA file
 
Last edited:

lindahl85

Senior Member
Feb 9, 2011
1,037
134
Vetlanda
I'd like to get a second opinion on this. My primary is the original OOS 3.5.3. Can I flash this 4.0.2 kernel (as posted here https://forum.xda-developers.com/showpost.php?p=70994161&postcount=486) on that and then flash RR (https://forum.xda-developers.com/oneplus-3t/development/rom-resurrection-remix-5-8-0-oms-t3527338) as a secondary? Also, the install instructions say to use TWRP 3.0.4. Is there a multirom version that can handle this install? Is there a way to backup my original kernel and modem from OOS 3.5.3 in case something goes wrong?

I did that change and went to firmware 4.0.3. The nougat rom boot and works very good as secondary. The problem is when i want back to my primary marshmallow rom. It just don´t work anymore :( I tried to install the 3.5.4 firmware and RR 5.7.4 from a clean state. It starts but instantly reboots. Could it be the latest multirom that´s causing this?

---------- Post added at 10:11 ---------- Previous post was at 09:43 ----------

I noticed another funny issue. I have OOS 4.0.3 as a secondary rom. I switched to sRGB mode in that. When i reboot to recovery, i can see that the blue color has changed too so sRGB follows to recovery from a secondary rom.
 

tyler19820201

Senior Member
Jun 19, 2011
360
55
London
I have Internal ROM OOS 4.0.3 but i can not add any ROM for secondary...I was trying the Lineage 14. version but i am always having error 7 on TWRP. asserts failed: oppo.verify.trustzone
:rolleyes::(
I did factory reset wipe chache/dalvik but does not help.
 

lindahl85

Senior Member
Feb 9, 2011
1,037
134
Vetlanda
I have just formatted data to clean my device. Installed multirom twrp and a RR rom. Tried to reboot but it just goes back to recovery and make me to swipe to allow modifications. I can´t get out of here.

Screenshot.png
 
Last edited:

deeplyyoung

Senior Member
Feb 28, 2013
3,567
1,710
I have just formatted data to clean my device. Installed multirom twrp and a RR rom. Tried to reboot but it just goes back to recovery and make me to swipe to allow modifications. I can´t get out of here.
Swipe to allow modifications once and you good to go...

---------- Post added at 02:46 AM ---------- Previous post was at 02:46 AM ----------

I have Internal ROM OOS 4.0.3 but i can not add any ROM for secondary...I was trying the Lineage 14. version but i am always having error 7 on TWRP. asserts failed: oppo.verify.trustzone
:rolleyes::(
I did factory reset wipe chache/dalvik but does not help.
Try flashing 4.02 FW and then try flashing Los
 

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 <sndnva[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 !