yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] snebojsa:
In your place I would try to reflash multirom and twrp from Multirom app, may help.

What I noticed, when I delete cache and dalvik from secondary rom in recovery, can't boot it anymore, stuck on splash screen. It happened 2 times. Even when reflash secondary rom without wipe, can't boot, must delete rom and flash from scratch.

Another question, there is a long waiting time (4-5 minutes) when flashing secondary rom, "preparing zip file...", and on the end also "restoring script file..." or something like that. So when flashing secondary I lose 10 minutes for waiting. Can this be avoided somehow?

EDIT:

About waiting times, if rom is flashing from internal memory of the phone, the waiting time is much shorter.
[One (M8) Android Development] dragontology:
Quick question. I rained down holy hellfire on my device and I'm trying to figure out just what I did wrong. Verizon HTC One M8 user here.

Main was a GPE port, and I had the kernel with the kexec-hardboot thing (sorry, not well versed in kernel features, but I know what's needed and I chose a kernel that had it), secondary was basically whatever ROM I wanted to test. Currently, it was a debloated stock ROM.

So I'm testing a feature where the dev removes R/W protection from the SD card. His fix doesn't work. But it's working for others, and I read the situation as that the developer had considered the matter solved. So, I got JRummy's fix, run it, problem solved. Well, the developer wasn't done trying to solve the problem, and put forth a second fix. I can't undo JRummy's, and the similar apps don't seem reversible either.

My solution: Flash his ROM a second time, as a tertiary ROM. So I'd have GPE and then this ROM, twice. I'd just sign into Google, download my file manager, flash his second patch, and try to make a file on the SD card. What happened: MultiROM only showed the two ROMs. So... I went to boot up the secondary ROM. Said I didn't have a kernel supporting kexec-hardboot. Wait, what? So I went to boot my primary ROM, and it hung on the boot animation for 15 minutes. Power cycled, went in, and flashed the kernel to my primary. So there's at least a kernel and a boot animation. Now I can boot secondary. Sure enough, it's hosed and I had to start over. Okay. Flashed the fix. Lo and behold it doesn't work, but it does for others (who I'm guessing aren't on MultiROM, though I definitely flashed it to the secondary, and not the primary, and I've successfully flashed another patch, and a kernel, to the secondary, and they took fine).

So... Can one ROM not be flashed as two secondaries (or secondary and tertiary)? Was that bad? And, any ideas on how I hosed my primary? Primary was never touched and I'd used it as recently as yesterday.
[One (M8) Android Development] ckvisme:
I don't know why but yes it 'seems' like when you are flashing to sencondary roms if switch internal to ex_sd or vice versa (while trying to find a file to flash) from the secondary select zip menu, TWRP seems to forget you are flashing to secondary partition and not the primary-ROM partition.. So at least from what I've seen it ends up flashing to primary-ROM and causing general choas..

I'm sure there is a much better explanation and reason but I just always keep lots of backups on ext sd card and pc.

Also I know the maintainer was waiting on help from other Devs to put in the new updates from Tasssadar, so we will have to be patient and try to find work arounds

But I try to make sure that I don't have to switch location weather internal sd or ext_sd when picking zips to flash to secondaries in TWRP. And make sure to have time to restore your primary-ROM NANDroid backup if choas reigns down again (that usually fixes most of the damage)

Hope you figure it out, and good luck ?

the sd fix your referring to.. I have know idea

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

Oh and as far as 2 secondaries what I did was change the name of the rom zip file with ES FILE Explorer

Had 'ViperOne' as primary

-changed the zip file name to 'NiperOne' and flashed it as a secondary, and that worked for me ?
[One (M8) Android Development] riteshbendre:
Can I use multi-rom to flash Lollipop 5.0.2 Sense 7 (if not then Sense 6) ...and CyanogenMod 12 working as second rom ?
[One (M8) Android Development] ckvisme:
Yes and yes, I have LeeDroid sense 7port as primary

And cm-12.1 team UB as a secondary...make sure you have updated firmware though

via my Sprint CDMA SkyDragon v8 reptile ?
[One (M8) Android Development] dragontology:
That makes sense, my ROMs are on external and the fix was downloaded to internal.

The SD card fix itself is easy, there are, like, ten fixes on the Play store.
[One (M8) Android Development] TarekElsakka:
May I ask what kernel you're running on LeeDroid?
[One (M8) Android Development] ckvisme:
HyperNova v1.4.7 by MassStashed

His thread is here :

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

Its an awesome kernel, really try it out for a few days and see what you think

via my Sprint CDMA SkyDragon v8 reptile ?
[One (M8) Android Development] TarekElsakka:
For some reason I still cannot find v1.4.7 for Sense 5.0.2 after searching for a while. Got any direct link to it? The only 1.4.7 version I found was for GPE.
[One (M8) Android Development] ckvisme:
Yeah , I Dont think he has had a chance to update the OP...but post #780 , MassStashed , there is a link that just says:

" sense " (no quotes )

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

The link above will get you to the correct page then

Just click on the 'sense' link and it will auto download... Let me know if you have problem and I will try to link it. Good luck ?

via my Sprint CDMA SkyDragon v8 reptile ?
[One (M8) Android Development] fizbanrapper:
I made the changes, but I'd really like to test them since there are probably some errors. I've had the device for about a month and my previous device (jewel) did not have MultiROM. As you may know, I've compiled a lot of AOSP ROMs and my own kernel for my last device, but I've never compiled MultiROM or TWRP. Can you give me some guidance on what to do next? I'd like to test it. I'm sure I can find the answer on my own, but I'd appreciate if you could help me with the next step.
[One (M8) Android Development] riteshbendre:
Thanks mate, I exactly wanted to use the same ... Team UB ROM + LeeDroid or SkyDragon...depends...

now just one small question..

On my previous phone, Desire HD, there was an app called "Boot Manager" ...on which, can install primary rom on the phone's internal storage and other ROMs on the SD card,... does the same same logic applies here ?

---------- Post added at 11:07 AM ---------- Previous post was at 11:01 AM ----------

Also... can anyone link me to the latest kernels and whatever needed to flash Sense 7 + CM 12.1 ?

As I see in the OP.. the kernels and recovery is for Android 4.4.4
[One (M8) Android Development] ckvisme:
Tbh I haven't spent enough time on figuring out how to set up the partitions for ext_SD , I've just been running everything from internal SD card, (I had 6 different ROMs at the same time for awhile). But as long as your "internal" ROM (or primary) has a kernel with the kexec hardboot patch you are good to go.

Which ever ROM you start set up with will be your primary ( although you can easily change it later in TWRP)

Right now I have LeeDroidv7.1 +HyperNova kernel as primary

Cm12.1 UB as secondary

SkyDragon v8 as secondary

via my Sprint CDMA SkyDragon v8 reptile ?

---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------

Sorry if I didn't answer the question ...if not ask again and I will try. ?

via my Sprint CDMA SkyDragon v8 reptile ?
[One (M8) Android Development] riteshbendre:
Well ... thanks for the reply ... a few more questions...

1) Do you have a 32GB variant ?

2) First i flash Skydragon..then flash Hypernova after it ?

3) and then UB team ROM ?

Let's see..will look for more info before doing anything...dont wanna brick it!!
[One (M8) Android Development] TarekElsakka:
Thank you very much! I found post 780 under page 78, and here's the direct link for future reference: http://lantowcorporations.com/andro...Hypernova-m8-1.4.7-Sense-04-12-2015-00-00.zip
[One (M8) Android Development] Captain_Throwback:
Thanks for your help!

Can you post the file here, so I can build and test? I had tried making the edits myself, and even had a working build, but I always got kexec errors when trying to boot a secondary ROM. So I'd like to see if your edited version is the same.
[One (M8) Android Development] ckvisme:
#1. yes I've the 32gb version

#2. It doesn't matter what ROM you start with as long as it has/or you add a kernel with the kexec hardboot patch.

Actually there are compatible kernels you can pick and install right from the MultiRom app.

There are a couple of CM kernels (I Dont know if they have updated the CM kernels to work with 5.1... But for Sense there is Beyond Stock kernel , its a good one) these are some of the in-app kernels

Just start from whatever rom ,like SkyDragon if you want..

Download the app, use it- it will walk you through set up

--just be sure to read through this thread and some of Tassadars first...if you haven't yet.

Then your all set and can start adding secondaries

via my Sprint CDMA SkyDragon v8 reptile ?
[One (M8) Android Development] Walhalla:
I just played a little bit with MultiROM ("multirom-20150307-v31-UNOFFICIAL-m8.zip" and "TWRP_multirom_m8_2.8.6_20150409-01.img"). I think I spotted a bug. When I restored an TWRP Backup into a new MultiROM slot it wiped the whole internal storage. It said it can not unmount /data before it remapped the the mount points, but continued to wipe and restore /system and after that /data (I had an open adb shell in path /data/media/). Shouldn't it abort the whole restore when it can not unmount / remap the partitions?
[One (M8) Android Development] ckvisme:
I Dont have the answer to this one but I do know they are trying to work on the updates...keep following should get better soon

I just make lots if backups and Dont flash unless I have enough time to go back and restore my set up.

via my Sprint CDMA SkyDragon v8 reptile ?
[One (M8) Android Development] fizbanrapper:
Hope it actually works! Here's the commit.

https://github.com/Colonel-Corn/kexec-tools/commit/bef8fcc6bb97c9365f3ed253a372ee1d04eadb06

Accidentally synced in the backup copies of two files too. Easy enough to delete, of course.

Edit: In hindsight, my commit did a pretty poor job of properly maintaining authorship. If the changes work, and we're in a position to issue a pull request, I'll want to go back and fix that first.
[One (M8) Android Development] snebojsa:
Have this problem for third time. Everything working fine, and I reboot phone, but then can't boot into primary or secondary rom, just stay on splash screen. Then I tried to flash kernel again, but on the end have error "E: unable to mount storage". What to try to do?

Latest multirom and twrp multirom from Multirom app

Primary rom Viper 4.3.0 with ElementalX 4.0.4

Secondary LeeDroid 7.1.0

Everything installed to internal memory.

Just re-flashed secondary without wipe, no good, just splash screen.

Deleted secondary and flash from scratch, booting fine (just secondary, primary not booting at all). How to restore just data from backup to secondary rom, like I can to primary?
[One (M8) Android Development] Captain_Throwback:
So, I built with your patches. First of all, a big thanks for your help!

There was one edit missing for it to recognize the "m8" board, but that was easy enough to add in: https://github.com/CaptainThrowback/kexec-tools/commit/350865ffce1b12d160ff9d2b3c9c7e5408837eb0

So, attached is the zip I built with your changes. It doesn't appear to be working, but I figured if I post it here, people can try it and post logs with their errors that maybe you can look at and figure out what's wrong. Right now I can choose a secondary ROM and the device reboots as if it's going to work, but it never makes it to the boot animation.

The key item I'm seeing in the last_kmsg appears to be this:

[ 17.284020] c0 1 !!! COULDN'T FIND CONFIG DATA node !!!

I have no idea what that means.

I can at least see that it's booting into the right kernel, but something isn't mapping properly, I guess. Here's my last_kmsg, if it helps: http://paste.omnirom.org/view/0bc7a519

If you need help, you might be able to catch [MENTION=3418703]Tasssadar[/MENTION] in Freenode IRC in the #multirom channel. He's always very helpful :).

Again, please note that the below zip does not work!! Please only flash it if you are willing to provide logs to assist with the further development/improvement of MultiROM on the M8.

MD5: 91f05f316edcb1a918f5299f48ca5414
[One (M8) Android Development] fizbanrapper:
Thanks! I'm definitely going to take a look, but it's going to be a day or two before I can spend meaningful time on it.

the one thing I did notice that might be a problem is

line 263

#define DTB_PAD_SIZE 4096

located at

kexec/arch/arm/kexec-zImage-arm.c

If you look at the commits made by the thread OP, I think he had increased this to over 30k.

I can't boot to ROMs on my external to save my life. I've got the AT&T variant and I think it might be an issue specific to AT&T phones. Even if I create the partition from within TWRP, SD-Ext never mounts by default. I think the same is happening when MultiROM boots up. I'm guessing something with fstab, but I'm not quite sure.
[One (M8) Android Development] Captain_Throwback:
Well MultiROM wasn't originally designed to boot ROMs from external, but your issue sounds like a partitioning issue versus a MultiROM problem. You can always try partitioning the card using GParted in a PC and then see if the ext4 partition is recognized by recovery.

I also tried changing the DTB_PAD_SIZE to 32768 as in the original source, but that had no effect. The problem lies elsewhere. Hopefully when you have a chance to look into it, you'll be able to figure it out, or get the necessary help from [MENTION=3418703]Tasssadar[/MENTION] to get it working.
[One (M8) Android Development] Captain_Throwback:
[MENTION=5676253]fizbanrapper[/MENTION]

With some quick help from [MENTION=3418703]Tasssadar[/MENTION] on IRC, I was able to get MultiROM booting on my M8. However, there is some additional code that is missing for variant detection that needs to be added in. I tried copy/pasting it, but it won't build. Tasssadar said he might have a chance to look at it and update it tomorrow morning, unless you're able to take a look at it first. Looks like it's time to get all that authorship cleaned up so we can submit a pull request soon :).

Here's the detection code that needs to be added: https://github.com/alexandru-g/kexe...963#diff-053477609f9b4a1c1b5204e42362920dR450 (I tried adding it myself, and while it built, a secondary ROM failed to boot)

And, it turns out the extra DTB padding is needed for it to boot successfully, so that'll have to be included in the pull request as well. I'm not sure if Tasssadar will have any reservations about that change.

So I'm attaching the partially working version here. There are some glitches because of the missing DTB detection - my touch screen is a bit wonky - but it mostly works until all the code can be properly inserted :).

MD5: 7b5ac177355788b880da1b71503e4987
[One (M8) Android Development] fizbanrapper:
Sweet! I'll have to flash it and take a look at the logs.

In the meantime, I've cleaned up the authorship issues and picked your latest commit. I didn't add the detection code yet though. I hope Tasssadar can work his magic! Thanks Captain!
[One (M8) Android Development] Captain_Throwback:
Crap, I forgot to push the last two commits. Let me try and do that real quick right now.

EDIT: And done!
[One (M8) Android Development] fizbanrapper:
Wasn't sure if you were going to commit the pad size change, so I'd already incorporated that into my commit. I doubt you care, but let me know if you do.

I just cherry-picked the other one though, so we should be even now.

Between cleaning up my mess earlier and fixing a ROM build, I didn't get a chance to even flash it yet. Hoping for tomorrow.
[One (M8) Android Development] Captain_Throwback:
Oh, I didn't look at any of your updated stuff. I'm still going off the original code you posted, since I did that earlier in the day. I wasn't planning on re-pulling anything right now. I'll deal with that tomorrow.

Since the pad size change was originally from [MENTION=5565418]boringalex[/MENTION], that should stay with his authorship anyway.
[One (M8) Android Development] MassStash:
So glad to see you guys getting somewhere, thank you very much for the efforts

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)

row
[One (M8) Android Development] fizbanrapper:
You'll wind up with the same code in the end anyway, so it's certainly not a priority.

That's what I figured too.

Yeah I'm having the same issues. I'll elaborate for the benefit of those reading the thread. The attachment Captain posted works almost flawlessly. After booting into a given ROM, I can't successfully type the "t" key from within Swype. It'll instead type an "r" or a "y". Many of the other keys are clearly slightly offset, but can be made to work.

One great piece of news is that this version actually shows and will allow me to boot to, both my internal and external SD. I flashed back to the last stable version (3/9 build v. 31, I think) and I'm still able to boot to my external. So whatever the 4/21 build fixed, didn't get undone when I flashed back to the stable version. (FYI I'm on the AT&T variant).
[One (M8) Android Development] MassStash:
Hmmmmmm that's interesting the fix stuck. Perhaps just correct formation to external? That older version isn't doing?

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)

row
[One (M8) Android Development] erislav:
Hey Dudes

There is a Bug , in the recovery (im using the latest aviable in the app)

If you want to install a secondary rom, and choosing the Direction of the rom.zip.

If you change the direction from internal to SD or SD to internal, the Rom.zip gets installed in primary Slot .

I saw that because to confirm flash a secondary Rom, there is never the inject multirom

"Button", but if you change direction before installing, everything works fine.

I think because of that, some where unable to boot the secondary.

And at the End thanks for everyone who keeps the multirom alive ?
[One (M8) Android Development] vkass:
[MENTION=6172183]erislav[/MENTION] Thanks! I thought I was going crazy for a moment, doing everything right but it still wasnt working.
[One (M8) Android Development] str8str:
I am getting reboot to bootloader on reboot of secondary rom. I have to try booting it two or three times before it boots proper into secondary rom. Main rom has no such issues. Any ideas?
[One (M8) Android Development] garywojdan81:
Been like that since lollipop hit, at least for me.
[One (M8) Android Development] fizbanrapper:
FYI, I'm still working on this. The issue definitely relates to the kexec binary. What i still need to determine, is if it's the binary itself. It probably is, but it could instead be a change in the way multirom uses it. There also might be a change we're supposed to make to the kexec-hardboot kernel patch. I'll need to scour a hammerhead repo for that information. I want to make sure we're looking in the right places.
[One (M8) Android Development] MassStash:
Heads up, I hear we still need tasssadar to update kexec-tools first so the model detection in the M8 dtb code works. Apparently the function is dtb_get_model() at the end of the mach-m8.c file. That function isn't being called anywhere (yet)

I'm no pro, but looking to help take wheel of building multirom twrp, so trying to learn more of how this works, and help get 'er updated. Need to help us go ask tasssadar in Inc too so he gets on it haha

~m8whl on the Always Solid ViperOneM8 Latest

Hypernova mako_hotplug kernel at 2.572 Max ¦ 300 Min ¦ 1.190 Sleep

interactive (Franco tweaked)

row
[One (M8) Android Development] ckvisme:
Thank you MassStash and Fizbanrapper for stepping up and working on this project!

Also to those that already have (Captainthrowback, Tassadar etc.) helped !

I've been using MultiRom for awhile now (started about a week after I rooted my M8) and I don't think I could ever go back ...the reasons are legion (many) ?. Anyone who enjoys flashing really should be following these threads .

So thanks to all that contribute here ?

via

RedBulled SD Sprint CDMA !

SkyDragon v8 Sprint CDMA !

LeeDrOiD 7.1 + HyperNova 1.4.7

Team UB CM12 5.1.1

MultiRom v31
[One (M8) Android Development] movielover76:
Sense 5.0.1

Thinking about using multirom, I've used it on other devices, I am rooted with S-OFF

but I have a question since a list of multirom compatibile kernels doesn't seem to be up to date in this thread or in the multirom manager app.

If I wanted to keep Sense as the base Rom 1 which 5.0.1 kernel is closest to stock?

Ideally what I want is just to be able to multiboot between Sense and the GPE rom.

If installing GPE and then Sense as rom 2 is better for compatibility let me know

Also if my AT&T One M8 has the 5.0.1 firmware do I have to stick with the 5.0.1 GPE rom or will the 5.1 rom work as well?

thanks for the help,
[One (M8) Android Development] janarp:
I'm lazy to read thread and use search but noticed that when I try to flash zip file to secondary Rom or update secondary Rom it flashing over primary Rom.
[One (M8) Android Development] redwiz666:
Are you going to list roms. Then clicking on the rom you want to flash it to?
[One (M8) Android Development] janarp:
Yes that was exactly what I did...
[One (M8) Android Development] ckvisme:
I think what he means is when you go into recovery you need to go directly to the file you want to flash (ie if you try to click the 'internal' or 'external' tabs (switching from either) when choosing file to flash to secondary it will flash to internal rom.... Usually..i

When I need to switch the internal or external I use the " \. " on the file menu... Not the independent tab above it...

Or you choose internal/external and reboot to rom, then you can reboot to recovery and your choice of internal/external will already be selected for you..

Clear as mud... Right?
[One (M8) Android Development] Giblet-dono:
I think you should start searching and reading, the answer has been given a few times already in the thread!

Goodluck
[One (M8) Android Development] janarp:
This is what i did:

2. Secondary Android ROMs

If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.Select "Flash ZIP" and flash ROM's ZIP file.

Thanks for nothing :)
[One (M8) Android Development] Giblet-dono:
...............
[One (M8) Android Development] jasonzarko:
I'm too lazy to give you any help.
[One (M8) Android Development] xunholyx:
Dude.
[MENTION=2133457]janarp[/MENTION] isn't really lazy. He contributes with themes, and helps people in a few threads. He does more work than you, and everyone else who tried to shame him, have ever done on this website. Combined.

He was being lighthearted, and asking for a solution.
[One (M8) Android Development] janarp:
Actually if u read my post again u see I'm not asking any help... Just letting know I have that problem...
[One (M8) Android Development] jasonzarko:
Thanks for clearing that up.