yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Djok:
[MENTION=5093942]KINGbabasula[/MENTION]

Wonderful :D. Any ETA?

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] KINGbabasula:
I hope not more than a few days
[ONE Android Development] musklor:
You have a life, your life so we can't blame you [emoji6]
[ONE Android Development] paarkhi:
Glad that you are back and not abandoned us
[ONE Android Development] maxed4901:
Wow

Welcome back [MENTION=5093942]KINGbabasula[/MENTION]

Much deserved!! As father of the Multirom- I got few complains...!!!:(

Felt realy sad thinking that this was it for Multirom.:highfive::highfive:

Lot of rom devs make the roms with the google assertive script which does not let us boot the rom. Dont know why its done.. the only reason i could think of is a fool flashing an OPO rom on a Iphone.

We would like to request (Humbly) to have an option to stop the scripts o read them possibly. + MM roms as secondary.. Its not stable yet so dont want to put it on primary just yet.
[ONE Android Development] KINGbabasula:
That assert gets bypassed automatically in new MultiROM recovery :)
[ONE Android Development] merothh:
Thanks a lot..
[ONE Android Development] maxed4901:
Wow.. That is so good..cant say how glad i am to hear that. Thank you KING for the great news. Looking forward to the update/s. I was almost giving up on multirom till today. For me, multirom is the reason I am still on oneplus. Glad glad glad for your support and contribution

---------- Post added at 06:19 PM ---------- Previous post was at 06:16 PM ----------

After many moons, i am looking forward to an update!!!
[ONE Android Development] x.0ni.x:
Welcome back good sir!! Man I can't wait to have my multiROM bk!! Thanks a lot for not forgetting about us.
[ONE Android Development] fldc:
Hopefully some love for OxygenOS also, I use it as my primary ROM because of heavy mifare usage mostly, which is not supported on anything else. ;)
[ONE Android Development] merothh:
There was this problem with the 3.0.0 TWRP where formatting cache or dalvik (not sure) took a lot of time/wouldn't complete..You might wanna look into that too bro before releasing !! [MENTION=5093942]KINGbabasula[/MENTION]
[ONE Android Development] maxed4901:
*peep *look around *still happy -Sign out
[ONE Android Development] mattnate:
wowwwww many many thanks.....
[ONE Android Development] Djok:
Has sultan's kernel got a kexec patch?

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] Natakranta:
The Return of the King (2016)

I like this trailer [emoji16]

So good to see you back!

Take your time, remember, it's supposed to be fun for you, not duty.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] KINGbabasula:
The updated MultiROM and recovery are now available on the app :)
[ONE Android Development] Shadowghoster:
I can flash secondaries as intended, but I don't get the trampoline on startup, so I can't boot the secondary :D

Multirom installed fine on VM13, kernel has kexec patch.

PS: installation of xposed isn't working on secondary (no idea if systemless SuperSU installation is working)
[ONE Android Development] KINGbabasula:
That's weird, make sure you have injected the boot sector and post a kmsg and the kernel you are using in the primary if still not working
[ONE Android Development] paarkhi:
Thanks for the prompt Update sir Please don't think that I'm not grateful, this is just a feedback

1. White hurt the eyes even in low brightness, Do we have the option to change the background color to dark

2. Swapping ROMs is taking much longer time than 2.8.7.0
[ONE Android Development] KINGbabasula:
You can choose a theme, there is a thread here around on Xda with those themes with the color you want. No changes have been made on swapping, probably it's because your rom's data are big
[ONE Android Development] mpaopao:
http://xdaforums.com/android/themes...light-play-t2915584/post65089401#post65089401

2.8.7.x theme doesn't work with 3.0.0.0 (already tested)

