yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] cli-addicted:
Last upgrade seems to brake OTG

I'm on cm-12.1-YOG7DAS2K1 and the last update seems to brake "some" OTG functionality. The system don't recognizes my Kingston microDuo (also TDK TransIt isn't recognized) exFat formatted anymore once installed the kernel patch, but seems to recognize other vendors such as Transcend Information or Chipsbank Microelectronics.

MultiRom v33a

Recovery 2016-02-21(1)

Kernel: 5.0.x kexec-hardboot patched
[ONE Android Development] Mike_1996:
Had exactly the opposite problem. Had a GUID-bootable MBR drive, Android automount mounts only the first EFI partition. Then formatted the disk from Android, which works well on Windows but fails to mount on Mac. Again wiped and formatted on Mac and now works for all three. I'm still on the older YOG4PAS3JL and suppose the problem comes from the partition table.

By the way, before reformatting, try with the recovery which newly gained support for exfat partitions.
[ONE Android Development] :
Has anyone else noticed how some ROMs get super laggy and sluggish after like 5 minutes? For example: Earlier i had COS12.1 with AK Kernel on Primary and it was working perfectly fine. I flashed Resurrection Remix 5.5.9(Last Lollipop build) on Secendory and whenever i booted into it would get really sluggish after some time, rebooting would fix the problem temporarily as the sluggishness came back after 5 minutes again. And by sluggishness i mean like where it takes 10 seconds to react to a touch, and takes even more time when i lock the screen and switch it back on. Also, i've tried flashing AK Kernel, same as the one i had on COS 12.1 on RR but it didn't help. Same used to happen with TugaPower's V100(Again, his Last lollipop build) on Secendory. So today i made a clean flash, wiped everything and flashed TugaPower on the Primary Partition, it worked fine until i installed MultiROM and the problem came back even though i had no other ROMs on Secendory partition. So is it a problem with the ROM? Cause Unofficial EuphoriaOS(CAF) always worked fine and so did some other ROMs. Sorry for the long post. Hope someone can help me :)
[ONE Android Development] MMWolverine:
I wouldn't use Ak kernel with any of these roms. It's totally outdated.
[ONE Android Development] :
But all of them are from around the time that kernel was released. The last RR build came out on 20th November, COS12.1 was a little older, AK Kernel came out on 28th October. Anyways, I just tried Boeffla on COS12.1 primary and the same problem persists although I'm using the Stable Version(not the Beta) Hope that doesn't cause any problem?
[ONE Android Development] MMWolverine:
Well with similar config (COS12.1.1 primary and RR secondary, both running Boeffla) I never had such problems. Latest RR releases do have system UI lag/stuttering, but is fine once you change the theme and reboot. Imo not caused by Multirom.

Btw, which firmware did you install? The one that comes with COS12.1?
[ONE Android Development] nimeshlmcp:
multirom twrp fails to flash SuperSU
[ONE Android Development] :
I'm using this firmware(It uses c1-11 base and 241 modem/sb1) and tried the 15th May 2015 one also. But can Firmware cause such a problem? Anyways, Thanks a lot for your time, i guess i'll just stick with other ROMs...

---------- Post added at 05:24 PM ---------- Previous post was at 05:19 PM ----------

Are you trying the system less ones? They won't work. Try using the "SystemMode" version here: http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[ONE Android Development] mickcost61:
Thanks

---------- Post added at 01:28 PM ---------- Previous post was at 12:56 PM ----------

Many thanks
[ONE Android Development] bkr32:
Clean flashed stock images and tried re-installing multirom, installation goes fine but the device bootloops instead of showing the multirom menu/screen anything special i have to do?

uninstaller doesn't help either neither does flashing another kernel,i have to reflash stock zip each time this happens
[ONE Android Development] albi97x:
Can somenone help me to install ubuntu touch using multirom manager app? Because when i try any version the opo stuck in the boot logo
[ONE Android Development] darshiz:
try the stable version 10
[ONE Android Development] lokesh.3440:
Can't boot Jgcaap's cm 13 with Sultan's cm 13 ROM as secondary. I am unable to see the multiROM splash selection screen at all. Can anybody put a light on this ??

Edit: BTW my selinux is permissive.
[ONE Android Development] darshiz:
Try using lightning kernel for cm13
[ONE Android Development] lokesh.3440:
OK buddy I will try flashing it first.
[ONE Android Development] buginside:
Using F2FS?
[ONE Android Development] drmuruga:
I download Ubuntu touch seen in multi ROM manager, but when trying to flash error seen, any idea to flash ?
[ONE Android Development] MexiDroid:
i have cm13 with lightning kernel v16 and now i have v17

before i was able to boot secundary cm13 sultan, but not anymore.

why?
[ONE Android Development] Seagorilla2:
I had the same problems after updating to the latest of SultanXda (prim) and Jgcaap (sec). Even with lightning kexec kernel on prim. multirom did not show. I solved the issue by reflasing multirom zip in recovery. I think latest SultanXda CM13 did something to overwrite multirom files.
[ONE Android Development] dragsterman:
If I flash a ROM to secondary or 3rd ROM which contains a different firmware than my OPO currently have (I know that all secondary ROMS use the firmware of the primary ROM) will be my firmware uptated? (so all of my ROM's firmwares updated)
[ONE Android Development] merothh:
You have to inject multirom into kernel after every flash..that's why it didn't show up.
[ONE Android Development] :
I've tried many solutions but none of them seem to work, most of the LP 5.1 based ROMs just start lagging and take 10 seconds to respond after some time of booting, even when i have only the ROM on primary and nothing else on secondary :(
[ONE Android Development] dragsterman:
Could you help me in this question?
[ONE Android Development] acuicultor:
Firmware only gets flashed on primary rom on secondaries you have to apply the option to set different radio.img.

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] dragsterman:
OK, but this means that if I flash a ROM to secondaries and this ROM contains a firmware then this firmware will be ignored when I flash? So after the flashing my primary ROM will have the old firmware?
[ONE Android Development] acuicultor:
Yes

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] dragsterman:
Thank you.
[ONE Android Development] crazydude10:
Hey I'm trying to use Sultan's MM rom as secondary and have a KK CM nightly as primary with boeffla kernel.

When I try to use the system mode version of super su on MM, ,zip flashes successfully but it results in a bootloop. Systemless version too has the same problem.

I tried all 3 versions from the thread you quoted - 2.65; 2.68; 2.70.

Any idea on how to diagnose the problem?
[ONE Android Development] :
It used to work fine for me :/ Maybe Sultan's MM doesn't work with SuperSU? He used to recommend not to flash SuperSU before, not sure about current status.
[ONE Android Development] crazydude10:
Oh :( he has since shifted the rom base to stable cm branch which doesn't include root hence this trouble.
[ONE Android Development] :
Oh yeah, i read about it..Last option..Did you try v2.52?
[ONE Android Development] crazydude10:
I tried that as well with the same results, so I'm beginning to wonder if that particular kernel lacks support for the 'system mode' version. Anyways thanks for your help !:good:
[ONE Android Development] silvagroup:
Having same problem with many different ROMs doesn't matter if cm or asop or version of supetsu. Also noticed since flashing latest MultiRom and twrp my once stable primary ROM reboots 5-6 times on average per day... Data, wifi, sync, etc all screwed up. I know it sounds like firmware except it's the firmware that has been rock solid pre flash of 33a and twrp 3.1.

Going to try reverting to last working version me things something with multi or twrp causing most of these problems.

---------- Post added at 05:15 AM ---------- Previous post was at 05:04 AM ----------

PS

Don't want to assume we all know what happened when we assume.

So do I have to use 33a with twrp 3.0.0.1 only can I mix them up. Can I try 33a with 2.*.* versions ???? for example???
[ONE Android Development] MexiDroid:
1.- i have istalled CM march 28 stock cm kernel

2.- i installed the neccesary to multirom

3.- i have installed sultan as secundary

4.- im able to boot into any of these rom (works perfectly)

5.- i update primary cm rom march 31

6.- i have nstalled kernel patch from multirom apk

7.- reboot and after created cache i got system UI FC

8.- flashed the march 28 again and booted

9.- patch the kernel and reboot

10.- secundary rom wont boot

why???

------

i have to delete secundary rom and reinstalled again and boot (have to setup again)
[ONE Android Development] Mike_1996:
The kernel is different after upgrading the primary ROM, so you'll have to use the new kernel as your base for faking boot.img. The easiest way would be a dirty flash on secondary.
[ONE Android Development] kuulbhaskar:
install the latest Supersu from HERE which is SuperSU v2.71 and flash working fine in 26/3 cm13 sultan's build !!
[ONE Android Development] crazydude10:
Great ! :good: The latest version worked ! I gave up trying it after 2.70 but this one worked.

On another note, the first boot after Super su installation failed and it rebooted into TWRP. The second boot worked fine. Maybe the older version worked too and I just happened to give up after the 1st failed boot. :confused:
[ONE Android Development] dragsterman:
I have successfully deleted a ROM but in the log there was 2 red error with this text: "Unable to find partition for path '/realdata' "

What does this mean?
[ONE Android Development] ARAVIND_PAVAN:
Which version??

33a or 32l ??
[ONE Android Development] Tomcar:
33a, but Kitkat is not runnung properly.
[ONE Android Development] :
Nevermind, i found it. Sorry for the post. It doesn't affect the original firmware

I know it might sound a little stupid but i was running Mr.shme's Frankenstein Firmware and flashed OxygenOS 1.0.3 as a secondary and it seems like it also flashed the firmware, so i was wondering if this is possible(Secondary ROM flashing the firmware by itself)? I can't confirm if it did cause they both use 241 modem but the Bootloader icon makes me feel like it did...
[ONE Android Development] sabbeer:
After installing multirom, camera isn't working. It says, "can't start camera." Running on latest version of multirom. Sultans cm13...
[ONE Android Development] Okeys:
+1,the same.

---------- Post added at 10:43 AM ---------- Previous post was at 10:43 AM ----------

Can I install Ubuntu Touch with kernel from Multirom manager?
[ONE Android Development] dragsterman:
I have forgotten to write I got this error in MultiROM TWRP 3.0 and yesterday I have also seen this error message when I flashed a new build for one of my secondary ROM but the flashing was successful.

Why I am getting this error?
[ONE Android Development] SirSoviet:
I have Private Kernel r9 installed on internal (which includes kexec-hardboot patch) and injected boot sector, however secondary roms will not boot because I apparently don't have the patch on internal. Do I have to install a kernel that includes this patch for secondaries too? Also, do I flash GApps , SuperSU, Xposed, etc. by going into manage secondary roms, selecting rom and pressing "Flash ZIP"? Sorry, it's my first time using MultiROM.
[ONE Android Development] phillipmckinnish:
Do any of y'all have link for Multirom TWRP 2.8.7??? Thanks in advance..
[ONE Android Development] Okeys:
How can I install kali nethunter? MultiROM wrote an error... I'm on Sultan 13.
[ONE Android Development] maxed4901:
Yes.. and i recomend you wipe cache and dalvik from the same menu before reboot.

Multirom>list roms>"choose rom"> wipe cache>wipe dalvik> reboot after flash

---------- Post added at 04:12 PM ---------- Previous post was at 04:08 PM ----------

[MENTION=5093942]KINGbabasula[/MENTION] i also came across this- but did not notice any issues because of this.. would also like to ask if you are planning TWRP update.

Thanks
[ONE Android Development] maxed4901:
Multirom and cos13

[MENTION=5093942]KINGbabasula[/MENTION] and anyone who could propose a solution.

I am on multirom 33a and last modified recovery twep 3.0.0-0

Are these latest?

Tried to flash cos 12.1 YOG7DAS and getting error. Couldn't upload image from browser. Will post tomorrow when m on more stable network.

Couldn't flash cos13 which is posted on XDA either. Please help.
[ONE Android Development] nachomagic:
Hi mates

In in a xposed bootloop but for a secondary rom, so in the twrp file manager I don't know where is the /data/data to disable xposed.

Do you anybody know where is it?

Thanks in advance
[ONE Android Development] Kingzak34:
It's in system/framework delete xposed bridge.jar

Tapatalké depuis mon mega Mate 8
[ONE Android Development] maxed4901:
I am having error 6 flashing a secondary ROM dirty flash update. Anybody can help? Where's [MENTION=5093942]KINGbabasula[/MENTION]? Been having issues flashing DU. And i really want this ROM. It doesn't have multirom support so can't keep as primary. Prepared to pay for a fix too.
[ONE Android Development] KINGbabasula:
I have now updated the recovery to TWRP 3.0.2 with included [MENTION=2605798]nkk71[/MENTION] 's no kexec workaround which I tested and seems working pretty good, finally it's not always needed to have a kernel with kexec hardboot patch
[ONE Android Development] Hijmen:
Updated multirom and recovery. Was scared at first when I booted in recovery, no multirom entry to be seen at first sight. Looking around I found it in the top right corner under the 'menu' stripes.

Thnx for the updates!
[ONE Android Development] nkk71:
Glad to hear it's working for you as well :D

For those interested a description of the no-kexec workaround (including the advanced options) is here

there's some outdated information (from the previous workaround) which needs to be updated, but it should give you a general idea and explanation of the various options.
[ONE Android Development] crazydude10:
Does anyone know of a workaround for Twrp not remembering the last used folder path? I was hoping it would be fixed in latest twrp update, but it still exists.
[ONE Android Development] clock51:
the new TWRP has also not the Italian language?
[ONE Android Development] kuulbhaskar:
i too confirm that the new multirom along with twrp with no kexec boot workaround is working fine. Have just flashed cm12.1 sultan's latest build as internal with no kernel with kexec hardboot patch and exodus 6.0.1 with lightning kernel as secondary and is working flawlessly with no bootloop !!
[ONE Android Development] musklor:
Hello, I have encrypted my phone, could I install multirom with no kexec boot and put some secondary roms ?
[ONE Android Development] maxed4901:
Thank you for your contribution dear and to [MENTION=5093942]KINGbabasula[/MENTION] for coming to the rescue.:good::fingers-crossed:

. The no Kexec is a great thing for sure but if i may- on a scale of 1 to 10- how safe is it to use a rom without Kexec as primary with the workaround? does this also mean we now can use any rom as primary despite it having or not having Kexec? if i do choose "use no Kexec workaround always" that is...

wow!! i never thought this day will come.. now i am sad because i couldnt try some roms bcz of Kexec support!!! LOL..:good:...:cool:

CUSTOM ROMS!- Here i come!
[ONE Android Development] anagramgenius:
[MENTION=5093942]KINGbabasula[/MENTION], thanks for the update and stock theme of TWRP.
[ONE Android Development] nkk71:
I can't really put it on a "scale"... MultiROM in itself is a hack (with or without the no-kexec workaround), so that is already something to be aware of.

As for me, I've been running the no-kexec workaround (version 1) for about 8 months or so, until I eventually released it for the HTC One M9 in December.

version 1, had an issue with a possible "lingering primary_boot.img" (though it would not happen in most cases, it was something that could be done easily, if you wanted to and knew how to)

as of version 2, I believe I've accounted for most/all possibilities regarding that, and i've done considerable tests on HTC One M7, M8 and M9

the workaround does (in the background) flash your boot partition when needed, so yes, that could be considered "unsafe"? .... though, flashing a custom ROM, kernel, (even TWRP backup & restore) does it.... are those "unsafe" as well, and how would you rate those on a scale of 1 to 10 ;)

The real question is, do you consider kexec-ing a secondary boot.img safer ... is MultiROM in itself "safe", etc.

I have purposely added it as an optional build option, since I cannot test devices I dont have, nor do I know much about the OPO, Samsung (though also got a confirmation it worked), LG, etc.

hence:

If the device maintainer deems fit to include it, then I'm pretty sure, he has tested it, and finds it suitable for the device.

Long story short: flashing anything can be "unsafe" whether that has to do with MultiROM or not... it's really an individual decision, of how far you want to mod your phone ;)
[ONE Android Development] néonaloj:
Hi,

I need help please... I only today understood what the problem is, trying to update to 33b. But the problem began with 33a update.

In fact, since the 33a update I could no more update my/ flash new secondaries . The error was like that:

"extracting contents of boot.img..."

"failed to load bootimg!"

"erasing incomplete ROM..."

"FAILED" (in red)

But today, with the new multiROM update 33b, I could observe what's happenning: when time has come for the app to follow the update process into twrp, in my case it goes into it, only 2 or 3 sec , and it comes back on the bootmenu (with roms to choose from)!!!

So I tried to "Inject curr. boot sector", and the result is:

"MultiROM is not installed!"

All "seems" to be ok with my twrp, but "Multirom is not installed", and I am not able to install it trough the app.

Can I just get the "multirom-20160417-v33b-UNOFFICIAL-bacon.zip" and flash it in my "not installed" twrp?? Other solution?

Many thanks to who will help!
[ONE Android Development] nkk71:
Small note regarding encrypted devices using the no-kexec workaround

Since I dont use encryption, I haven't tested this to much extent, but I believe that there is a

BOOT PRIMARY ROM

option, which you can choose to boot into Internal without decrypting the device first.

Please be aware that this should not be used, if: the last booted ROM was a secondary using the no-kexec workaround.

The reason is that the backup of the primary_boot.img, is stored in the multirom folder, so for the no-kexec to be able to restore it, it needs access to the /data partition:

Booting into primary,

while the previous rom was using the no-kexec-workaround

(in which case the real primary needs to be restored first)

It's not too much of a big deal, because when the no-kexec workaround encounters an error, it reboots to recovery (and since recovery will restore the primary_boot.img), another reboot would be fine.

I do however (until I address this particular issue), encourage you not to use the BOOT PRIMARY ROM option, but instead decrypt the device, and then select the Internal ROM to boot.
[ONE Android Development] laulau42400:
Hello

Thank you for the update, it does exist a theme for this release?

Laurent
[ONE Android Development] threetwentyfizzle:
Think I just Soft Bricked my phone. Tried to install via the MultiRom App, and now just bootloops in the multirom boot menu. Cannot reboot to recovery or bootloader.
[ONE Android Development] bick:
Press an hold POWER button for 15-20 seconds to switch it off, then press and hold VOL DOWN + POWER for 5 seconds to get into RECOVERY (or press and hold VOL UP + POWER for 5 seconds to get into BOOTLOADER).

Hopefully you'll get one of them.:good:
[ONE Android Development] threetwentyfizzle:
Was able to force reboot out of the multirom bootloop eventually into recovery, but it was Read only, couldn't write. So essentially I racked my brain for about an hour trying to change the kexc workaround option in multirom settings, but it would never stick, and couldn't flash any roms.

So I had to fastboot flash twrp and delete all of multiroms traces while I was mounted and connected to my PC to get running again.

Wish I had a log to provide, but it was a freak weird occurance, I've never had any problems installing Multirom from the app before. Hopefully I can successfully get it going in the near future, I love the ability to test various roms without sacrificing time to reflash your usual setup afterwards (Nandroids take forever to restore)
[ONE Android Development] FloorFox:
Is there any different thread for Ubuntu touch? So i can ask questions about it.

Thanks
[ONE Android Development] sabbeer:
Today i tried flashing paranoid android 4.4.4, and got an error.
[ONE Android Development] Shadowghoster:
[MENTION=5093942]KINGbabasula[/MENTION] did you ever consider making multirom f2fs capable? I think it would be a nice addition because a lot of people are using it. Besides that a warning in OP that f2fs isn't supported right now would be helpful, I must dig in my kmesg to figure that out...
[ONE Android Development] JJohnson1988:
This.

The sole reason I'm not using MultiROM is because I really don't want to go back to Ext4.
[ONE Android Development] IamsKs:
which rom are you using now on f2fs?
[ONE Android Development] JJohnson1988:
Sultan's CM13.
[ONE Android Development] néonaloj:
Up please...

I still have a "working" TWRP but cannot use it because of "MultiROM is notinstalled", that happened when I tried to update first to 33a, then 33b...

How can I re-install multirom please?? By flashing trough 'install' into my twrp?

Thanks for your help, sorry for bad english.

EDIT: I did flash "multirom-20160417-v33b-UNOFFICIAL-bacon.zip" many times, it says it works successfully.

BUT, when I try to flash a new rom as secondary or to update a secondary rom, it ends up with the same words at the end:

"..."

"extracting contents of boot.img..."

"failed to load bootimg!"

"erasing incomplete ROM..."

So I suppose I need to have a "dramatic" response no? Could someone please help me? How do I procede?

Thanks ;)
[ONE Android Development] nkk71:
full log please (found in /tmp/recovery.log),

as well as details (links to thread and file) you were flashing,

as well as details if this had systemless root involved or not

.
[ONE Android Development] néonaloj:
I'm sorry, but I only have between "/system" and "/vendor" a file called "/tmp-mksh", nothing like "/tmp" alone, and a search for "recovery" gives a empty file...

Also I cannot take any screenshot of my TWRP, it says something like "screenshot saved here...", but it's not saved and I cannot find it back after that!

The zip I flashed is the one of the MultiROM app, you can find the link of "multirom-20160417-v33b-UNOFFICIAL-bacon.zip" in the second post of this trhread

I also tried with versions 33a and 32k with the same results.

I don't understand this part of the question, sorry ??

What I can do:

- delete a rom

- backup a rom

- restore a rom (install from a backup)

- add some stuff to an existing rom (xposed, change gapps ...)

- to boot from any of my existing roms.

What I cannot do:

- add a new rom as secondary/ update a rom

- update/ flash a working Multirom app

Thanks for your help!