yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] TheBurgh:
Only speaking of recovery at this point. How has your experience been?
[One (M8) Android Development] jcole20:
I'm not using throwbacks 2.8.6 recovery but the 2.8.6.1 (more up to date) version has a new splash screen but works great and secondary boots without going to bootloader. So definitely better.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] TheBurgh:
Much appreciated. Did you update the recovery through the apk?
[One (M8) Android Development] jcole20:
I used MultiRom Manager from the Play Store to update.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] jcole20:
HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

Edit: sorry I meant to edit that last post not quote.
[One (M8) Android Development] Tech_Savvy:
where do i find 2.8.6.1?? my multiboot find the 2.8.6......5-20.15
[One (M8) Android Development] jcole20:
If you download MultiRom manager from the play store it will update it through the app.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] Tech_Savvy:
I tried...the same one i put a link up came up....
[One (M8) Android Development] jcole20:
Well if that's the case cool... The newest version is 2.8.6.1 but if you use a theme it probably won't show the right number because the number is part of the theme. But the recovery splash is different

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] Tech_Savvy:
I've tried that one it it reboots to bootloader again when selecting the rom? its doable bt i'd prefer if it would work like yours...:p
[One (M8) Android Development] Captain_Throwback:
There is no 2.8.6.1 version. MultiROM recoveries use a 3-digit version number, along with a date. I don't know where you're getting 2.8.6.1 from.

I have explained several times in this DEVELOPMENT thread that just because the MultiROM version number doesn't change (i.e. v32) doesn't mean updates haven't been made - especially if there's a different date on the file. For every release I've posted in the thread for testing, I've explained what the changes were. It's a known issue that v32 currently has broken/wonky touch on secondary ROMs. That hasn't and won't change until [MENTION=3418703]Tasssadar[/MENTION] makes the necessary update to the kexec-tools source. I've said it several times. When v32 is fully working, the app will be updated with it. Until then, I will continue to post test versions in this Development thread as I find/fix other issues.

For kernel devs, if they'd like to support encryption with MultiROM, they will need to build dm-crypt into the kernel, rather than as a kernel module - otherwise trampoline can't find the dm-crypt table to decrypt storage.

I can either keep posting test versions here for people that are here to help with Development, or not. But having you say no one should use a version posted is in direct opposition to the purpose of this thread. So please understand this is a Development thread and that's what it is for. I understand the OP hasn't been updated in ages. [MENTION=5676253]fizbanrapper[/MENTION] has agreed to update the OP (which is long overdue) and I hope that'll help reduce the number of spurious questions and unnecessary comments in the thread.

I took a break for a while because of the frustration that comes with developing and the repetitive questions and lack of appreciation I've seen, and I don't want to stop because I feel like we're doing good work here. So, please, help me retain a level of sanity here. That is all.
[One (M8) Android Development] Captain_Throwback:
Please just go back and re-read your reply to my post where I clearly stated I was posting an updated version and what the update entailed. You asked me if it was the same. The file isn't named the same, and I say it's updated. I don't understand what else I would need to confirm. Then, you say that no one should use it if it has the same issues I already mentioned it has. Well, that's not what this thread is about/for, and that's all I was saying in my reply. That's what is frustrating. If you're here to help, then please help test it. Try what I post. Don't tell people not to use it. And there is an official standard TWRP update to 2.8.6.1, but as I said, that version number doesn't apply to MultiROM TWRP. 5/20/2015 is the latest MultiROM TWRP, which I pushed as an update through the MultiROM Manager app and also uploaded to my Basketball mirror.

I appreciate anyone that's here to help. So everyone please test and post logs if there are issues.
[One (M8) Android Development] fizbanrapper:
I'm not going to touch any of the third rails (intentionally anyway) from the last few posts...

I just want to clarify something for everyone (based on my understanding). Captain Throwback has a lot on his plate and I think he's looking to take a step back. MassStash is learning the ropes and will be taking the reigns. I think Captain really wants to see this through though would like to continue to do the hard work at least until #1 we're able to get a working v32 and official support for the M8 and #2 MassStash is up to speed and able to handle things on his own.

My role? Very little. I consolidated some code... which after consolidating, still doesn't work.

My other contribution is in cleaning up the abortion that we call the OP. It was just peachy for a long time but when the OP went MIA, the OP was neglected and could have really benefited from updates. I've got lots of irons in the fire (you may have noticed) and I won't be able to get the OP to where it should be in one day.

I'm a smart guy, but MassStash and Captain are doing 99.9% of the work, and for a reason. I'm taking notes and trying to get closer to where they're at, but I'm just not there and it's going to be a while. I do outsourced CFO and Controller work for Non-Profits for a living. I may be a CPA but I have zero training in programming. I think I often get more credit here than I deserve, while some others get less than they deserve.
[One (M8) Android Development] jcole20:
Honestly fiz I'm in contact quite a bit with stash as I'm part of one of his hangouts groups for beta testing and I've made it clear that you, smac (from dirty unicorns), [MENTION=4453458]upndwn4par[/MENTION], and stash are the only people I really follow closely. Though the only reason I haven't said the same for Captain_Throwback is because I'm new to the device and he hasn't been very active since I've been around. The venom team I follow too but I don't like sense as much as aosp. I'm extremely grateful for all of the work that all of you do. As I've said throughout my post history here I've repeatedly praised all of you when applicable.

Recently too the candy team has really caught my attention due to their generosity and interest in seeing development regardless of if it's their Roms or not. This is how the android community should be.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

EDIT: AND I WANT TO NOTE FOR THOSE INTERESTED... BOTH THE NEW TWRP RECOVERY AND MULTIROM V32 ARE WORKING ON MY END.
[One (M8) Android Development] Tech_Savvy:
well I have to say I've seen you around quite a bunch....always helpful and always seems like you testing stuff..a typical flasholic ;) check out candy5 kernel...its a beast!!!!
[One (M8) Android Development] Nezorflame:
Unfortunately I can't use the updated version of TWRP. Flashing some zips (like the latest MultiROM or new alpha of xposed) sends the recovery to reboot itself without any visible error. Other zips work just fine.

Maybe it's a problem with a zip and not with the recovery, gonna redownload them and check again. But if there's something with the recovery itself I'd like to help with some logs, just need to be pointed at their location.

P.S. Also just noticed that I've lost the ability to connect from recovery to PC either with MTP or with USB storage mode. That's a dealbreaker.

P.P.S. Turns out that MTP and USB modes weren't working because of the bad cable and the ZIP files were corrupted. Sorry for the trouble.
[One (M8) Android Development] TarekElsakka:
I appreciate all your hard work and dedication to this, for sure. I tried MultiRom v32 and it had the touch problems you mentioned where whenever you try to type a certain letter (y, for instance) it would type several other letters at the same time. When I updated to the latest recovery from the MultiROM app and installed MultiROM V31, all issues were fixed and everything seems to be working flawlessly. My primary ROM is SkyDragon V9 (Sense 7) with ElementalX kernel and my secondary is Resurrection Remix LP v5.4.5 which is 5.1.1 AOSP. Thank you for all your hard work!
[One (M8) Android Development] jcole20:
Yeah this is what I was mentioning... I seem to be one of the only people not having issues with v32 but judging by the large numbers of people who are this is why I asked that question. I can say though that I'm having no issues thus far with v32

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1
[One (M8) Android Development] Tech_Savvy:
whats you primary rom?
[One (M8) Android Development] jcole20:
What my signature shows.. PAC

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

And just for clarification I didn't have issues with the old v32 release but I hadn't seen anyone other than me not have issues. <-- my lack of issues came from a bad flash... After a ruu and reflash the issues are quite apparent.
[One (M8) Android Development] jcole20:
Hey I'm glad you got it working but I know that sometimes when I'm in recovery my computer doesn't recognize the m8 or its internal/external storage. When this happens I go to mount and mount USB storage. My computer will then pick up only the external SD on the m8. Once this happens I unmount the phone (in twrp). Almost immediately the computer detects the m8 again and both internal and external storage. (Internal and the SD that is).

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

---------- Post added at 10:48 AM ---------- Previous post was at 10:36 AM ----------

I hate to quote the same post twice, but why not make a new release post and (judging by the current release status) post v31 and current v32 as a beta? (I say this because I've not seen anyone other than myself post saying v32 is working without the touch issue for them). That along with the latest twrp and a shoutout to the MultiRom Manager App by Vojtec Bocek should be plenty. XDA usually has no issues accommodating such things in instances like this.

HTC One M8 w/MultiRom: PACman 5.1.1 & DirtyUnicorns 5.1.1

Edit: Third rail... Really? That's stretching the misunderstanding a bit.

Edit 2: I want to also note that I ran a RUU this morning and installed PAC w/ Candy Kernel merges as primary and then set it up and booted back to recovery and installed MultiRom v32. I just flashed a secondary and my phone is no longer avoiding the bootloader when going to secondary and the touch issues stopped me from even being able to setup my secondary. So something was apparently corrupted in some way stopping me from getting proper flashes. But anyways v32 is NOT working for me as I previously said and the new twrp is not allowing me to boot straight to secondary as I previously said. I think the recovery had been corrupted somehow. What was happening is when I'd boot secondary the screen would go black then light up solid white then go black again and after 30 seconds or so I'd see the bootanimation of my secondary.
[One (M8) Android Development] kerryh420:
Hoping I'm not in serious trouble....

So I haven't read every single page of this thread but I have gone through it quite extensively, especially the first several and last 10-13 pages.

It is obvious that cat'n and fiz are quite full on their plate, so this question isn't directed at them exactly but if no one else can help it would be appreciated if they might take a quick peek as my phone i stuck in fastboot. It will not reboot.

I downloaded the multirom installer from playstore and used that to install the default multiron, twrp recovery, and the default kernel. After booting into recovery and doing it thing it said something had failed, i didn't get a chance to write down what it siad but then it booted right back into fastboot. I can boot into recovery but I can not boot into system. I really don't want to brick my phone as this is my first HTC I have had less than a week....

Can anyone tell me what I have done and can it be fixed?

Should I just try to restore from my nandroid?

M8 verizon rooted, s-off, BL unlocked, running viper OS
[One (M8) Android Development] Shamestick:
First off, you're not bricked at all and this is all fully recoverable. what kernel did you choose from the multirom menu? To me it sounds like an incompatibility there. Restoring your nandroid should fix the issue, although multirom *probably* won't function as I don't know what kernel you have in there. Do you have any secondary Roms installed? And what carrier/fw are you running right now?
[One (M8) Android Development] kerryh420:
The kernel was the first one listed I believe it was called sense1xxx (or whatever number was next to it), not the last one which is sense"unknown" (I cant remember but it had letters/words & not a version number) What kernel should I use? What kernel are others using successfully?

No secondary ROMS, I have not gotten mutirom installed yet. That's what I am doing here with the app. I found the .zip files for twrp (modified) and the multirom, can I or should I flash them through fastboot?

Currently on Viper OS and Verizon is carrier....

Why? Is there something you see that can be changed to improve the chances of being able to install this? I see others running it so I assume I am doing something wrong...Now that I have the zip files can I [using fastboot to] flash the new recovery and then use the new recovery to flash the multi ROM?

Use fastboot to flash both???
[One (M8) Android Development] Shamestick:
The app should install both of those things for you when you choose them (the process may take you to recovery), so i'm not exactly sure when in this process your issues are arising.. you can flash the multirom.zip through twrp if you'd like, or flash the recovery (if it is an img) through fastboot, through an appropriate version of twrp, or using flashify. Like I said though, the app will usually take care of this for you so I'm a little confused. As for the kernel, I haven't used one from the app in a long while so I don't know if they're updated/good to go for the latest lollipop roms. For verizon I would recommend using elite, hypernova, or flarport kernels (I'm not listing in any particular order, find the one you like) as all of these are fabulous kernels themselves and support multirom. If you still need some help feel free to pm me so we don't clog the thread (I'll be at my computer for the next 45 or so for sure, after that it may be a little as I have a few commitments but I am still glad to help!)
[One (M8) Android Development] fizbanrapper:
I'm sorry you've been having trouble, and I take partial responsibility for that. The OP hadn't been updated in some time, and about a week ago I received access to update it so that things like this wouldn't happen as often. It was a work in progress then, and it still is now, unfortunately. I did however, update the instructions and add a lengthy note specifically addressing your very situation. You can definitely flash just a kexec-hardboot kernel, but getting a list of kernels together that are going to be compatible with all versions of android for M8 is a huge undertaking. Kernels (some) also seem to be getting more and more picky (AOSP) and only wanting to work when compiled as part of the ROM zip.

In your specific situation, here's what I'd do (admittedly haven't read every single word, but I think I get the gist). If your ROM isn't booting because of the kernel, reflash your ROM over the existing install, so that your old kernel replaces whatever you flashed. Make a nandroid. Assuming viper doesn't have kexec-hardboot patch already incorporated, I'd flash a different ROM as primary. Use one that has the patch. Then do the other steps in the OP. After all is working well, add Viper as a secondary on your internal memory, from the nanroid you made earlier.
[One (M8) Android Development] redwiz666:
For some reason my secondary rom will not boot. It just boots into the internal rom no matter what i select. I have attached the error log so maybe someone can give me some insight to whats going on and maybe a way to fix it. Let me know if you need any more information.
[One (M8) Android Development] fizbanrapper:
What primary ROM are you using? Please provide a link to the specific zip file you used, if possible.
[One (M8) Android Development] redwiz666:
The primary rom is Bad Boyz Sprint ONE M8 ROM 5.0.2 Sense 6 v3.4. which can be found Here and the secondary rom that i installed is ViperOneM8 4.3.0 which can be found here. I have tried downloading the Viperrom again and still not working.
[One (M8) Android Development] fizbanrapper:
I suspect your kernel is missing the kexec-hardboot patch. Try one of the AOSP ROMs that has it built in. There are tons to choose from. Search the thread for "kexec" and you'll surely find out if a given ROM has the patch.
[One (M8) Android Development] jcole20:
That or I know the hypernova sense kernel is popular on the sprint variant and a very good kernel... It definitely has the kexec patch. Flash it on your primary and go back to recovery and reinject multirom. Not sure where the option is in plain multirom twrp but themed material multirom if you select multirom from recovery and then the three dots settings thing at the top right you should see the option there. Good luck.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] Captain_Throwback:
BeyondStock is still an option, you just need to make sure you're using the latest version. The latest version works on GPE 5.1 and LolliSense. I'll try and get it added to the app later today (and remove the outdated kernels).
[One (M8) Android Development] Captain_Throwback:
Okay, I updated the kernel in the app. Only 1 kernel in there now. Works on Sense 6 Android 5.0.2 for sure and GPE Android 5.1. It even boots on CM, but Wi-Fi is borked and Settings FCs on boot. But of course I don't expect it to work on AOSP, as the source is different.

But at least this should prevent people from getting stuck without being able to boot.
[One (M8) Android Development] Nezorflame:
Hi Captain. You can now add here the latest ElementalX kernel 5.00 for GPE 5.1. He have released it earlier today.
[One (M8) Android Development] Captain_Throwback:
I'm sure [MENTION=5676253]fizbanrapper[/MENTION] can add it to the OP when he gets a chance. It won't be going in the app, though, as it doesn't work on all variants.
[One (M8) Android Development] Captain_Throwback:
I think we may have a winner!

With [MENTION=3418703]Tasssadar[/MENTION]'s brief help today it appears that MultiROM v32 is fully working for me! Here's the updated zip for all to try. Please report whether you have any issues. No more problems with touch for me, as model detection appears to be working now for loading the dtbs.

MD5: ea1f07385d3097a5d4beb1d00de796b9
[One (M8) Android Development] Tech_Savvy:
Working perfectly for me... At&t s-on.... Lollipop firmware.... V32 and twrp 2.8.6......thankz for you work!!!!
[One (M8) Android Development] ckvisme:
[MENTION=1162986]Captain_Throwback[/MENTION] I tried BeyondStock 4.00 from the MultiRom app on my internal rom (DigitalHigh GPE 5.1 from5/20)

--I wanted the 4.00 kernel to try booting DH GPE as a secondary like you suggested--

When MultiRom boots to twrp (twrp_multirom_m8_2.8.6_052015-01)

I am getting errors .

I rebooted and tried manual flash and same result .

Tried a couple of times both ways ...is there another link for the BeyondStock4.00 kernel (bad downloads?)

Here is a link where I have the multirom log ...if that helps and attached a screen shot. Tia ?

https://mega.co.nz/#!3spgyKRI!1sntVoGV_UIr5Oj_rnz8sI13GPHE5bVKm8Byri6ye0M

*MultiRom v32

*Twrp MultiRom 05-20-15(from the app)

*Sprint m8_whl CDMA

*S-OFF

*4.25.651.14

*Hboot 3.19.0.0000

*DigitalHigh GPE internal
[One (M8) Android Development] ckvisme:
Forgot to attach the screen shot
[One (M8) Android Development] Captain_Throwback:
MultiROM log wouldn't be useful for a failed recovery install - that would be a recovery log I'd need. However, I'm having the same issue as you at the moment and have no idea why.
[One (M8) Android Development] ckvisme:
OK thanks.

Same issue with the copy from the app or the copy you already have on hand?

I'll see if I can get the recovery log ...?
[One (M8) Android Development] Captain_Throwback:
Like I said - don't need one. It says nothing useful. It appears to be an AnyKernel problem, but I couldn't tell you why, since no previous version has had such an issue.
[One (M8) Android Development] jcole20:
Just thought I'd note that v32 is working perfectly for me. I still have the issue where when booting to secondary it goes to the bootloader before going to the secondary but that's always been the case. Thank you [MENTION=1162986]Captain_Throwback[/MENTION] ... I love multirom. Such a great feature.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel
[One (M8) Android Development] ckvisme:
Anyone tried booting to internal/secondaries from the multirom app on v32 ?

Multirom app > manage Roms > (select ROM) > boot :

Instead of booting to the selected ROM it shows the internal ROM boot animation then boots back to the multirom menu screen.

Obviously not a big problem but wanted to report ( although I think its been reported b4 ) ...what logs would help --multirom logs?--

Tia

4.25.651.14 / HBOOT 3.19.0.0000

Sprint non-harmon

m8_whl CDMA

Twrp multirom 2.8.6. 052015

Multirom v32 --latest from few days ago--

S-off
[One (M8) Android Development] fizbanrapper:
Try selecting the ROM in recovery and hit restorecon. That may fix the problem.
[One (M8) Android Development] ckvisme:
OK I'll try it.. Here is a link to a multirom log.. ?

https://mega.co.nz/#!ypJElTyB!CRcIV9fpBiJD9QZ8wU5s5mF9OEeO1PpW7lceoI51OBM
[One (M8) Android Development] ckvisme:
Good call, thanks ?

Had to run restore con on all of the secondaries then full reboot... Now multi-rom app is letting me boot to any internal/secondaries I want with no problems.
[One (M8) Android Development] Captain_Throwback:
Thanks to [MENTION=3418703]Tasssadar[/MENTION]'s help, we have (what I hope is) a final v32 update for M8!

The updates have been officially merged into the multirom and kexec-tools repos, so hopefully everything is working.

Please test and confirm (I'm especially interested in seeing how it behaves on Verizon devices).

If all is well then I'll finally update the app with this version.

MD5: b50bebc43c24155a89766f2314590377
[One (M8) Android Development] fizbanrapper:
Cookin with gas!

Workin well here!

Firmware 4.28
[One (M8) Android Development] ckvisme:
Lol... Good here too. (almost missed the thread with the Op change ?). Nice bit of work guys!

Sprint CDMA

4.25.651.14
[One (M8) Android Development] daorderdillon:
flash multiboot over and it will work
[One (M8) Android Development] Galaxysm:
The .zip on the OP? Not the recovery right?
[One (M8) Android Development] jake.99x3:
Yeah the zip not the recovery. The recovery is already installed
[One (M8) Android Development] Galaxysm:
Well time to redownload the ROM xD
[One (M8) Android Development] jake.99x3:
lol just save it to external sd card. Then flash Captain_Throwbacks twrp- kernel- multirom zip
[One (M8) Android Development] Galaxysm:
You think his recovery works on T-Mobile?
[One (M8) Android Development] Captain_Throwback:
It works on all M8 variants.
[One (M8) Android Development] daorderdillon:
op recovery or captain's own