White background with lowest brightness still too bright. :crying:
[ONE Android Development] Shadowghoster:
[MENTION=5093942]KINGbabasula[/MENTION] here is a kmsg from the last boot. I injected boot sector without any errors. My kernel is a custom build of Lord Boefflas (not most recent source because of my ROM).
[ONE Android Development] Tomcar:
Works with Lightning Kernel.
[ONE Android Development] KINGbabasula:
No MultiROM signs in that kmsg, it seems it's not even installed. Check in the app, and if it is, probably you brought the wrong kmsg
[ONE Android Development] Shadowghoster:
[MENTION=5093942]KINGbabasula[/MENTION] I went through my recovery log and found those lines:

about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/busybox] with 3 args
minzip: Extracted 63 file(s)
minzip: Extracted 4 file(s)
about to run program [/tmp/extract_multirom.sh] with 1 args
rm: can't remove '/data/media/0/multirom/boot.img-ubuntu*': No such file or directory

No idea if something went wrong on installing but installer said script succeeded and multirom version is properly properly shown in the app. Will try to get another last_kmsg. The one I linked was taken from /proc/last_kmsg after ROM booted.
[ONE Android Development] Micalus:
Tried to flash different roms like ResurrectionRemix, CyanPop and AICP nightly as secondary. Neither of them works, different kernels like boeffla, jgcaap's new kernel and radioactive reborn.

Also can't flash latest opengapps nano. Error Code 25. No build.prop or default.prop found.

I hope it helps.

multirom log in the attachments

Cheers

Mike
[ONE Android Development] KINGbabasula:
/proc/last_kmsg is the last boot, not the current one, to get the current kmsg you need to type dmesg in the terminal. Anyway, those lines look interesting, thanks for posting

It seems that the roms haven't been flashed correctly, I'll look into it
[ONE Android Development] darjwx:
Aicp as secondary works for me in the previous version of multirom. I haven't tried it in the last one.

---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------

Btw, I got this error with dirty unicorns test build of marshmallow. The rom is flashed correctly but don't boot. Here is the log:

https://drive.google.com/file/d/0B7jW9QY0h5cfaEZVTUFtaFVoYk0/view?usp=docslist_api

Stuck in opo logo and suddenly appears a terminal screen of multirom saying that can't boot.
[ONE Android Development] paarkhi:
+1 Can confirm this...
[ONE Android Development] Micalus:
Primary rom works like a charm. I'll try to put a backup of a caf and a non caf working temasek build as secondary. Will report back if it works. Here a photo what happens when i try to boot up a secondary newly flashed rom via multirom twrp 3.0.0

Edit1: first attempt to boot up with temasek CAF by [MENTION=5022494]Vivek_Neel[/MENTION] failed, hung itself up in boot animation, 2nd try succeeded and booted up launcher. Temasek CAF MM build 6th feb with opengapps nano 6th feb and radioactive CAF kernel v1.13. I will now try non caf temasek v4.0 build by [MENTION=3814731]katinatez[/MENTION] with boeffla kernel beta 5.1 and opengapps latest.

Edit2: Non caf temasek with boeffla kernel beta 5.1 booting up but it takes a good long time to boot. around 4-5 minutes, but running smooth as it were the primary. Also overflashing gapps and the rom itself to update stuff works as well. Like you said it seems like a problem with clean flashing a rom as secondary.

I hope it helps. Let me know if i can do anything else to help.

Cheers

Mike
[ONE Android Development] darjwx:
I got the same black "window" error (your photo) flashing dirty unicorns. (Log is in my previous post).
[ONE Android Development] mattnate:
Oneplus One user here.... I tried CM13TugapowerM33 as secondary .... dusnt work... is there any Marshmallow rom work as secondary
[ONE Android Development] darjwx:
I am with cyanogen OS as primary and omni 6.0.1 nightlies, aicp 6.0.1 nightlies and broken os 6.0.1 as secondaries.
[ONE Android Development] maxed4901:
Thank you & Feedback

Hi [MENTION=5093942]KINGbabasula[/MENTION] thank you so very much for the update. Downloading now.. Although Wolverine posted a build called 32L- i did not flash it. Just using your last 32K til now. Downloading now V33 and TWRP update. If not much to ask, maybe could you post the links in the OP thread link as well.. When you have time. Incase something happens, we can do manual also.

