yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] M!shr@ji:
[MENTION=5686657]smeet.somaiya[/MENTION], thanx for clearing that :)

Post #3 says -

"Can I have different versions of Android working alongside

Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated."

I wonder if two ROMs can have different kernels then how come kernel might be an issue :confused:
[Galaxy Note II Original Android Development] ravijani:
Yes camera works without any issues.
[Galaxy Note II Original Android Development] afarkas:
Thanks. And which version should it be? The 4.2.8 right?

And the, I cant find the blobs there
[Galaxy Note II Original Android Development] tilaksidduram:
Touch input fixed in the multirom boot manager. No more of using vol up and Down keys to navigate. Just use touch.

Download the updated multirom zip file from the 2nd post.

Boot into recovery and flash the zip normally and before rebooting the phone, select "Inject multirom into current Boot sector" and then reboot
[Galaxy Note II Original Android Development] MBariya:
I flashed TW as primary and CM11 as secondary with Agni 4.2.8 which causes WiFi problem in secord ROM.

But just to check kernel capability I flashed CM11 as primary with Agni. WiFi problem is still there in CM11. May be Agni is not compatible for AOSP.

Even I got some call related problem after flashing multirom. Call volume gets mute when I flash aosp ROMs as primary and secondary. Anyone facing same problem?

It only comes back after removing multirom. Tried both kernels but same result.
[Galaxy Note II Original Android Development] Chris189:
Hi! Is it possible to run 4.4.4 TW Ported rom with this MultiROM? When i'm trying to boot it says error occured and not booting. I'm tried 4.4.4 AOSP roms and they are working fine. Thanks.
[Galaxy Note II Original Android Development] Ismail.A:
Yes on my second aosp rom no wifi
[Galaxy Note II Original Android Development] paarkhi:
Yes 4.2.8 it is and no need of blobs with the new version
[Galaxy Note II Original Android Development] kashortiexda:
Where can you select "Don't share kernel" ????????
[Galaxy Note II Original Android Development] smeet.somaiya:
[MENTION=539770]tilaksidduram[/MENTION] Touch Input still doesn't work with that updated multirom.zip
[Galaxy Note II Original Android Development] simo.scorpion:
to me work
[Galaxy Note II Original Android Development] M!shr@ji:
+1
[Galaxy Note II Original Android Development] tilaksidduram:
DOnt share kernel option has been removed. we no longer use it. i will update the faq section later.
[Galaxy Note II Original Android Development] tilaksidduram:
It is working on my phone. how are flashing this new zip file?

boot into recovery, select Install Rom and then choose the file and click "swipe to flash" once it is complete do not reboot, select inject multirom and then reboot the phone.
[Galaxy Note II Original Android Development] shujanster:
[MENTION=539770]tilaksidduram[/MENTION] i follow the step by step and MultiROM inject curr. boot sector but touch not work.thanks.
[Galaxy Note II Original Android Development] Seken:
How to download Firefox OS and Ubuntu Touch ? Please help
[Galaxy Note II Original Android Development] ztotherad:
okay, so this is a killer experience, I'm wondering if this can easily be ported to the other note 2 variants (US variants).
[Galaxy Note II Original Android Development] tilaksidduram:
I see u are injecting current boot sector. That is incorrect. Pls choose inject multirom after you gave flashed this zip. Make sure you are flasing this using the install ROM option for the primary ROM and not for secondary ROM.
[Galaxy Note II Original Android Development] M!shr@ji:
Sorry buddy, can't find this 'Inject MultiROM' option. While flashing, 'Inject multiROM after install' option is checked by default, I leave it as it is. Then after flashing, We have an option of 'MultiROM. Inject curr. boot sector' but not 'Inject MultiROM'. And thus touch is not working.

And moreover, I flashed the latest version (20141019) in the first go itself, so should this option even matter to me for touch? :confused:
[Galaxy Note II Original Android Development] kbhuvi:
You mean when flashing the zip in the primary, there is an option just above the swipe that says 'inject multi rom' . Is that to be checked. After flashing, out of the four options, one is inject current boot sector with multi rom written on top. Apart from above i have not been able to locate any other option to inject multirom.

Touch still not working ??
[Galaxy Note II Original Android Development] kbhuvi:
delete
[Galaxy Note II Original Android Development] tilaksidduram:
Not sure how you are doing it. The steps are as follow

1. Click Install button in TWRP recovery - Screen 1

2. Select the MULTIROM zip file dated 2014-10-19 - Screen 2

3. check mark the option that says "Inject Multirom after Installation" and then swipe to confirm flash - screen 3

4. reboot
[Galaxy Note II Original Android Development] M!shr@ji:
Followed word by word. No luck again. :(
[Galaxy Note II Original Android Development] smeet.somaiya:
Doing exactly the same. But still it's not working. I guess can it be because I am dirty flashing it? I mean flashing it over already installed multirom zip and secondary rom too
[Galaxy Note II Original Android Development] tilaksidduram:
can u post screen shots of the twrp screen. i have listed 3 steps above, each of them are in sequence.

Use the power button and vol down key to take a screen shot when you are in twrp recovery.
[Galaxy Note II Original Android Development] tilaksidduram:
that does not matter, since you are in the Multirom TWRP recovery, you just need to choose Install and follow the steps i have mentioned above in my earlier post. Send me screen shots of ur Multirom recovery.
[Galaxy Note II Original Android Development] kbhuvi:
Bro, did it as you have detailed. Still a no go

Not much of a bother though, No sweat in pushing buttons.

Perhaps will reinstall it from scratch when i have some time

I have come across another issue. When in secondary rom, although the device is in MTP mode, the computer fails to recognise it. Cant transfer files. Had to remove card and do via a reader.

By the way did i thank you for your efforts and your hard work. Its been amazing using this utilty. Way to go bro, you are the man. Godspeed..
[Galaxy Note II Original Android Development] M!shr@ji:
Here You go
[Galaxy Note II Original Android Development] M!shr@ji:
About thanks, no words would suffice :)

About MTP mode, my computer fails to install the device driver when connected with secondary ROM. Same works with primary ROM. Is this problem irrelevant to this thread or has to do something with MultiROM?

---------- Post added at 11:26 AM ---------- Previous post was at 11:22 AM ----------

Is there a remote possibility that touch interface might not be working for those using AGNi 4.2.8 and not the stock one provided by you [MENTION=539770]tilaksidduram[/MENTION] ?
[Galaxy Note II Original Android Development] kbhuvi:
I agree. Hats off to [MENTION=539770]tilaksidduram[/MENTION]

I think the issue of not connecting to computer perhaps has something to do with multirom as it does not connect when secondary rom is booted. Primary connects fine. Not a big issue though. (I am just expressing my thought, please do not construe it as a complaint)

The kernel provided by [MENTION=539770]tilaksidduram[/MENTION] is for aosp roms. With that both the rom (primary and sec) will also have to be aosp. At this point only [MENTION=4365701]psndna88[/MENTION] has come out with agni kernel with kexec patch for tw roms.

I think somebody using tw rom and agni kernel can let us know whether he has got touch interface working or not.

For members who have got touch interface working may kindly let us know whether their primary rom is tw or aosp and other codes that their devices are wearing.

Another thorn is Whatsapps. It has to be re-verified on changing roms. Hope some developer can wrap his head around it.

regards
[Galaxy Note II Original Android Development] M!shr@ji:
I'm one of them, touch not working :( Dr.KetanV12.1+AGNi 4.2.9, CM11+AGNi 2.8.9, OmniNightly20141014.
[Galaxy Note II Original Android Development] kbhuvi:
Lol. i know that [MENTION=5636029]M!shr@ji[/MENTION]. I am expecting others who have touch interface working to respond to the roms and kernels they are using
[Galaxy Note II Original Android Development] M!shr@ji:
+1 :silly:
[Galaxy Note II Original Android Development] Mike0505:
Touch not working , primary Dr.KetanV12.1+AGNi 4.2.9 , (sec Xperia z-ized not booting dosn't matter (as in Op sayed to large image))
[Galaxy Note II Original Android Development] shujanster:
sorry [MENTION=539770]tilaksidduram[/MENTION] bai, i can't find 'Inject MultiROM' option. but 'Inject multiROM after install' option is check by default. maybe i forget something. i try every way but can't find any solution. anyways thanks for your help.
[Galaxy Note II Original Android Development] tilaksidduram:
can some one using AOSP rom as primary confirm if there are also not able to see Touchscreen working after flashing the updated Multirom zip.

I am using AOSP as Primary and touch is working fine on my phone. i haven't tried with Touchwiz. i will install touch wiz and check later in the evening and revert back.
[Galaxy Note II Original Android Development] simo.scorpion:
No, for me working fine, cm11 primary with your kernel

Inviato dal mio OnePlus One
[Galaxy Note II Original Android Development] M!shr@ji:
That means it's almost confirmed, TW is the culprit. Let us wait for [MENTION=539770]tilaksidduram[/MENTION] 's observation.
[Galaxy Note II Original Android Development] M!shr@ji:
Secondary ROM stops booting when I flash AGNi kernel to primary TW ROM. Reflashing the secondary ROM doesn't help. I have to delete the secondary ROM and install it again with recommended steps and it starts working again.

Any work around for this?
[Galaxy Note II Original Android Development] shamiflavour:
It would be a lot easier if some one upload whole process video for note 2 n7100..im confused
[Galaxy Note II Original Android Development] kashortiexda:
screen / phone freezing up upon sleep

I'm on primary TW DN3v5 and secondary AOSP

Everything works great but every time the phone enters deep sleep, it literally enters a DEEEEEEP sleep, and cannot be woken from it, unless I reboot.

Anyone else experiencing this ?
[Galaxy Note II Original Android Development] M!shr@ji:
Select Normal (Optimised) Main profile from AGNi control app. Solved the issue for me.
[Galaxy Note II Original Android Development] tilaksidduram:
Go to recovery and select Advanced -> Multirom -> List ROMS -> Select your secondary and click remove boot.img and reboot

now you secondary rom will boot fine with out any more issues.
[Galaxy Note II Original Android Development] kingkij:
[MENTION=539770]tilaksidduram[/MENTION] I just restored a nandroid backup on primary rom and touch on multirom manager started working, So i can confirm that culprit is touchwiz. Previously i was running ditto note 3 with patched agni kernal as my primary rom and touch was not working.
[Galaxy Note II Original Android Development] M!shr@ji:
[MENTION=539770]tilaksidduram[/MENTION] I knew you would say this :D But I already tried that. The boot.img is already deleted and it shows add boot.img instead of delete boot.img. :confused:

Actually it gets selected for boot but after entering it's stuck on boot logo. If I install another aosp rom after the tw agni kernel flash, It boots fine.
[Galaxy Note II Original Android Development] kashortiexda:
^^ [MENTION=5636029]M!shr@ji[/MENTION] what aosp rom are you having issues with ?

I tried Nameless yesterday and it wouldn't boot .... because it needed rp40 Mali or something to that effect which needs it's own special kernel

Don't know if you're having similar issues ???
[Galaxy Note II Original Android Development] M!shr@ji:
Naah... no empathy here mate... I was using cm11 ss M11 and omni nightly which both worked okay (without wifi ofcourse) before I reflashed the AGNi kernel for some reason.
[Galaxy Note II Original Android Development] tilaksidduram:
Touch screen issue has been fixed. the Problem was touchwiz had a different input path compared to AOSP and i was missing that in my sources. i have tested it on my phone where i have DN3 running as primary and other AOSP roms as secondary touch works fine.

i will upload the files in some time.
[Galaxy Note II Original Android Development] dream_catcher79:
Hi Guys,

I just installed multirom on my gt-N7105.

I can only install on internal memory? Because. The options when I am installing are:

Internal memory

Devblock "something" vfat (I suppose this is the memory card)

But when I am in the menu to boot roms, it only shows the internal rom.

Do I need to do something more?
[Galaxy Note II Original Android Development] M!shr@ji:
Is your memory card format ext4? Same happened to me too. Try copying you data to PC and formatting the card in extX, NTFS or FAT32 format. Should solve the issue. FAT32 is working. Can't say about the other two. They are mentioned in the OP though.

One more thing, even FAT32 formatting didn't let me boot into USB OTG though the ROM option was there but with external memory card, you should not face the issue.
[Galaxy Note II Original Android Development] M!shr@ji:
Waiting since 01:29 AM :fingers-crossed: Busy shopping for Dhanteras? ;)
[Galaxy Note II Original Android Development] Ismail.A:
How about wifi working. In secondary rom
[Galaxy Note II Original Android Development] kbhuvi:
Folks, i have installed two roms

primary - TW and secondary is AOSP

i have tried to install third rom (tw) on internal storage

rom is installed but does not boot

removed boot img but no luck

can i install another tw rom or it has to AOSP only.

can i have some steps for reference

regards
[Galaxy Note II Original Android Development] MBariya:
Two Roms are bigger. So they will not load proper as secondary ROM. Prefer Aosp Roms as secondary ROM.
[Galaxy Note II Original Android Development] kbhuvi:
My primary rom is debloated. Storage shows 580mb used by system, out of 5.5 gb

sec rom is AOSP. 288 mb being used

after installing 3rd tw (debloated) the available storage is 7.75 gb

i think it can be done
[Galaxy Note II Original Android Development] :
I've had this exact same issue/question for almost a week now. My memory card is exfat formatted and it shows up as '/dev/block/mmcblkp1 (exfat)'

Also, I installed a ROM to my external SD card. It shows up in 'List ROMs' in recovery, but during boot up, when selecting ROM, i select External tab, it just says "The list is refreshed automagically, just plug in the USB drive and wait." If I select internal, I can't see the ROM i just installed.
[Galaxy Note II Original Android Development] M!shr@ji:
As I said above, exFAT is not mentioned as supported format in OP. Try FAT32.
[Galaxy Note II Original Android Development] yogesh324:
[MENTION=539770]tilaksidduram[/MENTION] hi sir

I m a newbie in this but I would like to prapose a fix for secondary rom wifi issue. .. I read in a thread named kexec hardboot patch explained in nexus 7 thread... from what I understood to boot another kernel there is a compatibilty patch for the secondary kernel... have u looked into it... suppose if we are able to boot using the the patched aosp kernel maybe we can use compatible wifi drivers... u can create a anyrom patch like agni kernel for cm roms ... I m not asking anything just give this a shot

also I flashed latest multirom version in which u mentioned that touch was fixed but unfortunately It doesn't seem to work for me

thank u
[Galaxy Note II Original Android Development] tilaksidduram:
i will look into it. as per the Multirom developer, the secondary roms does not need any kexec patch at all, it works like a normal rom.

if i flash the CM/PA/AOSP stock kernel on the secondary rom it wifi works, but this same kernel is not compatiable with some of the other custom AOSP roms like OMNI, SLIM, Carbon. the reason is they have added some more extra custamization in their kernel. The best way is to have a seperate kernel for all of these customer ROMS, so when any of these are installed as a seconday rom, just flash the respective kernel after the ROM is flashed and wifi starts to works again. I have already tested it and it works fine for me at least on PA and CM as the kernel source that iam using are the same for these two roms.

Regarding the touch screen issue, i have updated the 2nd post with the new file. download it from there. i have tested it and it now works in touchwiz roms too.
[Galaxy Note II Original Android Development] ParanoidNote:
First of all thanks tilaksidduram for multi rom, it is one of the best mods for android and works fine for me, the roms which i flashed boots but doesn't load theirs kernels only the main with kexec hardboot patch. I missed something or what?
[Galaxy Note II Original Android Development] shujanster:
Now Touch Is Wrking...

I confirm that touch is working. Big thanks to [MENTION=539770]tilaksidduram[/MENTION].
[Galaxy Note II Original Android Development] M!shr@ji:
How can we make the secondary ROMs to use their own kernel [MENTION=539770]tilaksidduram[/MENTION]. It's also mentioned in your Q&A but I can't find it while secondary installation. Flashing a separate kernel shouldn't be an issue at all if our WiFi works :) About touch, just downloaded new zip, 'll report back.

Edit: Working like a charm. Thank you Sir! :)
[Galaxy Note II Original Android Development] kbhuvi:
Hi mate [MENTION=539770]tilaksidduram[/MENTION]

i am trying to install a debloated tw rom as secondary. Same base as primary. Initially it says the size of rom is large and the zip is being modified. The new zip can only be used in multi rom now.

it gets installed to internal storage but does not boot. Just get a black screen

If force reboot, it again enters the rom selection screen. if i remove boot image, the same blank screen.

i flashed the agni kernel zip with blobs after going into multirom option and then choosing the sec rom and then flashed the zip.

instead of blank screen i get the samsung logo and it bootloops.

on going into the multirom folder and navigating to the roms folder, it is seen that the cache folder of the tw rom is empty. In other roms there are some folders such as dalvik cron backup recovery etc.

Does multirom has size limitation for secondary roms. Is my tw secondary rom being truncated because of it. Kindly guide me how to go about it. The debloated tw rom that i am trying to install is less than 600 mb. Primary rom is tw debloated and apace being uaed is 528 mb by the system. I have around 7 gb available in internal memory. Regards
[Galaxy Note II Original Android Development] smeet.somaiya:
[MENTION=539770]tilaksidduram[/MENTION] Touch Inputs are now working . And as u mentioned I tried to flash respective aosp kernel on my secondary rom which is vanir. But when i boot into vanir I have black screen. Similar to the one which we get before flashing gpu drivers blobs on tw roms.

So i tried to flash blobs on secondary rom. But still i am getting black screen. Can u suggest some fix for it?
[Galaxy Note II Original Android Development] M!shr@ji:
Did you delete boot.img after installing the secondary ROM kernel? I flashed AGNi for my secondary CM11 and it booted just fine.
[Galaxy Note II Original Android Development] yogesh324:
[MENTION=539770]tilaksidduram[/MENTION] here is the link to that thread I was talkin about http://xdaforums.com/showthread.php?t=2104706
[Galaxy Note II Original Android Development] kbhuvi:
How to flash kernel for secondary rom. After removing boot.img or directly after flashing secondary rom without removing boot.img.
[Galaxy Note II Original Android Development] M!shr@ji:
You can do it either way but remember to delete boot.img after flashing. But I think secondary kernel doesn't matter as wifi is still not working. So don't bother yourself unless some working wifi is reported. :D

---------- Post added at 02:39 PM ---------- Previous post was at 02:29 PM ----------

I think that is some important info [MENTION=539770]tilaksidduram[/MENTION]. Here is the portion that must have your attention.

Another difference is that both kernels must be patched. The "host" kernel requires a full patch, the one which is being kexecd' requires only two small compatibility patches.

To sumarize the process:

kexec --load-hardboot.... is called and kernel it loaded into RAM.

kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.

After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.

Kexecd' kernel starts and boots.

I'm sorry if copy pasting from another thread is forbidden.
[Galaxy Note II Original Android Development] sumer1:
So can this be used on the 1317M? I'm asking because we can flash there roms.

Cheers
[Galaxy Note II Original Android Development] MBariya:
No.
[Galaxy Note II Original Android Development] saulotas:
So just to clarify, I cannot have Omnirom as primary (dont have a kernel) and Stock rom as secondary (not supported).

Am I right?
[Galaxy Note II Original Android Development] dream_catcher79:
Hi guys,

I am facing a problem now. Twrp is saying my device is called t03g and dont let me install anything now. It shows a message saying my device isnt anyone compatíble.

Anyone can help me?
[Galaxy Note II Original Android Development] jlmancuso:
[MENTION=539770]tilaksidduram[/MENTION] I am working on making this compatible with the l900 (sprint note 2). So far I have everything working except the kernel. I tried compiling your smdk4412 kernel source but it errors out with /mm/migrate.c:228:2 implicit declaration of function '__migration_entry_wait' got any hints on how to fix this?
[Galaxy Note II Original Android Development] dream_catcher79:
[MENTION=539770]tilaksidduram[/MENTION]

Just to let you know that TWRP has been updated 2.0.8.1 that fixes some important bugs that some users was having.
[Galaxy Note II Original Android Development] kbhuvi:
You can have aosp as primary rom by flashing the kernel in the op but your secondary rom also has to be aosp. Tw as secondary roms are not supported ATM

---------- Post added at 04:41 AM ---------- Previous post was at 04:33 AM ----------

What rom are you using. In some custom roms, the developer has changed the name of device to make it compatible with samsung gear or to get updates for apps of other devices ported to n7100. Verify the name of your device by going through build.prop in system folder using a root explorer.
[Galaxy Note II Original Android Development] saulotas:
Omnirom is not working with the AOSP kernel provided in the post, at least in my case.

Actually the only reason I want TW is the HDMI out

---------- Post added at 01:14 PM ---------- Previous post was at 01:14 PM ----------

Omnirom is not working with the AOSP kernel provided in the post, at least in my case.

Actually the only reason I want TW is the HDMI out
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] black05x5:
I've been trying different settings but was hoping other users might share what settings they use on their Note 3s? In Gravity Box is states the brightness range is from 1-255. I'm unclear what the range is for Lux max though.

Not sure if it's the same on all ROMS. I'm running Jasmine and there are 7 levels that can be set using Gravity Box auto brightness. Any feedback would be appreciated, thanks..
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] black05x5:
Just realized I posted this on wrong section. Can a moderator pls move this post?
[Windows Mobile Development and Hacking General] vvv121:
I know I have to use the privileged HTC certificates, but let's imagine I do have them and created the .NBH file. How do I sign it???