yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] SamadiPour:
sorry guys

didn't anyone found a way for this problem?
[Xperia Z1 Original Android Development] abbychauhan:
It very unlikely that u ll get a answer as this project looks abandon, so ur on ur own
[Xperia Z1 Original Android Development] smart8bits:
hi

any one can flash MIUI as secondary rom?

if yes can you tell how? :)
[Xperia Z1 Original Android Development] Chocolatetrain:
Yes MIUI is my third ROM, you first use this tool (http://xdaforums.com/showthread.php?t=2662941) to build a rom zip from a clean install of miui, then you use that to patch your rom, but it did fail a few times but I found a work around, you go into the zip and remove the kernel.sin or whatever format the boot is in, I forgot and then replace it with a kernel like trinity v2.9 (boot.img) and then edit the updater script to remove the bit that detects the model, then go to the bottom of the scrip and replace the kernel.sin with boot.img, it is a method that works every time :) Thanks to [MENTION=5618877]abbychauhan[/MENTION] for showing me the guide however I found the workaround for MIUI and [MENTION=4120742]munjeni[/MENTION] for the rom cooking tool.
[Xperia Z1 Original Android Development] blueether:
[MENTION=4120742]munjeni[/MENTION], I was thinking of porting this to the Z-Ultra. Is the GitHub code upto date?
[Xperia Z1 Original Android Development] abbychauhan:
Have u tried to port Multi ROM. BTW i think Git is updated upto the last released of Multi Boot after that Munjini left the project.
[Xperia Z1 Original Android Development] Garcia98:
I have ported MultiROM to Xperia Z1c but it works in a strange way, MultiROM menu gets loaded twice when you select secondary ROM, so secondary kernel needs to be also kexec patched, otherwise it won't boot. If anyone want to help me it would be awesome :)
[Xperia Z1 Original Android Development] abbychauhan:
Well i only asked because if someone is trying to PORT then try for Z1 too.
[Xperia Z1 Original Android Development] davidteri91:
Thanks I will take a look for honami :)
[Xperia Z1 Original Android Development] abbychauhan:
Ahh.. that would be superb man.
[Xperia Z1 Original Android Development] Aaskereija:
would be great if you could bugfix some things on multiboot (like cwm link for main rom not work and is useless in bootmenu, especially if the rom use twrp)
[Xperia Z1 Original Android Development] Garcia98:
MultiROM is totally different from Multi Boot Menu of munjeni ;)
[Xperia Z1 Original Android Development] Aaskereija:
my fault. i overread that point :)
[Xperia Z1 Original Android Development] HypoTurtle:
0. So userdata block => /multiboot works as is with the fstab line

1. Was thinking that if 0 (above) was false then using a folder that is definitely there prior to the fstab line being called may work, I know for example: mount --bind 123 /mount, then running mount --bind 456 /mount would result in 456 being mounted rather than 123, a dirty workaround but useless anyway as I don't think a bind mount will take priority over a block mount.

2. Seen a few examples were LABEL= looked like it was being used to create a label in fstab, but in actuality it just uses a prelabed filesystem instead of writing the full path

3. Thats odd... could it be a toolbox/busybox issue?
[Xperia Z1 Original Android Development] munjeni:
3. I think thats a cwm isue since ramdisk rc command mount_all mount them! Busybox via adb shell allso mount them! But trought cwm menu I can see that it is mounted, I can umount them but not mount!

In any way my progress in one click solution is almost done, new version soon! Short... principe is:

1. Chose rom.zip to patch from bootmenu (I have implemented modified install function) -> bootmenu read name of the archive -> forward name argument to the script in bootmenu folder -> script doind the rest, create folder to botmenu with these name, extract boot.img and patch all ramdisk which is in boot.img, patch updater script, repack zip archive with patched things, create settings.ini entry, create file parritions (or if we get bind working than thats great :), pack ramdisk, append dt to zimage

2. Step 2 - user reboot again to the bootmenu, new rom entry in bootmenu is displayed, user chose to boot into the new rom, on led blink press volume button to enter into cwm ramdisk (all xperia roms have 2 ramdisks - main and cwm! You know that?), install modified rom.zip directly to the file partitions (or if we get bind than thats great again :))

3. Step 3 - rom is installed and ready :)

So you know now what I mean and how things working. You understand now why I can not use bind?
[Xperia Z1 Original Android Development] HypoTurtle:
Yeah thanks for that, I've seen the boot.img you guys have - looks a tad odd at first glance. The only think I wasn't 100% sure about is what is shared between what's essentially the roms ramdisk and the recovery ramdisk, other than the kernel: the recoveryonly option in the roms ramdisk had me a little confused - should all the mount options be placed in this fstab with the recoveryonly option?

From what I've seen: device fstab and recovery fstab are structured differently and you shouldn't need to add mount_all to an .rc file

"/system none /muliboot/media/0/bootmenu/ggg/system bind" in recovery.fstab
[Xperia Z1 Original Android Development] munjeni:
Every xperia rom have 2 separated ramdisks, one ramdisk is rom ramdisk and another one is cwm ramdisk. All two is totaly separated! In system/bin there was replaced cahrgemon binary with chargemon script whick doing "choice" for boot. You can look into chargemon scrit to understand how boot and cwm working on xperia phones. All chargemon hacks is done because we have no dedicated recovery partition.
[Xperia Z1 Original Android Development] munjeni:
New bootmenu is out! New principe (I think that is very easy now):

- in no settings.ini (that mean - first time use) than boot into boot menu, chose zip of the your primary rom (make sure your main rom is installed from these zip), boot menu will install things needed for you to boot into your main rom! Simple when you done, reboot again into boot menu (now your main rom will be displayed in boot menu as a new entry, chose these menu to boot into your main rom. Easy? Ofcourse :D

- if there is settings.ini and you allready have main rom installed or more than main rom, than simple chose submenu "patch...", select rom package you want to patch, bootmenu will patch them and will add new menuentru into settings.ini, will patch rom package, updater-script, all ramdisks from rom, will create zimage-dtb and initrd.gz, will create all file based partitions...etc. Reboot again into boot menu (now you have new menu entry added to the boot menu - patched rom), select them to boot, after led blink press volume keys to enter into cwm, install these modified rom package, you are done. Easy? Yes but I not deeply tested thing, but since new principe in our new version - you can look into multiboot.sh (main script for installing and patching roms!) try to fix or improve them, I will be glad if there get something improved! Let me know if you found something bad or better! Enjoy!

WARNING:

- there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
[Xperia Z1 Original Android Development] diabolus81:
deleted :)
[Xperia Z1 Original Android Development] gregbradley:
OMG (facepalm)

No...... Did you even read any of the thread.....
[Xperia Z1 Original Android Development] diabolus81:
hmm truly...no ;) sorry

there were no question ;)
[Xperia Z1 Original Android Development] ntmohammad:
thx for ur great job ! but i could not patch any zip ,,, did u test it on ur phone ? or can sb confirm that this will be work or not ?

(sry if i am noob)

and i have another question , if my main rom package does not including kernel , aka boot.img , can the scrpit patch it ?
[Xperia Z1 Original Android Development] munjeni:
Curently only packages which contain boot.img or kernel.elf can be patched! For main rom you can use kernel zip archive (make sure kernel version is the same like in your main rom!) so these kernel and ramdisk will be extracted and used for booting into main rom! You can use diferent kernels but than you will need to use kernel modules of these kernel since without using kernel modules your wifi, bt...etc will not work! So make sure you chose right kernel package! Later you will need to change title of the main rom in settings.ini since title will be used from name of the zip (for example if you used kernel package than title in bootmenu will be for example "doomkernel_v.1234xxxblabla")! Do not change paths or to rename folders created by patch because paths is harcoded! If you rename folders or you change paths in settings.ini, than things will not boot! You can change paths only for main rom!

Curently only main rom is working because multiboot script need to be repaired, I am working on them now, hope today I fix them for installing cm nightlies. Later I will try to fix script to be used for patching stock based roms.
[Xperia Z1 Original Android Development] munjeni:
New version of the multiboot.sh is out! Simple redownload bootmenu_honami.rar and extract bootmenu folder to the your internal storage. Changelog:

- fixed multiboot.sh script, now you can patch cm11 nightlies and install (I have tested and confirm it working!)

- some missing binaries needed for booting

Warning:

Previos multiboot.sh patched original package instead of making new one, so if you going to try cm11 nightlies than strongly recomended is to redownload these zip since if you used previous script than for sure these zip is corupt! New version create new zip instead of patching original one (which is better idea). Enjoy cm11 nightlies in multiboot! :) I not tested stock based roms (probably roms will not work since most of the these roms have no cwm inside ramdisk like cm11 roms so you will not be abble to boot into patched cwm since cwm not exist)... I will try to do something related to the patching stock base roms. Main rom and cm11 roms is tested and working!

Allso, (if you using multiboot first time and you never done that before) make sure multiboot.sh have permission 755 !! Simple go to /data/media/0/bootmenu using an root file explorer and make sure multiboot.sh script have permission 755 (-rwxr-xr-x)! Happy patching! ;)
[Xperia Z1 Original Android Development] Chocolatetrain:
This still doesn't work for me, it says the patching was unsuccessful, any tips?
[Xperia Z1 Original Android Development] munjeni:
While you get these message simple establish adb connection and give me a log:

adb pull /tmp/recovery.log

I will look into log and let you know what is failed! Probably you forgot to give 755 perm to the /data/media/0/bootmenu/multiboot.sh ??
[Xperia Z1 Original Android Development] Chocolatetrain:
I did change the permissions, let me pull the log lol

There you go;

oh i realise it says the permissions were incorrect, let me try again :P
[Xperia Z1 Original Android Development] munjeni:
You have 2 problems:

1. sh: /data/media/0/bootmenu/multiboot.sh: Permission denied which mean you not gaved permissin to multiboot.sh !!! Simple fix that using adb while you are in bootmenu:

adb shell chmod 755 /data/media/0/bootmenu/multiboot.sh

2. never use space in folders naming like you done here: "Root and Recovery" ! Instead of that rename you folder to something like: "Root_and_Recovery"

Everything will work after that! Let me know! ;)
[Xperia Z1 Original Android Development] Chocolatetrain:
Still isn't working D:

By the way, i don't have a settings.ini file or an unpacked boot.img
[Xperia Z1 Original Android Development] munjeni:
If you have no settings.ini that mean you have no main rom! You need to generate them! Do it in few steps:

1. remove settings.ini if you failed in previous atempt

2. Reboot into boot menu

3. Open submenu "patch..."

4. Locate your mainrom package (make sure zip contain boot.img or kernel.elf and make sure thats the same kernel like your primary rom kernel!)

5. Apply. Step 5 will generate initrd.gz, zImage-dtb, and will create folder for you main rom, create settings.ini and add entry to settings.ini

When you done main rom steps than you can continue on cm11
[Xperia Z1 Original Android Development] Chocolatetrain:
I tried, this is where it gives me errors
[Xperia Z1 Original Android Development] munjeni:
There is no errors in your logcat! Check zip of the your main rom package, make sure there is boot.img ! If there is no boot.img simple put them to the zip (make sure boot.img kernel version is identic like kernel of the your main rom).

Allso make sure you reboot after you do something (new menu will apear on you screen if you have success)
[Xperia Z1 Original Android Development] Chocolatetrain:
I tried the latest cm nightly, i really can't get it to work, I'll try again tomorrow, thanks for the help;)
[Xperia Z1 Original Android Development] munjeni:
Folow carefully what I say in posts and you will get success! You can not start with cm11 if you have no completed main step aka main rom! When you complete main rom and get your main rom working (booted) trought bootmenu than you can start working in seccond, third...max 10 roms! Good luck! :) I think things is a lot easy in new bootmenu version since things is automated.
[Xperia Z1 Original Android Development] ntmohammad:
i did everything to change the permisson of multiboot.sh , but it is impossible :D

with root expolrer or other apps , it says , some file systems do not allow permission changes

and via adb , it looks the permission has changed , but in log , it says Permission denied .

do have solution for this ?

(sry for my bad english and if im noob )
[Xperia Z1 Original Android Development] Chocolatetrain:
I had this problem but instead go to data/media/0/bootmenu
[Xperia Z1 Original Android Development] munjeni:
New bootmenu.img is out! Simple install via fastboot command:

fastboot flash boot bootmenu.img

Changelog:

- no need to mess with permissions anymore since permission for multiboot.sh will be set on bootmenu startup

Going now to improve multiboot.sh related to the creation of the main rom.
[Xperia Z1 Original Android Development] munjeni:
New version of the bootmenu_honami.rar is out! Changelog:

