[TOOLS][All quark] MultiROM_TWRP [TWRP 3.1.1_Mod_3][MR 35][20171111]

[newbe1droidx]

@bhb27 for some reason I have to run restorecon the last couple days to be able to boot into second ROM, using R R N as internal then cf274 1.0.8 as second.

Droid turbo on verizon

 

[fgl27]

@bhb27 for some reason I have to run restorecon the last couple days to be able to boot into second ROM, using R R N as internal then cf274 1.0.8 as second.

Droid turbo on verizon

That workaround is expected to be used some times, primary ROM may affect secondary permission, and that will solve, that can happen randomly or some times after primary update or clean install...

 

[newbe1droidx]

That workaround is expected to be used some times, primary ROM may affect secondary permission, and that will solve, that can happen randomly or some times after primary update or clean install...

Ok thanks for your hard work

 

[fgl27]

MultiROM Update...

* multirom_twrp-3.1.1-mod_3-quark-20171009-01.img
* multirom-20171009-v34-quark.zip

Changelog:
* Add latest bugs fix and improves for MultiROM TWRP and MultiROM.zip
* Included untested encrypton support, I have no time to test this now but eventually I will and update the tread, if any one try encryption and MutlROM let me know the result/device/rom
* Included a update Screen/Display support to prevent glitches on XT1254 stock ROM, untested as I only have a xt1225, the screen glitches only occur on stock VZW ROM on xt1254 running as primary so if anyone test let me know the result.

Download folder click here
MultiROM_Manager file updated

Advised, after the update run a restorecon on secondary ROM's like this:
Update TWRP, reboot to twrp, Update/flash MultiROM.zip reboot to TWRP again
Click on the top right MultiROM menu on twrp
List ROM > select the ROM > Run Restorecon

Repete the process "List ROM > select the ROM > Run Restorecon" for all secondary ROM's

:good:

 

[newbe1droidx]

Just updated thru manager app, worked perfectly.
Any problems let you know. Thanks so much!

 

[weaver11b]

That may have been it when I installed kernel, thanks

which boot.img do you install when you inject boot.img?

 

[newbe1droidx]

which boot.img do you install when you inject boot.img?

It will be the boot.img of the rom you want, i believe you do that in place of flashing rom zip. Dont think there is an img rom available for quark tho.

 

[weaver11b]

It will be the boot.img of the rom you want, i believe you do that in place of flashing rom zip. Dont think there is an img rom available for quark tho.

I just extracted the boot.img using ES File Explorer and then used that to flash with the inject boot.img. Booted up just fine. Love having multirom available; as someone else mentioned earlier in the post this reminds me of the good ole days of Safestrap on the Droid Razr. Ahhh those were some good crack flashing days over at droidrzr.com. Shame i just pre-ordered a google pixel 2 xl last week and will be giving up multirom support for a while maybe for good....

 

[fgl27]

Is anyone running latest MutiROM 34 and MutiROM_TWRP 3.1.1_Mod_3 on stock VZW xt1254 ROM as primary?
I wanna know about the visual glitches that happen on the first version I made...

:good:

 

[newbe1droidx]

Is anyone running latest MutiROM 34 and MutiROM_TWRP 3.1.1_Mod_3 on stock VZW xt1254 ROM as primary?
I wanna know about the visual glitches that happen on the first version I made...

:good:

I was but glitches still there for me, had to go back to stock as secondary. Every time I typed 3 or more keys popped up with key I was pressing. Had to use phone right away so had to switch back. Sorry

 

[fgl27]

Read it all before update
MultiROM Update:
* MultiROMMgr_APP_Quark_02.apk
* multirom_twrp-3.1.1-mod_3-quark-20171111-01.img
* multirom-20171111-v35-quark.zip

Before update do the fallowing:

For this version is needed to update all files, the app, the TWRP and the multirom.zip
Backup all yours secondary ROM first, because after this update they will not work, after the update delete all secondary ROM even they are there they will not work or if they work they will not fully work, then restore one by one...

Changelog:
* Fix primary boot problem after rebooting from a secondary (only affects those running a updated version of the kernel or Nougat ROM I make)
* Latest TWRP/MutiROM updates to improve the experience and compatibility

Download folder click here
MultiROM_Manager file not updated because I wanna those that update to read this post

:good:

 

[fgl27]

I notice a small bug that can happens I update second post to included a help about "Switching ROMs (primary to secondary and vice versa):" and included the below warning

Very importante always go back to primary ROM from a secondary before going to another secondary this is to prevent the boot.img of primary be override with the secondary and cause boot problems, in case that happens is always possible to restore a boot.img of primary using TWRP backup or flashing a boot.img that can be found on the ROM.zip of your current ROM

 

[newbe1droidx]

I notice a small bug that can happens I update second post to included a help about "Switching ROMs (primary to secondary and vice versa):" and included the below warning

Very importante always go back to primary ROM from a secondary before going to another secondary this is to prevent the boot.img of primary be override with the secondary and cause boot problems, in case that happens is always possible to restore a boot.img of primary using TWRP backup or flashing a boot.img that can be found on the ROM.zip of your current ROM

