yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] nkk71:
I'm downloading the plus edition atm, will take a while...

(just fyi: it used to work, i've tested older versions)

what firmware are you on?
[One (M7) Original Android Development] Claydelas:
7.19.401.2
[One (M7) Original Android Development] nkk71:
They're both working fine for me, both Plus Edition and stock edition

steps I did with both of them:

1- download rom, check it's not a bad download, put on device

2- "add rom"

3- let installer flash / choose default options in aroma and let the installer flash

4- exit installer, restoration and injection complete

5- reboot device, select new rom, wait about 10mins or so, to get to the setup screen

PS: don't allow the installer to "reboot device", just exit installer, and reboot from twrp once it's done
[One (M7) Original Android Development] Claydelas:
I didn't know about the last part, and that could be the source of the problem! Every time i flashed it I let it reboot from aroma. Will try and report back! Thank you very much!
[One (M7) Original Android Development] nkk71:
no problem, lemme know how it goes

and just and fyi: don't allow a script to reboot the device, TWRP should be allowed to finish it's job, and MultiROM-TWRP needs to do it's part as well (ie restore the original script, and more importantly do the multirom injection)

i'll try and see if that is a problem, and if so, try to remove the "auto-reboot" in some of the ROMs
[One (M7) Original Android Development] Claydelas:
Solved the problem! I didn't think restoring the original script would take 10 minutes on it's own so it must have been crucial. Thanks for taking the time to help me! <3
[One (M7) Original Android Development] nkk71:
Actually the restoring original script isn't so important, it only adds back the original installer-script, which get's modified for flashing to secondary.

However after the restoring part, twrp does the multirom injection into the secondary boot.img, and this part is the important one... if that isnt done the secondary wont be "multirom aware" and therefore not function properly.
[One (M7) Original Android Development] Claydelas:
Hey! It's me again :D Back at it with another quick question.. :D Is it possible to S-OFF while having multirom installed or should I wipe completely (i don't really want to)?
[One (M7) Original Android Development] nkk71:
Not entirely sure, but multirom may interfere with the process. You can keep all your secondaries as is, but I would recommend you

make a backup of your primary ROM

then install a sunshine compatible one (ViperOneM7 is known to work, you may/should choose an older version, depending on your firmware)...

without injecting multirom (untick that option!)

run sunshine to get S-OFF

restore backup made in point 1

PS: although sunshine doesn't wipe your device, it's always good to have backup (and copied to PC) of all your "critical" information, just in case.... this doesn't only apply to sunshine, it's a good habit when modding your phone ;)
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

See you on the 10 maybe.

Thanks for this on the m7, an integral part of the experience for me.
[One (M7) Original Android Development] nkk71:
Thank you, and no, the M7 hasnt been abandoned, once the code fixes are ready, the M7 will be as worthy as any other device I support... i actually used it today, still a great device!
[One (M7) Original Android Development] mitchst2:
Great phone no doubt.

