yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] 5m4r7ph0n36uru:
[MENTION=3987079]remicks[/MENTION] thanks to your reply earlier I found out how to solve my problem regarding multiboot in connection with the new ROM version 3.28.401.6.

I endet up extracting the boot.img and editing the default.prop, as described here. After flashing the boot.img and backing up the ROM again, I have been able to install the Stock 3.28.401.6 ROM through "TWRP > MultiROM > AddROM > Backup" and choosing the backup containing the unsecure boot.img as secondary ROM besides my primary ViperOne M8.

I guess I should've done a little bit more reading :o
[One (M8) Android Development] jtommyj:
I had no trouble just downloading and installing 1.08 Sense. Just an FYI.
[One (M8) Android Development] Galaen:
Indeed, but I would hate to dirty flash my rom just to flash a zip to update my blacked out Google keep app or something silly like that.

Sent from my AT&T HTC One M8
[One (M8) Android Development] _moelle:
can someone tell me why auto-boot doesnt work even its set in recovery?
[One (M8) Android Development] ironbesterer:
Whenever I flash an AOSP rom in MultiROM, I get no signal and no WiFi. I have the Verizon variant. MultiROM is working, so I have no idea why I get absolutely no network connection on AOSP roms. On Sense, it's working just fine. :confused:
[One (M8) Android Development] fguerra024:
Hey so I'm a little confused about the compatibility of the latest 4.4.4 sense ROMs... I updated my firmware and installed SD v18 but it says I need patched kernel when I try to boot it. Is there a new patched kernel I can use?
[One (M8) Android Development] BIGWORM:
AFAIK, there is not patched kernel yet for 4.4.4. If you want MULTI-ROM, you'll have to switch back to a 4.4.3 ROM
[One (M8) Android Development] 5m4r7ph0n36uru:
It works using a 4.4.3 (2.2x.xxx.x) based primary ROM combined with the Stock ROM, if you'd do it like I described here.
[One (M8) Android Development] jcrompton:
Yes. As long as the new 4.4.4 Sense ROM is secondary there is no problem
[One (M8) Android Development] anthony92170:
I'm on sprint with base 2.16.651.4 as you see I am running a 4.4.4 as primary sense second and gpe 3rd. All work with no problems and all have kexec.
[One (M8) Android Development] Captain_Throwback:
The discussion was actually about 4.4.4 Sense, not AOSP ;).
[One (M8) Android Development] anthony92170:
Sorry for some reason I thought my sinless sense was 4.4.4 its 4.4.3 . but at least this can show people who say they can't run gpe asop ect in here as a primary.
[One (M8) Android Development] shorty1483:
Need your help guys. Using latest TWRP with Multirom. I try to add a secondary ROM from backup, when it points me to the backup folder the backup process (swipe to confirm...) does not start. It seems just as an empty folder, all backups I have on external SD. When try to restore the backups to primary everything works fine.

Any help is appreciated...
[One (M8) Android Development] donmarkoni:
Check this. ;)
[One (M8) Android Development] shorty1483:
As always you're a real hero ?

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] donmarkoni:
No, no, I'm just a humble newspapers reporter... Kent, but you can call me Clark. ;)
[One (M8) Android Development] fguerra024:
9

Thanks, this worked perfectly, didn't need to modify and inject any boot img jazz... ViperOne running as primary and Redbulled SD running as secondary.. Had to install the ElementalX sense kernel through ViperOne to get things rolling. :D

EDIT: looks like motion gestures don't work. Any ideas for a workaround or do we jusst need to wait for an updated patched kernel?
[One (M8) Android Development] HC4Life:
If you flash the kernel after installing MultiROM you will need to go to Advanced->MultiROM->Inject curr. boot sector so everything is installed properly, as it says in OP page.
[One (M8) Android Development] fguerra024:
I did that, still no gestures.
[One (M8) Android Development] Captain_Throwback:
That has nothing to do with MultiROM. That's a conflict between the kernel and ROM, I believe. Take a look in the ElementalX thread about that issue.

Part of it will depend on what you selected during the AROMA install.
[One (M8) Android Development] matmaneyre:
Excellent! Thanks a lot, I'll give this a shot. But it's only easy when you know how (and why) :laugh:
[One (M8) Android Development] fguerra024:
Actually everything I chose during the aroma setup was stock... So the problem isn't the options I chose, but simply just the kernel, from my understanding at least.

