{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello everyone!
Together with @h0rn3t we bring you Dual Boot Support for the Samsung Galaxy Wonder (Ancora)
Let's get started
Requirements:
Root
Busybox
CM or other AOSP like ROM based on 4.0+
Minimum ~350MB internal storage free space
External SD (min 4GB, the higher class, the better)
Description:
The process is fairly simple. The application will format your external-sd (we recommend to back up your personal data), then create 3 partitions as follows:
/dev/block/mmcblk1p1 -> storage (formatted VFAT)
/dev/block/mmcblk1p2 -> /system (formatted EXT4)
/dev/block/mmcblk1p3 -> /data (formatted EXT4)
After that you'll be given the possibility to flash a secondary ROM on your EXT-SD (currently only 4.1.2+ ROM's are supported as secondary and 4.0+ as primary).
At last, you'll be able to switch between ROM's within the app.
Process:
WARNING: Partitioning and flashing operations could take up to 5 minutes to complete, please be patient !
Download the app and kernel pack from the Downloads section
If you want the app to be automatically installed on the secondary ROM, push the app to /system/app and give proper permissions (rw-r-r or 644). Otherwise, just install it normally.
Backup your personal data from the external sd card.
Run the app and partition your external-sd.
In app, choose flashing then choose your preferred secondary ROM from your internal SD card (must be 4.1.2 or higher).
Your phone will reboot into recovery and automatically flash the secondary ROM. (in CWM, if you get "Signature Verification Failed", continue flashing, it is normal)
After the flashing process is done, you'll be redirected to your primary ROM.
On your internal SD-Card, you'll have a folder called DualBootSplus, open it up.
Copy the kernels from the kernels pack into their appropriate subfolder. (eg CM-10 kernel (boot2.img) goes into 4.1.2 subfolder -> you'll have to create the subfolder if it doesn't exit)
Now you can switch between ROM's or flash secondary gapps within the app.
Additional details:
You must put only 1 boot2.img in each DualBootSplus subfolders.
The kernel will determinate which ROM will be booted. So, if you have a primary and secondary ROM, you can quickly switch between them within the app (make sure you have the kernels in the SD-Card subfolders), or manually by flashing the correspondent kernel.
The boot2.img can be flashed separately in ADB.
Special thanks goes to @arsradu for his kernels and @Madridii for testing.
XDA:DevDB Information
[GT-I8150] Dual Boot [ANCORA], Tool/Utility for the Samsung Galaxy W I8150
Contributors
educk, h0rn3t
Version Information
Status: Stable
Current Stable Version: 1.5.1
Stable Release Date: 2013-10-27
Created 2013-10-04
Last Updated 2014-05-20
For Kernel Developers
For Kernel Developers
How to make a kernel suitable for dual-booting (mounting ext-sd partition)
We know that a kernel (for Galaxy W, S Plus and many others) has 2 major components. The RAMDISK and the zImage.
The RAMDISK is responsible for mounting and other init processes so to successfully boot up a secondary ROM (from the external SD-Card) we need a kernel with a modified RAMDISK, so that it recognizes these external partitions.
As stated in the OP, the app partitions the ext-sd like this:
/dev/block/mmcblk1p1 -> storage (formatted VFAT)
/dev/block/mmcblk1p2 -> /system (formatted EXT4)
/dev/block/mmcblk1p3 -> /data (formatted EXT4)
So these are the exact instructions we should pass to the fstab. (this particular file from the RAMDISK is responsible for disk mounting).
I pasted here a modified fstab.qcom which should explain pretty much everything I did to make a proper dual boot kernel:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
[B]/dev/block/mmcblk1p2[/B] /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p16 /cache ext4 nosuid,nodev,barrier=0 wait,check
[B]/dev/block/mmcblk1p3[/B] /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=1 wait,check,encryptable=footer
Please note that fstabs might vary with Android version.
Currently, only 3.0 kernels are able to mount ext-sd partitions, the 3.4 one has some bugs/differences in the emmc driver which were not fixed/adapted until now.
For decompiling the boot image there are several tools out there. My personal favorite is bootimgtools, there are several toolkits which use this little binary like dsixda's Android Kitchen.
Good luck!
educk said:
Hello everyone!
Together with @h0rn3t we bring you Dual Boot Support for the Samsung Galaxy Wonder (Ancora)
Let's get started
Requirements:
Root
Busybox
CM or other AOSP like ROM based on 4.0+
Minimum ~350MB internal storage free space
External SD (min 4GB, the higher class, the better)
Click to expand...
Click to collapse
awesome job:thumbup:
Sent from my GT-I8150
finally, thanks mr educk :good::good:
---------- Post added at 12:33 AM ---------- Previous post was at 12:24 AM ----------
hi mr educk, it's that ok if i swap the mmc to sd when dual boot ? sorry bad english
Good job mate... thanks :thumbup:
Awesome
Thanks sir educk:thumbup::thumbup:
I have to think about it because i already formatted and configured my ext-sd to be used as app swap with link2sd.
Thanks a lot nevertheless!
tycoo said:
I have to think about it because i already formatted and configured my ext-sd to be used as app swap with link2sd.
Thanks a lot nevertheless!
Click to expand...
Click to collapse
haha sure, i'm just test it, my second rom is swap mmc to sd and i forgot to change it, it's run very laggy on second rom
GOOD!!
thank you very much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
sir mordred said:
thank you very much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
Click to expand...
Click to collapse
i think no, the primary rom is 4.0.+ and secondary is 4.1.2+
sir mordred said:
thank youcan't use sy much educk .
now we are able to use stock rom and cm together on the one phone :good::good::good::good:
you are awesome man thanx again
Click to expand...
Click to collapse
First big thanks to Mr Erik..
No you cant use stock rom as primary read carefully ..
We hope it will support cm9 and 2.3.6
fsl7th said:
i think no, the primary rom is 4.0.+ and secondary is 4.1.2+
Click to expand...
Click to collapse
no first rom is cm10.1 second rom is stock
if there is a cwm flashable stock rom for galaxy w like that XXLB4.zip ı think we can do it
sir mordred said:
no first rom is cm10.1 second rom is stock
if there is a cwm flashable stock rom for galaxy w like that XXLB4.zip ı think we can do it
Click to expand...
Click to collapse
but the rule is that the second rom must be 4.1.2+, that's why mr educk append the cm 10 and cm 10.1 kernel on his post,
correct me if im wrong
fsl7th said:
but the rule is that the second rom must be 4.1.2+, that's why mr educk append the cm 10 and cm 10.1 kernel on his post,
correct me if im wrong
Click to expand...
Click to collapse
You are right.
As stated in the OP, the primary ROM can be any either ICS or JB (4.1.2 & 4.2.2).
The secondary can be only JB (4.1.2 & 4.2.2). Make sure you have the appropriate dual boot kernel (boot2.img) in the correspondent sub folder from /sdcard/DualBoot.
I'm working on ICS as secondary. After that, we'll see about GB.
educk said:
You are right.
As stated in the OP, the primary ROM can be any either ICS or JB (4.1.2 & 4.2.2).
The secondary can be only JB (4.1.2 & 4.2.2). Make sure you have the appropriate dual boot kernel (boot2.img) in the correspondent sub folder from /sdcard/DualBootAncora.
I'm working on ICS as secondary. After that, we'll see about GB.
Click to expand...
Click to collapse
Is cm 10.2 not possible ?
Guys, I made a mistake in the application. Please wait few minutes until I fixed... Sorry for inconvenient !
---------- Post added at 11:02 PM ---------- Previous post was at 10:53 PM ----------
OK. Problem solved. Please update your application. You must put boot2.img files in DualBoot folder. If you already have DualBootSplus folder rename it DualBoot.
The correct folder is /sdcard/DualBoot. You must have something like this /sdcard/DualBoot/4.2.2/boot2.img
Well, thanks guys! I've been waiting for you to do that for ancora.
Sent from my GT-I8150 using Tapatalk 4
This is really new for galaxy w, Amazing work educk.... :thumbup:
Sent from my LT29i using Tapatalk 4
does it support cm9 as secondary ?
Dwama said:
does it support cm9 as secondary ?
Click to expand...
Click to collapse
Not yet !
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the unofficial CyanogenMod 10.2 nightlies
The releases will co-inside and the build start time is at 03:01 UTC every night and should be uploaded soon after. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP.
These builds are compiled from the latest CyanogenMod repos and device repos on device, kernel and vendor.
These are NativeSD builds Repartitioning may be required
With aging nand storage filled with BBs, a crappy filesystem (namely yaffs2) and high speed sdcards these days it really makes sense to mount /system and /data on the sdcard. prerequisite is a fast sdcard (class 6, class 10 - they're really cheap these days). transfer rates are ~2.5x-3x nand speed with a decent sdcard and we can benefit from ext4. of course, one needs a compatible recovery (built with this change included) and a partitioned sdcard. e.g. minitool with win and fdisk with *nix.
Partition layout
Device partitions (cLK):
* boot: 10
* recovery: 10
* cache: 5
* misc: 1
Click to expand...
Click to collapse
You need to create two primary ext4 partitions in addtition to the regular fat32 partition on your sdcard.
SDcard partitions:
* 1st primary sdcard partition: fat32 storage (should already be there)
* 2nd primary sdcard partition: ext4 (at least 500MB)
* 3rd primary sdcard partition: ext4 (e.g. 2000MB)
The first partition will be your regular sd storage.
The second partition will be /system.
The third partition will be /data.
You can use MiniTool Partition Wizard with Windows and fdisk with Linux
Click to expand...
Click to collapse
Click to expand...
Click to collapse
NativeSD recovery required to properly support these builds
Download
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download builds here
Click to expand...
Click to collapse
Download Google Apps
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changes
Upstream changes
Devicetree commits
Kernel commits
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And as always: I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
IRC channel
Visit us in #cmhtcleo on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
---------- cmhtcleo team ----------
arif-ali | milaq | Rick_1995
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks/Credits
Click to expand...
Click to collapse
Marc Alexander (marc1706) - for his awesome work on the HD2 kernels
Sportsstar89 - for carrying on open development - all your build trees are in an open git. Way to go mate. Thats the spirit of FOSS
Securecrt, Rick_1995 - for their awesome work on a full HWA kernel and other great contibutions to the Leo codebase
Evervolv - for the now mandatory legacy repos
arif-ali - for his huge contribution to the cmhtcleo project and beeing a indispensable part of the Android community
copenhagen, warrenb213 - for keeping on devloping for the hd2
charnsingh_online - For starting this great project for porting to CM
tytung - for of his work on the HD2
texasice - For creating the first HD2 compitable ICS through passion/bravo
ankuch - thanks for the HW accel, codecs and Camera
Xylograph - for carrying on development
zivan56 - your input for the headphone fix
Bexton - The fix for USB Mass Storage
michie - Your work on ICS for the HD2
Steve Kondik (cyanogen) - for starting this great project
Google - for an awesome OS
Let me know if i omitted you and i will add you here asap
Preferred and yet more advised is cLK.
If you REALLY need to use MAGLDR then keep on reading.
MAGLDR instructions
We are using boot.img style kernel/ramdisk (as everyone else should be).
For MAGLDR users that means that you need to specify your boot partition as rboot.
The following flash.cfg is recommended (system and data size doesnt matter as we're using NativeSD)
Code:
misc ya 1M
recovery rrecov|ro 10M
boot rboot|ro 10M
system ya 300M
cache ya 5M
userdata ya|asize|hr allsize
Thank you for your awesome work.
HWA??
Does This Rom Support The HwaSettings App, Does this rom have the hwui edit for the hwasettings to work in the Android Source?
thank's man happy to see a dev in this forum .:laugh:
wow a rom by Dev ... Downloading.. plz work on kitkat for hd2 too.. n wish hd2 gets 3.0 kernel... thanks for the great rom.. :good::good::good:
hirencj said:
wow a rom by Dev ... Downloading.. plz work on kitkat for hd2 too.. n wish hd2 gets 3.0 kernel... thanks for the great rom.. :good::good::good:
Click to expand...
Click to collapse
Here's a sneak peak
I from the HD24EVR team is now working for a Kitkat rom that will be uisng ION with the 3.0 kernel
Also a Shoutout to @marc1706 for making the 3.0 kernel
aazzam16661 said:
Here's a sneak peak
I from the HD24EVR team is now working for a Kitkat rom that will be uisng ION with the 3.0 kernel
Also a Shoutout to @marc1706 for making the 3.0 kernel
Click to expand...
Click to collapse
Thank you for your dev on Kernel 3.0 on LEO
I hope we can use new kernel with ION soon..
:good:
fengsam said:
Thank you for your awesome work.
Click to expand...
Click to collapse
Dear Sir,
Can we use this on NativeSD or DirectSD as i am using windows mobile 6.5 and nativesd for android
aazzam16661 said:
Here's a sneak peak
I from the HD24EVR team is now working for a Kitkat rom that will be uisng ION with the 3.0 kernel
Also a Shoutout to @marc1706 for making the 3.0 kernel
Click to expand...
Click to collapse
Wow Thats going to be awesome... HD24EVE Best Wishes for the team... Plz keep up good work.. :good::good::good::good::highfive:
as installed, this ROM?. Lapsus, forgotten concepts. I had my HD2 in a drawer, and I see that this becomes animate. If developers continue to give life to this superphone, put for sale my HTC One Thanks
I think it will be a great build.
Is a problem with GPS fix a known problem or maybe only I am experiencing it?
Can I install this using one ext4 partition on sdcard? Or I need to make another?
vlado3399 said:
Can I install this using one ext4 partition on sdcard? Or I need to make another?
Click to expand...
Click to collapse
Hi vlado3399, I am almost certain you need 2 ext partitions, as it says in OP (so it is not NativeSD)
I tried installing it to one partition, and there is no /data on the ext partition. Also, the install process has formatted the ext partition, so if you have any NativeSD roms or anything in dataonext, be sure to back them up first.
I will try adding another partition. Am trying to boot from magldr, but I think clk is the way to go
Edit; Thank you milaq and team, exciting to see nightlies back on our hd2. I hope there will be enough ongoing interest in testing etc from the hd2 community:fingers-crossed:
OP says that build is NativeSD, that's why i asked my question. Give us feedback when you add another partition and install rom
Robbie P said:
Hi vlado3399, I am almost certain you need 2 ext partitions, as it says in OP (so it is not NativeSD)
Click to expand...
Click to collapse
mounting partitions on sdcard partitions is exactly what nativeSD is.
nativeSD is just a term used for the general principle and is not limited to a specific partition layout. it makes sense to use 2 partitions instead of fuse mounting hackery with only one sdcard partition. e.g. formatting /data and /system separately, etc.
Ok, have added 2nd partition using minitool.
installed 20131227, magldr, using the recommended cwm recovery
It reboots during bootanim, have attached dmesg.
will try with clk a bit later.
Edit; same on clk, reboots during bootanim
Edit2; same with 20131228 on clk. I also tried putting tytung's r2 into boot.img (using this, and adding system files to rom.zip) but the same thing happens, so i don't think it is kernel related.
I can try and get a dmesg, but not sure how to with clk, will have to search a bit
I did notice that minitool sees the first (system) partition as ext3 after installation, looking at updater script, it is formatted as ext4...
format("ext4", "EMMC", "/dev/block/mmcblk0p2", "0", "/system");
Click to expand...
Click to collapse
So not sure why minitool would see it as ext3
goglum said:
Is a problem with GPS fix a known problem or maybe only I am experiencing it?
Click to expand...
Click to collapse
Is anyone else experiencing problems with GPS? Cause I don't know if I should look for the source of the problem on my side. I tried digging through device and kernel commits, but I don't get much of it
I already tried replacing /system/etc/gps.conf with something suitable for my region (Europe/Poland), but it didn't help.
Pls answer someone. ;]
goglum said:
Is a problem with GPS fix a known problem or maybe only I am experiencing it?
Click to expand...
Click to collapse
I cannot get GPS working either.
My phone was previously running CM7 (HyperDroid-CM7-Licking-Lobster-v5.7.0) and it was working fine, so I tried using gps.conf from this version, but it did not work.
[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions..
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
[updated 20140401]
version v2.11
ubuntu touch support ( http://www.androidfilehost.com/?w=files&flid=13392 )
Important recommandations and details of working features can be found in this thread : http://forum.xda-developers.com/showthread.php?t=2702692
[updated 20140316]
version v2.0
qcow2 support ( https://www.youtube.com/watch?v=LGoTb0u5oX0 )
[updated 20140311]
version v1.2
migration to twrp2.7.0.0
sizing of system/data/cache now possible
real internal/external sd mounted ( respectively in /storage/intsdcard and /storage/extsdcard )
new way to boot roms
new link to download : http://www.androidfilehost.com/?w=files&flid=12801
Hi,
This recovery image is based on twrp with multiboot feature on Galaxy S3.
I did this on Galaxy S3 Bell model but it as been reported to work on Tmobile Model ( by saranhai, thank's to him )
( original thread : http://forum.xda-developers.com/showthread.php?t=2577211 )
Please follow exactly the operations in videos examples to avoid any risk.
Very important recommendations :
- BACKUP all your data first !
- Use only your internal if you have at least 4G available ( 7GB recommended because img files are sparsed but if you fill all the rom, it will take 7GB )
- Use your external sd card only if :
- you have at least 7 GB free
- your filesystem is vfat ( exfat,ntfs not supported for the moment ) - Very very important : when you use "set rom" option, you have to see "command succeded" at the end of the output. If not, don't go further and reboot.
- start by playing with recovery roms ( check video ) before testing full rom
- creating rom on external vfat can take about 15 minutes (to create img files). Be patient...
The method used is an adapted kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827), but with a complete replacement of kexec by a new userspace program I did ( kload-hardboot ) and a very small kernel patch ( hardboot-reserve ). Note also that this adapted method is easily portable to any android devices.
I will publish sources when cleaned.
Booting multiples ROMs demo:
Playing with recovery roms:
Creating a new rom, installing gapps ( if not done at first stage ) :
Multiboot android app ( early dev stage )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link : http://www.androidfilehost.com/?w=files&flid=12801
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
saranhai
Philippe,
I can personally confirm that this DOES indeed work! I currently have loaded up 3 different ROMs, and they eaach boot no problem, loving it! Great job and hats off to the developer! :good:
-Saranhai
I assume this takes up a lot of space though?
I was able to flash the recovery via Odin. Now what? Do I need to reinstall my ROM to have it work for multi-boot? Or can I have it recognize my existing ROM?
Also, if I make changes to the ROM, will the multi-boot functionality know that I've made changes or do I need to backup?
Thanks.
OMG ! Now mobile device becoming very interesting !!!
Sent from my SGH-T999 using xda app-developers app
Amazing how booting back and forth is just like rebooting your phone, in terms of their responsiveness. I thought there would be some sort of noticeable lag on each boot. It does use about 7GB like OP says. Pretty cool though, to be able to go back and forth between stock tw to ASOB in so little time. App works like a charm too. This is great, thanks for creating and sharing.
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
Bass_Man25 said:
I was able to flash the recovery via Odin. Now what? Do I need to reinstall my ROM to have it work for multi-boot? Or can I have it recognize my existing ROM?
Also, if I make changes to the ROM, will the multi-boot functionality know that I've made changes or do I need to backup?
Thanks.
Click to expand...
Click to collapse
Multiboot rom keeps changes. The last rom you were running is your internal (it will boot on every reboot). Follow the third video exactly and you will see, and make sure to read the OP again.
[/COLOR]
Multiboot rom keeps changes. The last rom you were running is your internal (it will boot on every reboot). Follow the third video exactly and you will see, and make sure to read the OP again.[/QUOTE]
Oh, I think I get it now. So, my current ROM (CM11) is still stored in the original ROM partitions, but selecting a different ROM to boot is pulling it from the internal SD card. So, I could boot a secondary ROM (say TW) or a third ROM (like SlimKAT) but then choose Reboot to get back into CM11. Am I correct?
Yes
Tomb77: Thanks for the clarification.
This recovery ROCKS! Not only can I use a TW ROM for WIFI calling when needed, I can also test other ROMs without having to wipe/format/etc. Awesome work!!:good:
Will we have to create the multiroms again after updates for mulitirom twrp? And, can we flash over an already created multirom for an update on the rom?
Edit: So I was able to update my multirom rom. I got hung up on symlink... I did a battery pull, eventually booted the multirom rom and it was updated. been playing with it for a couple hours and there doesn't seem to be any instability issues. Thought I would through that out there.
Bass_Man25 said:
Tomb77: Thanks for the clarification.
This recovery ROCKS! Not only can I use a TW ROM for WIFI calling when needed, I can also test other ROMs without having to wipe/format/etc. Awesome work!!:good:
Click to expand...
Click to collapse
My try this tomorrow just to check out other roms an stuff so i know what is good with out wiping all my data c:
Seems to be getting great reviews from everyone
Sent from my SGH-T999 using xda app-developers app
If you're a flash junkie, this is for you. I'm so excited
Sent from my SGH-T999 using Tapatalk
VFAT, Same as FAT32? If not, how do I get the external sd in VFAT?
Well I bought a 16gig sd and it appears to be corrupt of something. I can format it and then put it in my phone and it just freaks out. Put my original 2 gig card in and everything is fine again.
---------- Post added at 05:57 PM ---------- Previous post was at 05:55 PM ----------
Also another question. Each ROM will take 7 gigs, or is that just the image file that all the ROM's run on?
zul8er said:
VFAT, Same as FAT32? If not, how do I get the external sd in VFAT?
Click to expand...
Click to collapse
I am using FAT32. I think FAT32 is an extension of VFAT so it shouldn't matter. Could someone verify? It's working for me and I didn't change the format.
I read it was the same... Just wanted to make sure.
I did buy a faulty SD card. Constantly disconnects corrupting files.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 07:26 PM ---------- Previous post was at 07:24 PM ----------
But I did get Philz recovery, Slimbean, and Dandroid running.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I wiped everything and started over. Had some issues afterwards and eventually had to Odin stock. After setting everything up again, I am unable to flash a rom onto the multirom. It looks like the error starts where it is unable to connect to data. Any suggestion would be great, thank you.
Edit: Not until I full wiped with the phones original recovery have I been able to play again.
Working nicely, but your videos were kinda confusing and figured it out on first try. Nice work
Sent from a potato from the future.
G1-evolve said:
I assume this takes up a lot of space though?
Click to expand...
Click to collapse
Yes, ~7GB if installed on external vfat, a lot less if installed internally as img files holding filesystems are sparsed. Say ~2G max after installation
But I admit that 7GB hardcoded is too much.
Next version will add possibility to custom sizes of /system, /data and /cache. For example, a light rom like Dandroid4.7 can be installed on ~1.8G ( 1G system, 500M data, 200M cache).
PS : for people who want do do it now manually, it is easy : just connect shell with adb when in recovery and edit values (in hexa) /sbin/create_rom.sh of SIZECACHE,SIZESYS and SIZEDATA. Without rebooting, you will be able to create new roms with new size under twrp menus.
Philippe,
Been running this recovery for over ten days now. I have to say that this is very awesome, it works great. About the only issue I had once is a multiboot rom not deleting for a couple of tries. I am surprised that it seems like very few people are trying this out here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Many Stock-based ROMs will fail to install because their boot.imgs cannot be unpacked using normal tools or use unsupported compressions. Please contact me in that case, but do note I can't add support for each Stock-based ROM out here.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Don't try to flash ROMs with Stock boot.imgs (supported by LBs). They need special unpacking tools and are therefore currently not supported. I haven't yet tried flashing other Stock ROMs. Besides, I have configured MultiROM to only support boot.imgs that use the 2 stage boot method (boot.imgs with recovery ramdisks inside).
This is still a work in progress. Don't ask for ETAs please.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernel to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on OmniROM
Flash my modified kernel
Flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/tree/master (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/omnirom/android_kernel_sony_apq8064 (branch android-4.4)
FAQs can be found here.
CREDITs
Tasssadar
Kr3i0s
omnirom
Everyone else mentioned here.
XDA:DevDB Information
MultiROM for Sony Xperia ZL, Tool/Utility for the Sony Xperia ZL
Contributors
Olivier
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Beta
Current Beta Version: 31x
Created 2014-09-02
Last Updated 2015-02-13
Changelog
DOWNLOADs
You can get everything from my build server.
CHANGELOG
Code:
[b]13/02/2015:[/b] Updated to v31x | Updated adb | Print error when multirom crashes | Added support for multiple entries per path in fstab | Set is_second_boot also if mrom_kexecd=1 is present in /proc/cmdline | Support interlaced PNGs | Updated to MultiROM TWRP 2.8.5 (incl. upstream <-> TWRP 2.8.5.0)
[b]17/01/2015:[/b] Updated to MultiROM TWRP 2.8.4 (incl. upstream <-> TWRP 2.8.4.0), fixed "Swap ROMs" feature
[b]08/01/2015:[/b] Inserted dummy line instead of removing to prevent breaking IFs (fixes the installation of AOSPA 5.0)
[b]04/01/2015:[/b] Updated to MultiROM TWRP 2.8.3 (incl. upstream <-> TWRP 2.8.1.3)
[b]08/12/2014:[/b] Fixed the installation of L-based ROMs as secondary ROMs
[b]04/12/2014:[/b] TWRP upstream
[b]28/11/2014:[/b] Moar TWRP upstream, updated to MultiROM v30x, fixed klog saving and text size on emergency reboot screen
[B]28/11/2014:[/B] Updated to MultiROM TWRP 2.8.1 (incl. upstream <-> TWRP 2.8.1.0) | Fixed perms of extract_elf_ramdisk
[B]23/10/2014:[/B] Upstream: Updated to v29x | Added "DirtyUnicorns icon" | Added device hook to allow incomplete fstab file | Bind mount /realdata to /data for rom quirks to work properly
[B]02/10/2014:[/B] Added support for external sdcard
[B]27/09/2014[/B]: Fixes for recovery, updated to MultiROM v28x (device-specific version)
[B]02/09/2014[/B]: Initial public release.
SUPPORTED KERNELs
OmniROM (and DirtyUnicorns, which is based off Omni)
lightning kernel by nikhil18
psycho-punk said:
Can OmniROM be replaced with some other after installing MultiROM?
Click to expand...
Click to collapse
I'm running Dirty Unicorns ROM which is omni based rom, will this work?
I'm want to make PA my secondary rom..
Thanks
psycho-punk said:
Can OmniROM be replaced with some other after installing MultiROM?
Click to expand...
Click to collapse
DU should work too, but otherwise no.
AndreIrawan97 said:
I'm running Dirty Unicorns ROM which is omni based rom, will this work?
I'm want to make PA my secondary rom..
Thanks
Click to expand...
Click to collapse
Yes, probably.
Thanks for this, it gave new life to my ZL! Multiboot rocks! I've managed to run Omni, CM11 and Carbon KK , so far so good. Are you also by chance doing a stock kernel for ZL that works with multirom, just like your stock kernel in Z? Hope you could also create stock kernel for ZL, really appreciate it. Thanks in advance.
What about adding MultiRom support to 4.4.4 stock kernel? Should we wait for new kernel source release from Sony?
francarl said:
What about adding MultiRom support to 4.4.4 stock kernel? Should we wait for new kernel source release from Sony?
Click to expand...
Click to collapse
I'd need you to upload a stock boot.img/kernel.elf in that case.
Olivier said:
I'd need you to upload a stock boot.img/kernel.elf in that case.
Click to expand...
Click to collapse
Will this work, it is based on stock .283 but with added features -
http://www.mediafire.com/download/1bf5bhjbtbvxhnk/Advanced_stock+kernel_for_KK_10.5.1.A.0.283.zip
Features:
Dual recovery - CWM Philz Touch 6.48.4/TWRP 2.7.1.0 (vol up - CWM / vol down - TWRP)
Init.d suport
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Kernel taken from here - http://forum.xda-developers.com/xpe...ed-stock-kernel-kitkat-4-4-t2873475#undefined
I've also informed the developer if he is ok with it being modified to have kexec patch.
^^ probably not, as multirom needs w/ kexec modification, which isn't listed above.
Did someone manage to boot ubuntu ( http://forum.xda-developers.com/showthread.php?t=2434585) in multirom? How?
Could we have native ubuntu touch support with the next version, please?
Gesendet von meinem Xperia ZL mit Tapatalk
stock rom as primary rom
ryanrudolf said:
Will this work, it is based on stock .283 but with added features -
http://www.mediafire.com/download/1bf5bhjbtbvxhnk/Advanced_stock+kernel_for_KK_10.5.1.A.0.283.zip
Features:
Dual recovery - CWM Philz Touch 6.48.4/TWRP 2.7.1.0 (vol up - CWM / vol down - TWRP)
Init.d suport
Debugging enabled by default
Disable debugging notification icon in the status bar
Kernel insecure (ro.secure=0)
Kernel taken from here - http://forum.xda-developers.com/xpe...ed-stock-kernel-kitkat-4-4-t2873475#undefined
I've also informed the developer if he is ok with it being modified to have kexec patch.
Click to expand...
Click to collapse
Thank you.
So could this kernel be used to start stock rom 10.5.1.A.0.283 as primary rom?
Hey guys, a new update is up. There have been many changes, you can now install ROM to the external sdcard. Enjoy!
thanks for this! im using latest update and also lightning kernel and CM11 as primary rom, it works good! im thinking for stock kernel to work as secondary rom, we have to modify the mount points? edit the ramdisk? just trying to understand before i try to do it on my own. really wanted to have working CM11 as primary and stock as secondary. thanks again
Olivier said:
Hey guys, a new update is up. There have been many changes, you can now install ROM to the external sdcard. Enjoy!
Click to expand...
Click to collapse
Thanks @olivier. Ext SD support is great.
I was wondering if we will get stock rom support as primary in the future.
ryanrudolf said:
thanks for this! im using latest update and also lightning kernel and CM11 as primary rom, it works good! im thinking for stock kernel to work as secondary rom, we have to modify the mount points? edit the ramdisk? just trying to understand before i try to do it on my own. really wanted to have working CM11 as primary and stock as secondary. thanks again
Click to expand...
Click to collapse
You can do the following (once my stock-based kernel is available): Install a stock rom as primary, back it up and restore it as secondary ROM.
Kr3i0s said:
Thanks @olivier. Ext SD support is great.
I was wondering if we will get stock rom support as primary in the future.
Click to expand...
Click to collapse
I will as soon as I get enough time.
Gesendet von meinem Xperia Z mit Tapatalk
Olivier said:
You can do the following (once my stock-based kernel is available): Install a stock rom as primary, back it up and restore it as secondary ROM.
I will as soon as I get enough time.
Gesendet von meinem Xperia Z mit Tapatalk
Click to expand...
Click to collapse
sorry for asking, but do you have any news on this? thanks
francarl said:
sorry for asking, but do you have any news on this? thanks
Click to expand...
Click to collapse
Patience please, I do have other things in life to do - I'll let you know for sure.
Gesendet von meinem Xperia Z mit Tapatalk
MultiROM v29x is up!
As for the Stock-based kernel: I have decided not to support Stock ROMs officially, but you can always use the lightning kernel by nikhil18 to have a Stock-based kernel with kexec-hardboot support.
Olivier said:
MultiROM v29x is up!
As for the Stock-based kernel: I have decided not to support Stock ROMs officially, but you can always use the lightning kernel by nikhil18 to have a Stock-based kernel with kexec-hardboot support.
Click to expand...
Click to collapse
@Olivier which version of lightning kernel to use?
Kr3i0s said:
@Olivier which version of lightning kernel to use?
Click to expand...
Click to collapse
The one for Stock ROMs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)
FAQs can be found here.
CREDITs
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
If you think I deserve a donation, I won't stop you
Thanks a lot to those who have donated!
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the Z3
XDA:DevDB Information
MultiROM for Sony Xperia Z3, Tool/Utility for the Sony Xperia Z3
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2015-01-23
Last Updated 2016-06-06
CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
M5 Kernel
AndroPlus Kernel (starting with V19)
If you want your favorite kernel to support kexec tell the dev to merge my commits.
Reserved
General Informations about Kexec are coming here soon.
I will test it when i come home and report the result.
Edit: all is stable only Multirom menu needed to be fixed but that you have reported, thanks
Now i can use stock as daily driver and cm12 to see the progress. many thanks.
Whaaaaaaat. This is amazing! Thanks for your work, keep at it! I will surely use the multirom a bit later, when some more roms like PA are avaiable.
Wow great work! A noob question but one assumes that I would not be able to have one rom on 4.4.4 and another on Lollipop 5.0 due to the fact the base Kernel AndroPlus is designed for 4.4.4 or does Multi Rom allow 2 different Kernels? Thanks in Advance.
Sent from my D6603 using XDA Free mobile app
panzerscope said:
Wow great work! A noob question but one assumes that I would not be able to have one rom on 4.4.4 and another on Lollipop 5.0 due to the fact the base Kernel AndroPlus is designed for 4.4.4 or does Multi Rom allow 2 different Kernels? Thanks in Advance.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
It actually is possible. The Base Kernel is patched to be kexec-hardboot compatible. This means it is able to load other kernel to the RAM and run them from there. The host kernel is just a middleman loading the kernel to the RAM, it is not doing anything else which means it is not affecting the secondarys kernel at all.
I used to do this on Nexus 5, loading 4.4.4 with kexec kernel and then 5.0 preview as the other rom and it worked, so it should be possible here as well.
Myself5 said:
It actually is possible. The Base Kernel is patched to be kexec-hardboot compatible. This means it is able to load other kernel to the RAM and run them from there. The host kernel is just a middleman loading the kernel to the RAM, it is not doing anything else which means it is not affecting the secondarys kernel at all.
Click to expand...
Click to collapse
Oh wow thats fantastic news for sure. Lollipop here I come. I was hesitant before due to lollipop not being daily driver material but now it does not really matter. Do you get an option to select which rom upon phone boot up?
Thanks guys and great work
Sent from my D6603 using XDA Free mobile app
panzerscope said:
Oh wow thats fantastic news for sure. Lollipop here I come. I was hesitant before due to lollipop not being daily driver material but now it does not really matter. Do you get an option to select which rom upon phone boot up?
Thanks guys and great work
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
see the pic in the op ? Thats what is going to appear after the Sony scrren and before the initial Rom bootup.
Myself5 said:
see the pic in the op ? Thats what is going to appear after the Sony scrren and before the initial Rom bootup.
Click to expand...
Click to collapse
Woops I thought all that was is a logo but did not check, my bad and thanks!
Sent from my D6603 using XDA Free mobile app
Wow it's already here for the Z3, thanks guys, this is awesome!!
Sorry but my english is to bad to understand what to do... Can anyone create please a step by step tutorial i have the d6603 whith androplus kernel v 19a please help me
Just confirming, looking at your files I assume that the Leo folder is for the z3?
Sent from my D6603 using XDA Free mobile app
panzerscope said:
Just confirming, looking at your files I assume that the Leo folder is for the z3?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
yup, leo is the Z3's codename. Sirius is Z2 and n801x is my Samsung Galaxy Note 10.1. Guess thats what happens when CM breaks the naming law and calling it just z3..
Myself5 said:
yup, leo is the Z3's codename. Sirius is Z2 and n801x is my Samsung Galaxy Note 10.1. Guess thats what happens when CM breaks the naming law and calling it just z3..
Click to expand...
Click to collapse
Yeah I knew it use to be Leo but after checking the CM website it was Z3 so I just wanted to confirm before fracking my phone lol. Thanks!
Sent from my D6603 using XDA Free mobile app
---------- Post added at 10:47 PM ---------- Previous post was at 10:04 PM ----------
So far so good, Modified Recovery and Multirom Installed. Now to flash CM12
Sent from my D6603 using XDA Free mobile app
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
Reporting back after testing.
This is either my ignorance or a possible bug.
So I am ready to add a second ROM. These are the steps I take.
Select Add ROM
Select Internal Memory ( I did get another option called ''/dev/block/mmcblk1p1 (exfat) ....Should that have been used instead ? )
Select Next
Select ZIP File
Select The Rom To Flash (CM12)
The flashing Process starts but fails with the following message
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Please see below for full Flashing Log.
Updating Partition Details.....Done
Full Selinux Support Is Present
Installing ROM cm12
Creating folders and images for type 1
Flashing Zip File cm12
Rom: cm12
Preparing zip file
Copying ZIP to /tmp
Changing mounts to ROM cm12
Current Boot Sector was used as base for fake boot.img !
Zip uses block updates
Creating system.img
Installing 'tmp/mr_update.zip.....
Checking for MD5 File
Skipping MD5 Check: No MD5 File Found
This Package Is For devices: D6602,D6603,D6633,D6643; This device is Leo
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Failed To Install ZIP
Restoring Mounts
Updating Partition Details.....Done
Erasing Incomplete ROM
Click to expand...
Click to collapse
I hope this helps.
panzerscope said:
Yeah I knew it use to be Leo but after checking the CM website it was Z3 so I just wanted to confirm before fracking my phone lol. Thanks!
Sent from my D6603 using XDA Free mobile app
---------- Post added at 10:47 PM ---------- Previous post was at 10:04 PM ----------
So far so good, Modified Recovery and Multirom Installed. Now to flash CM12
Sent from my D6603 using XDA Free mobile app
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
Reporting back after testing.
This is either my ignorance or a possible bug.
So I am ready to add a second ROM. These are the steps I take.
Select Add ROM
Select Internal Memory ( I did get another option called ''/dev/block/mmcblk1p1 (exfat) ....Should that have been used instead ? )
Select Next
Select ZIP File
Select The Rom To Flash (CM12)
The flashing Process starts but fails with the following message
E: Error executing updater binary in zip '/tmp/mr_update.zip'
Please see below for full Flashing Log.
I hope this helps.
Click to expand...
Click to collapse
see there we go with the Leo thingy again Seems like I need to edit the device tree to make the Phone in Recovery appear as some D**** device instead of Leo. Will do tomorrow and release a update. /dev/block/mmcblk1p1 is your physical SD Card (it is formatted as exFat which is what TWRP is displaying).
change updater-script to leo. this should help.
Yeah when I saw that in the log I figured it was incorrectly detecting the device. I look forward to the update. I also guess that's why the Multirom app does not work?
Sent from my D6603 using XDA Free mobile app
Possible use for the Z3 compact?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support L3II, L5, L7 and L7II (Officially)
I am not the creator, just the supporter
XDA NEWS!!!
Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements
1. A Custom Recovery (TWRP or PhilZ Touch or the old CWM )
2. A KitKat ROM (Real KitKat ROM, not build.prop edited, a fake KK ROM)
3. The Dualboot Patcher - http://goo.gl/0bcbbN (Download the APK in Downloads Section)(For L3II, L5, L7 and L7II)
4. A KitKat ROM (To install )
Installation
1. Make a nandroid backup in case anything fails. (optional if you like playing with fire)
2. Install the DualbootPatcher
3. In the Patcher, go to the ROMs section, and a popup will ask you to set the kernel. Do it.
4. After this you need to go in menu (the tree dots) of Primary ROM and search for Update Ramdisk. Press it.
5. In the patcher, go to the Patch ZIP file section, open your ROM zip file
6. After this select in what partition you want to install:
Primary ROM Upgrade - To update ROM without affect the Secundary ROM (and others) when you have one installed.
Secundary - To install in /system.
MultiROM (1-3) - To install in /cache, you have 3 slots in this.
Data Slot - To install in /data (ID is IDentification of ROM)
Extsd slot - To install in your sdcard
7. You not need to change the Device
8. Do the same for GAPPS (optional)
9. Press in confirmation button and wait.
You have two options here:
9. Go to ROMs section and press in button of a device with arrow inside, select the patched zip files (ROM and GAPPS), and by last press in confirmation button, just wait..
10. After finish, close the app (see Know Issues), open and go again to ROMs section and you will see the default ROM to boot (the last installed). Reboot your phone.
11. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
or
9. Restart in recovery, flash the patched zip files (ROM and GAPPS). Restart your phone.
10. It will now boot onto your ROM installed, once you've completed your first boot setup, install the DualBootPatcher.
You are now able to select which rom to boot from the ROMs section. Once you've selected which rom is the default, restart your phone. Voilà!
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Never use this in JellyBean 4.1 or "You are gonna have a bad time"
- Contact me
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
@virulentt for him original thread for tutorial (and encouragement)
@Jonas Cardoso for testing in L5
@WinterR for testing in L7
@ECr34T1v3 for testing in L3II
ScreeShots
Thanks for the mention
@WinterR test the unofficial snapshot, please
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
ch3mn3y said:
What about different kernel and not the one from rom's zip? Better to add them to zip before patch or can be installed later by patching kernel's zip?
Or there can be only one kernel for all roms?
Sent using XT1562 - stock 5.1.1
Click to expand...
Click to collapse
For kernels you need to flash two times, first flash with patched zip (in app) and second flash you need to set the ROM and flash again (via recovery).
The first will update modules (/system) and second is to update the boot.img
Note: Ever you change kernel you need to go to app and set the kernel to save you new boot.img
Now DualBootPatcher supports the L7 and L7II!!!
I got some time and would like to check it out.
I can only use 4.4.4 roms (on L7 there are no newer ones)?
How it works with sdext? Is it used as both /system and /data? Or just /system? But than where is nonprimary rom /data located?
PS. What file systems are supported by app? Or maybe it depends on kernel?
@ch3mn3y you can use all ROMs up to 4.2, because SELinux and other core things like storage/emulated/0.
The SdExt only store system.img, and only system (for now, the patch is under progress all time).
You have option to put 1 in /system (dual), 3 in /cache (multi-slot), and unlimited in /data and /sdext (External Card).
Support F2FS and Ext4, auto-detect, just need support in your ROM and all will works (not tested because no F2FS support for mine device )
If I can ask: where /data goes? I mean /data/app, /data/data, etc., not /data/media)?
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
ch3mn3y said:
So I tried to mod cyanhacker 2.0 to work from extsd, but app FC's at 1.4%. Tried last 8.0.0. Anyone know which one works with our device or this rom (don't know which one cause FC)?
Click to expand...
Click to collapse
The rom is stored in any partition in a folder called "multiboot", try other rom or old app versions.
Enviado de meu E435 (L3 II Dual) usando Tapatalk
I used this: DualBootPatcher-8.0.0.r2115.g279e1b2-win32.zip (last build from 09.01.2016). It patched the file (older ones couldn't open the archive). Now i will try to flash it on my device and than i will probably use app from the same build (DualBootPatcherAndroid-8.0.0.r2102.gd35e5db-snapshot.apk).
Naah, i use newest app. Zips can be edited on Windows machine.
Small request: any chance to move /cache and /data to the same folder as /system? Or at least /data (as /cache is more temporary) as it can become big for one rom and we have less than 3GB of space on this partition...
Sent using XT1562 - stock 6.0 (retasia DualSim)
---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------
Bug?
After reboot from extsd rom back to primary, app on ptimary doesnt find sdext rom. I can only choose primary one.
Only change on sdext rom I did is installation of app...
Sent using P700 - Mahdi-Rom/SKernel
Check in external card the multiboot folder.
This app have a lot of bugs, use the zip in DualBootPatcher site, for cat the logs, and we can see if something goes wrong and report a bug.
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Its ok. After 2 reboots of primary rom, sdext one is back and after next two reboots between roms its still there. Dont know what was wrong, but right now i suppose there wont be any useful info in logs.
Downloaded the logs zip, so next time will use it.
It works really fast from class 4 sdcard. However I thought that extsd is 2 partition and created one
Sent using P700 - Mahdi-Rom/SKernel
Thread closed as per OP request.
-XDA Staff