Will report back. Again- Glad So Glad about this come back.:laugh: :highfive::highfive::highfive:

Edit:

Was greeted with "system partition un modified" screen to allow or not allow system modification.

My primary is SOKP5.1.1 and does not look like this rom will update further as the DEV is working on MM build.. I am choosing allow modification of system. Love the UI by the way. Going to flash HTC build by Manav and see if it boots. will revert

Edit:

tried to flash https://forums.oneplus.net/threads/omnisense-sense-omni.420705/page-9

Result is erro 7. See attached Screen shots. Please let me know what the issue was. Any help? suggestions?
[ONE Android Development] mattnate:
tried omni 6.0.1 homemade still not work as secondary.... it says delete incomplete rom... do u think i need to change my kernel? using AK kernel atm
[ONE Android Development] Hkpatel111:
Somebody plz Link/Upload Latest Multirom recovery.img here.

(better if give md5 checksum).

So i can flash it through flashify.

Multirom Manager app showing installation failed error.? i tried flashing downloaded recovery by Multirom Manager app but it's NOT booting in recovery & stuck it Oneplus logo.

(Running Resurrection Remix 6.0.1_r13 build)

*RIP English ?*
[ONE Android Development] Alby7:
Sultan's CM13 ad secondary isn't working anymore after update

I had Sultan's CM13 installed as secondary until yesterday with multirom 32k, and it was working fine, after the update I renamed it and now when it tries to boot it crashes and go back to the recovery, not even going in bootloop, any thoughts on this?

Renaming could have hard any impact? Or it's just the update that broke it?:confused:
[ONE Android Development] Sander9847:
I have been using unofficial version 32l for the last month with both primary and secondary Marshmallow roms and I've had no problems. Seeing as alot of people here are having problems with the new build I think I'm gonna stick with 32l for a little longer but I'll keep following this thread closely.
[ONE Android Development] Laamapalmu:
When I boot to second rom CM13 Nightly I get error and a console with bunch of text.

"Alternate GPT is invalid, using primary GPT"

"Could not open /system/build.prop to read api level!"
[ONE Android Development] naveenjohnsonv:
For everyone in the latest multirom with the black screen error after flashing secondary rom, it's because the latest twrp doesn't flash secondary roms properly. Here's a workaround. (Worked for me)

Flash the 2.8.7 twrp from here http://xdaforums.com/showpost.php?p=63982555&postcount=2860 .

Make sure you have the latest 3.0.0 twrp img file too.

Then install the secondary rom/gapps through this recovery. Now multirom rebooting from this recovery doesn't work so once you flashed the secondary rom , flash the latest twrp, then reboot to recovery to see if it worked, then reboot to your secondary rom.
[ONE Android Development] maxed4901:
Thanks for the suggestion but the latest TWRP recovery (20160210) is in .img format. how to do suppose we flash it from twrp? or do mean to say to flash latest multirom zip?

I have tried

Sultan CM13.

Rev4mpd CM13

Cm nightly.

VM13

So far none of them booted. some are black screen and some are not installing. Error code 7 etc etc.

I think KING is working on another build seeing lot of issues with this early version. looking forward to having it sorted out.. And [MENTION=5093942]KINGbabasula[/MENTION] the white is very painful for my dear sensitive eyes. The 2.8.7 theming doesnt work. Any workaround or better if you could make some changes please. Black and dark.. wth white font perhaps.
[ONE Android Development] paarkhi:
Yes, I'm doing the same, Indian Jugaad :silly:
[ONE Android Development] Laamapalmu:
While installing second rom "E:Error executing updater binary in zip '/tmp/mr_update.zip'"
[ONE Android Development] darjwx:
Humm, I'm using boeffla kernel. You can try with other kernel just to check it.
[ONE Android Development] maxed4901:
If you have cm13 as primary, most roms boot. But having an unstable rom as primary isnt the best thought for some of us. I have not tried the 32L version yet as it wasnt an official version. I am on SOKP5.1.1 which is an AOSP rom as primary. Secondaries are MIUI7+official COS12.1 latest. latest Multirom updates havent effected any existing roms. booting perfectly. just cannot install most CM13 roms:rolleyes::crying:

---------- Post added at 04:25 PM ---------- Previous post was at 04:23 PM ----------

Anyone who can respond quickly... does changing back to old 2.8.7 multirom and twrp works? i mean its sort of a downgrade so just asking before flying off.
[ONE Android Development] mattnate:
hi... do u have link to download this kernel?
[ONE Android Development] maxed4901:
Issue comes on VM13 as follows. Ran restorecon after flashing as secondary.

No run on boot scripts for rom xxxxxxxxxx

using fstab .fstab bacon from rc files

modifying fstab ./fstab bacon

could not open /system/build.prop to read api level

left split =0

right split =0

any ideas guys?
[ONE Android Development] darjwx:
http://xdaforums.com/showthread.php?t=2899974
[ONE Android Development] KINGbabasula:
It's easy to see that MultiROM can't find the build.prop meaning that the secondary ROM hasn't been flashed correctly. The error 7 seems more like ROM specific. I'll soon have a new build
[ONE Android Development] Tomcar:
Sailfish OS as second hangs at One+ screen.
[ONE Android Development] paarkhi:
You are the best ???
[ONE Android Development] x.0ni.x:
Same here. It will have to be worked out. Give the devs time and get logcats if possible. Makes for quicker bug smashing.
[ONE Android Development] maxed4901:
Great to know.. I will only flash an official version you provide. For now I wait until next update. I feel firmware flashing needs to be improved. Assert certificate also is same on some roms. Like all ur builds I expect more stable versions to come as v33a 33b and so on..thanks. I also noticed after flashing a rom which didn't boot, i still had memory used after wiping it. Maybe auto wipe.?

Also.. What difference does it make on the multirom flashing to mount system or as read only.? What's safest option and could this effect rom flashing?

Looking forward to the delicious ? multirom updates.

Salute!
[ONE Android Development] prashuyv:
Later multirom V33 is not supporting backward compatible .... means lolipop roms are not booting as secondary .. only if we dirty flash to 6.0 can able to get... can you fix this issue
[ONE Android Development] rphlfjrd:
Hi. I'm new to multirom. What kernel is preferred if I want CM13(TugaPower or CyanPop) as primary and OmniSense (or SlimSaber) as secondary?

Currently on CyanPop w/ jgcaap newKernel
[ONE Android Development] maxed4901:
My humble suggestion [MENTION=5093942]KINGbabasula[/MENTION] .. Multirom twrp themes like this.. And option to Flash firmware also provided in this version.

http://xdaforums.com/oneplus-one/development/unofficial-twrp-2-8-3-0-t2981495

---------- Post added at 08:09 PM ---------- Previous post was at 07:53 PM ----------

All, I am writing to all MM devs in their threads to add multirom support. I did for my favs. Please vote up in ur favs
[ONE Android Development] fischwrap:
Is it possible to run omnirom as primary? Been searching for an aosp kernel that has the right patch, but to no avail (the ones that do break wifi). In sick of the cm13 battery drain, but want to experiment with other roms as secondary :-/
[ONE Android Development] ARAVIND_PAVAN:
Where's v33 link sir??

I can't seem to find it
[ONE Android Development] anagramgenius:
Download using multirom app.
[ONE Android Development] maxed4901:
Mine still booats 5.1 roms nicely

---------- Post added at 05:08 PM ---------- Previous post was at 05:01 PM ----------

I dont think omisense will boot on multirom.. lot of users complaining on the V4 not booting but [MENTION=6641721]Manav Bhagia[/MENTION] is busy with studies and is best if he does on his own time. For choosing rom> it depends on the functions. if you face difficulty in flashing any of above, i am writing a small tutorial to do it. which will be in a lower post minutes from now :)

Tugapower and cyanpop both dont have Kexec support. For more info on Kexec. read page 1. I have requested on several dev threads to include Kexec support. So far i know Marsh rom by Aaahh has kexec multiboot support meaning it can boot on multirom primary without a custom kernel.

try boeffla kernel/lightning kernel has kexec and good kernels. I would go for boeffla. Read read read... the kernel thread to find the available options and if it supports Kexec.:good:

---------- Post added at 05:28 PM ---------- Previous post was at 05:08 PM ----------

Hi everyone.. this is a small post on how i was able to install MM rom using TWRP3 and multirom33. on TWRP2.8.7Multirom32K i was able to flash and boot into Marsh rom but on multiromV33 with TWRP3- it hangs on 1+1 logo. so below is my procedure. This procedure should logically work on any CM13 rom.

1. Find the CM13 firmware file - Its 30mb+- check rom threads where they ask to flash firware (sorry i dont think i should give link/Hint:look for a MM rom thread with 180,186 views)

2. Flash the firmware package as secondary rom- it will show as a rom

3. swap internal rom with the firmware rom. so now ur internal/primary rom is the firmware rom flash.

4. reboot recovery- go primary wipe>cache>dalvik>data>system (optional since there wont be any data or system there but best to do)

5. flash the MM original rom you want in the primary slot. Flash gapps. if ROM you flashed doesnt have Kexec support, flash custom kernel (recomend boeffla kernel/AK kernel)

6. Reboot system. boot into primary.. :cool: profit!

you can move it to secondary or keep it as primary. I moved my MM rom (Marsh by Aaahh) to secondary and my primary rom is 5.1.1 stable build. all secondary and primary boots perfect. Marsh CM13 has multiscreen function too and has Kexec support so i did not need to flash any custom kernels. They clutter internal storage too much.:cowboy:

My secondaries are: MIUI7 (kitkat)+COS12.1.1+now Marsh MM

My primary is SOKP5.1.1 by Aadi Shakti

On SOT -is too soon to judge- but when i flashed it was 56% battery. Used untill drain to 13% and reached an SOT of 3hrs 24mins which isnt half bad.

Share your results. Have fun:fingers-crossed:
[ONE Android Development] rphlfjrd:
Yeah I'm getting error 7 all around with Omnisense v4 (even with v3)
[ONE Android Development] smartvinu:
When I wipe the system partition it hangs at the formating using make.ext4 . tried using f2fs and it worked. Any idea?
[ONE Android Development] darjwx:
Sometimes its slow, just wait. Yesterday was line almost 8 minutes to me and other day just a few seconds.
[ONE Android Development] laulau42400:
Hello, how are Rom who work with this release? cordially

Tapaltak and Marshmallow & jgcaap rom
[ONE Android Development] KnarrePete:
I can Boot in existing Roms but 4 me it is not possible to flash New Roms .. 1st Rom flyme 5.1.1 secondarys ressurection remix 6.01 nuclear Rom reborn 6.01 xperience 6.01 and lewa OS 5.1.1 .. Tried to flash smartisan and candy did not work update RR worked well flashing boeffla kernel into RR didn't work
[ONE Android Development] laulau42400:
Thank you

Tapaltak and Marshmallow & jgcaap rom
[ONE Android Development] darjwx:
Using the last version I was able to flash and use omnirom and broken os. Both in the mm version.
[ONE Android Development] KnarrePete:
Well my post wasn't correct i think multirom works good and with twrp 2.8.7 it was possible 2 flash
[ONE Android Development] m i n a r:
Cmon mate, I need to flash a secondary!

