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

[newbe1droidx]

Ok I had already installed your kernel and didn't see any changes. I then flash adreno custom as you said and phone would not boot or screen just black, was able to get into recovery manually after some time and rebooted to see if that would help, it didn't. Had to manually get to recovery, wiped everything but internal and reflashed from beginning as before. Then flashed adreno custom without using your kernel. Same thing wouldn't boot or screen just black. Am back at clean install awaiting your ideas. Thanks so much.

 

[newbe1droidx]

I decided to install rrn as secondary after flashing multirom to primary. All went well in twrp. Rebooted and secondary was not showing up in boot menu, went to twrp and secondary shows there. Hmmmmm lots of fun eh ? Going to install twrp again and do rr n primary

 

[newbe1droidx]

Wellllll, using latest twrp flashed RR n latest, kernel n gapps. Latest ka installed. Flashed multirom 35. Booted up, set up all well. Then flashed crdroid as secondary, then kernel then pico gapps. Set up then rebooted and flashed custom ROM fix. Then rebooted and flashed cf274s 1.0.8. All working great so far using custom ROM as primary.

 

[fgl27]

Ok I had already installed your kernel and didn't see any changes. I then flash adreno custom as you said and phone would not boot or screen just black, was able to get into recovery manually after some time and rebooted to see if that would help, it didn't. Had to manually get to recovery, wiped everything but internal and reflashed from beginning as before. Then flashed adreno custom without using your kernel. Same thing wouldn't boot or screen just black. Am back at clean install awaiting your ideas. Thanks so much.

there is two options for adreno, I remove the last as is not suited for M, have you try the first adreno option?

I try the cf274s 1.0.8 on xt1225 is runs perfect regarding visual glitches there is none for me running as primary (to make it fully work is need to flash the custom kernel I make because the wifi driver of the ROM is not compatible with xt1225 the kernel I make is), so I have no idea way the xt1254 device has that problem as is not something related to the OS it self seems something more related to firmware something we can really change so I keep trying to find a fix even though I can reproduce it at all with make really hard to find a fix.

 

[newbe1droidx]

Ok will try the first one as I can, thx

 

[newbe1droidx]

Started clean all over again. Tried adreno before flashing kernal. Was able to run 1.0.8. Had to Chang persist.hwc.enable to false for keyboard fix. Still had problem of only last digit on clock when wave hand over phone while sleeping. Also while updating thru store screen distortion was still happening. Then flashed kernel and installed ka app. Booted fine but was very jerky motions. Started ka app and said i had to disable screen overlay for ka went to settings and didn't list ka at all to do that so i couldnt useka app at all. I don't have trouble when I run 1.0.8 as second so I will just run that way as this may just be the way it is unless someone can get a turbo to you. Thanks so much tho...

 

[fgl27]

Started clean all over again. Tried adreno before flashing kernal. Was able to run 1.0.8. Had to Chang persist.hwc.enable to false for keyboard fix. Still had problem of only last digit on clock when wave hand over phone while sleeping. Also while updating thru store screen distortion was still happening. Then flashed kernel and installed ka app. Booted fine but was very jerky motions. Started ka app and said i had to disable screen overlay for ka went to settings and didn't list ka at all to do that so i couldnt useka app at all. I don't have trouble when I run 1.0.8 as second so I will just run that way as this may just be the way it is unless someone can get a turbo to you. Thanks so much tho...

Thank you... I will make some test build specific regarding this, as I have some free time on this week, if any of the test build work OK for me I share on the thread.

:good:

 

[newbe1droidx]

Thank you... I will make some test build specific regarding this, as I have some free time on this week, if any of the test build work OK for me I share on the thread.

:good:

One more thing after I updated to latest RR n on primary with 1.0.8 already as secondary, after booting into updated RR n first I rebooted to get to 1.0.8 and phone started to boot then shut down. I got to recovery and ran restore but still wouldn't boot a few times to 1.0.8. I went ahead and cleaned everything and started over with both ROMs same way. Just an update for you...thx

Found my error forgot to inject cur sector, sorry bout that...

 

[z4ck1n]

@bhb27

Tried mod3 on stock. Old display issue still persists.

Recovery takes some time(2~3mins) to boot n start, is it normal?

 

[fgl27]

@bhb27

Tried mod3 on stock. Old display issue still persists.

Recovery takes some time(2~3mins) to boot n start, is it normal?

For some devices that happens, when you have too many single files and or the storage is full or close to full.

 

[fgl27]

I push a new version but is for Oreo as primary only multirom-20180720-v36-quark.zip
https://www.androidfilehost.com/?w=files&flid=279364

Right now I can't support oreo and older OS as primary with one single multirom.zip so you need to change from v35 for older and to v36 for oreo

there is also a updated twrp multirom_twrp-3.1.1-mod_3-quark-20180720-01.img
https://androidfilehost.com/?w=files&flid=208031

TWRP is for everyone, only kernel improves

 

[fgl27]

