yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] johnbravado:
[MENTION=5747496]bhb27[/MENTION] I installed the installation instruction but i think i may have now 2 Nougats. I made a backup of my current system. Installed the multiROM.zip file and then went to add ROM and installed my backup on internal memory. When i rebooted it did the 5 second countdown and i saw boot options internal and my backup. i though nothing of it until it finished booting and it was a barebone Nougat install.

On initial install is the multirom.zip going to be our base zip so i need to do a clean install and TiBU all my apps on to that, and then if i wish, install a second ROM. or can i install my backup on that base internal ROM which is currently a blank Nougat RR? Or did i choose wrong option when installing my backup?
[Moto Maxx Original Android Development] fgl27:
the multirom.zp doesn't change yours current ROM you did something that cause that, it is just the boot manager support.

on main twrp menu you manage yours primary ROM, on MultiROM menu the extra secondary, you can restore yours backup via normal twrp menu and all must be fine, inject the multiRom boot after restore before reboot.
[Moto Maxx Original Android Development] fgl27:
I push the manager app to download folder, it allow in android changes, direct boot, etc...

View attachment 4245736

when open the app it will point out that the TWRP is out of date, I push a new twrp that is the same as the previously but this "new" one has a version tag that can be see in twrp and by the app that version tag will help with future updates via app.

:good:
[Moto Maxx Original Android Development] johnbravado:
This is nice. Kinda like having safestrap again from the Moto Droid Maxx I had before the turbo.
[Moto Maxx Original Android Development] RSDamasceno:
:good:

Seven android nougat!!

:svetius:
[Moto Maxx Original Android Development] gangrenius:
Links to all those?

Bumpn gums from my vzw DROID Turbo xt1254

---------- Post added at 04:14 AM ---------- Previous post was at 04:13 AM ----------

Which is best? RR I'm sure haha

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Original Android Development] z4ck1n:
[MENTION=5747496]bhb27[/MENTION] this is fantastic !! Thanks !!

Never tried custom ROM as using quark as daily driver. This will allow me to try and test Roms.

Which partitions to backup before trying this ?
[Moto Maxx Original Android Development] ChazzMatt:
I'm sure you are joking? You know they are all the

Development section

of this forum. Well, except for AOKP, which is over in the

Development section of the split "Droid Turbo" forum.

But if you really are serious, then it's always a good idea to keep an eye on this thread:

[ROMs][Quarks][List for Moto Maxx and Droid Turbo]

That link is to the most recent post.
[Moto Maxx Original Android Development] gangrenius:
Rarely I speak before thinking and this was an occasion

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Original Android Development] fgl27:
system and boot, for ROM only.

system, boot and data if you wanna keep apps and they data...

if you test stock ROM as primary let me know the result.
[Moto Maxx Original Android Development] ghpranav:
Fantastic work

It's really great to see that devs are still working on quark. I'm also very excited to see Multi ROM for our device. It would be even more great if someone ports any Linux based OS to our device...
[Moto Maxx Original Android Development] fgl27:
there is no need to flash Quark_Multi_ROM_FIX_CustomROM_V_1_0.zip to a secondary ROM if you have update your secondary to the latest version of the ROM or the kernel that I released...
[Moto Maxx Original Android Development] Bruno Wagner:
It worked very well on my Maxx :good:

Thank you!
[Moto Maxx Original Android Development] RSDamasceno:
Is it possible to include the queue function for the secondary ROMs?
[Moto Maxx Original Android Development] z4ck1n:
I don't want to mess with primary rom (current stock mm). Want to install this over it, without losing data.

My Data is to big to be backup :confused: ...

Few Questions :confused:

How does multirom work? Does it change boot sector record like normal desktop oses?

In multirom installation which partitions are impacted?

Where is secondary rom installed?
[Moto Maxx Original Android Development] fgl27:
You are confusing data with internal memory they are two separated thing, data app and they data usually around 2gb of size of course as much app and data you have bigger it will be, internal memory were yours pics downloads wherever is in the fake sdcard folder that is not afectd.

the description is on the first page, you flash it will not change a thing, I personally already test on stock MM works just fine, primary is the main system you already have no changes, secondary is a ROM that will run from the fake sdcard folder in the multirom folder, were all the multirom files are installed...

you can search about it on the web, tasssadar has made a wiki

https://github.com/Tasssadar/multirom/wiki

I do not released something that will kill your devices if you don't have experience and are afraid of ruining something make the backups save they out side of the device and try in doubt or problem ask specific a question to solve yours problem.
[Moto Maxx Original Android Development] fgl27:
Just push a new file to the download foder

multirom_uninstaller.zip flashable zip to remove multiROM boot manager interface and cleanup any secondary ROM
[Moto Maxx Original Android Development] mrkhigh:
Nice, thanks! I've been wanting the ability to run a stock rom for a while now, bit not willing to drop RR.
[Moto Maxx Original Android Development] gangrenius:
If I wanted to us ComputerFreeks stock Verizon debloated rooted rom 1.0.8 as a secondary rom to RR remix do I need to flash anything special besides the Rom? I know stock can be tricky.

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Original Android Development] digolg:
I tested here as primary marshmallow stock having bug, I made the swipe roms and as a secondary is ok
[Moto Maxx Original Android Development] fgl27:
I don't get what you are trying to report "having bugs" makes no sense I look for detailed description of a problem. above post I already informe on the thread stock ROM is just fine primary and secondary.
[Moto Maxx Original Android Development] digolg:
Here I tested with stock being primary but presented constant graphical errors, I made the swipe rom making it secondary and the problem disappeared, now expecting a different rom custom with the same base to test together with my stock holder :highfive:
[Moto Maxx Original Android Development] z4ck1n:
[MENTION=5747496]bhb27[/MENTION]

On Stock MM.

Tried to install via app. It failed to flash recovery. Saw error in bootloader log related recovery image size.

Flashed multirom twrp via flashify. Success, Multirom is now showing recovery present.

Should I install multirom thru app or twrp?
[Moto Maxx Original Android Development] fgl27:
I did not try the app for flashing yet, the recommendation are from the developer of the app, I only tested via twrp it can install another twrp and flash the zip just fine, theoretically if the app also doesn't work for that it can cause a problem and then you can use twrp...

I take a look on the app flashing of twrp when I have the time.

:good:
[Moto Maxx Original Android Development] fgl27:
I just test this with success, TWRP and Multirom downloaded and installed from the app.

the problem was on the external download link that is fixed now, no need to update anything on the app just open it select one or both and click install, if doing only one do the TWRP first...

:good:
[Moto Maxx Original Android Development] z4ck1n:
[MENTION=5747496]bhb27[/MENTION]

Fail to flash via app. Screenshots from app and after reboot in twrp log.
[Moto Maxx Original Android Development] fgl27:
the file is ok I tested, but you probably had a download problem, try again but before delete the file from the Download folder in internal memory or use the AFH link from OP.
[Moto Maxx Original Android Development] z4ck1n:
Followed your instruction with success :)

Edit: [MENTION=5747496]bhb27[/MENTION]

On stock MM as primary, waving hand over phone is now just showing last single digit from time eg. "2" and not showing full time like earlier 9:42

On few screens thr is garbled display type of effect.
[Moto Maxx Original Android Development] digolg:
Stock is not good as primary, screen with lag redemption problem in graphics screen overlay problem, this was the problem encountered, and reported for a support only because it asked for feedback if read the second post it does is able to interpret about which bug I mentioned .
[Moto Maxx Original Android Development] fgl27:
I can't simulated this problem, theoretically the multirom will only effects the boot process and if works well on secondary the same must happens on primary, theoretically theoretically...

when I tested here I did not notice any problem, but I test a full stock ROM for xt1225, no changes made regarding flashing zips etc...

the question here is what have you guys change, magisk? xposed? modules? kernel? any zip and etc related that can change system, explain in a way that can help me to reproduce it here, because with what you guys post I can't reproduce here...
[Moto Maxx Original Android Development] digolg:
Here the stock is standard with root the old way not by the magisk, last patch of update and without mods, without xposed without substratum. the lock screen timer also shows only the minutes, today I am again putting a second rom (viper) and soon now when restarting the problem persisted again, I made the swap rom sending the stock to secondary and it is now ok.
[Moto Maxx Original Android Development] fgl27:
This is really odd, because secondary or primary, under multirom environment it must be all the same..

I try here exactly what you wrote, change primary to stock M, update everything to latest latest, update all apps, install "BETA-SuperSU-v2.62-3-20151211162651_3", then update to latest "SR3-SuperSU-v2.82-SR3-20170813133244", try for some time, flash my kernel, try for some time, all the time I let the Moto display on, in lock screen or Moto display no glitches, any were no glitches.

I know only test for a few hours, but I did not find a problem... on a next try if you or any one with a problem has the time try this:

running the problematic stock ROM, make a backup of primary and all secondary, them flash the "multirom_uninstaller.zip", if no backups are made flashing it will erase any secondary ROM, then after that re-install the stock boot.img you can find it on the stock xml.zip or the zip you use to for the stock ROM...

Don't inject any multirom support via twrp, and reboot, it must boot OK, and now no multirom will be there to cause problem, if the bugs desapear was a multirom problem, that I need to find a way to reproduce to see if I can fixe...

:good:
[Moto Maxx Original Android Development] tseh:
hi BHB27, do you have planes to release kexec support?

without kexec I cannot install mrom builds.

I tried to install Sailfish OS build using cm snapshot zip + sfe.zip, but it cannot start due to init files.
[Moto Maxx Original Android Development] fgl27:
Is really hard to make the kexec to work, I don't now how to, so probably not.

Are you shore it doesn't work, you have tested but have you search about(others none androidOS and multirom without kexec)?
[Moto Maxx Original Android Development] tseh:
I have not yet looked for other non-androidOS (no linux-based ROMs for quark) to can be installed with multirom without kexec, I'll look, if I find it, I'll post, maybe someone else will be interested in this question. In any way, thanks for your work
[Moto Maxx Original Android Development] z4ck1n:
[MENTION=5747496]bhb27[/MENTION]

On stock MM with stock kernel, BETA-SuperSU-v2.62-3-20151211162651 and Xposed.

Flashed "multirom_uninstaller.zip" and with inject option UNCHECKED. Success, tested for sometime now lock screen issues seem to be gone.

Guessing, multirom installer is doing something wrong in stock MM.

On this stock mm version, should i flash your kernel and try multirom again?
[Moto Maxx Original Android Development] fgl27:
My question is, is that ROM that is OK now was't before the same ROM + data and boot, I mean the problem was there then you flash the multirom_uninstaller and was gone?

if is a different ROM start from a zip or a backup that never see multirom make no sense. like I wrote before I have tested no problem with stock, if I can reproduce the problem I can fixe it. them must be something that you did , change that I simple did not try...

it theoretically the kernel doesn't affects but you can try and tell the result.
[Moto Maxx Original Android Development] z4ck1n:
It's same rom. No change in rom. Didn't even reflash boot or system.

I only flashed multirom uninstaller. Issue disappeared.
[Moto Maxx Original Android Development] tseh:
I took this thread https://xdaforums.com/redmi-2/how-to/guide-how-to-boot-sailfish-os-secondary-t3434696/page1 as example, did changes quark related and it is works, thanks bhb27 for multirom
[Moto Maxx Original Android Development] fgl27:
try the custom kernel when you have the time with multirom and stock as primary...

I will take a look at fixing this, at least make some test multirom later in the weekend...

Nice, a little complicated process there... did you use cm12 or something new?
[Moto Maxx Original Android Development] z4ck1n:
Update : [MENTION=5747496]bhb27[/MENTION]

On same stock MM rom, I have flashed BHB27-Kernel-V63.zip and Kernel adiutor app. I was bit scared as it took some on boot static logo, after 3~5 mins animation started. Success, everything seems to be working. Speed in drawer is improved.

Then on the same rom with custom kernel, flashed multirom_installer thru multirom manager app.

Post reboot, same problem again started.

then again, flashed multirom_installer and problem is gone.
[Moto Maxx Original Android Development] tseh:
yes, used cm12 snapshot + Sailfish 2.1.0.10 build, many things partially works or not works at all, but now I can continue porting
[Moto Maxx Original Android Development] z4ck1n:
Let me know, if I can help on this by providing some log or something...
[Moto Maxx Original Android Development] newbe1droidx:
[MENTION=5747496]bhb27[/MENTION] am trying this on droid turbo Verizon, using cf274's 1.0.8 as primary and latest rr-n as secondary. Secondary works fine but primary is having screen issues it didn't have before on lock screen and main screen and same when typing. Seems to happen if widget is updating and trying to do motion similar when typing. Installation of multirom went perfectly using apk. See attached, thanks
[Moto Maxx Original Android Development] fgl27:
I'm aware of you can see the previously post about it, not a problem on xt1225 stock works well as primary and secondary, I did not had time to fix it, noting attached to yours post.
[Moto Maxx Original Android Development] newbe1droidx:
I uploaded 2 picks of what its doing for you to see. Dont know where they went, sorry. Will try rr as primary and 1.0.8 as secondary and see how that works in mean time. Thanks for the help
[Moto Maxx Original Android Development] z4ck1n:
[MENTION=5747496]bhb27[/MENTION]

Wanted to test it with clean boot...

Do you have clean or stock boot & system (build mpg24.107-70.2)?

Edit ..

Found it XT1225_QUARK_RETEU_6.0.1_MPG24.107-70.2_cid7_subsidy-DEFAULT_CFC.xml.zip .

https://xdaforums.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470

https://firmware.center/firmware/Motorola/Moto MAXX/Stock/XT1225/

http://www.filefactory.com/folder/f9d1880e6c5b4800/?sort=created&order=ASC&show=50

Now Exploring how to flash it...
[Moto Maxx Original Android Development] newbe1droidx:
[MENTION=5747496]bhb27[/MENTION] put RR as primary, CF 1.0.8 secondary screen problem gone on my xt1254 turbo. Just an update!
[Moto Maxx Original Android Development] newbe1droidx:
Well something happened, turned phone off for some time, when tried to boot into cf274's 1.0.8 as secondary is it stayed in bootloop. Rebooted and tried viper as 3rd is and had same problem. Installed fix for viper and still bootloop. I cleaned cache, dalvic and data on both, deleted both and have just finished resetting up as latest RR primary, viper 2nd and 1.0.8 3rd. Will try this out.. Thanks for your hard work.
[Moto Maxx Original Android Development] fgl27:
maybe you change the main boot and did not re inject the boot, have you change ROM or boot.img for primary?

2# post may help
[Moto Maxx Original Android Development] newbe1droidx:
That may have been it when I installed kernel, thanks
[Moto Maxx Original Android Development] fgl27:
enable the below on twrp will make it persistent and will prevent that from happen it time you update ROM/Kernel of primary

View attachment 4281324

The problem may be something else but to see that is need to logcat and dmesg during the bootloop to catch the problem...
[Moto Maxx Original Android Development] newbe1droidx:
I believe it is enabled by default but will double check thanks.
[Moto Maxx Original Android Development] newbe1droidx:
Ok it is checked and i saw it inject on install, i deleted viper and then ran restorcon and it has worked flawlessly since. Rr-n and 1.0.8 great.
[Moto Maxx Original Android Development] newbe1droidx:
One question, is there a way to have a pin number before booting into secondary roms? So you would have a pin for booting, then pin for rom you choose? Kind of a double security feature...
[Moto Maxx Original Android Development] newbe1droidx:
[MENTION=5747496]bhb27[/MENTION] 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
[Moto Maxx Original Android Development] fgl27:
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...
[Moto Maxx Original Android Development] newbe1droidx:
Ok thanks for your hard work
[Moto Maxx Original Android Development] 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:
[Moto Maxx Original Android Development] newbe1droidx:
Just updated thru manager app, worked perfectly.

Any problems let you know. Thanks so much!
[Moto Maxx Original Android Development] weaver11b:
which boot.img do you install when you inject boot.img?
[Moto Maxx Original Android Development] newbe1droidx:
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.
[Moto Maxx Original Android Development] weaver11b:
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....
[Moto Maxx Original Android Development] 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:
[Moto Maxx Original Android Development] newbe1droidx:
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
[Moto Maxx Original Android Development] 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:
[Moto Maxx Original Android Development] 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
[Moto Maxx Original Android Development] newbe1droidx:
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?
[Moto Maxx Original Android Development] fgl27:
for some days it will not have the update files... just that...
[Moto Maxx Original Android Development] newbe1droidx:
Are the updates to deal with visual problems running cf274 1.0.8 as primary? Updated just fine, willing to try if need to.
[Moto Maxx Original Android Development] 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
[Moto Maxx Original Android Development] fgl27:
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: