yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] jcrompton:
Ok so I went to bootloader and fastboot flashed openrecovery-twrp-2.8.1.0-m8.img

Rebooted to recovery and I had my data back. I was able to mount data but when I tried to repair data file system I got an error - something about an unknown multirom error

Went back to bootloader and flashed TWRP_multirom_m8_20141208-01.img

Went to recovery and now multirom present and after two reboots was able to boot into primary SkyGPE ROM

Now the latest is that open MultiROM app and try to boot to Candy and sure enough - no cellular data

Somehow that latest combination of TWRP and installing Candy to secondary screwed things up.

I reinstalled the TWRP that you just posted and was able to get a succesful repair of the data partition but still no cellular data for the ROM

I will now try to install BlissPop -
[One (M8) Android Development] Captain_Throwback:
You'll definitely need to reinstall the ROM with the no data as it wouldn't have installed properly/correctly with the recovery you used (I don't think).
[One (M8) Android Development] jcrompton:
Ok so I tried to install BlissPop with the latest TWRP and it will install (and the data repair with that recovery now works) But after installing the ROM with no errors I tried to install the Gapps and I got an error -- log attached

When I tried to boot into that ROM got stuck at the spinning BlissPop animation (left it for about 15 minutes)

Something is screwy IMO wit the latest recovery and installation of CM12 still
[One (M8) Android Development] Captain_Throwback:
Then why does it work perfectly fine for me? And the other person that confirmed working?

I'm not sure what's going on in that log. I see the Gapps install successfully in there, but it seems to have an issue repacking the boot.img. I was able to flash Candy5 with no issues. I'll try BlissPop now. I'm using Gapps from Basketbuild.

EDIT: I think the issue is the ROM. I was able to flash it with no issues. However it appears to take a LOOOONNNGGGG time at the boot animation. See here: http://xdaforums.com/showthread.php?p=57379355#post57379355.

Candy5 worked fine, as does CM12. I think you might be in good shape now. I don't think anything is wrong with the recovery.
[One (M8) Android Development] jcrompton:
LOL ... I was definitely not insinuating that work was faulty or anything BUT you have been doing this long enough to know that there are way too many variables to assume that because it worked for you and one other ..... that it is going to work for everyone.

I'll try again later. Thanks for trying though! Your work is appreciated
[One (M8) Android Development] Captain_Throwback:
Did you see my edit above?

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

It appears that BlissPop encrypted my device, which would explain the long boot-up time, and it not actually booting up, since it's trying to encrypt the partition on which the ROM resides while simultaneously trying to boot it.

Definitely something wrong with that ROM. And now I have to wipe out data to fix it. That's very annoying.
[One (M8) Android Development] jcrompton:
Sorry

That stinks
[One (M8) Android Development] str8str:
I to have no problem with blisspop. Everything flashes and works fine

---------- Post added at 06:02 PM ---------- Previous post was at 05:58 PM ----------

There is no way the rom encrypted your phone. You probably had done it or selected it by mistake. If it was the rom every single person who downloaded it would have the same thing
[One (M8) Android Development] Captain_Throwback:
Are you really telling me that I accidentally encrypted my phone? Seriously?

Perhaps it wasn't fully encrypted, but recovery seemed to think so.

EDIT: And every single person that downloaded the ROM DID have inordinately long first boot times. The only variable is that they didn't flash it as a secondary in MultiROM. Do me a favor - try flashing it that way and let me know what happens. Use these GApps (they're the ones I flashed after the ROM in MultiROM).
[One (M8) Android Development] jcrompton:
Are you installing Bliss as a secondary or as a primary?
[One (M8) Android Development] Captain_Throwback:
I'm going to have to re-create your exact procedure and see if I have the same issue as you.

I still don't understand how this can be a MultiROM issue, unless it's the feature that copies a ROM from primary to secondary that's broken. Have you tried doing it a different way? I have several ROMs as secondaries, and they all boot fine. But I flashed them direct or restored backups to them. Have you tried doing that?

---------- Post added at 07:01 PM ---------- Previous post was at 06:48 PM ----------

I just copied my Primary ROM over to a secondary and it booted up just fine. I'm really not sure why you're having issues with it [MENTION=230362]jcrompton[/MENTION]. I'm really not convinced MultiROM is at fault, unless we can come up with a log or multiple reports that show us why.

I am getting some odd behavior from ItsOn, which is a Sprint thing, and WiFi tells me connectivity is low. I'm not sure why that is. I think the proper symlinks don't get set when simply copying over a ROM. That's why I always flash it or restore a backup. It might just be a limitation of that method - it might not work for all ROM/ROM types.
[One (M8) Android Development] jcrompton:
es I would ve to agree with your assessment but I have tried restoring backups as well .. to date I have not found a way to "keep" any of my GPE Lollipop secondary installs alive (where they don't bootloop) AFTER I mess with the primary ROM , i.e, install a new version of a CM12 ROM as a dirty flash, or do a clean new install. It seems that flashing in any way that primary slot loses the ability of a GPE LP ROM to not bootloop (whether copied or restored form backup) -- and the problem is that even dirty flashing over the GPE Rom doesn't save it from the bootloop. I am glad you aren't experiencing that but I have consistently
[One (M8) Android Development] russellvone:
just curious....why don't you just keep one primary rom, then use all others as secondary?

that's kind of the point of MultiROM isn't it?

use a known bugless ROM as primary so you have a (perfectly working) ROM at all times, while flashing secondary ROM's for testing and fun?
[One (M8) Android Development] jcrompton:
I would for SURE do that if I could flash / reflash CM12 as secondary --- unfortunately , it is the one that is getting updated with good fixes almost daily.

It is still a blessing to have MultiRom but disappointingly complicated in that you have to know which you can install as secondary and which you can't, etc etc
[One (M8) Android Development] Captain_Throwback:
In that case, why not use that ROM as your primary, and have your "stable" ROM as secondary? That's what I do.

My daily driver is GPE, which I run from the ext4 partition on my SD card. Also installed as a secondary is my BeyondStock ROM, for if I need Sense or want to use HK audio. I don't even usually have anything installed to the device - just a kernel so I can have the MultiROM boot menu. No reason you can't use the ROM that changes every day as your primary. Primary doesn't mean you have to use it the most ;).

In fact right now I have a stock unrooted ROM as my primary, so I can receive the OTA (whenever it may arrive). Only thing I did was flash my BeyondStock kernel to it so I can boot my secondary, which won't affect my ability to receive an OTA.
[One (M8) Android Development] jcrompton:
Man I hate for you to look at my login name and run, but that's exactly what I want to do. But therein has been the problem:

Anytime I change the primary Rom (in this case the CM12 based ROM ) the secondary GPE ROM becomes un-bootable. There is something that the install of the primary CM12 ROM (I've tried Bliss. Candy, and plain ole CM12) and when I flash an update it screws up my secondary ROM and my "daily driver" boot loops (lol.. I see those floating colored circles in my sleep now)

Bless you man
[One (M8) Android Development] Captain_Throwback:
Ah. Interesting. That I have not tried. So if I was to flash CM12 as a primary right now, you're saying that I won't be able to boot my secondary? Though in my case, it may be different, since my secondaries are on SD card rather than on /data.
[One (M8) Android Development] jcrompton:
Yes absolutely

Can I easily only partition a part of my extsd card as ext4 and just do what you do? How?

Maybe you can try my deal first but I suspect that being on the \data is the reason!
[One (M8) Android Development] Captain_Throwback:
Well, looks like it's your device.

I flashed GPE as a secondary first (to Internal), and booted it. Then back to recovery, full wiped, and flashed CM12 + GApps. Booted it up.

Rebooted, chose GPE, and it booted fine. Rebooted again, back to CM12. Booted fine. Rebooted back to GPE one more time to make sure.

Then, I booted into one of my secondary ROMs on external, booted right up. However, when I tried booting into my daily (GPE on external), the boot appeared to get hung up. Turns out I was probably just being impatient, but I rebooted back to recovery and repaired SD-Ext partition, and rebooted. Seemed to get stuck again. Rebooted to recovery again, flashed updated GPE, and booted it up. Seemed to be getting stuck, and I was about to reboot again when I saw the optimizing apps screen. Now, I'm posting about it from my daily ;).

So it seems to be working for me. My only guess is that whatever ROM you're trying to run as primary is the problem.
[One (M8) Android Development] jcrompton:
You may have done it and didn't mention it but it appears you missed one of the main steps :

Did you reflash the primary CM12 ROM to an updated or another CM12 ROM -- that is the step that screws up booting the secondary GPE ROMs from booting ! Everything works great for me until I have to change or update the primary ROM - that is what makes the secondary ROMs unbootable
[One (M8) Android Development] Captain_Throwback:
How are you doing that, exactly? Are you wiping cache and system, then flashing? Are you reflashing GApps?
[One (M8) Android Development] jcrompton:
I would typically wipe cache and dalvik, flash the ROM and then flash GAPPS

That works will for the primary. I actually dirty flashed several versions of Bliss updates without problems ..... but each flash killed my secondary GPE
[One (M8) Android Development] Captain_Throwback:
Okay, so I booted back to recovery and flashed Candy5 over my CM12. I wiped nothing (GApps should persist through updates). Booted up the ROM. Rebooted and tried to boot into GPE on my internal, only to find out that Candy5 doesn't have a MultiROM-compliant kernel. Booted into recovery and flashed CM12 back over Candy5 (again wiping nothing). Booted it back up. Rebooted again and chose GPE on my internal. Booted right up. Rebooted again into my daily GPE on external, and I'm posting this from it right now.

So again, I'm sorry to say, it appears to be your device. Did you ever find an RUU to run for it? I've run one recently so my device is nice and clean.
[One (M8) Android Development] jcrompton:
Which type of RUU did you run? You are GPE are you?

Would not just formatting the data do it ??
[One (M8) Android Development] Captain_Throwback:
No, I have a Sprint device, so I run the latest Sprint RUU. You need an RUU for your carrier. Formatting data isn't the same. The RUU will normalize all the device partitions. It'll basically give you a clean slate and get rid of any lingering corruption that may have happened on the device.

Any additional discussion on this is off-topic for the thread, though. Since it works for me, it doesn't appear to be a MultiROM issue.
[One (M8) Android Development] teethgrinder32:
How did you fix the no cellular data issue? I'm getting the same thing and I've tried fixing data. My setup is similar. I have Skydragon GPE as primary and I've tried Candy, CM12 and CM11 (wifi doesnt work either) and I get no cellular data. I'm on an international M8 (Vodafone UK) )with the GPE L firmware.

EDIT: A GPE rom on secondary works fine on first boot then loses wifi on the second boot.
[One (M8) Android Development] Captain_Throwback:
I haven't had the no cell data issue since using the updated recovery, myself.

And dirty flashing the GPE ROM over itself will get your WiFi back, and it should stay after that. Not really sure what causes that.
[One (M8) Android Development] teethgrinder32:
Thank you my friend. Dirty flash worked. Now need to figure out the cell data issue so I can have a CM and GPE, not GPE and GPE
[One (M8) Android Development] jcrompton:
Me again

[MENTION=388504]captaint[/MENTION]hrowback

Is there a guide or good source to show how to put an ext4 partiton on my extsdcard ? I tried but after I created one fat32 partition and one ext4 partition on my extsdcard neither one were visible in TWRP

I want to try to put a secondary on that ext4 partition like youmentioned
[One (M8) Android Development] Captain_Throwback:
How did you create it? Using the option in TWRP? Did you reboot recovery after doing so?
[One (M8) Android Development] jcrompton:
I don't understand how to do that with TWRP

(I did sb on the exearch - sorry)

What I would like to do is make a partition about 25gb on the extsd that is fat32 or ex-fat (which would you suggest)?

And then have another partition on the extsdcard that is ext4 for multiROMs

Can I do that?
[One (M8) Android Development] Captain_Throwback:
Advanced -> Partition SD Card in recovery (make sure you're on the latest version).
[One (M8) Android Development] jcrompton:
What settings (inTWRP) did you use to create the ext4 partition? Also is there a way to also have a partition for windows accesible storage?
[One (M8) Android Development] Captain_Throwback:
I never said I created mine in TWRP. The first partition on the card is always going to be a FAT-based partition, which Windows can read. Typically Windows can't read an ext4 partition, but it will mount in a Linux-based system.

Just choose whatever size you want the ext partition to be, choose 0 for SWAP size, and it'll partition the rest as FAT32. Once completed, you can use the change FS option (in the Advanced Wipe Menu in TWRP) to change the FAT32 partition to exFAT if you'd like (provided you're using an XC card).
[One (M8) Android Development] jcrompton:
I do recognize that some of our conversation may make you wonder about my intelligence ... but that was soooo easy after your explanation ( part of it was having a bad theme so the SD Partition tool wasn't visible until you "made" me look for it.

I try some ROMs on the ext SD now

Thanks!!
[One (M8) Android Development] jmgg2k:
I have the same bug with cm12 (candyrom) as secondary (no cell data issue). My internal Rom is Viper 321, as secondary roms i have GPE DH rom (working fine), and Cm12 CandyRom with no cell data. My firmware is the "carrier agnostic firmware" that came with GPE DH rom.

[MENTION=1162986]Captain_Throwback[/MENTION] could you please review that "no cell data" bug ?. Thanks
[One (M8) Android Development] Captain_Throwback:
Review with what? What recovery are you using? You've given me nothing to work with.
[One (M8) Android Development] jmgg2k:
im using your latest multirom recovery (2014-12-08)
[One (M8) Android Development] Captain_Throwback:
That's not the latest, actually. There's a newer version posted in the thread. Try it and report back, please. Next time with logs, if there's still an issue.
[One (M8) Android Development] teethgrinder32:
Which logs do you need? Just "Copy Logs To SD" in TWRP?
[One (M8) Android Development] Captain_Throwback:
Well the data issue is happening in the ROM, so perhaps a logcat as well.
[One (M8) Android Development] jmgg2k:
Candyrom installed again as secondrom with recovery (2014-12-09-p1)... still no cell data.
[One (M8) Android Development] teethgrinder32:
On it, might need a few hours though as I need to head out now. Unless jmgg2k can provide some info in the interim.
[One (M8) Android Development] Nilsonf:
Try going into settings, Mobile data, APN and change the APN protocal to ipv6
[One (M8) Android Development] jmgg2k:
The bug is no data and signal (like no sim card on phone)
[One (M8) Android Development] Captain_Throwback:
Can you confirm you have data if you flash it as a primary?

I flashed Candy5 yesterday as a secondary and had data just fine. Same with CM12.
[One (M8) Android Development] jmgg2k:
will try it, and post
[One (M8) Android Development] Captain_Throwback:
Thanks.

Just for proof, here are the screenshots that show CM12 as a secondary, and it booted up, with data connected.
[One (M8) Android Development] jmgg2k:
data (LTE) and signal confirmed working on Candyrom as primary rom... i will swap roms with Viper 321 (former primary) and report
[One (M8) Android Development] Captain_Throwback:
I flashed directly as a secondary. It should work that way.
[One (M8) Android Development] jmgg2k:
Im now with Viper rom 321 as primary, GPE DH secondary (fully working) and CandyRom with working data and signal (after being installed as primary rom and swaped later with Viper rom).
[One (M8) Android Development] jcrompton:
Ext4 ExtSD Installs

I have been playing with installs to an ext4 partition on my extSD. I have a working Primary Skydragon GPE ROM. I did a fresh nandroid back and then created a new install on my extsd card ext4 . The GPE backup crreated ROM just reboots to TWRP over and over. Of note a backup of Skydragon 4.4.4 ROM works great on the ext4 partition.

Any thoughts? Should I try a dirty flash over the backup created GPE ROM?
[One (M8) Android Development] Captain_Throwback:
I wouldn't dirty flash over a backup, no. I can install digitalhigh's GPE directly to the partition with no issues.
[One (M8) Android Development] Ather:
I have the latest recovery [ 2014-12-10 (1)] and MultiRom v30, i tried to install Candypop on my sdcard along side cm11,but it doesn't show up in the list, the success message showed up fine...
[One (M8) Android Development] teethgrinder32:
Here is the logcat and recover log for the no data issue. Not urgent. I've shuffled my setup so I don't need CM on secondary now but in case it is useful.
[One (M8) Android Development] Ather:
I just tried with another cm12 rom, same thing.. Finished successfully, when i back out i get a partition named loop and vfat.. So that's candy pop and bliss pop, no luck with them :/
[One (M8) Android Development] Captain_Throwback:
Seems everyone is late to the party . . .

http://xdaforums.com/htc-one-m8/development/multirom-v28-unofficial-port-t2884413/post57197943
[One (M8) Android Development] Mike02z:
[MENTION=1162986]Captain_Throwback[/MENTION], you might recall my issues with getting WiFi to turn on when using the DH 12.5BF release as my primary ROM on my VZW M8 with the most current firmware. When using CleanROM as my primary, no issues with WiFi.

I tried again tonight with the DH 12/9 release as my primary ROM and the latest Multrom TWRP (V2.8.2) and first boot and I have Wifi and no noticeable issues. When I flashed MultiRom I picked the stock insecure GPE kernel and it would boot directly into HBOOT then I flashed the latest Elite GPE kernel manually and then did the Inject boot.img file. So the only difference is the version of DH's ROM.

I then installed Vanillapop 1.4 and ran into a few issues but feel confident I can get it working. The primary is running flawlessly.

Great job on this port and your TWRP!
[One (M8) Android Development] k4p741nkrunch:
I've searched through this thread, but I can only find one other person with my issue and I didn't see a solution posted.

I've been using MultiRom for a month or so now and have had zero problems.. Until this week. I decided to change my primary to Skydragon 5.0.1 and update my firmware to modified 3.11.1700.2 with a Sense boot loader to avoid repartitioning. I've got HolyAngels kexec-hardboot patched kernel, but the touch does not work on the boot menu! It's such a small thing, but honestly having the ability to tap on a ROM to boot it MADE this mod for me. I feel like I'm back in the HTC Evo days using volume keys to navigate the menu. Anyone know of a way I can get my touch menu back while keeping Skydragon?
[One (M8) Android Development] Captain_Throwback:
You have to wait until we get updated touch panel firmware for Lollipop. Either that or don't have a Lollipop ROM as your primary. Sorry, those are the only options.
[One (M8) Android Development] miffymiffy:
Ive been having issues trying to remove multirom. I can no longer install any roms. I continually get an unable to open zip file warning.

I have tried the uninstaller zip, but this fails also.

I have tried all recoveries however same still occurs.

Whilst on captns twrp, if I try to flash a file, recovery just restarts.

All in all, ive not had success with multirom which is disappointing. Could never get two roms to work.

Any ideas?
[One (M8) Android Development] jcrompton:
Lag on Secondaries

[MENTION=388504]captaint[/MENTION]hrowback

Thank you so much for your help in the lst few days. I was successful in getting the latest BlissPop CM12 ROM to install to an extSD ext4 partittion yesterday and last night. I have noticed that there is a bit of lag in the menus opening up, etc. Is there a secret to improving this lag. I've not heard you mention it here as a problem for you .... ?

Is it the brand or type of SD card that slows things down? Do you have suggestions?
[One (M8) Android Development] Captain_Throwback:
There will ALWAYS be lag running ROMs from external SD.

It's just not enough lag to bother me :rolleyes:.

Plus, the advantage of being able to run my daily ROM from SD card is that when I have to swap between devices (as I had to do earlier this week to send my device to HTC for repair), I can just pull out the card, put it in my backup device, and boot up the same exact ROM.

It also survives factory resets, data wipes, and RUUs. The benefits outweigh the disadvantages for me.
[One (M8) Android Development] jcrompton:
Yes that sounds really good and I'm going to try. Is there a particular type of SD card or brand that is better? What size do you have?
[One (M8) Android Development] Captain_Throwback:
I have a SanDisk 128GB Class 10 SDXC, with a 16GB ext4 partition. I've found SanDisk cards to be the most reliable, though I also have an older Samsung Card that's held up well. And Samsung creates most of the eMMC chips that our devices use as internal storage, so that's a good choice for people that are OCD and like brand continuity.

Here's a link to a Samsung Card. I might look into getting one myself, because I AM a little OCD, lol.
[One (M8) Android Development] jcrompton:
Wow what a great deal. I just ordered one. Thank you very much .

It seems like I was reading somewhere in the last day or two about someone having a Windows 7 version on there SD card..... That would be the extreme multirom multi OS setup

That wasn't you was it?
[One (M8) Android Development] Captain_Throwback:
Not me. I'm not even sure how that would work.
[One (M8) Android Development] jcrompton:
I agree -- didn't really focus on it but was in the back of my head.

One last question for now -- what program do you use to partition your cards? I used the TWRP method that you explained yesterday and it worked well. But I was hoping that I might be able to use a PC program or other method when my new card arrives tomorrow and possibly copy my existing partitions form my old card and possibly even create an additional partition for other purposes since I will have 128gb (!!) of space.
[One (M8) Android Development] Captain_Throwback:
I typically use GParted to partition my cards, and then reformat the created FAT32 partition in Windows as exFAT.

Creating additional partitions is pointless since Windows will only ever see the first created partition. What other partition would you create?
[One (M8) Android Development] ziaulh.ch:
Can someone tell me how to patch kexec-hardboot? M7 doesnt have any stock kernel patched. I like stock kernel better.