I kept sweep to sleep default and left gestures stock. Only other option was stock cpu performance (cooler) and gboost for games.

Still no working gestures. Now I did notice when I run the multirom app in the 4.4.4 sense rom, it says my kernel is not patched... I install the patched elementalx kernel through the app and get the same lack of gestures and it still says my kernel isn't patched...
[One (M8) Android Development] Captain_Throwback:
The kernel isn't compatible with Sense 4.4.4. That's probably (at least part of) your problem.

If you're talking about on Viper, I'm telling you there's a conflict between the Venom CPU control and the kernel's native settings (specifically relating to gestures).
[One (M8) Android Development] boringalex:
I have updated the first post with a multirom zip that doesn't hang on boot (for those having this problem). It does not have external SD support. You can use that one with internal storage until I can fix the hanging issue.

Link for the lazy
[One (M8) Android Development] shorty1483:
For swapping first and second rom, do I need a special amount of free space on internal storage or SD?
[One (M8) Android Development] darkboy654:
secondary rom on external sdcard

Have any chance of leaving the secondary rom on the external sd card? :confused:
[One (M8) Android Development] remicks:
Enough to house the old primary rom and the new secondary rom, so around 4gb or so for Sense rom but a bit less for GPE/AOSP.
[One (M8) Android Development] XotusBlack:
Works perfect on:

International M8 (Germany)

Stock Rom as base

TWRP and Multirom installed with multirom app works but Download Source is sometimes busy!

ElementalX Kernel M8 1.08

After flashing Kernel Re-Root required!

Thx for the Port!!

//edit

Slimbean Rom = works

Cyanogenmod 11 Nightly = works
[One (M8) Android Development] TarekElsakka:
Hey there

I have ARHD 20.1 (4.4.4) installed which I am going to use as my base ROM, but I was wondering how do I go about installing a custom kernel since the current ones only support up to 4.4.3?

And also in the main page it says "Stock Sense insecure (4.4.3): boot_m8_sense_insecure.img not tested properly!" so I am assuming this wouldn't work while I have a 4.4.4 Sense ROM installed? Can someone please provide any information regarding this? Do I need to revert to a 4.4.3 Sense ROM in order for things to work properly?

Thanks.
[One (M8) Android Development] NJGSII:
Not going to happen til source is released for Sense 4.4.4 base. Install any rom based as on that as secondary til then
[One (M8) Android Development] AnimusVoxx:
Getting a weird bug, I'm using aokp as my secondary rom but my daily driver and a gpe rom as my primary, when I charge my phone on aokp, it charges to 50 percent then stops charging, it will still be plugged in but not charging, at least it says it's not, now when I switch to my primary gpe rom it shows that my battery actually was charging just not showing it correctly in aokp, I can charge my phone on gpe no problem, anyone else experience this odd bug?
[One (M8) Android Development] TarekElsakka:
My main ROM is ViperOne and I tried installing Elix-R ROM as secondary but it just won't boot in. Anybody know why? Could it be because it is 4.4.4 based?
[One (M8) Android Development] ArtificialMusik:
Is use the new Elix-R rom and it works great for me as a secondary rom.
[One (M8) Android Development] TarekElsakka:
Well I had a couple of issues throughout the download so I am guessing I ended up with a corrupt ROM file. I'll be redownloading it. Thank you!
[One (M8) Android Development] remicks:
As long as the boot.img is insecure you can run it as a secondary rom but not as primary because it lacks the kexec patch.

What this guy said ^ lol
[One (M8) Android Development] anthony92170:
You can run 4.4.4 as primary and 4.4.3 as secondary with no problems all you need to do is use elementalx kernel for sense ROM. For aosp liquid kernel. I have a gpe sinless as primary and sinless sense as second.
[One (M8) Android Development] TarekElsakka:
Yeah, I thought I can until I tried running Elix-R (4.4.4 GPE) ROM as secondary and it just won't boot. I am not sure where the problem is, to be honest, I even redownloaded the ROM file twice in case it was a corrupt download. My main is ViperOne 2.5 (4.4.3) with Elemental X 1.08.

