yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] throcker:
how to get NFC fc and phone fc roms working on multiboot:

flash rom, gapps and stuff you want as secondary

boot the rom

get NFC fc

reboot on recovery

flash the kernel you want (ex. I used team7)

reboot the rom...

and magically BAM no fc's
[One (M7) Original Android Development] tyessen:
Love the mod, used it on my Nexus 4 while I had it. I'm getting a 502 bad gateway while trying to download both files on my phone, so I'll try later from my laptop :)
[One (M7) Original Android Development] vedesh45:
Dirty Flash

you have to dirty flash AOSPA in orfer to fix FC's
[One (M7) Original Android Development] scrubsja:
I backed up the data on my secondary rom using the Multirom menu with the 1080_multirom_nexus.zip ui. I do not see the restore option.

Is there a restore option for secondary rom TWRP nandroids? Should I change the ui?
[One (M7) Original Android Development] z31s1g:
To restore a backup, you use the install function for secondaries, but choose install from backup rather than install zip.
[One (M7) Original Android Development] smouker:
I'm I right that I can't use a sense Rom as secondary!?

for primary im using onedroid and I want to use ViperOne as secondary... Ive got problems with the kernel patch for the sense rom... is there any way to get it working?
[One (M7) Original Android Development] michealderek:
Trying to install MIUI as secondary rom, but can not boot to system,

if make MIUI as primary system, then no kernel for the ROM, CM10.2 kernel can not be used on MIUI.

Also tried to install as backup, only MIUI set as primary can boot, but secondary can not boot. after swap primary/secondary, then Sense ROM can boot, but not MIUI.

Any idea for this problem?
[One (M7) Original Android Development] EaglesGPC:
MIUI is SENSE Based. ElementalX works fine :good:
[One (M7) Original Android Development] michealderek:
Thanks,

I tried to flash ElementalX for MIUI, it works fine for MIUI. But there is still a problem, the kernel for 4.2.2 does not contain kexec patch, which mean I still can not use the secondary rom.

MIUI for htc one only based on android 4.2.2, right? Is there a android 4.3 MIUI or a kernel with kexec patch for 4.2.2?

I have tried to flash 4.3 and 4.4 kernel, which made the secondary sense rom works, but MIUI stoped working.

It seems only 1 ROM can works correctly.........
[One (M7) Original Android Development] andybfmv96:
Okay so here's my dilemma x3 wondering if I still need super CID with this mod? (Im on tmobile)

I am on sense 5.5 android 4.3, is there a RELIABLE kernel with a kexec patch I can use for primary?

Can my secondary be a different android version from the primary?

Are we finally able to use sense as secondary w/ aosp as primary?

I'm late to the party and read the first 12 pages to get info. Sorry if this is a repeat.
[One (M7) Original Android Development] michealderek:
ElementalX is good for you.

I am currenty use sense (Viper 4.3.0) as secondary rom, primary rom is miui.
[One (M7) Original Android Development] andybfmv96:
So just flash elementalx for my primary (sense) then whatever I want for secondary? Do I still need super cid?
[One (M7) Original Android Development] navjot2785:
my primary rom is viper 4.4.2 nd secondry is probam 4.4.2.... but am unable to instal MIUI .. any help >?
[One (M7) Original Android Development] NightForce:
How do you go to become MIUI as primary and Viper One as secondary rom????? can you explane your steps please???? i love Viper One but also MIUI and i will run both roms on my HTC One. Please explane the way you go!!! :fingers-crossed::fingers-crossed::fingers-crossed:
[One (M7) Original Android Development] michealderek:
basically, install roms with normal recovery , do backup, then I installed multi ROM, use backup restored viperone as primary, swap it to secondary, then restore MIUI to primary, flash kernel elementalx 5,6, this kernel is for Android 4.3 sense 5, so camera will fc in MIUI, but since no kernel with kexec for 4.2.2 sense ROM, there is no better choice. now you can have both ROM run on your HTC One.

and if you found 4.2.2 kernel with kexec for sense, pls let me know.
[One (M7) Original Android Development] NightForce:
Thanks for your answer! I will test it! ?

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] TabascoJoe:
I have a Sense 4.4.2 Rom with teaMSeven2.3.6 kernel.

When I flash CM 11 as the secondary I get FC right away. NFC and Themes and andriod system.

