Dual-Boot FAQ thread | devil2-kernel by DerTeufel1980 [Note 2]

[sabresfan]

You need to mount Secondary System in due boot menu

duel boot menu -enable mounting of sec File.


regards
Joy

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





Hi
Tried this on Primary Rom, Its not working. Checking again.n will also test for secondary Rom n let yoiu know

JoyMoro

Theres no space after the / in either the 1st or 2nd rom scripts. It didn't work for me on primary rom until this. All great now.

Sent from my SCH-I605 using Tapatalk 2

 

[dagosjt]

Hello,
I've a "little" doubt. Let's say I'll be able to install both ROMs and everything works beautifully everywhere. One day will appear an update about the ROM on secondary partition (let's call it ROM_B). What will I have to do to install it? Will it be possible to simply choose the second partition and operate normally (all the wipes and flashes), or I'll have to nandroid backup both roms (ROM_A & ROM_B), clean everything, restore ROM_B on primary partition, install update, than move it on second partition and restore ROM_A on primary?

I hope my question is clear, sorry in advance for my english

 

[RichMD]

Hello,
I've a "little" doubt. Let's say I'll be able to install both ROMs and everything works beautifully everywhere. One day will appear an update about the ROM on secondary partition (let's call it ROM_B). What will I have to do to install it? Will it be possible to simply choose the second partition and operate normally (all the wipes and flashes), or I'll have to nandroid backup both roms (ROM_A & ROM_B), clean everything, restore ROM_B on primary partition, install update, than move it on second partition and restore ROM_A on primary?

I hope my question is clear, sorry in advance for my english

Your question is clear. I would say "it depends". If you have a 4.1 non-AROMA ROM on secondary then the update directly to secondary should work other than MTP possibly breaking. Some scenarios will clearly require the full backup/restore you listed. Some will be try it and see. ..

Sent from my SGH-I317 using Tapatalk 2

 

[irule9000]

I don't want to sound like a ****, but is derteufel's phone working again, If so is the cdma recovery in progress?

Sent from my SPH-L900 using Tapatalk 4 Beta

 

[greenguggu]

Should I be on stock rom and recovery before the whole process???
Current I have android revolution hd 17.0 installed and custom recovery!!

 

[RichMD]

I don't want to sound like a ****, but is derteufel's phone working again, If so is the cdma recovery in progress?

Sent from my SPH-L900 using Tapatalk 4 Beta

DerTeufel's phone and pc both had problems but both are working again. However, I am not even sure what you are asking. There is a specific recovery (listed as N7100) for non-LTE phones which is what I "assume" you would mean when you ask about a "CDMA" (not LTE) recovery. It has been available for a while. Are you asking about an update?

 

[RichMD]

Should I be on stock rom and recovery before the whole process???
Current I have android revolution hd 17.0 installed and custom recovery!!

There is no requirement to be stock. I flashed both from TWRP custom recovery initially. I don't know the ROM you are talking about but if it is either Samsung based or AOSP/AOKP, etc then just flash the kernel to ensure it still works, then flash the dual-boot recovery appropriate for your phone (LTE or not)

 

[medic86]

Hi one Question.
Is this MOD working with Dual Boot kernel?
http://forum.xda-developers.com/showthread.php?t=2036796

Sent from my GT-N7100 using xda premium

 

[irule9000]

DerTeufel's phone and pc both had problems but both are working again. However, I am not even sure what you are asking. There is a specific recovery (listed as N7100) for non-LTE phones which is what I "assume" you would mean when you ask about a "CDMA" (not LTE) recovery. It has been available for a while. Are you asking about an update?

I am on the l900. Each phone requires a slightly different custom recovery. I was trying to slyly ask the eta for the sprint l900 dual boot recovery. I appreciate all his hard work and saw the numerous updates to the kernel itself. I was just wondering why there is no l900 recovery yet.
Sorry for asking for the eta.

Sent from my SPH-L900 using Tapatalk 4 Beta

 

[n1nj4Lo]

I will try to update this thread to clarify the methods you can use to enable dual-boot functionality along with common problems and solutions. This is an initial draft that I will update after it is verified (by DerTeufel and others). Additionally, I will try to re-word as necessary to avoid confusion. Hopefully, the list of questions should help you to complete what you are trying to do.
Initial dual-boot config, skip to the questions below

FAQs
Q) I am having ... problem with the secondary ROM (Play Store FC, no SD card access, no MTP, it fails to install and affects the primary ROM, etc)
A) 4.2 ROMs do not typically (if at all) install properly to the secondary partition currently. Additionally, 4.1 roms have a problem with MTP frequently or AROMA roms will fail the ROM to secondary install-script-modification step . Instead backup your current primary (nandroid) and install the 4.2 ROM to primary, boot with the kernel included in the ROM and ensure everything works including MTP. Then flash the dual-boot kernel. Then wipe the secondary partition, and restore your 4.1 ROM to the secondary. 4.2 on the primary and 4.1 on the secondary (or 4.1 on both) seems to be a reliable setup. I will update on steps if anyone has 4.2 working completely (via restore) on secondary but it often problematic.

Initial Setup
1) Have you flashed the dual-boot (aka DB) kernel yet? If yes, go to step 3

2) Flash the DB kernel: Go to the DB OP here and flash the version for your model type - http://forum.xda-developers.com/showpost.php?p=40410021&postcount=1 N7100 is for non-LTE models and t0lte is LTE enabled (AT&T, Verizon, etc). The zip will NOT list recovery in the name...

3) Have you flashed the DB recovery? If yes, go to step 5

4) Flash the DB Recovery: Navigate to DB OP listed above and flash the version for your model type (as in step 2 above)

5) Have you created the secondary system partition? If yes, go to step 7

6) Create the secondary partition image: Boot into the DB recovery and select Dual Boot Menu > enable mounting primary and then select create secondary system image (also under Dual Boot Menu". This will take a couple of minutes. This only has to be done once.

7) Ready to flash primary or secondary ROMs: Note: It is probably a good idea to get in the habit of always selecting the FS (primary or secondary) that you want to affect just to ensure you don't wipe the wrong one, etc. Select Dual boot menu > enable mounting of (pri or sec.)... It stays selected until you boot into recovery and change it. You will see recovery flash (reload) with the appropriate FS selected. Obviously, don't select it again - logic loop...

8) You at least need to follow standard ROM installation instructions at this point such as wipe data, etc (as appropriate). Wipe Data/Factory Reset will leave the ROM (typical) and the 2nd option (wipe data-cache-system-preload) will wipe out the ROM completely so you can start "clean". Only the selected FS is modified so the other ROM is not affected. All apps and data are separate for each ROM. SD card storage is common so keep that in mind for an app that exists in both ROMs.

9) Installing to the primary partition does not need any special instructions. You should have already selected "enable primary". Select "Install zip" > Choose zip from sdcard or external > ROM to Primary FS. The difference between the "ROM" and "Zip" selections is that zips do not typically explicitly access the file systems - they use references in recovery.fstab which DerTeufel modified to point to the appropriate locations depending on your selection (primary or secondary). Yes, choosing install zip might work for installing a ROM to primary but NOT to secondary. Also, the intention is to avoid confusion.

10) Installing to the secondary partition MIGHT be more problematic since the zip has to be modified first to replace FS references with the secondary locations. When you select this option, it can take a couple of minutes since it is changing the references and then re-zipping to a modified file on the SD card. Note: The original will be gone (at least if it was originally on the SD rather than the external SD) so make a copy, etc before proceeding if you want it to be available for standard/primary flashing in the future. The modified file will always install to the secondary partition after being modified. Note: Complicated install scripts (such as AROMA) will likely fail. If you want an AROMA based installation then the safest way is to install it to the primary partition, ensure it is working, make a backup and then restore the backup to the secondary partition (using the DB recovery of course). Backup/restore will be detailed below.

11) Recovery does not automatically mount /system, and /data so ensure /cache and these are already mounted before running a zip that will need to modify them

12) Avoiding MTP issues: After flashing a ROM, recovery prompts you to install the DB kernel again. Otherwise, the kernel installed with your ROM will not be able to boot the secondary ROM. However, if you do flash the DB kernel right away (for now at least) you may have a problem with MTP (access from a PC over USB). If you boot the new ROM (with the ROM's kernel which will work for PRIMARY) then MTP should be working. You can then flash the DB kernel after rebooting to recovery and MTP will still work (afaik). Similar to the AROMA note above, you might want to install a ROM to primary first even if you want it in the secondary partition. The install script will not need to be modified and a normal kernel will boot the ROM so MTP will work. Then you can flash the DB kernel, make a backup and restore to the secondary. Hopefully, this is only temporary but at least this workaround exists.

13) Ready to flash zips to primary or secondary ROMs Flashing gapps, etc. simply requires that the correct FS is enabled, /system and /data (as necessary) are mounted and select your target under "Install zip" > "Choose zip from..." > Zip to (primary or secondary).

Kasortiexda has created another installation process documented in post #13 > http://forum.xda-developers.com/showpost.php?p=41992232&postcount=13

Step 6) Tried to do that then it says E: unknown volume for path [/data] E: failed to mount primary filesystem

I did reboot immediately (reboot primary system now) after I installed DB Recovery, then rebooted (reboot primary system now) let phone load up. Did I do something wrong?

 

[dingokevin]

Try this first mount secondary then create secondary system.

Sent from my GT-N7100 using Tapatalk 4 Beta

 

[n1nj4Lo]

Try this first mount secondary then create secondary system.

Sent from my GT-N7100 using Tapatalk 4 Beta

All in dual boot menu correct? I did it there 3rd option then 1st option, now it's sitting there, so I guess it's working. I remembered reading this may take a lil while.

 

[dingokevin]

It can take a bit yes in the dual boot menu.


Edit let me know if you get it.

Sent from my GT-N7100 using Tapatalk 4 Beta

 

[n1nj4Lo]

It can take a bit yes in the dual boot menu.


Edit let me know if you get it.

Sent from my GT-N7100 using Tapatalk 4 Beta

I believe it's working and make sure I made a NAND and as far as Ubuntu Touch goes I selected secondary and I guess for this

To install you need to download the cm-10.1-20130317-UTOUCH2-t0lte.zip latest quantal-preinstalled-phablet-armhf.zip. Then preforme a full wipe of cache, delvik cache, factory reset, and system. Then flash the two files in the order given below.

1.cm-10.1-20130317-UTOUCH2-t0lte.zip
2.quantal-preinstalled-phablet-armhf.zip
3.Reboot

I have to do both as Zip to Secondary FS? I tried 2. zip as a rom and it didn't work.
^---that method didn't just reboots to splash screen then goes black and shuts down....

---------- Post added at 11:39 PM ---------- Previous post was at 10:58 PM ----------

Okay for some reason anything I try to install as a rom always says Something went wrong... Then gives me a log, right now it appears as I have no rom at all.

 

[dingokevin]

Start fresh do a reset for new rom then flash rom to primary and reboot

Sent from my GT-N7100 using Tapatalk 4 Beta

 

[RichMD]

I believe it's working and make sure I made a NAND and as far as Ubuntu Touch goes I selected secondary and I guess for this I have to do both as Zip to Secondary FS? I tried 2. zip as a rom and it didn't work.
^---that method didn't just reboots to splash screen then goes black and shuts down....

---------- Post added at 11:39 PM ---------- Previous post was at 10:58 PM ----------

Okay for some reason anything I try to install as a rom always says Something went wrong... Then gives me a log, right now it appears as I have no rom at all.

Sorry if I had the wrong step for the initial creation of the second partition. I originally didn't have enable either before create and someone said it should be enable primary. However, if you are trying Ubuntu which could have a very different install script, etc, I would suggest installing it to the primary partition. Backup your current primary and restore it to the secondary partition. The "Install ROM to secondary" step has to modify the install script which is what is causing the "something went wrong" message. Installation to primary does not need to do that step so AROMA installs, or non-typical installs etc will work.

I've updated step 6 of the OP.

 

[n1nj4Lo]

Start fresh do a reset for new rom then flash rom to primary and reboot

Sent from my GT-N7100 using Tapatalk 4 Beta

Is it normal for it to say that to "Rom to "Given" FS" so should I just wipe completely and start all over, factory/data reset, wipe cache partition too? Cause it appears that's the only way I'm able to flash. But I'm getting nowhere with it so far.

---------- Post added at 11:58 PM ---------- Previous post was at 11:57 PM ----------

Sorry if I had the wrong step for the initial creation of the second partition. I originally didn't have enable either before create and someone said it should be enable primary. However, if you are trying Ubuntu which could have a very different install script, etc, I would suggest installing it to the primary partition. Backup your current primary and restore it to the secondary partition. The "Install ROM to secondary" step has to modify the install script which is what is causing the "something went wrong" message. Installation to primary does not need to do that step so AROMA installs, or non-typical installs etc will work.

I've updated step 6 of the OP.

Well if all goes well and as planned, we'll have confirmation of being able to dual boot android with android on devil.

---------- Post added 8th June 2013 at 12:37 AM ---------- Previous post was 7th June 2013 at 11:58 PM ----------

FINALLY Got my Android Daily Driver of choice to flash to secondary fs... I guess I'll wait on a reply from the T889 Ubuntu Touch Port to see the proper method for flashing it.
-edit-
If there ever is a reply, it seems as though it's since then become a dead and abandoned project.
-edit-
Is it safe to delete sdcard/0 I believe that's a NAND I was never able to restore I also see secondrom, but I'm drastically out of inner space. Or where exactly are the NANDROIDS Stored at? I believe I somehow have the same rom just installed twice, not from Devil Recovery, but prior to trying to set up a dual boot.
-edit-
Okay now I'm at a loss, I rebooted into Devil and did all 3 wipes and still no changes to inner sd space.
-edit-
Formatting sdcard fixed that.

 

[greenguggu]

Not working man!!..stuck on blank screen after first boot

 

[RichMD]

Not working man!!..stuck on blank screen after first boot

I can try and help but you need to provide more detail such as "first boot" after what step/procedure?
Did you flash the DB kernel?
Did you flash recovery"
Did you create the secondary partition?
Did you try "Rom to secondary FS" "Zip to secondary" (which would be wrong), etc?

 

[n1nj4Lo]

Is there a proper way to flash addons and extras? My rom is sec fs, I've tried flash 4.2 camera and aroma to sec fs as zip in that method, but they don't seem to take, I even tried enabling sec fs before flashing and still nothing.