yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Questions and Answers] jntdroid:
Lens is clean, and HDR is on Auto. I never turn it off as it's been reliably good up until now.
[Samsung Galaxy S7 Questions and Answers] jntdroid:
Here are the stats from the original (if something is left off, then it wasn't showing any info):

Dimensions: 4032 x 3024

Hor resolution: 72 dpi

Vert resolution: 72 dpi

Bit depth: 24

Resolution unit: 2

Brightness: -2.13

Light Source: Unknown

Exposure Program: Normal

White Balance: Auto

EXIF version: 0220

F-stop: f/1.7

Exposure time: 1/10 sec.

ISO speed: ISO-400

Exposure bias: 0 step

Focal length: 4 mm

Max aperture: 1.53

Metering mode: Center Weighted Average

Flash Mode: No Flash

35mm focal length: 26
[Samsung Galaxy S7 Questions and Answers] *Detection*:
Test it with HDR disabled, HDR takes 3 images with different exposure settings and merges them iirc

And it is well known to be a little buggy anyway, leaving pink dots on photos

Might not be that, but if you want to narrow down the issue you need to test everything :)
[Samsung Galaxy S7 Questions and Answers] jntdroid:
Agree, but based on the stats on the photo, it's looking like HDR was indeed disabled (or it would've indicated HDR right?)

I've read about the pink dot issue and never seen that on mine - and this doesn't appear to be the pink dot issue. The spots are clearly reflections or flares off of the lights that are closer. They're just so significantly worse than other phone cameras I've used. On the iPhones I referenced, you can see small tiny light dots in other parts of the photo, but they're much more inconspicuous and don't take away from the photo.

I'll keep playing with it this evening and see if I can narrow things down any more. I just wanted to see if others had seen this or had an "issue" like this, or if it was just a difficult spot that the S7 couldn't handle while other top-tier phone cameras could (if so, that would be a first in my experience).
[Zuk Z1 Android Development] BitOBSessiOn:
** Work in progress (Original thread here) **

To be able to run multiple ROMs on your system you need a Modded TWRP version (for flashing ROMs as secondary systems) and MultriROM utility to choose which ROM you want to boot, in this case, the NO-KEXEC version (no patched kernel needed).

Screenshots:

[IMG="TWRP"]http://i.imgur.com/tczD5yV.png?1[/IMG][IMG="TWRP"]http://i.imgur.com/hWcrsyc.png?1[/IMG]

[IMG="MultiROM"]http://i.imgur.com/kN2bTVc.jpg?1[/IMG]

Disclaimer:

Remember: You use this under your own risk!

Notes:

I can't maintain this project... I don't have the device... and no time... so don't expect to be updated frequently, sorry.

If you are a developer and want to maintain, update or upgrade this project, let me know... I will try to give proper support.

Download (Latest TWRP and MultiROM):

Androidfilehost

MultiROM Uninstaller

MultiROM Manager (APK). Updated version here.

Guide (short version....):

Flash TWRP-MROM modded and reboot in recovery mode

Flash MultiROM ZIP

Set No-Kexec option in settings for MultiROM from TWRP

Inject boot sector

Flash your favorite ROM as secondary from MultiROM menu

Reboot

Select ROM to boot from

*Your device must be unencrypted or MultiROM won't work !

Known Bugs:

Still a bug that prevents it from flashing IMG files, like recovery images, from TWRP...

Thanks:

To [MENTION=3418703]Tasssadar[/MENTION] for all awesome MultiROM dev

To [MENTION=2605798]nkk71[/MENTION] for NO_KEXEC work

To TeamWin for TWRP (Specially [MENTION=4545031]Shivver[/MENTION] for his port for ZUK Z1)

To [MENTION=5044876]acuicultor[/MENTION] and all guys who have tested and for their support

To [MENTION=6097419]sahu.prashant[/MENTION] for screenshots

XDA:DevDB Information

MultiROM, Tool/Utility for the Lenovo Zuk Z1

Contributors

BitOBSessiOn, acuicultor

Source Code: https://github.com/BitOBSessiOn/android_device_zuk_ham/tree/mm6.0-twrp-mrom

Version Information

Status: Testing

Current Beta Version: 2017.08.18

Beta Release Date: 2017-08-18

Created 2016-12-01

Last Updated 2017-08-18
[Zuk Z1 Android Development] BitOBSessiOn:
Reserved
[Zuk Z1 Android Development] rockzvishu17:
screenshot pls
[Zuk Z1 Android Development] BitOBSessiOn:
I don't have the device, sorry, so, if somebody can provide any screenshot I will nicely add to OP.

Thx.

PS: Initial thread:

http://xdaforums.com/zuk-z1/general/multirom-unofficial-v33-t3492262
[Zuk Z1 Android Development] sahu.prashant:
I'll surely post the screenshots soon :)
[Zuk Z1 Android Development] BitOBSessiOn:
Thnx !! :)
[Zuk Z1 Android Development] sahu.prashant:
TWRP Screenshots

:)
[Zuk Z1 Android Development] sahu.prashant:
MultiROM Screenshots

:D
[Zuk Z1 Android Development] acuicultor:
Wow, awesome work!!!! Slowly this device is getting what deserves. Thanks BitOBSessiOn for all your efforts for this community,you're great!! Even without the device you're pushing it to a next level with this awesome tool.

Enviado desde mi ZUK Z1 mediante Tapatalk
[Zuk Z1 Android Development] tech mashido:
woah finally...thanks...awesome man
[Zuk Z1 Android Development] S3V3N:
Mega thx :)

Wysłane z mojego ZUK Z1 przy użyciu Tapatalka
[Zuk Z1 Android Development] psyckoze:
This is awesome! Thanks for your dedication. I didn't expect this because you said you left zuk on the table. Than this happened. It escalated very quickly. Watching the development of this project has been really fun. I am so happy about the point where we arrived.
[Zuk Z1 Android Development] rradix:
Hi, is there a possibility that the phone will lose sound when using this? I recently lost sound in all my ROMs including the primary rom after I used and flashed ROMs via multi rom twrp.

Any insights to this? Thanks.

Base ROM: ZUI 2.3.045
[Zuk Z1 Android Development] acuicultor:
Roms share partitions, means the firmware used in primary rom is same for all roms so if you flash a secondary rom not compatible with the current firmware you will face weird bugs, in your case roms not zui based will not work properly unless you flash the correct firmware.

Enviado desde mi ZUK Z1 mediante Tapatalk
[Zuk Z1 Android Development] OrdenKrieger:
That may happen if you use the Stock ZUI rom also with multi rom. ZUI is using another kernel then all the roms on xda. You may remove ZUI and reflash other cm roms. That should work.
[Zuk Z1 Android Development] rradix:
The use case is to get zui as the daily driver rom. Is it possible to do that if I make zui as a secondary rom (but auto boot to it?) Will the sound problem still exist?

Or is it really necessary to stop using zui rom altogether to avoid sound problems with multi rom?

Also, what is the cause of the sound problem? Is it the kernel? Cause based from what I read, multi rom uses a different kernel for each rom. So, it should not matter if my primary is zui since flashing secondaries won't touch the primary kernel. Any insights to this? Thanks!

---------- Post added at 02:28 PM ---------- Previous post was at 02:12 PM ----------

Okay. But why is sound in all ROMs primary and secondaries were bugged? Flashing secondaries should in theory not affect the primary ROM right? So the sound bug will appear on secondaries but not on the primary ROM. Am I getting this correct?
[Zuk Z1 Android Development] acuicultor:
Yes secondary roms don't affect primary in any way and kernels aren't shared between roms so doesn't matter what kernel you have in secondaries, the only kernel which can affect multirom is the one in primary rom if it have the kexec hardboot patch or not, if it have then you can boot secondaries without any work around in twrp, that's the only difference between kernels in mrom afaik.

Enviado desde mi ZUK Z1 mediante Tapatalk
[Zuk Z1 Android Development] rradix:
Okay. Thanks for clarifying.

So secondaries should not mess up my kernel, recoveries and other partitions used by the primary rom. However, after flashing some secondaries, my old ZUK boot splash was replaced by a Linux penguin. I'm not that concerned about it but secondaries might be messing with my primary partitions (not sure).

