yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] jawonder:
What kernel do use to do this and which recovery , i thought KiIKat use TWRP 2.6.3.3 which MultiRom doesn't support . I used a 4.3 Sense rom as my main rom then try to restore a backup of AOSP kitKat rom which i installed with TWRP 2.6.3.3 . The backup worked for a little while then it froze on the startup screen .
[One (M7) Original Android Development] Ste98B:
Wow! Loving your work.

Inviato dal mio One utilizzando Tapatalk
[One (M7) Original Android Development] jawonder:
What version of MultiRom TWRP is it for ?. Ok never mind i see it's for 2.6.3.0 .
[One (M7) Original Android Development] Giblet-dono:
Oblikas is very busy with his school and will update the recovery later for multirom support, but this could take a while.

As of now you can flash some kitkat roms (TripNDroid works for me), but only those that are flashable with 2.6.3.0
[One (M7) Original Android Development] formula84:
Is there anything that you guys could share that would eliminate this memory issue? Reading these posts seems like you guys were able to fix the problem but I have not seen anything after this...

---------- Post added at 05:14 PM ---------- Previous post was at 05:06 PM ----------

Seems like we may be able to just replace this binary and that's it? A bit confused and would appreciate some clarification.

---------- Post added at 05:58 PM ---------- Previous post was at 05:14 PM ----------

Can I just take the kexec.txt file downloaded from that link off your github, remove the .txt extension and overwrite the one in the zip from the OP the folder structure is multirom-20132709-v1-m7ul.zip\multirom\ and just flash it? I no longer have multirom installed.
[One (M7) Original Android Development] Arcterus:
To fix the issue, download Tasssadar's kexec binary (the first binary posted) and use adb push /realdata/media/0/multirom path/to/downloaded/kexec.

Replacing the kexec in the multirom zip should work, too.
[One (M7) Original Android Development] formula84:
I did the zip replacement method and can confirm it's fixed the memory issues
[One (M7) Original Android Development] oblikas:
I will add it in the next version of multirom. thanks [MENTION=3418703]Tasssadar[/MENTION]
[One (M7) Original Android Development] shasen1235:
Ta Era Tassadar!!
[One (M7) Original Android Development] formula84:
Guess what else? I was able to get gpe 4.4.2 as an additional ROM rather then primary... Anyone else want to try to verify, I used one without aroma installer not sure if that is related.
[One (M7) Original Android Development] Giblet-dono:
Could you please ling me to the specific GPE thread you used?

Thanks in advance!
[One (M7) Original Android Development] formula84:
http://xdaforums.com/showthread.php?t=2568879

[ROM][DEC 13][m7] - Stock Rooted 4.4.2 - KOT49H.H1 - Google Play Ed. - Odex&Deodex
[One (M7) Original Android Development] Giblet-dono:
I just tried the odex as secondary.

For me it doesn't boot at all.

is there anything you did apart from installing it ?
[One (M7) Original Android Development] formula84:
Well my setup is not what most people would do... my primary rom was GPE stock 4.4 with elemental x 9 and I had and aosp rom as secondary working, then when 4.4.2 was released I wanted to check it out with stock kernel. So I flashed the linked odex rom as an additional rom and it booted.
[One (M7) Original Android Development] Giblet-dono:
There are a lot of variables here:

Which TWRP do you use? is it the one form this thread or a custom one?

Dit you use the standard multirom zip? or did you edit it with a new kexec file?

Now there is some mor eI don;t full understand

How does Multirom Handle kernels?

What is actually the reason sense/GPe roms don't work as secondary roms normally?

---------- Post added at 08:25 PM ---------- Previous post was at 08:10 PM ----------

I just took the kexec patch posted a few posts above and added it to the multirom zip.

I also removed the device check so everyone can install it on their M7

The recovery zip can be downloaded here: http://d-h.st/5vf
[One (M7) Original Android Development] formula84:
I think no one knows yet why sense/GPE do not work as additional roms , but I may be a step closer to helping figure out why...

I was wrong in that the secondary is fixed, the only reason it worked is because I had GPE as first and also as an additional rom...

It seems that the issue is that any Sense\GPE rom that is booted as a secondary is somehow pointing to internal rom system rather then the redirected one.

