yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] Captain_Throwback:
I have no idea. I've been trying to figure out how the app determines whether a MultiROM recovery is installed, but I don't have a clue. I'm sure [MENTION=3418703]Tasssadar[/MENTION] would know.
[One (M8) Android Development] manup456:
I know it will get worked out at some point it's no big deal.
[One (M8) Android Development] jake.99x3:
Next time when your data partition is corrupted format data from twrp

---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------

All you had to do was format data xD. Go to wipe-format data
[One (M8) Android Development] S1L3nTShaDoWz:
I used to do that, but format data wipes all of my pictures. I really could care less about the ROM and stuff as I have most of those on SD card, but the pictures have value and I absolutely hate having to replace them all once they are gone. & Yes I do occasionally back them up but it's been a while this time, got a lot I'm gonna lose if I do that. At the moment I'm facing tons more problems than just my ROM's disappearing. ADB hardly functions, reboots phone everytime it's used, most things in TWRP auto-reboot the phone into oblivion, at the moment I just want to save these pictures and then I'm gonna ATTEMPT RUU'ing to stock. I don't really think the partitions it made are gone, I'm hoping RUU will solve that because the MultiROM uninstaller zip only flashes half way then as stated above, phone reboots. Nothing else flashes from TWRP either, just reboots or fails and reboots. Sigh lol, don't know what I did to cause this many issues with it.
[One (M8) Android Development] Ideas4ya:
Hey guys I don't see anything in the OP about support for AOSP so I'm assuming AOSP users need to wait until there is a kernel patch for us? Are there other things we need to wait on as well before we try this?
[One (M8) Android Development] boringalex:
Do you know for a fact that TWRP isn't compatible with all M8 variants? AFAIK it is.

Also, I've made the m8 MultiROM compatible with all variants as well. It just needs testing.
[One (M8) Android Development] Captain_Throwback:
[MENTION=1238555]MassStash[/MENTION]'s flar2 port Sense kernel has the necessary stuff. If his latest GPE kernel has it too, then the version posted in my GPE thread would also work if you're on GPE.

[MENTION=5565418]boringalex[/MENTION]

I assume everything I need to create a MultiROM version of my TWRP build is in the source in your OP? If not, could you let me know what else is needed?
[One (M8) Android Development] boringalex:
Please give me a source code link for the kernel you wish and I will port kexec-hardboot. Besides the source code, I will need an up-to-date and working boot image (generated for the same kernel).

I will update the original post to include this information as well.
[One (M8) Android Development] xLoveHateLegend:
This is the other 50% of what I'm hoping for :p
[One (M8) Android Development] shasen1235:
Other than happy my first thought of this mod is "My goodness,but do I need to lose CPTB's recovery"

Then I see you here...what a wonderful day:victory::victory::victory:
[One (M8) Android Development] colthekid:
No errors from me using Flashify and I was already using elemental so didn't have to flash the boot image, but the app does have that option, so I'd be suprised if it didn't work

Yes please...I haven't got a 128GB SD Card for nothing!!! ;)
[One (M8) Android Development] boringalex:
I didn't get to publish the m8 device config. I will try to do that asap.

Until then, can you please tell me what exactly is the incompatibility between this twrp and yours? As I see from the device tree I started from, it seems to be compatible with all variants.
[One (M8) Android Development] Captain_Throwback:
[MENTION=1238555]MassStash[/MENTION]'s kernel is a port of [MENTION=4684315]flar2[/MENTION]'s ElementalX (built specifically for Sprint).
[One (M8) Android Development] xLoveHateLegend:
Thanks for the info!

I'll be watching your thread for the next update to your twrp.
[One (M8) Android Development] Captain_Throwback:
I didn't say mine was incompatible, but it has some support/features the official one lacks. If yours includes the same features then mine isn't necessary. But I wanted to confirm. I know TWRP has to be built specifically with MultiROM support, correct? What tree did you use as your base?

EDIT: If you built your TWRP using the GPE source linked on your github, then it won't support the Verizon or Sprint variants, as the dts files for those aren't included, so the dtb image lacks the necessary information for it to boot.
[One (M8) Android Development] boringalex:
I used task650's tree as base, I think it was intended for AOKP. I modified it and compiled it inside AOSP.

I sent you a PM with everything you need to compile the modified TWRP (with multirom support). Please tell me if I can help you further.

