yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] MassStash:
What rom you install? May be rom or kernel related not seeing external once booted into user land. Could you describe what you are referring to a little more in detail please?

~Jflteusc on cm12 unoffical

KToonsez Kernel

1.998 Max ¦ 189 Min ¦ 1.134 Screen Off

Ktoonsified v6 Script Tweaked
[One (M8) Android Development] Captain_Throwback:
Of course you can't see external SD. That's where you're running the ROM from. That's why using an ext partition is recommended.
[One (M8) Android Development] Dark hanzo:
Good

[MENTION=1162986]Captain_Throwback[/MENTION]; if I partitioned the external sd, one in exfat and the other in ext4.

1- partition EXFAT

2. partition. ext4.

that is the order they should bear external sd?

Help me with this?

regards

Enviado desde mi hTC One_M8
[One (M8) Android Development] Captain_Throwback:
Just do it in recovery. Then you don't have to worry about order - it'll be done properly.

Once it completes, you can just change the file system of the FAT32 partition to exFAT and you'll be ready to go.
[One (M8) Android Development] HOLLOWHEART:
I have kind of a odd request. Would it be possible to make a updated build that holds the possibility to *optionally* create 2 additional partitions of 612mb each. One fat32 partition and one ext4 partition. This would be helpful for moving apps in between fs 's. Also, I have a class 10 8gb card now so i don't know how this would work for the moment exactly.

By the way, yes i did say 612 not 512. 6 as in six hundred.
[One (M8) Android Development] HOLLOWHEART:
ok :p
[One (M8) Android Development] Dark hanzo:
Good

[MENTION=1162986]Captain_Throwback[/MENTION]; if I understand well the recovery I return to format the sd in fat 32, and create or format the partition ext4?

when finished formatting the pc's formatting the partition fat32 to exFAT?

swap partition should be created?

the ext4 partition of what should be the size?

is the above correct? and obviously I do backup of my data,

regards

Enviado desde mi hTC One_M8
[One (M8) Android Development] Captain_Throwback:
You don't need a computer for this at all (except to backup your data).

Use the partition SD Card feature in recovery. Make the ext4 partition as large as you want (if you're going to be using it for ROMs, think about how large those ROMs are). No need for swap. Then once complete you can change the file system of the FAT32 partition to exFAT from the Advanced Wipe screen in TWRP.
[One (M8) Android Development] bbell101584:
This only wipes the external sd card or it wipes internal as well? Thanks
[One (M8) Android Development] Captain_Throwback:
This doesn't touch internal.
[One (M8) Android Development] thelangosta:
Getting a 404 error for the beyond stock link. I tried 3 browser's with the same result on all 3. Thanks
[One (M8) Android Development] Captain_Throwback:
Works here. I clicked the link right from your quote.
[One (M8) Android Development] thelangosta:
Weird, I even tried turning off Wi-Fi and using Mobile instead. I'll try again when I get home.
[One (M8) Android Development] bbell101584:
Hey so I'm on multirom twrp 2.8.6-3/28/2015 and I did the partition sd card and it says creating fat32 partition then creating ext4 partition then it says failed to find partition and so I go to multirom and it gives me option for ext2 and a vfat partition am I doing something wrong my external sd is 16 GB I wanted to do half and half any suggestions?
[One (M8) Android Development] Captain_Throwback:
It sounds like you created an ext2 partition instead of ext4. and vfat is your FAT32 partition, so what is it you're asking? It seems that the partitioning worked fine.
[One (M8) Android Development] colthekid:
Unrooted secondary

Can we install an unrooted rom (i.e. Completely stock) as a secondary rom?
[One (M8) Android Development] Freak07:
Yes you can.

But make a backup before you attempt anything.
[One (M8) Android Development] colthekid:
Any suggestions for a rom then... Tried the odexed one from http://xdaforums.com/showthread.php?t=2694994 but the install crashes with an error about the boot.img... Does it have to be de-odexed?
[One (M8) Android Development] daorderdillon:
i have a stock rom and it works fine with this be sure to check to see where exaactly u guys are flashing mods

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

do multi boot works on your recovery
[One (M8) Android Development] colthekid:
Running latest Viper rom as primary.

Trying to install the odexed rom from my previous post. The zip is on internal memory & trying to install to internal memory (as ext sd cards are not yet supported)

Install fails with a message about can't unpack boot.img (can't remember the exact wording!)