That explains the problem I've been having lately, thx

---------- Post added at 10:24 PM ---------- Previous post was at 09:31 PM ----------

@bhb27 so don't use app to update update manually?

 

[fgl27]

That explains the problem I've been having lately, thx

---------- Post added at 10:24 PM ---------- Previous post was at 09:31 PM ----------

@bhb27 so don't use app to update update manually?

for some days it will not have the update files... just that...

 

[newbe1droidx]

for some days it will not have the update files... just that...

Are the updates to deal with visual problems running cf274 1.0.8 as primary? Updated just fine, willing to try if need to.

 

[newbe1droidx]

Just tried it screen problems still there and for some reason couldn't get the WiFi to be seen. Clean installed RR and working fine. Will trycf274 ROM as secondary soon

 

[fgl27]

Are the updates to deal with visual problems running cf274 1.0.8 as primary? Updated just fine, willing to try if need to.

Just tried it screen problems still there and for some reason couldn't get the WiFi to be seen. Clean installed RR and working fine. Will trycf274 ROM as secondary soon

The last was only addressing problem related to file system...

For visual glitches I have 3 options that I can't test as xt1225 rom is fine...

1#
change the prop persist.hwc.mdpcomp.enable to false
Kernel adiutor can do that...

2# try adreno driver from stock xt1225
https://androidfilehost.com/?fid=889964283620765693

3# try adreno driver from used on custom ROM
link removed file not suited for Marshmallow


the test are simple change one test if no good restore a backup of system...

the wifi driver is on system, if you change the boot.img the the kernel on the boot.img change if the driver on system is't compatible with the kernel that can happens, the custom kernel I share is not compatible with any stock boot.img, maybe is that the problem, flashing the kernel over that ROM may solve the problem as it will make kernel and driver compatible because I share it all on the kernel.zip...

Any one that can test those let me know the result... :good:

 

[newbe1droidx]

The last was only addressing problem related to file system...

For visual glitches I have 3 options that I can't test as xt1225 rom is fine...

1#
change the prop persist.hwc.mdpcomp.enable to false
Kernel adiutor can do that...

2# try adreno driver from stock xt1225
https://androidfilehost.com/?fid=889964283620765693

3# try adreno driver from used on custom ROM
https://androidfilehost.com/?fid=962021903579492069

the test are simple change one test if no good restore a backup of system...

the wifi driver is on system, if you change the boot.img the the kernel on the boot.img change if the driver on system is't compatible with the kernel that can happens, the custom kernel I share is not compatible with any stock boot.img, maybe is that the problem, flashing the kernel over that ROM may solve the problem as it will make kernel and driver compatible because I share it all on the kernel.zip...

Any one that can test those let me know the result... :good:

I decided to start over, using multi ROM twrp, I installed bootloader and radio from cf274's 1.0.8 thread. Then installed 1.0.8. during setup keyboard was doing the multiple pop up for the first four keys from left side all rows, other keys worked fine. Got set up and updated play services the 14 apps updated. During that time the screen was distorting on the updating app showing the updating process. After that finished I installed magisk root and manager. Then edited buidprop - persist.hwc.mdpcomp.enable to false. So far keyboard working correctly. I haven't flashed kernel or installed ka yet. I am typing this in labs app and no problems typing. There is still a problem when I wave over phone to see time after screen off I only get the last time digit all others to left black. Should I installed latest kernel and ka or proceed to step number 2.

 

[newbe1droidx]

I decided to start over, using multi ROM twrp, I installed bootloader and radio from cf274's 1.0.8 thread. Then installed 1.0.8. during setup keyboard was doing the multiple pop up for the first four keys from left side all rows, other keys worked fine. Got set up and updated play services the 14 apps updated. During that time the screen was distorting on the updating app showing the updating process. After that finished I installed magisk root and manager. Then edited buidprop - persist.hwc.mdpcomp.enable to false. So far keyboard working correctly. I haven't flashed kernel or installed ka yet. I am typing this in labs app and no problems typing. There is still a problem when I wave over phone to see time after screen off I only get the last time digit all others to left black. Should I installed latest kernel and ka or proceed to step number 2.

I decided to try your kernel first, didn't notice any change on wave for time. Keyboard working fine.

 

[fgl27]

I decided to start over, using multi ROM twrp, I installed bootloader and radio from cf274's 1.0.8 thread. Then installed 1.0.8. during setup keyboard was doing the multiple pop up for the first four keys from left side all rows, other keys worked fine. Got set up and updated play services the 14 apps updated. During that time the screen was distorting on the updating app showing the updating process. After that finished I installed magisk root and manager. Then edited buidprop - persist.hwc.mdpcomp.enable to false. So far keyboard working correctly. I haven't flashed kernel or installed ka yet. I am typing this in labs app and no problems typing. There is still a problem when I wave over phone to see time after screen off I only get the last time digit all others to left black. Should I installed latest kernel and ka or proceed to step number 2.

Odd result I expect to be only one thing causing all the glitches problems...

Please try the zip I share before there is no need to use the kernel in theory, but if all fail on the last test try the kernel on the top of "3# try adreno driver from used on custom ROM"

:good: