yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Rix70:
After swap the primary rom works and updated nightly but the second one nothing....after click on the rom appear a message for hardboot/kernel compatibility....I don't remember well.

I reflashed ex but nothing..reflash boot.img but nothing.

now I proceed to dirty reflash and see ;)
[One (M7) Original Android Development] nkk71:
after you flash a kernel with kexec-hardboot support, you need to "Inject curr. boot sector"
[One (M7) Original Android Development] Rix70:
....unfortunately nothing...

This problem happened after I swap the roms order, now the message appear when I boot the secondary but in the first row it say "kernel-hardboot support is required to boot this rom. but the second row say "install kernel with kexec-hardboot support to your

internal

rom!"

but the primary boot perfectly....

now return to swap and see if resolve.

Thank you

EDIT: I think that the solution was very simple......Exodus rom do not support "kexec-hardboot" :)

Now I reswap the order and all returned perfect!!! :)

Thanks
[One (M7) Original Android Development] mitchst2:
Sorry bad advice from me. Forgot to remind you primary kernel needs kexec support. Often you learn these things the hard way.

PS

My primary Rom is Eragon which I'm back onto as my daily driver. Started getting random reboots on Exodus. Good as it is that's just annoying.
[One (M7) Original Android Development] Rix70:
No problem my friend!! ;)

No, if I setup a sense rom use viper...

However, I have a question, in all roms the first step to good install is "WIPE" all, system and data.....

In multirom the sd is used from all roms, this can cause issue between vaious type of roms...cm...sense....aosp?

Thanks
[One (M7) Original Android Development] mitchst2:
I never wipe for secondary as it creates a new folder in data/media.

BTW XenonHD has kexec patch.
[One (M7) Original Android Development] bdizzle1686:
I'm on VERIZON m7, and would LOVE to test!!! Plz send me link and I'll get right on it!!!
[One (M7) Original Android Development] nkk71:
Well the MultiROM TWRP recovery and MultiROM_zip in the second post are universal, so they should work on M7_U/UL, Sprint and Verizon just fine.

However you need to find a

Verizon specific kernel

that supports kexec-hardboot (since I dont follow Verizon threads, I dont have any links around, sorry);

that kernel will only be needed in the primary partition/ROM, the secondary ROMs will work fine with their own [normal] kernel.

As always, remember to have backups, just in case.

PS: remember to only flash

Verizon compatible

ROMs/MODs/etc.
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

Official at last. Good work.
[One (M7) Original Android Development] mitchst2:
Deleted
[One (M7) Original Android Development] nkk71:
Yeah saw the update, will edit the OP later
[One (M7) Original Android Development] nkk71:
any feedback? all working okay?
[One (M7) Original Android Development] bdizzle1686:
2bhonest w/ ya, haven't done it yet. Downloaded it, but haven't gotten to testing yet. Been dealing with a few issues trying to figure out how to get S-Rom compatible on Vzw, plus had my daughter this past weekend-now, she's probably going back to her mom's tomorrow or next day. But I do have it all downloaded and ready to go, made a backup of my partitions, etc. So I'll probably get to it by Thursday.
[One (M7) Original Android Development] nkk71:
No problem, enjoy your time with your daughter :good:
[One (M7) Original Android Development] Rix70:
Deleted
[One (M7) Original Android Development] nkk71:
You can use the official app from play store, it's been updated
[One (M7) Original Android Development] Rix70:
But I have the 2015/08/06 version installed on my phone..

You have 2015/07 ....? I don't understand sorry..

Inviato dal mio One utilizzando Tapatalk
[One (M7) Original Android Development] nkk71:
I *think* [MENTION=4333421]mitchst2[/MENTION] was just showing that the official app will show an update to 2015-08-06(1) if he has the 2015-07-04(1) installed
[One (M7) Original Android Development] Rix70:
I love this multirom.. Works perfectly and I now love aosp/cm ROMs.

Thank you so much!!! ?

Inviato dal mio One utilizzando Tapatalk
[One (M7) Original Android Development] mitchst2:
Yes that was it. I hadn't updated to latest as all was OK. I have now. Thanks

mitchst2
[One (M7) Original Android Development] nkk71:
And just FYI, it does seem that official app support makes a difference:
[One (M7) Original Android Development] mitchst2:
Well deserved attention.

Can't believe so many didn't update before though.

mitchst2
[One (M7) Original Android Development] nkk71:
yeah, me too, since this is essentially a huge hack, i can't believe people would rely mostly on the app

... not to mention how much I dislike flashing recovery, using apps, instead of the "fastboot flash recovery ...." method
[One (M7) Original Android Development] mitchst2:
Funny that. Even though the app reminded me I hadn't updated I downloaded the recovery from here. I then flashed the image in recovery though.

mitchst2
[One (M7) Original Android Development] FP94:
hi guys

i've a problem here

i'm on hboot 1.55 unlocked with s-on

the strange fact is that i can't boot into the modified recovery but i see the multirom boot menu

i've tried with and without the app but i've still the same problem
[One (M7) Original Android Development] nkk71:
I really don't recommend running a huge hack on an S-ON device with outdated firmware
[One (M7) Original Android Development] FP94:
my phone is working, i'm on viper 9.0.0 working flawlessly

the hack IS actually WORKING but i cannot enter in recovery
[One (M7) Original Android Development] weigeloveu1:
thx,is there any way to implement multirom boot to f2fs now?cause most of rom cant aware if f2fs.so i think if it could be that the primary use f2fs and secondary ext4
[One (M7) Original Android Development] ad2003:
Wow this is great! Just used multirom with my HD2 back in the days and loved it "nativeSD" it was called. Great to see the same approach on newer devices. Just testing it our right now.

Would be cool, if multiboot would remember which rom is running and uses this rom for the startup. I am asked to boot to internal rom, everytime I am booting.

Works great.

thx
[One (M7) Original Android Development] ejswagon:
There is an option to switch from autoboot to " use last booted rom" in multirom/settings/configure autoboot.
[One (M7) Original Android Development] Xib0:
First of all thanks for porting MultiRom to m7. It works great for me. I have only one problem. I cant use MTP with my internal Rom since i flashed MutltiRom. In the modified recovery MTP works.

Have anybody else the same Problem?

I am using:

Internal: ViperOne 9.0.0 with ElementalX 20.2

MultiRom: v32f with latest modified TWRP Recovery (06.08.15)

Firmware: 7.19.401.22

HBoot: 1.61

S-OFF
[One (M7) Original Android Development] nkk71:
Havent had time to look into this, didnt think it's a priority... any ROMs out there that rely on f2fs? (link pls)

MTP shouldnt be affected in booted ROM by multirom, and I havent encountered this issue; though I have ViperOne 9.0.0 in a secondary slot with it's own kernel and MTP works fine

you'll have to track down whether it's an issue of ROM+kernel, some setting, some app/tweak, or possibly even a driver issue (check Windows Device Manager)
[One (M7) Original Android Development] Xib0:
I used the MultiRom uninstaller, wiped Cache/Dalvik Cache and flashed the lastest official TWRP. After that i booted ViperOne without flashing ElementalX again and now MTP works again. For me its look like MultiRom destroys the MTP function of ElementalX when its injected in the kernel. But im not sure :o
[One (M7) Original Android Development] nkk71:
but i'm running ElementalX (the older one) + ViperOne 7.0.x in primary and have no issues. will flash new EX + ViperOne 9 later, and see what gives

anyway, MultiROM doesn't "destroy" anything, it only injects itself into the main kernel so it can show up on boot, the actual primary kernel pretty much remains untouched.

EDIT: and using the uninstaller was a bit of overkill imho, you could have just reflashed ViperOne 9 (without injecting if you're worried about that), and that would have worked just as well
[One (M7) Original Android Development] Xib0:
I used ViperOne and ElementalX for 3 months or longer and modified the system, so it was easier for me to uninstall MultiRom than reflashing ViperOne.

I did not want to be disrespectful, the word "destroy" was wrong. Maybe one could say that MultiRom has an influence of the MTP feature with the newest ElementalX.

It would be nice if you can take look on it.
[One (M7) Original Android Development] nkk71:
no worries, i didnt take it as disrespect, what I meant to say is that MultiROM doesnt actually "change the kernel", it "hooks" into it, basically "renaming" the initial startup, to go to MultiROM, then once the boot menu selection is complete, it "hands over" back to the normal kernel code.

anyway, flashing atm.... will keep you posted, as you know, first bootup takes quite some time :eek:
[One (M7) Original Android Development] nkk71:
This will have to wait, my M7 is soooo messed it up it seems :eek::eek::eek::eek:, I cant flash anything :rolleyes:
[One (M7) Original Android Development] Xib0:
Yea... Sometimes i would like to have more than 32 GB :D

You must not do this now, but please post it when you flashed it and had the same problem. Make sure, that you dont use the stock kernel of ViperOne but ElementalX :o
[One (M7) Original Android Development] nkk71:
sure will, but

doesn't really matter, the "inject" is the same

words of wisdom: don't flash wrong firmwares :p (<- seems that's what i did at some point :cyclops:)

will let you know how it goes, but my whole m7 was messed up due to too many flashing "i dont know what" things.... seems nice and clean after an RUU, yay :D
[One (M7) Original Android Development] nkk71:
I stand corrected, just tried and can confirm, MTP will not work,

if

you have TWRP->Advanced->MultiROM->Settings->Enable ADB checked

(this could very well apply to most situations)

if it's not checked (the default for most people), it works fine

will fix in next build

bad:

[ 28.173721] c2 1 init: starting 'adbd'
[ 28.174027] c2 1 init: service 'adbd' is running
[ 28.174179] c2 1 [USB] func_en_store: adb function is already enable

good:

[ 11.408637] c0 1 init: starting 'adbd'
[ 11.408942] c0 1 init: service 'adbd' is running
[ 11.409156] c0 1 [USB] android_switch_function: android_switch_function: 131, before 129
[ 11.409247] c0 1 [USB] android_switch_function: # mtp
[ 11.409247] c0 1 [USB] android_switch_function: # adb
[ 11.409278] c0 1 [USB] android_switch_function: # mass_storage
[ 11.409278] c0 1 [USB] android_switch_function: android_switch_function: vendor_id=0xbb4, product_id=0xdea
[ 11.409278] c0 1 [USB] android_bind_enabled_functions: android_bind_enabled_functions bind name: mtp
[ 11.409308] c0 1 [USB] mtp_bind_config
[ 11.409339] c0 1 ===========interface_id 0 mtp
[ 11.409400] c0 1 [USB] android_bind_enabled_functions: android_bind_enabled_functions bind name: adb
[ 11.409430] c0 1 ===========interface_id 1 adb
[ 11.409461] c0 1 [USB] android_bind_enabled_functions: android_bind_enabled_functions bind name: mass_storage
[ 11.409461] c0 1 ===========interface_id 2 mass_storage
[One (M7) Original Android Development] Xib0:
Thanks for the fast testing. I checked "Enable ADB" because i found it useful.

If i only had known that this caused the problem i would not have deleted MultiRom :(
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

Are M ROMs likely to cause similar issues that L Roms did initially?
[One (M7) Original Android Development] nkk71:
no idea, havent had much time lately for xda etc

but i think Tasssadar did some modifications for the M preview... guess we'll have to wait and see :o
[One (M7) Original Android Development] mitchst2:
One developer has mentioned an M8 GPE port besides the AOSP ROMs that will become available so I hope there's still demand for this.
[One (M7) Original Android Development] nkk71:
post me any links when they are released, and i'll be happy to test. :D:cowboy:

anyway, i'll probably keep updating for the M7 since I'm also working on this for the M9 (which I havent been able to release yet, and at this time is a bit cumbersome due to the lack of kernel, so it requires a few more steps)

and contrary to the "thanks" or feedback (or lack thereof), it still seems a somewhat popular mod:

unless if that's you downloading it a lot of times :p from different IPs :eek:
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

Latest gpe skydragon failed to boot. Got the cancelled boot to protect.... Message

http://xdaforums.com/showthread.php?t=2400161
[One (M7) Original Android Development] Rix70:
Hi guys

I installed cm rom to primary few days ago and when I apply a theme with custom bootanimation it works.... But when the rom is secondary the boot animation remain stock.

Please, how I can resolve this little thing?

Thanks

Inviato dal mio HTC One utilizzando Tapatalk
[One (M7) Original Android Development] nkk71:
is the theme a TWRP flashable zip? if so, it will only "automatically" flash to primary. You can still flash it to secondary, by downloading only, then manually:

TWRP -> Advanced -> MultiROM -> <select ROM you intend on updating> -> Flash Zip, then select the addon/theme for that particular secondary ROM... then the addon/theme will go to that particular slot
[One (M7) Original Android Development] nkk71:
Just got back, will test / look into it.

On the bright side though, before I left, already got TWRP slightly better,

MTP on startup now works properly

USB-OTG now also works properly

didnt wanna upload, before finalizing it, so hopefully later this week, after I catch up on some work
[One (M7) Original Android Development] nkk71:
mitchst2, sorry, didnt take any screenshots, but flashing to primary, then moving seems to (kinda) work, didnt properly test,

but the updater-script, is definitely not something multirom will like

eg:

...
package_extract_file("rom/system.img", "/dev/block/mmcblk0p35");
....

not good practice, if I understand this "thing" correctly; it may try to work-around the kernel/boot.img, but that above thingy, isnt going to work at this time.... maybe it never should

.
[One (M7) Original Android Development] mitchst2:
Not to worry. Did you try as primary?

mitchst2
[One (M7) Original Android Development] Rix70:
Thanks for response..

No, I mean CM theme....it apply bootanimation by theme app only in the primary rom....

However I solved manually in system /media ?

Thanks again

Inviato dal mio HTC One utilizzando Tapatalk
[One (M7) Original Android Development] nkk71:
it works fine as primary and secondary (screenshots attached), but due to the

...
package_extract_file("rom/system.img", "/dev/block/mmcblk0p35");
...

it cannot be flashed to secondary (even if you attempt, it will just overwrite the primary system partition... as long as it's the correct partition, so on Sprint it'll probably just crash, cause p35 is boot.img and therefore not big enough)

unfortunately, there's no easy workaround for this either, basically the updater-script is treating "rom/system.img" as a

file

and "extracting" it directly to the hard coded system partition

one possible work-around would be to extract it to the internal storage (assuming there's enough space; cause there isnt in RAM, so it'll crash), mount the .img and then write the files to the MultiROM system location

... however, way too many assumptions for this to be a reliable method

the alternative would be to repackage the ROM into the more traditional manner on the PC, change the script, etc.

or, the easiest:

make a backup of current ROM, flash to primary, move it to secondary, restore backup, boot up ;)
[One (M7) Original Android Development] mitchst2:
Yeah just discovered today it's borked my primary ROM. Only noticed after Exodus performed a very random reboot.

mitchst2
[One (M7) Original Android Development] nkk71:
The primary data partition should be intact. You could do a backup, then dirty flash the primary again and it should be good
[One (M7) Original Android Development] mitchst2:
Wasn't using it anyway so installed that gpe to primary. Somehow it managed to nuke my secondary (daily) as well [emoji24] luckily had a recent nandroid.

It's on there now but I recommend everyone steer clear.

mitchst2
[One (M7) Original Android Development] nkk71:
weird, it shouldnt have touched your secondaries :mad: :(
[One (M7) Original Android Development] coendeurloo:
I have installed MultiROM and I tried installing 'AICP - 10.0 - LP 5.1.1_r6' alongside my existing Google Play Edition + ROM, but it keeps hanging at: 'Patching system image unconditionally...'
[One (M7) Original Android Development] mitchst2:
How long did you wait? That message is normal and sits there for a while.

mitchst2
[One (M7) Original Android Development] coendeurloo:
I think I waited for about 15 minutes, the phone didn't get any hotter like it normally does when it is actually doing something, and it just seems like it was hanging. Do you recommend waiting longer?
[One (M7) Original Android Development] mitchst2:
No shouldn't take that long to flash.

mitchst2
[One (M7) Original Android Development] coendeurloo:
Any suggestions or is this issue related to the ROM in question?
[One (M7) Original Android Development] mitchst2:
Not used AICP in a while, but it used to flash OK. I always had an issue with screen touches during calls as the screen wouldn't switch off.

You could try Exodus. Well worth a shot in my opinion, plus if it works you'll know it's ROM related.

mitchst2

---------- Post added at 02:13 PM ---------- Previous post was at 01:17 PM ----------

@coendeurloo

Just installed AICP with no issues whatsoever. Patching system image stage only took about 60 seconds.

Unfortunately for me the proximity sensor still doesn't work on this ROM.

mitchst2

---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------

Try downloading the ROM again. Bad download?

mitchst2
[One (M7) Original Android Development] mitas35:
Can i install a sense7 rom and use as a secontary GPE rom?:confused:

Thanks.
[One (M7) Original Android Development] mitas35:
Hi mate thanks for your great work first of all.:fingers-crossed:

I have s on device with IC ROM and i wand to use GPE ROM for secontary but it requires a boot .img flash how can I do it ? Thanks.
[One (M7) Original Android Development] nkk71:
Please provide a link (to both the thread and file downloaded), but I'll test

thread

file

later,

but as [MENTION=4333421]mitchst2[/MENTION] already confirmed, it shouldnt be a problem.

yes, shouldnt be an issue

what do you mean? seperate boot.img (kernel) flashes are not needed on the M7 (even with S-ON), that was needed for older devices

BTW, I dont typically recommend using multirom on S-ON devices, if something goes way wrong (it shouldnt, but it could), then you may need to RUU to be able to reset your phone completely, and that's somewhat difficult with S-ON, just my opinion
[One (M7) Original Android Development] mitas35:
Thanks mate ,so you thing i should stay away ??:(:(
[One (M7) Original Android Development] nkk71:
not necessarily, just saying be careful what you flash

the same rule applies to normal flashing as well as for multirom flashing, provided what you are flashing is compatible with your device, your firmware, etc

it should be fine (eg read back a page about GPE SkyDragon ROM, and how that updater-script messes things up... didnt need an RUU, but still)

I've personally had to RUU on a few occasions, because my system became too unstable, and only RUU fixed it... then again, I was testing stuff :eek:

there may even be a signed RUU for you in case need be; but it's so much easier to do things (flash firmware, upwards, downwards, ruu, etc) when you're s-off
[One (M7) Original Android Development] mitas35:
Hmmmm i have 7.19.401.30 and i found 7.19.401.22 can i use that?or i have to find .30?

Sorry for noob questions thanks.
[One (M7) Original Android Development] nkk71:
yes, you should be able to... in case you get a version-main error, then it's probably best to write 7.19.401.22 as version-main to the phone's misc partition, then it should work without any issues

this can be accomplished on a rooted ROM, or while booted into TWRP, and then using an "adb shell" followed by certain commands.... i've posted something similar in alray's thread; where you just asked as well ;)
[One (M7) Original Android Development] mitas35:
So i will go for it :D:D

I am out of (thanks) so thanks i ow you a couple :p:p

Last 2 questions (hopefully) the app in play store is the same with this one here ?

If a rom (secondary) need to flash boot.img how to do that? Thanks.
[One (M7) Original Android Development] nkk71:
Yep, same app, the links in here just redirect to the Play Store, the official MultiROM Manager app is by Tasssadar, which has been updated to link to the new versions, which I'm mantaining for the M7
[One (M7) Original Android Development] mitas35:
Thanks mate you have been very helpful :angel::angel:
[One (M7) Original Android Development] nkk71:
would anybody care to comment about why f2fs support is needed?

from the quick look, doesnt seem very M7 friendly to begin with, let alone with MultiROM

any input would be appreciated, before I push a new update.

Thanks
[One (M7) Original Android Development] ljjehl:
Wish I could give you some info. F2FS isnt really that friendly with Marshmallow, for sure...at least not so much on M7.
[One (M7) Original Android Development] nkk71:
thanks for the feedback (any M ports??); and well i'm encountering several issues / dilemmas here

1- i can get f2fs working, but there's no primary kernel (as far as I can tell) with both f2fs and kexec-hb support

or

2- i can get MTP, and USB-OTG working

and 1 + 2, means patching the kernel (I'm no good at that), and some other stuff

3- maybe i should focus those few hours, on an M9 build

... the M7, is a great test device for me, so hence the dilemma
[One (M7) Original Android Development] nkk71:
why, watcha running, what's not working?
[One (M7) Original Android Development] nkk71:
upcoming changelog:

MTP working

USB-OTG working

F2FS working (dunno why, since no kecex-hb kernels around... but anyway, it works)

MTP with adb enabled multirom boot menu, working
[One (M7) Original Android Development] mitchst2:
Exodus - 'Nothing Else Matters'

mitchst2
[One (M7) Original Android Development] ljjehl:
Not yet, that is. I suppose getting a MM rom built right is first and foremost!
[One (M7) Original Android Development] nkk71:
I need a link to the thread, ROM, and exact file-name please :D

the one you sent me worked just fine, but I can't help the system partition checks

1- I could circumvent them

2- ^^ that will break any possibly OTA/upgrade/whatever
[One (M7) Original Android Development] mitchst2:
Why?

mitchst2
[One (M7) Original Android Development] nkk71:
well to answer you question properly, it's "because." (that is the exact answer to that particular question)

but other than that, i dont really need it
[One (M7) Original Android Development] mitchst2:
Glad we cleared that up.

Carry on :rolleyes:

mitchst2
[One (M7) Original Android Development] ljjehl:
You don't need to worry about that portion. Its up to the ROM developer to make sure it works both primary or secondary, or create an option to work either way. Thanks again for that tip.