- for main rom creation - you no need any zip anymore, simple extract bootmenu_honami.rar archive to the your internal storage, put boot.img or kernel.elf (make sure these kernel is the same like in your primary rom) to the mainrom folder, reboot into bootmenu, chose "patch...", navigate to internal storage, navigate to bootmenu, navigate to mainrom folder, chose mainrom.zip, install, you are done main rom step! After sucesfull main rom step you can only than install another roms! Happy patching and let me know! Hope things is more easy now. ;)
[Xperia Z1 Original Android Development] ntmohammad:
still i got this error :
[Xperia Z1 Original Android Development] munjeni:
Probably you have running previos bootmenu version? Install new bootmenu.img version 1.3 and no more perm problems!
[Xperia Z1 Original Android Development] Chocolatetrain:
I still have this problem as well :/
[Xperia Z1 Original Android Development] munjeni:
Hey sorry, I foun why you have these perm problems :( Please do:

abd shell chmod 755 /data/media/0/bootmenu/bin/*

Going to make new version, sorry!
[Xperia Z1 Original Android Development] Chocolatetrain:
Still doesn't work for me, should i send a log?
[Xperia Z1 Original Android Development] munjeni:
Yes, please send a log.
[Xperia Z1 Original Android Development] Chocolatetrain:
Thank you, also,

here;
[Xperia Z1 Original Android Development] munjeni:
Thanks, finaly I will solve now, sorry! Hope all get working in next version, will make new now. :o
[Xperia Z1 Original Android Development] chrisi091:
I have one question for the installation guide must we rename our rom that we used as mainrom to mainrom?
[Xperia Z1 Original Android Development] munjeni:
Yes, mainrom ONLY can be renamed, but make sure you modify path in settings.ini if you renamed mainrom folder! Other roms can not be renamed since ramdisk paths is hardcoded and must match folder name! Menutiltle you can change for every rom!

New bootmenu.img version 1.4 is out, will definitelly fix permissions problems! I have tested now!
[Xperia Z1 Original Android Development] chrisi091:
Yeeees man it function a very special thanks to you and your hard work
[Xperia Z1 Original Android Development] munjeni:
Finaly perms problem solved :o Did you got main rom working?
[Xperia Z1 Original Android Development] chrisi091:
i did a little mistake i have put boot.img in mainrom folder instead of kernel.elf but the process to make an entry as mainrom did function

update: it makes sucessfull an entry and boot in my mainrom
[Xperia Z1 Original Android Development] munjeni:
If you were unable to get main rom working since you got mistake with boo.img than simple remove settings.ini and repeat process because when settings.ini exist or when an entry is added to the settings.ini than you are unable to make main rom because script is attempted to make main rom ONLY AND ONLY when there is no settings.ini or when there is nothing in settings.ini ! So simple remove settings.ini, put boot.img or kernel.elf to the main rom and repat whole main rom process creation. When you get main rom working than the rest is not so hard :)
[Xperia Z1 Original Android Development] munjeni:
You can put kernel.elf and allso you can put boot.img, booth will work since I made a tool for format detection! You can allso use boot partition dump (by renaming them to kernel.elf or to boot.img) and it will work too! :)
[Xperia Z1 Original Android Development] munjeni:
This is a time for next step - patching cm11 and adding them to the multiboot :D
[Xperia Z1 Original Android Development] chrisi091:
that i want make now :D i will use slimkat
[Xperia Z1 Original Android Development] Chocolatetrain:
Okay so just to make it clear do i rename the cm nightly to mainrom.zip with the boot image in that folder and patch the zip to make the first entry in bootmenu?
[Xperia Z1 Original Android Development] munjeni:
Ok but to let you know, I have tested only cm11 nightlies and I can confirm cm11 nightlies is propertly patched and working, but you must know - if multiboot fail to patch propertly your slim kat, than probably your main rom partitions will be overwiten so you will lost your main rom!! Report here if you get slim rom working, I am glad to know. :)
[Xperia Z1 Original Android Development] munjeni:
No! These thing is only for main rom! You no need to rename anything if you completed main rom creation (1.)! And allso you no need to copy boot image! Simple folow (2.) from here -> http://xdaforums.com/showpost.php?p=51901049&postcount=1

Please read instructions carefully from first post, I am sure you will get them working, thats very easy, trust me.
[Xperia Z1 Original Android Development] chrisi091:
it creates successful the entry for slimkat but when i select slimkat in bootmenu no led blinks so i can no go in cwm and install it
[Xperia Z1 Original Android Development] munjeni:
Slim cat is based on stock rom? If yes, than yes I know these problem! Curently stock or stock based roms is not supported as a seccond rom since stock roms have diferent principe than cm11, for example - cm11 roms boot.img have 2 ramdisks (one is rom ramdisk, seccond is cwm ramdisk), but stock rom boot.img have only main ramdisk (there is no cwm ramdisk) so you were unable to boot into cwm since there is no cwm :( You can install them manually which mean a lot of work. By now there is no 2 click solution for install stock based roms, but I have plan to improve script and make that possible.

I'm curently investigating, hope I get idea and complete these problem. By now I thinking to make something on the fly, for example I planing to patch stock rom ramdisk (add on the fly cwm into them) :)

If some one want to help me than please look into multiboot.sh located under multiboot folder and help me to improve script which will patch everything propertly.
[Xperia Z1 Original Android Development] chrisi091:
cool thanks i install cm11 my mainrom is the googleplay edition ported from the zu
[Xperia Z1 Original Android Development] Chocolatetrain:
Thank you so much for your hard work. it works! :D
[Xperia Z1 Original Android Development] munjeni:
Happy multibooting ;)
[Xperia Z1 Original Android Development] Chocolatetrain:
Sorry to be a pain in the ass but now whenever i try to boot my rom from the boot menu entry it says 'Something went wrong, please check log.' This only happens when trying to boot from the primary rom though.

The log says;

I:Checking for extendedcommand...

I:Skipping execution of extendedcommand, file not found...

Cannot open `/data/media/0/bootmenu/mainrom/zImage-dtb': (null)

Cannot open `/data/media/0/bootmenu/mainrom/zImage-dtb': No such file or directory

Something went wrong, please see log!

Cannot open `/data/media/0/bootmenu/mainrom/zImage-dtb': (null)

Cannot open `/data/media/0/bootmenu/mainrom/zImage-dtb': No such file or directory

Something went wrong, please see log!

Cannot open `/data/media/0/bootmenu/mainrom/zImage-dtb': (null)

Cannot open `/data/media/0/bootmenu/mainrom/zImage-dtb': No such file or directory

Something went wrong, please see log!
[Xperia Z1 Original Android Development] munjeni:
You missing something! Thats happened after your unsucesfull main rom step so script not extracted boot image and not prepared zimage-dtb and initrd.gz! You can try again. Delete settings.ini, put boot.img of the your main rom to the mainrom folder, repeat whole main step, you can do all trought adb shell. Probably you repeated main step but you forgot to place boot.img to the folder!
[Xperia Z1 Original Android Development] olokos:
[MENTION=4120742]munjeni[/MENTION] - I mean nothing else than I write now. Is this going to be the final for of the multiboot? I mean no gui at all, complicated stuff etc.? :(

I think that I'll use it by myself, but not soon. Stock rom would have to annoy me to the extent that I'd go for UB as I'm not so keen on loosing the camera stuff. If that would be for LB then I'd do that ASAP, but this is really complicated, propably would take me some time to get it done and I would loose all of the LB features. :/
[Xperia Z1 Original Android Development] ntmohammad:
at first , sry for my bad english , and thx a lot for ur hard work

i tried ur tutorial many times , i put boot.img in the mainrom folder and patch mainrom.zip , but it didnt extract zimage-dtb or inited,gz

i tried doomkernel v18 , when it doesnt extract , i tried adv stock kernel v03 . no one work for me

next i tried tu patch the zip including my mainrom kernel , so i saw 5 file in the new folder created in bootmenu , i copy zImage-dtb and initrd.gz in the mainrom folder , and when i choosed the mainrom option , for doomkernel v18 it didnt show kernel logo , then it reboot to bootmenu

and for advanced stock kernel v03 , it show kernel logo , and i could enter cwm , but it didnt boot my rom

do u know where is my wrong ? i saw some other one has this problem , too .
[Xperia Z1 Original Android Development] munjeni:
Did you read what I said in previous posts? For example did you read -> http://xdaforums.com/showpost.php?p=52825841&postcount=99 You need to delete settings.ini and repeat whole process is you failed in main rom step!
[Xperia Z1 Original Android Development] munjeni:
You can not use boot.img for example from cm11 to boot into stock rom! You need excatly the same kernel like you had in main rom!