How can I run 4.4.4 as primary when the only available boot.img is for 4.4.3 and Elemental X only supports up to 4.4.3?
[One (M8) Android Development] remicks:
That's odd, I've seen screenshots of people running elixr as secondary. Maybe a firmware issue?
[One (M8) Android Development] anthony92170:
In the op there is a liquid kernel for soap then you can run 4.4.4 also elementalx has gpe 4.4.4 kernel if you want gpe as primary
[One (M8) Android Development] remicks:
Liquid kernel only runs on a couple roms, causes infinite phone fc on most aosp/cm based roms. Also the elemental x gpe kernel is available from the MultiROM app.
[One (M8) Android Development] anthony92170:
I tried on all aosp Roms no issues it is the gaps that are causing it
[One (M8) Android Development] TarekElsakka:
I'm not sure. I have the latest 3.28 firmware installed.
[One (M8) Android Development] remicks:
That's odd considering I run the same gapps on Liquid as I do on CM and other roms but I only get the phone fc on CM/etc with Liquid kernel.
[One (M8) Android Development] Captain_Throwback:
[MENTION=5565418]boringalex[/MENTION]

Your test MultiROM build has working brightness, which has been bothering me for a while. Of course now I need it with external SD support :).

P.S. You have a patch uploaded to fix brightness somewhere? I was merging in [MENTION=3418703]Tasssadar[/MENTION]'s latest commits for autoboot, but it's breaking my ability to boot some secondary ROMs.
[One (M8) Android Development] HC4Life:
It was the first time i did this, so i Have ViperOne as primary and MaximusHD as secondary rom, i made a backup of MaximusHD using the MultiRom recovery menu cause i wanted to install some mods, after flash the mods using the MultiRom menu i decided to restore my backup, but in MultiRom menu there is no option to restore only backup, so i hit the backup button and immediatly the back arrow button to comeback to mainmenu and i realized that i have the name of the rom in statusbar not the number of the recovery version. Then i made a restore normally using the retore option in mainmenu. Reboot and success.
[One (M8) Android Development] mlin:
Does that mean you got a replacement phone?

Auto boot would be a very nice feature to have.
[One (M8) Android Development] Captain_Throwback:
Is auto boot not working for everyone? It's always worked for me.

(unless I misunderstand what that feature is)
[One (M8) Android Development] mlin:
Sorry, I guess I was thinking of auto boot for any selected ROM, not just the internal rom.
[One (M8) Android Development] Captain_Throwback:
Isn't that already an option? I have mine set to boot the last booted, but I thought these settings already existed and were working?
[One (M8) Android Development] mlin:
Weird. I don't seem to have this option. I installed everything from the app. Maybe I'll try the zip in the op.
[One (M8) Android Development] Captain_Throwback:
The option is in recovery, not in the app.
[One (M8) Android Development] mlin:
Oh yep, there it is! Sorry about that and thanks!
[One (M8) Android Development] boringalex:
MultiROM freezes when booting for some users. I don't know exactly what variant they are using. I hope I can get started soon on the bugfix...
[One (M8) Android Development] Sojourner353:
I'm one with the freeze problem, can take up to 5 tries before the device will boot, I'm also using the HK mod on my device which I think might be causing the issue.
[One (M8) Android Development] d3adbroke:
i had a question im helping a friend with a m8 with this installed and he would like to uninstall it can anyone point me to the directions?
[One (M8) Android Development] HC4Life:
In OP page u find the MultiRom uninstaller flashble zip.
[One (M8) Android Development] boringalex:
I posted a test multirom installer in the first post. You shouldn't have the freeze issue but you won't have external sd either (until it's fixed).
[One (M8) Android Development] Captain_Throwback:
Did you change anything to get brightness working in that version? I tried building with the latest source and couldn't get my secondary ROMs to boot.
[One (M8) Android Development] boringalex:
I didn't change anything. It's built using the same options I gave you a while ago (for the BoardConfig).
[One (M8) Android Development] nicholician:
I'm having an issue when trying to boot to a sense ROM from my google play edition device. Whenever select to boot to my sense ROM, it brings me to the bootloader screen, but when I scroll down the menu and hit reboot, it boots up just fine. This doesn't happen for any other ROM.
[One (M8) Android Development] Captain_Throwback:
You must've changed something - otherwise why would you have posted it as a new test version? I'm just wondering if something else you changed or a patch down the line is what fixed it.
[One (M8) Android Development] TarekElsakka:
I just tried flashing TeamEOS's ROM as secondary while ViperOne is the main and it still wouldn't work. That's the third failure in a row with three different secondary ROMs.
[One (M8) Android Development] remicks:
I'm not personally using multirom atm but here's a tip:

Don't flash secondary roms. Take the extra few minutes, backup ur current rom, wipe, flash rom to primary, move it to secondary, restore original backup to primary. This is what I did every time and the only issues I had with secondary roms were caused by the roms themselves.
[One (M8) Android Development] 5m4r7ph0n36uru:
[MENTION=5565418]boringalex[/MENTION] / [MENTION=1162986]Captain_Throwback[/MENTION]: sorry for this silly question, as maybe I missed something reading through this thread ... seem to be blind. I'm currently using multirom-20140922-v28-UNOFFICIAL-m8.zip. But if I'm running Stock 2.22.401.6 (ElementalX) as primary and install ViperOne as secondery onto ext_SD it doesn't show up on boot. As I'm guessing it should do so on the External Tab. But this tab keeps showing me the following:

​

while on internal tab - as is logical - only the stock ROM shows up.

Could you tell me what I'm doing wrong. Did I miss some setting in TWRP, or anywhere else?
[One (M8) Android Development] Captain_Throwback:
That's not the latest version of MultiROM v28. Download the latest version through the app. Though it's odd the ROMs aren't showing up, since you have an actual "External" tab.

Do you have a screenshot of the ROMs in recovery?
[One (M8) Android Development] 5m4r7ph0n36uru:
Thanks I knew I missed something ....

Edit: will do a reboot an make one.
[One (M8) Android Development] Sojourner353:
I will give it a look once I'm home from work today and let you know how it goes, cheers.

Edit: Just flashed the test version and the freeze issue is fixed, cheers.
[One (M8) Android Development] Captain_Throwback:
FYI I just updated the link in the MultiROM app to a freshly built version of the MultiROM zip. I figured out why brightness wasn't working and fixed it. I also pulled in a few commits from the master branch I noticed were missing.

To update just open the app, check the box for "MultiROM v28" and let the app take care of the rest :). If you detect any issues with this version, let me know.
[One (M8) Android Development] 5m4r7ph0n36uru:
[MENTION=1162986]Captain_Throwback[/MENTION] two calls later I finally got the time to get my screenshots. Here's what I get:

​
[One (M8) Android Development] Captain_Throwback:
Yeah, it should be showing up on the "External" tab. You can try the MultiROM zip I just uploaded and see if that makes a difference. I don't have any issues seeing ROMs on my SD card (though my card isn't formatted the same as yours).
[One (M8) Android Development] 5m4r7ph0n36uru:
Thanks will try it right away!
[One (M8) Android Development] jcrompton:
Any thoughts

I had the latest AndroidHD Sense 4.4.4 installed and booting as secondary. I don't recall why but I switched it back to primary and it booted fine. I tried to swap back to secondary and it won't boot - hangs at HTC One boot screen. If I swap it back to primary it will bit again. I even tried reinstalling on primary and then swapping back to secondary and it still won't boot.

Any ideas?
[One (M8) Android Development] HC4Life:
Thx Cap for this version but i have an issue, when autoboot a rom the screen turn off i have to press the power button to turn screen on but the rom boots anyway...i didn´t have this issue in the previous version.
[One (M8) Android Development] Captain_Throwback:
I'm not sure I understand the issue. When does the screen turn off? Can you explain completely what you mean so I can try to re-create?
[One (M8) Android Development] HC4Life:
Weird it only happened in the primary rom, when the rom boots i can't see the bootanimation, i have to press power button to wake the phone but when boot the secondary rom it is fine.

Edit: In the beginning the screen stays black for a few seconds but then the bootanimation appears...
[One (M8) Android Development] 5m4r7ph0n36uru:
No success with the new version and multiboot from external SD as well.

I tried two ways:

Delete and reinstall secondary ROM to external SD (FAT32)

After once more deleting secondary ROM, power down M8 > exchange FAT32 SD by ext2 formated SD > Power Up and reinstall

No problem to multiboot from internal. So Iguess I'll leave it that way for the time being.
[One (M8) Android Development] Captain_Throwback:
Yeah that's the old problem coming back to rear its ugly head . . . seems fixing brightness breaks the first half of the boot animation on the Internal ROM. I'll have to look into it more tomorrow.

---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------

Weird. Sometimes my External ROMs don't show up, but booting to recovery then rebooting makes them show up again.
[One (M8) Android Development] HC4Life:
Well it seems to me not a big deal cause the rom boots anyway...

Thx 4 your great work. ;)
[One (M8) Android Development] TarekElsakka:
Thanks for you reply. I am going to attempt this right now. I just have a couple of questions:

1) After backing up the ROM and then wiping it, I flash the GPE one I want and then move it to secondary immediately or should I boot in it first?

2) How do I actually move it to secondary?

3) When I want to restore my backup, do I just do so after moving the earlier ROM to secondary and then restore ViperOne backup and then "inject current boot sector"?

4) What about the .img file I flashed before installing MultiROM (4.4.3 unsecured image), do I just keep as it is or what?

Basically, I want my main to be Viper One 2.5 (Sense 4.4.3) and secondary to be Elix-R (GPE 4.4.4). Thanks!
[One (M8) Android Development] AnimusVoxx:
Wow now I remember why I never ask questions in this thread, because when I do nobody helps, thanks for the feedback guys, this is why people use XDA less and less everyday.
[One (M8) Android Development] remicks:
1) Doesn't matter honestly, either way works fine.

2) In the MultiROM menu there is an option called Swap Roms.

3) Yes

4) You need the correct kernel for the rom you will be running as primary. Sense for Viper, GPE for GPE etc.

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

What's your problem that you are having?
[One (M8) Android Development] TarekElsakka:
Thanks man. I tried that and when I installed gpe as primary it booted fine however after moving it to secondary and then restoring viper as primary and injecting current boot sector, gpe won't boot in.
[One (M8) Android Development] Galaen:
It's probably nobody has experienced your charging bug or knows what's happening. Personally, I have gone through many secondary roms, including the one from g+ that is a continuation of Task650's rom, and have not had this issue.

Sent from my AT&T HTC One M8
[One (M8) Android Development] remicks:
For what it's worth I have NEVER used that inject boot sector, ever.
[One (M8) Android Development] AnimusVoxx:
That rom is my rom and I understand that maybe not anyone has had that issue but it still would have been nice to hear if people had or hadn't had the bug, I'm was just trying to narrow it down to a specific issue if it was something in my rom or if maybe it was something with multirom or possibly just my phone, thank you for your input, glad to see people on XDA have actually heard of my work, hope you like it.

---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------

http://xdaforums.com/showthread.php?p=56009962
[One (M8) Android Development] Galaen:
I thought it was your rom, but wasn't completely sure. I do like it, and can't wait to see what else you have in store. As for your charging issue, I have no idea. I am no expert, but I can say this: my friends say that my phone should have herpes from all of the roms I go through. Saying that, I haven't had the issue, and I full wipe probably more than required. So, for the more experienced and curious, here is his original post:

http://xdaforums.com/showthread.php?p=56009962

Sent from my AT&T HTC One M8
[One (M8) Android Development] boringalex:
It's a new test version because it tests the boot freezing for some users. Other than that, I made no changes to the tree I have on github.
[One (M8) Android Development] remicks:
For what it's worth I had some weird battery bugs, recovery would show 35% battery but booting into Sense or CM would show 90-100%. I believe it's just something to do with how the battery stats are reported to the rom. Try using a battery app like gsam or something to see what your actual battery capacity is showing between roms. As for a fix I'm super clueless as I'm not a Dev for this project (hell I'm not even using it right now), just a user trying to help when I can. Maybe try mentioning [MENTION=5565418]boringalex[/MENTION] in your post for added exposure?
[One (M8) Android Development] Captain_Throwback:
Yeah I figured it out - it was a TWRP build flag, not a MultiROM flag. But it's also the flag that causes the boot animation on the Internal ROM to show up dark at the beginning, so I need to see if Tassadar knows how to fix it.
[One (M8) Android Development] Captain_Throwback:
Maybe this is a silly question, but would everyone rather have working brightness in the MultiROM boot menu, or a fully working boot animation on the Internal ROM?

I'm thinking the latter, but I figured I should ask anyway. I added some additional missing patches to the MultiROM source and in the meantime built a version that excludes the brightness fix. So I'm thinking I should push this version, unless people would prefer to have the brightness control.
[One (M8) Android Development] HC4Life:
Sincerely i prefer a fully working boot animation but it's my opinion.
[One (M8) Android Development] Captain_Throwback:
So do I. I updated the MultiROM zip in the app to fix this.

I have a question for people on either the latest or previous (9/28) versions - when you try to use a button combination to save a screenshot on a secondary ROM, does it save? I think the answer may depend on the location of your secondary ROM as well (internal vs external storage).

I want to see if any of the patches I merged broke something of if it's this way for some other reason on my ROM.