[MOD] MultiROM v33b

[maxed4901]

Multirom and cos13

@KINGbabasula and anyone who could propose a solution.
I am on multirom 33a and last modified recovery twep 3.0.0-0
Are these latest?

Tried to flash cos 12.1 YOG7DAS and getting error. Couldn't upload image from browser. Will post tomorrow when m on more stable network.

Couldn't flash cos13 which is posted on XDA either. Please help.

 

[nachomagic]

Hi mates

In in a xposed bootloop but for a secondary rom, so in the twrp file manager I don't know where is the /data/data to disable xposed.

Do you anybody know where is it?

Thanks in advance

 

[Kingzak34]

Hi mates

In in a xposed bootloop but for a secondary rom, so in the twrp file manager I don't know where is the /data/data to disable xposed.

Do you anybody know where is it?

Thanks in advance

It's in system/framework delete xposed bridge.jar

Tapatalké depuis mon mega Mate 8

 

[maxed4901]

I am having error 6 flashing a secondary ROM dirty flash update. Anybody can help? Where's @KINGbabasula? Been having issues flashing DU. And i really want this ROM. It doesn't have multirom support so can't keep as primary. Prepared to pay for a fix too.

 

[KINGbabasula]

I have now updated the recovery to TWRP 3.0.2 with included @nkk71 's no kexec workaround which I tested and seems working pretty good, finally it's not always needed to have a kernel with kexec hardboot patch

 

[Hijmen]

Updated multirom and recovery. Was scared at first when I booted in recovery, no multirom entry to be seen at first sight. Looking around I found it in the top right corner under the 'menu' stripes.
Thnx for the updates!

Sent from my A0001 using XDA Free mobile app

 

[nkk71]

I have now updated the recovery to TWRP 3.0.2 with included @nkk71 's no kexec workaround which I tested and seems working pretty good, finally it's not always needed to have a kernel with kexec hardboot patch

Glad to hear it's working for you as well

For those interested a description of the no-kexec workaround (including the advanced options) is here

there's some outdated information (from the previous workaround) which needs to be updated, but it should give you a general idea and explanation of the various options.

 

[crazydude10]

Does anyone know of a workaround for Twrp not remembering the last used folder path? I was hoping it would be fixed in latest twrp update, but it still exists.

 

[clock51]

the new TWRP has also not the Italian language?

 

[kuulbhaskar]

i too confirm that the new multirom along with twrp with no kexec boot workaround is working fine. Have just flashed cm12.1 sultan's latest build as internal with no kernel with kexec hardboot patch and exodus 6.0.1 with lightning kernel as secondary and is working flawlessly with no bootloop !!

 

[musklor]

Hello, I have encrypted my phone, could I install multirom with no kexec boot and put some secondary roms ?

 

[maxed4901]

Glad to hear it's working for you as well

For those interested a description of the no-kexec workaround (including the advanced options) is here

there's some outdated information (from the previous workaround) which needs to be updated, but it should give you a general idea and explanation of the various options.

Thank you for your contribution dear and to @KINGbabasula for coming to the rescue.:good::fingers-crossed:

. The no Kexec is a great thing for sure but if i may- on a scale of 1 to 10- how safe is it to use a rom without Kexec as primary with the workaround? does this also mean we now can use any rom as primary despite it having or not having Kexec? if i do choose "use no Kexec workaround always" that is...

wow!! i never thought this day will come.. now i am sad because i couldnt try some roms bcz of Kexec support!!! LOL..:good:...

CUSTOM ROMS!- Here i come!

 

[anagramgenius]

@KINGbabasula, thanks for the update and stock theme of TWRP.

 

[nkk71]

Thank you for your contribution dear and to @KINGbabasula for coming to the rescue.:good::fingers-crossed:

. The no Kexec is a great thing for sure but if i may- on a scale of 1 to 10- how safe is it to use a rom without Kexec as primary with the workaround? does this also mean we now can use any rom as primary despite it having or not having Kexec? if i do choose "use no Kexec workaround always" that is...

wow!! i never thought this day will come.. now i am sad because i couldnt try some roms bcz of Kexec support!!! LOL..:good:...

CUSTOM ROMS!- Here i come!

I can't really put it on a "scale"... MultiROM in itself is a hack (with or without the no-kexec workaround), so that is already something to be aware of.


As for me, I've been running the no-kexec workaround (version 1) for about 8 months or so, until I eventually released it for the HTC One M9 in December.
version 1, had an issue with a possible "lingering primary_boot.img" (though it would not happen in most cases, it was something that could be done easily, if you wanted to and knew how to)

as of version 2, I believe I've accounted for most/all possibilities regarding that, and i've done considerable tests on HTC One M7, M8 and M9

the workaround does (in the background) flash your boot partition when needed, so yes, that could be considered "unsafe"? .... though, flashing a custom ROM, kernel, (even TWRP backup & restore) does it.... are those "unsafe" as well, and how would you rate those on a scale of 1 to 10

The real question is, do you consider kexec-ing a secondary boot.img safer ... is MultiROM in itself "safe", etc.

I have purposely added it as an optional build option, since I cannot test devices I dont have, nor do I know much about the OPO, Samsung (though also got a confirmation it worked), LG, etc.

hence:

If the device maintainer deems fit to include it, then I'm pretty sure, he has tested it, and finds it suitable for the device.


Long story short: flashing anything can be "unsafe" whether that has to do with MultiROM or not... it's really an individual decision, of how far you want to mod your phone

 

[néonaloj]

Hi,
I need help please... I only today understood what the problem is, trying to update to 33b. But the problem began with 33a update.
In fact, since the 33a update I could no more update my/ flash new secondaries . The error was like that:
"extracting contents of boot.img..."
"failed to load bootimg!"
"erasing incomplete ROM..."

"FAILED" (in red)

But today, with the new multiROM update 33b, I could observe what's happenning: when time has come for the app to follow the update process into twrp, in my case it goes into it, only 2 or 3 sec , and it comes back on the bootmenu (with roms to choose from)!!!

So I tried to "Inject curr. boot sector", and the result is:
"MultiROM is not installed!"

All "seems" to be ok with my twrp, but "Multirom is not installed", and I am not able to install it trough the app.

Can I just get the "multirom-20160417-v33b-UNOFFICIAL-bacon.zip" and flash it in my "not installed" twrp?? Other solution?

Many thanks to who will help!

 

[nkk71]

Small note regarding encrypted devices using the no-kexec workaround

Since I dont use encryption, I haven't tested this to much extent, but I believe that there is a
BOOT PRIMARY ROM
option, which you can choose to boot into Internal without decrypting the device first.

Please be aware that this should not be used, if: the last booted ROM was a secondary using the no-kexec workaround.

The reason is that the backup of the primary_boot.img, is stored in the multirom folder, so for the no-kexec to be able to restore it, it needs access to the /data partition:

Booting into primary, while the previous rom was using the no-kexec-workaround
(in which case the real primary needs to be restored first)

It's not too much of a big deal, because when the no-kexec workaround encounters an error, it reboots to recovery (and since recovery will restore the primary_boot.img), another reboot would be fine.

I do however (until I address this particular issue), encourage you not to use the BOOT PRIMARY ROM option, but instead decrypt the device, and then select the Internal ROM to boot.

 

[laulau42400]

Hello
Thank you for the update, it does exist a theme for this release?

Laurent

 

[catxda]

I have now updated the recovery to TWRP 3.0.2 with included @nkk71 's no kexec workaround which I tested and seems working pretty good, finally it's not always needed to have a kernel with kexec hardboot patch
@KINGbabasula

Nice update Thanks.
Please see following logs maybe will help to improve.
I was scrolling on internet and get hard reboot

http://s.go.ro/rlbnvlwh
http://s.go.ro/rlar7azc
http://s.go.ro/eqfbfy9z

Sent from my A0001 using XDA-Developers mobile app

 

[KINGbabasula]

I have now updated the recovery to TWRP 3.0.2 with included @nkk71 's no kexec workaround which I tested and seems working pretty good, finally it's not always needed to have a kernel with kexec hardboot patch
@KINGbabasula

Nice update Thanks.
Please see following logs maybe will help to improve.
I was scrolling on internet and get hard reboot

http://s.go.ro/rlbnvlwh
http://s.go.ro/rlar7azc
http://s.go.ro/eqfbfy9z

Sent from my A0001 using XDA-Developers mobile app

I can't find any error related to MultiROM, probably it's the ROM's fault

 

[catxda]

I can't find any error related to MultiROM, probably it's the ROM's fault

Thanks for looking in the logs.
Maybe the ROM which I use don't support multirom.


Sent from my A0001 using XDA-Developers mobile app