I know this because when I go into my additional GPE rom and delete something from system it is also gone from the internal one, but interesting enough the kernel verison / data / cache are using the redirected paths. It almost seems like a glitch in the mounts or something.

To recreate this use GPE as internal with. Kernel using kexec-hardboot and then flash the same GPE rom as a secondary but leave the stock kernel. When you boot the secondary GPE rom, it will be easy to tell that the data is not the same because you will have to go through setup as new, and no apps or settings are carried over, also look at the settings - about - kernel version you will see they are different. Now if you use root explorer to remove an app from system / app and then boot into your internal rom you will find it missing.

I guess this is why I thought it was working because it kinda was, but the sharing of system is not gonna fly for most.

I also tried Sense as my primary and GPE as an additional rom and found that when it rebooted it was still showing the sense boot splash and obviously did not boot.

May this info of proper redirect of everything besides system will help Devs that understand this mounting issue and possible offer a solution...
[One (M7) Original Android Development] Giblet-dono:
What I take away from this is that the secondary kernel points to boot the primary system partition..

In other wors, the path (Mount point) for the system mount might be hard coded in the kernel

So.. maybe we could contact some kernel developer to ask them if something like this happens and can be "fixed"

I am goign to check if Flar2 could give me some information
[One (M7) Original Android Development] formula84:
Great idea, would be great if a kernel dev got involved.
[One (M7) Original Android Development] Giblet-dono:
I send him a mesage just now

---------- Post added at 10:02 PM ---------- Previous post was at 09:14 PM ----------

I just noticed Faux123 was online on Googletalk

So I thought: Why not just ask him.

And so I did

He had some insights:

Well, the problem in Nexus 4 is that bootloader passes some ATAGs to the kernel during boot, if those ATAGS aren't parsed properly and passed the correct parameters to the kernel during early boot, the kernel will panic and reboot again.. so when you said it always boot to primary ROM, this probably is because it booted twice during kexec boot but kernel paniced, then rebooted to default kernel again. (This is how it is on Nexus 4 when Kexec failed)

I would look at msm_restart.c or something similar under /arch/arm/mach-msm/ Qualcomm has a pretty standard restart code BUT HTC ALWAYS screws with Qualcomm stuff and add their crap to it.. they probably did something there

This is best fixed in kexec patch, otherwise if done in kernel, it could lead to bigger issues when OTHER legit errors happened

Now I myself know nothing about kexec/kernel development, so I hope someone else can use this information to patch the Kexec patch (yo dawg)

And bring us Secondary GPe/Sense roms!
[One (M7) Original Android Development] tbalden:
Thing is that the Cyanogenmod and other AOSP kernels are rather based on HTC kernel sources for GPe with many-many patches on top of it...yet I don't think that it was fixed in AOSP kernels intentionally, to make it work, and AOSP kernels use the same kexec-hardboot patch too. You can try to compare the source trees of a Sense kernel and an AOSP kernel, and then you might see if there's a difference that gives explanation why it is working, but most probably there won't be such a difference. Anyway, worth a try, comparing AOSP kernel vs a vanilla Sense kernel

Wild guess coming: So the issue might be somewhere else, maybe in the ramdisk or something in the android framework of Sense is checking something additional...
[One (M7) Original Android Development] formula84:
Strange thing is this also happens on gpe as well as sense and from what I remember the gpe is no longer using HTC framework. But maybe something in ram disk.
[One (M7) Original Android Development] HTCCT:
Hey guys

One question ?

I have installed everything right now and the special boot screen pops up, but the thing is that on the first site of the thread is written I have to flash a special kernel which is attached at the second post but in the faq is written I have the proper kernel for my Rom eg. Sense Rom is elemental.

Which kernel should I flash ?
[One (M7) Original Android Development] Giblet-dono:
The special kernel is actually any kernel which has the Hardboot Kexec patch included!

ElementalX has it included, Teamseven has it also.. so it's actually your pick ;)

Also: if the menu pops up, and your primary rom boots normal, you dont have to flash anythign anymore, it already works as supposed =3
[One (M7) Original Android Development] formula84:
The thing with his input is that our devices do not panic and reboot, they are actually booting properly as long as Internal Rom System partition and additional Rom System are close or match.

I posted in the creator of MultiRom thread to see if he has any insight. I think that TBalden may be on to something with the issues maybe being in RamDisk as thats were all the mounting is done according to creator or multirom.
[One (M7) Original Android Development] Giblet-dono:
That's actually pretty good news, narrowing in on the actual problem!

Keep us up 2 date ;)!
[One (M7) Original Android Development] HTCCT:
Is miui Rom as secondary Rom possible ?

It is not sense based, isn't it ?! I only have to install it under add Rom in twrp or not ?!
[One (M7) Original Android Development] formula84:
Pretty sure MIUI is AOSP based, so it should work , cant hurt to try, yes you would just install as additional rom. Make sure to grab the updated zip posted to get the latest version so to not have memory issues on secondary roms, read the past few pages.
[One (M7) Original Android Development] HTCCT:
Ok thanks. What do you mean with updated zip exactly ?

I have downloaded the miui Rom zip from the first site of the mihi thread and the gapps ?!

I will try it tomorrow and report. Thanks so far
[One (M7) Original Android Development] formula84:
Look at this zip link above... use this one instead of the one in the op it has the updated binary.

---------- Post added at 08:55 PM ---------- Previous post was at 08:55 PM ----------

Look above
[One (M7) Original Android Development] electronical:
[MENTION=4870917]oblikas[/MENTION] Your ported MultiROM version is 15 and the latest official MultiROM is version 19. Could you please port the latest version which has loads of bug fixes and improvements? Thank you very much for all your effort. It's much appreciated.
[One (M7) Original Android Development] HTCCT:
I have tried the Updated zip which is posted above but I didn't work.

I get a error message in recovery . Something like... assert fail get proper build and installation failed.

Any ideas whats wrong !?
[One (M7) Original Android Development] Giblet-dono:
uhm.. it's actually impossible..

The assert check has been removed from the zip I uploaded (and that's the one a few posts above)

So, maybe redownload: http://d-h.st/5vf

-> Are you also sure you are flashing the multirom zip posted above and not the kernel or zip from the OP?

-> Please also check out the FAQ: http://xdaforums.com/showpost.php?p=46692680&postcount=132

---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------

You could try my updated package: http://d-h.st/5vf

I am not sure which parts are updated in v19 compared to v15, but it includes the updates kexec file

Which makes sure you can use all your ram in secondary roms.
[One (M7) Original Android Development] HTCCT:
I am using the venonom viper Rom 3.5 with the newest elemental kernel.

I have flashed the multi zip of the first post (later your updated zip) and the modified twrp recovery via flashify app.

Then it works because every boot up the special boot menu pops up.

Yesterday I wanted to flash miui Rom but this has failed three times with the error message.
[One (M7) Original Android Development] Giblet-dono:
Possibly, but that's not on us ;)

You could try to open the miui install zip, open META-INF folder

Open Com open Google open Android

And in there open updater-script with notepad/notepad++

There should be a line on top resembling: "assert(getprop("ro.product.device") == "M7UL" || getprop("ro.build.product") == "M7UL" || getprop("ro.product.board") == "M7UL");

You could remove the line, repackage the file in the zip and try to flash it..

KEEP IN MIND, THIS IS DANGEROUS!

You are effectively removing the "device check" to see if the zip is actually meant for your device!

So only do this if you are absolutley sure!
[One (M7) Original Android Development] HTCCT:
No, I will try another rom. I wanted only miui because it looks so pretty and because colour os isnt possible yet.

I have attached the whole error process for you. :)

Thank u
[One (M7) Original Android Development] Giblet-dono:
Yep the error is exactly cause by what I said in my last post.

It does a device check for the M7, your device might fail it because its an M7UL, M7TMO or another version

Which carrier do you use? and is your device carrier branded?
[One (M7) Original Android Development] HTCCT:
Ok that's strange. I have the Rom from here :

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

I thought if I root and unlock my device the branding is away. By the way the device is from Vodafone Germany.
[One (M7) Original Android Development] Giblet-dono:
I will download, check, test and report back, give me 30 minutes or so
[One (M7) Original Android Development] HTCCT:
THANK U very much ! ?
[One (M7) Original Android Development] Giblet-dono:
Sooo when editting the zip file it can install

But it does not boot Miui, it just boots my primary rom..
[One (M7) Original Android Development] HTCCT:
Ok. In other words that means miui or this miui Rom is unusable !?
[One (M7) Original Android Development] Giblet-dono:
Well.. One guy said he had it booting with another version previous in the thread..

It is an older version but does work: http://xdaforums.com/showthread.php?t=2352742

Still JB 4.2.2 Miui

I am goign to retry the current release later on
[One (M7) Original Android Development] oblikas:
Updated to v19 :)
[One (M7) Original Android Development] formula84:
Thanks Mate, donation (not much but something) is coming your way as well as Tassadar... I just spent some time with him in IRC and he fixed the mounting issues (Sense or GPE as additional roms), he said he would be pushing the changes to you soon. Its working wonderfully, now that we have this fixed this mod is 100% on our m7, thank you both.

---------- Post added at 03:05 PM ---------- Previous post was at 03:02 PM ----------

Thanks! 5DV6462091134843H
[One (M7) Original Android Development] oblikas:
Thanks a lot,much appreciated !
[One (M7) Original Android Development] HTCCT:
Thank u, but I have watched a video and there the Rom is laggy because it's just beta version.

The question is why this old miui works and the newer one not ?!

Maybe it will work with the newest multi Rom zip. I 'll try.
[One (M7) Original Android Development] formula84:
https://github.com/oblikas/mr_device_m7ul/pull/1
[One (M7) Original Android Development] Giblet-dono:
So do you already have a working version?

Could you share it?

---------- Post added at 09:35 PM ---------- Previous post was at 09:29 PM ----------

For me the V19 TWRP shows only empty folders, can't acces storage/SDcard
[One (M7) Original Android Development] oblikas:
It should be fixed now.

I have also merged Tass' pull request in the v19a.
[One (M7) Original Android Development] Giblet-dono:
After flashing the new twrp 19a I can't get into recovery anymore

The device just reboots

I already tried erasing cache from fastboot, it did not help
[One (M7) Original Android Development] oblikas:
That is really weird,i will try again 2moro after school,sorry for that
[One (M7) Original Android Development] Giblet-dono:
No problem, I know how to recover ;)

Take it easy and good luck at school tomorrow
[One (M7) Original Android Development] Freak07:
can confirm this.
[One (M7) Original Android Development] merrittj1989:
It'd love to see a 100% fully working & stable release of Ubuntu Mobile to use this to dual boot with OMNI if possible. That's the only thing I'd find useful work this vs 2 separate Android builds sharing no data together.

Sent from my One using the Tapatalk app that I...paid for?!
[One (M7) Original Android Development] Giblet-dono:
Well, than go and port Ubuntu ;)

This thread is not for rom/ubuntu development but soley for Multirom Development/help
[One (M7) Original Android Development] merrittj1989:
Don't believe that I requested ROM/Ubuntu development. Was stating my opinion that using this tool to dual boot 2 different systems seems to make more since vs booting 2 ROMs of the same system. I understand that different ROMs incorporate different features, it just seems to be a bit of storage waste to me. Others obviously find this useful, so that's awesome. Now, if it was possible to share user apps+data, call logs & message database between both Android ROMs, I would have 100% stuck to using this.

Sent from my One using the Tapatalk app that I...paid for?!
[One (M7) Original Android Development] MJFox78:
[MOD][01OCT]MultiROM for HTC One // Unofficial port // FIXED RECOVERY UI //

I'm new to this MultiROM-topic and not totally sure so here is my question: does this support kitkat ROMs? what is the difference to the MultiBoot solution?

Greetings

MJFox
[One (M7) Original Android Development] Giblet-dono:
It does support some kitkat roms (actually all I have tried)

But, some kitkat roms need an updated TWRP (2.6.3.3) and Multirom for now uses 2.6.0.3

Biggest difference is that multiboot makes datasharing between rom 1 and 2 possible.

And Multiboot only supports up to 5 roms, and this one potentially supports unlimited roms.

Apart from that the Multiboot mods lets you change roms from the OS

MultiRom gives the option during the boot proces.

I have found MultiRom to be more flexible

You can use any kernel that has the Kexec patch, and there are several AOSP/Sense/GPe kernels with the patch.

The Multiboot works as far as I know only on Teamsevens kernel

There are more subtle differences but i gues these are the most important..
[One (M7) Original Android Development] MJFox78:
thanks a lot for your detailed answer... would you mind to tell which ROMs you successfully tried?

greetings

MJFox

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] Giblet-dono:
Omni 4.4

TripNDroid TripKat

I haven't had the time or need to test others.

Keep in mind that only the first (primary) rom can be Sense or GPe

The rest can only be AOSP based for now

Also please read the FAQ before attempting a multiboot setup.

There is a treasure of information in there:

http://xdaforums.com/showpost.php?p=46692680&postcount=132
[One (M7) Original Android Development] formula84:
Not anymore sense or gpe can be additional roms.
[One (M7) Original Android Development] Giblet-dono:
Only when Oblikas posts an updated version

The version currently posted doesn't even boot into recovery for me.

He would update when he has time
[One (M7) Original Android Development] formula84:
You don't need the updated recovery for that to work that's part of the multi Rom zip you flash from recovery. V19a
[One (M7) Original Android Development] Giblet-dono:
I will try that, but why then is the recovery updated at all by oblikas to v19a?
[One (M7) Original Android Development] HTCCT:
Colour OS isn't still possible or not, because of the oppo recovery !?

Had any one tried it ?
[One (M7) Original Android Development] Freak07:
[MENTION=1662843]Giblet-dono[/MENTION]

if you test this would you be so kind and post your result here? for me the v19a.img of the modified recovery won´t work too.

and if your test is negative could anyone post the old modified recovery because i do not have this file.

thanks :)
[One (M7) Original Android Development] Giblet-dono:
Old recovery:

http://d-h.st/XR9

Old Multirom ZIP:

http://d-h.st/5vf

Still testing the rest, will report back

-> The New v19a zip works, and my primary boots without a hitch

-> Secondary (AOSP) also boots

-> Currently downloading a GPe and a Sense rom to test as secondary
[One (M7) Original Android Development] jawonder:
So you are saying if i flash the old TWRP img and the new Multirom zip it should work with 4.4 roms ?, also what about the "Kexec Patch" ?, it's still for CM10.2, have you tried it with 4.4 roms. I tried it with the old MultiRom zip and 4.4 rome and it didn't work .
[One (M7) Original Android Development] Freak07:
thanks for reporting back :)

okay just to clarify a few points.

i didn´t mess with this mod before. i´m currently running the newest twrp version and an renovate 4.4 sense svn build and elemental which supports multiboot (kexec patch).

i have to download and flash the "old" modified recovery.

within the modified recovery flash newest multirom zip and reboot. inject current bootsector. let primary rom boot.

boot to recovery install secondary rom.

are these steps correct? :)

and the recovery is able to flash 4.4 sense roms? :) because everywhere is stated you need twrp 2.6.3.3. following this thread for a long time. now is holiday time and i finally have enough rest to apply this mod.
[One (M7) Original Android Development] Giblet-dono:
You are missing but one step, make a backup before attempting all this ;)

Besides that I am very confident this should work properly!

I have not tried Sense /GPe 4.4 yet, and indeed everywhere is stated you need new recovery so i'd guess it won't work

GPE 4.4 is booting for me with the old multirom recovery and the new multirom zip
[One (M7) Original Android Development] Freak07:
backup already applied, sir :)

thanks for testing all this :)

so now hope [MENTION=4870917]oblikas[/MENTION] will find some time to look into the issue with newest recovery.

besides one more question. anyone know a convenient way to sync sms between the two roms? :)

had sms backup + (this : https://play.google.com/store/apps/details?id=com.zegoggles.smssync&hl=de) when i was on the other multi boot mod. but i´m curious if anyone knows about other solutions :)
[One (M7) Original Android Development] jawonder:
Are you using the latest version of Elemental ?
[One (M7) Original Android Development] Giblet-dono:
I have been using SMSBackup+ as you suggested