I've been able to use MultiRom in the past without issue. It seems like this latest version has issues. Has anyone had success with Sense 4.4.2 and CM 11?
[One (M7) Original Android Development] Giblet-dono:
Please post an url to the CM11 build you used, I will test it
[One (M7) Original Android Development] TabascoJoe:
Here ya go: http://download.cyanogenmod.org/get/jenkins/56742/cm-11-20140127-EXPERIMENTAL-m7.zip
[One (M7) Original Android Development] Giblet-dono:
I can confirm the problems you have

Try to cold boot (reset) your device by holding the power button and boot into CM11 again

This time you should NOT be getting any errors

Please report back
[One (M7) Original Android Development] TabascoJoe:
That worked! Thanks
[One (M7) Original Android Development] colthekid:
Unrooted Rom

Hi all,

Tried this method a few times & it seems to work ok, but recently tried to install a "stock" unrooted sense rom (so I could use my banking app!) & I get a message about unable to unpack boot image.

Any ideas?

(I want the Unrooted rom as a secondary)

Cheers,

Colin.
[One (M7) Original Android Development] vettejock99:
So thoughout this thread there appears to be a number of us getting assert failed errors with a number of ROMs because the check is returning m7 and the ROMs are expecting m7ul, or m7att, or whatever. When I boot into bootloader mine, for example says m7ul as I intended, as I modified it from a m7att.

Anyway, if bootloader shows m7ul, and my ROMs expect this, then I'm thinking it must be recovery reporting it as m7? If so, can we get a modded version which reports m7ul?
[One (M7) Original Android Development] Headless96:
Just edit updater script and take out the assert lines. Worked for me when I installed the Ubuntu preview rom, wouldn't install without the changes

Just make sure you flash the correct rom for your phone, these checks were there to make sure you don't mess your phone up
[One (M7) Original Android Development] vettejock99:
I've been doing that, and it does work. I've just never had to do it before and I've always used m7ul versions. Some roms, however, like ProBAM, result in no radio signal for me if I flash their m7ul version (though 95%+ of the rest of the time m7ul works fine), so I have to flash the m7att version. Right now, without editing, the m7att version fails, as do both the m7att AND m7ul versions of Pac Rom. I didn't have these issues before, so I thought maybe the board ID this recovery is reporting might be different from what my regular TWRP 2.6.3.x recoveries were reporting.
[One (M7) Original Android Development] Headless96:
I have no idea about the radio issue since I've never encountered it, but there's a link in the FAQ that disables the check instead of having to delete assert lines for every single rom
[One (M7) Original Android Development] vettejock99:
Odd thing is I tried that at it didn't seem to work. Looks like CM11 just merged their device trees so now they're all m7, so maybe it will become a moot issue soon.
[One (M7) Original Android Development] vettejock99:
Any chance this will be updated soon? I'm running into issues flashing the latest roms with the 2.6.3.0 TWRP we've got. Looks like the Nexus is at v22 or higher. Thanks for any info, and for doing this in the first place!
[One (M7) Original Android Development] Giblet-dono:
Are you srue you are using the latest release?

v19 should be able to flash and use all the latest roms.

Please post urls to roms that you have ran in to problems with so I can test them.
[One (M7) Original Android Development] vettejock99:
Let me correct my potential error. I should say that after running Vipermod as primary and many non Sense roms as secondary for months, now trying any Sense or GPE rom, with or without any patched kernel in that slot, gives a bootloop or an error before it even tries to boot.....and I've tried about 6 with different kernels as well.
[One (M7) Original Android Development] Cr3a7eR:
Any luck with the Sprint variant? I flashed both of the recoveries but while tring to instal MultiROM.zip or wipe it says unable to mount /system /dalvic ...

And also I found out that when I put files in my /sdcard in MultiRom recovery files aren't there.
[One (M7) Original Android Development] vettejock99:
Looks like the behavior I'm experiencing is because these are 4.4 and not 4.3, and our MultiROM port can't do those properly, at least not as secondaries.
[One (M7) Original Android Development] Giblet-dono:
please let me know which secondary you tried so I can test them
[One (M7) Original Android Development] vettejock99:
AndroidNOW, SkyDragon, and Sinless. Thanks for taking a look!
[One (M7) Original Android Development] Giblet-dono:
Next time it would be a good idea to post which versions we are talking about, or preferably a download URL.

AndroidNow has a 4.4.2 version and a 4.4.2.1 version

I tested: AndroidNow_NG_4.4.0-10

Result: They do some funky stuff in their build.prop which messes with multirom initialization process (can't get app level)

SinLessRom has an ART and NOART version

I tested: SinLessROM_GPe_v6.4.0_NoART

Result: Has a TERRIBLE install script, it installs itself to a hardcoded block location! this is VERY bad practice, and could be potentially dangerous if flashed on a device with a different partition layout!

Sinless mounts the folloiwng way: mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/system")

In other words: mount block x as system

Then it formats system, and overwrites system (in other words it formats the block and overwrites it)

Normal installers mount like this: mount("ext4", "EMMC", "system", "/system");

In other words: let recovery find the right partition (called system) and mount it as system

Multirom would step in here and give the adjusted path to the system partition block

Skydragon has a GPe and a Sense version

I tested: SkyDragon v 10.0 Sense

Result: Will come tomorrow, as soon as I have restored my ViperOne after the Sinless disaster, they could better change their romname to SinnersRom
[One (M7) Original Android Development] vettejock99:
Holy moly that's good info. Sorry about the headache, but I couldn't imagine all 3 being bad. Guess I'll have to chalk that up to no more Aroma or no more Multirom. Thanks for the great info!
[One (M7) Original Android Development] Giblet-dono:
I also tested skydragon, and it has the same updater script problem as sinless

It also formats primary and tries to install to primary
[One (M7) Original Android Development] optimus0208:
I followed the instructions like

Install multiROM zip

Flash twrp

Flash kernel from 2nd post.

Then from recovery I installed cm11

Cm 11 works fine but I can't boot into my sense ROM. When I selecte the intermal ROM the screen goes black. I can't take logcat as adb can't detect it .

I'm sorry if I asked noob question.
[One (M7) Original Android Development] Giblet-dono:
It's not completley clear what you are trying to do

Please tell us:

What is your primary rom

What is your Primary kernel

What is your secundary rom
[One (M7) Original Android Development] optimus0208:
ROM : viperone 17 Jan update

Kernel : elementalX

Secondary Rom : cm11 official
[One (M7) Original Android Development] Giblet-dono:
Keep in mind Only the primary rom needs a kernel with the kexec hardboot patch, and ElementalX already has it included!

If you alreayd have ViperOne as primary with ElementalX as kernel do the following:

Install the Multirom Zip

Install install Multirom TWRP

Go into multirom twrp menu and add rom

Install the CM11 rom as normally

THATS IT!

ONLY the primary rom needs an editted kernel with the kexec hardboot patch

The secondary rom uses their normal kernel

PS, to fix your problem: Dirty flash ViperOne, and Dirty flash ElementalX afterwards

Then perform the steps described above to get CM11 working
[One (M7) Original Android Development] phazepiracy:
Hey guys,

i'm using multirom since some weeks now without probleme, but i noticed that when i flash as secondary rom PA or another KK rom, i get NFC force close before the rom start the first boot.(i have viper as a Primary rom with elemental kernel)

After some fails in fixing it, i deleted my sense primary rom and flashed these KK rom wich loaded quite well and workings on dualboot.

Am i missing something on the process ? i would love to stay on Viper as primary and let my secondary rom for testing or for a good KK rom.

Another thing, please could someone explain to me what is exactly to be done to dirty flash the phone if i want to get back to normal recovery and monoboot. ?
[One (M7) Original Android Development] Giblet-dono:
When you get the NFC force close, just reboot the phone holding the power button

The next boot should not give you the error anymore.

I have personally tested this a few pages back.

Please report back!

To get back to "stock"

First remove all secondary roms trough twrp > advanced > multirom > list roms > select rom and delete it

Second just flash your primary rom without wiping anything

This will keep your existing data, but will remove multirom

Last thing left then is to flash a normal twrp
[One (M7) Original Android Development] phazepiracy:
thkx for the quick reply, i'll test it as soon as possible, as i just get back to sense as primary.

i was little confused about dirtyflashing but it seems close to a normal one with a recovery change.
[One (M7) Original Android Development] optimus0208:
Thanks it worked. It's working fine with

Viper one and aokp. Will you explain how it works? please.. it's amazing. I really want to know where the secondary ROM is installed and how its booted.

Ps : I understand a bit about Android and I'm not a complete noob.
[One (M7) Original Android Development] Giblet-dono:
Not exactly true

A dirty flash is a flash without wiping

Maybe a dirt analogy but compare it to using the toilet ;)

dirty if you don't wipe

the recovery flashing part is something you normally don't do when you flash dirty, but it's nessecary to fully get rid of multirom

---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------

the method is quite neat

It works like this:

A normal boot (without multirom) first starts the bootloader

Then comes the kernel, which in turn starts the android operationg system

A Multirom boot has a extra stage

First comes the bootloader, as normal, then starts the kexec-hardboot-patched kernel

This kernel checks wether it's booting the first or second time

If it's the first time it will show the multirom menu, so you can choose your desired rom (kernel)

When you choose the rom (kernel) it will reboot, this time it's a second boot

So it will load the kernel of your choosing and boot the accompanying rom

Because of this only the first roms kernel needs the patch, that is the kernel that loads the menu

That is the kernel that gets booted every (first) boot to choose your desired rom (kernel)

All the data of "secondary" roms is saved on your data partition (your sdcard partition) in a directory named multirom

and all the multirom menu does is look for kernel files in this menu

Now have fun and enjoy your multirom, just don't forget to make a backup of your PRIMARY rom before flashing secondaries

some roms have very bad updater scripts which block the multirom install process and just install over the primary rom
[One (M7) Original Android Development] phazepiracy:
It worked with all roms, thankx mate and nice metaphore with the toilet thing... :laugh:
[One (M7) Original Android Development] sane82:
sprints htc one

Sorry I'm new to the HTC one system so I don't know much about it yet but I want to learn and I seen this thread but notice it is for the HTC one and not the Sprint HTC one. I did search the threads but didn't find anything helpful what I was wondering is there anyway to port this to the Sprint HTC One Any help would be helpful.
[One (M7) Original Android Development] Giblet-dono:
As far as I know the Sprint One has a different Partition layout, as such this rom will not work

Please do NOT test it, as it might softbirkc your phone
[MENTION=4870917]oblikas[/MENTION] might have more information regarding the subject
[One (M7) Original Android Development] rockyseenu:
In the FAQ it states, Android 4.4 is not supported. However i see few users have installed successfully. Hoping someone could help me in my issue. Please tell me what am i doing wrong.

1) I am currently in Sinless GPE ROM 6.4.0

2) As mentioned in OP, flashed teamseven kernel

3) Multirom recovery

4) multirom zip

5) added another ROM (Insertcoin sense) through advanced menu - selected not to share kernel.

6) Installation is successful. And selected reboot.

7) in the bootmenu even when i selected Internal ROM, i am getting insertcoin bootscreen and get stuck there.

multiple reboots only takes me to 2nd ROM bootscreen irrelevant of whatever i select in the bootmenu. Any inputs?
[One (M7) Original Android Development] Silver-1:
I'm wondering if this can be ported for the HTC one J m7_wlj, I installed it and that all goes well, boots to recovery but has an error seeing both the internal memory and the external microsd. Would be happy to help out any way I can to make this possible.
[One (M7) Original Android Development] Giblet-dono:
probably the same error that has been happening to a lot of users

The problem is not that it's android 4.4, it's the wat the rom update script handles partitions

I have not checked this as I have no (decent) internet now

I will check it when I'm back home (sunday/Monday)
[One (M7) Original Android Development] andybfmv96:
Any eta on when we can port a working multirom for 4.4? What needs to be fixed?
[One (M7) Original Android Development] sane82:
I had already tried before but no luck and no soft brick it just wouldn't let me load any ROMs or find anything on my SD card so I just reflashed my normal recovery and now everything seems to still be fine but thanks.
[One (M7) Original Android Development] Giblet-dono:
.. 4.4 roms already work.
[One (M7) Original Android Development] oblikas:
The partition layout is different on Sprint M7 so it will not work.
[One (M7) Original Android Development] Giblet-dono:
I checked and indeed Insertcoin also uses the wrong update script thing..
[One (M7) Original Android Development] d.kuyt:
I tried the combination of ViperOne 5.0.0 and SinLess v6.4.0

Having the problem of choosing the primary ROM will end up showing the boot animation of the secondary ROM's boot animation, and get stuck there

Sent from my HTC One
[One (M7) Original Android Development] rockyseenu:
Thanks for checking. If possible, can you let me know what exactly needs updating in updater script.

i will try making some changes in the script or let Baadnewz know to get it sorted.