Don't think I'm doing anything wrong, installed multirom & recovery fine (used it before on the m7)
[One (M8) Android Development] Galaxysm:
So made a mistake switched primary gpe Rom with a sense Rom and now it won't boot into multirom :(
[One (M8) Android Development] daorderdillon:
probably kernel was changed with the switch
[One (M8) Android Development] Galaxysm:
Was thinking about that I'm downloading a kernel

Edit: couldn't boot a sense ROM to work. Had to go back to gpe ROM and then I was able to multiboot again. Sucks oh well Lol.
[One (M8) Android Development] boringalex:
I saw that as well. That stock odexed Sense, I presume. There is something weird about its boot image, didn't have the time tot take a look. Long story short it cannot be installed (unless you change its boot image in the archive).
[One (M8) Android Development] boringalex:
Did that sense rom work for you if you flashed it clean (no multirom)? Without flashing any firmware?
[One (M8) Android Development] daorderdillon:
yes the sense rom will work
[One (M8) Android Development] colthekid:
So anyone have a link to an installable unrooted rom?
[One (M8) Android Development] daorderdillon:
i think u will have to flash the unrooted stock rom first with regular twrp then impliment the multiboot twrp afterwards. i cant even root my stock rom even though i flash supersu to my stock rom but i am able to use multi boot because i swap it to secondary
[One (M8) Android Development] vision89:
any chance to synchronize the whatsapp chatlog?
[One (M8) Android Development] colthekid:
Hmm, forgot about doing it that way! Downloading the de-odexed rom now to try it, then will have a go at your suggestion

Will report back!
[One (M8) Android Development] daorderdillon:
i cant get it to root as a seconday rom it wont flash at all in order for me too root the stock rom
[One (M8) Android Development] rockyseenu:
Nope. Data is not shared between ROMS. you have to use titanium backup for that.
[One (M8) Android Development] Diddy555:
Maybe there are tools to symlink/mount /data/whatsappfolder to /sdext/anyfolder on both roms? Cant look if there are apps that do that now...

Or 2 init.d scripts that copy the whatsapp data folder from other rom at boot time :P
[One (M8) Android Development] jake.99x3:
Could you please tell me your exact steps to get this working on your Verizon m8

---------- Post added at 01:45 PM ---------- Previous post was at 01:40 PM ----------

Did you flash the multirom installer from fastboot and did you flash the kernel on your host rom before flashing the modded twrp.

So Flash kernel on clean rom- flash modified twrp recovery in fastboot- flashed multirom installer ( fastboot or recovery?)- added secondary rom

Edit

---------------------

The recovery from [MENTION=1162986]Captain_Throwback[/MENTION] works on Verizon devices. For some reason the other modified twrp does not work for Verizon users
[One (M8) Android Development] Galaxysm:
Yeah I swapped Roms and it worked like a primary ROM but then it wouldn't boot into multirom so I couldn't choose another ROM.
[One (M8) Android Development] bbell101584:
OK well I picked ext4 for my partition and it's say failed unable to locate sd-partition. Can I install roms as secondary to ext2 partition then?
[One (M8) Android Development] Captain_Throwback:
Just convert it to ext4.
[One (M8) Android Development] bbell101584:
Do you mind explaining how I went to advanced wipe choose the micro sd and choose repair file system but I only see the vfat partition to change that I don't see the ext2 partition to even change the file system
[One (M8) Android Development] Captain_Throwback:
Did you scroll the list down to "SD-Ext"?

If you created the partition in the current recovery session, you may need to reboot recovery to see it.
[One (M8) Android Development] bbell101584:
Thank you I got it now I didn't realize I had to choose ext-sd for the second partition
[One (M8) Android Development] bbell101584:
[MENTION=1162986]Captain_Throwback[/MENTION] idk if you know but multirom manager isn't compatible with lastest skydragon 5.0. Before you say its because it a m9 port I do realize that I was just curious if the multirom is planning to be updated to work on the m9 eventually not asking for ETA or anything its just i installed the app and opened it and it said not compatible with this device but if I go back to a 501 sense 7 port it works fine so I guessing its just the 502 framework. Not sure though so I figured I would ask
[One (M8) Android Development] Captain_Throwback:
I don't know, but I have no evidence that MultiROM is at fault. Even if I did, you'll need to ask someone else for help. And you should probably at least consider providing a log to give them a chance of identifying the issue :rolleyes:.
[One (M8) Android Development] bbell101584:
I asked you a simple question if you wanna be rude then don't ****ing answer and its just the app that not compatible with this device there is no log to get there no errors no FC or anything just says not compatible with this device but don't worry I won't ask you any more questions at all. Even if you did know id have to ask someone else for help what kind bull is that so you just don't wanna offer me no help. Rolling your eyes huh what a joke. The issue is the multirom manager app isn't supported on the m9 right now I was just asking if it plans to be wasn't looking for any advice so brush up on your reading before talking down to someone
[One (M8) Android Development] Captain_Throwback:
I think you misunderstood my post.

In the MultiROM thread I already started that it couldn't progress anymore without outside/dev help, and that there was nothing else I could do with it. I've also stated on numerous occasions that I can't assist with anything without a log.

If you were only referring to the MultiROM Manager app from the Play Store, I have nothing to do with that. A screenshot might have been helpful, though, to see what you're talking about.

I'm just not sure how you were able to rule out the ROM being at fault when you provided no evidence to suggest it isn't? I'm pretty sure the app reads from build.prop to make sure you're using a compatible device, and if you're using a port where those lines don't reflect your actual device, of course the app will show incompatible.

But you need to slow down before you assume I'm trying to be rude and fully explain your issue and troubleshooting steps. That's what you do in a Development thread. And I sincerely hoped you could find someone to help since my calls for it have gone unanswered.

I sincerely hope your day improves.

EDIT: As I go back and re-read your post, are you really asking about M9 support for MultiROM? We don't even have kernel source for the device yet. If you want it, you should reach out to some devs and post a thread in the M9 section. This isn't the place for that request.
[One (M8) Android Development] bbell101584:
My day is fine and I understand and know its the rom issue cause its a port that's why I only wanted to know if there are any plans to make the app compatible with the m9 that's why I said its a ported rom in the first place everything else is fine and works fine its just the app itself. Im sorry if this is the wrong thread but as I have a m8 and I haven't seen a m9 multirom thread I didn't know where else to ask. I said I didn't want ETA or anything. I understand you don't develop the app but as you seem to be the most knowledgeable about multirom I figured id ask.
[One (M8) Android Development] Captain_Throwback:
MultiROM has to be ported, by devs. There isn't a thread for M9 because no one has asked any devs to port it. So, if that's what you want, you need to start a thread to champion that initiative.

And app compatibility is irrelevant until there's an actual port of MultiROM. That is literally the last thing in the process to worry about, and that's just a matter of contacting [MENTION=3418703]Tasssadar[/MENTION] to add it.

I know I may seem to know all about MultiROM and how it works, but that's a misconception. I didn't do any of the work to get MultiROM or MultiROM TWRP ported to M8. I just build other people's work. That's why I'm a "Contributor" not a "Developer". So, that's why you need to reach out to real devs in the appropriate forum for your request. And maybe once kernel source is available, some devs will be able to help you out.
[One (M8) Android Development] bbell101584:
OK thank you im don't wanna request anything just wanted to inquire if it was going to happen so instead of multirom thread on xda need to actually inquire with multirom manager app developer. My fault for the confusion?
[One (M8) Android Development] threetwentyfizzle:
[MENTION=1162986]Captain_Throwback[/MENTION] , Sorry if this has been covered, I backread this thread about 10-15 pages, but I am having an issue with my MultiRom TWRP Recovery. I think I had a bad flash with SkyDragon V6 as a Primary Rom, as the Rom will not boot, It will boot back into Hboot, and I cannot boot into Recovery from Hboot. If I try to reboot into recovery from the Multirom Menu, I can get into TWRP, but it freaks out, and reboots back into Hboot. I can boot into my Secondary Rom just Fine (GPE), and I have tried to reflash the MultiRom Recovery from within the Multirom App, but it doesn't fix TWRP, It still hangs and reboots back into Hboot. And lastly, I downloaded your latest TWRP you posted a page or 2 back, and flashed it via fastboot, but still no dice.

I am thinking its the Primary Rom causing these issues? Have you had any users report this sort of issue in the past, or any resolution you can think of that can get my recovery back and running so I can at least remove this primary Rom and flash something that will be more stable as a Primary Rom?

I do have a Recovery Log in my Root of my SD Card, Will that help any?
[One (M8) Android Development] Diddy555:
For me most TWRP Problems I had were caused by buggy/incompatible themes. If you have installed one, try to delete ui.zip. Otherwise you can also try to delete the TWRP folder on internal storage and ext sd. But dont forget to backup your backups ;)
[One (M8) Android Development] threetwentyfizzle:
Thx, ended up having to RUU my way out of that problem. Something with that ROM flash just destroyed TWRP.
[One (M8) Android Development] snebojsa:
I also had flickering problem in multirom.

M8 international, unlocked, S-off

run ruu for clean start, firmware 4.16.401.10

installed twrp multirom 2.8.6_20150328-01

then Viper 4.3.0, boot, finish initial setup

then reboot in recovery, flash ElementalX 4.04, boot to system

reboot in recovery, flash multirom-20150216-v31-UNOFFICIAL-m8, post 1862, MD5: c24c87613fbca140f1950c18f065b122

multirom starts flashing but at the end the screen start flickering, and reboot automatically to recovery

in the multirom menu it seems that all is ok, and I flashed secondary rom, Leedroid v7.2.0

everything went well, but when I want to boot to secondary, it boot to primary, Viper 4.3.0

primary boot ok, but when I checked kernel, it was stock although I installed ElementalX

boot in recovery and install ElementalX again, but when inject.boot occur then flickering happened again and automatically reboot recovery

list roms in multirom and there is Leedroid rom listed, I tried to boot but again boot in to primary

Tried above steps again and everything was the same.

Then I flashed multirom v.30 and everything worked like it should.

Maybe this will help somebody, if someone have problems like I did, try multirom v.30.
[One (M8) Android Development] Captain_Throwback:
Why aren't you using the latest versions of anything?
[One (M8) Android Development] snebojsa:
As far as I know, those are the latest versions,

multirom twrp from your sig, and in the BasketBuild that is the latest

multirom 20150216-v31 from post 1862, page 187, I read from there to last page, 220, and there is no newer version,

ElementalX 4.0.4 is the latest.

Did I overlooked something?
[One (M8) Android Development] Captain_Throwback:
The latest (stable) versions of MultiROM are ALWAYS in the MultiROM app.
[One (M8) Android Development] snebojsa:
Ok, installed MultiRom, there is new multirom twrp from yesterday, I am installing it and will report back, thanks.
[One (M8) Android Development] Captain_Throwback:
Install MultiROM v31 as well. The version you have isn't the same version (just because it doesn't say there's an update doesn't mean there isn't one).
[One (M8) Android Development] redwiz666:
Anyone having issues trying to create partations on sd card? It fails at created ext section. Which im assuming I would want. I want to be able to store multirom on my sd card
[One (M8) Android Development] snebojsa:
Ok, I will.
[One (M8) Android Development] Captain_Throwback:
Log?
[One (M8) Android Development] snebojsa:
When the app asked to reboot in to recovery to install, I did. In recovery, script is executed but at the end it said "failed" at the top, but at the bottom it said something like "there is no need to....", so I think the script went well but there is no need to do something... I rebooted and everything is ok, primary and secondary boot fine, so I think that is all ok. Thanks.
[One (M8) Android Development] ckvisme:
( Captain_throwback, 'just because the version number doesn't change does not mean its not updated. Update MultiRom too its probably updated')

I dont know how many times I have to read that before it stays in my thick skull...

Yesterday I updated the recovery with the app - TWRP 2.8.6_2015-04-09 - TWRP randomly crashed a few times so I re-flashed it with the app.. No good.. Zipped the recovery.img with an android - info.text file from Captain_throwback build basket and flashed through HBoot... No good

Then i read again: Captain_throwback saying, 'update MultiRom, just because the number is the same...'

... Face-palm :what:

So I start over update recovery AND MultiRom... ALL GOOD!!!

Just though I should share,

Thanks again Captain_throwback for repeating yourself and generally knowing why people screw up ? ?

device - Sprint HTC One M8 -

~ MultiRom TWRP v2.8.6_2015-03-28 {Captain_throwback} ~ °MultiRom v31 /

(primary-ROM)

*ViperOne 4.3.0 + HyperNova 3.4.0/

(secondaries -ROM)

*LeeDroid v7.0.2 + soundwave 7.0.2 red

* Resurrection RemiX 5.1.0

*DirtyUnicorns 5.0.2

°S-OFF via SunShine

[ Huge THANKS and respect to all of the absolutely brilliant XDA-Devs' and Community for all of your hard work and sharing]*
[One (M8) Android Development] Captain_Throwback:
I actually haven't updated the MultiROM zip since 3/7 . . . :eek:

Because, as I've posted and re-posted in the thread, additional dev help is needed to merge the latest changes in the multirom and kexec-tools source.
[One (M8) Android Development] ckvisme:
Oh... well.? .. Seems to be working now... Not sure what i screwed up before.

Still no love for your request for help? Do they frown on MultiRom, or is it just a busy season with lollipop updates?

Very sorry to hear that, this is an awesome tool ( you guys are doing great work) AND I see you on literally almost every thread I visit helping others... - lol, and I read alot -

Well I hope you can get help soon and please dont give up, im a Huge fan ?

device - Sprint HTC One M8 -

~ MultiRom TWRP v2.8.6_2015-03-28 {Captain_throwback} ~ °MultiRom v31 /

(primary-ROM)

*ViperOne 4.3.0 + HyperNova 3.4.0/

(secondaries -ROM)

*LeeDroid v7.0.2 + soundwave 7.0.2 red

* Resurrection RemiX 5.1.0

*DirtyUnicorns 5.0.2

°S-OFF via SunShine

[ Huge THANKS and respect to all of the absolutely brilliant XDA-Devs' and Community for all of your hard work and sharing]*
[One (M8) Android Development] xdadevelopers-user:
I've got the tools in place to help. Unfortunately I don't know that I have the knowledge necessary. From what I remember of your earlier plea you need someone to take changes that were patched into kexec-tools and multirom and incorporate them into external m8 modules?

If you pretty much know what needs to be done and can direct my efforts I'll be happy to try and help get it done.

Send me a pm if you think I might be able to help and we'll see where it goes.

-xdadevelopers-user
[One (M8) Android Development] ahmad.gh1:
Hey guys i flashed sd rom v7 sense 7 and sd romv5 gpe 5.1 buti couldn't boot to gpe (secondary rom).

Can someone help me?

Thanks
[One (M8) Android Development] fcukmayank:
Some rom are not compatible with multirom

So the best way is to create a nandroid of your current setup and flash other roms
[One (M8) Android Development] titanshadow:
I'm booting GPE from Digital High but for Sense 6 with Bad Boys Sense 6 ROM but as far as I know, there are kernel issues with sense 7 because there is no released source.
[One (M8) Android Development] ckvisme:
As I understand it you will need to flash the MultiRom uninstaller zip through recovery ( to uninstall MultiRom) . After that no need to change TWRP as it will work normally, or just change recovery as you normally would.

Instructions are found in Tasssadar's MultiRom instructions here:

https://github.com/Tasssadar/multirom/wiki/Using-MultiROM

device - Sprint HTC One M8 -

~ MultiRom TWRP v2.8.6_2015-04-09 {Captain_throwback} ~ °MultiRom v31 /

(primary-ROM)

*ViperOne 4.3.0 + HyperNova 3.4.0/

(secondaries -ROM)

*LeeDroid v7.0.2 + soundwave 7.0.2 red

*Resurrection RemiX 5.1.0

*DirtyUnicorns 5.0.2

*BadBoyZ v3.2 + BeyondStock™ V3.2.1

°S-OFF via SunShine

[ Huge THANKS and respect to all of the absolutely brilliant XDA-Devs' and Community for all of your hard work and sharing]*
[One (M8) Android Development] snebojsa:
Have Viper 430 as primary, LeeDroid as secondary, and tried to flash S.Rom as third. Everything went well, but S rom won't boot, just stay on splash screen. When tried to boot to primary, i saw that primary is overwritten with S rom. S rom started to boot but with lot of errors, probably because of mix with Viper rom. Now have just LeeDroid booting, don't know what went wrong.
[One (M8) Android Development] TarekElsakka:
I posted about this before and I was asked for more details and information in order to resolve the problem:

1. The MultiROM version I have installed is "multirom-20150307-v31-UNOFFICIAL-m8.zip

2. The recovery I have installed is TWRP_multirom_m8_2.8.5_20150320-01.img

3. My primary ROM is SkyDragon v7.0 (Android 5.0.2 with Lyopota's Modpack installed)

4. The kernel I have is SkyDragon's custom kernel and I use Lyopotoa's Modpack in order to make it unsecure (even though it probably already is)

Whenever I try to add a ROM using MultiROM, it ends up replacing (or dirty flashing) over my Primary ROM even though it still shows two separates ROMs at the boot screen. I've tried flashing the following ROMs as secondary with the same results:

1. S.ROM

2. SkyDragon GPE

3. a couple of AOSP (CM-based) ROMs

Any ideas on what could be the problem? I am going to backup and try flashing the latest Bliss ROM as a secondary and provide you with a log file in case it happens again.
[One (M8) Android Development] TarekElsakka:
And this is what I get on the multirom app.
[One (M8) Android Development] TarekElsakka:
I just flashed Bliss rom as a secondary and it's as though I didn't even flash anything. Here's the log file: