Guys,
I have been using codecROM for the past one month and i felt it was Superb. but i'm a viber user so viber isn't working on codecROM 9.1 so i had to revert back to stock ICS ROM. i have seen few posts regarding dual boot in Siyah Kernel. what i wanted to do now is as follows:
1st Boot: Stock ICS 4.0.4
2nd Boot : Any other custom ROM
is this possible..??
Currently my phone is Fully rooted.
also suggest me any ROM in which apps like viber which use wifi for calling will work for sure..
Thanks a lot guys i have learnt a lot from xda-developers
Great first post - not
Tip: Search for Siyah kernel
BPhild area
rahulbalmuri said:
Guys,
I have been using codecROM for the past one month and i felt it was Superb. but i'm a viber user so viber isn't working on codecROM 9.1 so i had to revert back to stock ICS ROM. i have seen few posts regarding dual boot in Siyah Kernel. what i wanted to do now is as follows:
1st Boot: Stock ICS 4.0.4
2nd Boot : Any other custom ROM
is this possible..??
Currently my phone is Fully rooted.
also suggest me any ROM in which apps like viber which use wifi for calling will work for sure..
Thanks a lot guys i have learnt a lot from xda-developers
Click to expand...
Click to collapse
my bad ... sorry guys.. just now i came across this thread.. http://forum.xda-developers.com/showthread.php?t=1709686 so according to tht dual boot is not supported by ICS... what if i update to 4.1.1(jelly bean)?? then how to dual boot??
Once you upgrade to jelly bean you will have to install siyah kernel, the latest version to be able to dual boot. Read through the siyah kernel thread under original android development, it'll explain everything.
Sent From My Omega'd Galaxy S3 ...
Hi,
Should be a fairly easy quick question
I'm running Siyah 1.8 Kernel on my phone to have dual-boot, which I really like as I can use a lightweight ROM for gaming and things and also have my stock features to hand as well.
However have decided I have tired of Stock and would like to use CyanogenMod JB 4.2 as my primary ROM and stick with my current WanamLite as secondary.
Are there any issues with flashing a new Primary ROM with CWM and keeping the 2nd ROM as it is?
Thanks
557953 said:
Hi,
Should be a fairly easy quick question
I'm running Siyah 1.8 Kernel on my phone to have dual-boot, which I really like as I can use a lightweight ROM for gaming and things and also have my stock features to hand as well.
However have decided I have tired of Stock and would like to use CyanogenMod JB 4.2 as my primary ROM and stick with my current WanamLite as secondary.
Are there any issues with flashing a new Primary ROM with CWM and keeping the 2nd ROM as it is?
Thanks
Click to expand...
Click to collapse
The Siyah thread gives you instructions on how to flash CM 4.2. If I remember well you can only have it as 2nd ROM (??). If so, than you can just select in STweaks to boot always into 2nd ROM for instance. To keep your WanamLite version, just swap 1st & 2nd ROM.
Hi everyone
My issue is somehow strange, I performed a clean install (full wipe, etc..) with Dorimanx Kernel 7.43 of Neat ROM 4.0 (XXLSJ) as primary ROM
When I install secondary ROM, Neat ROM boot loops and get stuck on the first Samsung bootanimation (where the logo is being drawn again and again)
I fixed permissions for secondary ROM, but still no boot, neither primary, nor secondary
I thought that ROMs are independent but seems like I'm wrong
Now I'm hesitating to retest the same with 7.44 kernel and 4.1 ROM (XWLS8)
What Have I messed ?
PS:
I reflashed my ROM and my phone is working fine, this thread is not about solving bootloop (with hundreds of threads dedicated here), it's about dual booting
Dorimanx doesn't support dual boot with any Samsung jelly bean roms currently
So it's kernel related, I did not notice this detail when flying over the changelog or the infinite number of replies :silly:
Thank you for the quick answer...
Try this Siyah MCM Kernel ver 3.0.60
http://sourceforge.net/projects/cm10i9100vsync/files/kernel/
I believe it is smoother than the Dorimanx Kernel and it supports dualboot.
Tha'ts the Kernels XDA thread:
http://forum.xda-developers.com/showthread.php?t=1891222
Not exactly sure what Conny has posted, but just incase you didn't know dual boot can't work with any siyah or dorimanx kernel till the dev fixes it, and only siyah 6 beta 1 or above and dorimanx v3.37 or above work with samsung jelly bean
1Chef said:
Not exactly sure what Conny has posted, but just incase you didn't know dual boot can't work with any siyah or dorimanx kernel till the dev fixes it, and only siyah 6 beta 1 or above and dorimanx v3.37 or above work with samsung jelly bean
Click to expand...
Click to collapse
1Chef is right, I thought Neatrom published a 4.2.1 release
Considering neatrom is based on stock Samsung and not aosp then it can't have released 4.2.1
Got another bootloop while trying (hopfully) the new setup (7.44 + 4.1.2 XWLS8), nothing happened
I think that siyah will give the same result as Dorimanx is forked from, maybe with latest stable future release of Siyah, it could be fixed.
Now, I got tired from re-re-re-re-reflashing my phone :silly:
I'd better wait
Newbie Takes The Plunge to Custom Rom and Kernel: Any Suggestions?
I'm still fairly a newbie, but have rooted two phones so far, thanks to the great information, tutorials, guides, resources, and videos posted here on XDA. I have a Samsung Galaxy S2 GT-I9100 and my daughter's Samsung Epic 4G.
I rooted my I9100 successfully a few months ago, but have never flashed a rom. I'm going to try out Neat Rom Lite tonight. I've finally gotten up the nerve!
QUESTION: Does anyone have any suggestion of which kernel I should flash along with it? I need better battery life. I would love to be able to watch videos and use the phone regularly and make it through the whole day without charging. Is this possible? Can a kernel and Neat Rom Lite do this for me?
Also, I rooted the Samsung Epic 4G yesterday. Any suggestions on what rom and kernel to put on it and how would be greatly appreciated.
Thanks a bunch for any assistance and comments.
Sorry to bring up such a silly issue.
But I never encountered any problem like this. So, pls help me out....
I have a WT19i device which being modded with various custom rom at various time.
for more than 1.5 years I didn't got into any kind of problem. and it all messed up.
Yesterday I was trying to install Super jelly bean 8.0 rom.
to do that,
1. I flashed nAa's kernel
2. Wiped whatever needed.
3. Installed rom's zip and gapps
4. Reboot my device.
Everything working well except i don't have any touch response....!
Then I re-flashed my stock 4.0.4 rom, and then everything working fine. (including touch)
Again I flashed cm10 kernel and then installed Cm10 rom
Same problem again, no touch response.....
I really want to install jelly bean rom to my device.
So, pls give me a solution.
Sry if this [Q] is bothering.
I have been downloading and installing and downloading..... Reading and researching!!! I have an unlimited data plan so let's face it I kick the hell out of it. I like to watch movies a lot on showbox or on cartoon HD threw mhl HDMI to my TV (mirrored). I can't stand touchwiz ROMs and I also like to have the latest even if its on my sgs3. I love this phone. Anyways after loads of messing around installing loads of different ROMs I realized the truth is that only Sammy tw ROMs have the USB drivers. This was all because I read on some post somewhere that said they had a custom ROM and a touchwiz launcher and to use mhl they simply boot the tw launcher for mhl use only and then back to Google launcher as a daily driver. Post didn't say which custom ROM they where using and/or if they had a custom kernel installed. So that's what set me of trying to conker making it work and my solution to this problem is "arter97 kernel" plus dual boot.zip plus back to noot ROM and I really do like the resurrection remix ROMs. I like the new marshmallow 6.1 but the arter97kernel doesn't support this so I settled for RR lollipop 5.1.1 v5.5.9 as the first ROM. installed this as per normal protocol and then flash the arter97 kernel using twrp recovery. I used v4.1 kernel because it has load more customizations than v5 for ex. Over clocking to 1800mhz and more Governors etc. Now arters back to noot kitkat 4.4.4 is very stable very good ROM. So once the first aosp ROM is OK and stable with the kernel (make sure you flash superSU) boot back into recovery and flash the dual boot zip and anything flashed during that visit to the recovery goes to the 2nd ROM partition. Next flash the back to boot ROM and superSU and boot back into 1st ROM (automatically) but don't wipe cache/dalvic/data (this will just wipe from the 1st ROM). Now the aswitch app will work to boot into the 2nd ROM. And because you flashed the superSU into 2nd ROM the aswitch will work to allow you back to the 1st ROM!!!! Every time you want to flash to 2nd ROM use the dual boot zip first. Because the back to boot kk 4.4.4 ROM already has arter97 kernel don't flash the kernel zip just leave it and it will have the same arter97 kernel once booted. If you flash the kernel to 2nd ROM it will just cause lag and instability The only problem I have had is whilst using this whole configuration is when inserting the mhl lead into sgs3 it freezes and/or shutdown. After a little tweaking I figured out it was a CPU issue and to enable the mhl and showbox use I used atweaks config app and changed Max over clock CPU to 1704mhz and governor setting to performance!!! Now this profile makes the CPU stick at 1704mhz permanently. This method works but unfortunately also creates massive battery drain so I have also been messing with the USB charge/power variables. But do be careful if you follow any instructions on this post as I am not responsible for a bricked divice so make sure you do your homework. This arter97 kernel is EOL @v5 for the sgs3 so versions 4.1 and 5 are only compatible for lollipop 5.1.1 so always read changelogs. Many thanks to arter97 for this dual boot and customisable kernel and ported ROM.