Develop Bugs

[ROM] Darchdroid For Hero v1.1 | CyanogenMod, JIT, Fast!

Hey guys, it looked like you guys didn't have a real up to date aosp/cyanogenmod rom, so i decided to take my build and port it over for you guys. This is built from the latest cyanogenmod sources and whatnot. everything should work as fine as any other aosp rom. I Don't have a GSM hero, so you guys gotta tell me how this goes, and what needs fixing.
Thanks Cyanogen for the source to work off of, and experience for showing me how easy it is to port roms to other phones
Standard Order to flash this rom is first the Full Rom, then The Google bits. You only need to wipe if you are coming from a non cyanogenmod rom
HOW TO REPORT BUGS OR PROBLEMS? | kanged from cyanogen's guidelines for bugreporting, lol
- Was it a hard reboot? Get me the file "/proc/last_kmsg". adb pull /proc/last_kmsg
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output. Pastebin links preferred
- Please use the the bugreporter whenever possible!
well, here you guys go
Stable Darchdroid ROM
MD5SUM: c73584f2a52762b62f8e1a2acb26e5d6
Google Bits Flash these for the market app and other google proprietary stuff
MD5SUM: eee5a0de29831f913b2a40efa4df69ec
CHANGELOG
v1.1 - fixed youtube, gps, akmd issues, wifi, plus other additions made by cyanogen (check his github)

downloading now.
Will be interesting to see how it differs from VanillaEclair and aHero.

GSM
Is the rom directly ported from a non gsm hero, because is so wouldnt flashing this rom onto our GSM heros brick or cause problems with our hero? Any feedback from some1 who has flashed, or dev will be great

bratfink said:
Is the rom directly ported from a non gsm hero, because is so wouldnt flashing this rom onto our GSM heros brick or cause problems with our hero? Any feedback from some1 who has flashed, or dev will be great
Click to expand...
Click to collapse
no it wouldn't. flashing a cdma hero radio (most of the time) would, but flashing a rom would never ever brick your phone.
And really, why would someone ever release anything with the possibility of bricking your phone, eh?

darchstar said:
no it wouldn't. flashing a cdma hero radio (most of the time) would, but flashing a rom would never ever brick your phone.
Click to expand...
Click to collapse
Did you do something special with this rom? Cause it look interesting, but i don't think its gonna work without adjustments for HERO GSM.
Hope to see some progress with this rom. Thanks for sharing.

Flashing it now.
I will be running a logcat while booting, just to see if anything interesting turns up.

don't show to much gratitude
bratfink said:
Is the rom directly ported from a non gsm hero, because is so wouldnt flashing this rom onto our GSM heros brick or cause problems with our hero? Any feedback from some1 who has flashed, or dev will be great
Click to expand...
Click to collapse
you even know how to flash a update.zip?

CDMA
So if we could flash CDMA roms then why dont we grab the 2.1 roms off the cdma thread that are generally a step ahead in development than the roms we GSM owners have, unless they didnt work on our phones :S?

Pagan said:
Did you do something special with this rom? Cause it look interesting, but i don't think its gonna work without adjustments for HERO GSM.
Hope to see some progress with this rom. Thanks for sharing.
Click to expand...
Click to collapse
I made the adjustments necessary to get it to run on a gsm hero, such as i changed the kernel... but i don't think i edited the base when packing the boot.img, if that matters. I edited the build.prop to point to wcdma, i editeed the sensors libs... though i think i need to port akmd from your guy's hero rom, and i edited the keylayouts to suit hero gsm

Well, I'm at the blue nexus load screen, still going
Nothing odd in the logcat so far

It's booted
Just going through setup.

darchstar said:
I made the adjustments necessary to get it to run on a gsm hero, such as i changed the kernel... but i don't think i edited the base when packing the boot.img, if that matters. I edited the build.prop to point to wcdma, i editeed the sensors libs... though i think i need to port akmd from your guy's hero rom, and i edited the keylayouts to suit hero gsm
Click to expand...
Click to collapse
Flashed now but unable to start wifi.

ok guys, post all the bugs and i'll make one big update.zip to accommodate them all