(we need you in Hangout though ._. )
[ONE Android Development] MMWolverine:
What the hell is wrong with you? Use older versions 32k/l & 2.8.7 and stop forcing ETA. He just got back from a long absence and promissed a fix, so let him breathe.
[ONE Android Development] darjwx:
What is wrong with you? First that is so disrespectful, and second, who are you to demand anything? He has also a life and he don't his without ask for anything. If you are so impatient build it by yourself.... That types of comments only help to pissed of the dev. Damn, think a bit, if you have a ROM and all the people is writing that type of comments....
[ONE Android Development] m i n a r:
Maybe, and just maybe, this man is part of my team and I know him personally?! But just maybe. =_=
[ONE Android Development] darjwx:
And maybe I don't know any of you personally, and I don't know if you know him and your comment to him sounds so rude for me?

And better return to the topic here.

Pm if you want but if your last comment was a kind of a joke, no one here got it cause didn't sound like that :)
[ONE Android Development] m i n a r:
Never mind, now you know it! My humor is so rude :)

Backing on topic, the problem is the multirom rather than the recovery imo. I'd recommend to stay on primary Rom and wait :/
[ONE Android Development] thedoctor.gz:
So [MENTION=5093942]KINGbabasula[/MENTION] is working on a multirom new version to flash MM rom as secondary with LP rom as primary?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] zjxpot:
you read the last few pages and didn't understand what is happening, or you just jump in and ask question hoping to be spoon fed????
[ONE Android Development] x.0ni.x:
Good stuff!!??
[ONE Android Development] tushparmar:
I know this is kind of repeated post but still posting it because I couldn't find the exact resolution to this problem. I am getting below error while trying to boot into secondary rom (Official CM13 Nightly, Temasek CM13 Unofficial),

<14>[ 4.034340] multirom: ROM: RR-CM-13

<14>[ 4.034589] multirom: base_path: /realdata/media/0/multirom/roms/Internal

<14>[ 4.035012] multirom: icon_path: /realdata/media/0/multirom/icons/romic_cm1.png

<14>[ 4.035434] multirom: type: 0

<14>[ 4.035685] multirom: has_bootimg: 0

<14>[ 4.035933] multirom: ROM: cm-13.0-20160214-NIGHTLY-b

<14>[ 4.036355] multirom: base_path: /realdata/media/0/multirom/roms/cm-13.0-20160214-NIGHTLY-b

<14>[ 4.036779] multirom: icon_path: /realdata/media/0/multirom/icons/romic_default.png

<14>[ 4.037029] multirom: type: 1

<14>[ 4.037454] multirom: has_bootimg: 1

<11>[ 4.037735] multirom: Skipping ROM selection, is_second_boot=1, auto_boot_type=0x1

<11>[ 4.038282] multirom: No run-on-boot scripts for ROM cm-13.0-20160214-NIGHTLY-b

<14>[ 4.088424] multirom: Using fstab ./fstab.bacon from rc files

<11>[ 4.088512] multirom: Modifying fstab: ./fstab.bacon

<11>[ 4.089257] multirom: Could not open /system/build.prop to read api level!

<14>[ 4.090091] multirom: Left Split=0

<14>[ 4.090316] multirom: Right Split=0

<14>[ 4.114341] multirom: Framebuffer implementation: Qualcomm ION overlay

<3>[ 4.133668] mdss_fb_ioctl: unsupported ioctl (40c86da4)

It would be great help if anyone can guide me to resolve the issue. Thanks in advance.
[ONE Android Development] darjwx:
A easy solution is:

1. Make a backup of your actual primary ROM.

2. Flash the wanted ROM as a primary and boot it.

3. Make a backup of the new primary ROM.

4. Restore if you want your old primary.

5. Flash the backup of the wanted ROM as a secondary.

I did this with dirty unicorns and now its working.
[ONE Android Development] tushparmar:
Thanks for the tip.

Couple of questions,

1) Do I need to follow the same steps for all following updates or is it required only for the first boot?

2) Does it mean Multirom latest version is not yet ready to flash MM rom as secondary?