yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] jcole20:
Yeah taking to different people it seems to be unique to Verizon devices. I know two others outside of myself with this issue. All 3 of us are on Verizon devices.

---------- Post added at 01:17 AM ---------- Previous post was at 01:15 AM ----------

I'll pull a logcat but honestly I'm on v31 and its working flawlessly for me thus far. I really have no need to go to v32 again.

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] MassStash:
Well that's not very forward thinking brah...

~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] dnkjordan:
Is there a way to flash a new boot.img to a secondary ROM in TWRP without creating a flashable zip?
[One (M8) Android Development] fizbanrapper:
Remove the old one first.
[One (M8) Android Development] TheBurgh:
V32 was doing the same for me so I also went back to V31 and has been working great.
[One (M8) Android Development] fizbanrapper:
I have a hypothesis, but need more info. Have you ever flashed a zip file with an auto-reboot script at the end?

Examples would include, but not limited to:

Aroma ROMs that ask you if you'd like to reboot after the ROM is done flashing

An update.zip from Titanium Backup, which is used to restore apps & data in a batch via recovery

I suspect that this may be the cause of the problems, but I need to get feedback from everyone.
[One (M8) Android Development] garywojdan81:
Nope, no auto-reboots here. On Verizon with andybones' Fluent 7.5 as primary, and and aosp as secondary. Updated both twrp and multirom through the app and I've noticed all of these issues. The only thing that works in secondary is a nandroid. Anything flashed clean is borked.

Anyone have a link to v31?
[One (M8) Android Development] TheBurgh:
I have done both while using multirom
[One (M8) Android Development] jcole20:
I just don't see why I even need a v32... V31 is working fine for me and the bootloader issue was the same in v32. I'm not trying to hinder development but the old saying about "if it isn't broke" kinda rings true here lol. I mean v31 works absolutely flawless for me. But regardless I'll pull a logcat this afternoon when I'm done at work.

HTC One (M8) MultiRom: PACman 5.1.1; SOKP 5.1.1; CyanogenMod 12.1.1 (Nightlys updated weekly); ViperOne M8 w/Hypernova Kernel

---------- Post added at 10:03 AM ---------- Previous post was at 09:59 AM ----------

I can tell you for a fact I did not use any script that auto rebooted the device when I had the secondary issues. I had it following a ruu with a fresh install of carbon and pac + minimal gapps on both. After we talked via pm I was careful to ruu and only install the roms + gapps to make sure if this. I do install SuperSU via zip on pac but it does not reboot the device.

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] Shamestick:
For those not able to access internal/external storage on Roms installed as secondary, installing a ROM via the swap method allowed for good installs and data access on Roms that previously didn't when installed straight to secondary

Edit: v32 from app
[One (M8) Android Development] jcole20:
What makes v32 a need? v31 works just fine. I've got no issues with v31 that v32 corrected. Really the only issue I've had is secondaries booting to bootloader before actually going secondary. I'm really not trying to hinder development once again but v31 seems to have no issues for me outside of that and I found a fix for that. I'm still at work unfortunately so it'll probably be tommorow before I get the cat.

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:
For me v32 is better as I'm not having to worry about secondaries flashing to the internal partition (I know the work around is stupidly easy but for new users it's nice to avoid problems...also helps when I get flash happy :) .

And I would like to see the Verison booting to boot loader fixed.. If you guys can manage catch it in a log...again for the new users.

Just my 2 pennies ?
[One (M8) Android Development] jcole20:
I still had the issue with secondaries overwriting primary without themed twrp on v32. I posted how I fixed the bootloader issue on v31 and v32. It's a simple workaround but your primary kernel has to be compatible with your secondaries.

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] ckvisme:
Weird ...I also removed the theme (its still removed ) and actively tried to make it flash over primary, changing internal/external selection multiple times in more than one session and have had no instance of it flashing to incorrect partition with v32 ... ?..lol maybe MultiRom is prejudice against Verizon ( understandably...bootloader locking punks ).

I read your fix for the booting to bootloader. Thumbs up!!
[One (M8) Android Development] jcole20:
The Verizon devices from what I've seen seem to have the most issues but it's not something that affects every Verizon device. I'm in regular contact with two other vzw m8 users who of the three issues I've had with multirom we all have the same problems except one of the three isn't going to bootloader when booting to secondary like I did. Where I have to use a workaround to avoid that he is able to boot to secondary with no issue on v31 and v32. The same person couldn't access their storage on secondaries with v32 (tried five different roms and a plethora of kernels to no avail) but had no issues with the play store like I did.

Where the sprint devices seem to have the most issues with certain features of aosp roms the Verizon devices are having the most issues with multirom. I think it's an AT&T and T-Mobile conspiracy where they're bribing HTC to make the CDMA networks branded devices buggy. I think the "can you hear me now?" and "blazing fast LTE" commercials got to AT&T and T-Mobile.

˙ʎlsnoᴉɹǝs uǝʞɐʇ ʇ,usᴉ ǝʌoqɐ ɥdɐɹƃɐɹɐd ǝɥʇ ʎllnɟǝdoH

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] ckvisme:
[MENTION=4452290]jcole20[/MENTION] ?..thx for that
[One (M8) Android Development] adeptustech:
Oh no everyone they discovered our secret. Now what are we going to do to make sure that Verizon & Sprint go out of business....

Maybe just sit back & let them do it for us.

Now that all the poking fun at Verizon & sprint people is done.

We also have problems just like your devices. But we don't let it stop us from trying to make the AOSP Roms or tweaks & mods the best thing that ever happened to our devices.

The other thing just remember nothing is impossible for us to make happen for us & our devices, no matter what they do to try to stop us from making it happen.

The ROMs & tweak are only as good as we make them.

Don't ever let the company tell you what you are going to do with the devices we buy from them. MAKE IT YOURS.

One last thing FIGHT, FIGHT, FIGHT ALWAYS to get what you want from your device, it's your device, not theirs.

PS: nothing I said here is aimed at anybody or company, so please don't take offence.

Just we have to keep trying.
[One (M8) Android Development] jcole20:
Yup... [emoji106] If you're using that boot.img workaround please understand if you clear cache on your secondaries from recovery it will break the fix (at least for me it does). I run three different roms from time to time. I'll be setup with PACman (from fizbanrapper), Carbon 5.1.1, and other aosp builds and am able to boot to all of them without going to the bootloader as long as I keep the primary roms kernel (boot.img) but delete the kernel off the secondaries. This works perfectly regardless of the number of secondaries as long as you don't clear cache from recovery on them. I know I said this in the prior post but I want to reiterate it.

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] ckvisme:
Nah, I'm on Sprint so MultiRom works great for me... I just want as many people using it as possible so development keeps rolling along.. That way we can have MultiRom as long as we have our phones ?
[One (M8) Android Development] jcole20:
Heh... There's a few court rulings that back this mindset up. But, we're on xda bud... We're here because we've all embraced this mindset. :)

Truth be told I wish Verizon and all carriers would back off the lockdown of their devices but I completely understand why they do it.

Case in point, I've been rooting/jailbreaking/flashing/modding cellphones and electronics for a decade or so now. Developing roms off and on for like 3-4. I've seen people blatantly ignore instructions/common sense and brick their devices quite a bit. I've talked countless people through restorations/recoveries/Odin/ruus on the android site I'm a coadmin ofs irc channel. There are a lot of people who try to 'hack' (used extremely loosely) their devices that really have no business doing so. I can understand why carriers would try to cut back on warranty claims/insurance claims by reducing the consumers ability to do so. But... Verizon actually has a real nexus cellular device on their network now. So that says a lot for them considering their past.

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] adeptustech:
I will admit all of the carriers have come a long from back in the day. I've been doing the same to phones (rooting, flashing, unlocking, modding) since my first Java phone back in the day. I think it is time we put a stop to the companies & carriers from hard locking the devices, but make a different insurance or warranty for people that want that kind of things to be done to their devices. That is separate from the companies. Hacking might be the wrong word to use here, but the very loose use of the word "cracking" considering what we are actually doing is cracking the codes & scripts that they are using, so we can make mods, apps, & ROMs to do what people want from their devices like they think they should be, in stead of what they bought.

I also wish there was a good way to end ALL of the carriers from trying to out do each other but finally work together to make a truly unrestricted device for their customers that would give them the best products without strings.

PS: my problem with Verizon & Sprint is not their products but with how they do their business. Kind of reminds me of Apple and their products.

That is the EXACT reason (Apple), I'm here on XDA doing what I do. To help as many people as possible to make it possible for them to have what they actually deserve from their devices.

I can't do it all by myself, that is XDA is here & that why I'm here.
[One (M8) Android Development] jcole20:
I agree almost wholeheartedly with this post. I used the word 'hack' there to kind of illustrate the erroneous mindset of the people that don't have any business rooting let alone unlocking the bootloader of the device. That's not the right word but, in general, I either hear the terms 'hack' or 'jailbreak' rather than 'unlock the bootloader' or 'root'.

Nothing against anyone... I love helping people on our irc channel but my favorite is when someone asks me how to get cydia on their android.

I'm a strong advocate that if you're going to root your device and get into installing recoveries/custom roms you need to learn/get comfortable with the use of adb and a command line. My first android device in order to get a recovery on you had to manually write the recovery to the recovery partition from a terminal app or adb. People love Samsung and I think Odin is great but you should understand how your phones software is setup if you're going to mod it. A lot of people blindly root and flash kernels, roms, recoveries, and even radios without really understanding why or how the commands they read work. Luckily android has come a long way but I still see people make ignorant choices that lead to soft bricks that are, in many cases, quite convoluted to correct and exacerbated by having to walk them through correcting it via a chat window. Understanding a command line and the structure of the device goes a long way in troubleshooting.

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] adeptustech:
I agree, ignorance is abundance when it comes to people today that just jump the gun to flash anything.

First they NEVER read anything about what they are about to do. Guess that thinking comes from the lack of people being made to read anything anymore. Things have become to easy to go into the store & pickup a product without to read manuals of how to do anything with the product. We have made to simple for them to mess things up then they either went a quick fix or blame the devs about everything that they messed without even understanding whatever they have really done to get to where they are now. But they expect us to fix it without willing to make any effort to read through everything & try to fix it with new education of what they learned from the reading.

I have to blame some of that on today's education system in this World. It is sad that you can read articles, manuals, forums or even watch videos online that are very detailed worth information on how things work & how to do ANYTHING anyone would ever want to do in this World. But that goes back to "NO ONE EVER READS ANYTHING AT ALL"

Second people think we are gods. That all they have to do is cry help & magically everything is going to be fixed.

I think we are on the same train of thinking, just different words to used to express it.

I wish people would learn to read then read it again & again. Open-minded to learn New things & not rely only on everyone else to do everything for them. We learn by trail & error.

I will always be here to help anyone that ever needs help.

But do us all a favor, READ EVERYTHING TWICE FIRST.

I mean no harm against anyone who may take anything said here.
[One (M8) Android Development] jcole20:
I agree with the majority of what you said but I will say if I was to walk into an android device today... Never having touched Linux or another android device it would take awhile to really understand android. Especially htc devices because sense is quite different from raw android.

I agree part of it is we're in a generation of immediate satisfaction and all the knowledge of man at our fingertips... But at the same time there's a generation that because of the wealth of info at their fingertips are taught to provide answers and don't need to use critical thinking and this is a problem. I'm not saying this applies to all but anyone who's supervised late teenagers/early-mid 20 somethings (I'm only 27 so it's probably asinine of me to say this) knows what I mean here.

I think there's a ton of information that a new android user would have to memorize to catch up with those that have been in android and custom roms a long time.

Ie...

Touchwiz vs Sense vs AOSP vs GPE

Kernels and what they're designed to work on, what the Framework is, what the systemui controls

The use of adb/fastboot

What rooting is and what lib files control, what bin is.

The basic file structure of your android device

The various well known team roms on the market, the history of aosp and cm especially.

JIT, ART, DALVIK

Logcats, recoveries, s-on, s-off, bootloader, radios

and a plethora of more information... Not even touching build environments or compiling... No source info. Or the difference between open source and vendor data.

This is all info that everyone should know but you don't just learn in a few minutes when you get a device. So I can understand that everyone doesn't know it all, but you're right it's vital to read and read before jumping into anything.

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] ckvisme:
Haha just found the updated Beyond Stock kernels in the app. Thanks [MENTION=1162986]Captain_Throwback[/MENTION] ☺

And successfully flashed to DH GPE ?
[One (M8) Android Development] jbm76:
I installed it from the Multi-rom app and it went on my primary which is a sense rom, then it didn't boot that rom. I had to re-install the kernel for my primary. Then go to the download folders and flash Beyond sense to work with DH GPE which I am using as secondary.
[One (M8) Android Development] ckvisme:
I just swapped my internal ASOP rom for my secondary GPE rom in recovery before I used MultiRom app to install the kernel ...any thing you flash that starts from android will always flash to primary...to flash to secondaries you must do it from MultiRom recovery menu.
[One (M8) Android Development] d1ez3:
Having issues with google play services stopping with v32, is there a way to get a v31 download?
[One (M8) Android Development] ckvisme:
I have a copy of MultiRom v31 zip (03072015) uploaded to MEGA if you want it.
[One (M8) Android Development] d1ez3:
Thanks. Is this a flashable zip?
[One (M8) Android Development] ckvisme:
Yep, just flash in recovery
[One (M8) Android Development] midas69:
I had a major issue with the BeyondStock kernel. It would not read my 64GB SD card. I thought the card just died so I bought another one and had the same problem. Thinking I got a bad one, I bought a third. When that didn't work i did some investigation. As soon as I flashed a different kernel everything was fine.
[One (M8) Android Development] MassStash:
Did you investigate to just pushing the texfat.ko to system/lib/modules?

~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] midas69:
I have no idea what that means.

I tested by putting in an old 32GB card and it worked. Put in 2 more 64GB cards that didn't work. Flashed new kernel and the 64GB cards all worked. That's all the testing I needed.
[One (M8) Android Development] MassStash:
It means for some reason exfat isn't working. So you flashed wrong kernel for the rom you were on, or something messed up on flash for some weird reason. So texfat.ko pushed to system/lib/modules may solve it. Use the one from the rom you're on

~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] midas69:
I now see that Multirom shows both a Sense and GPE kernel. When they nuked the long list of kernels there was only one choice. That might explain it.
[One (M8) Android Development] eskimosound:
Hi guys, last time I tried this it boot looped my phone. I'm using SRom M9 port, international version on HTC One M8. Twrp recovery. Can someone confirm it will work with this rom please. And what do I need to look out for?

With the multirom app it says the recovery needs updating, well according to twrp, I have the latest. So I dunno what to do.

Reading the forums it seems it can't work on the M8 Sense based roms, any progress on this?
[One (M8) Android Development] ckvisme:
Latest stable multirom recovery should be the one in the app.

As far a SRom ..its the only rom that ever gave me a hard time with multirom..

But make a NANDroid backup of SRom with normal TWRP.. then set up multirom via the app (that includes multirom, multirom recovery, and a different rom using a kernel with kexec hard boot patch, such as the ones in the app).

Once setup the rom with the kexec kernel is now your internal rom. You can now setup your SRom NANDroid as a secondary.... Just woke up.. Hope this makes sense. Good luck
[One (M8) Android Development] MassStash:
Can everyone test this latest multirom recovery. Everything I noticed is working, but need everything test I don't have time for haha. Just rename to .img after download

~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] Tech_Savvy:
everything working great here on my end..anyways of what i normally do.. btw i have at&t
[One (M8) Android Development] jcole20:
So stash it's confirmed working on att, sprint, Verizon I think you just need to confirm international :)

HTC One (M8) MultiRom: PACman 5.1.1; Carbon 5.1.1
[One (M8) Android Development] MassStash:
NICE! Now can everyone retest this one? haha. Just made the 2.8.7.0 updates, so everything should still work as it did before, but if anyone has time to fully test, would be much appreciated. Still weary of the build quality just because still noob building these lol

Multirom TWRP M8 2.8.7.x

Fix system read only behavior during boot …

Fix unable to uncheck the mount read only check box …

Add resize2fs and ability to run resize2fs via GUI …

Mount system as read-only by default …

2.8.7.0 …

Cleanup device_id retrieval …

[WIP] gui: software drawn keyboard (code only) …

Fix mass storage in recovery …

fix settingsstorage mark …

Allow ORS set command to work with spaces in the value …

Make sure that adbd restarts after sideload …

framebuffer: s6 edge takes a little lomger to initialize fb0 …

add magic property.* value for accessing system property variables …

minuitwrp: fix crash when taking a screenshot. …

partition: recreate tw_internal_path(/data/media/0), after wipe media… …

Fix ORS scripts displaying an error after completing …

avoid possible dead loop for invalid utf8 …

gui: set tw_file to the currently flashed file name without path …

Fix double free crash during encrypted backups …

gui: move retainaspect handling to the resource ctors …

Don't try to read temparature file if TW_NO_CPU_TEMP is set to true. …

remove useless memset and \n …

minuitwrp: remove unused variable …

Only include uncrypt if not in system/core …

recovery: Add lz4 libs if available …

partitionmanager: remove broken and unused progress calculation code …

bootloader: align with AOSP code …

GUI: Prevent duplicate page overlays …

TZ: Update default time zone string …

Support Qualcomm hardware decrypt …

Add option to use new heap_id_mask instead of old heap_mask …

bootloader: fix crash with empty lines in /cache/recovery/command …
[One (M8) Android Development] ckvisme:
NICE [MENTION=1238555]MassStash[/MENTION]... That really didn't take long at all ...well maybe the work did, but the wait was short here in user land ?

Md5 on hand?... If not I can deal.. Thanks Mass!

Edit: and re-name to .img instead of .txt?
[One (M8) Android Development] MassStash:
lol seemed fooooorrrrever here.... The read only commits merged weird, and took me 3 days to get around to figuring out it was just a pick error, hand fixed the one file that was causing build issue and seems to be good to go.

md5: a8c627b32df7ee91dfe995ea8d903a2c
[One (M8) Android Development] ckvisme:
Not sure if I'm just getting a bad download.. But the md5 I'm getting is

c3d741daddd71daa0349ae04e10908bc

and of course I flashed it before anyway and it just boots to the bootloader...

Anyone have better luck?
[One (M8) Android Development] Tech_Savvy:
Same thing here... Its only 7mb and it shud be close to 15mb