Launcher2 force closes immediately after setup. :-(
Home is ok though.

just got it up and running, seems nice so far (battery indicator is good).. off to test..

Speed
Could anyone quickly run a neocore (W+w/o sound) and linpack test just to see what results this rom can give.

xanadu said:
Flashed now but unable to start wifi.
Click to expand...
Click to collapse
yup me too..

Wifi isn't working the rest looks good.

Used this wlan drivers before to try n fix wifi and its worked, give it a go worth a try
adb push wlan.ko /sdcard/wlan.ko
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/wlan.ko /system/lib/modules/wlan.ko
reboot

Can't start Wifi.
logcat shows
Cannot open firmware file </system/etc/wifi/Fw1251r1c.bin>: No such file or directory.
I'll try grabbing it from another ROM.
@Darch,
I can post a full logcat somewhere if you need, from first boot until now (still going)

[CWM] Perm. CWM included in Stock boot.img

Hello everybody,
I don't know if this has been done already, but I couln't find it so I thought why not make a version of my own.
Next to WhiteXP i'm also working on a version of CyanogenMOD 7.2, but with a different approach.
In my oppinion before even trying to release something it's important to have a permanent and working version of instead of the stock recovery.
The difference between this phone and many other phones is the fact that the recovery is included in the boot.img file.
My own phone for example, a Samsung Galaxy S Plus, has a seperate standalone recovery.img.
Because I don't own this phone myself I hope another developer can test if this is working properly.
I didn't change the kernel or important boot files other than the recovery itself, so booting into android shouldn't be a problem and remember it's build upon the stock kernel for now.
Here is the downloadable boot.img: http://depositfiles.com/files/90ye57wtm
The kernel should be flashable through the existing CWM which is already posted in the forums with this file:
http://depositfiles.com/files/e21qacxo9
Hopefully somebody is willing to give me some feedback.
Greetings PsychoGame

Hello
Here I am again with a little update.
This version doesn't seem to work okay, it gets into a bootloop.
I will try to fix these problems at a later time.
Greetings
Psycho Game

Thanks...for your work merge CWM into stock kernel...:thumbup:
Sent from my GT-S5360 using xda app-developers app

Here's a little update of the work i'm doing right now.
As I already said I'm also working on a version of CyanogenMod myself.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y at first, but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the make file of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary [status: complete]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: WIP]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. [Status: Planned]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Greetings
Psycho Game

[ROM][Unofficial/Experimental][Android 4.3] CyanogenMod 10.2 for SGS4A (int'l)

-------------------------Warning!-------------------------------------
This ROM is for SGS4A (int'l) ONLY. Does not work on SGS4 from AT&T as it has a locked bootloader.
Please refer to this thread for a bounty on the bootloader.
-------------------------Please note---------------------------------
This is an experimental build of CyanogenMod 10.2 running Android 4.3.
Meaning there's a couple of known issues with the camera. It is my hope these will be sorted out over time.
If anyone has any interest in helping out, please PM me. Or simply fork the code if you want.
-------------------------Instructions---------------------------------
Install CWM recovery from here.
Download most recent ROM from here.
Download most recent Google Applications for Android 4.3 from here.
Boot into recovery by holding the Volume Up button as the phone is booting.
Back up your current ROM inside CWM recovery.
Flash CyanogenMod ROM to your device using CWM recovery.
Flash Google Applications to your device using CWM recovery.
Do a wipe data/factory reset from within CWM recovery.
Reboot system
---------------------------Known issues-----------------------------
Several camera functions such as HDR don't work.
---------------------------Build from source------------------------
Please consult this guide for setting up CyanogenMod for compile.
Please use
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
when you initialize the CyanogenMod repository so you get the source for CM-10.2.
Download roomservice.xml (see below) and put in ~/android/system/.repo/local_manifests/.
Run 'repo sync' and compile with 'brunch jactiveltexx'. You can get the proprietary files from the ROM.
As always, I take no responsibility in case your phone blows up.
And thanks to the CM team for all their hard work.

Downloads
---------------------------CM-10.2 ROM (Android 4.3) -------------------
---------------------------cm-10.2-20130917-----------------------------------
CyanogenMod 10.2 - 20130917
CyanogenMod 10.2 - 20130917 (mirror - thanks to mrvovven)
---------------------------cm-10.2-20130910-----------------------------------
CyanogenMod 10.2 - 20130910
CyanogenMod 10.2 - 20130910 (mirror - thanks to mrvovven)
---------------------------CM-10.1 ROM (Android 4.2.2) ----------------
CyanogenMod 10.1 - 20130810
----------------------------Google apps -------------------------------
Download the official Google apps. Need to download this in order to have apps like Google Play.
For CM-10.1 choose Android 4.2 apps.
For CM-10.2 choose Android 4.3 apps.
http://goo.im/gapps
------------------------------------- KERNELS ---------------------------------
- SGS4A android 4.2.2 kernel for CM10.1
https://www.dropbox.com/s/oo1hr2n6evp3zu9/sgs4a-cm10-1kernel.zip

----------------------- Changelog--------------------
-------CyanogenMod 10.2 - 20130917----------
- Fixed video preview resolution
- Disabled zsl for slightly more stable camera app.
-------CyanogenMod 10.2 - 20130910----------
- Updated kernel to most recent version of cm-10.2 for SGS4.
- Replaced all sensor drivers with SGS4A kernel sources.
- Replaced several camera blobs in /system/lib/* with SGS4A versions enabling basic camera functionality.
-------CyanogenMod 10.1 - 20130810----------
Initial build.

Good job.
Sent from my Nexus 7 using Tapatalk 4

hello
anyone tried this out ?
feedbacks ?
thanks in advance

pdf5 said:
hello
anyone tried this out ?
feedbacks ?
thanks in advance
Click to expand...
Click to collapse
This is not something you should install unless you want to be compiling and debugging yourself. It's far from usable as day to day rom. I hope I'm clear on that.

Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help

LeJay said:
Fixed wifi and a number of small issues. Should be a lot more stable. Seems the main remaining issue is, not surprisingly, the camera. If anyone knows how the entire camera driver setup is supposed to work in android, I'd love some help
Click to expand...
Click to collapse
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.

aurelm said:
Call it just a hunch. But have you tried the camera drivers from the s3 ? I would say that it's basically the same camera and has been added in s4 active because after 1 year it became very cheap to continue manufacturing and this way compensate for the more expensive case and water proofing.
Click to expand...
Click to collapse
Honestly, not exactly sure how the setup is. I assume it's mostly in some proprietary libs separate from the kernel, but it's hard to find good information on it.
Sent from my GT-I9295 using xda premium

Thank you for you work!!
But search another File hoster!! DropBox close your account if the trafic is to big!!

So S4 Active Original is the intl i9295 ?
EDIT: oh ok the real dev thread
Sent from my GT-I9295 using xda app-developers app

I've a MicroSD in my SGS4A and i can't choose the external_sd in the CM File Explorer.
Is there any solution?
For example creating symlink or mounting in /sdcard
I've never tried anything of that!

It's working really well Wifi works yay, well done! Hopefully you can get the camera working too.

Building from source
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.

snadge said:
Hi,
I'm happy to see such great progress already, and am only diving in to this because I'd like to be able to lend a hand in any way I can.
Is it too soon to be asking questions about how to build for 10.2? I'm having a go at it right now, and if I use Lejay's kernel and device configuration (jactivelte), the kernel fails to compile, something about BUG_ON rcu error, I can come back to that if its relevant. So I tried Epsylon3's suggestion to use tpruvot's kernel and device config. This builds a rom, but black screen, can't see anything or get into adb. If I flash Lejay's kernel over the top of my 10.2 build, it boots. Phone (dialer) keeps force closing in a loop, which is annoying, but asides from that it seems to boot.
Keep up the good work, can't wait to get some 10.2 love.
Click to expand...
Click to collapse
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.

Are you going to try to make CM 10.2?

LeJay said:
Comparing the 9295 and 9505 kernels, there's quite a lot of differences. Cyanogenmod tried to merge the two, but apparently gave up. The question is really if we should start with the 9505 and add the camera or start with the 9295 and make it compatible for CM. The stuff i uploaded here is a port of the 9505 kernel, but now I'm looking into starting out with the 9295 kernel instead.
The problem with 10.2 is of course there's no released 9295 kernel for android 4.3. I'm guessing there are not that many differences, so it might not be too hard.
I think I'm getting the same compile error you were with 10.2. Not sure what it means.
Click to expand...
Click to collapse
I had a chat with noobnl about it, and he pointed out a patch on gerrit: http://review.cyanogenmod.org/#/c/44552/
I spent hours manually merging it with cm jf kernel, to finally end up with a kernel that gives me. You guessed it, a black screen. After investing about a days worth of effort into it, I ended up with a buggy unstable CM10.2 build, that will boot if I flash LeJay's kernel zip, but its unuseable. It's going to take some serious effort to come up with a functioning CM10.2 kernel for the International S4 Active. In the meantime, a CM10.1 build with a non functioning camera, is still way better than the stock TouchWiz rom, so I'm happy. :laugh:

Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.

snadge said:
Ok, I got bored and had another play around with 10.2 and the CM jf kernel. With the black screen problem, if you power the device down, then boot into recovery (power + vol up), you can adb pull /proc/last_kmsg and it tells an interesting story. It looks like the init scripts are totally borked. init.qcom.rc and init.carrier.rc are completely missing. I tried simply copying them into the root, but it looks like its a bit more complicated than that. The problem is clear that it is unable to mount /system for whatever reason, because it can't find /system/bin/sysinit, then pretty much gives up after that.
This looks like a pretty simple problem for a relatively experienced device maintainer, or rom kernel dev to be able to fix. It would be nice if we could get some more developer attention for this device.
Click to expand...
Click to collapse
You probably forgot to add jactivelte to the list at the bottom of device/jf-common/Android.mk. I didn't want to fork their repo just to add one word on a line, so you have to do this manually. It's probably also a good idea to extract rom files from a cm.10.2 rom for something like jfltexx.

LeJolly said:
Are you going to try to make CM 10.2?
Click to expand...
Click to collapse
I have cm10.2 running. The problem is really the camera.

[Q] SELinux custom kernel for SM-T900 (pro 12.2)

Hi,
I've successfully rooted my UK galaxy tab pro 12.2 SM-T900 (using a P900 img as the T900 one bricked it), I'd like to try running linux via chroot but I think I need a custom kernel to set SELinux to permissive.
Since there don't seem to be any in existence I think I need to build one from source as described here (I can't post links):
graemehill.ca/compiling-permissive-android-kernel/
The build # on my device is T900XXUANI1
however on the Samsung open source site this particular version is not listed.
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=T900
I'm not sure if they're supposed to be the same thing - Should these versions match? Will I break something if I download the source for T900XXUANB5 and compile that or is that the right version to download?
Thanks

RealZogger said:
Hi,
I've successfully rooted my UK galaxy tab pro 12.2 SM-T900 (using a P900 img as the T900 one bricked it), I'd like to try running linux via chroot but I think I need a custom kernel to set SELinux to permissive.
Since there don't seem to be any in existence I think I need to build one from source as described here (I can't post links):
graemehill.ca/compiling-permissive-android-kernel/
The build # on my device is T900XXUANI1
however on the Samsung open source site this particular version is not listed.
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=T900
I'm not sure if they're supposed to be the same thing - Should these versions match? Will I break something if I download the source for T900XXUANB5 and compile that or is that the right version to download?
Thanks
Click to expand...
Click to collapse
You can use bonuzzz's Custom PRO-VTFB. But if you really want to create your own, you can use the B5 kernel. However, that kernel has been followed by two firmware upgrades.

Thanks, so there's no problem using the p900 kernel on the t900? It's not something I've ever done before and I don't really know how much difference there is between various kernels

RealZogger said:
Thanks, so there's no problem using the p900 kernel on the t900? It's not something I've ever done before and I don't really know how much difference there is between various kernels
Click to expand...
Click to collapse
You might loose the automatic screen rotation, but that's the only difference. I use it as an alternative to cm-11, together with bonuzzz's Custom ROM 1.01 the most debloated TW ROM available. There is also a cm-11 kernel with enabled VT, but same thing here you will most likely loose the auto rotation.

If anyone is interested, i sent a request to samsung via their open source website on the day I posted this thread, asking for the XXUANI1 source. Got an email back today to say it's now available on the website. I haven't tried doing anything with it yet though!

WorkAround: MultiRom + Kernel Panic on Secondary Rom

Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.

Thank you for this. I have been flashing RIN kernel after any cm12 I've installed since installing MultiROM. Seems to work too, but the hour long wait to flash a 7mb kernel really bugs me.
Next time I flash a cm12 as secondary I'll give this a go.

Eliminater74 said:
Not sure if im posting in correct area,
If Posted in wrong area, my Bad..
Ever since MultiRom come out for D851, People have been experiencing Kernel panics with the latest updates from the CM Sources. (Not everyone, But Most)
The method I used below has worked with no problems with me. I cant say it will work with everyone. But it worked for me..
I know installing a Full Kernel ZIP file on secondary rom can either take 45 mins or longer, or not even work at all. (My Experience.)
But the method listed below, only took 5 secs and worked perfectly..
Now I just wanted to post a work around for the people that are experiencing Kernel Panics when using MultiRom..
Example: you install CM-12 as a secondary rom, Reboot and it crashes with Kernel Panic,
Work around: This awesome Kernel: Optimized SM-4.9.3 Kernel V2.2 for D855/D851/D850/LS990 http://forum.xda-developers.com/lg-g3/development/kernel-optimized-sm-4-9-3-kernel-t2976049
Take that kernel and unzip file. Then in Multi rom settings in TWRP-MultiRom goto list roms.. Pick the Rom with the kernel panic and Then remove Boot image..
click on the add boot image now.. and then goto the unziped kernel from above, Find the boot.img and click on it.. it will add it.. takes only a few secs.
Reboot.. Kernel panic is now gone..... (Becides, that Kernel works great)..
Note: that above example is for Lollipop only.. I havent tested it with any other kernels.. Most kernels that I unziped had that bump stuff listed for the locked bootloaders.
and no correctly listed boot.img So.. it wouldnt work...
You can also Make a Backup of your current working boot image and then flash that into it, Havent testing it like that, but should work the same.
The other work around I heard posted is:
Install to primary ROM then move to secondary rom.
Click to expand...
Click to collapse
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.

aclegg2011 said:
Or you can try the tootsie-pop test kernel. I implemented the multirom patch into it tonight. If everything works fine it'll be been bumped into the stable kernel and be included with bliss pop and Resurrection remix ROMs.
Click to expand...
Click to collapse
Yes from what I have tested it works with any Compatible flashable Kernel that unzips and has a boot.img..
The above kernel that I listed on post #1 is Stable but is overclockable, If you dont want that.. Then dont use that one, It was only listed as an Example.
I use that kernel with no problems.. I dont OC my phone, but its nice to have the option to do so.
Ill test out the tootie-pop kernel the next time I feel like messing with my phone.
Now isnt a good time, Im sick, and I have already messed up my linux system and my windows system (windows 10 Enterprise build 9926).. Had to do a fresh install on windows.. my linux doesnt want to let me mount my own drives in gnome.. Says I dont have access do to some error, But I am running Ubuntu Vivid 15.04.. so thats to be expected..
So touching my phone isnt a good idea right now.. I might just end up blowing it up the way my luck is going.

Thanks to the OP. This was a quick and simple fix to a frustrating issue.
Sent from my LG-D851

After doing a little research, and finding out that the MultiRom is pretty much dead. I decided to delete it all together and stick with the one rom that seemed
very stable and likable for me. I wont say what rom that was as to respect all developers on this forum.. So I stopped all testing and experiments dealing with MultiRom..
If the Developer once again decides to post updates and fixes. I will again. try it.. but for now.. I will no longer post any workarounds or help with this MultiRom section anymore...
As you know that thread was closed in the ROM Development section..