yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] formula84:
Until the op fixes the recovery what I was able to do was use two flashable recovery zips. One for the latest 2.6.3.4 twrp and the Second is the op recovery from first release v15.

Since I had 4.4.2 GPE already as my primary that I flashed under the 2.6.3.4 version. What I did was make a backup, installed sense 4.4 as the primary verified everything was working with it prior to flashing the multi Rom mod.

Then flashed the modified recovery from the zip and the multi Rom zip. After flash used the twrp reboot menu to reboot recovery.

From the multi Rom recovery I was able to add an additional Rom from my backup. Then injected current boot sector, reboot system. This worked beautifully.

Oh and I had elemental x as my sense kernel since primary kernel needs the patch.

With my work around you are able to flash any 4.4 Rom and use the backup as the additional Rom installs...

1. backup your current primary completely...twrp

2. Wipe it and install the additional Rom of your choice.

*This part is done by the regular twrp 2.6.3.4 to flash a 4.4 primary Rom

3. Make a backup right after first boot (you can even power down prior to completion of setup to keep it as a fresh install.

4. Restore your desired primary Rom you made a backup of earlier.

5. Flash modified 2.6.3.0 multi Rom recovery, reboot recovery.

6. Add Rom from backup.

7. Inject current boot sector.

8. Reboot system and you should now see the boot menu with Rom selection.

Some things to keep in mind, you do not need to keep reflashing the multi Rom zip one that is installed it remains through this work around...just as does existing multi Rom settings and Rom selection and data...So there is no harm in trying it this mod it's pretty low risk.
[One (M7) Original Android Development] Giblet-dono:
Fantastic! I already thought about trying this, but.. Well I'm already in my pajamas..

Fantastic that you tried and reported back!
[One (M7) Original Android Development] Freak07:
yes. 10.8 as far as i remember.

Gesendet von meinem HTC One mit Tapatalk

---------- Post added at 08:27 PM ---------- Previous post was at 08:23 PM ----------

yeah thats pretty much what i did. now running asylum rom as secondary and renovate 4.4 sense svn build as primary rom and everything works great so far.

thanks for the help guys.

Gesendet von meinem HTC One mit Tapatalk

---------- Post added at 08:28 PM ---------- Previous post was at 08:27 PM ----------

does it work for you to automatically sync in background? I had to sync manually everytime i switched roms
[One (M7) Original Android Development] Giblet-dono:
Manual sync here aswel
[One (M7) Original Android Development] jawonder:
For some reason Renovate 4.4 won't boot for me it's stuck on the Renovate boot animation .
[One (M7) Original Android Development] Giblet-dono:
Yeah the mod is not 100% stable..

For me Android Revolution HD GPe as secondary spits out an error message on boot

TripNDroid TripKat works flawless, as does Omni..

But now my primary ViperOne Shows very weird colors (inverted) during boot, and doesn't seem to boot at all.

So I think there are some problems with the current implementation of the mod, but it does work on other points so..
[One (M7) Original Android Development] Freak07:
thats quite strange because i could not flash trip kat. It would hang forever on md5 check while flashing. but got asylum to work. :)
[One (M7) Original Android Development] jawonder:
Which Elemental Kernel you use ?.
[One (M7) Original Android Development] Giblet-dono:
Lol for me Asylum spits out an error just after install.

I am using my main rom ViperOne with ElementalX 8.2 (8.3 gave me a problem)

On the GPe I use the stock kernel

-> After restoring my ViperOne backup It boots properly with proper colors
[One (M7) Original Android Development] jawonder:
So you use GPE as secondary and check do not share Kernel ?.
[One (M7) Original Android Development] Giblet-dono:
Yeap
[One (M7) Original Android Development] HTCCT:
I have no modified the updater skript in zip file of miui Rom, to eliminate the get proper build ....assert failed...error and it worked.

But now I get the following error message: failed executing update binary in zip

The installation fails.

What's now wrong xD ?!

Greets
[One (M7) Original Android Development] Giblet-dono:
Try the following:

http://d-h.st/Eim

It already has the check removed, and I have tested it, works 100%

I also wanted to say that for me Android Revolution HD roms do NOT work..

This is most likely due to the build.prop tweaks the roms incorporates
[One (M7) Original Android Development] HTCCT:
Have downloaded and flashed it yesterday but no changes ...I get the error above.
[One (M7) Original Android Development] Giblet-dono:
Impossible I only uploaded it today..

Please use MY download in the above post

It's already edited, tested and ready to flash
[One (M7) Original Android Development] HTCCT:
Ok I'll try.
[One (M7) Original Android Development] jawonder:
Yeah after i install ElimentalX 8.2 Android revolution won't boot, also I can't get Vioer or Renovate to boot even when i'm not using MultiRom to install them . I have CM11 and Omni in MultiRom and they are working ok just can't get the main Sense Rom to boot .
[One (M7) Original Android Development] Giblet-dono:
Android Revolution HD messes with the mod in such a way that even my primary rom won't boot after I install ARHD as a secondary..

Only when I restore My backup it will work..

Other GPe like 'HTC One Nexus Edition 2.0" does work properly
[One (M7) Original Android Development] jawonder:
I always install sense rooms as my primary as they normal don't boot in MultiRom and if they do they start to fC after a while .
[One (M7) Original Android Development] Giblet-dono:
I also have a sense rom as primary (ViperOne)

But I want to be using My primary as my day-to-day rom

And a secondary as testing, to test new versions of android and sense, and some other things

I would actually like to make a rom compatibilty list!

And I am going to..

So if anyone likes to help just fill out the following form:

Primary:

Rom Name:

Rom Type:

Base:

Android:

Sense:

Kernel:

Working:

Secondary:

Rom Name:

Rom Type:

Base:

Android:

Kernel:

Working:

Sense:

For instance:

Primary:

Rom Name + Version: ViperOne 3.5

Rom Type: HTC Sense

Base: 3.62.401.1

Android: 4.3

Sense: 5.5

Kernel + Version: ElementalX 8.2

Working: Perfectly

Secondary:

Rom Name + Version: TripNDroid TripKat 016

Rom Type: AOSP

Base: KRT16M

Android: 4.4.2

Sense: -

Kernel: TripNDroid Kernel

Working: Perfectly

Secondary: 2

Rom Name + Version: Omni Official 19-12-2013

Rom Type: AOSP

Base: -

Android: 4.4.2

Sense: -

Kernel: CM10.2?

Working: Perfectly
[One (M7) Original Android Development] HTCCT:
[MENTION=1662843]Giblet-dono[/MENTION]

I have tried your multi rom zip, but still the same error with failed execute updater binary.

But it is not a mistake of multirom !!!

I have removed multi rom by a factory reset, reinstalling my viper one rom and flashing twrp 2.3.4 recovery and then exactly the same error message. (The error message with device verification is gone by your zip and/ modifing the updater skript)

It seems to be a failure of twrp or the miui rom zip or maybe both.

By the way multirom mod is working for me ( i can choose for example viper one again as my second rom and it works)

I think something is wrong with miui.

Any other opinions :D

Thanks for help.....miui f*cks my phone :D
[One (M7) Original Android Development] Giblet-dono:
Ah it was a misunderstanding, i thought the Multirom zip gave the error..

But it was the Miui zip

I also have had some problems with miui, and there was only one very old version working for me
[One (M7) Original Android Development] HTCCT:
Yes, I thought so too.

But I have tried it with another version of twrp recovery and without multirom zip and the error, while flashing the miui zip, still exists.

The thing is that i only want to have miui because it is so eyecatchy. equally like colour os and ubuntu touch, but these arent working too :D

Now I think I`ll try a AOSP rom as second rom.
[One (M7) Original Android Development] Giblet-dono:
If you want eyecathing try to use an AOSP (like TripKat) and install the "themer" app

It is great! and eyecandy!
[One (M7) Original Android Development] HTCCT:
Which TripKat you mean, because the newest (android 4.4) isnt a still a daily driver, inst it ?!

themer app ?....can u post a link please :)
[One (M7) Original Android Development] Giblet-dono:
Themer I use: https://play.google.com/store/apps/details?id=com.mycolorscreen.themer

TripKat I use: http://xdaforums.com/showthread.php?t=2519054

And i don;t see why it shouldn't be daily..

As far as I can tell everything works, and it works FAST

Especially when you enable ART in developer settings..

I however do not use many apps on it..
[One (M7) Original Android Development] HTCCT:
Whats ART ???
[One (M7) Original Android Development] Giblet-dono:
http://source.android.com/devices/tech/dalvik/art.html
[One (M7) Original Android Development] HTCCT:
[MENTION=1662843]Giblet-dono[/MENTION]

Now miui works for me :D

It was JUST a bad download caused by a wrong md5 xD

I have miui now as primary rom and will install tripkat with themer beta as second rom :)

One question: Can I share sms data between the roms ? I mean if i receive messages on one rom, can i see it on the other rom ?!
[One (M7) Original Android Development] Giblet-dono:
Not directly but you can with a synchronization app..

I use SMSBackup+ https://play.google.com/store/apps/details?id=com.zegoggles.smssync&hl=de
[One (M7) Original Android Development] Vitruvian:
Can u please post the exact steps on how did u manage MIUI to work, couse i've tried yesterday and it did not work, i ended up with a boot loop?
[One (M7) Original Android Development] HTCCT:
I have made a backup of my existing sense Rom.

Then I have done a factory reset via twrp recovery and installed miui as normal Rom.

After booting miui I have flashed multirom recovery image via flashify and booted into modified recovery

Then I have flashed multirom zip and booted up again.

---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------

@Giblet-dono

Which kernel do you use at tripkat ?
[One (M7) Original Android Development] jawonder:
Which Kernel did you use for this ?.
[One (M7) Original Android Development] Vitruvian:
Thanks... but, what kernel did u use?
[One (M7) Original Android Development] HTCCT:
nothing that worked :(

I thought it will work with one of the newest elemental kernels, because it seems so, but then it stucks after booting miui at °starting apps°.

sorry guys. Both roms arent possible together at the moment, becuase there is no kernel which is compatible with miui and tripkat
[One (M7) Original Android Development] jawonder:
That's why i asked because i tried and it didn't boot with Elemental .
[One (M7) Original Android Development] Vitruvian:
Yes i've tried with elemental too, it didn't boot :(
[One (M7) Original Android Development] jawonder:
Well guess i'll just wait for MultiRom to be updated .
[One (M7) Original Android Development] Vitruvian:
Yes, me too :(
[One (M7) Original Android Development] formula84:
Are you guys both trying to get miui to be a secondary? I'd so you use stock kernel as you only need a modified kernel for the primary.

Here is what I would try...

From regular twrp install and have miui functional... Then make a backup from recovery.

Now flash the multi Rom setup and do a primary Rom that had working kexec kernel.

Then once this is working reboot to recovery and add a Rom from backup.

More then likely the issues with some roms breaking during install of multi Rom as additional is either do to recovery version is too old or the installer is incompatible too big...

I posted a work around a page or two back this is how you can get around the problem roms by installing them as primary just temporarily to get a backup through twrp... I believe the add Rom from backup will have the best results because it's a image based restore rather then scripts and such with those funky aroma installers.
[One (M7) Original Android Development] jawonder:
Yeah but which rom has the working kexec kernel . The roms inside MultiRom works fine for me i used CM11 and Omni, the problem is with my primary, i used Viper, Renovate and ARD with ElementelX and non would boot . I also tried restoring a backup of Miui in MultiRom and as primary and no go .

Don't know what's the deal as Viper use to be my Primary in MultiRom . If i use CM11 or Omni as my Primary they work fine only i can't boot into the roms in MultiRom because it's asking for Kexec which i don't have for CM11 and Omni. ARD flashes and boot's up one but it's stuck on boot screen with Elemental Kernel .

It seems switching between different recoveries has broken something because even my backup of Miui won't work with the regular TWRP and it was working a few day ago . I tried flashing Miui with the recommended TWRP 2.6.3.0 and it won't boot . Something went wrong somewhere because this was working before i tried MultiRom again yesterday .
[One (M7) Original Android Development] lcvdb:
I did this last night. I had InsertCoin 7.0.6 as primary Rom with ElementalX 10.8 kernel and a twrp backup of MIUI as secondary Rom. When i selected MIUI to boot it would reboot, show a black screen for some seconds and then reboot again to the Rom selection. So that didn't work. I did get HTC One Nexus Edition 2.0 (GPE) to boot as secondary Rom.

I then installed MIUI as my primary Rom from the same twrp backup, installed the MultiRom zip and it would boot just fine. I couldn't boot into a secondary Rom however because i couldn't find a 4.2.2 kernel with the kexec patch. But that could just be me being stupid.
[One (M7) Original Android Development] Giblet-dono:
I use ViperOne as my primary with ElementalX 8.2, version 8.3 would not boot for me (with ot without multirom)

It has always been my primary..

I still need to test miui with the new Multirom as a secondary... But I'm guessing it will work
[One (M7) Original Android Development] oFAMOUSo:
can i use this one the sprint version?

i see on the first page where it says that it should work on sprint if we're s-off and super-CID which I'm both.

i ask because when i install the custom twrp in the op and boot into recovery it doesn't show me my sdcard where i have the multiboot that needs to be installed.

thought I'd ask, thanks in advanced!
[One (M7) Original Android Development] oblikas:
That is a problem that I have to fix on latest recovery.
[One (M7) Original Android Development] nightwind84:
the recovery not work for me... i have flash by fastboot but the phone reboot when i try to enter in recovery...
[One (M7) Original Android Development] Giblet-dono:
Please use the "old" recovery for now with the new multirom zip (19a)

It works properly and can be downloaded here: http://d-h.st/XR9
[One (M7) Original Android Development] Mr. Droid:
I'm a little confused

Can we boot sense and aosp roms or different variations of aosp ?

Data shared between the roms ?
[One (M7) Original Android Development] oblikas:
CM and AOSP only for now.

Data is not shared between .
[One (M7) Original Android Development] leventccc:
I couldn't get gpe and sense working together because htc kernels doesn't have kexec-hardboot patch. I hope custom kernel developers can include the patch in the future releases.
[One (M7) Original Android Development] oblikas:
To use same kernel ,press share kernel while installing the secondary ROM.It won't ask again for kexec.
[One (M7) Original Android Development] leventccc:
I tried sharing first, it didn't give a kexec-hardboot error but it also didn't booted. It looked like booting to a sense rom not to a gpe rom because the bootanimation was from the sense system partition, not the gpe. It got stuck at the boot anim.
[One (M7) Original Android Development] jawonder:
So the main rom can be sense but roms flashed in MultiRom has to be CM/ASOP ?.

---------- Post added at 01:00 PM ---------- Previous post was at 12:23 PM ----------

Would like to do SuperCid and try this on my Developer One but waiting for you to resize TWRP .
[One (M7) Original Android Development] oblikas:
You can't use Sense ROMs at all.
[One (M7) Original Android Development] jawonder:
Ooh ok, because they are still gonna share Kernel, Thanks . So will you have the time to make the size adjustment to TWRP ?.
[One (M7) Original Android Development] oblikas:
I'll do it ASAP
[One (M7) Original Android Development] jawonder:
Thanks much, did SuperCid and now waiting .
[One (M7) Original Android Development] jawonder:
Ok so i went ahead and install MultiRom, my internal rom is Paranoid Android 3.99 RC2. I boot into recovery select Advanced/MultiRom/Add ROM, then tried to flash a CM10.2 zip and it failed, i tried with "don't share" Kernel and 'Share" Kernel and select Rom type as 'android" the same result the rom failed to flash .
[One (M7) Original Android Development] oblikas:
Failed to flash? Upload a recovery log.
[One (M7) Original Android Development] jawonder:
Ok so it did restore a backup of CM dated sept 10/13, so i'm gonna try to see if it has to do with the patch Kernel

---------- Post added at 04:31 PM ---------- Previous post was at 04:25 PM ----------

Tried again and this is what i get in recovery :-
[One (M7) Original Android Development] oblikas:
Unzip the ROM,open the updater script and remove assert lines from it then zip it again and flash.
[One (M7) Original Android Development] jawonder:
Ok 'oblikas" will try that and report back .

---------- Post added at 05:25 PM ---------- Previous post was at 05:09 PM ----------

So i removed the one "assert" line i saw which is "assert(getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" ||" and i'm still getting this error :-
[One (M7) Original Android Development] oblikas:
Upload the META INF folder somewhere.
[One (M7) Original Android Development] jawonder:
At work now might not be able to upload the META folder now .
[One (M7) Original Android Development] jawonder:
I think the problem is with CM , i'm at work but i just downloaded and flash Andy's Miui V5 and it went well also the backups i've restored are working fine .
[One (M7) Original Android Development] oblikas:
So you can boot more ROMs just fine ?
[One (M7) Original Android Development] jawonder:
Yes for sure, maybe it was that build of CM10.2 Nightly i'll try today's build when i get home.
[One (M7) Original Android Development] nightwind84:
but it's work with the kitkat rom? I knew that you had to have the 2.6.3.4 in order to work correctly...
[One (M7) Original Android Development] Giblet-dono:
It works with some, I still have not figured out why it works with some and not others..

For instance GPe: HTC One Nexus edition 2 work properly

But the GPe: Android Revolution HD GPe doesn't work properly

If you already have your primary rom setup (and is kitkat) it will work fine afterwards

and you can experiment aroudn with other roms as secondaries
[One (M7) Original Android Development] nightwind84:
i have viperrom 3.5 on primary rom... now i want try the asylum omni rom with other ;)
[One (M7) Original Android Development] Giblet-dono:
I have the same setup currently and it works fine for me.

May I also advise to try TripKat it is very very very fast!
[One (M7) Original Android Development] nightwind84:
thx I hope that the recovery will soon be updated ;)
[One (M7) Original Android Development] oblikas:
Can anyone test this updated TWRP?

http://d-h.st/Li3
[One (M7) Original Android Development] nightwind84:
this work! but is still 2.6.3.0... not 2.6.3.4...

edit i have problems... not show the list of the rom in the menù "multirom"...
[One (M7) Original Android Development] oblikas:
Now I know what's the problem... i will solve it right in the morning
[One (M7) Original Android Development] nightwind84:
but you can get an updated version to 2.6.3.4? thank you very much! :o
[One (M7) Original Android Development] dbaler:
To double check, you can have a sense rom as your primary? Lets say ARHD 4.4 Sense, could you use a 4.3 rom like AOSPA? Or can you not do sense and aosp. Or is it that you cant use different version numbers
[One (M7) Original Android Development] Giblet-dono:
basically everything is possible, this mod should support anything as long as you adhere to a few simple rules:

First rom must have a kernel with the Kexec patch, such as elementalX, Teamseven, or the CM kernel in the first post.

Secondary roms have no requirements, any SHOULD work..

Now there is one recovery limitation

If a rom needs the updated recovery (some 4.4) it MIGHT not work, it's up to you to test it yourself

If you want to use a 4.4 rom as primary and it needs the updated recovery you could try the workaround

First install it with the new TWRP recovery (without multirom)

make a backup of the full rom

Then flash the modified recovery, the rom and recovery should work out of the box.

If the rom doesn't work, you could always restore the backup.

And ofcourse some roms might just not work, ARHD does not work as a secondary rom (sense nor GPe) because it has some build.prop scripts which mes with the Multirom boot process

Miui has had some mixed experiences.

So with a lot of this stuff just backup your current rom and test it yourself, I have tested ALOT and I am in the process of making a post about what works and what doesn't
[One (M7) Original Android Development] h4waii:
Is there a v17 -> v19 changelog?
[One (M7) Original Android Development] Giblet-dono:
Mostly the RAM in seconday roms is fixed (previousl only around 800mb was usable for secondary roms)

And furthermore now you can use Sense and GPe roms as secondary roms
[One (M7) Original Android Development] snowblind2142:
quick question.

I've quietly followed this thread for a while now.

Last time I tried, I couldn't mount my USB otg cable with flash stick.

Just tried again, still no joy. Am I missing something?

It's the only think holding me back trying a load of roms to see what works.

Thanks,
[One (M7) Original Android Development] h4waii:
USB mounting works on v17, I have the updated kexec, so I don't plan on going to v19, but nothing in TWRP changed to break that.
[One (M7) Original Android Development] w3thax:
Will there be an update for TWRP 2.6.3.3? The new ViperOne 4.0 works only with this version.. And the v19a from this thread isn't flashable as mentioned earlier.
[One (M7) Original Android Development] Freak07:
Read back a few pages there's a possible solution posted. Basically first flash unmodified twrp that is able to flash viper. Then flash old modified recovery, New multirom zip and follow standard procedure. :)
[One (M7) Original Android Development] Giblet-dono:
To clarify, the above solution works when you want it as a primary:

Flash 2.6.3.3 TWRP

Flash Rom

Flash Multirom Zip

Flash Multirom Recovery

...?

Profit

To use ViperOne 4.0.0 as a secondary rom

You could try the following (untested by me)

Flash 2.6.3.3 TWRP

Make a backup of primary rom

Install ViperOne normally

Backup ViperOne

Restore your original rom

Install MultiRom TWRP

and restore the ViperOne 4.0 backup as a secondary rom

This SHOULD work but is untested as for now
[One (M7) Original Android Development] Ste98B:
Hi, has anyone found a way for booting in recovery with latest twrp with multirom? Does Oblikas know this issue?

Inviato dal mio One utilizzando Tapatalk
[One (M7) Original Android Development] Giblet-dono:
Well.. It has been mentioned a lot in the thread so yeah..

Oblikas knows and the "solution" is also out there..

For any 4.3 rom you can use the old multirom recovery

For 4.4 roms:

Primary:

Flash 2.6.3.3 TWRP

Flash Rom

Flash Multirom Zip

Flash Multirom Recovery

To use 4.4 as a secondary rom

You could try the following (untested by me)

Flash 2.6.3.3 TWRP

Make a backup of primary rom

Install ViperOne normally

Backup ViperOne

Restore your original rom

Install MultiRom TWRP

and restore the 4.4 backup as a secondary rom

This SHOULD work but is untested as for now