I push a new version but is for Oreo as primary only multirom-20180720-v36-quark.zip
https://www.androidfilehost.com/?w=files&flid=279364

Right now I can't support oreo and older OS as primary with one single multirom.zip so you need to change from v35 for older and to v36 for oreo

there is also a updated twrp multirom_twrp-3.1.1-mod_3-quark-20180720-01.img
https://androidfilehost.com/?w=files&flid=208031

TWRP is for everyone, only kernel improves

NO need to use multirom-20180720-v36-quark.zip[ after you update to a ROM released today or after

 

[czechop]

NO need to use multirom-20180720-v36-quark.zip[ after you update to a ROM released today or after

Hi @fgl27. Should this multirom work with your pie?

 

[fgl27]

Hi @fgl27. Should this multirom work with your pie?

ins't OS associated, so it probably works, probably because I personalty didn't try.
So if you do let us know.

as long you have a backup is very safe to use, if it fails just run the uninstaller and if after the OS doesn't bot restore and that is it.

TWRP can install recoveries so is very easy to go back and for on this project.

 

[czechop]

ins't OS associated, so it probably works, probably because I personalty didn't try.
So if you do let us know.

as long you have a backup is very safe to use, if it fails just run the uninstaller and if after the OS doesn't bot restore and that is it.

TWRP can install recoveries so is very easy to go back and for on this project.

Thanks. I've tested it but it does not seem to work(or perhaps I've done something wrong). Multiboot shows up, and when I leave it for 5 seconds it is trying to start internal ROM(RR 7.0.2), but the screen stays black. I've waited for some 5 minutes and nothing shows up(but it does not reboot). ADB was working so I've gathered logs(just in case you would like to look at it). Hopefully uninstaller is working fine

 

[fgl27]

Thanks. I've tested it but it does not seem to work(or perhaps I've done something wrong). Multiboot shows up, and when I leave it for 5 seconds it is trying to start internal ROM(RR 7.0.2), but the screen stays black. I've waited for some 5 minutes and nothing shows up(but it does not reboot). ADB was working so I've gathered logs(just in case you would like to look at it). Hopefully uninstaller is working fine

Yes this is a pie issue on the ROM side a simple permission missing for mulitrom start the video driver properly. I will push a ROM update later and all will work, I post here again after.

 

[fgl27]

Thanks. I've tested it but it does not seem to work(or perhaps I've done something wrong). Multiboot shows up, and when I leave it for 5 seconds it is trying to start internal ROM(RR 7.0.2), but the screen stays black. I've waited for some 5 minutes and nothing shows up(but it does not reboot). ADB was working so I've gathered logs(just in case you would like to look at it). Hopefully uninstaller is working fine

Push it latest RR 7.0.2 is booting fine. :good:

 

[czechop]

Push it latest RR 7.0.2 is booting fine. :good:

Thanks a lot. New RR 7.0.2 is working fine both as primary and secondary ROM

And should the encryption work on the secondary ROM?

 

[fgl27]

Thanks a lot. New RR 7.0.2 is working fine both as primary and secondary ROM

And should the encryption work on the secondary ROM?

I never tested encryption on multirom. I don't keep it encrypted, I only have this device as a main device is hard to test all scenarios.

If you test something related to encryption let me know the result.

remember that TWRP can't backup or decrypt data encrypted on Oreo or Pie: no know workaround, one day TWRP will support it.

 

[czechop]

I never tested encryption on multirom. I don't keep it encrypted, I only have this device as a main device is hard to test all scenarios.

If you test something related to encryption let me know the result.

remember that TWRP can't backup or decrypt data encrypted on Oreo or Pie: no know workaround, one day TWRP will support it.

I was trying to encrypt secondary ROM but it seems it does not work. Some logo with an "android" is displayed for a while, then it UI is restarted but when the system gets back nothing happens. I've noticed also that system freezes after a while(even if I not trying to encrypt device) and phone becomes unresponsive(but the screen stays on). Could not run adb at the time so was not able to capture logs.
I thought that it's because I've made the secondary ROM from the backup of primary one so I've made a clean install of 7.0.2 as secondary.
At first boot it did not pass android logo(waited for some 5 minutes). Second time it reaches this "first time installation" screen, but then it said that System process becames unresponsive so I've to kill it. At third time it again displayed "first time installation" screen and after a while said that "intefrace" is not responding. I've gathered the logs(only logcat, adb shell was not working so could not get dmesg) from the last try

I've also installed your RR 5.8.5 as secondary(I thought that perhaps encryption will work there better) but it also freezes(so could not even get to the point of starting encryption). Unfortunately I haven't got logs from this try.

------------------------------edited----------------------------
Sorry, it looks like it just needed more time. Forth restart I've given it few more minutes and it stabilized and looks like is working just fine. Will try to gather logs from encryption

------------------------------edited----------------------------
I've tested again encryption. In the logs there is something like this:
07-26 10:58:04.367 308 3585 E Cryptfs : Unexpected value for crypto key location
07-26 10:58:04.367 308 3585 E Cryptfs : Cannot open block device