yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] domicq:
boot into recovery and post there your log (advanced -> copy log to sdcard)
[One (M7) Original Android Development] TabascoJoe:
I was impatient with the Rom install. I think there are issues with TWRP 8 and the aroma installer. It does work, but take a long time to install.

Two things I did notice...

1. you need to plug in your OTG cable in after the recovery boots. If its plugin in before TWRP will not recolonize the USB OTG. (This may be a TWRP 8 issue, I really never tested 8 before MulitRom)

2. After MultiRom boots the internal rom, the HTC logo (the one that says powered by Android) does not show. Just a black screen. This is with the brightness of the MultiRom set to the highest. The ROM's HTC splash screen does show. This is a very minor cosmetic inconvenience.

Other than that a Huge Thanks for updating MulitRom. I've been waiting ages for this.
[One (M7) Original Android Development] miko12312:
Is sprint HTC one m7 ever going to see multirom on it , haven't seen any development , since Verizon supports it why can't this be ported
[One (M7) Original Android Development] domicq:
Main porter to m7 got not much time. Device repo is in op. Maybe had someone more time.
[One (M7) Original Android Development] the-blind-bandit:
Modded twrp not working for me, maybe it needs updating?
[One (M7) Original Android Development] danborza:
Hey guys! I've tried flashing ElementalX kernel for lollipop on NuSenseSix 10.6 but I got stuck on boot! any ideea on how to get multirom going?
[One (M7) Original Android Development] Lossyx:
I haven't checked that version for lollipop... But does it have kexec-hardboot patch on?
[One (M7) Original Android Development] danborza:
Yes ,it has! I managed to start dual boot!

I could boot the secondary system,but base system didn't load after reboot...
[One (M7) Original Android Development] mochoandre:
Please Update multirom
[One (M7) Original Android Development] domicq:
Maybe is problem just by you.
[One (M7) Original Android Development] the-blind-bandit:
Yeah I guess it must be, strange because twrp works fine I'll look in to it. Thanks
[One (M7) Original Android Development] domicq:
There were problems with hboot, try 1.57
[One (M7) Original Android Development] the-blind-bandit:
I would but after downloading the HTC one toolkit and just playing with it I clicked s-on thinking it was to select wether you are s-on or off and it wasn't it was to put you back to s-on and now I can't turn it off again
[One (M7) Original Android Development] Lossyx:
Then it looks like, if you want to S-OFF then you have to pay $25 for SunShine. Best case for you this is a problem not regarding hboot..
[One (M7) Original Android Development] the-blind-bandit:
Yeah thanks, I know now firewaters gone sunshine is my only option (hopefully maybe a substitute will come along :confused:) but i dont really want to pay for what others are kind enough to make for free. I dont really think its an hboot problem just a recovery issue but im probably wrong.
[One (M7) Original Android Development] miko12312:
Can someone please port this to m7spr or lead me in the right direction , nobody ever replies or tries to help , I have read the multirom op for porting but still unsure what to do
[One (M7) Original Android Development] Claydelas:
Ok guys, I have some serious issue right now. For educational porpuses (trying s-off on 1.57 without sunshine) I flashed CM 11 as a primary rom as well as a the kernel needed but unfortunately there is no aosp kernel with kexec-hardboot so I just thought i will loose my ROMs while in the CM 11 kernel only. But after flashing a sense rom with elementalx as a primary suddenly all my secondary ROMs wont boot and will just restart into recovery after selecting them. Any thoughts ? I have some data i want to pull out of them so help will be very appreciated :) P.s - Any easy way to flash kernels on the secondary roms with S-ON ?
[One (M7) Original Android Development] the-blind-bandit:
In multi rom TWRP go to » advanced » multirom » ROMS » install boot.img / remove boot » then select the boot.img you want for the Rom you selected
[One (M7) Original Android Development] nkk71:
[MENTION=5401235]abdulwakil[/MENTION]

NuSenSeveN-LP-m7_v1.00c_031615 worked just fine as secondary: (flashed directly to secondary)

[/IMG]

I also figured out what to change for the selinux issue (which would mess up any [already working] secondary roms), i'll try to post a flashable zip when i get a chance.

what problems did you get flashing NuSenSeveN ?
[One (M7) Original Android Development] :
Yup. I think the kernel was the problem. I flashed it as secondary and then flashed elemental x 20 over it. now its booting up.

which kernel did you use ?
[One (M7) Original Android Development] nkk71:
just the built-in one (first option i think), but still need to fix the file contexts, otherwise some roms will nuke multirom directory.... hopefully i'll get that up tomorrow
[One (M7) Original Android Development] mitchst2:
ViperOne8 nuked all my secondary ROMs. Installing as primary first then moving to secondary worked though. Be good to have a fix should secondary ROMs get corrupted.

Sent from my HTC One
[One (M7) Original Android Development] nkk71:
this is due to the (in)famous "restorecon -FR /data/media/0", it will nuke every secondary rom, i have a fix, just need to fix it up properly then will upload a flashabale zip

it HAS to be flashed before booting the rom so as not to run:

restorecon -FR /data/media/0/B] and exclude the multirom directory

i've successfully tested it on viperone 8.0.0, but the file_contexts needs a slight modification (ie ramdisk modification), otherwise everything on "internal storage" will get messed up for multirom
[One (M7) Original Android Development] nkk71:
hey guys, attached is a flashable zip in TWRP to add an exception for multirom folder

basically what happens is when you (intentionally or not) run: "restorecon -FR /data/media/0" to fix the internal storage, the usual file_contexts will also "fix" the multirom folders which will break ALL secondary ROMs

for example on ViperOne 8.0.0 after "Android is upgrading", at one point the command is run by itself as can be seen through the logcat:

Line 32209: D/m0narX_shell( 2937): restorecon -FR /data/media/0 output: SELinux: Loaded file_contexts from /file_contexts

the default file_contexts defines /data/media/0 as follows:

/data/media(/.*)?	u:object_r:media_rw_data_file:s0

which ultimately breaks any secondary ROMs

the flashable zip will add the following exceptions:

#### MultiROM exceptions
/data/media/multirom(/.*)?	<<none>>
/data/media/0/multirom(/.*)?	<<none>>

so as not to touch the multirom folders, in case a restorecon is (manually or automatically) triggered

I recommend you flash this onto both primary (using normal TWRP -> Install method)

and ALL secondary ROMs (using TWRP -> Advanced -> MultiROM -> List ROMs -> select the ROM -> Flash Zip)

Also when adding a new ROM (primary or secondary), immediately after successful installation, do not boot the rom, but flash this zip first;

for example, I was able to flash ViperOne 8.0.0 directly to secondary, then before booting, flashed this zip, and was then able to successfully boot it, and it ran the restorecon program, but didnt touch the secondary ROMs (which includes itself, otherwise it would have crashed)

BTW: this flashable zip will not change the kernel per se, it will take the existing kernel (of whatever ROM you are using), and just change the file_contexts to exclude multirom folders from being touched

Hope this helps, if you have any questions (I tried explaining above what happens, but not sure if I wrote it clearly enough), let me know

EDIT: use v2 from post 610 below
[One (M7) Original Android Development] Lossyx:
Many thanks! Worked for me.
[One (M7) Original Android Development] nkk71:
:D

actually, i have a better idea... though this works just fine, it's a bit cumbersome... i need to rewrite it later, so it'll be a one time flash, and fix all installed roms :eek:.... will post back when i have that done
[One (M7) Original Android Development] mitchst2:
Why oh why didn't I download this. Latest IC just nuked all my ROMs. Normally OK on this ROM. I'll wait for your new solution and resist flashing anything else until then.

Sent from my HTC One
[One (M7) Original Android Development] nkk71:
That zip should do fine in the meantime, don't think I'll have anything before the weekend, it will be the same thing of sorts,

Only difference is that it'll go through all ROMs (primary and secondary) and "fix" the file contexts

I'll need to rewrite the script and test it when I can
[One (M7) Original Android Development] mitchst2:
Had to flash latest IC. Used your fix and it worked perfectly. Thanks.

Sent from my HTC One
[One (M7) Original Android Development] nkk71:
I'm much happier with version 2, just need to do a bit of testing and will upload tomorrow hopefully

Can be installed directly from main TWRP install menu, and should fix both primary and secondary ROMs

Pretty much does the same thing, just more globally and checks for duplicate entries.

Let me test it better, then I'll upload it.
[One (M7) Original Android Development] :
I flashed the latest IC 7.0.1 yesterday directly to secondary without any problem.

and then flashed DU 9.2 just the way [MENTION=2605798]nkk71[/MENTION] posted on page 57 and it was profit !
[One (M7) Original Android Development] nkk71:
Hey guys,

Attached zip should work better... well it pretty much does the same thing, except this should be flashed using the main TWRP -> Install method.

This new flashable zip will:

go through all secondary ROMs installed and fix the file_contexts

fix the primary ROM

actually check if the [multirom] exceptions already exist (the old one would just append the exceptions, so everytime you flash it, it'll just add more lines, even if the exceptions are already in there)

I've tested as best I could, and it worked for me.... even manually initiating a "restorecon -FR /data/media" would no longer touch the multirom folders.

Let me know if you run into any bugs

Note: during processing of secondary ROMs it will fail on "Internal" as that folder doesnt actually have any kernel, it's just a placeholder for the icon or name; so this is expected behaviour

Usage: flash this using the normal TWRP -> Install method (

before

booting the new/old ROM)

it should be flashed anytime you add/change a kernel in either secondary or primary ROMs; note that flashing a new ROM / reflashing a ROM / etc. will also include a kernel, so you need to flash this again.

you can flash it as many times as you want, since it will check if the exceptions already exist and wont add them if they are there.

I just flashed 3 ROMs (including InsertCoin) all to secondary, then flashed this zip.... it fixed all the ROMs (kernels & file_contexts) installed, and they all booted fine.

Enjoy :)
[One (M7) Original Android Development] melando:
ROMs restored as secondary from back up are no longer booting up for me, they hang and reboot on the boot animation... Have tried memory fix zip and wiping cache, dalvik but no good. Any suggestions?
[One (M7) Original Android Development] sumanth08:
Has any one flashed cm12 as secondary? Could anyone provide steps to flash cm12 as secondary as I dont want my Primary rom to be borked.
[One (M7) Original Android Development] blast1987:
i've tried to flash cm 12 and 12.1 as second , but both roms doesn't seem to work, if required i can attach the TWRP log
[One (M7) Original Android Development] nkk71:
CM12 uses "block_image_update" to install, there is no way for it to go directly to secondary, you have to flash it to primary, then optionally move it to secondary as described here: http://xdaforums.com/htc-one/orig-d...8-redesigned-gui-t2880887/page57#post58731640

recommend you also keep/use the Fix File Contexts zip
[One (M7) Original Android Development] majed19:
Been reading through this thread for a while, just to make sure i got this right...

1)It should be ok to install multirom on s-on, no? Seen some people already done that, i guess

2)LP based roms that uses "block_image_update" should be installed as primary then could be swapped other than that there should.be no problem installing LP as secondary?

3)any problems with 1.61 hboot?
[One (M7) Original Android Development] ziaulh.ch:
V28 b download link please. Cant find anywhere.
[One (M7) Original Android Development] nkk71:
1 & 3-> i guess so, since you're on hboot 1.61 already means your firmware is up-to-date for multirom, iirc hboot below 1.57 had problems

2-> yes correct, any ROM that uses block_image_update has to be flashed to primary and can then be moved to secondary.

dont forget to get the Fix File Contents (flashable zip) to avoid having your secondary ROMs "nuked" in case of a "restorecon -FR /data/media" as mentioned on page 61

look at my post above, it links to here: http://xdaforums.com/htc-one/orig-d...8-redesigned-gui-t2880887/page57#post58731640

all the files are linked in that post
[One (M7) Original Android Development] ziaulh.ch:
Cant flash this rom. http://xdaforums.com/htc-one/orig-development/rom-cyanogenmod-12-official-nightlies-t2995218

Any idea why?
[One (M7) Original Android Development] Lossyx:
http://xdaforums.com/showthread.php?p=60105410

This version of MultiRom doesn't support 5.0 ROMs as secondary. (Sense 5.0 roms is supported but not AOSP)
[One (M7) Original Android Development] ziaulh.ch:
HEH? I am using GPE 5.1 with this version of multirom as secondary. It DOES work with others but not CM rom I linked.
[One (M7) Original Android Development] Lossyx:
As I said it does not work with AOSP 5.0 roms, Google Editions isn't AOSP.
[One (M7) Original Android Development] alex26aly:
If I try to install a sense 7 rom and a 5.1 rom will it work?
[One (M7) Original Android Development] Lossyx:
I does work with Sense 6 and 5.x.x so it should with with Sense 7.
[One (M7) Original Android Development] mitchst2:
Sense7 works fine.

mitchst2
[One (M7) Original Android Development] majed19:
I got SD v5 sense 7 and GPE 5.1 installed
[One (M7) Original Android Development] Lossyx:
I'm thinking of porting MultiRom by myself (latest version) as this thread isn't going anywhere. But I'm little worried 'if' my phone can get bricked if I did something wrong in porting process. I only have 1 m7
[One (M7) Original Android Development] ziaulh.ch:
I wish Someone ports as I cant.
[One (M7) Original Android Development] mitchst2:
This still works why risk bricking your phone.

mitchst2
[One (M7) Original Android Development] Lossyx:
Because the newest version works better and you can install cm12 as secondary without installing it as primary, backing up ....
[One (M7) Original Android Development] mitchst2:
fair enough

mitchst2
[One (M7) Original Android Development] domicq:
If you'll use my device tree, should be everything fine. Maybe just software brick, what isn't nothing extra.
[One (M7) Original Android Development] nkk71:
getting closer :D ... i think :confused:

multirom compiles, so does twrp... twrp even boots (mostly) :eek::eek:

maybe soon-ish, had hoped to get this up before i travel, if i dont, then maybe when i get back :angel:
[One (M7) Original Android Development] mitchst2:
Good to see someone working on this. There's no panic take your time. We are all coping with what we have at present.

BTW thanks again for your context fix. Not mullered a ROM since you released that.

mitchst2
[One (M7) Original Android Development] nkk71:
thanks... unless i missed something (probably a lot ;) ) that fix still may be needed... hopefully i'll get there without any brick :o
[One (M7) Original Android Development] mitchst2:
Good luck.

mitchst2
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

I've tried your steps to get CM12.1 to boot but seem to get stuck in a perma-boot. Normally phone gets hot when generating dalvik cache (ART) during boot. If it's cold I tend to abort after about 5-10 minutes. Any advice.

Here's the error message I get at install (AICP in this instance) to primary. http://xdaforums.com/showthread.php?p=60989681

Do you change recovery?

Dirty Unicorns worked and boot time was normal for lollipop.

mitchst2
[One (M7) Original Android Development] nkk71:
Yeah, I've had no success trying it either as secondary (never bothered trying as primary though), but according to Tasssadar's changelog, this could be the issue:

MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)

However, on the brighter side of things, check out the extract of the recovery.log flashing CM12.1 directly to secondary:

[B][COLOR="Blue"]MultiROM Recovery version: 2015-05-25 p1[/COLOR][/B]
...
ro.twrp.version=2.8.6
ro.build.date=Sun May 24 16:23:42 EEST 2015
ro.build.version.incremental=eng.nkk71.20150524.142803
...
I:operation_start: 'Installing'
Installing ROM cm-12.1-20150525-NIGHTLY-m...
Creating folders and images for type 1
...
Changing mounts to ROM cm-12.1-20150525-NIGHTLY-m...
...
[B]ZIP uses block updates[/B]
Creating system.img...
...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
...
[B]Patching system image unconditionally...
writing 120935 blocks of new data
wrote 120935 blocks; expected 120935[/B]
...
[B]script succeeded: result was [0.200000][/B]
...
[B][COLOR="Blue"]ZIP successfully installed[/COLOR][/B]
Restoring mounts...

then (using multiom v29) it boots to the bootanimation, and stays on the animation forever :silly:

still need to get multirom v32 working though.... it compiles fine, but just doesnt exactly work (strike the "exactly" :eek: , it doesnt work yet)

I'm new to all this, so you'll have to bear with me :o
[One (M7) Original Android Development] mitchst2:
CM12, AICP, NOSP all the same........................................

Tried quite a few recovery versions without success. I'd be quite happy to install and boot using another recovery. Then restore multirom recovery and move to secondary. But I've yet to find anything that works.

mitchst2
[One (M7) Original Android Development] nkk71:
YAY :D

okay, had a little brain fart (or was it a large one :p)

(i was expecting something to be in place, whereas it wasn't) ... so took way longer than expected, but now updated successfully

for your viewing pleasure: CM12.1 flashed directly to secondary (no backup/restore/bla bla)

i've hardly tested, so unless anybody is in a rush, lemme do some testing tomorrow (if you want me to flash something in particular, please post the link to the thread and mention version number)

PS: if anybody wants the current test build, just lemme know, but at your discretion as always, i take no responsibility for anything going wrong
[One (M7) Original Android Development] mitchst2:
Well done that man.

I suppose if CM12.1 works these will too.

AICP

http://xdaforums.com/showthread.php?t=3026304

CARBON

http://xdaforums.com/showthread.php?t=3066364

NOSP

http://xdaforums.com/showthread.php?t=3118686

None of these work at present.

mitchst2
[One (M7) Original Android Development] nkk71:
tell me which one to test (slow internet here), then if you want, i can send you the test version.... i would like to improve it a bit... but if you like early releases, i have no problem with that
[One (M7) Original Android Development] mitchst2:
AICP.

I'd be only to happy to test this.

It won't nuke my current ROMs?

mitchst2
[One (M7) Original Android Development] nkk71:
i havent tested the "not nuking" the other ROMs, they still show up fine, just dont know about the restorecon issue.... that's why i didnt post the files.

downloading AICP "aicp_m7_lp-9.0-NIGHTLY-20150528.zip", will flash when done and report back.

my m7 isnt my daily, so i'm happy flashing stuff on it :eek:
[One (M7) Original Android Development] mitchst2:
Nice one.

mitchst2
[One (M7) Original Android Development] nkk71:
hmm, well (flashing directly to secondary, no blabla workarounds), my findings so far:

1- recovery log result:

script succeeded: result was [0.200000]
ZIP successfully installed

2- nice bootanimation havent seen one that funky yet :cowboy:

3- "AICP is upgrading" actually shows which file is being upgraded (nice :))

4- is the Settings -> About supposed to look like this :confused:

if yes, then YAY :D

... havent done any testing... so if anybody wants the files that's fine, but can't promise anything wont bork other roms, (or anything else; i havent even tested most of the functions in particular twrp backups)

i'll have to check that later :rolleyes:
[One (M7) Original Android Development] mitchst2:
Pm'd

Haven't seen the settings app for a while.

Seen plenty of the boot animation though lol.

mitchst2
[One (M7) Original Android Development] nkk71:
files sent, word of caution, it could be secondaries **could** get messed up, dont know if they were from before or after.... needs more testing :o
[One (M7) Original Android Development] mitchst2:
Cheers

I'll backup first

mitchst2
[One (M7) Original Android Development] Lossyx:
Nice job! I stopped porting after 20% done because I have too much other thing going on IRL :/

Good luck with testing :D
[One (M7) Original Android Development] nkk71:
i dont have IRL ... i have full fledged 4Mbps download

and [MENTION=4333421]mitchst2[/MENTION] seems to be doing some testing too (thanks :D), all good on my end, just never figured about that little brain fart
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

You're a genius dude.

So far tested.

Existing ROMs boot

MaxHD53

Dirty Unicorns

But best of all.......

Successfully restored Stock GPE5.1 direct to secondary.

Other ROMs still booting after restore.

Will test NOSP shortly.

Thank you for this.

mitchst2
[One (M7) Original Android Development] nkk71:
Thanks for testing

Hopefully I'll get a better build out in the coming days

Anyway Tasssadar is the one to be thanked, he came up with it.

And thanks to CT also
[One (M7) Original Android Development] mitchst2:
NOSP successfully installed.

All other ROMs still booting.

As for thanks.

I've bought the donation app.

But you deserve the thanks for working on our abandoned m7.

mitchst2
[One (M7) Original Android Development] Lossyx:
Any chance I can try the test version?

Thanks
[One (M7) Original Android Development] nkk71:
I'm off pc for tonight, the Dropbox links are still up
[One (M7) Original Android Development] mitchst2:
Just done a backup of Dirty Unicorns and restored successfully.

Anything else you want me to test?

mitchst2
[One (M7) Original Android Development] nkk71:
Nice, thanks for testing, so I guess everything seems to work.

i need to cleanup some stuff, then i can post a proper build.

BTW: looks like manually triggering a "restorecon" still mess up secondary ROMs for me, so i'll see if I can incorporate the FixFileContexts directly into multirom twrp.

If all goes well will post updated multirom later during the day :angel:
[One (M7) Original Android Development] mitchst2:
Multirom app still shows v29.

Will you be starting a new, clean thread?

mitchst2
[One (M7) Original Android Development] nkk71:
Don't know if it's worth opening a new thread, what do you think?

Anyway, once the new version is up and running, I'll try and check with [MENTION=3418703]Tasssadar[/MENTION] what he thinks about a new thread and updating the app.
[One (M7) Original Android Development] Droidcore:
No problem open new thread:)