Develop Bugs

[KERNEL]DualBoot - Devil4.2 (04-Feb-2013)

Attention! Before installing this kernel, read carefully (don't forget reading post 2!)!
1.) Make a Nandroid!
2.) If you are installing this kernel the first time, it wipes your data and system! (this is caused by creating the secondary system partition) - you can restore your nandroid afterwards
3.) Make sure to have 700 mb free space at your internal sdcard (this is needed for secondary data)
4.) You can't install a rom as secondary rom, without doing some work yourself! This is caused by the way, rom installing is mounting the system partition. I can't do anything against it (What you need to do is written in the guide of post 2)
5.) You only can install 4.2.1 roms, with the "default"/cm partition layout!
6.) You have to install the kernel again, after you have installed a new rom. If you forget to install it, you just boot up to primary rom.
Many thanks to:
- cm team, especially pawitp
- stratosk
- mialwe
- zachariasmaladroid
- kasper_h
- krarvind
- kufikugel
- gokhanmoral (great idea to build a dualboot kernel, always helpful)
- Bejda
- sUsH667 ( i have taken his design for aroma filemanager, it's looking great)
- amarullz ( who coded the filemanager)
- ...

About this kernel (and installing it):
installing a dualboot kernel the first time:
1.) the kernel needs to create a secondary system partiton. this is taking place at the current /data partition.
b) the new version (04-Feb.) is creating an addional "devil" partition of 20 mb. it currently isn't used, but i am preparing already for later (boot.img is limited to 7.5 mb in size because of the boot partition size), because the dualboot kernel needs to include more files as the stock one, and for 4.1.2 support, i even need to include more...
2.) by installing the kernel the first time, data and system get deleted due to the partition change.
3.) as a security feature, the install fails the first time, before your data gets formated. if your install fails, you still can make a nandroid, if you didn't before. then just install again. this time the install does not fail. the kernel reboots to recovery automatically now
4.) install the kernel a third time
5.) before installing a new rom, go to advancend, reboot recovery
6.) after installing a rom (primary or secondary), flash the kernel again, follow the steps below for this!
updating the dual boot kernel to a newer version/installing the kernel after a rom flash:
1.) flash the kernel
2.) reboot to recovery (just in case...)
how to revert the partition changes:
there also is a "revert" kernel now, which is available here:
http://rootaxbox.no-ip.org/derteufel/jellybean4.2.x/
if one isn't using the dualboot kernel, the "revert" kernel doesn't revert anything, but is a normal single boot kernel, with the same features as the dualboot one.
if one is flashing reset kernel after dualboot, you need to flash it three times. the first install just fails. the second one succeds and reboots to recovery. the third one finishes the restore.
The reset kernel wipes data and system, (only) if coming from dualboot kernel!
in the recovery:
1.) by default, there is no entry for system and data in the fstab. i have done this, to ensure you don't install apps/packages to the wrong rom. this means, if you just go to install zip, install fails, because there is no system partition which can be mounted.
2.) the dualboot menu. what do these options do?
a) the first two options are mounting primary/secondary filesystem right after clicking.
b) these two options are preparing for mounting primary/secondary filesystem after you reboot to recovery. without using this, you don't have the options in recovery, to mount/format data or system, etc
3.) reboot primary/secondary system should be clear
how to install a rom as primary/secondary rom:
1a ) remove spaces from filename!
1b )install zip from sdcard
2.) choose from where to install
3.) choose what and where to install
note: the kernel installs itself after the rom. no need to reflash. this does not work with elite rom (because of the zip design)
How to create/restore a nandroid:
1.) go to dual boot menu
2.) select "enable mounting of pri. fs" or select "enable mounting of sec. fs"
3.) reboot to recovery
4.) backup or restore your nandroid, depending on your previous choise, you'll backup/restore the primary or secondary system
5.) consider to rename your backup, to something like primary_date or secondary_date
here you get the kernel. nothing else needed:
http://rootaxbox.no-ip.org/derteufel/dualboot/

Going to try it out
Enviado desde mi GT-I9000 usando Tapatalk 2

Where is the link
Sent from my GT-I9000 using xda premium

WOW great work derteufel
thanks a lot

WOW... Just wow!

almost all files uploaded/added now
a dualboot version of hellybean is currently uploading

thanks dev :good:
will give it a try ! ...

will you compile a kernel without dualboot for JB4.2.1???
Gesendet von meinem GT-I9000 mit Tapatalk 2

Awesome. Cant wait to try this. I remember a long time ago i mentioned it in your kernel thread.
Still following your work actually, but got stuck on CM all this time. Now can be on both! Nice.
So how does one boot into 1st or 2nd rom? By button combo? Dont see it mentioned.
Considering second donation :thumbup:

WOW WOW WOW WOW !!! DUAL BOOT ON OUR GALAXY S!!! FANTASTIC!!!! someone tested it???
sorry for my bad english

jelle2503 said:
Awesome. Cant wait to try this. I remember a long time ago i mentioned it in your kernel thread.
Still following your work actually, but got stuck on CM all this time. Now can be on both! Nice.
So how does one boot into 1st or 2nd rom? By button combo? Dont see it mentioned.
Considering second donation :thumbup:
Click to expand...
Click to collapse
Also, when do we need to flash the kernel again? When we install the main rom, or every time when we install a rom, even if its primary or secondary.

I am scared
Sent from my GT-I9000 using XDA Premium HD app

Perfect timing and choices DerTeufel,that guy:
DerTeufel1980 said:
- sUsH667 ( i have taken his design for aroma filemanager, it's looking great)
Click to expand...
Click to collapse
Keeps telling me i have to test Slim beta 2

Trak-X said:
Also, when do we need to flash the kernel again? When we install the main rom, or every time when we install a rom, even if its primary or secondary.
Click to expand...
Click to collapse
you have to flash the kernel everytime you install a rom, because every rom flashes a kernel. as this is implemented in the rom update script, i can't avoid it.

Terrible.... I am without voice!

There is no need to edit the primary ROM, is it?
Sent from my GT-I9000 using Tapatalk 2

So i flashed Dual Kernel (2 times as expected,error 7 first).
Advanced>reboot recovery> dual boot menu and all is here.
I mount secondary filesystem and flash the edited Slim beta2.
Reflash the dual kernel but it only boot in recovery.
If i don't flash dual kernel after Slim install it is stuck at semaphore boot image.
I have 1g free on sd,don't know what i'm missing,i think i'll download again edited slim beta2..don't know but its install seems too fast in cwm (i know it's Slim but hey,it's fast lol).

I love you DerTeufel.
Good Job.
Amazing<3
Gesendet von meinem GT-I9000 mit Tapatalk 2

Bejda said:
So i flashed Dual Kernel (2 times as expected,error 7 first).
Advanced>reboot recovery> dual boot menu and all is here.
I mount secondary filesystem and flash the edited Slim beta2.
Reflash the dual kernel but it only boot in recovery.
If i don't flash dual kernel after Slim install it is stuck at semaphore boot image.
I have 1g free on sd,don't know what i'm missing,i think i'll download again edited slim beta2..don't know but its install seems too fast in cwm (i know it's Slim but hey,it's fast lol).
Click to expand...
Click to collapse
This should not happen. Could you please flash the kernel a third time.
If the install fails like it does the first time, secondary system did not get created
Gesendet von meinem GT-I9000 mit Tapatalk 2

CM 11 4.4 kitkat issue

I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?

mr. ya-di-da said:
I'm using cm9 that has the team win recovery. When I try to flash the cm 11 kitkat rom it says fail. Do i need to use a cwm recovery or is the download link bad ?
Click to expand...
Click to collapse
Flash it from cwm... but after the flash completes, reboot recovery and do you're wipes ( again ) and flash kitkat from it's recovery. Then reboot.
Let it chill for a few minutes, then boot back to recovery and flash you're 4.4 gapps.
This process always worked for me on 4.3 and I'm assuming it will work on 4.4. But I've not flashed 4.4 yet. So proceed with caution.
Good luck...

I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?

mr. ya-di-da said:
I will try it when I get home from work so I can use Odin to flash a cwm recovery. Everytime I use mobile Odin to flash a recovery it bricks my phone ....why does that happen ?
Click to expand...
Click to collapse
I'm not sure about the mobile Odin issue... are you making sure the tar file for the kernel is a good download and that it is compatible with the Android version and rom you're trying to run...?
Try downloading the Directboot EL29 kernel from rwilco12's repo.. ( make sure you get the Directboot EL29 kernel and not the stock el29 kernel )
After you have it and the rom you want on you're sdcard... use mobile Odin to flash the el29 db kernel.. it should boot to recovery on it's own..
Push volume up, volume down, volume up... this enables the power button as the select button...
Do you're wipes... and flash 4.4...reboot recovery... do wipes.. ( data, cache, dalvik, and format system )...flash 4.4 again.. reboot.. settle in for a few minutes and then boot recovery and flash gapps 4.4...reboot.
Let me know how it goes... I'll stick around tonight until we get ya up and running...

It failed.. (status 7)

mr. ya-di-da said:
It failed.. (status 7)
Click to expand...
Click to collapse
Ok... I'll try to get to it tomorrow... but Thursday at the latest.

OK thx. I saw that other people where getting the same fail (status 7) let me know what u find.

Status 7 is a syntax error in the updater script... Probably missing a semicolon or something silly like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Not related to this issue, unsure if it would be better etiquette to make my own thread for this, but an issue I'm having with dastins CM11 ROM (12-04-13 version) is that I have two "Internal Storages" instead of one (I do not own/use a SD card)
On CM10/10.1/10.2 I had one internal storage, but on CM11 I have a 2GB internal storage and then a second internal storage (that things seem to not be installed to at all) with the remainder of my devices space.
One of the applications I used a lot on stock TouchWiz and earlier versions of CM is larger than two gigs, so on CM11 I can't even install it because it says I have insufficient storage. Is there a way I can combine the two internal storages into one, so it functions like it did on CM10.2 so I can use all of my devices space instead of only 2GB?
---------
Another question, and this one I'm probably just being blind and not seeing it, or maybe this setting is in a different location in KitKat, is my phone is set to USB mass storage instead of MTP. Normally I head over to Settings > Storage > hit the menu key and change USB connection type to MTP, but the menu key doesn't seem to do anything anymore on the Storage page. Where would I change to MTP instead of Mass Storage, or how can I just disable Mass Storage, I honestly don't care about being able to get any files on/off the device, but 90% of the time I'm charging on USB and I just don't want a full screen prompt showing up every time I touch my phone saying "Hey! It's Plugged In! Do you want to turn USB Storage on?"

You need to flash cm11 with the newest cwm... The old regular way of the"safe" recovery doesnt work... The easy way Is to download the blasphemy kernel and install it then boot back into recovery... It will be cwm 6.0.4.5... Flash the rom with this and no status 7...
Hope this helps...
Sent from my SPH-D710 using Tapatalk 2

I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.

kitkat 4.4.1
I rooted my device using rwilcos fl24 method although I was on a fd24 model. After root I flashed a custom recovery using Odin I believe it was agats...I then proceeded to flash a ROM cm10.1 then upgraded to cm 10.2. Now running KitKat 4.4.1 12/7 edition I believe and works like a charm...thought I had a battery problem because it wouldn't charge right it would take forever. I didn't I jus had to stop oc/uv ...BTW using the kernel that came with the rom flashed using cwm recovery from cm10 which was on jb not ICS and works fine little bugs here and there such as attempting to open incognito window fc browser the battery read when phone was off was inconsistent versus when the device is off but other then that KitKat is great if I can help anyone I'll be more then glad to I don't mind helping people that don't know I don't give attitude and noon user friendly,after all I was there once....besides all the guys who really know what thier doing are busy creating Roma and tweakimg programs to keep us happy let's make it a little easier on them like I said I don't know everything but I have some knowledge and if I'm able to point you in the right direction without wasting your time I will

easyrider77 said:
I have an EL29 direct boot zip file that works with agats and even the newer cwms to flash back to.
I've tested it on the following recoveries and not had an issue at all:
agats (both 1.3 and 1.4), stock twiz, and the latest CWM they are useing.
I have gone to el29 direct boot with all of the above and had no issues, it goes into el29 recovery just fine.
DO keep in mind though I made this zip mainly for flashing into roms, not as a stand alone kernel, so you may have issues wif you use this as your standard go to kernel with the rom. Mst roms already have thier own kernel anyways, so that's normally not an issue, jsut so you are aware this is basically used for flashing roms not as the normal kernel.
I can host it on dev-host if anyone is interested, otherwise I won't bother.....and I ask because sometimes people just don't wanna be bothered, so I always ask......anyways let me know I will host it.
Just as a side note the steps I have done are as follows:
-reboot to recovery
-flash el29 zip file within said recovery (as I said I've tested this on all the above and it works fine)
-reboot recovery (it will be el29 now)
It should be back to the el29 recovery and you can flash from there.
Done this on hood pope (4.3), Viluminati (4.4 and 4.4.1 KitKat), cm10.1 (4.2.2) and stock Twiz rooted (not stock Twiz recovery) but agats recovery 1.3 and 1.4.
Those that don't know how to activate the power button to select what you do is toggle up > down >up > down until it says something about it being activated, you can then just use power to select your option.
Click to expand...
Click to collapse
There's a tread that might use your assistance
Sent from my d710 using XDA Premium 4 mobile app

CM 4.4.1 build 2013-12-07
Hey guys...Been rocking this build for a month now with no real problems. Only a couple of things i have noticed and thought I would drop in and mention since I haven't heard about it talked about in the main thread or here yet.
1. Every once in a while I will be showing full 3g bars and wont connect to the internet (says "no connection") I have fixed this with just toggling off and then back on the Sprint Radio Toggle in the drop down window. The phone will then immediately connect after.
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
SPH-D710 EL26.....flashed to Boost Mobile with working Hangouts MMS and SMS from day one (no fix)
Build; 4.4.1 2013/12/07
Everything else is just ROCK SOLID, and love this ROM.

adjday said:
2. During the first 2 weeks the camcorder was working...now its just borked. Every time i try to use it, it will just freeze up (the camcorder) and then force close. Then the camera is also unresponsive after trying to use the camcorder. I have tried to clear catch and force stop but the only way to fix this is with a reboot.
Click to expand...
Click to collapse
This Camera Fix worked to get my camcorder working perfectly. Have you tried it? http://forum.xda-developers.com/showthread.php?p=48620791&highlight=3a04f599232ee62c6b63a6e4f1d3f7d3#post48620791

You can uninstall the gallery app (using titanium backup)
Then download and install a different Kit Kat gallery app...(just search google, it's everywhere Lol)

[INFO] Recoveries for the Samsung Galaxy Ace II X

Work in Progress
List of Custom Recoveries for the Samsung Galaxy Ace II X
For all things rooting and installing, a custom recovery is often needed. New things are being developed day and night. Thus, I find it necessary for there to be a list of all the recoveries that are compatible with the Samsung Galaxy Ace II X. Some are better than others, though it is a matter of preference. Anyways, commencing the list...
1. ClockworkMod 5.5.0.4 - not my work
ClockworkMod recovery, usually abbreviated as CWM or CWMR, is a custom recovery based off of AOSP source, created by Koushik Dutta (known by the nickname "Koush").
Bugs - Mount USB doesn't work.
Download
2. ClockworkMod 6 - not my work
Bugs - Mount USB doesn't work, "dancing screen," SOME USERS REPORT THAT INSTALLING CWM6 CAUSES THE DEVICE TO BOOT INTO RECOVERY INSTEAD OF THE ROM
Download
3. TeamWin Recovery Project 2.6.3.0 - my work
TeamWin Recovery Project, often abbreviated as TWRP, is a custom recovery that has a fully touch-driven interface. Aside from the uniquity of being 100% touch controlled, it also contains an ubiquity of features. It has a built-in file manager, support for sideloading via ADB, support for backups and restoring backups, a completely theme-able interface, and more sorts of customization.
Bugs - Mount USB doesn't work.
Download
Changelog:
Release 2 - backported some features from TWRP 2.7, fixed color tint issue, implemented internal storage
Release 1 - initial release
4. TeamWin Recovery Project 2.7.1.0 - my work
Download
Bugs - None reported.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
Release 4 - Upgraded to 2.7.1.0 (customized to build on a JB-based tree: removed mouse support via USB OTG, removed text wrap for now), fixed internal storage
Release 3 - Fixed color tint issue
Release 2 - Fixed USB Mass Storage
Release 1 - Initial release *TWRP 2.7.1.0 has some mount issues. Don't use it.
5. TeamWin Recovery Project 2.8.1.1 - by @draekko
Check his post here for details and download links.
This list will be updated regularly as recoveries are updated, new recoveries are built, or for miscellaneous reasons. If there are any bugs I haven't mentioned for any of the recoveries, let me know and I'll add it to the OP.

Nice thread.
keep up the good work.

Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app

CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:

Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
AndroidAssassin said:
Any more recoveries and kernels for ace2x 7560m
Sent from my GT-S7560M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
Seb269 said:
CodeName, you resolve the bug for TWRP 2.6 can you try for CWMR 6 ? :angel:
It's just a question :good:
Click to expand...
Click to collapse
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?

Codename13 said:
Woops, wasn't seeing any notifications because I forgot to suscribe. Anyways...
What do you mean? I can tell you that I am not done with custom recoveries or custom kernels. CM10.2 is just my focus at the moment. Also, this thread is under construction. I don't have time to work on it for awhile.
I've already tried, but I either got build errors or a black screen when I booted into CWM6. I'll try again sometime another day, because I would love to get a nonbuggy CWM6 working. Just a question - is CWM6 different from Philz Touch or are the two a single custom recovery?
Click to expand...
Click to collapse
They are the same.

Bug report (TWRP 2.7.0.0)
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.

gregory678 said:
I have bug report (TWRP 2.7.0.0) - settings are not saving, every time I enter recovery, I have to set everything again. Console says that it can't find something to store the settings if I remember correctly.
Click to expand...
Click to collapse
The latest release? I have no such problem. TWRP is configured so that the settings are stored on the external sdcard. So if you don't have one, your settings won't be saved. I considered setting the cache partition as the TWRP settings storage, but cache is often wiped when installing ROMs and packages. The same with system, data, et cetera. I've considered setting the recovery partition as a settings storage partition; however, whenever a new build of TWRP is installed, the recovery partition will be overwritten. I could try splitting the cache partition up so there is the cache partition and a new 12mb partition, but then there would either be errors when installing firmwares via Odin, or the new settings storage partition would be wiped. Unless you have any better ideas than the sdcard being the settings storage, don't complain. I'm not sure what's causing your issue - perhaps it's because you only insert your sdcard when you boot into TWRP? Enlighten me, and tell me a bit about your device setup (ROM, kernel, size of sdcard, etc).

OMG, I'm such dumb, I just noticed that settings file is hidden. I was wondering why it's always left empty folder after rebooting from recovery mode, now I discovered a hidden settings file in it, I'm Scherlock of the year . Sorry for bothering you, can someone delete these ashaming posts?

Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?

I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Jeremicus said:
Hi Everyone, so I have tried installing a few of these recoveries with Odin. Every time it runs through fine, no errors, but when I restart the device in recovery mode I just get the default stock recovery screen. Has anyone encountered this?
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh then try installing a recovery again and booting into it.

Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk

I was thinking about the advantages of TWRP 2.7 over 2.6. I knew that if I looked in the commit history for 2.7 on Github, I would be bound to find the commits that brought in some of my favorite features of TWRP 2.7.0.0. That, along with I having just discovered that Github commits can be download as patches, will bring the best version of TWRP for us yet. So far, I've successfully backported haptic feedback (along with the settings for it) and a bit more. I've also fixed internal storage in TWRP. I plan to backport the smoother scrolling, USB Mass Storage (it only works in 2.7 at the moment because 2.7 added in a different way to handle and mount UMS. I'll backport the different way of handling and mounting UMS), and add in some other bits of fun. It's going to be really cool, and it really isn't time consuming, so I should be able to bring it to you all very soon.
AndroidAssassin said:
Can someone make a .zip file that has the recoveries .img to be flashed in recovery instead of .tar which needs odin for the ace2x preferably one of TWRP RECOVERIES PLEASE
Sent from my GT-S7560M using Tapatalk
Click to expand...
Click to collapse
Just download Recovery Tools from the Play Store.

It dont have nething for ace2x
Sent from my GT-S7560M using XDA Premium 4 mobile app

Codename13 said:
I'm going to stop working on TWRP 2.7.x because it is designed to be built in KitKat-based ROMs' source trees since I don't work on KitKat. I had several issues trying to restore a backup of stock ROM, because it does not have SELinux support at all. There's a reason why TWRP dropped support for older versions of Android - SELinux. It causes the restore to fail for some reason. Anyways, I'll message one of our device's KitKat-based ROM devs, and I'll find someone who can continue work on TWRP 2.7 for us. I was also having issues compiling it after some major commits that were committed to it, so I really am unable to compile it properly unless I migrate to KitKat, which I won't be doing for awhile. Good news though, I've managed to get internal storage working on TWRP 2.6.3.0!
Click to expand...
Click to collapse
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:

husokal said:
So you suggest 2.6.3.0 instead 2.7.0.0 for stock rom users. Regarding restore issues?
______________________________________________
Thank you for great work.
So far so good. The only Bug-free recovery! :victory:
Click to expand...
Click to collapse
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.

Codename13 said:
Yes, I say to use 2.6.3.0 as a universal recovery for our device. TWRP 2.6.3.0 works for both stock and custom ROMs, it doesn't enforce SELinux, so I say to use it. Plus, I've back ported some little changes from 2.7 to make it even better. Thank you for the praise, but it actually does have some bugs (mount USB storage) which I'll probs try to fix after the summer.
Click to expand...
Click to collapse
Im sorry i dont know much things about SELinux
As i see 2.7.0.0 Forces SELinux which i dont know what can be problem about it.
and 2.6.3.0 Mount Storage not working.
So im using 2.7.0.0 for my stock. Cause i need this function sometimes.
Sorry for noob question but what can be problem about Enforcing SELinux for 4.0.4
Edit:
Got it! : http://forum.xda-developers.com/showpost.php?p=52013947&postcount=5392

There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.

s7560m said:
There's another bug with cwm 6. It shows a warning called warning:no file_contexts, as well as bootlooping into cwm again. This happens when you flash any rom, or restore to a nandroid backup. Please add this bug for future reference, as this can cause low experienced users to brick their devices.
Click to expand...
Click to collapse
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
EDIT - It seems that there's also a new version of TWRP out. It seems to be quite minor, but I'll see if I can port it. It's been bumped up to version 2.7.1.0 now.

Codename13 said:
So is it pretty much unusable? I never actually tested it and I didn't even create it, but a user had told me that it worked fine. I'll post a little warning for CWM6. Anyways, I think that TWRP 2.6.3.0 is the best custom recovery ATM. Of course, there are only 4 custom recoveries that have been built. I actually was going to return to porting some other custom recoveries to our device the other day. I want to port CWM6, Philz Touch, try out a few little hacks, and I want to implement internal storage into TWRP 2.7 just as it is in TWRP 2.6. Also, I think I'm going to try fixing the USB Mounting issue in TWRP 2.6. I know that 2.7 introduced a new, more universal way of handling UMS, so I'm going to see if I can backport it.
Click to expand...
Click to collapse
Definitely twrp is the best! Never had any issues with it whatsoever, and has a great ui. If you could though, it would be awesome to try and port philz touch and cwm touch as well, just in case those who like cwm want that touch feature, or like the theme and features of philz touch . And I really hope the usb mounting issue can be fixed, as it can save so much time, rather than downloading to my computer, transferring to phone external storage, and then booting into recovery. Those who are lazy don't want to do all of that lol. Anyways, keep up all of the good work, and hopefully these bug fixes and new recoveries are implemented in future notice!

[Guide/Development/Info/Discussion][GEE] Multiboot for the Sprint Optimus G!

This was being discussed in the unofficial CM11 thread, So I thought I would give it a home.
Here is the thread for; Development, Discussion, Information, and Also A guide on how to Multiboot different ROMs on the LG optimus G.
Code:
I in no way made this MOD,
all the rights and credit go to the original creators.
I Just wanted to give an area and help other people learn how to do this.
I (Or the Creators of this mod) are NOT responsible for anything bad happening after flashing this MOD;
Bricks, Soft Bricks, Explosions, Implosions, Girlfriend leaving you after trying to boot too many roms.
YOU choose what YOU do to your 700$ Device. Now Lets get to the Guide. :)
Before you do ANYTHING, Be sure to read this over many, many times. If you do NOT know what you are doing, do NOT try this. Enjoy. :good:
This is how I multi boot, using a backup.
1st: To multiboot, please be rooted.
2nd: Please Flash the Custom TWRP Multiboot recovery. (Link Below)
2½ (Optional, but still preferred.): If you plan on multibooting a 4.2+ ROM, I would make an "0" (Zero) folder and moving all precious things there. (So that your backup will go there and you can also see your download folder.)
3rd: Make A backup of whatever ROM you are on in that recovery, and as you will see if you reboot, the backup in be in the "0" directory. (I prefer stock as my ROM to backup.)
4th: Flash the Multiboot.zip (Link Below)
5th: Now Wipe as normal like if you installing another ROM. and Set whatever ROM you want as your primary ROM.
6th: In Recovery, go to advanced> add ROM
7th: click next then choose backup as 2nd ROM.
8th: Let it do its thing, and guess what?
Enjoy Multi booting.
This is how to Multiboot with a .zip. (results may vary)
1st: To multiboot, please be rooted.
2nd: Please Flash the Custom TWRP Multiboot recovery. (Link Below)
2½ (Optional, but still preferred.): If you plan on multibooting a 4.2+ ROM, I would make an "0" (Zero) folder and moving all precious things there. (So that your backup will go there and you can also see your download folder.)
3rd: Make A backup of whatever ROM you are on in that recovery, and as you will see if you reboot, the backup in be in the "0" directory. (I prefer stock as my ROM to backup.)
4th: Flash the Multiboot.zip (Link Below)
5th: Make sure you have primary ROM. You don't need to edit this if you want to keep it
To change primary ROM before adding new ones, wipe as normal and setup/backup etc.
6th: In Recovery, go to advanced> add ROM
7th: click next then choose .zip file of ROM as 2nd ROM.
8th: Let it do its thing, and guess what?
Enjoy Multi booting.
Helpful Quotes:
dopy25 said:
If you are on the ls970 sprint Optimus make sure to use the geehrc4G and not the geespr versions in the google drive. I know it might not make much sense but they work and they were edited by gearslam to flash pretty much any rom for the ls970 or gee.
Go to twrp, advanced, multiboot, add rom, then follow the prompts. I prefer to use the do not share kernel option. After that you can choose to install a rom from zip. Then the next boot you can choose which one to boot into.
If you want to add stuff, IE; change kernel or flash another zip to that rom (GAPPS) just go to advanced, multirom, list roms, then select the rom you want and you can choose a normal option such as flash zip, wipe data, wipe dalvik, wipe cache. It's all there once you select list roms.
Click to expand...
Click to collapse
gearslam said:
You need to install the TWRP-2.7.0_MR_geehrc.zip Recovery and then flash the multirom-20140409-v22-UNOFFICIAL-geehrc.zip
In TWRP under Advanced There is a MultiROM option. You can use a TWRP Backup or a ROM ZIP.
I'm currently running both Stock and Unoffical CM11 without any problems on the Sprint LS970.
Click to expand...
Click to collapse
gearslam said:
I just wanted to point out for those that don't know. OTG is working good in this recovery. I've been using a 16Gig flash drive formated to exfat. All you need is an OTG-Y cable. You can easily backup/restore and flash ROM's from USB drive. Another alternative to sideloading if you accidently wipe everything out.
Click to expand...
Click to collapse
gearslam said:
I patched the recovery and multirom zips so geespr roms can be flashed and EFS backups can be made. I used Unoffical CM11 as my primary ROM and a TWRP backup of the stock based ROM as a boot option. You can flash different kernels on the primary ROM not sure about the secondary, etc. Anytime you flash a new Kernel, you have to go into advanced ->multirom and there is an option to inject multirom into boot.img
The secondary ROM's and there Data are stored in /data/media/0/multirom/...
The patched recovery and multirom are in my google drive: https://drive.google.com/folderview?id=0B3Vq3sppfNgnVjUzMy1YVXZxYmM&usp=sharing
Click to expand...
Click to collapse
Download Links to MultiBoot Recovery & .Zip: https://drive.google.com/folderview?id=0B3Vq3sppfNgnVjUzMy1YVXZxYmM&usp=sharing
*ALL* credit goes to Gearslam and anyone who helped.

Mine. Muhahahahaahahahaha :good::good::fingers-crossed::laugh:

Awesome.
I use this method and am rocking the dual boot with @gearslam 's mods. Thanks again for all the help.
EDIT: 4-29-2014
@gearslam Can you edit the script to allow installation of geespr roms? I tried to install an official rom and it said during installation that the process is for (insert multiple "GEE" type roms) and listed gee_spr but said the one I was trying to install was geespr. I think the underscore might make a difference. And since I have no idea how to update it to allow other roms, would you please?

Awesome! Thanks for this guide!
Sent from my Optimus G using XDA Free mobile app

Thanks for this, and thank you too gearslam! Rocking both cm11 and stocktimus ce. Love it, especially now that the stock Rom is using the 0 folder to load files so there aren't 2 separate areas to search through ( had to use twrps file manager to move some things up so I could view photos I took on stock lol)
Sent from my LG-LS970 using Tapatalk

So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...

treezy26 said:
So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...
Click to expand...
Click to collapse
From what I have personally tested yes. But you will need a backup of a run to use as 2nd. Like I said I use cm11 as primary and stock as backup. Very nice.

treezy26 said:
So... Does multibooting mean I can switch between roms and its just how I left it each time I switch? For example if I download an app and switch its still in the rom I downloaded the app for? Like I don't need to create a backup every time ?
idk how I got here...
Click to expand...
Click to collapse
Yes,
I use about 5 different ROMS and they all have different apps, and app data for that matter unless you have the app synced to something like facebook. Also, it depends on if you choose restore from my google account and back up this phone to my google account during setup.
Whiplashh said:
From what I have personally tested yes. But you will need a backup of a run to use as 2nd. Like I said I use cm11 as primary and stock as backup. Very nice.
Click to expand...
Click to collapse
Also, a backup to create a secondary rom is not necessary, you can choose to flash a zip to add a rom. I do it every time I want to try a new rom instead of flashing over my current. BUT YOU CAN CHOOSE TO RESTORE A BACKUP AS SECONDARY.
This by far is the most awesome feature I have ever came across. You can even have different kernels for each, just make sure during install that don't share kernel is checked.

dopy25 said:
Yes,
I use about 5 different ROMS and they all have different apps, and app data for that matter unless you have the app synced to something like facebook. Also, it depends on if you choose restore from my google account and back up this phone to my google account during setup.
Also, a backup to create a secondary rom is not necessary, you can choose to flash a zip to add a rom. I do it every time I want to try a new rom instead of flashing over my current. BUT YOU CAN CHOOSE TO RESTORE A BACKUP AS SECONDARY.
This by far is the most awesome feature I have ever came across. You can even have different kernels for each, just make sure during install that don't share kernel is checked.
Click to expand...
Click to collapse
You got it to work without a backup? Can you elaborate how? I couldn't get it to. Whenever I tried to flash normal zip ROM, it gave me errors.

Whiplashh said:
You got it to work without a backup? Can you elaborate how? I couldn't get it to. Whenever I tried to flash normal zip ROM, it gave me errors.
Click to expand...
Click to collapse
All I do is go to TWRP, Advanced, MultiRom, Add Rom, Make sure it says Android rom and not .mrom, check do not share (I don't know if it's necessary but I prefer not to share the kernel because I am greedy, also I have gproj and GEE roms) zip file then select your zip from storage.
Also, gearslam updated the files again, that might have something to do with it. I noticed a few errors while installing so I sent him a PM. The new files are on the google drive that's linked in the op.
His response was
I uploaded another one using the "geehrc4g" id which seems to be what the latest version of the LS970-TWRP is using these days...
Click to expand...
Click to collapse
Try using the ones he said. I was able to flash them in the order they are supposed to be OVER the old ones without losing anything, there is an option to inject multi rom after install, I selected that and everything works great. I can flash pretty much any rom as a secondary. I haven't messed around with much swapping because there hasn't really been a need.
I have Pac gee, Pac LS970 nightly, Beanstalk, Mokee, Lego, and stock. They were all flashed by adding a rom as a zip. No problems with any that I can see so far. I have a problem with Mokee and the keyboard but that might be unrelated.

dopy25 said:
All I do is go to TWRP, Advanced, MultiRom, Add Rom, Make sure it says Android rom and not .mrom, check do not share (I don't know if it's necessary but I prefer not to share the kernel because I am greedy, also I have gproj and GEE roms) zip file then select your zip from storage.
Also, gearslam updated the files again, that might have something to do with it. I noticed a few errors while installing so I sent him a PM. The new files are on the google drive that's linked in the op.
His response was
Try using the ones he said. I was able to flash them in the order they are supposed to be OVER the old ones without losing anything, there is an option to inject multi rom after install, I selected that and everything works great. I can flash pretty much any rom as a secondary. I haven't messed around with much swapping because there hasn't really been a need.
I have Pac gee, Pac LS970 nightly, Beanstalk, Mokee, Lego, and stock. They were all flashed by adding a rom as a zip. No problems with any that I can see so far. I have a problem with Mokee and the keyboard but that might be unrelated.
Click to expand...
Click to collapse
Okay. Thank you man

Whiplashh said:
Okay. Thank you man
Click to expand...
Click to collapse
Any time. Let me know how it goes if you do flash those other files.
If you try it out and it works for you maybe you could add it to the OP, that the ones to flash are the geehrc4g because anyone looking at them might not know that right off hand.

Quick question... When flashing a new rom to try, how does one go about doing that?
idk how I got here...

treezy26 said:
Quick question... When flashing a new rom to try, how does one go about doing that?
idk how I got here...
Click to expand...
Click to collapse
If you are on the ls970 sprint Optimus make sure to use the geehrc4G and not the geespr versions in the google drive. I know it might not make much sense but they work and they were edited by gearslam to flash pretty much any rom for the ls970 or gee.
Go to twrp, advanced, multiboot, add rom, then follow the prompts. I prefer to use the do not share kernel option. After that you can choose to install a rom from zip. Then the next boot you can choose which one to boot into.
If you want to add stuff, IE; change kernel or flash another zip to that rom (GAPPS) just go to advanced, multirom, list roms, then select the rom you want and you can choose a normal option such as flash zip, wipe data, wipe dalvik, wipe cache. It's all there once you select list roms.

Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app

spleef said:
Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same problem with the error saying no Kexec. Have you tried making a new backup and then adding as 2nd rom? That is now mine worked.

spleef said:
Trying to get this working but running into a few problems when adding a rom tells me can't find my data partition... It does complete and shows it to be added but once I reboot and select it... It has error box pops up says kernel doesn't have kexec I've tried many different ways having stock as primary on internal have PAC on primary internal tried adding as a zip tried adding as back up all ends the same with me only being about to boot into the primary internal ROM...
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any luck!? I have PAC gee as primary but I forget the kernel at the moment. I'm almost sure it's matr1x. Also make sure to use the geehrc4g version. It works perfect for me. And mine always says it can't find data partition. I think it's because it uses a folder named multirom in the sd0 partition. Also when your in a file manager you can't open that folder. I haven't tried with root permission but I don't want to mess anything up.

dopy25 said:
Any luck!? I have PAC gee as primary but I forget the kernel at the moment. I'm almost sure it's matr1x. Also make sure to use the geehrc4g version. It works perfect for me. And mine always says it can't find data partition. I think it's because it uses a folder named multirom in the sd0 partition. Also when your in a file manager you can't open that folder. I haven't tried with root permission but I don't want to mess anything up.
Click to expand...
Click to collapse
Not yet just tried again by making a back up of PAC and flashing a stock ROM but the stock ROM wouldn't boot kept kernel crashing immediately after the lg pop up so I'm going to download another stock ROM which one are you guys using? Says the same thing with trying with liquid though so I'm not sure what's going on tried to dual boot liquid and PAC had same exact results even tried making those two share the kernel as well as not buy of course didn't try that with the stock rom I kept it as is
Sent from my LG-LS970 using XDA Premium 4 mobile app

EDIT: I added some pics. 2 show the about this device. One is the boot menu the other is the list ROMs function under recovery.
The screenshots are the about info for my primary ROM.
Edit 2: Wow that was a weird double post. I use the stock zvc (from zip on the forum) but only as a secondary. PAC gee version from 4-4 is my primary.
@spleef ! I just thought of something, when I tried to use solid kernel on liquid smooth ls970 when it was a secondary ROM, my phone would also only boot the primary! I had to use f93 cpq to boot it and any other ROM other than primary. Maybe some kernels are not compatible if they override the primary. Try like I have with gee version of pac as primary and the kernel I'm using (might even be built in kernel) I'm hoping you know more than I do about it based on the about device info.

Nope still couldn't get it going...no matter how i try it get the kexec error doesn't matter which i use a primary stock or custom and same goes for secondary doesn't matter which one kexec error when trying to choose...I'm using geehrc4g version is very confusing
Sent from my LG-LS970 using XDA Premium 4 mobile app

[MultiBoot][unofficial]MultiROM V32 [DISCONTINUED]

Whats MultiROM
Multirom is a ROM manager created by Tasssadar with the ability to load multiple ROMs without the need to remove your older one, giving you the ability to test/run multiple ROMs at once, you can also restore TWRP backup as Secondary ROMs allowing you to look at your backup to choose the right one, or maybe just have 2,3,4,5,6 working OS on your phone... just because it's cool.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack.
I Nuked my SDCard twice in porting this tool over, I'm not entirely sure what caused it, but I reverted few changes which might have been the reason, so I hope it wont happen again.
Still, I'll highly recommend you make backups and keep them on your computer. Always.
I've been using this for 2 weeks now with no serious problems, but just as well, don't be blaming me if anything goes wrong.
keep the "i cant get this to work" messages out of my PM i wont bother replying to them,
as almost anyone on this thread can help you.
you have a problem, read the main OP and if you still cant get it to work... post your problem here...
and be specific... "this is not working" will get you nowhere and no answers.​
Special Thanks:​ @Tasssadar: For The MultiROM Source.​
Sources:​MultiROM
Modified TWRP​
Download is one post below.​

Requirements:
S-off/Unlocked Bootloader
Understand How KL Zeus Work*
By Flashing That Kernel, you'd need to flash a 2nd kernel to go along with it..
if you don't follow those instruction, the main ROM wont boot.​
To Install MultiROM:
Flash Zeus Boot.img
Flash Multirom-20141228-v30-UNOFFICIAL-endeavoru.zip normally trough recovery.
Flash Multirom-20150430-v32-UNOFFICIAL-endeavoru.zip normally trough recovery (New Layout ONLY).
Reboot
To Fix Write To SDCard issue(flash on secondary ROM only):Not Needed with New Layout
Flash UPDATE-SuperSU-v2.40.zip(possible only needed on Lollipop, if no, no harm in switching to SuperSU)
Flash SDFix.zip
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Add ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> Add ROM
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Change Kernels:
Boot TWRP --> Advance --> MultiROM --> List ROMs --> Flash Modules Zip*
List ROMs --> Remove boot.img
List ROMs --> Add boot.img
* The Modules must be flashed 1st, as the boot.img is replaced with each flash.​
Failed Install & losing memory
MultiROM -> TWRP
adb shell dosfsck -a /dev/block/mmcblk0p14
ToDo:
-- Nothing as it stands

and another one...

Amazing you did it..well done mate glad you are still with us on our dated hox.
Sent from my One X using XDA Premium 4 mobile app

Great!!! Eager to try but its very late night here
Also waiting for your Kernel
Sent from my One X using XDA Premium 4 mobile app

Wow your are just great ...... Will Test it if i have enough time.
Maybe you get tomorrow a pm
Gesendet von meinem HTC One X mit Tapatalk

Thant said:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
Click to expand...
Click to collapse
It'll be better if i answer this here,
during boot, after flashing MultiROM, MultiROM starts and prompts you to choose what to boot,
Internal (Main ROM), TWRP or other ROMs you installed.
if you want to change kernel of a secondary ROM,
You boot TWRP -->Advance --> MultiROM --> Select ROM --> Remove boot.img
Select ROM --> Add boot.img, then you get to select the kernel you want.
To Flash the Zips/Modules
TWRP -->Advance --> MultiROM --> Select ROM --> Flash Zip
Ill update the OP with these now.

I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app

lalit387 said:
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main ROM will remain untouched..
but you'll need to know how KL Zeus works to boot it.

Great! I do not have important data in the internal storage, so I can test it.

@Thunder07 I want to test it too

The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.

Thunder07 said:
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Click to expand...
Click to collapse
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.

ljjehl said:
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
Click to expand...
Click to collapse
jeez... 1GB it is then :/

Thunder07 said:
jeez... 1GB it is then :/
Click to expand...
Click to collapse
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk

humzaahmed155 said:
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok

Thant said:
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Click to expand...
Click to collapse
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat

cappuccina said:
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
Click to expand...
Click to collapse
just now deleted CM11 to many bug for me I missed important notification. The phone beep but I don't see nothing on the screen. Now for this week I think to test SlimKat to see how it works I hope to be stable and don't miss any inportant notification. Whole day I thik on the question why today I have too many free hours and in the end of the day when start main rom I understand why

So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.

humzaahmed155 said:
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
Click to expand...
Click to collapse
When I add a secondary Rom I also go into the advanced/Multirom/ list and select the Rom I installed. I then remove boot.img, then go back and install boot.img (the boot.img I extracted from Rom), go to the directory I saved that to and it's done. Should boot after that.
@Thunder07,
My current issue seems to be a cache issue. I seem to have to fastboot cache a lot more than I like, otherwise I can't always get to TWRP. Reboot (or from poweroff) more often than not seems to get me only the internal Rom and not the MultiRom startup. I was hoping a wipe cache from device would be sufficient, but no luck.