If there are DTB changes then there is a chance multirom won't work for those variants. Please send me a PM with the incompatibilities (what is added or removed), I need to see if I must change multirom. There is no chance of bricking or anything like that, but there is a chance guests roms won't boot properly. Someone with those variants must test and send me a last_kmsg if there are issues.
[One (M8) Android Development] Captain_Throwback:
I looked at your TWRP image and the dtb appears to be compatible, which makes sense if it was initially built from a unified source. It should be good to go. Now I just have to update my build. Thanks for bringing this to our device!
[One (M8) Android Development] TarekElsakka:
Thank you so much for your hard work. I read all the instructions and I just want to make sure I am on the right track before proceeding.

Right now I am on the latest Sense firmware and have the latest ViperOne ROM installed. The latest firmware is helpful because it reduces the long boot-up time so I'd love to keep that if possible. My questions are the following:

1) After installing modified TWRP and boot image and then installing MultiROM from recovery, how do I install ViperOne as the BASE (main) ROM? I'd like to install a GPE ROM as a secondary one.

2) What are those modified kernels? Do I really need to flash one or can I just keep the one that came with VenomROM? I wouldn't mind installing ElementalX for ViperONE if that's what it takes, I'm already using it. But what about the GPE ROM? Do I need to flash a kernel for it as well or just the main ROM?

3) How does the dual-booting actually work? Do you just reboot the device and you choose which ROM to load?

4) How does battery life perform on this? I know that since the M7 days and now the M8, you're supposed to give any ROM you install around 2 - 3 days for it to settle and the battery stabilizes, so how would that work when you're actually dual-booting two entirely different ROMs?

Thank you for your time and I apologize if my questions are stupid. Please forgive me ignorance. Thank you.
[One (M8) Android Development] rockyseenu:
1) You dont have to. Your current ROM will stay as it is and it won't be touched. After installing recovery, multirom zip and Kernel - Just go to advanced and add ROM of your choice. Make sure you dont select share kernel

2) You have to use a kernel which supports kexex-hardboot. So Elemental is a good choice.

3) Yes

4) I think it depends on the particular ROM&Kernel you use and multirom doesn't have any impact on the battery.

BTW - i installed and everything runs great. Skydragon Sense as primary and PA as secondary. now going to add a GPE rom as well. :D
[One (M8) Android Development] daorderdillon:
does the kernel get installed on the base rom?
[One (M8) Android Development] boringalex:
Yes, you need to install the kexec-hardboot kernel in the base rom. The secondary roms don't have to have special kernels.

For the base kernel, ElementalX is a good choice, as rockyseenu said. Or you can flash a stock one from the first post.
[One (M8) Android Development] daorderdillon:
i need my ota from htc when its time
[One (M8) Android Development] boringalex:
When OTA comes you can flash stock recovery and update. I don't know if stock kernel is required as well.
[One (M8) Android Development] TarekElsakka:
Thank you for your helpful reply. I wanted to install a stock AOSP ROM (not a GPE one) but I am not sure how GAPPS would play into this since I'd have to flash them from recovery. Are they going to be installed directly to the AOSP ROM or will the base (sense) ROM create a conflict?

And one more thing, I already have ElementalX installed on ViperONE so do I need to reinstall it after the process?

Thanks again.
[One (M8) Android Development] Captain_Throwback:
Got it! If you delete the previously downloaded recovery and reinstall the one from the app, it should show up properly now :).
[One (M8) Android Development] manup456:
On your game for real today I see ?
[One (M8) Android Development] Jbb3393:
Just beautiful!!!! I learn to love Linux/android more and more everyday. Thanks to everyone involved throughout the entire community. ?
[One (M8) Android Development] Captain_Throwback:
[MENTION=3418703]Tasssadar[/MENTION] is in the process of updating the official app now, so all of these random APKs won't be necessary soon :)
[One (M8) Android Development] daorderdillon:
How to get back the stock kernel afrter applying the patch before I go ahead and do it
[One (M8) Android Development] Captain_Throwback:
:confused:

Who's doing anything with a kernel?
[One (M8) Android Development] jake.99x3:
RUU will wipe the internal storage so you'll lose the pictures. You should have selected to save them to external SD card. Not sure but I think you can create a backup from fastboot. If you can't attempt to make a twrp backup and then pull the pictures from the backup
[One (M8) Android Development] sabag123:
Host rom is ARHD 11 , and secondary rom is cm 11 , when I'm trying to boot cm it's getting stuck on Booting ROM... and I can't do anything