Thanks again.
[One (M7) Original Android Development] Giblet-dono:
Trouble is, there is a little more to it..

So a partition can be hard mounted:

mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "0", "/system");

-> here the partitionblock

Or soft/variable mounted: mmcblk0p35 get's mounted to the directory /system

mount("ext4", "EMMC", "system", "/system");

Here the partition named system will get mounted to the directory /system

Now a partition can NOT be formatted when it is mounted

So it will first have to be unmounted

Formatting (as far as I understand) can only be done the following way:

format("ext4", "EMMC", "/dev/block/mmcblk0p35", "0", "/system");

In simpeler words: Format partition block mmcblk0p35 and mount it as /system

So as far as I understand it, when the "wrong" updater scripts get loaded they just format ther blocks and mount them

But the blocks they format are the primary partitions, used by your primary rom.

The only way to get around this is to make the wipe optional.

Like ViperOne has, last time I tried you could install ViperOne as a secondary without wiping it and it would work perfectly.

Another soulation you coudl try is just remove the formattin bits from a updater script and see if it runs..

I might be trying it later when I ahev some time on my hands..

p.s. The updater scripts aren't as dangerous as I previously thought, as they do check which device you use.
[One (M7) Original Android Development] andybfmv96:
Not as secondary I thought.
[One (M7) Original Android Development] Giblet-dono:
They do ;)

Just not all depending on their updater script they may or may not wipe and install to the primary partition
[One (M7) Original Android Development] rockyseenu:
Thanks a lot. I will try from my end too.

May be a stupid question - if the problem is only with updater script.

If i install a second ROM using nandroid backup, will it work correctly?

// i will check both these options when i reach home from work //
[One (M7) Original Android Development] Giblet-dono:
Restoring from a nandroid will work correctly
[One (M7) Original Android Development] andybfmv96:
Ohh alright. Does viper work as secondary?
[One (M7) Original Android Development] Giblet-dono:
if you don't wipe it should work..

but make a backup of your primary just in case
[One (M7) Original Android Development] andybfmv96:
Kk I shall not. Thanks a bunch
[One (M7) Original Android Development] gh_3210:
up
[One (M7) Original Android Development] Giblet-dono:
How does the One J differ from the One?

Can you flash normal One roms? -> Do they work properly?

Can you flash normal One kernels? - > Do they work properly?
[One (M7) Original Android Development] Frenix27:
Hi I have 2 questions:

1) I had 2 roms with this method. Now I deleted in recovery my second rom, so now it has been deleted succesfully?

2) Cause I want to try MIUI V5 but I know it's impossible use it as second rom, i thought: can I do a nandroid of first rom, install miui as 1 rom and restore backup done before as second rom?
[One (M7) Original Android Development] Giblet-dono:
1). Yes should be gone

2). this should work! and if not you can always restore your primary rom backup ;)

Please report back with the result
[One (M7) Original Android Development] s2k7:
One J kernel

The One J model (m7wlj) uses different kernel, you can find TAKO's work at

https://github.com/tako0910/android_kernel_htc_m7wlj

and his CM11 port at

http://android.slateblue.tk/viewtopic.php?f=26&t=154

Thanx for porting multiron to the ONE J model.
[One (M7) Original Android Development] Silver-1:
You said thanks for porting multirom to the HTC J one, did someone actually do it? I so would love that. Do you have a link?

Thanks

Ron

---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------

The htl22 has a internal miniSD slot, and it's file structure is different, like the sprint HTC one. I am running Viper rom 5.5.1 on mine. It works great.
[One (M7) Original Android Development] Giblet-dono:
No it has not been done, but I was exploring the possibilities..

Trouble is that oblikas has very very very little time with his studies.

Plus he does not have the device.

As such YOU will need to provide any and all information about the device,,

Is it possible to send (pm) me a list of the partition layout of the device?
[One (M7) Original Android Development] Silver-1:
I sent you a PM with the layout of my device.

I hope it will help.

Thanks

Ron
[One (M7) Original Android Development] Toxicoblivion:
Can we flash 4.4.2 roms with this?
[One (M7) Original Android Development] Giblet-dono:
yes

see my signature for my setup
[One (M7) Original Android Development] Actuamy:
Any update about this MultiROM?
[One (M7) Original Android Development] Giblet-dono:
Update for what?

Basically everything works

With exception of:

Different models (like the HTC One J)

and some Roms are not installing properly due to their updatescript