Related
OK so i know a lot of members are intrested in Dual booting their galaxy S2, so i have decided to complice a list of all the dual boot options i can find and have found. I have found two ways as it stands now, but my search has not been that deep yet, so here are the two ways for now and i hope to add more to the list soon.
SGS2 Dual-Boot Setup (LolBoot) - Ok so the first is an app by Hellcatdroid that you can download from Google Play. It only supports GB roms for now, but their is hope that he will put his PSvita down and continue to work on this great app.
Links
Thread
Google Play
SiyahKernel v3.1beta1 Kernel - So option 2 is a kernel from Gokhanmoral, the kernel is stable but the dual boot side is still in beta. This dual boot kernel is working with ICS roms (not GB), Gokhanmoral has tried a dual boot on stock and cm9 and this combo is working, he is pretty sure it will work with MUIU roms. The members on this thread will start to tell of other working combos they have tried, so give this one a go it is looking very good.
Links
Thread
Blog - The blog includes a changelog, and the download link for his kernel
Here is a guide thanks to Phistachio on how to dual boot using Siyah Kernel
[GUIDE] How to Dual Boot using the Siyah Kernel
Here is a fantastic guide, FAQ writen by droidphile for the use with Siyah kernel, it is a fantastic FAQ, so if you use it please go and thank him here -
Dual Booting FAQs
Here are some dual-boot faqs. Some answers may not be 100% true at present since Gokhan is still working on enhancing dual-booting and implementing all the placeholder features in touch recovery dual boot options.
1) So what's dual booting?
A. Option to boot into either two ICS roms - aosp or sammy. Immediately after boot logo is displayed, you will have a 3 seconds time-out where you can boot into secondary rom by pressing the home key. To boot into primary rom, wait for 3 seconds time-out to complete. If you don't like to wait - touch the screen, or press a volume key, or press power key during time-out.
2) What's the basic architecture behind dual booting?
A. Any rom will have /system, /data, /cache partitions and requires a kernel to boot. Primary rom has all these partitions on the same location as if you were single-booting. Secondary rom uses a hidden partition (/dev/block/mmcblk0p9) to be used as /system (it's /dev/block/mmcblk0p12 for primary rom). Second rom uses sdcard to store /data and /cache partitions. They're stored in /sdcard/.secondrom directory as mountable ext4 block device images (data.img and cache.img).
Kernel partition is shared, so same kernel boots both the roms. If you switch from Siyah to a different kernel dual booting will not be available even though you have a clone of secondary rom. Internal sdcard, ofcourse external plastic sdcard, /efs, /emmc, other kernel related virtual filesystem directories, etc are shared among roms.
3) I have just one rom now. How do i setup one more rom to dual boot?
A.
-To use current rom as primary: Assuming the other rom is downloaded and copied to phone memory
i) Flash latest Siyah that supports dual boot.
ii) Nandroid backup your existing rom.
iii) Full wipe, install the rom you need to dual boot into.
iv) Boot into that rom, perform initial setups, flash whatever zip you need to flash on that rom - gapps, themes, mods, etc. (Because after setting up dual boot you don't have an easy way to flash zips onto second rom. Remember /system and /data partitions are different for both roms)
v) Flash latest siyah on this rom.
vi) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary". Be patient and wait about 6-7 minutes.
vii) Within recovery, restore nandroid backup.
viii) Just to be sure, flash latest Siyah again.
-To use current rom as secondary: Assuming the other rom is downloaded and copied to phone memory
i) Flash latest Siyah that supports dual boot.
ii) Boot into recovery, under dual-boot options, select "Clone Primary ROM to Secondary".
ii) Without exiting recovery, Full wipe, install the rom you need to use as primary rom.
iii) Boot into that rom, perform initial setups.
iv) Flash latest Siyah just to be sure.
Now you have two roms. Press home key to boot into second rom when time-out is shown.
4) How much time was it to clone a rom?
A. There's /system, /data/ and /cache to clone. 2 GB data + 103mb cache + 513 mb system = 2.6 gb
Shell prompt read speed = 7mb per second.
Total Time = 2.6*(1024/7) = 380 secs = 6/7 minutes.
5) If i reboot to recovery from power-off state using 3 button method, to which rom's recovery it's booted into?
A. Unified kernel, same recovery. And remember - flashing zips to second rom is not possible.
6) Any solution to flashing zips to secondary rom?
A. Not until secondary rom is "converted" to primary rom. If you know what the updater script in the zip is doing, you can do that manually using Root Explorer (replacing/copy files, setting permissions, etc).
Else, temporarily make secondary rom the primary rom. Goto recovery, dual-boot options, "Clone Secondary Rom to Primary". Now your second rom becomes primary rom. Flash your zips. When you're done, restore nandroid backup of the other rom to make it primary as before.
7) Should i have same versions of kernels on both roms?
A. Flash kernel from any rom. Both uses the same kernel partition anyway.
8) Will i get a prompt to dual-boot if i'm not using dual boot, as in i haven't cloned any rom to use as secondary?
A. NO
9) I don't like waiting for 3 seconds to boot into primary rom.
A. Touch the screen immediately upon prompt.
10) How do i swap primary and secondary roms?
A. Goto recovery, dual-boot options, "Backup secondary rom"
Under original Backup and Restore option, "Backup" to backup your primary rom.
"Restore as secondary rom" or "Restore as secondary rom from internal sd" and select the nandroid backup of what was actually your primary rom.
Then under original Backup and Restore option, "Restore" to restore the rom you backed up as secondary.
11) USB mass storage works?
A. Only external sd is mounted for second rom atm. MTP will work for internal sd also. Both will be mounted for primary rom.
12) If i had the same /data partition shared between roms, i could use same apps on both roms.
A. Data partition can not be shared as they're incompatible between roms. (Sometimes dev asks you to perform full wipe even if you're switching between versions of the same rom right). Even if they were shared, separate dalvik caches has to be used and hence every boot will take a long time to rebuild dalvik.
13) How to undo dual booting?
A. Use "Remove secondary rom" from dual-boot options in recovery.
14) How to remove secondary rom if "remove secondary rom in recovery" fails for some reason?
A. Format /system2 directory partition, remove data.img and cache.img under /sdcard/.secondrom directory manually by booting into primary rom.
15) How to upgrade primary rom?
A. As usual, goto recovery, wipe whatever you need to wipe and install the new version.
16) How to upgrade secondary rom?
A. Temporarily convert secondary rom to primary (like explained above), install new version and revert primary back to secondary.
17) How to replace secondary rom with another?
A. Perform the steps to setup dual boot as if you had only one rom which is going to be used as primary rom.
18) How to replace primary rom with another?
A. Normal procedure - wipe, install from recovery.
19) Can i have both aosp roms/both samsung roms/first aosp, second samsung/first samsung,second aosp?
A. Yes
20) Can i have one GB rom and second ICS rom?
A. No
21) Why?
A. Kernel partition is shared between roms. Dual boot functionality is implemented in ICS kernel. ICS kernel can run only ICS roms.
22) Are init.d scripts and extweaks profiles shared across the roms so that i can make changes by booting into any rom and the other rom automatically inherits the settings?
A. NO. Roms have differet /system partitions so different init.d directories. Roms uses different /data partitions and extweaks profiles are stored under /data/.siyah. So you gotta configure both separately. Initramfs scripts are shared anyway since both rom uses the same kernel.
23) So if at all i format /sdcard, my second rom is gone?
A. Yes
24) Is the size of /system partition of secondary rom re-sizable from user space?
A. NO
25) Can i have different kernels for the two roms?
A. NO
26) What're the options under dual-booting in touch recovery?
A. i) View Status
Displays secondary rom info if found.
ii) Clone Primary ROM to secondary
First time, you will have only one rom. You may clone it as secondary rom (so that another rom can be used as primary by nandroid restoring)
iii) Clone secondary rom to primary
Whatever has been cloned as secondary rom is cloned to primary rom.
iv) Remove secondary rom
Deletes /system, /data and /cache partitions of second rom. You will have normal booting.
v) Backup secondary rom
Nandroid backup secondary rom to external sd.
vi) Restore as secondary rom
Restore any nandroid backup as secondary rom from external sd.
vii) Backup secondary rom to internal SD
Nandroid backup secondary rom to internal sd.
viii) Restore as secondary rom from internal sd
Restore any nandroid backup as secondary rom from internal sd.
ix) init second rom data
Initialize /data parition of secondary rom to resize the partition to make it bigger in case you run out of space for apps. Init also wipes all the data in /data partition. So your existing apps in secondary rom will be gone.
x) wipe second rom davik cache, xi) wipe second rom cache, xii) fix permissions in second rom - self explanatory
Click to expand...
Click to collapse
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running CM9 and Resurrection Remix ics v1.2 PRO[4.0.4]
This is what i have got for now, but i am always looking for more dual booting options, if anyone knows of any please let me knowand i can add it to this thread.
If you have found this thread usfull then please hit the Thanks button
Nice work again fella
You should request this and your other thread are made into sticky's
Also, im hoping these two threads will help to stem the flow of threads and questions for previously trodden ground
Keep it up dude
Thanks man, the XDA community has give me so much, I just want to give back. It would be nice to see these as stickies, maybe the FM would be kind enough to consider placing them on the sticky thread.
Sent from my GT-I9100 using XDA
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running CM9 and Resurrection Remix ics v1.2 PRO[4.0.4]
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running SensatioN ROM 3.3 ICS by Crysis21 as Primary and CM9 as Secondary.. can anyone tell me any app so that i can automatically sync both rom 's SMS, Phone log and Phone Contact.. i know manual process..
What are the pro's/con's of dual booting? Cheers
Sent from my GT-I9100 using Tapatalk
shareking said:
I am now running a Dual Boot galaxy s2, using Siyah Kernel by Gokhanmoral, i am running SensatioN ROM 3.3 ICS by Crysis21 as Primary and CM9 as Secondary.. can anyone tell me any app so that i can automatically sync both rom 's SMS, Phone log and Phone Contact.. i know manual process..
Click to expand...
Click to collapse
You can use Rom Manager to Extract the apps and data from your nandroid backup, or another app that does the same is Nandroid Browser, you can get both of google play. Just as a side note, you should get an automation sync of data when flashing a new rom, as google now store all you apps and setting in the cloud, if you check in your settings it should be under Backup and reset - back up my data - check the box, and you should have an auto sync for your next rom flash.
blade30p said:
What are the pro's/con's of dual booting? Cheers
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
For me it is just the chance to have a change never getting bored of the same rom, the con is using a dual boot that is still in better and is buggy at the moment, which may cause problems with your rom mainly the 2nd rom, also the storage of data is causing some people problems, but the thread is give good solutions.
Dual booting rocks. android rules...
Thank you for this guide
So there is an option to boot two GB ROMs but no ICS and now we can boot two ICS ROMs but no GB...
The third option should be... - you know it
Sent from my GT-I9100 using XDA
Probably get flamed - btw, I don't care one jot - but why on earth should this be stickied?
This isn't a guide, it's a post with two links to the relevant threads, where the discussion is going to be a lot more useful than anything here.
s.d. o'connor, your other guides are guides, and are very useful, for which my thanks. This one isn't.
Flame-retardant pants on - fire away.
My defence
B3311 said:
Probably get flamed - btw, I don't care one jot - but why on earth should this be stickied?
This isn't a guide, it's a post with two links to the relevant threads, where the discussion is going to be a lot more useful than anything here.
s.d. o'connor, your other guides are guides, and are very useful, for which my thanks. This one isn't.
Flame-retardant pants on - fire away.
Click to expand...
Click to collapse
Why would you get flamed for having an opinion, you are entiled to that, but here goes my defence. I could only but ask if it could be a sticky i didnt make it one, and the idea is to stop new threads being opened asking the question can you dual boot the galaxy s2. Also as more options of dual booting become avaiable then they can be added to this thread.
P.S I dont want people to get flamed for having a opinion, they have a right to that, as long as they put that across in a good manner.
You don't need a defence (unlike Leeds United, but that's another story).
Flaming is an occupational hazard here sometimes, especially if someone has the temerity to diagree with someone else. I'm way past worrying anyway.
On topic - I still don't think this deserves sticky status. You and others do. No problem. Each to their own. It's up to the mods anyway, not us.
No foul on you SD O'C because you've put together some really good threads, but if this is 'sticky worthy' standards have plummeted on XDA. Rapidly. As has been pointed out, there's a couple of links & pretty much no original content or anything that could remotely be considered a 'guide'.
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
okay, i am on dual boot. using LPQ as primary and cm9 latest nightly as secondary
and i note battery drain
MistahBungle said:
No foul on you SD O'C because you've put together some really good threads, but if this is 'sticky worthy' standards have plummeted on XDA. Rapidly. As has been pointed out, there's a couple of links & pretty much no original content or anything that could remotely be considered a 'guide'.
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
Click to expand...
Click to collapse
What post number is it and i can include it and give him full credit, i will of course ask first. Also i would like to point out this was never intended as a guide, more a point of ref.
P.S If LUFC would like to change his mind on this being a sticky then i would have no problem with this.
ashifr5 said:
okay, i am on dual boot. using LPQ as primary and cm9 latest nightly as secondary
and i note battery drain
Click to expand...
Click to collapse
Battery drain has been noted with the kernel, he has made a fix for most roms and combo's but he will need time as it is still in the early stages. Also when flashing a new rom this can alter the casuse battery drain, a full charge of the batter could fix this problem.
MistahBungle said:
Droidphile's excellent dualbooting post in the Siyah dev thread a few days ago, now that was a guide (and sticky worthy).
Click to expand...
Click to collapse
Here it is, for all the non-searchers.
Off-topic again - s.d.oconnor, to quote an earlier post from yourself:
s.d.oconnor said:
Thanks man, the XDA community has give me so much, I just want to give back.
Click to expand...
Click to collapse
If so, what's the "donate to me" banner doing in your signature? Just awaiting love and affection?
You've compiled some useful guides, but let's face it, your work has mainly been collating readily available links and other posts that any reasonable modicum of searching ability could accumulate.
Nothing in the site rules that forbids you to ask for donations, but for what you've done - especially taking into account that you've been a member here for two months - I can think of an awful lot more contributors ("recognised" or not) whom are far more worthy of donations than yourself.
The "giving back to the community" spiel is very valiant and honourable, but you want donations. Fine, sure you've got some too. But don't dress it up behind the "giving back" line - not exactly sincere, no?
Again, I'm not flaming/trolling - merely my opinion.
B3311 said:
Here it is, for all the non-searchers.
Off-topic again - s.d.oconnor, to quote an earlier post from yourself:
If so, what's the "donate to me" banner doing in your signature? Just awaiting love and affection?
You've compiled some useful guides, but let's face it, your work has mainly been collating readily available links and other posts that any reasonable modicum of searching ability could accumulate.
Nothing in the site rules that forbids you to ask for donations, but for what you've done - especially taking into account that you've been a member here for two months - I can think of an awful lot more contributors ("recognised" or not) whom are far more worthy of donations than yourself.
The "giving back to the community" spiel is very valiant and honourable, but you want donations. Fine, sure you've got some too. But don't dress it up behind the "giving back" line - not exactly sincere, no?
Again, I'm not flaming/trolling - merely my opinion.
Click to expand...
Click to collapse
Ok, the banner donate to me has been their since i joined as you are giventhe option to include one, i was new (still am), i have not recived any donations, and if i did they would be used to go back to the XDA website, if it offends anyone i will remove the banner. Also if any mod belives that i am not worthy of my title and that my guides are not of the standard that is very good then they can by all means remove them from any sticky they may be on, and remove my title if they see fit.
I know you are saying that you are not flaming me, but it seems to be moving in that direction. I know i have only been here a short while but i belive that what i have done is not that bad of a standard, in the short time i have been here.
This is a modified ClockworkMod recovery for the Xiaomi Mi3 tegra4 (pisces). It includes some changes from M1cha's CWM for Mi2 to support the dual-system design of the Mi2 (same thing on Mi3), while leaving out "true dualboot" feature for now. I think TDB is useless as long as there is only MIUI available for this device. See source for details.
Working so far:
adbd in recovery
nandroid backup/restore, including system1, boot1
running any update.zip (including AROMA)
choose system to install update to
set active system
Anything else untested.
Installing:
(1) Flash using fastboot:
adb reboot-bootloader
{wait for fastboot screen}
fastboot flash recovery cwm-*-pisces-*.img
(2) Boot new recovery:
Type fastboot reboot and press enter while holding Vol+ key should take you directly to CWM.
(3) Let CWM disable recovery flashing (offered automatically when selecting reboot)
I didn't test this method so far (feedback welcome) -- in case it doesn't work, try this instead:
Alternative installation method:
(1) Disable automatic recovery reflashing (while running MIUI, requires busybox installed and a root shell, eg "adb root; adb shell")
Code:
mount -o remount,rw /system
chmod 444 /system/etc/install-recovery.sh
mount -o remount,ro /system
(2) Flash using fastboot
Code:
adb reboot-recovery
{wait for fastboot}
fastboot flash recovery cwm-*-pisces-*.img
Use at your own risk, right now this is largely untested
Download: cwm-6.0.3.7-pisces-a20131110a.img
Older Releases: cwm-pisces
Source:
Device tree (stub)
Recovery
Note: As there's no kernel source available yet, the kernel is left out of device tree. For building yourself, extract stock kernel from your boot image and place it in the device tree (filename "kernel")
History:
a20131110a:
Integrated all fixes by M1cha that are not related to TDB -- backup/restore of boot1 now working
Set default storage to /sdcard/0, nandroid backups now accessible via MTP
a20131110:
Integrated boot-system selection and recovery-check for both systems
Used biggest font for readability on fullHD display
a20131109a: Integrated the first dualsystem support modification by M1cha
a20131109: Unmodified CyanogenMod source, no dualsystem support at all
This is my future phone.. So thanks
Thanks, but keep in mind this phone comes with 2 different SoCs, Tegra4 and Snapdragon800 -- this here is for Tegra4, which is found in TD-SCMA version... maybe I should update OP to explicitly state that.
Btw, it's not complete yet, it doesn't flash original ROM updates correctly, I think thats because named partition nodes are missing ... I'll add support for these soon
Gesendet von meinem MI 3 mit Tapatalk
No third-party ROM MI3 brothers now seems less useful but thank you
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://115.com/lb/5lbdstd81pd#
recovery-clockwork-cwm-6....3.7-pisces-a20131110a.zip
115 network disk packs code：5lbdstd81pd
yao85930101 said:
No third-party ROM MI3 brothers now seems less useful but thank you
Click to expand...
Click to collapse
Well, I need some time to improve it, because there's two possible uses with stock ROM:
- nandroid
- re-flashing mods after upgrade
I'm especially interested in the second, because I want some apps to reside in /system/app permanently. Unfortunately, it doesn't work yet, as it doesn't flash official upgrades (right now need updater app for this) -- as I said, probably the named device nodes for partitions, need time to work on this.
For 3rd-party ROM ... There COULD be. I assume stock kernel is somehow based on this:
http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=tree;hb=refs/heads/linux-tegra-nv-3.4
(seems to contain platform drivers for tegra pluto board, has android drivers and it's even exactly the same linux version)
So, it COULD be possible to build a working kernel from these sources. Well, I didn't even get anything to boot far enough for giving useful error info to me But if you want to "waste" hours and days, please try yourself A custom kernel would be an excellent start.
yao85930101 said:
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://pan.baidu.com/s/1Dwmj9
Click to expand...
Click to collapse
Nice! :good: Is this installable from stock recovery, too?
A little remark: I'd prefer not to modify /system automatically from the installer but better boot directly into CWM and then let the user decide. Of course thist would require rebooting to recovery from updater-script. I didn't do edify script for quite some time -- is this possible? If not, maybe we could throw together a little arm7 binary for the boot to CWM for some kind of "final" release. I'd consider thios CWM version "final" as soon as it can flash official updates (from xiaomi)
Oh look forward to updating you again Come on you are the best
However, a day to focus on the brothers really no way to track it?
Hello, I don't have time for this right now. I'll get back to the project probably after christmas.
But, as I said, it's probably the missing partition names -- so this SHOULD be fixable in the device tree, adding init scripts to the recovery (no need to modify CWM itself further). Feel free to clone the repo (AND you need an original kernel image extracted from the phone)
Any reason this wouldn't work on Tegra Note 7?
e8hffff said:
Any reason this wouldn't work on Tegra Note 7?
Click to expand...
Click to collapse
At least two.
1. The kernel. It's taken from an original Mi3 tegra phone, unfortunately, there are no sources yet from Xiaomi. Although it's the same platform, the chances this kernel would boot on any other device are low.
2. "Dual-system". I don't know much about the Tegra Note 7, but I doubt it has 2 system and boot partitions. Most android devices don't -- the Xiaomi phones are the only ones I'm aware of. CWM code in this zip is modified/extended to handle this (mostly taken from modifications done by M1cha for the Mi2). It won't work on a normal single-system device. In fact, there's no need to modify CWM source for a standard single-system device, a device-tree would be enough for building a working CWM recovery.
Zirias said:
At least two.
Click to expand...
Click to collapse
Ok thanks for the reply.
any progress on this work? is this CWM fully working now?
Don't Copy Others Work
If u Copy some ones Post Then Plzzz........... Mention
http://forum.xda-developers.com/showthread.php?t=2521125
new cwm but in chinese dor tegra 4
i have find these two but i think it is in chinese
http://4pda.ru/forum/index.php?showtopic=541742&st=5360#entry32916655
http://www.miui.com/thread-2069908-1-1.html
if any one could help and translate them to english we can have true dual boot and try the new custom roms for tegra 4 xiaomi
Android - 5.0 Lollipop for tegra 4 xiaomi but this must be in chinese too
http://www.miui.com/thread-2111749-1-1.html
Introduction
This is a collection of Tools and Resources for Flashing Mi2(s)(c).
MiFlash4Linux
https://github.com/M1cha/aries-image-builder
Core Recovery Package for MiFlash
This is a small package to Recovery MI2 from any bricked state. It has the following advantages over the official ones from Xiaomi:
They don't flash any ROM, just the core system(bootloaders, modem and recovery)
They are small which means both Download and Installation are faster
It directly installs custom Bootloader and TWRP. That means you easily get your device back to a modded status.
Please follow the official MiFlash guidelines for installation with the following differences:
the DLOAD config is called rawprogram_core.xml
the fastboot script is called flash_core.bat(or flash_core.sh for linux)
there's a script called flash_partition_table_and_core which is a alternative to flash_core.bat/sh.
It can be used to change the partition table.
USE THIS WITH THE CUSTOM BOOTLOADER INSTALLED BY ONE OF THE CORE PACKAGES ONLY. Xiaomi's bootloader will format your whole MMC device. THIS WOULD ERASE YOUR EFS AND YOU CAN'T MAKE CALLS ANYMORE
Changing the partition table
There are multiple packages available:
separated: Xiaomi's original layout with a virtual internal sdcard
separated_single: same as separated but without Dualsystem and bigger system partitions
unified: Xiaomi's new layout with /data/media support
unified_single: same as unified but without Dualsystem and bigger system partitions
unified_single_xiaomi: Xiaomi's version of unified_single
SkiFire13 said:
aries_core_unified_single.zip -> only MIUI > 5.4.x or M1cha's CM12.1 or latest AOSP5 works (only they can see Internal Storage, that now is a virtual sd-card in /data/media/0)
aries_separated_single.zip -> other roms
Click to expand...
Click to collapse
Installation:
Backup all your data(including internal sdcard, and EFS just to be safe)
if you don't use the custom Bootloader yet, flash this package using flash_core.bat/sh first. See the big red warning above for more information
flash the package using flash_partition_table_and_core.bat/sh
boot into recovery(which is TWRP now), recreate the filesystems for all partitions(system,data,cache,sdcard to ext4) in the wipe menu and reinstall your ROM.
Version Information
Bootloader: https://github.com/M1cha/mi2_lk/commits/LA.AF.1.1-02810-8064.0
TWRP: v2.8.7.0
core partitions: aries_images_5.7.16_20150626.0000.4_5.0_cn_a63cddccfa.tgz
Download links for Mobile users:
aries_core_unified_single_xiaomi.zip
aries_core_unified_single.zip
aries_core_unified.zip
aries_core_separated_single.zip
aries_core_separated.zip
XDA:DevDB Information
Flashtools, Tool/Utility for the Xiaomi Mi 2
Contributors
m11kkaa
Source Code: https://github.com/M1cha/aries-image-builder
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2015-07-27
First (as always)
Sent from my A0001
the singleboot packages causes the latest version of CM12 to fail booting because of SELinux enforcing. I'll upload a fixed package asap.
everything has been fixed and is up again.
Pls download everything again(especially MiFlash4Linux if u use that).
i think i will wait util the release of GRUB4Android....
acastrocab said:
i think i will wait util the release of GRUB4Android....
Click to expand...
Click to collapse
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
m11kkaa said:
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
Click to expand...
Click to collapse
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
On the top of the page just followed by the title, there is a "Download" tab, you could find the miracle at there ;p
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
ancics said:
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
Click to expand...
Click to collapse
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Hey M1cha, thank you! Great job!
I have some issues about the procedure:
1. I am not sure if already had a custom bootloader, so first i'll flash the package flash_core.bat :
- turn on mi2s in fastboot mode
- plug usb, device should appear in miflash(the program should be configured as the photo?)
- and click flash
- reboot phone, enter in fastboot mode again and do the same procedure with flash_partition_table_and_core.bat
Is that right?
It's easy to recreate the ext4 filesystem in TWRP? always used CWM....
m11kkaa said:
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Click to expand...
Click to collapse
Oh that's why, I'll download it from a computer, thanks!
Sent from my MI 2S using XDA Free mobile app
@m11kkaa: thnx for the linux tools/scripts, it made my migration from CWM to single-system partition + new bootloader + TWRP easier.
BTW, I just wanted to migrate and keep my current CM11 for the time being. I had to fight a bit with restore from backup because I was not aware of the incompatibility between CWM and TWRP, luckily enough it eventually was sufficient to:
reformat system, data and cache in TWRP
flash the old CWM temporarily and restore boot, system and data
flash TWRP again and make new backups.
Proposal:
It would be good if you can change the heading style of "Installation" in the OP to be the same as e.g "Introduction", because now it looks like part of "Singleboot Partition Layout" section only. It is confusing IMHO.
In my case (i.e. flashing both flash_core.sh and then flash_partition_table_and_core.sh), I had to recreate ext4 FS not only on the system partition in TWRP, but also on the data partition (it could not be mounted and TWRP announced 0 MB size) and eventually also on the cache partition. This seems to contradict the info in OP, part "Singleboot Partition Layout", which mentions that data will be preserved.
@cogano thx for your feedback
it's weird that u had to recreate the filesystems because the positions of these partitions still are the same. I resized system1, modem1 and boot1 to 2KB and system, modem and boot to 2*oldsize-2KB. I checked the offsets and they still are the same.
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
cogano said:
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
Click to expand...
Click to collapse
thx "parted /dev/block/mmcblk0 p" will help to debug these things.
If you don't have a ROM/Recovery with parted you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
m11kkaa said:
you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
Click to expand...
Click to collapse
What a great feature!
superiyezi said:
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
Click to expand...
Click to collapse
There's a Download "card" on top.
What are the partitions sizes after flashing the singleboot partition layout?
(My English isn't very practice. If you have any question reading this post, please feel free to ask. I'll try my best to express.)
## 0. Update: 2018/04/16
Some information I got today:
1. OnePlus is doing a repartition in OP5 Open Beta 8 / OP5T Open Beta 6 (or earlier, who knows). It'll split the 1.5GB "last_parti" partition into a 1.0GB "vendor" and a ~500MB "reserve3" partition while booting the system.
2. Yes, the repartition process was done in system, not during OTA in recovery.
3. The official vendor partition is still unused (not formatted). OnePlus will fill it in a future OTA, said their engineer.
4. I think it won't be conflicted with our "homemade" unofficial Treble. I just tested that the stock H2OS/OxygenOS can run on our homemade partition table.
5. It's very easy to undo the unofficial treble. I'll make an undo flashable zip later (through it's unnecessary in this time).
6. Of course, MoKee now (since 20180417) can run on the official partition table too.
==========
The MoKee ROM is now shipping unofficial Treble update for OnePlus 5/5T since 20180411. As the maintainer, I would like to share some information here.
## 1. How is this possible for OP5/5T?
Project Treble requires 2 keys: a standalone /vendor partition, and fully binderized HALs.
In fact, OnePlus have a 1.4GB unused, unformatted partition "sdf6" on OnePlus 3, 3T, 5 and 5T. This partition was possibly left by the ODM company, OPPO. OPPO R11/R11s series have a simular partition layout with OnePlus, and OPPO really did release an OTA update to enable Project Treble for their products.
The other key is binerized HALs. More specifically, the Camera HAL. The good news is, OnePlus recently released OP5 Open Beta 6 and OP5T Open Beta 4, with all fully binerized HALs, including the Camera HAL.
So as these 2 majar problems were solved. Project Treble is possible.
## 2. How did this come true?
To make Project Treble come true for OnePlus 5/5T, these should be done:
1. All vender-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused sdf6 partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount sdf6 as /vendor as well
## For users - How to enable Treble for OP5/5T?
The most easy way now is, flash the latest MoKee MK81.0 nightly build with latest TWRP (OP5: http://rom.mk/?device=cheeseburger, OP5T: http://rom.mk/?device=dumpling). The updater script will do the job automatically for you.
It's possible to make a flashable zip contains only the kernel and vendor image, without the MoKee system. But I'm busying on some other features. I'll do it later.
Tested fully works with Phh-treble system image, including:
- Audio
- Camera
- Phone & data
- Bluetooth & Wi-Fi
- Fingerprint
## For developers - How to ship Treblize update with my ROM?
(I'm organizing the patch list, I'll updte this section later)
## Can I flash non-Treble ROMs? How to "undo" this change?
You don't need to undo it, I think. For those non-Treble ROMs, including H2OS and OxygenOS, the /vendor partition is invisible. So you can flash back to any other ROMs at any time you want.
This is good news for us, thank you for your hard working!
So, once we flash the Mokee ROM, will we then be able to flash the other treble ROMs like RR and Lineage?
Skeptico said:
So, once we flash the Mokee ROM, will we then be able to flash the other treble ROMs like RR and Lineage?
Click to expand...
Click to collapse
Of course.
Great job!
Any specific instructions to install this or like a normal install ???
Amanpreetsingh said:
Any specific instructions to install this or like a normal install ???
Click to expand...
Click to collapse
Please, read OP message fully
you are awesome, big thank you from every OP5/5t owner
Damn, Oppo enabled Treble but 1+ didn't
What a shame...
Does this mean that the camera quality will be as good as stock on a custom room?
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
hemant_jeengar said:
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
Click to expand...
Click to collapse
No, as the normal update packages don't touch that partition. On the other hand, there's no repartitioning involved - the type, filesystem and mount point of /sdf6 are changed.
hemant_jeengar said:
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
Click to expand...
Click to collapse
No, Oxygen OS doesn't know there's a partition named sdf6.
First of all appreciate your effort for bringing treble support for op5t.. am currently running xxx ROM and decrypted..questions I have is does blu_spark or codeworkx twrp support flashing system image..also if I flash mokee latest update then will it wipe all my internal storage data..also I read no_verity zip doesn't work so when we go back to other non-treble roms then format data is mandatory..am I right..
Can someone who has already installed a treble gsi try and install oneplus camera apk and see what's happens? Or maybe even gcam? Thanks
Jamie_oppo said:
Can someone who has already installed a treble gsi try and install oneplus camera apk and see what's happens? Or maybe even gcam? Thanks
Click to expand...
Click to collapse
Gcam is crashing..tested and confirmed by a user in the group.. thanks
Can someone post a mirror link. For some reason I cant download from the main site, the countdown disappears at 56 seconds.
This is all I see
cubandanger05 said:
Can someone post a mirror link. For some reason I cant download from the main site, the countdown disappears at 56 seconds.
Click to expand...
Click to collapse
Had the same issue, downloading work on internet explorer on PC so maybe Safari on Mac? Give that a shot
BenisMusical said:
Had the same issue, downloading work on internet explorer on PC so maybe Safari on Mac? Give that a shot
Click to expand...
Click to collapse
Tried bunch of different browsers on my phone, desktop mode and all, but nothing, I'm going to have to try on my laptop tonight. Unless someone posts a mirror link.
Not working on the computer at work ?, getting frustrated ?.
I'm proud to present the first dual boot project for the Samsung Galaxy A5 2017 Exynos version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer 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
Instructions for dual booting
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.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
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.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
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
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
Downloads
Patcher: Download
Utilities: Download
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A5 2017 Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
simon151102 said:
I'm proud to present the first dual boot project for the Samsung Galaxy A5 2017 Exynos version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer 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
Instructions for dual booting
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.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
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.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
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
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
Downloads
Patcher: https://drive.google.com/open?id=18rN9RqiSWlbwBXPlZzdsXw4W4ZQD2tId
Utilities: https://drive.google.com/open?id=158n-YhyHqjvNfhZJWpFTYWgDIqsIBaaL
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A5 2017 Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Click to expand...
Click to collapse
But, there is official support for our device, what's different in this version?
sheepkill15 said:
But, there is official support for our device, what's different in this version?
Click to expand...
Click to collapse
Ofiicial patcher only supports the A5 2017 with Snapdragon SoC, it wont work on the Exynos version. Basically the only difference is the architecture.
A patched ROM for A5 2017 Snapdragon wont work on A5 2017 Exynos. So heres support for the Exynos version
simon151102 said:
Ofiicial patcher only supports the A5 2017 with Snapdragon SoC, it wont work on the Exynos version. Basically the only difference is the architecture.
A patched ROM for A5 2017 Snapdragon wont work on A5 2017 Exynos. So heres support for the Exynos version
Click to expand...
Click to collapse
I see. I didn't know that
sheepkill15 said:
I see. I didn't know that
Click to expand...
Click to collapse
No problem dude?
Wait, there is a version of the A5 2017 with Snapdragon Soc?
MinwooChong said:
Wait, there is a version of the A5 2017 with Snapdragon Soc?
Click to expand...
Click to collapse
Yeah, the US A5 2017 is powered by a Snapdragon 660. Other countries (like korea, germany, ...) have Samsungs Exynos 7880 instead.
Does it support Oreo and pie ROMs???
iloveoreos said:
Does it support Oreo and pie ROMs???
Click to expand...
Click to collapse
Im able to boot Oreo and Pie ROMs, but I have not tested much ROMs (only tested RR with android 8 and PixelExperience with android 9).
For me they are working without problems
simon151102 said:
Im able to boot Oreo and Pie ROMs, but I have not tested much ROMs (only tested RR with android 8 and PixelExperience with android 9).
For me they are working without problems
Click to expand...
Click to collapse
Cool. Hope I have success with this version.
I just tried pixel experience as the second rom. Failed with error 1 like normal. Is there a certain slot that works better? I usually do ext sd.
iloveoreos said:
I just tried pixel experience as the second rom. Failed with error 1 like normal. Is there a certain slot that works better? I usually do ext sd.
Click to expand...
Click to collapse
I always use data slot, extsd isnt working for me(dont know why).
But make sure you checked the A5 2017 exynos, it normally checks the snapdragon one when patching a zip
Update 13 Feb
Patcher and Utilities built from latest sources with support for A5 2017 Exynos and (because someone in the main DBP thread asked) support for S9 Plus Snapdragon.
Patcher: https://drive.google.com/open?id=1ND...Jh4imaAbgR1Chz
Utilities: https://drive.google.com/open?id=13H...1PlJ6bI8bpydSh
Update
Added a few more codenames (A520W, A520DS)
Patcher: Download
Utilities: Download
Update
Re-compiled the app with a different linker (got some errors before)
Patcher: Download
Utilities: Download
simon151102 said:
Update
Re-compiled the app with a different linker (got some errors before)
Patcher: Download
Utilities: Download
Click to expand...
Click to collapse
Tried with the last update and dual boot app keeps stopping..(force closes)
EDIT:The app force closes only when i press the tab ROMS.
broky said:
Tried with the last update and dual boot app keeps stopping..(force closes)
EDIT:The app force closes only when i press the tab ROMS.
Click to expand...
Click to collapse
Which ROM are you using as primary ROM?
I cant reproduce the error on any of my ROMs.
Sharing logs would be great
simon151102 said:
Which ROM are you using as primary ROM?
I cant reproduce the error on any of my ROMs.
Sharing logs would be great
Click to expand...
Click to collapse
I m using Hades rom V6 for primary.
broky said:
I m using Hades rom V6 for primary.
Click to expand...
Click to collapse
I think this is a ROM-related bug Im not able to fix.
This bug has to be fixed in the sources I guess, and as Im not a programmer, I have no idea how to do this.
Im sorry
Boot loop on a520f after updating ramdisk
After updating ramdisk for primary rom (hadesrom v1.5) phone goes into bootloop.
But lineageos 16 as secondary works well even after updating ramdisk.