I flashed the cm kernel using inject boot img in twrp

what's the problem?
[One (M8) Android Development] AnimusVoxx:
Using my own version of aokp, I'm trying to use the quick settings button but is says unable to save storage not available, and I know it's not my rom because it works without multiROM
[One (M8) Android Development] Giblet-dono:
... Well I don;t have an answer to your problem..

But your SECONDARY roms DO NOT need a patched kernl, NEITHER do the need to inject boot.img!

Only the PRIMARY rom needs this!

Please try to remove your secondary rom, and flash it again.

Don;t inject, don;t share don;t flash kernel, just try to boot it (first boot might take 5+ min)

---------- Post added at 12:07 AM ---------- Previous post was at 12:06 AM ----------

You dont have to get back to the original kernel, the one with kexec patch works exactly the same

If you do want toi: just dirty flash your (original) kernel, or if your kernel is included in your rom: dirty flash your rom

---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------

So is the storage available in settings?

Also does it see both the internal storage and the SDcard?
[One (M8) Android Development] sabag123:
Does it matter where I boot it from ? the app or the bootloader itself?
[One (M8) Android Development] Giblet-dono:
I don't get the question...

Maybe you don't understand how this mod works, please read my FAQ it may already answer a lot of questions for you!:

http://xdaforums.com/showpost.php?p=55611597&postcount=121
[One (M8) Android Development] sabag123:
Thanks , So I only need kernel for the host rom , right?

I don't need kernel for the secondary rom?
[One (M8) Android Development] Giblet-dono:
EDIT: Just understood the question, Booting secondary roms can only happen from the MultiRom menu

So reboot the phone, wait for the multirom menu to show up, select the cm11 rom and press it again to boot it

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

Read the FAQ!!!!!! It has your answer!!
[One (M8) Android Development] beats4x:
Why would I do that when it all came back and I didn't lose anything? Of course I thought of that, but that'd defeat the purpose
[One (M8) Android Development] Sojourner353:
Could you possibly link me to the GPE Rom you are using? I have tried 2 and both install but fail at the boot.img part then the ROM gets removed, thanks.
[One (M8) Android Development] Captain_Throwback:
I'm using my GPE port for Sprint. I don't think that'll help you.
[One (M8) Android Development] Sojourner353:
Was hoping you weren't going to say that lol, thanks anyway.
[One (M8) Android Development] Captain_Throwback:
Works fine here.

I tried Power+Home and Power+Volume Down.
[One (M8) Android Development] NJGSII:
Had the same thing just happened when I tried installing a completely stock GPE ROM. Failed when trying to install the boot.img.
[One (M8) Android Development] Sojourner353:
I'm really keen to try and get this working if anyone knows what might be causing it or a workaround I'd be happy to try things out, below is a screenshot of my install script showing the error, cheers.
[One (M8) Android Development] Captain_Throwback:
I can't read that. It's very small in my mobile app.

EDIT: Opened in Browser. That's better. First off, I see that's a test recovery version you're running, which I didn't recommend. Second, I can't even see what you're trying to flash.
[One (M8) Android Development] Sojourner353:
That's a thumbnail, click on it and it will open up in a browser to its full size.

EDIT: we replied at the same time lol, I'm on 2.8.0.6 now too and same result, will try to get the full script.
[One (M8) Android Development] daorderdillon:
Don't think it will allow odex Rom installation it has to convert the entire Rom before flashing and odex roms can't be manipulated so it will fail lol the only way is to have it already on the phone as a backup then wipe internal and restore the stock backup while keeping the secondary custom rom

---------- Post added at 12:31 AM ---------- Previous post was at 12:26 AM ----------

Ok first have your primary Rom then flash the secondary after that delete primary then restore your stock Rom to the internal from your backup but don't boot the phone as yet but make sure element x kernel is on secondary Rom but after the backup is done swap it with the secondary so the custom Rom is the primary and viola you have a stock unrooted secondary custom Rom
[One (M8) Android Development] Galaxysm:
Is someone running PA has 4th or so ROM? Or is there a kernel compatible with Multirom?
[One (M8) Android Development] boringalex:
The changes are merged in.
[One (M8) Android Development] Sojourner353:
Got a GPE Port working so all happy now.
[One (M8) Android Development] MICH_**:
I think PA is not compatible with MultiRom yes because it´s AOSP based. There is no pached kernel for AOSP - corrent me if i´m wrong.
[One (M8) Android Development] kedar18:
I am running PA as secondary. Same Kernel that comes with PA works very well. Patched Kernel if required only if PA is your Primary ROM. In my Case I use Stock Sense as Primary for which I use ElementalX kernel as it has the required patch.
[One (M8) Android Development] Captain_Throwback:
Odexed ROMs work fine.

---------- Post added at 08:19 AM ---------- Previous post was at 07:55 AM ----------

Thanks!

Were you able to determine why our MultiROM interface is oversized? The screenshots in the N5 thread show a color picker, I believe.

EDIT: See here - http://xdaforums.com/showthread.php?p=48508455

I don't recall seeing the logo in the upper left either. I wonder why?
[One (M8) Android Development] boringalex:
There was no xxhdpi defined in multirom and saw no easy way to implement it properly (nor did I have the time). So I wrote a little hack to increase font size.

The interface may be oversized because of the "MR_DPI_MUL" config. You can try lowering it and test the results.

I don't think the Nexus 5 was built from the master multirom branch without changes. If you don't change anything, the font size is ridiculously small on FHD resolutions.
[One (M8) Android Development] Captain_Throwback:
I did try that, but it had no effect. I guess whatever "hack" you did is overriding it.

I'll try and check with [MENTION=3418703]Tasssadar[/MENTION] and see what he did for the N5. In the meantime, is there a way to disable the change you made to zoom the display?
[One (M8) Android Development] boringalex:
The "hack" is enlarging the font based on DPI_MUL. There should be some changes. Did you clean before re-issuing make?

You can disable by checking out multirom before last commit.
[One (M8) Android Development] Captain_Throwback:
I clobber every build, lol. Thanks for the info. I'll take a look.
[One (M8) Android Development] Captain_Throwback:
[MENTION=5565418]boringalex[/MENTION]

What do you think? Should I go a little smaller with the text?

If you want to update the installer linked to in the app, here's the info you'll need:

multirom-20140926-v28-UNOFFICIAL-m8.zip
"size": 3528905
"md5": "ec0c5a2767ccef57fd4e94e93e9be73d"

If you think I should change it, let me know. What does everyone else think? Maybe a little bit smaller?

EDIT: I made it a little bit smaller, lol. Updated the details above (size, md5). Filename is unchanged.
[One (M8) Android Development] manup456:
Looks great like that, nice work on that.

---------- Post added at 11:28 AM ---------- Previous post was at 10:34 AM ----------

@captain_throwback how are you changing the little icons in the app? I have a miui and the same icon your using for gpe, but when I browse and select it nothing happened.
[One (M8) Android Development] Captain_Throwback:
Because the newest version of the app has it fixed ;)

I'm not updating the version in my thread because [MENTION=3418703]Tasssadar[/MENTION] is going to be pushing an official update that includes M8 support :).
[One (M8) Android Development] manup456:
Oh got you on that, does this mean we are going official soon?
[One (M8) Android Development] Captain_Throwback:
See below ;)

---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------

Ignore the above. I talked to [MENTION=3418703]Tasssadar[/MENTION] and fixed it properly (I also posted a comment on your github "hack" on how to fix it, so you can revert it). Updated file stats are below:

multirom-20140926-v28-UNOFFICIAL-m8.zip
"size": [B]3528914[/B]
"md5": "[B]5a0717250153d0a5ffd5adef94a5379f[/B]"
[One (M8) Android Development] erapmicks:
Has anyone used the stock sense insecure img and confirmed it working having a primary of stock sense Rom?
[One (M8) Android Development] Captain_Throwback:
I'm on Sprint, so I couldn't use the ones from the OP, but I am using a stock rooted odex ROM as my primary with the kexec-hardboot-patched stock kernel that I built with no issues.
[One (M8) Android Development] mlin:
Hey [MENTION=1162986]Captain_Throwback[/MENTION], any interest in building a kexec-hardboot-patched stock kernel for VZW or perhaps pointing me in a direction to try on my own?
[One (M8) Android Development] Captain_Throwback:
There's no kernel source for 4.4.3 for Verizon yet. Go harass @ HTCDev on Twitter to upload it for you.
[One (M8) Android Development] mlin:
Oh, gotcha. Thanks for the response!

---------- Post added at 12:44 PM ---------- Previous post was at 12:13 PM ----------

What about the 4.4.2 kernel?
[One (M8) Android Development] Captain_Throwback:
What about it? Most of the ROM bases have moved on to 4.4.3. There's no reason to mod that when HTCDev has the source, they just need to post it. Usually if you Tweet at them they get it up in a few days.
[One (M8) Android Development] boringalex:
Sure dude, I'll make the changes as soon as I get to a PC.

Edit: Done and done.
[One (M8) Android Development] mlin:
Fair enough, I wasn't sure if you were serious or sarcastic about hitting up HTCDev on Twitter. I use 4.4.2 because I think the camera is better. Thanks for the replies.
[One (M8) Android Development] Captain_Throwback:
Awesome, thanks. So now everyone just needs to update their MultiROM through the app, and they should be good to go. I don't think [MENTION=3418703]Tasssadar[/MENTION] has updated the Play Store yet, so the unofficial apps will have to do for now.
[One (M8) Android Development] throcker:
Info: sense arhd 11.1 primary, elementalx kernel lastest

I am experiencing very strange slowdowns, never happened like this, even on m7, I have some heavy lags sometimes and system gets slow. I always keep the rom very clen no xposed, no mods. Damn, I feel like if I have a damn Samsung device in my hand...

Does anyone have something like that? And, I'm posting vere because it came up after I installed this mod. Do you think that this could even remotely cause these issues?
[One (M8) Android Development] manup456:
The one you showed earlier? You posted on your site?
[One (M8) Android Development] Captain_Throwback:
The one in the OP here will work too. Either one is fine.
[One (M8) Android Development] manup456:
I was talking about the one you posted a pic of earlier with fixed icon issue.
[One (M8) Android Development] Captain_Throwback:
Download it through the app.
[One (M8) Android Development] manup456:
How can I update the through the app never seen the option.
[One (M8) Android Development] Captain_Throwback:
What do you mean? The first check box, above recovery in the app is MultiROM v28. Check it and Install it.
[One (M8) Android Development] manup456:
Not that I figured that out earlier today the app it's self you have 1.51 I believe I seen.
[One (M8) Android Development] Captain_Throwback:
As I already said, once [MENTION=3418703]Tasssadar[/MENTION] pushes the update to the Play Store, then you can update it, just like any other Play Store app. You *might* have to uninstall whatever version you currently have installed first, but once the update it available, I'm sure someone will post about it.

---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------

That was fast, lol . . . ;)
[One (M8) Android Development] manup456:
That's cool don't see it yet in the playstore but I'll keep a lookout for it.
[One (M8) Android Development] Captain_Throwback:
Doesn't look promising: http://review.cyanogenmod.org/#/c/74041/

Apparently the code needs some cleanup, and I have no idea how/what to clean.
[One (M8) Android Development] Captain_Throwback:
Update is live: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
[One (M8) Android Development] SeVIIn:
So, I am experiencing a major problem at the moment and could use some help. I had everything setup and installed properly through the Multirom app today. I then decided to install a second ROM, which also went fine. However, after I booted into the second ROM (Vanir) and setup a few apps I went to reboot into recovery again, but this time I encountered the following problems. If you look at the pictures I took, it seems that recovery cant gain access to the data or storage partition anymore, and refuses to boot into anything. Anytime I try it just goes to the stock boot screen that says "Android" and sits there indefinitely. The base rom is Renovate Sense 6 and the second rom is Vanir AOSP.
[One (M8) Android Development] Captain_Throwback:
Have you tried repairing the data partition in recovery?
[One (M8) Android Development] SeVIIn:
No I haven't, how would I go about that exactly? Additionally, it looks like the internal sdcard is empty, which I really hope it's not....
[One (M8) Android Development] Captain_Throwback:
I think the option is in the Wipe Menu.

And your internal sdcard is emulated storage, so if /data won't mount that's why you can't see it.
[One (M8) Android Development] SeVIIn:
I tried but it didn't do anything unfortunately it seems the mount point was somehow wrong or corrupted. I just gave in and selected factory rest under the wipe menu, and it kicked me back over to my first ROM. Everything seems to be fine now, but I'll try booting back into the second one to test
[One (M8) Android Development] Captain_Throwback:
Could be that pesky AOSP encryption bug I keep hearing about.