Hello fellas
This guide is just a quick how-to on dual booting. Many people have doubts on how to dual boot on Siyah, because it's something new and perhaps "scary" because they may think it can brick their phone.
___________________________________________
Requirements
A Galaxy S II I9100
3.x Siyah Kernel (3.2.x preferred). For latest version, visit the Siyah Kernel thread
90% charged battery
2.5GB of free space in your internal SD card
Patience
Time
So, do you complete all those requirements? Time to go to action. BUT BEFORE, a brief FAQ in a simplified way, based from this post made by the amazing droidphile
___________________________________________
FAQ
Can I dual boot Ice Cream Sandwich and Jelly Bean?
Yes you can, using Siyah v3.5.2.
1) What is dual booting?
Dual booting is the ability to boot into two different Ice Cream Sandwich-based ROMs (like CM9 and AOKP).
2) How is this done?
This is achieved by sharing the kernel and using a hidden partition in dev/block to store the 2nd ROM's /system and the /sdcard (Internal storage) to store /data and /cache inside a hidden folder (/sdcard/.secondrom)
3) How much does it take to clone a ROM?
It should take around 7 minutes
4) I want to dual boot fasturr. wat do?
When you get the splash screen to choose between ROMs, touch the screen or press volume UP to enter the PRIMARY ROM, and press the Home button or volume down for the SECONDARY ROM.
5) How can I remove the Dual boot and its partitions?
Just use the "Remove 2nd ROM" option in the Dual Boot options menu.
6) If I format my /sdcard, will my second ROM go kaput?
Yep, because you're wiping the folder that contains /data and /cache.
7) Can I dual boot a gingerbread ROM in a ICS ROM?
Niet. No.
___________________________________________
Now, the PROCEDURE
You must flash the Siyah kernel, either with CWM or ODIN
After you have flashed the kernel, reboot and let Android upgrade itself.
All done? Alright, move up to next step!
Download the desired ROM that you want to make it secondary, and place it in a safe place in your internal SD card
After that, reboot to CWM Recovery, and navigate to "Dual Boot options"
You'll see a list of options, namely :
View current status
Clone 1st ROM to 2nd ROM
Clone 2nd ROM to 1st ROM
Swap 1st ROM with 2nd ROM
Swap 2nd ROM with 1st ROM
Remove 2nd ROM
Install 2nd ROM from Internal SD card
Install 2nd ROM from External SD card
Wipe 2nd ROM data/cache
Wipe 2nd ROM dalvik-cache
Fix 2nd ROM permissions
What does each one mean, you ask?
View current status - This option will show you the stats of the dual booted ROM.
Clone 1st ROM to 2nd ROM - This option will copy (clone) the current ROM that you use (for example, CM9) and paste it to the 2nd ROM directory. Takes around 7-20 mins.
Clone 2nd ROM to 1st ROM - This options copies the 2nd ROM (after installed of course) and pastes it to the place where the 1st ROM was, replacing it.
Swap 1st ROM with 2nd ROM - This will swap the 1st ROM with the 2nd ROM, making the Primary ROM -> Secondary ROM and the Secondary ROM -> Primary
Swap 2nd ROM with 1st ROM - This will do the exact opposite of the above option
Remove 2nd ROM - This will completely wipe and remove any 2nd ROM files and folders
Install 2nd ROM from Internal SD card - This option is to flash the ROM to the 2nd ROM directory from the Internal SD card
Install 2nd ROM from External SD card - This option is to flash the ROM to the 2nd ROm directory from the External SD card
Wipe 2nd ROM data/cache - This will wipe the 2nd ROM data and cache. When it's done for the first time, it'll create data.img and cache.img and create the folders inside /sdcard/.secondrom, preparing your phone for the 2nd ROM.
Wipe 2nd ROM dalvik-cache - This will wipe the dalvik cache of the 2nd ROM
Fix 2nd ROM permissions - This will fix the permissions of the 2nd ROM
Select the option Wipe 2nd ROM data/cache. This will prepare your phone to flash the 2nd ROM. It takes around 5-7 minutes.
After having that done, select the option to wipe the dalvik cache.
After all that is done, select either "Install 2nd ROM from Internal SD card" or "Install 2nd ROM from External SD card" depending on the location of your ROM
Wait a few minutes for the flash
Reboot
Press the Home button or volume down to enter the Secondary ROM
___________________________________________
After you have done all that, you're set and you're in the Dual Booting world! I hope that this guide helped you, and if it did, press the thanks button!
___________________________________________
Credits
GokhanMoral - For his amazing kernel
Droidphile - For his great FAQ
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Nice tutorial, very clear...
One question: I want to dual boot to a stock ICS rom for use a MHL adapter (resurrection remix dont support it as most of the AOSP/AOKP roms)... appart of that, what uses can you give to dual boot?? I cant imagine more!
whats wrong with this guide which is in the first post of siyah thread if people fail to read the faq prior to doing this instructions are pretty easy anyways even tho your guide is more clearer and pretty lol and you have taken the time to do this you will still get the some old questions beening asked lol.
anyways best wishes to you
Maybe it is time GM gets a section in XDA specifically for Siyah ...
g00ndu said:
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Click to expand...
Click to collapse
It seems that kernel was changed recently. What I did for my current dual-booting (used Siyah 3.2.3 that time): Wiped data/cache and dalvik of 2nd rom and just flashed new rom from recovery. I didn't format any partitions and had no problems at all with possibility to choose a rom at boot. Regards
Perhaps you can put in the GUIDE FAQ that step 9 doesn't flash the kernel image if present in the zip. (Assuming that it doesn't flash anything other than the /system and /data partitions correct me if I'm wrong)
The first time I used it I feared that I would mess up because I knew that the zip had the kernel img inside.
Good tutorial, thanks!
Many40 said:
It seems that kernel was changed recently. What I did for my current dual-booting (used Siyah 3.2.3 that time): Wiped data/cache and dalvik of 2nd rom and just flashed new rom from recovery. I didn't format any partitions and had no problems at all with possibility to choose a rom at boot. Regards
Click to expand...
Click to collapse
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
g00ndu said:
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
Click to expand...
Click to collapse
Belive me I did only what I wrote to you. I did not format any partitions and had no problems at boot at all. (Boot option to choose 2nd rom has been available). To be sure I have asked this afternoon also droidphile (author of very helpful guide and experienced on this topic). This is his answer: http://forum.xda-developers.com/showthread.php?p=26742671 Regards. Happy if helped.
Sent from my GT-I9100 using xda premium
DJBoxer said:
whats wrong with this guide which is in the first post of siyah thread if people fail to read the faq prior to doing this instructions are pretty easy anyways even tho your guide is more clearer and pretty lol and you have taken the time to do this you will still get the some old questions beening asked lol.
anyways best wishes to you
Click to expand...
Click to collapse
My intent was to make it even easier and more accessible/straightforward. My guide is meant for first timers, while that guide is more for people who have basic knowledge, which isn't always the case.
g00ndu said:
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Click to expand...
Click to collapse
g00ndu said:
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
Click to expand...
Click to collapse
Replying to both of those quotes, wiping data/cache creates data.img and cache.img. GM did a great job on dual booting, now it requires fewer steps.
Not booting second rom!
Hey there its a good tutorial but the problem is that its not booting the second rom! My primary rom is Resurrection Remix v2.0 and I want to dual boot Cyanogenmod 7.2.0 RC3 but I do everything and when I go to boot it and press the home button to boot into the second rom it just displays a blank screen with no boot animation. Any help would be appreciated!
Thank you!
Catley!
Sweet...Siyah
Cool Tutorial...Been using dual ROMS on my GS2 for about a week now...works like a charm...gives a chance to try out all those cool customs ROMS...
Catley said:
Hey there its a good tutorial but the problem is that its not booting the second rom! My primary rom is Resurrection Remix v2.0 and I want to dual boot Cyanogenmod 7.2.0 RC3 but I do everything and when I go to boot it and press the home button to boot into the second rom it just displays a blank screen with no boot animation. Any help would be appreciated!
Thank you!
Catley!
Click to expand...
Click to collapse
Phistachio said:
7) Can I dual boot a gingerbread ROM in a ICS ROM?
Niet. No.
Click to expand...
Click to collapse
It's all in the FAQ/OP...
I currently have VK 4.8 and I was wondering if it's possible to install a stock rom as secondary, XXLPW for istance.
Thanks
pippofiori said:
I currently have VK 4.8 and I was wondering if it's possible to install a stock rom as secondary, XXLPW for istance.
Thanks
Click to expand...
Click to collapse
Currently ICS Sammy and AOSP roms can be dual-booted so it's possible.
If you have .zip CWM flashable rom file:
1. Flash Siyah kernel
2. Flash your rom as 2nd from dual boot CWM menu
If you have .tar Sammy rom file:
1. Flash Siyah kernel
2. Clone 1st rom to 2nd
3. Flash Sammy rom as 1st rom from for example mobile odin - remember not to loose root so when you open rom .tar file then when all partitions are recognized change in odin stock kernel to Siyah.
4. Swap 1st and 2nd roms.
Sent from my GT-I9100 using xda premium
hello,
I want cm9 and the stock rom.. is it the same way to do it? just flash the stock rom as secondary??
yakie996 said:
hello,
I want cm9 and the stock rom.. is it the same way to do it? just flash the stock rom as secondary??
Click to expand...
Click to collapse
Yes, but a way to do that depends whether you have .tar or .zip rom file
Sent from my GT-I9100 using xda premium
Great info and easy to follow, will give it a try and see the results
Hi,
I have Resurrection Remix 2.0 as my 1st ROM with Siyah 3.2.7.2. I'd like to add Slim ROM as a 2nd, but Slim comes with the Fluxi kernal as part of the zip. Will that screw things up?
Related
DUMMIES, FOLLOW THIS STEPS TO INSTAL MIK_OS GINGERBREAD CYANOGENMOD 7 PORT:
FIRST OF ALL GO HERE AND READ MIK's POST and thank Mik for his work!!!!!!!!!!!!
READ THE CHANGELOGS AND THE KNOWN BUGS!!!!!
Let's suppose you have Froyo on your device and want to go Gingerbread:
- you need: root, custom recovery, and rom zip from here
- boot into recovery, go to backup/restore and do a backup. For your own privet safety, you could use TitaniumBackup before booting into recovery to backup your files and settings.
- while in custom recovery, go to wipe and perform all wipes. WIPE DATA AND CACHE IF YOU ARE UPGRADING FROM FROYO! Go to adb shell and make a /system wipe (mount /system in recovery; adb shell rm -rf /system/*), or copy this file on sd, and flash it via cusom recovery to automatically wipe your /system data
- after the wipe, put your rom on the sd card - get the beta2 here , and flash it from custom recovery.
- wait until it boots up and set the phone up. If you're stuck on LG logo it means you didn't performe the wipes corectly, mainly the system wipe.
- you will have no google apps after the install, so go here and get them, or manually download them from market
- you now have Mik_os unofficial CyanogenMod 7 2.3.3 on you phone. Install TitaniumBackup and perform a restore if you used this metod to backup your data as i described in the second step.
Now, if you have an older version of Mik's CM7:
-boot into recovery and flash the newer version just like that. It will update the one you have on your device, and no data will be lost.
GO AGAIN TO THE OFFICIAL DEV THREAD AND RE-READ THE BUGS AND CHANGELOGS. AND AGAIN... THANK MIK FOR HIS WORK!!!!!
If you have questions about Mik's port, go to the correct thread and ask them! This is not a developer thread, it is just for info, or for those of you who are new to xda and cannot post in dev threads.
AND AGAIN, THANK MIK FOR HIS WORK, AND BUY HIM A LOLLYPOP VIA PAYPAL.
I have tried your steps but could not install this ROM. It got stuck on the boot animation. An it wasn't CM7 animation. Tried few times but without any luck. Now i am back to my old rom. atleast i did not brick my phone but i will sure give it a another try
You are probabily stuck at the lg logo. You should try to wipe the system manually, by adb or flashing the zip I linked in the original post, in the third step. I had the same problem, but this solves it.
Sent from my LG-P500 using XDA App
Ruwin said:
You are probabily stuck at the lg logo. You should try to wipe the system manually, by adb or flashing the zip I linked in the original post, in the third step. I had the same problem, but this solves it.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
I wasn't stuck on LG Logo. I had Megatron installed, it went through LG logo, then got stuck Megatron's Android Logo. Seems the rom was never installed properly and i have tried few times.
I have wiped everything, i have flashed from the zip you provided, and also i re-partitioned the sd card but it never worked
Did you got any errors when flashing cyanogen zip? From what you said, I think you shoul rewipe everything, part the sd 0 swap, ext 2 to ext3 and ext3 to ext 4. Make sure that you have the check for signed option in custom recovery.
Sent from my LG-P500 using XDA App
Ruwin said:
Did you got any errors when flashing cyanogen zip? From what you said, I think you shoul rewipe everything, part the sd 0 swap, ext 2 to ext3 and ext3 to ext 4. Make sure that you have the check for signed option in custom recovery.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
I have done all of the above, may be the zip file got corrupted. Anyway, i will try again this weekend. thanks
How did you do the system wipe? You flashed the zip for wipeing or did you do it from adb shell?
I have another friend that flashed the /system wipe tool, and forgot to flash the actuall rom zip file, and had the exact simptomes as you described.
Sent from my LG-P500 using XDA App
Ruwin said:
How did you do the system wipe? You flashed the zip for wipeing or did you do it from adb shell?
I have another friend that flashed the /system wipe tool, and forgot to flash the actuall rom zip file, and had the exact simptomes as you described.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
I used custom recovery, nandroid back up, then re-partition the sd card. then wiped the card, then usb toggle to copy 2 zips on to sd card. flashed debug system just in case and then flashed mik's rom. I don't know where did it go wrong.
Would have been great if someone made a step by step video and put that on youtube
Have you wiped cache/dalvink cache/android secure and the rest from the wipe menu?
Sent from my LG-P500 using XDA App
Ruwin said:
Have you wiped cache/dalvink cache/android secure and the rest from the wipe menu?
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Yes, I think so. Don't worry about it for the moment. if it worked for you, it will work for me too. I may have missed something that i can't remember. I will give it a try again this weekend
Although if you could give me the Partition requirements. I know the swap should be zero. But how much should i use for ext2?
Ext partiton can be how big you want, it's where a2sd puts the files and other cache info. I use 512 mb, and works flawless.
I will make a video guide in the morning, and link it in the original post.
Sent from my LG-P500 using XDA App
Do I need to install that new recovery? Or is the one you posted a link to OK?
There is a new recovery that's been in the development forum for a few weeks that says it's for gingerbread.
thesmoth said:
Do I need to install that new recovery? Or is the one you posted a link to OK?
There is a new recovery that's been in the development forum for a few weeks that says it's for gingerbread.
Click to expand...
Click to collapse
The link i posted goes to another thread that explains some basic stuff. Including the recovery. But i didn't find any problems using different versions of custom recovery. So go for which one you like more, as long as it can backup your system
1. go in recovery mode
2. wipe everything
3. then go to others
4. mount/system
5. flash the system zip
6. flash the rom zip
7. reboot
it worked for me. hope it helps
Ruwin buddy, you will be happy to know that i am using Mik's rom. I still don't know what went wrong last time. If some thing that i had done differently, that would not upgrading ext3 to ext4.
Thanks buddy for the support and the tips
Thank you very much!!! Will try this today.
Is it possible to get the SMS widget back? The simple one from Market sucks...
Do I need to partition the SD-card?? The directions made no mention of this.
how to enable 3G mode only in this rom ?
Good work, very useful.
i currently have Megatron v1 rom in my p500
i installed the custom recovery thing and installed the rom and after that i flashed mik_os kernal..
phone is working great from some time now but now i m thinking of updating to franco's as megatron is pretty outdated now + i m getting a new memory card..
so i dont know from where to start ?
pls guide me ?
Hey,
1 : Dload Rom an Kernel .
2 : create backup !!
2.5 : reboot in recovery !!
3 : clear cache , all
4 : create partition as per req
5 : toggle usb
6 : copy rom an kernel , then flash from sd !!
If I missed anything , sorry :!
So i straightaway put in the new memory card and restart into custom recovery and follow the steps u mentioned ??
Some questions/doubts i have.
As i have partioned this current memory card... what files does it hold ?? (Hope i wont face any prob after removing this card)
And should i flash the rom first or the kernal ??
And in francos topic he has menrioned that data2sd thing is not stable yet ??
So what kind of problems are we talking about and is franco's kernal and rom stable altogether ??
I dont like my fone to be stuck after eveylry 5 mins or so .... pls reply...
Nd thanks in advance..
Sent from my LG-P500 using Tapatalk
Just put in the new card, reboot into recovery, create the ext partition (the card will be formatted afterwards), wipe everything Franco says in his first post, then toggle USB mode, connect to PC, paste the rom and kernel, exit USB mode, flash the rom, reboot. Then power off, enter custom recovery, flash the kernel, wipe caches, reboot.
Install SetCPU, set 729max - 480min with smartass and set it on boot.
Rest assured, Franco's devoid is a very stable build... you will really be amazed by your phone afterwards. If you want, afterwards you can install all sapps or just the essestial gapps (you can find links in the ROM thread - in the last 2-3 pages).
Thanks for the reply..
One ques remains abt data2sd thing (which is step 1 in his topic)
What steps shud i follow to install that ? Or is it already a part of the rom ?? If not where cn i dl it ? Is it gud ??
Nd i heard there is an altermative (apps2sd) ??
Which one do u recommend ?
Apps2sd is used in megatron rom rite ??
Sent from my LG-P500 using Tapatalk
Oh, sorry... I forgot about that!
Neither app2sd nor data2sd is included in the rom, but you can easily flash them in recovery. You will need to enable them afterwards (there's a market app and also a command for the terminal emulator).
Use Darktremor's app2sd, not ungaze's data2sd (since from what I've read, it's pretty buggy with Franco's ROM&kernel).
I don't know what is used in Megatron, but you can find out all you want about app2sd here: http://forum.xda-developers.com/showthread.php?t=670087.
Thanks a lot dude !
Sent from my LG-P500 using Tapatalk
Glad to be of help!
(you can also click the thanks button)
Happy flashing!
sholimar said:
Glad to be of help!
(you can also click the thanks button)
Happy flashing!
Click to expand...
Click to collapse
sorry i m new
done
hey one last thing
the link u gave to the app2sd topic
it says ***OUTDated*** right in the topic name
so just wanna ask should i install the latest version found here
or is that outdated version only compatible to our phones ??
I apologize, I was in a hurry and provided you with an old link...
The latest versions of Darktremor's app2sd are supported by Franco's rom, so install whichever you like from http://forum.xda-developers.com/showthread.php?t=926015.
Oh, and from what I've read, Franco also supports ext4 partitions (although I recommend having an SDHC 6 or above card).
ok
so here goes ?
1) Download rom kernal and app2sd image
2) boot in custom recovery (i have RA_thunderg-1.1.0-GNM)
3) Wipe everything (everything rite ?? all the options ?)
4) partition my new sd card (swap: 0, ext: 512, ext2-ext3, then ext3-ext4 it.)
5) Flash the app2sd image file (gonna flash the last stable build.. not latest beta)
6) after its completed straightaway flash franco.devoid rom file
7) after its completed i reboot < chk out the new rom for a moment
8) reboot into recovery again and then flash the kernal
9) Wipe cache (not sure how to do this ??)
10) install set cpu through the link u gave ?
and please afterwards how to make sure the app2sd is working as u said earlier i need to fill in a command or install an app ??
oh before wipe i will create a backup too
what kind of backup do u recommend ?? as there are 5-6 options i guess ??
and should i wipe before or after partioning my sd card ?
Gagan91 said:
oh before wipe i will create a backup too
what kind of backup do u recommend ?? as there are 5-6 options i guess ??
and should i wipe before or after partioning my sd card ?
Click to expand...
Click to collapse
I think there is only one option for backup, that's nandroid backup.
Which is there in CWM.
Sent from my LG-P500 using XDA Premium App
It aso shows options like nand backup, nand+android secure, nand + ext
and then at last they say google something..
So pls suggest ?
Sent from my LG-P500 using Tapatalk
You have amon RA, so a simple nand backup will be fine. And after that you can wipe, then partition. I installed DT apps2sd (the beta 4) after flashing the ROM and kernel and it works great. So I guess it's fine.
Lets say I don't want to flash any app2sd or d2sd on my phone and I want only the native a2sd which comes with the ROM. Do I need to create any partitions? Or can I simply skip that step?
sweettaniyaa said:
Lets say I don't want to flash any app2sd or d2sd on my phone and I want only the native a2sd which comes with the ROM. Do I need to create any partitions? Or can I simply skip that step?
Click to expand...
Click to collapse
No, you don't have to create any partitions in that case.
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
Okay i read his entire thread almost at least 100 pages, I searched countless times for a dummies installation guide
My old andriod dell venue broke so, Okay i got mad and threw it lol, anyways i read reviews about the Samsung Galaxy S2 so got it, I decided i want ICS and i choose his as it looks more favorable among the others.
My Model number is GT-I9100
Andriod version 2.3.4
Can some one please take the time to tell me what is the correct steps to take to make my phone capable of installing this Rom
I seen his instructions
Install the Main ROM 1.4 (important: dont install siyah kernel yet )
install aokp gapps
Reboot
and the Faq Link
Reboot into recovery
Wipe Data / Factory Reset
Wipe Cache Partition
Install the Main ROM
Install the Gapps for AOKP
In recovery go to Advanced
Wipe Dalvik Cache
Fix Permissions
Wipe Cache Partition
Reboot
This will be my first time doing this so can someone please dummy this down for me cause the install rom is greek to me, Do i need to put the rom somewhere, is there pre steps i must do before my phone will accept this
Thank you in advance to any one that helps
Hey,
Im assuming that you still have a factory standard phone so you will first need to root it. If you search google there is loads of guides on how to do this.
then you need to download and install CWM recovery (clockworkmod) again another google search
then you can proceed to the rom installation instructions
download the ROM (zip file ... dont unzip) and stick it somewhere on your SD card
turn your phone off then boot in to recovery by holding volume up, menu key and power button then do factory reset etc and then install zip from sd card (the zip being the ROM)
Please press the thanks button on this reply if you found it helpful
Cheers
Bidoa
Read and learn, everything is there for a noob : http://forum.xda-developers.com/showpost.php?p=24849218&postcount=3 thanks to JJE
Keep reading. All will come together. Basics first. Root then look on how to install roms. Patience.
Sent from my GT-I9100 using xda premium
First step you need to do is root the phone. I used the guide here after following what the guy was doing a few times in the video.
Then BACKUP YOUR EFS FOLDER as soon as you have root. An app called HC-KTool on the android market can do this. Be sure to verify your backup too and copy the efs.img to your PC for safe keeping.
Get titanium backup and batch backup all user apps and system data. Copy the folder on your internal SD onto your PC also.
Boot into CWM and make a backup here too.
Now you are ready to flash a ROM - Resurrection Remix ICS 1.4 here contains links and FAQ.
As it's your first ROM install you should follow the full installation guide in the FAQ. I stayed with the stock kernel as had problem with siyah and theroux.
DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App and data sharing?
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
(Hope my analogy didn't suck too much )
Click to expand...
Click to collapse
How do I?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Just in case, if the app does not work, use the DualBootUtilities.zip from recovery to switch.
Downloads
App - https://www.androidfilehost.com/?fid=24438995911976818
Utilities - https://www.androidfilehost.com/?fid=24438995911976820
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Samsung Galaxy Star, ROM for the Samsung Galaxy Star
Contributors
corphish, chenxiaolong
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Beta
Created 2016-03-11
Last Updated 2016-03-11
Reserved
Info about partitions
Our system partition is large enough to hold both CM10.1 and CM11.
I am currently using CM11 as primary and CM10.1 as secondary ROM.
In any case, one of the ROMs is stock, you may want to install the other on some other partitions.
It is recommended to use stock as primary.
If you are installing any ROM on ext-sdcard, you would need a fast sdcard.
corphish said:
Info about partitions
Our system partition is large enough to hold both CM10.1 and CM11.
I am currently using CM11 as primary and CM10.1 as secondary ROM.
In any case, one of the ROMs is stock, you may want to install the other on some other partitions.
It is recommended to use stock as primary.
If you are installing any ROM on ext-sdcard, you would need a fast sdcard.
Click to expand...
Click to collapse
Just in one day you did it ! you're GREAT corphish !
At all can the system partition hold both of cm12.1 and JB4.1 ? also what about kernel ? will the both of them use the same one or each one uses its individual one ?
This will save a lot of time for me when I want to test cm12.1 as I have to flashed it then restore the one I use :crying:
thanks @corphish
i cant open shared apps menu while on cm11(primary).. and rom menu wont open too in cm10(secondary) but can access shared apps menu
LahKeda said:
Just in one day you did it ! you're GREAT corphish !
At all can the system partition hold both of cm12.1 and JB4.1 ? also what about kernel ? will the both of them use the same one or each one uses its individual one ?
This will save a lot of time for me when I want to test cm12.1 as I have to flashed it then restore the one I use :crying:
Click to expand...
Click to collapse
You will have to check how much space is left in system when on stock. Then calculate accordingly.
And kernel used is different for different ROMs.
aLchiEro_06 said:
thanks @corphish
i cant open shared apps menu while on cm11(primary).. and rom menu wont open too in cm10(secondary) but can access shared apps menu
Click to expand...
Click to collapse
App works perfectly fine on kitkat. But not in jb because it is not able to load libs, I will have a look on it.
corphish said:
You will have to check how much space is left in system when on stock. Then calculate accordingly.
And kernel used is different for different ROMs.
Really ! Ok I will try it !
Click to expand...
Click to collapse
@corphish
That moment, when u helped me to remember about somebody who tried to make multi-boot supporting kernel for gts5282.
And we have the thing now.
---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------
[/COLOR @corphish
That moment, when u helped me to remember about somebody who tried to make multi-boot supporting kernel for gts5282.
And we have the thing now.
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
duck'man said:
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
Click to expand...
Click to collapse
you need to patch it's zip first , and if you will use original ..tar file you won't be able to do it !
LahKeda said:
you need to patch it's zip first , and if you will use original ..tar file you won't be able to do it !
Click to expand...
Click to collapse
for primary partition its only working for KK+ right?
duck'man said:
can i instal stock jb 4 .1.2 on my secondary partition? ,, thanks
Click to expand...
Click to collapse
yah
duck'man said:
for primary partition its only working for KK+ right?
Click to expand...
Click to collapse
I don't think so you can flash any ROM in primary one !
LahKeda said:
I don't think so you can flash any ROM in primary one !
Click to expand...
Click to collapse
im using 4.1.2,, it cant instal dualbootpatcher.apk
duck'man said:
im using 4.1.2,, it cant instal dualbootpatcher.apk
Click to expand...
Click to collapse
this app still not usable for jb
How to delete or disable this dual boot
Any way
Hridul P.K said:
How to delete or disable this dual boot
Any way
Click to expand...
Click to collapse
by wiping system/data/cache/dalvik from recovery
Dark Knight Begins said:
by wiping system/data/cache/dalvik from recovery
Click to expand...
Click to collapse
Thanks man
Going to boot cm 11 and cm 12 in external sd
Is there any problem iam gonna face
Or
Can i flash a new cm 12.1 on old cm 12.1
Hridul P.K said:
Thanks man
Going to boot cm 11 and cm 12 in external sd
Is there any problem iam gonna face
Or
Can i flash a new cm 12.1 on old cm 12.1
Click to expand...
Click to collapse
to do a clean install u should wipe things first.
hit d thank button, don't say it
Help me plzzzz..........
I am using gts5282 resurrection remix marshmallow custom ROM and I want dual boot but my kernel is not supported and in the previous link of gts5282 in which the developer has given a link of kernel which supports dual boot. This is the link- http://forum.xda-developers.com/showthread.php?t=2733137.
But the download link was expired so I kindly request you guys who downloaded that kernel to please update that link or just upload that kernel in this blog so that I can flash that kernel . And MY device will also be dual boot supported .Your help will be appreciated :good: .
Mohsin Pathan said:
I am using gts5282 resurrection remix marshmallow custom ROM and I want dual boot but my kernel is not supported and in the previous link of gts5282 in which the developer has given a link of kernel which supports dual boot. This is the link- http://forum.xda-developers.com/showthread.php?t=2733137.
But the download link was expired so I kindly request you guys who downloaded that kernel to please update that link or just upload that kernel in this blog so that I can flash that kernel . And MY device will also be dual boot supported .Your help will be appreciated :good: .
Click to expand...
Click to collapse
It's not necessary just use this tool and it will patch the kernel image for you .