Update : got sound working now. Un installing multirom is not enough. I refreshed the official twrp for Zuk Z1.

I'm still wondering what went wrong. Also I'm still getting that penguin in boot splash.

Update 2: after a second reboot, sound is gone again.
[Zuk Z1 Android Development] acuicultor:
Without any log is difficult to know what's happening btw i strongly doubt that multirom has nothing to do with any sound issue, for the changed boot image that can only happens if you flash a different one in primary slot. I'm using mrom since it wasn't public released, flashed several secondary roms and didn't face any issue.

Enviado desde mi ZUK Z1 mediante Tapatalk
[Zuk Z1 Android Development] rradix:
Any tips on how to get logs?

I guess I'm on my own then. I'll try to figure this on out. Thanks for the info! ?

Update 3: got the sound working again. Refreshed zui except for the system partition. Let's see if this will stick.
[Zuk Z1 Android Development] nomadman:
Thanks for the contribution!

Was wondering if it's possible to restore a nandroid on the secondary OS with Bliss 6.01 then upgrade to nuclearom 7.1. Was thinking since bliss is cm13 based, that should work right?

/edit/

went the safe route and installed a fresh CM13 ROM and flashed nuclearom 7.1 after. The only hiccup I had was that I could not install the secondary OS until I reboot to the primary OS first then reboot back into recovery. CM13 installed just fine after.
[Zuk Z1 Android Development] QuazIqbal:
Does this support Magisk xposed & phh superuser?
[Zuk Z1 Android Development] BitOBSessiOn:
MultiROM Manager APK available

Available here.

*OP updated with download link.
[Zuk Z1 Android Development] nomadman:
Having this issue with the manager.
[Zuk Z1 Android Development] sahu.prashant:
So do I but the app shows, renames and boots into the installed ROMs correctly. If you install the same app from Playstore, it won't even show the ROMs. :o

Our developer has certainly done some work here. :good:
[Zuk Z1 Android Development] nomadman:
I understand now. I can manually update the multirom. The app is just an easier way to reboot to the other ROMs. Thanks for the heads up.
[Zuk Z1 Android Development] xdddd23:
Other mods aren't supported like always , but yes it work. Tried it myself.
[Zuk Z1 Android Development] Amanpreetsingh:
V33 has the twrp and mrom in it ??

Which version to flash ??
[Zuk Z1 Android Development] xdddd23:
Read op.
[Zuk Z1 Android Development] ratoune:
Anyone succeded to run MIUi with this? Guess won't work because of kernel
[Zuk Z1 Android Development] sahu.prashant:
I tried both MIUI and ZUI but no luck, the ROMs won't boot
[Zuk Z1 Android Development] ratoune:
OK, got it to boot.

As I expected kernel related, but just flash radioactive kernel in mm (after you flash MiUI, in MIUI part) and voila, it boots.

Thanks [MENTION=5044876]acuicultor[/MENTION] for that!
[Zuk Z1 Android Development] sahu.prashant:
Thanks for the tip.. on my way to try it out
[Zuk Z1 Android Development] BitOBSessiOn:
Have you tried forcing no kexec option for MultiROM in TWRP settings with any other kernel?
[Zuk Z1 Android Development] ratoune:
Yeah I first tried that way with no success, also tinkered with different settings. The only way to make it work was with flashing radioactive kennel on top of secondary ROM.
[Zuk Z1 Android Development] sahu.prashant:
Same here, no success. Tried with both ZUI and MIUI and just like a mate stated above, the only way to make those ROMs boot is by flashing Radioactive Reborn Kernel over them. But in my case, that rendered Wi-Fi non functional on both ROMs.

Thanks :)
[Zuk Z1 Android Development] BitOBSessiOn:
It seems that [MENTION=5044876]acuicultor[/MENTION] 's kernel works because KEXEC hardboot patch applied, so MultiROM NO-KEXEC workaround is not working...

Two options... to try to fix MultiROM with no_kexec path or ask to your kernel devs to include kexec hardboot patch.

I'm going to try to build latest TWRP 3.0.3 + MultiROM, but it would be nice if any other kernel dev can merge KEXEC patch, and try....
[Zuk Z1 Android Development] sahu.prashant:
Thanks a lot for your steadfast efforts and for giving us what we could have only prayed for. Actually I even tried MultiROM with Stock COS based on lollipop and that booted just fine. Also, other ROMs based on AOSP and CM appear to be booting just fine even without Radioactive Reborn Kernel.

We just have this issue with MIUI and ZUI as far as I know. And I'm actually happy with we have, never really liked Chinese UI. :D

But thanks a ton for the awesome work!
[Zuk Z1 Android Development] BitOBSessiOn:
TWRP 3.0.3 + MultiROM v33 (20121220)

Available for testing:

TWRP 3.0.3 available here.

Latest MultiROM v33 available here.
[Zuk Z1 Android Development] xdddd23:
All Working fine . Install IMG like recovery still don't appearing (no problem, just informating) thanks for bring us this god tool . A question: Is possible to add f2fs funtion to this recovery? It exists but don't work .
[Zuk Z1 Android Development] BitOBSessiOn:
What error do you get when trying F2FS?
[Zuk Z1 Android Development] xdddd23:
error is when partitions are in f2fs this can't be mounted or unmounted(recovery unable to mount it ) that mean zips can't be installed, so recovery don't support f2fs , but well you're the expert, I don't know the reason .
[Zuk Z1 Android Development] BitOBSessiOn:
Probably we need a kernel with proper F2FS support... Any candidate...?
[Zuk Z1 Android Development] xdddd23:
I know of a person and you too , but not necessary thanks for reply and the work.
[Zuk Z1 Android Development] Amanpreetsingh:
Can anyone tell what's going wrong with this..

Multirom working good but when I flash something in first time that works but the second it's this error..

For example I have flashed a rom but when I go back to install gapps it's showing me this
[Zuk Z1 Android Development] BitOBSessiOn:
Are you installing GApps from selected secondary ROM in the MultiROM list...? If you still get the problem, reboot into recovery and try again to install only GApps in selected ROM...
[Zuk Z1 Android Development] xdddd23:
It happen to me one time but ROM booted also without problem's.
[Zuk Z1 Android Development] sahu.prashant:
Actually this happened to me too, once or twice when I was on previous MultiROM build and as far as I can remember, that happened to me after I tried to flash MIUI. However, the amusing part is that ROM still booted without any errors! Lol

Also I was recently contacted by a member saying he faced exactly the same error and I think he was trying to install CM13 as a secondary ROM.

I didn't find the error to be fatal, hence, ignorable. :)
[Zuk Z1 Android Development] Amanpreetsingh:
Yes whenever I add a rom for another zip I go to rom list then select a rom I want to flash the zip for but second time its giving me error but after rebooting it will work....

So far great work and appreciated dev ?

---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------

Yes rom booted fine that's what we want rest are ignorable but it's annoying sometimes that have to reboot and flash again but it's great work for zuk users
[Zuk Z1 Android Development] coderus:
hi, can this multirom have problem, when secondary roms have microphone problems? calls works with no issues, but all applications recording audio, including google now is not working.
[Zuk Z1 Android Development] :
Hi.

Thanks for the awesome tool.

Had a query, how do i go to twrp 3.1.0 from this. Unable to flash recovery using multirom twrp.

*am I doing something wrong or multirom doesn't flash .img files?

*will flashify or official twrp app work?

*anything else that i may try?

Edit - Solved.

Did this..

1. Uninstalled multirom twrp using multirom Uninstaller

2. Flashed twrp-3.1.0-0-ham.img using twrp

3. Reboot to recovery, flash img again to recovery

4. Reboot to recovery, dirty flash only the rom zip

5. Reboot to system.

Done.

* details regarding step 4.

Until flashing rom zip, reboot to system also sends me to twrp. But, after dirty flashing of rom zip, everything gets OK and rom boots up.
[Zuk Z1 Android Development] blackbirdoo:
aroma support.

aroma support not added brother. it just reboots after opening any aroma installer. :(
[Zuk Z1 Android Development] sahu.prashant:
I don't think we have any TWRP for our device that supports Aroma installer :(
[Zuk Z1 Android Development] Loganw21:
can u explain how exactly can i get it to work????
[Zuk Z1 Android Development] acuicultor:
You have instructions in op, basically you have to flash mrom zip and mrom twrp then add new roms in modded twrp under mrom section, you can Google for mrom there's a lot of documentation about it also there's a lot of YouTube videos.
[Zuk Z1 Android Development] ramu2514:
Few ROMs are not working with multi rom

xdaforums.com/zuk-z1/development/official-zui-v2-5-358st-t3597427

xdaforums.com/zuk-z1/development/rom-miui-v8-heavenke-t3487820
[Zuk Z1 Android Development] sahu.prashant:
Yep, specifically these two and Sailfish OS are not compatible with MultiROM.
[Zuk Z1 Android Development] ramu2514:
Is there any way to make them work by updating boot image. Any specific reason for the booting to fail?
[Zuk Z1 Android Development] Amanpreetsingh:
I am not able to remove mrom via mrom uninstaller zip. It's giving me error.
[Zuk Z1 Android Development] xdddd23:
Hi [MENTION=6411851]BitOBSessiOn[/MENTION] Could you please update MultiROM from this sources to have lastest version or maybe explain me how to setup correctly the directory and build?

Thanks in advance.

TWRP core: https://github.com/nkk71/Team-Win-Recovery-Project

multirom: https://github.com/nkk71/multirom
[Zuk Z1 Android Development] BitOBSessiOn:
Ok, I will try to update and/or show how I build if you are interested in maintaining...
[Zuk Z1 Android Development] xdddd23:
Thanks , when you have time of course, and we can talk in our language privately to do it faster.
[Zuk Z1 Android Development] BitOBSessiOn:
Sure! ;)
[Zuk Z1 Android Development] BitOBSessiOn:
MultiROM v33 (2017.08.18) + TWRP 3.1.1 - UNOFFICIAL

New builds available for downloading:

TWRP_3.1.1-1_multirom_ham_20170818-01.img

multirom-20170818-v33-UNOFFICIAL-ham.zip

Special thx to [MENTION=6552011]xdddd23[/MENTION] for testing.
[Zuk Z1 Android Development] Amanpreetsingh:
Thnks for your time and work ??
[Zuk Z1 Android Development] nomadman:
TWRP_3.1.1-1 & multirom-20170818-v33 worked perfectly! Upgraded from December version
[Zuk Z1 Android Development] hadiyalkishan:
Hello plz help me..

Followed instructions but this error appearing.

My primary rom is cos 12.1 yog4pas7df and want to install lineage 15th August build as secondary.
[Zuk Z1 Android Development] gt_555:
Primary ROM and all next ROM mast have equal kernel.
[Zuk Z1 Android Development] BitOBSessiOn:
Don't use app, you don't need it... My suggestion: Use TWRP to manage your ROMs and MultiROM boot menu to select which one to boot.

With latest version you don't need any special kernel.
[Zuk Z1 Android Development] hadiyalkishan:
Thanks sir.. I'll try.
[Zuk Z1 Android Development] Blackbirdxxx:
Aroma support

Latest twrp's support aroma

But this one dosent :'(
[Zuk Z1 Android Development] :
Anybody tried new version of multirom ?

Please review a bit about it.
[Zuk Z1 Android Development] gt_555:
work fine, without problem
[Zuk Z1 Android Development] danish0175:
How did you flash it

Cus with present multirom twrp IMG flashing doesn't work

---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------

Pls does this mean on the new multirom twrp MIUI can be loaded as secondary rom
[Zuk Z1 Android Development] Sharma_Ji:
I tried worked flawlessly
[Zuk Z1 Android Development] danish0175:
My phone kept booting into twrp after updating
[Zuk Z1 Android Development] Sharma_Ji:
After what, updating?

Installalling multitrom or installing miui ?
[Zuk Z1 Android Development] danish0175:
After updating multirom
[Zuk Z1 Android Development] Sharma_Ji:
Just follow the 5 steps given in op, not so hard, i regularly install and remove multirom, never faced such problem.
[Zuk Z1 Android Development] Akshatpunj:
Can we use materialized theme in recovery?
[Zuk Z1 Android Development] xdddd23:
Depend of the theme that u use..
[Zuk Z1 Android Development] Akshatpunj:
I want to use hdpi-light-play theme. Will it work?
[Zuk Z1 Android Development] xdddd23:
I don't know again look at the version of twrp in theme if u don't know how to check it don't do it.
[Zuk Z1 Android Development] Akshatpunj:
I know how to check it. Both the version of twrp & theme match. I just want to know if it will cause any effect on the modded multi boot twrp or not.
[Zuk Z1 Android Development] xdddd23:
And my question is if we support theme ? And why you don't try OMG. We must know it? Let's go to test and ask less this useless things. The most sure is not compatible
[Zuk Z1 Android Development] Akshatpunj:
I am asking because if someone has already tried then let me know. The obvious reason i am not trying is because i don't want to end up in a dead bricked phone. If you think it's useless then don't answer i am not specifically asking you.
[Zuk Z1 Android Development] Akhil916:
I'm unable to use multirom although the version it shows is MultiROM and I can't flash img files anymore. I even tried flashing uninstaller. I'm just stuck here. Is flashing stock and starting a fresh the only way now?
[Zuk Z1 Android Development] Sharma_Ji:
It's mentioned in the op that you can't flash img files.

You have to flash normal twrp using twrp app in your primary rom and go ahead then.
[Zuk Z1 Android Development] ansuman2017:
Is zui 2. 5 is bootable in the latest version ? :(
[Zuk Z1 Android Development] ziveca:
Hi, I am a new user of MultiROM. I successfully installed multirom but I have problems with the Multirom app.

I can not boot from it because it says that I have no patched kernel (kexec hardboot patch)

My internal ROM is official lineageOs, the secondary is unofficial Oreo.

Which kernel should I use? How can I patch the kernel?

Than you
[Zuk Z1 Android Development] BitOBSessiOn:
You don't need a patched kernel.. be sure to set no-kexec workaround option in twrp mrom section.
[Zuk Z1 Android Development] ziveca:
Hi

Thank you for so fast reply. The no kexec workaround is set but I can't boot from multirom app.

Please see the attached screenshot

Thank you
[Zuk Z1 Android Development] BitOBSessiOn:
Which apk are you using...? (keep in mind that the one from google store DOES NOT work, try this one )

Anyway, you should be able to select which ROM to boot from MultiROM boot menu, right ? I never use apk... almost useless for me.
[Zuk Z1 Android Development] ziveca:
I am using the app for ZUK Z1, version 1.188-debug (not from play store).... but you are right selecting the rom from the boot menu works.

Thank you
[Zuk Z1 Android Development] ziveca:
Hi,

Another question before I will do something stupid.

After updating the Internal ROM (official LineageOS) the boot menu (where is the option to choose which ROM to boot) has gone. In the ROMs list I can see secondary ROMs

Can I simply "Inject boot sector" in the MultiROM Main Menu?

What is the correct procedure to update the Internal (and secondary) ROM without loosing the boot menu?

Thank you
[Zuk Z1 Android Development] BitOBSessiOn:
You must set Multirom flag enabled while flashing... If not, re inject boot sector (at worst reflash Multirom zip... No prob).
[Zuk Z1 Android Development] ziveca:
Sorry my ignorance but where I have to set Multirom flag ... I can not find it :eek:
[Zuk Z1 Android Development] swaim7:
Can't boot secondary ROM. It appears boot animation then go back to recovery how can I fix it ... My primary ROM is RR 5.8.5

AND SECONDARY IS VALIDUS OREO
[Zuk Z1 Android Development] wahedkhan:
Do we have twrp update... I see 3.2.1 is available but not sure how multi-rom differ on it
[Zuk Z1 Android Development] xdaakhil:
oreo is not currently compatible with multi rom
[Zuk Z1 Android Development] Umeed Salman:
Whenever i update magisk either in primary rom or in secondary rom i get into a bootloop and this forces me to remove multirom. Plz help