yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] thekwijibo:
Thanks for the link! Now as to what to do with it... Would I be able to update the asserts with this file for a specific ROM that's giving me trouble? Or what can I do with this file? I apologize if this is a noobish question.
[One (M8) Android Development] nkk71:
If you look at the aroma config and updater script of ViperOne then you'll probably notice that it should auto detect Verizon and Sprint variants, as they are quite different from the GSM models

And you wouldn't even be prompted which kind you have. Since the script is using the old format to identify your device, it's mistaken your Verizon model for a GSM device, and asking you if you have a Default GSM, AT&T or TmoUS version.

So you need to change those scripts.

I don't have the ROM nor on the PC atm, so I can't show you in more detail.

If I don't forget, I'll do it tomorrow, or you can check in the relevant ROM thread if they can update their scripts, because even standard TWRP will be using those in the future / if not already
[One (M8) Android Development] nkk71:
For example this is from ViperOneM8 4.6.1, in /META-INF/com/google/android/aroma/VenomProp.sh

the above shell script set's the variables for both the aroma installer and installer-script

if [ "$device" = "m8wl" ] || [ "$product" = "m8wl" ]
|| [ "$device" = "m8vzw" ] || [ "$product" = "m8vzw" ] || [ "$device" = "m8wlv" ]
|| [ "$product" = "m8wlv" ]; then
AddPropSetting2 Verizon 1
else
AddPropSetting2 Verizon 0
fi

if [ "$device" = "m8_whl" ] || [ "$product" = "m8_whl" ]
|| [ "$device" = "m8whl" ] || [ "$product" = "m8whl" ]
|| [ "$device" = "m8spr" ] || [ "$product" = "m8spr" ]; then
AddPropSetting2 Sprint 1
else
AddPropSetting2 Sprint 0
fi

needs to be changed (or added) to include the new identifiers:

if [ "$device" = "m8wl" ] || [ "$product" = "m8wl" ]
|| [ "$device" = "m8vzw" ] || [ "$product" = "m8vzw" ] || [ "$device" = "m8wlv" ]
|| [ "$product" = "m8wlv" ] [B][COLOR="Blue"]|| [ "$product" = "htc_m8wl" ][/COLOR][/B]; then
AddPropSetting2 Verizon 1
else
AddPropSetting2 Verizon 0
fi

if [ "$device" = "m8_whl" ] || [ "$product" = "m8_whl" ]
|| [ "$device" = "m8whl" ] || [ "$product" = "m8whl" ] || [ "$device" = "m8spr" ]
|| [ "$product" = "m8spr" ] [B][COLOR="Blue"]|| [ "$product" = "htc_m8whl" ][/COLOR][/B]; then
AddPropSetting2 Sprint 1
else
AddPropSetting2 Sprint 0
fi

remember the above is for ViperOneM8 4.6.1. Each ROM / installer-script will have a different approach to how it detects the device variant.
[One (M8) Android Development] radeon_x:
Anyone aware of any possible configuration where you could have a secondary ROM that thinks that it is encrypted (whether it is or not)? Doesn't seem to be possible, but I can't find any definitive answer.
[One (M8) Android Development] ckvisme:
[MENTION=1162986]Captain_Throwback[/MENTION] while I am waiting for the always "late next week" for Sprint Marshmallow OTA I'm running your BeyondStock 4.0.0 kernel on my Stock primary internal Rom . Just wanted to say Holy Cow!!! Battery life is absolutely incredible and performance hasn't suffered at all. Great work, thank u
[One (M8) Android Development] thekwijibo:
I do appreciate the work and thought put into this possible solution, I haven't been able to get it to work with either Venom ROM. (4.6.1 & 5.0.1) I can get past the Aroma installer, and it says the ROM installed just fine. However, I still encounter the same issue with having to go through Fastboot/Reboot to get the ROM to boot. Whenever I've modded the installer script, the ROM never finishes booting. It'll stay on the ROM's splash screen for hours or until the battery dies during the initial boot.

I'm wondering if this is just a Verizon issue? Or perhaps hardware?
[One (M8) Android Development] nkk71:
you should pull the recovery log (after installation of the ROM has finished), we need more information

adb pull /tmp/recovery.log

or Copy log to SD Card

and then upload it.

by the way, is your firmware up to date?
[One (M8) Android Development] xdadevelopers-user:
I was having the same issue you described where all my secondary roms would boot straight to the bootloader. I could reboot from there and they would then start correctly.

It started working properly again when I flashed the modified marshmallow HBOOT from this post - http://xdaforums.com/showpost.php?p=64213619&postcount=3

Hopefully this helps.

-xdadevelopers-user
[One (M8) Android Development] thekwijibo:
Firmware should be up to date. Had some trouble pulling the recovery.log file, since I couldn't find it in a /tmp folder. I think I found the right one after doing a search, and copying it to the SD card as you suggested.
[One (M8) Android Development] thekwijibo:
Thanks! This did the trick!
[One (M8) Android Development] thekwijibo:
Here's the log we're looking for

Sorry about before, I was having frustration induced stupidity.

Here's the progress.

Flashed new 5.0.1 RUU

Flashed M8vzw_Marshmallow_hboot_6.12.1540.4.zip

Installed experimental TWRP 2.8.7 20151208

Flashed modded version of ViperOneM8 4.3.0 (with /META-INF/com/google/android/aroma/VenomProp.sh modified as per example code)

I've tried several versions of ViperOne using the aforementioned process, but I've gone back to the most stable for Verizon's HTC M8, which is 4.3.0

Still no luck. Here's the log renamed to txt. I'd appreciate any help.

Thanks
[One (M8) Android Development] S1L3nTShaDoWz:
Oh wow I feel a tad bit stupid now, I didn't even realize there was one named "MultiROM TWRP 2.8.0.6" right under the one I thought was it LOL. I assumed because the latest one was 2.8.0.6 that it would be the only one with that name and because of that it didn't occur to me to look for another...even though it was literally RIGHT below it. Only realized it when you told me if I "had the right one"..even then I still didn't understand until I looked again and this time I saw it. Anyways thanks for the assistance, got it working now!

Edit edit edit: saving from posting again, if I were to flash an AOSP ROM as secondary is it still possible to get the encryption bug?
[One (M8) Android Development] scataldo721:
An odd occorance for me. So I shut my phone off to charge it overnight, and when I woke up took it off my charger the light stayed on and it wouldn't boot until I went and did an adb reboot anyone else having this problem?

I'm on a sense primary with multirom completely set up on T-Mobile, S-OFF
[One (M8) Android Development] beats4x:
Quick update on the problems I was having before. I'm not sure why, but it was paranoid android that was causing the issue. I finally caved and tried a different rom (I only want to run pa ?) and it booted just fine. Not sure why multirom and pa aren't getting along, but I'll be trying the 4.6 beta 2 build when it's available
[One (M8) Android Development] nicholician:
So, something weird is going on with this mod. I tried to install it on GPE firmware (converted), but it would only show the internal ROM in the multirom menu even though i had patched in with a kexec hardboot kernel (ElementalX). So I switched back to sense firmware, did all the necessary steps, and now i can't access the multirom menu at boot. For some reason I can boot into the internal ROM with ElementalX and switch over to the AOSP ROM I'm running using the multirom app, but if i try to do the same on the AOSP ROM, the multirom app thinks that nothing is installed. Also, everytime I reboot now, I go directly back into the internal ROM. Does anyone know what on earth is causing this problem?
[One (M8) Android Development] S1L3nTShaDoWz:
Alright so I have tried numerous ROM's and I cannot get any of my main ROM's (not secondary) to boot, they all go to a black screen. If by the chance I'm not using any of the kernels listed above and MultiROM is not working properly then I can at least get to a boot logo that endlessly loads.

Also another problem, when I did manage to get my ROM's to load (both) the WiFi on my 4.4.2 ViperROM (with 4.4.3 kernel) ceased to work along with Task's AOKP ROM's WiFi.

Now I see why wifi might not work on the 4.4.2 ROM (due to kernel) but I've tried 4.4.3 ROM's and ever since then I simply cannot boot them.

Update, just re-flashed the kernel and injected curr. boot and got Task AOKP to boot again but still no Wifi. Rebooted and tried main ROM again and still just a black screen for infinity and beyond. At the moment I'm running CleanROM as my main and can't boot it, before that was NuSenseSIX (tried in-rom kernel and Elite Lunar) & before even that was 4.4.3 Viper ROM 2.4.0 and before that was 4.4.2 1.8.0 viper rom.

Yes the Wifi part is usually a firmware issue but I'm running the 4.4.3 new firmware now and that shouldn't be an issue...at least I don't think. Main problem is I cannot do ANYTHING with the main ROM, anything as in even load it that is lol.

Any ideas what I'm doing wrong or is this a bug of some sort?
[One (M8) Android Development] ggreenw:
I've been running Paranoid Android as my secondary rom for a couple days now with no issues at all... I have SkyDragon primary rom with Elemental kernel also.
[One (M8) Android Development] Galaxysm:
So after reading so much in the thread getting help from some ppl here and many reboots and ROM downloads I finally got Sense/GPE/MIUI booting :3 thanks a lot guys!
[One (M8) Android Development] boringalex:
Weirder thing is I am running PA just fine.
[One (M8) Android Development] boringalex:
What recovery are you running? Only captain's TWRP seems to work ok for verizon variant.
[One (M8) Android Development] Freak07:
Yes it's still possible. Just put the partition fixer zip on your external sd and you can restore your file system when it happens.
[One (M8) Android Development] rockyseenu:
+1

I am running PA without issues as well.
[One (M8) Android Development] _moelle:
I got some strange issue. I managed to setup SinlessROM GPE as intern and installed VanirAOSP as second base. - Everything just works fine but after a while and some reboots (without changing the rom, so only reboots on running base), when i try to boot into the other rom, i stuck on htc bootimage. - switching between the roms works fine as i said but when i stay some time on one of them, i only get access to boot into the other rom, if i do "swap roms" in recovery/multirom settings.

after i swap them, everything just works fine again. ?!

I dont get what i probably have done wrong.
[One (M8) Android Development] jake.99x3:
Yeah it's a kernel thing. Let it boot through the black screen just wait and it will work. I was having the same problem as you. I go multirom working and was able to add the secondary roms but when I choose to boot the secondary rom I got the error about the host rom needs to have a kexec-hardboot flashed kernel. I'm certain I flashed a kernel and I've done it multiple times but I still get the error. I can boot into the host rom with no problem after waiting for black screen. It's a black screen instead of a boot animation
[One (M8) Android Development] rockyseenu:
I was on Skydragon (sense) as Primary and PA as secondary rom.

Tried to install Sinless GPE as primary. Installed ROM, installed Elemental and rebooted.

Everything went fine. But when i select to boot Internal in the initial multirom screen, the phone is not actually booting from initial HTC screen as it did earlier and straight away going to Sinless bootlogo.

And in GPE, my battery shows as 12% but originally it is somewhere around 80% (it shows correctly in recovery)

Tried flashing multirom zip again and no luck. Any ideas?
[One (M8) Android Development] CPA Poke:
Alex, I'm trying to patch my AOSP kernel with kexec using the commits from your GPE kernel source so I can use my ROM as host...I added the flags to my defconfig based on Tasssadar's porting instructions, it builds fine, flashes fine, appears to inject MultiRom just fine, and was able to flash a secondary ROM (also aosp) just fine. (Note: I'm using your multirom repo ["m8" branch] and Tasssadar's libbootimg repo in my source.)

But when I reboot from recovery, it never enters the MultiRom boot stage and just goes straight to the normal boot process of my host ROM. From my experience on grouper, this would seem to indicate that my host kernel wasn't kexec-patched.

Am I missing a step somewhere that you can tell? Do I need to do something else to patch the boot.img other than bringing in the kexec patches to my kernel source?
[One (M8) Android Development] beats4x:
I got pa to work, but only after installing slim and booting successfully into it once. I haven't deleted slim yet as I don't want to mess up my chances on pa ? but at least I got it running
[One (M8) Android Development] S1L3nTShaDoWz:
I'm running Captains TWRP (multirom version). At the moment I'm avoiding all of the kernels above just so I can use my phone properly (i.e wifi issues n black screens). Also the partition fixer never really worked for me, when this occurs it simply will not run properly as my system is inaccessible. Instead I use the repair file system / change file system function of TWRP in a combo to solve it, it's just really panicking to have that issue as there's always the worry of "What if it doesn't work?" you know? lol

Try flashing the kernel then inject cur boot sector and re-attempt. As for that being my problem, I'm not really sure but it sounds a bit off to mine. Feel like I'm missing something but I don't know what :(
[One (M8) Android Development] MICH_**:
I didn´t really get this.. . i have to flash a boot image? why? which one? and where to get it?

Do i have to flash a patched kernel? Ther is justGPE and sense kernels.. i am running AOSP
[One (M8) Android Development] S1L3nTShaDoWz:
The kernels are the boot images, make sure you pick the right one for your variant (e.g international, Verizon). They are listed in the OP, only the one's listed will work as they are the only ones known to be kexec patched at the moment.
[One (M8) Android Development] MICH_**:
Which one to pick for Paranoid Android? Thanks! :)

can i use PA as primary rom?
[One (M8) Android Development] Captain_Throwback:
Did you save the AROMA log as well?
[One (M8) Android Development] thekwijibo:
Tried. After the install it says the log has been copied to external_sd/ViperOneM8_4.3.0_mod.zip.log.txt However, the SD card has no such file anywhere in there. For some reason it gets deleted after I reboot.

Did another install, and snagged it immediately after install. Hope it helps.
[One (M8) Android Development] Captain_Throwback:
Do you have a copy of the script you changed? And maybe also aroma-config and updater-script from the zip?

EDIT: The most important part of the log is this -

===========================================
ViperOneM8 4.3.0 By Team Venom
about to run program [/sbin/getprop] with 2 args
[B]htc_m8wl[/B]
about to run program [/sbin/getprop] with 2 args
m8
Be patient - 1st boot may take a while
===========================================
[One (M8) Android Development] ckvisme:
[MENTION=1162986]Captain_Throwback[/MENTION] we have the update for Sprint sense ...although not the kernel source ...will you be building Beyond Stock for MM sense ? ...or is there a sense kernel with the kexec patch I can use in the interim?

Tia
[One (M8) Android Development] nkk71:
You need to provide the logs after you finish installation, and before reboot... your recovery.log is before flashing anything, so pretty useless.

And you must have done something wrong, because it's still flashing a GSM version; here is the first part of the installer-script:

ui_print("@===========================================");
ui_print(" ViperOneM8 4.3.0 By Team Venom");
run_program("/sbin/getprop", "ro.product.device");
run_program("/sbin/getprop", "ro.build.product");
if file_getprop("/tmp/aroma/first.prop", "selected") == "2" then
ui_print("@===========================================");

ifelse(is_mounted("/system") == "/system", unmount("/system"));
run_program("/sbin/busybox", "mount", "/system");

ui_print("@Extracting tools");
ui_print(" Installing Venom Tools");
package_extract_dir("VenomTools", "/sdcard/Venom/Tools");

ui_print(" Extracting Build Tools");
run_program("/sbin/busybox", "mkdir", "/temp");
set_perm_recursive(0, 0, 0777, 0777, "/temp");
package_extract_dir("tools", "/temp");
ui_print(" Setting permissions");
set_perm_recursive(0, 0, 0777, 0777, "/sdcard/Venom/Tools");
set_perm(0, 0, 0777, "/sdcard/Venom/Tools/VenomCheck.sh");

delete_recursive("/system/lib/modules");
package_extract_dir("system/lib/modules", "/system/lib/modules/");
package_extract_file("system/bin/thermald", "/system/bin/thermald");

if file_getprop("/tmp/VenomProps.prop", "Sprint") == "1" then
[B][COLOR="Red"] ui_print("@Extracting Sprint Files");[/COLOR][/B]
delete_recursive("/system/lib/modules");
package_extract_dir("additions/carriers/Sprint/system/lib/modules", "/system/lib/modules/");
package_extract_dir("additions/carriers/Sprint/tmp", "/tmp");
endif;

if file_getprop("/tmp/VenomProps.prop", "Verizon") == "1" then
[B][COLOR="Red"] ui_print("@Extracting Verizon Files");[/COLOR][/B]
delete_recursive("/system/lib/modules");
package_extract_dir("additions/carriers/Verizon/system/lib/modules", "/system/lib/modules/");
package_extract_dir("additions/carriers/Verizon/tmp", "/tmp");
symlink("/system/lib/modules/exfat.ko", "/system/lib/modules/texfat.ko");
endif;

As you can see, if it recognized your device as a Verizon or Sprint variant, it would show in the log:

* Extracting Sprint Files

or

* Extracting Verizon Files

your log doesnt show either of those, so whatever you edited is wrong.

I've attached the edited shell script, unzip it and

replace

it in the original ROM.ZIP

in the following path: ViperOneM8_4.3.0.zip\META-INF\com\google\android\aroma
[One (M8) Android Development] ckvisme:
Have any of u maintainers/devs had time to build a MultiRom version of Captain_Throwback's new TWRP 2.8.9.0 ? ...lol, since he just build it probably not... ?
[One (M8) Android Development] ckvisme:
Took the Sprint sense MM update last night (6.20.651.3) .

Flashed Caps 12-08 MR TWRP and MultiRom installer back again

Full wiped and restored a MM Candy6 NAND (with Team M8 kernel) as primary... Injected curr boot sec

(primary boots and runs as expected)

All good to this point... However attempts to restore NANDs as secondaries or to just flash secondaries fails to boot... Just hangs on the boot screen until it gives up and reboots

I grabbed recovery logs from a DU secondary flash and a BeanStock secondary restore.

https://drive.google.com/folder/d/0B8bG_OajnI4gOVI4eTRSNWpEdTg/edit
[One (M8) Android Development] nkk71:
that statement is almost as scary as the M9 Q&A section :p
[One (M8) Android Development] ckvisme:
LMAO... What u never passive aggressively ask dumb questions? ?

---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------

What I really meant was:

Please for the love of multirom will someone update this beloved MOD.... Sprints MM firmware broke secondaries!

....is that better? ??
[One (M8) Android Development] nkk71:
trust me, go check the M9 Q&A section.... it's really scary :eek::eek:

and yeah, it's being worked on, but don't think it's as trivial as it seems android-6.0-mrom branch
[One (M8) Android Development] Captain_Throwback:
I have the Sprint MM firmware installed, my Sensified GPE as primary, and I just installed my HK Stock Rooted with no problem....:confused:
[One (M8) Android Development] ckvisme:
Are you using the 12_08 twrp and installer or something else? ...

And now that I think about it, I haven't tried installing a secondary to external SD again... Did u have any secondaries that were flashed prior to the MM update that still boot?

---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------

Lol, multirom is NEVER trivial too me... and I'm damn glad I'm on the m8 as we have some seriously talented people helping in here.

Daaaaamn! You've been busy ? thank u
[One (M8) Android Development] Captain_Throwback:
I've been running Marshmallow (GPE) for a while and I was also using the Dev Edition firmware previous to the Sprint MM update, so yes, all my secondaries still work fine.
[One (M8) Android Development] ckvisme:
OK, well clearly I have missed something or haven't googled enough since MM started... I'll look around.

Thx for letting me know it works ?

...i think I'll start with putting your MM GPE as primary again
[One (M8) Android Development] thekwijibo:
Spent a good part of this weekend trying to get things to work. Ended up bouncing between recoveries and ROMs just trying to get something to simply "work" without having to go back to one of my many month old recoveries.

Ended up doing another RUU, wiped everything again, and started from scratch.

Used the supplied script in Viper, and it seemed to install nicely. Thanks! Got Multirom up and running, and just installed a secondary GPE rom. So far, so good. Fingers crossed.
[One (M8) Android Development] rodohmes:
[MENTION=1162986]Captain_Throwback[/MENTION] - I'm new to using MultiROM and hope this doesn't come across as entitled at all, but is there anyway to have the latest MultiROM TWRP themed like your newest 2.8.9.0-m8 recovery? It's really sharp looking all the way around.
[One (M8) Android Development] Captain_Throwback:
Sure - as soon as you update the new standard TWRP theme to support MultiROM ;).
[One (M8) Android Development] rodohmes:
Uhhhhhhhh.........I barely understand how to use MultiROM, so......I'll just go back to being a happy user. :)
[One (M8) Android Development] MrTheenD:
Hello, I have couple questions:

1. Does this mod supports Marshmallow with 6.14.XXX.X hboot?

2. Do I need S-OFF to use this mod?

Thanks.
[One (M8) Android Development] and.u:
does multirom work on MM??
[One (M8) Android Development] Giblet-dono:
Does quoting the full first post get you an answer faster?

---------- Post added at 03:23 PM ---------- Previous post was at 03:20 PM ----------

I have been using the MM hboot and haven't faced any problems

I don't think you need S-OFF for it, not 100% sure tho as I've always had S-OFF
[One (M8) Android Development] Mjduddin:
You don't have to be S-OFF
[One (M8) Android Development] dhondooo:
Any alternative Linux-based operating systems for M8 ??

Thanks
[One (M8) Android Development] Giblet-dono:
Not at this time, and probably not going to happen any time soon either
[One (M8) Android Development] amirsardari:
i have already tried to flash 3 different rom as secondary rom but failed with this error: failed to execute update binary in zip

i am on mm and mm firmware

any help ?
[One (M8) Android Development] ckvisme:
What Rom are you using as primary?

...and a recovery.log will probably net better info

...and specific firmware and recovery info ????
[One (M8) Android Development] amirsardari:
stock mm rom .

firmware 6.14.707.1

i use recovery which is installed by latest multirom v.32 . i think its 2.8.7.4
[One (M8) Android Development] xdadevelopers-user:
[MENTION=1162986]Captain_Throwback[/MENTION], can you point me in the direction I need to look to get this:

Recovery: MultiROM TWRP 3.0.0-0_2016-03-11 p1

Thanks,

-xdadevelopers-user
[One (M8) Android Development] Captain_Throwback:
Not yet.
[One (M8) Android Development] xdadevelopers-user:
Can you confirm what the most recent experimental TWRP Multirom recoveryimage is? I got stuck in 3g and had to RUU so I lost whatever version was working well for me. Now I've got "2015-12-01 (1)" and I'm having lots of trouble booting into secondaries. I'm not sure if it's my primary kernel, the version of MuliROM, or the recovery that's the issue. Do you have any advice on how to troubleshoot issues where the secondary won't boot? Either boots back to MultiROM menu or boots to secondary rom bootanimation or just hangs.

Thanks,

xdadevelopers-user
[One (M8) Android Development] Captain_Throwback:
I honestly haven't been working on this very much, so I really don't have any answers for you. You'll have to wait until a new build is posted.