Haven't used this since I done GPE conversion ;)
[One (M7) Original Android Development] Nebrassy:
This is amazing, thank you, perfectly working on hboot 1.56 S-ON
[One (M7) Original Android Development] Nebrassy:
I had only 1 rom installed, wanted to install another but couldn't install as secondary, so I copied the primary to secondary and installed the new one as primary, it worked but it does n't support kexec and the workaround doesn't work, so I copied it to secondary and restored the previous one to primary, it didn't work for some reason, is there any lite ROM that supports kexec to install as primary just so secondaries can work? (I won't use it), or any minimum necessary to have installed on primary?
[One (M7) Original Android Development] markan1995:
CyanogenMod 14.1 (Android 7.1) is not supported? Such an error (.

View attachment 3937156
[One (M7) Original Android Development] markan1995:
You need boot that supports kexec
[One (M7) Original Android Development] nkk71:
Try the attached version, unzip first, you'll get 2 files:

TWRP_3.0.2-0_multirom_m7univ_20161115-01.img

multirom-20161115-v33-UNOFFICIAL-m7univ.zip

Installation:

Flash TWRP_3.0.2-0_multirom_m7univ_20161115-01.img either using TWRP itself (TWRP->Install-> select Image -> then flash new TWRP to recovery partition)

or using "fastboot flash recovery TWRP_3.0.2-0_multirom_m7univ_20161115-01.img"

.

Then flash the multirom-20161115-v33-UNOFFICIAL-m7univ.zip

These are

completely untested builds

(only tested on M8 and M9), so don't know if they work at all on the M7. So flash at your own discretion.

Not sure if [MENTION=921816]ljjehl[/MENTION] tested the 2016-11-11 build to confirm if it's working or not.
[One (M7) Original Android Development] nkk71:
The attached version includes NO_KEXEC v4.1 so kernels with kexec-hardboot support are no longer needed.
[One (M7) Original Android Development] Grobsen:
Nice work !

Just tested it with Viper 9 on primary and installed Slim7 Testbuild as secondary ROM.

Both ROMS boot up as they should.

:good:

Thanks a lot !
[One (M7) Original Android Development] nkk71:
Thanks for testing, I've also uploaded them to androidfilehost, so all

test builds

will be in M7 MultiROM TEST BUILDS

That also includes the unofficial MultiROM Manager app with a few additions (but does not currently have a link for updating from within the app).

MultiROM Manager App[-debug] version
=====================
* Add support for external storage
(allows listing, manipulating, and booting secondary ROMs on external storage)
* Highlight currently running ROM first
(also disallow deletion of it)
* Show ROMs in order of location (Current, then Internal, etc.)
[B][I]Bug: if the current ROM is on an OTG, then "Internal" will [COLOR="Red"]falsely[/COLOR] be highlighted as running!![/I][/B]
* Allow duplicate ROM names if on separate partition
* Fix Widget

And regarding the official app, it will tell you there is an update available...

this is incorrect

, so do not update from the official app.
[One (M7) Original Android Development] Grobsen:
I assumed that and didn't update ;)

But thanks for the hint
[One (M7) Original Android Development] nkk71:
So much to do, so little time ;)
[One (M7) Original Android Development] Fox36:
Please help twrp muiltyrom recovery not work for me

My device is pno7100 801n

Hboot 1.55

S-off

unlocked bootlaoder

On unoficiall cm13

Muilty ROM v33 was installed sucsefuly

But. Multy ROM recovery get me a black screen and reboot

Please heeeeeeeeelp
[One (M7) Original Android Development] nkk71:
update your firmware
[One (M7) Original Android Development] Sebby:
i have root and ElementalX 20.1 installed

so that should work ...correct

---------- Post added at 11:50 AM ---------- Previous post was at 11:00 AM ----------

now lets see if i can work this out....

one quistion

if the rom asking for wipe system and data can i do so ,it does not touch the reall system and data

how do i flash a custom kernel for the second rom

and thanks for the great work

---------- Post added at 12:44 PM ---------- Previous post was at 11:50 AM ----------

oke done

last quistion

why does it create two multirom dirs

1 in data/media/0 -where i see the files en roms

2 if i plugin de usb en i see my sdcard there is also a multirom folder -but empty (can i remove that on)

by the way great work....
[One (M7) Original Android Development] nkk71:
1- the multirom folder is in /data/media/0/multirom or /data/media/multirom (for old 4.1.2 or lower file structure)

however you cannot browse through it (unless through root priveleged shell/explorer), because permissions are denied for "normal" viewing ... this was implemented a long time ago to avoid battery drain by MediaScanner.

2- yes, during installation of a secondary ROM, you can wipe data and system, those should only affect the secondary ROMs data and system partition

but as always, having a backup is highly recommended

3- to flash anything additional to a secondary ROM: TWRP -> Advanced -> MultROM -> List ROM -> [select the ROM you want to modify] -> and you'll get a set of functions (including flash zip) which will affect that particular secondary ROM only
[One (M7) Original Android Development] nkk71:
Thanks, will look into it soon

EDIT: okay, that's weird. just booted into recovery and mounted USB OTG just fine.... will try flashing and get back to you

EDIT2: so it does seem to work, but as was the case for some users before, if the USB-OTG is already inserted while entering TWRP, you wont be able to mount it (even if you unplug and replug it), you need to remove the USB-OTG, then Reboot -> Recovery

then plug in the USB and mount it
[One (M7) Original Android Development] nkk71:
Bug reports:

1- off mode charging

2- USB-OTG has to be done as mentioned above

3- MTP needs to be toggled for it to "come back"

i've noticed the same problems on mdmower's unofficial build, and since my device files is based on that, it will have have the same problems

Still to be added

MultiROM support for encryption (only applies to AOSP based ROMs, not HTC Sence based ones)
[One (M7) Original Android Development] Black_Eyes:
Whenever i try to boot secondary rom, it says "ERROR : Kexec-Hardboot is required to boot this ROM " :(

How to add this support to kernel
[One (M7) Original Android Development] mitchst2:
Your primary Rom only needs the kexec patch. Install a primary Rom that will take ElementalX for example in the primary slot.

mitchst2
[One (M7) Original Android Development] Black_Eyes:
I just need to flash ElementalX on the top of my primary ROM?? And then flash any rom on secondry slot?
[One (M7) Original Android Development] mitchst2:
Correct

mitchst2
[One (M7) Original Android Development] Sebby:
I love it ...great work

1 - wich version of twrp is your recovery based on i want to theme it

2 - will the off charge mode be fixed soon , thats the only bug i am not happy with

Voor the rest ..great work
[One (M7) Original Android Development] nkk71:
1- it's based off https://github.com/Tasssadar/Team-Win-Recovery-Project (TWRP 2.8.6 series)

2- yes, will fix off mode charging soon, maybe even today, if the kids go to bed early ;)
[One (M7) Original Android Development] Sebby:
Really happy to hear that ,thanks alot
[One (M7) Original Android Development] rebel1699:
Thats pretty unique, lol. I have been having to test with an otg/host mode "Y" cable, because I can only connect when plugged into 5v. Ill build another with the correctly shorted pins and keep playing.
[One (M7) Original Android Development] alex26aly:
No luck with S-ROM and ARTMOD - same error Incomplete rom, tried to install as secondary, didn't try as primary yet, coz I have GPE installed with a ton of apps

Does these roms work only installed as prmary???

I need to know before trying to reinstall everything, thanks.

One more thing: I have 3.9gb of free space, could this be a problem?? I'm trying to install from OTG
[One (M7) Original Android Development] Black_Eyes:
Do you have enough space on internal storage???? And have you flashed ElementalX on top of primary Rom?
[One (M7) Original Android Development] nkk71:
links (to thread and download) please so i can check/test...
[One (M7) Original Android Development] nkk71:
i just rebuilt it, off-mode charging working fine now, but didnt get a chance to check (maybe even fix) MTP and OTG, if I dont have anything in a few hours i'll just upload it anyway
[One (M7) Original Android Development] Sebby:
Big thanks ..don't care about the other stuff ,if de off mode charging is fixed i am happy

Still working great ,thanks alot

OTG i have a cable but never used it

MTP same thing never used that option

Can you upload it now please ,i must go away in one hour
[One (M7) Original Android Development] alex26aly:
4gb, yes I have elementalX n primary rom

---------- Post added at 06:46 PM ---------- Previous post was at 06:44 PM ----------

S-ROM: http://xdaforums.com/htc-one/development/rom-s-rom-7-1-5-8s-1-32-1401-15-real-t3086915

https://drive.google.com/file/d/0B2oJuOoYCH0yUGlYZUtlNlA4ajA/view

ARTMOD:http://xdaforums.com/htc-one/development/rom-artmod-sense-7-lollipop-1-32-401-8-t3064090
[One (M7) Original Android Development] nkk71:
done, 32f added:

MultiROM TWRP Recovery: https://www.androidfilehost.com/?w=files&flid=33972

MultiROM main zip: https://www.androidfilehost.com/?w=files&flid=33971

i only did minor testing, hope everything else still works
[One (M7) Original Android Development] nkk71:
okay, downloading

1- S.ROM-M7-Sense7-Harman-SE-SignROM2.zip

2- M7_Sense7_artmod_10.0.zip

each download will take about about 1.5 ~ 2 hours... so dont hold your breath ;)
[One (M7) Original Android Development] Fox36:
How to ubdate it please helpe
[One (M7) Original Android Development] nkk71:
http://xdaforums.com/showthread.php?t=2316726
[One (M7) Original Android Development] Fox36:
It is so hard. Any uthere way to fix it please

Becuse ihave no pc

Sorry for my bad englishe

And there is information

M7_UL PVT SHIP S-OFF RH

CID-11111111

Hboot-1.55.0000

RADIO-4T.35.3218.16

openDSP-v31.120.274.0617

eMMC-boot 2048mb

sep 10 2013,00:20:44.22972

OS-

Pno7100 801n

I am on cm12.1
[One (M7) Original Android Development] crashdjent:
Stock recovery and firmware.zip
[One (M7) Original Android Development] nkk71:
If updating firmware is too hard, I would recommend you first get comfortable with firmware and ROM flashing before trying out MultiROM.

It's a difficult mod, and if you run into problems you're going to have a hard time getting your device up and running.

So read up on ROMs and firmware, etc before trying MultiROM.
[One (M7) Original Android Development] somenderjangra:
How to use it in m7 sprint
[One (M7) Original Android Development] nkk71:
As mentioned in the OP, and the last page or two.
[One (M7) Original Android Development] nkk71:
Did you quote the entire OP, to ask that :rolleyes:

Please edit your post and remove the quote, it's a bad idea to quote the entire OP.

And yes it should work fine on any M7 (GSM, Verizon and Sprint), just remember to

only

flash ROMs that say they are compatible with your device.
[One (M7) Original Android Development] Cloverkit:
OK
[One (M7) Original Android Development] TDJ512:
I don't have any multirom buttons in the recovery. When I boot my phone it goes into multirom, when I flash something it says inject all that stuff after the flash, everything seems to be working but I cant get to anything but my internal primary. Is this common?
[One (M7) Original Android Development] nkk71:
Not sure what you mean, but if you are talking about MuliROM in recovery, you need to click the icon in the top right corner to get to the MultiROM-TWRP section.
[One (M7) Original Android Development] TDJ512:
I was looking in the wrong place lol sorry for wasting your time, I could've sworn the multirom commands use to be in the advanced tab.
[One (M7) Original Android Development] RudyxPompa:
Is there kernel for CM14.1?
[One (M7) Original Android Development] nkk71:
You can no-kexec for kernel's that do not have kexec-hardboot support, here's how to enable it.
[One (M7) Original Android Development] jbradshw:
So I added the official Lineage 14.1 m7 ROM (7.1.1 Nougat) as a secondary. It installed fine, but it freezes when you go into Developer options. I couldn't find much on this except on this thread: (https://xdaforums.com/google-nexus-5/development/rom-lineageos-14-1-nexus-5-t3531208) there's a mention that it freezes because Lineage is a secondary ROM and that a beta Multirom is needed. Will the version that was mentioned in this post fix that?
[One (M7) Original Android Development] nkk71:
It was fixed on November 2nd, so any build of MultiROM prior to that does not include the fix/workaround and you won't be able to enter Developer Options on any Android 7.x based ROM.
[One (M7) Original Android Development] nsanzumuhire:
Hi guys am on the latest lineageOS and I want to Install the lollipop based on stock sense along with this lineageOS but i the TWRP multi-rom is not yet Installed because I have no idea about multirom this z for the first time !!
[One (M7) Original Android Development] haykweb:
Can we have TWRP 3.1 multirom version ?
[One (M7) Original Android Development] Captain_Throwback:
No
[One (M7) Original Android Development] nkk71:
Unless there is something terribly wrong with the last version, this one:

will be released when it's ready, not any time earlier.

And I would like to know a few things from all the people that keep asking for a "release"

What is wrong with the current version?

Which feature(s) do you *need* from 3.1.0-x?

You do realize MultiROM-TWRP is TWRP+<some MultiROM stuff>, so what's the point of having a 3.1.0-x if it doesn't include any MultiROM fixes?

I don't think I heard anybody complaining that the Nov 15 MultiROM-TWRP was *newer* than the official TWRP :eek:
[One (M7) Original Android Development] 5m4r7ph0n36uru:
Best guess is: they want to upgrade their firmware from MM to N, even though it isn't needed for things like the FP to work properly on the ROMs found for the HTC 10.

In addition many of them don't seem to know how much work it takes for such a huge hack to be ported to a newer version - if possible at all. It's sad but after an update (Recovery, ROM, or what so ever) all start to ask for bugs to be fixed immediately, or features to be ported immediately, instead of giving all developers proper time to dig through their large codes and do so, patiently waiting for them to announce as they got ready with their work. Not to mention to deliver proper logs to help developers.

Sorry for the OT. But I saw such requests this often lately that those words had to be said, or better be written.
[One (M7) Original Android Development] Captain_Throwback:
This is the M7 thread...
[One (M7) Original Android Development] nkk71:
So you're not going to release N firmware for the M7 :eek: :p
[One (M7) Original Android Development] Captain_Throwback:
I'd release it for the M8 first since I actually have one of those, lol :rolleyes:
[One (M7) Original Android Development] ljjehl:
You need a M7 also :)
[One (M7) Original Android Development] Captain_Throwback:
Nah, I don't like phones with no SD Card...:thumbsdown:
[One (M7) Original Android Development] bufe:
Android 7.1.1 compatibility
[One (M7) Original Android Development] nkk71:
Is that a statement, a question, or some riddle?
[One (M7) Original Android Development] 5m4r7ph0n36uru:
Sorry Cap. I own both devices an have both threads subscribed. Just didn't recognize it on the XDA labs App.
[One (M7) Original Android Development] bufe:
When it compatible to 7.1.1?:D
[One (M7) Original Android Development] nkk71:
Which version are you running and what's the problem/error?
[One (M7) Original Android Development] bufe:
MultiROM: v33b (multirom-20161115-v33-UNOFFICIAL-m7univ)

Recovery: TWRP_3.0.2-0_multirom_m7univ_20160409-03

Kernel: has kexec-hardboot patch ElementalX-m7 [Nov 26]

Internal ROM: ViperOne 9.0.0

Could not install ROM

[ROM][7.1.1] Lineage OS 14.1

[ROM][NOUGAT][7.1.x][M7]XenonHD

Slim-m7-7.1.1.build.0.16-BETA-20170317-2143
[One (M7) Original Android Development] nkk71:
Well, instead of asking for TWRP 3.1.0-x or later, maybe you should go check the last couple of pages, and preferably the OP, you'll notice that you are not running the correct build.
[One (M7) Original Android Development] saturday_night:
If you could re-add support for GPE Firmware in next rls that would be really great. A lot of users are switching to GPE Firmware because it make less problems with Android 7 Roms. And for me personal it would be the only way to ever get mr on my m7, i cant change my firmware and stuck on latest GPE Firmware because of an electricity failiure while flashing the GPE Firmware. I was lucky that the firmware files where all installed already, the only thing that broke for me permanently is fastboot connection in bootloader.
[One (M7) Original Android Development] nkk71:
Can you elaborate please.

MultiROM doesn't touch firmware, so I'm not sure what you mean by that.
[One (M7) Original Android Development] saturday_night:
I have read a lot in this thread, and somewhen in 2015 you changed something in multirom for usb OTG support. After that some users cant use mr anymore because they where using GPE Firmware. The GPE Firmware doesnt boot into mr twrp since this, funny is that also MdMower had the same problem with his first release of twrp 3.1 for m7, the first release didnt work with GPE Firmware (didnt boot into recovery) but he changed something before 3.1 came out official and the official 3.1 does work now with GPE Firmware. So its just the mr recovery where something would needs to be changed toboot on GPE Firmware.
[One (M7) Original Android Development] nkk71:
Nice thanks for the info. I wasn't aware that MROM-TWRP isn't booting with GPE firmware, I only new that MultiROM had some issues with old firmware, and never really bothered checking that.

The TWRP issue would be kernel related, I'm using an old kernel as well as still building in 5.1 (omnirom) whereas mdmower is building in CM/LineageOS 14.x (I think) which would be 7.1.

I'll see what I can once I have this whole mess figured out :eek:
[One (M7) Original Android Development] haykweb:
Not supporting for Android 8 :( Can't installing Lineage OS 15 as second rom.
[One (M7) Original Android Development] nkk71:
Error 7 doesn't say anything you'll need to upload your recovery.log
[One (M7) Original Android Development] haykweb:
Ok thank's
[One (M7) Original Android Development] nkk71:
If you're talking about lineage-15.0-20170902-UNOFFICIAL-m7.zip from here

then don't bother at this time

1- the asserts don't work properly

2- even with them removed the device doesn't boot (neither primary nor secondary)
[One (M7) Original Android Development] Nebrassy:
I'm having the same problem, could be an issue with the ROM, here's a log anyway
[One (M7) Original Android Development] nkk71:
Did you read the above post? Or even the LOS15 Dev's posts?

If it doesn't even flash nor boot in primary, then I doubt it will in secondary :p
[One (M7) Original Android Development] Nebrassy:
I was testing it, got a log the you posted that, so I uploaded the log anyway.

Haven't seen the Dev's post, got a link?
[One (M7) Original Android Development] nkk71:
https://xdaforums.com/showpost.php?p=73640890&postcount=7

I removed the asserts so it would flash, but as I mentioned above it won't boot, and I'm not a ROM dev, but I can tell you there are plenty of problems in there.
[One (M7) Original Android Development] nkk71:
By the way, would you mind removing your link in your signature. Most people (including me), don't like mirrors they don't control themselves, so unless something is wrong with my links, I'd appreciate it if you remove yours.
[One (M7) Original Android Development] haykweb:
Deleted
[One (M7) Original Android Development] alial04:
Cuz it's not ready still working to make it boot.!
[One (M7) Original Android Development] bojsa_boy:
Just installed test build 20161115 and RR 7.1 as a second rom successfuly. Everything works perfectly :) Thanks a lot!
[One (M7) Original Android Development] alex26aly:
Thanks for your effort
[One (M7) Original Android Development] Sebby:
big thanks from me
[One (M7) Original Android Development] nkk71:
My pleasure, let me know if i broke something along the way :angel:
[One (M7) Original Android Development] Sebby:
big thanks for the fast response

quick test

- off-charge mode working

- mtp als working ,i first disable it -then usb in -then enable it - 5 sec. and drive came up

thanks alot