This guide is show you how to install second OS in SDCard, so you can have two complete separate OS (each have their own /system, /data and /cache), this will be useful if you want to try out a new ROM or a new version, like CM or latest Stock build etc. I have pre-build 2 ROMs in this guide. and list the instructions of how to do it in post #2.
The whole method is just an implementation of @SHM (Modding.MyMind) guide that inside the post here, so all the credit goes to him:
http://forum.xda-developers.com/showpost.php?p=62460895&postcount=325
Highlight of the steps:
1. Partition a SDCard (32GB or bigger) to have 3 ext4 partitions after regular FAT32 partition
2. Flash two customized flashable zip in twrp so that:
boot image flashed to /dev/block/mmcblk0p18 (regular boot partition)
system image flashed to /dev/block/mmcblk1p2 (sdcard)
The boot image contains the fstab file, it has been updated to use partitions on sdcard as the /system, /data and /cache for the 2nd OS.
And of course, the flashable zip has updater script changed so that, it will flash they system image to correct partition on SDCard.
Note / Limitation:
1) After boot to 2nd OS on the SDCard, theoretically, while you are in Android OS, everything should work. The speed/performance may differ depends on the SDCard read/write speed.
2) TWRP, except flash the zip to install the customized system image to SDCard, all other function will not work for the 2nd OS, The backup/restore function is still working on the primary OS /system, /data etc.
3) Boot partition (/dev/block/mmcblk0p18), this partition will decide which OS it will boot, and the boot image should corresponded to your OS system partition. So if you flashed above boot image for 2nd OS, it will find /system on SDCard and boot it. And if you flashed (or restore) your primary OS boot image, then it will boot to your primary OS /system.
Things you need before you start:
1. MT2L03 with Lollipop installed, TWRP installed, and have a backup of your primary OS (at least /system, and /boot partitions)
2. An empty SDCard that is 32GB or bigger, strongly recommend class 10 or faster. (16GB will work, then you don't have much external space left)
Steps to install 2nd OS to sdcard:
(Note, I will call the empty SDCard as sdcard#2, and your current sdcard in the phone as sdcard#1.)
1. Make a backup of your current OS using twrp, include at least /system and /boot, to your sdcard#1.
2. Install the PartitionWizard (files location below) on windows, and put the empty SDCard#2 to computer sdcard reader.
3. Launch Partition Wizard, and carefully re-partition your SDCard#2 to following:
(pls refer to xda wiki about the usage: http://forum.xda-developers.com/wiki/SD_card_partitioning )
1st Partition: FAT32 primary size: (Total size minus 15000MB), for example, for 64GB(60000MB) card, choose 45000MB
2nd: ext4 primary size: 1800MB (/system for 2nd OS)
3rd: ext4 primary size: 12500MB (/data for 2nd OS)
4rd: ext4 primary size: rest space, should be great than 200MB (/cache for 2nd OS)
Since partition 2/3/4 total size is 14320MB, thus the 1st partition size is (Total size minus 15000MB)
4. Apply the change, this will take some time (like 20 to 30min).
5. Once sdcard#2 is re-partitioned and formatted, unplug and re-plug sdcard#2 to windows again. Right click the sdcard drive letter, and click "Open" to open the FAT32 partition. ( I found double click the drive letter will give error if the FAT32 is bigger than 32GB, but right click and open works)
Copy two flashable zip (file location below) to the sdcard#2.
6. Reject the sdcard#2, and remove it from windows machine.
7. In Mate2 phone, go to settings, storage, and un-mount your current SDCard#1, after it is unmounted, take out the sdcard#1 and put it to a save place. Do not mess the two sdcards!!
8. Put in the sdcard#2 to the phone, and reboot to TWRP.
9. Install the two zip you download in step 5 from sdcard#2. Reboot.
How to go back to your primary OS:
a. Put in sdcard#1 to the phone, boot into TWRP, restore your /boot partition from the backup you took in above step 1. then reboot.
How to switch to the 2nd OS on the sdcard again:
a. Put in sdcard#2 to the phone, boot into TWRP, flash the "MT2L03_xxx_BootOnly.zip" you downloaded in step 5.
Files to download:
PartitionWizard in above step 2:
http://tinyurl.com/q62m68x
location: under Lollipop/SD_Partition_Tools
FileName: pwfree91.exe
This tools is mentioned in XDA wiki: http://forum.xda-developers.com/wiki/SD_card_partitioning
You can use any tool you know to do the re-partition, above tools is what I used and it works.
Customized flashable in zip in above step 5:
http://tinyurl.com/q62m68x
location: under Lollipop/OS_on_SDCards
FileName:
If you want install B309 as 2nd OS, please download "MT2L03_B309_DBoot_BootOnly.zip" and "MT2L03_B309_DBoot_SystemWithRoot.zip"
If you want install CM12 as 2nd OS, please download "MT2L03_CM12_0820_DBoot_BootOnly.zip" and "MT2L03_CM12_0820_DBoot_SystemWithRoot.zip". (Please note the GApp is already included in the zip)
Attached two screenshot of the partition tool, one for 32GB, one for 64GB. Please note though the pic showing in GB, but when config the size, please use MB to make sure the partition size is accurate and big enough.
//reserved
I am not sure how many people is interested in dual boot, so for now, I have pre-built B309 and CM12 only.
In order to build a customize ROM for installing in SDCard, as detailed in SHM original post, two steps are required:
1) For Mate2, after split the original boot image, and unpack the ramdisk, only need following cmd to update the fstab:
cd ramdisk
sed -i 's/platform\/msm_sdcc.1\/by-name\/system/mmcblk1p2/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/userdata/mmcblk1p3/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/cache/mmcblk1p4/g' fstab.qcom
Then repack it back to boot2.img. Please note the un/repack boot image tool need support DTB section.
2) Then in the updater script of /META-INF/com/google/android/updater-script, install system.img to /dev/block/mmcblk1p2, and still install the new boot2.img to /dev/block/mmcblk0p18.
@SHM, Unfortunately, many tools mentioned in original post, the Aparted tool, and the android binary mkbootimg etc all have problem running under Lollipop, so for now, I am doing all the ROM modification under linux.
Lol. You just had to do it. Lol awesome work. And you picked up on that fast. Thanks Xordos.
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
MikeyLee said:
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
Click to expand...
Click to collapse
I think if huawei mention 64gb probably because they didn't have 128gb to test when they release the phone. 128gb has nothing special compare with 64gb card. But I could be wrong since I don't have 128gb.
For general use, no need to partition 128gb card unless you want to do something like this thread.
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
SHM said:
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
xordos said:
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
Click to expand...
Click to collapse
Yea, it's pretty nice. You can even modify the TWRP recovery for use with making backups and restoring to each Rom specific to their partition. Look at TWRP Unified and check out it's script inside the ramdisk. Modify the script to check some stuff and tell it which fstab to use . This way when you jump back and forth between roms just by the boot.img you flash TWRP will automatically recognize the change upon it booting up and target the partitions properly when you make a backup/restore. Put some thought into all of this and I am sure you could take this thread a bit further.
There are projects out there that are designed for multibooting on android devices but you would need to port one of them.
Sent from my C525c using Tapatalk
Just an update that the AParted app works for Lollipop now. Tested it out on my external sd tonight by resizing my fat partition without losing any of my contents and adding additional partitions with multiple filesystem's such as f2fs and ext4. Quick and effective .
Sent from my Ascend Mate 2 using Tapatalk
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Can't waiting.
MT2-User said:
Can't waiting.
Click to expand...
Click to collapse
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
You run all three (or four including stock one)?
MT2-User said:
You run all three (or four including stock one)?
Click to expand...
Click to collapse
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Could they or some of them share Data?
MT2-User said:
Could they or some of them share Data?
Click to expand...
Click to collapse
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
oh ic
MT2-User said:
oh ic
Click to expand...
Click to collapse
The app implements this feature but I'm working it out if that makes you feel better lol.
Sent from my Ascend Mate 2 using Tapatalk
Damn nice work SHM.. Congrats. And thanks!
Moody66 said:
Damn nice work SHM.. Congrats. And thanks!
Click to expand...
Click to collapse
I have it working %100 now. Its 3:35 am where I am at so time for bed. Sharing apps works as well between roms.
Sent from my Ascend Mate 2 using Tapatalk
Related
I had downloaded a version of this file from a post embedded deep inside one of the threads over here (sorry can't find it right now), but upon examination of its contents, I discovered some issues:
1. The checksums on the files in contained in the the original zip file showed that B&N had at least two versions of 1.3.0 update you can download from them, and the zip I got contained an older version so I put in the latest files in there.
2. There were unnecessary files included inside the original zip file, I deleted those, and only included what was needed.
3. There were errors in the script syntax, which I corrected, so that the proper commands are run during the update, and the proper sed substitutions are made during the editing of the unpacked init.rc inside the ramdisk.
What this zip will do is replace any older version of a B&N ROM on the alternate eMMC partitions of a dual booting configurations to the latest versions. This will prevent B&N from pushing the 1.3.0 update to you OTA, and messing up your dual boot setup. Just put the zip on your sdcard, boot into CWM recovery, and apply the zip. I apologize in advance for not giving credit to the original creators of the scripts here.
Note: There have been two different protocols for a dual booting u-boot.bin, with an older one relying on the files u-boot.altimg, and u-boot.altram to specify the names of the secondary boot ramdisk and kernel, and a newer one assuming that they are named uAltRam, and uAltImg respectively. This update conforms to the new u-boot.bin protocol. If you are still using the old one, you will have to get root access to /boot and edit the two files to point to uAltRam and uAltImg.
So if you want try it out, here it is:
http://www.mediafire.com/?gcrpzzc0kdoxcjx
MD5 Sum: 51e24c1e5eff11ba5ea481a63f7404eb
Update
I have now uploaded files for B&N Update 1.4.1.
The first file (MD5 Sum: 4ff1d9764663278c3f51e2e2c9d841a6) is meant to update a pre 1.4.1 Stock B&N ROM on secondary /system through CWM:
https://rapidshare.com/files/52135913/secondary_update_NC_stock_1_4_1.zip
The second file (MD5 Sum: c1506816fbfb8c419fbbc4afe1b12887) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM without messing with recovery;
https://rapidshare.com/files/869435270/primary_update_NC_stock_1_4_1_keep_CWM.zip
The third file (MD5 Sum: ab1307c55a2c35c91d339c8037ce9a78) is meant to update a pre 1.4.1 Stock B&N ROM on primary /system through CWM, replacing recovery and all:
https://rapidshare.com/files/2059644016/primary_update_NC_stock_1_4_1.zip
None of these files will wipe user apps and data, so if you wish to do that, boot into recovery and wipe from there. [This will work on primary /data partition only]
Please note: If the B&N Stock ROM is rooted, you will lose root upon updating.
Thanks!
This worked beautifully! I flashed it from my sdcard after booting into CWM on my primary partition on emmc.
I'm betting you got the original from jasoraso in this dual boot thread: http://forum.xda-developers.com/showpost.php?p=17122342&postcount=142
What I would love is a straight CWM-flashable 1.3 ROM, to include in my up-to-date (for now) guide for setting up the dual boot, rather than having to set up and move 1.2, then update to 1.3.
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Sent from my SAMSUNG-SGH-I897 using XDA App
rajendra82 said:
That is possible to do by combining three of the steps. You need commands from the scripts from the prepare dual boot zip to resize /media and create the secondary system and data partitions, then the part of the script from the file that copies the contents of /data from primary to secondary and replaces u-boot.bin , and then my file which formats secondary /system and puts 1.3.0 there, and copies the latest kernel and patched ramdisk onto /boot. I can put such a file together, but I wouldn't be able to test it. The Nook belongs to my wife, and and you get the rest of the drift.
Click to expand...
Click to collapse
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
rajendra82 said:
PS - You can use my file as is after running prepare dual boot and copy stock to secondary. It is not necessary to update secondary to 1.2 before going to 1.3.
Click to expand...
Click to collapse
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Taosaur said:
Wait...what? What I'm talking about is a 1.3 zip made to work with CWM and in no way doctored to account for dual booting, just like the 1.2 zip one would otherwise use.
Click to expand...
Click to collapse
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Taosaur said:
Have you tested this theory? I found that when I did not register my B&N install while it was on the primary partition, I was unable to boot into it on the secondary partition.
Click to expand...
Click to collapse
No way to get around having to register the primary partition image first. Once that is done it could be moved to secondary and then updated straight to 1.3 instead of going 1.2 first.
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
yelloguy said:
I have a dual boot eMMC NC. I am not sure which setup I use but the last time I updated the CM7 nightly, I lost the dual boot until I installed the u-Boot again. I suspect I have the setup that looks for altFImg. So this is not going to work for me. I have 1.2 rooted which I use only occasionally. I am not even sure what is in 1.3 but I am curious.
Click to expand...
Click to collapse
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
rajendra82 said:
Are you talking about updating an already rooted 1.0/1.1/1.2 Nook Color. I am sure the scripting to do that is exactly the same as what is in the 1.2 zip file. Just replace the 1.2 files inside the zip with the equivalent files from the 1.3 update. Make sure the portions which install su and busybox are included, and build.prop spoofig is applied. I am not sure it is worth it building such a zip file though. One is better off just applying the B&N update, and then rerooting with manual nooter. What I created was for people that have already doctored the setup for dual booting. In such a case, the B&N update would either fail, or would replace the primary partition instead.
Click to expand...
Click to collapse
I wouldn't know what to change and what to leave alone, myself, but I think you're making this more complicated than it needs to be. I'm talking about installing 1.3 using CWM, regardless of how the device is partitioned or what was on the primary partition previously. Like the files in this thread, but 1.3: http://forum.xda-developers.com/showthread.php?t=1050520.
I understand that you were just cleaning up jaso's update-dualboot-to-1.3 file. I used the original and it worked fine, but it would have saved me a couple steps (and would be more useful in a guide for setting up dualboot) to simply install 1.3 rather than 1.2 to the primary partition when setting up. The reason I started with 1.2 is because it is the most current stock ROM available for CWM. What I would like is to avoid a historical re-enactment of stock OS development altogether. A general-purpose, CWM-flashable 1.3 ROM would be broadly useful, but is so far lacking as far as I've seen.
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.
2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.
3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.
I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Taosaur said:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://forum.xda-developers.com/showthread.php?t=1050520
Click to expand...
Click to collapse
Then the best bet is two step process:
1. Wipe device and restore to factory stock.
2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.
Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.
It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
rajendra82 said:
All you need to do is boot into CM7, mount /boot as root, and then rename uFImg to uAltImg, uFRam to uAltRam, and then change the text inside u-boot.altimg and u-boot.altram to point to the new names instead of the old ones. This will keep you dual booting under the old u-boot.bin, and even after a new protocol u-boot.bin (like that installed by CM7) gets pushed to your Nook Color. Once you have done that, you can update the secondary to 1.3 using my zip file if you want.
Click to expand...
Click to collapse
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
rajendra82 said:
1. Wipe device and restore to factory stock.
Click to expand...
Click to collapse
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------
yelloguy said:
You lost me at mount
Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.
With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.
Thanks for your help.
Click to expand...
Click to collapse
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Taosaur said:
I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
Click to expand...
Click to collapse
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
Click to expand...
Click to collapse
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
yelloguy said:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.
The fix is simple: to rename the files. But I need to know how before I take the plunge.
Click to expand...
Click to collapse
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:
mount /dev/block/mmcblk0p1 <full path to the directory you created>
4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:
u-boot.bin which is the bootloader
u-boot.bin.stock which is the backup of the old stock bootloader
uImage and uRamdisk which are your primary kernel and ramdisk
uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)
u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam
5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.
6. Reboot as usual into primary or secondary.
Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.
Sent from my SAMSUNG-SGH-I897 using XDA App
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
Taosaur said:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:
such files exist for past stock versions
those files are in use
files like yours are used to work around the non-existence of up-to-date stock zips
If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?
Anyone?
Click to expand...
Click to collapse
I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------
Taosaur said:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
Click to expand...
Click to collapse
It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
rajendra82 said:
In order to rename the files, you can do the following:
1. Boot into CM7 (or any other place where you have command line root access)
2. Create a temporary directory at a location where you have read write access.
3. Type su in a terminal session to gain root access and then mount mmcblk0 at the temporary location you created using the command:
mount /dev/block/mmcblk0 <full path to the directory you created>
Click to expand...
Click to collapse
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
yelloguy said:
I get an error:
mounting <paths> failed: Device or resource busy
Any ideas?
Click to expand...
Click to collapse
I see a typo in my command (stupid Swiftkey X). It should be:
mount /dev/block/mmcblk0p1 <some directory>
Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
rajendra82 said:
Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter will lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.
Click to expand...
Click to collapse
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.
Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).
Hello you DualBooters and Triplebooters out there!
SDCacheMount for SD-Roms
Well, this idea came to me because many users of my triple-boot SD were getting tired of the rebuilding of system-cache when every time they had to switch between roms. What I have here is a small script that will install to /system/etc/init.d The script will run at boot time and create a 100mb .img file to be used for /cache. This way each rom will have its own dedicated /cache partition so to say. This will also benefit anybody that dualboots (eg. EMMC / SD-Rom). I've prepped two different versions. One for my triplebooters out there and the other for anyone running a rom off an SD card.
Things to note:
-This will dd a 100mb .img file to your /sdcard partition of your sd-rom on first boot. What this means is that before the system progresses any further the img file needs to be created so that the /system can use it as the /cache partition.
-It will sit at a black screen for up to 1 minute possibly. So please be patient!!!
-The dd'ing of the .img only happens on first boot. So once the cache .img is created. Boot time will be normal on successive boots.
-Make sure you have enough space on the /sdcard partition of your sd-rom.
-So for Dualbooters you will need at least 100mb free
-For Triplebooters you will need at least 200mb free
-Now you can switch between EMMC roms and SD roms without having to wait for /cache to rebuild every single time.
DOWNLOAD:
DUALBOOTERS ( EMMC / SD )
**You should be able to flash this from a standard CWM Recovery or rename the .zip file to begin with "update-" for Verygreens method.**
SDCacheMount_DualBooters.zip
Click to expand...
Click to collapse
TRIPLEBOOTERS ( EMMC / DUALBOOT-SD )
**You should only use the CWM Recovery that is included with my Dualboot-SD**
SDCacheMount_TripleBooters.zip
Click to expand...
Click to collapse
Big thanks to:
DizzyDen for helping me out with the script
Shumash for troubleshooting it for me
Inportb for some guidance
HacDan for his sense of humor
Hope this helps a few of you Nookers out there!
Thanks,
Racks
Reserved?!
Great job! gonna have a try on this
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
RASTAVIPER said:
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse
The advantage of the script is that each AOSP will have its own dedicated cache and not all be utilizing the same space for all the cache.
RASTAVIPER said:
So the main advantage of this script is smaller booting time?
And this is the case when you switch Roms only between emmc and sd or also 2 different roms from same sd?
Unleashed from my Nook Color at 1.2G
Click to expand...
Click to collapse
The most obvious effect is that booting between the various ROM's is seamless (except for the minimal wait at the blank screen) and fast. It makes switching between the AOSP's very easy. The less obvious, behind the scenes effect is as Dizzy describes.
It should be noted that if you flash an updated or newer ROM, you will also need to reflash the SDcacheMount.zip.
shumash said:
The most obvious effect is that booting between the various ROM's is seamless (except for the minimal wait at the blank screen) and fast. It makes switching between the AOSP's very easy. The less obvious, behind the scenes effect is as Dizzy describes.
It should be noted that if you flash an updated or newer ROM, you will also need to reflash the SDcacheMount.zip.
Click to expand...
Click to collapse
Yes correct, thank you. I'll make note of that in the OP. Also note that once the .img cache is created, although you have to reflash the SDCacheMount after flashing a new rom. It won't have to create a new .img. The script will detect if one exist already and if so, proceed to boot. But if you don't flash the SDCacheMount right after flashing the new ROM. /cache will default back to /emmc
-Racks
I got a nook tablet recently, i registerested it already which i understand you have to do... now i want to backup everything and run regular android as in not B&N version. Im not sure which way to go from here, i see there is an sd option and a regular option?
i was reading this
http://forum.xda-developers.com/showthread.php?t=1439630
as i was getting ready to do it, i started to double think if it was what i wanted.
i want to be able to run the latest android rom possible.
appreciate any help, thanks.
The process you are linking to is very simple and "safe". With the card you create you can startup CWM (ClockWorkMod - utility for flashing and backup and more) and not only root your device, but also make a backup, should you want to go back to where you were prior to flashing whwaever you decide to flash.
The rooting alone lets you install apps from other sources than BN. I think rooted stock tweaked a bit isn't too bad to run actually!
To try out other options completely risk free you can run CM10 (ICS) from an sd card. I do that while I wait for CM10 to be more stable/bug free. It runs incredibly well from sd, and I doubt performance will be greatly enhanced onec I install it internally (as I probably will do at som point.
To run from sd card you don't have to root the device unless you want to.
Great guides for making a sd-card are here and there. For example http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
The first thing I would suggest is to make a bootable recovery SD card using the process and files from here (use the MLO_u-boot_flashing-boot.rar and one of the packages with sdcard.zip suffix), and backup your current stock config and safely save/archive the backup folder -- you'll be glad you have it around one of these days. Make sure that you also keep a copy of whichever recovery program version you choose to use together with the backup folder, since different recovery programs and versions use different backup file archive formats.
If you want to root the NT I would recommend using the update.zip referenced in this post (by liquidzoo) which is more up-to-date than the rooting package you saw (I had used the latter version and had problem updating its Google Store app). Just put this zip package on the same recovery SD card and use the recovery program to install it.
Having tried out the rooted form of the NT for about a week I think it's just marginally better than a stock NT -- there are just so many common apps that are no longer available for the NT's Android version. You would be much better of investing time in going full-fledge CM10, either running off an SD or natively. If you choose to go native CM10 you can revert back to stock using the backup discussed above.
Can you please verify if I am doing the correct thing
@digimax,
I just got my Nook Tablet today, so just wanted to be very clear to make the backup of the current stock config. Here's what I propose to do. Please correct me if I am doing anything wrong.
1) As per you post, I downloaded 3 files
a) MLO_u-boot_flashing-boot.rar,
b) CM9-10_CWM_V6.0.1.2_8-16gb_tools_sdcard.zip,
c) CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip
2) Unzip all the above 3 files
3) Rename the CWM file to recovery.img
4) Rename the TWRP file to altboot.img
5) Copy recovery.img and altboot.img and MLO, flashing_boot.img and u-boot.bin to the root of the SDCard.
6) Insert the SDCard into the Nook Tablet and boot the Nook into one of the recovery and make a backup.
Please let me know if this is the correct procedure.
Thanks!
It looks right, make sure that your boot partition is Primary FAT32 (type 0x0C) with LBA and Active flags set (you can check and set all this using a partition management tool such as MiniToolPartition).
Also, to boot into SD: just turn off the NT and insert a powered-USB cable, and the NT will boot up after a few seconds (assuming that the SD is bootable).
Once CyanoBoot comes up, hold the "N" button to get the boot menu from which you can select one of the two recovery programs.
a lot of this is going way over my head, i need to make sure i go slow and read carefully.
thanks for all the info.
Snjperman said:
a lot of this is going way over my head, i need to make sure i go slow and read carefully.
.
Click to expand...
Click to collapse
Remember that you can make CM10 run totally risk free from am SD-card. That way you can have a smooth running device to explore while you keep reading up on diffrent options. That's what I do! The Tablet doesn't even have to be rooted to do this (mine is though).
asawi said:
Remember that you can make CM10 run totally risk free from am SD-card. That way you can have a smooth running device to explore while you keep reading up on diffrent options. That's what I do! The Tablet doesn't even have to be rooted to do this (mine is though).
Click to expand...
Click to collapse
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Snjperman said:
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Click to expand...
Click to collapse
This is the website I used:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Look through the comment sections for further clarity on the process.
If that is beyond you, then I suggest getting a pre-made image for the size of SDCard you have and burning your own image. Google AndroidforNook or N2A for the website links.
Snjperman said:
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Click to expand...
Click to collapse
To install and run CM10 off SD card: http://forum.xda-developers.com/showpost.php?p=35245689&postcount=7
To install and run CM10 internally on NT: http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
attiato year
thank you guys so much!
I have an 8gb nook tablet that I rooted probably 2 and a half years ago and haven't changed anything on it since. I am wanting to undo and update to current root and flash a 4.4 rom like on my phone. What is the best way to go about this? I know how to unroot, I just need to know the best way to root currently. Thanks.
Custom ROMs like CM comes with built-in root capability, and moreover once installed replaces completely the existing ROM currently in place (be it stock ROM, rooted stock ROM, or another custom ROM). As such, there is no need to root (or re-root) prior to flashing a custom ROM. See http://forum.xda-developers.com/showthread.php?t=2575489 for more background info and pointers.
Cool, thanks for the reply and links. I have some reading to do.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also? Will it work for CM11 also?
ryknow27 said:
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also?
Click to expand...
Click to collapse
Yes.
Will it work for CM11 also?
Click to expand...
Click to collapse
It should work (with the usual caveat YMMV). Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later (in step 2(b) of http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123); you can find the SD version of TWRP 2.6.3.x at http://techerrata.com/browse/twrp2/acclaim. You also need a recent Gapps version corresponding to the CM11.
Alternatively, if your NT is already on CM10.x (as my NT was), you can:
download CM11 ROM and the corresponding Gapps zip files onto your NT (user content media partition).
use SD based recovery to flash a flashable emmc CWM zip (http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2) or flashable emmc TWRP zip (http://forum.xda-developers.com/showpost.php?p=49111924&postcount=8) into emmc.
remove SD then boot onto emmc recovery (which is installed in step 2) and use it to install the ROM and Gapps zip files downloaded in step 1.
Remember to use SD based recovery to backup your current ROM before flashing CM.
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
ryknow27 said:
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
Click to expand...
Click to collapse
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
digixmax said:
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
Click to expand...
Click to collapse
I did try 7-zip first and it didn't work. I may have just done something wrong. I'll try it again. Thanks for all the help.
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.