yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] munjeni:
Bootmenu seems final, but multiboot.sh is not final, I have made them externaly so all of us can edit them without needs for compiling new bootmenu version. All things related to patching, installing... is in multiboot.sh, everyone can edit them and make things better!

Things is a bit complicated, but in comparation with version 1.0 things is a lot automated and a lot easy than manualy editings! If few clicks your rom is ready, yes but not for totaly noobs, but for users who have some small skills things is very easy, trust me! Simple folow first post and you will install main rom and cm11 very easy. You can not use bootmenu on locked bootloader!
[Xperia Z1 Original Android Development] munjeni:
And another thing, see this post from Xperia Z1 Compact forum -> http://xdaforums.com/showpost.php?p=52830021&postcount=45 , so CM11 roms is working, SlimKat roms is working, Resurection roms is working, thats comfirmed! I have replied to his post related to the his failed attemt to extract DooMkernel here -> http://xdaforums.com/showpost.php?p=52842202&postcount=46 so he failed because this -> http://xdaforums.com/showpost.php?p=52825841&postcount=99 Hope this help!?
[Xperia Z1 Original Android Development] munjeni:
New version of the bootmenu_honami.rar archive is out! Changelog is in multiboot.sh script :

- improved main rom step (if some one completed sucesfully first step aka main rom step and want to change main rom kernel and ramdisk, script is now a bit improved (there is now check for zImage-dtb and initrd.gz instead of check for empty settings.ini, so everyone can now easilly change main rom kernel and ramdisk) - simple remove old zImage-dtb and old initrd.gz, put boot.img to the mainrom folder, reboot to bootmenu, proced main rom procedure, script will generate a new kernel and ramdisk needed for booting into main rom! No need to delete settings.ini anymore!)
[Xperia Z1 Original Android Development] ntmohammad:
thx a lot ! finally i could complete first step successfully , my wrong was using doomkernel or adv stock kernel v03 .

i extracted sony official kernel.sin with flashtool , it gave me kernel.elf . i used it and everything are fine ^_^ thx a lot :D

now i want to see can i use carbon rom as second rom :D

u are the best munjeni :D

edit : unofficial carbon build 7 installed as second rom successfully ! and my main rom is KitSlim_FullPower-V4.1 .

if i try other roms , i wil report :D

second edit : i puted pimped kernel into carbon rom zip .(deleted caron's own kernel and puted the pimed kernel) and it has been installed as third rom successfully
[Xperia Z1 Original Android Development] munjeni:
Every kernel have his own kernel modules (/system/lib/modules) which is diferent on every kernel, hope you understand what I mean. So if your /system/lib/modules is from diferent kernel (for example from DooMkernel) than your main rom will not work correctly. So do not forget to replace kernel modules if you installed diferent kernel for your main rom!
[Xperia Z1 Original Android Development] HypoTurtle:
Minor "improvement to the multiboot.sh.

You could derive NAME from build.prop: NAME=`unzip $ARG 'system/build.prop' | cat system/build.prop | grep ro.build.display | cut -d ' ' -f '1,2' | cut -d '=' -f '2' | sed 's/ //g' | sed 's/userdebug//g'`

also a check around the making of data.img: if [ ! -b /data/media/0/bootmenu/$NAME/data.ext4 ]; then ... should allow ROM/system.img to be updated and data to persist.

Haven't checked all the build.prop's to see if there's any potential clashes/issues. The above NAME would give cm_amami-4.4.2 for candykat, alternatively: NAME=`unzip $ARG 'system/build.prop' | cat system/build.prop | grep ro.modversion | cut -d '=' -f '2' | cut -d '-' -f '1'` would be CandyKat. I just don't know if ro.modverion is present in all roms like ro.build.display is.
[Xperia Z1 Original Android Development] ntmohammad:
can i change the space of systam and data for second rom ?
[Xperia Z1 Original Android Development] HypoTurtle:
munijeni has the system size set to automatically change according to the size of the rom (you can change it but shouldn't have to)

for data you could change the value in multiboot.sh : the line is dd if=/dev/zero of=/data/media/0/bootmenu/$NAME/data.ext4 bs=4096 count=128000 (128000 is about half a GB I believe).

Alternatively you could download the tools here and resize it after the install by running: "resize2fs /data/media/0/bootmenu/$NAME/data.ext4 [new_size]" while running a different ROM replacing $NAME with one you want to change.
[Xperia Z1 Original Android Development] Chocolatetrain:
Deleted :fingers-crossed:
[Xperia Z1 Original Android Development] munjeni:
First of all thanks, I love all sugestions! but I used name of the zip as a name of rom - from two reasons: First reason: For example some users will install for example 3 cm11 nightlies so every nigthly will have name for example cm-11-20140520-NIGHTLY which have date,time,year string so users easilly know which of the nighties is runing in these time... I think my way is better idea than having real name of the rom - using build prop name! In any way everyone can easilly change menutitle displayed in boot menu, simple open settings.ini and change menutitle to something wanted.

Seccond reason: If ro.build.display from third rom is the same like seccond rom than seccond rom will be overwritten! :)
[Xperia Z1 Original Android Development] munjeni:
Yes you can change in multiboot.sh or use tool HypoTurtle mentioned! I have set by default:

- userdata 500mb

- cache 50mb

- system is calculated by formula: (zipsize * 2) + 100mb

100mb in formula is space for gapps
[Xperia Z1 Original Android Development] munjeni:
NOOOO!!! DO NOT DO IT since if you replace META_INF you will overwite main rom partitinos!!!!!!!!!! Remove your post please!
[Xperia Z1 Original Android Development] Chocolatetrain:
Then what do you think i should do?
[Xperia Z1 Original Android Development] munjeni:
You not folowed what I said before. You have not redownloaded rom packages after new version of the bootmenu so probably you have patched your zip earlier (two times :)) so with your lucky you had meta-inf allready patched by an old bootmenu so your main partitions lucky get not overwriten :D Please redownload your rom which you want to patch! Old versions of the bootmenu patched zip directly instead of making xxx.patched.zip.. hope you understand now why you failed...
[Xperia Z1 Original Android Development] Chocolatetrain:
Yeah i guess so but i downloaded it 2 hours ago so it wasn't modified by any bootmenu or scipts, but anyway thanks.
[Xperia Z1 Original Android Development] munjeni:
No way since I think error definitelly will encounter if there is a space! There is no way to prevent that, but maybe only to write warning message in first post :(
[Xperia Z1 Original Android Development] munjeni:
Hmm, thats a good idea!
[Xperia Z1 Original Android Development] munjeni:
I don't think since no one rom contain /dev/loopXX in updater-script ! You definitelly used meta-inf from an allready patched zip since your main rom partition is stil there. Be carefull next time if you realy want to save your main rom... just sugestion ;)
[Xperia Z1 Original Android Development] munjeni:
New version of the bootmenu_honami.rar is out, I have changed to this way -> http://paste.ubuntu.com/7502590/ thanks for sugestion! :) Now users can rename zip to something like for example cm11_blabla_v3 and every next version so after patching and installing the zip which have the same name like previous zip version - data will not be deleted and all userdata from previous rom version will be saved so rom will be like an update. :)
[Xperia Z1 Original Android Development] munjeni:
I thinked to use --bind mount without needs for using file based partition trought a loop device, but problem is cwm since cwm trought menu can not mount trought fstab lines if there is bind mounts :( I tried few ways to ge bind working but bind not working in cwm :( That will be the best solution if some one manage cwm working using bind mounts in fstabs!
[Xperia Z1 Original Android Development] HypoTurtle:
What I thought I saw in multiboot.sh was that the loops had been attached - with system.ext4 loop mounted as /system (meaning you could unzip the rom folder into it). But I now see that it isn't being mounted in the script.

What I was saying earlier was that adding sed 's/ /_/g' as in "NAME=`echo $ARG | awk -F "/" '{print $NF}' | sed 's/.zip//g' | sed 's/ /_/g'`" should replace all the spaces with _ , I'm not sure why the awk is there "NAME=`echo $ARG | sed 's/.zip//g' | sed 's/ /_/g'`" is what I'd have.
[Xperia Z1 Original Android Development] munjeni:
Things working in 2 steps:

1. patch rom.zip, create partitions, create zImage-dtb, patch/create ramdisk, add rom to the settings.ini, reboot

2. boot into cwm of these new rom to install patched rom to system.ext4 of these rom

If I modify $NAME argument I will need to rename zip archive and folder booth, but I am not sure what will be happen in ramdisk or in bootmenu since things is hardcoded to name of the zip. In any way I not care since I have warned users to write "_" instead of " " to folders and files naming. Maybe I can add AWK line you mentioned between start of patching procedure in multiboot.sh, for example to rename zip and replace spaces in naming (which is by now I think great idea by you!)

Edit:

No way since $ARG contain argument from bootmenu, for example BAD argument is sent from bootmenu to the multiboot.sh by this way:

/storage/sdcard/rooms and kernels/cm11 version2.zip

there is no way to rename "cm11 version2.zip" because line 56 in multiboot.sh will fail if I rename zip or folder:

/data/media/0/bootmenu/bin/7za x -so $ARG META-INF/com/google/android/updater-script > $BASE/$NAME/META-INF/com/google/android/updater-script

Edit:

NAME=`echo $ARG | sed 's/.zip//g' is used for folder creation reason!
[Xperia Z1 Original Android Development] HypoTurtle:
Is it the unzipping thats the issue

Would the issue not be solved by using brackets ie ${ARG} ?

What sort of output is arg? I though it was just the zip name but its /sdcard/ROMnameHERE.zip isn't it (that explains the awk you're using; I'd just use `cut -d '/' -f '2' ` instead ).
[Xperia Z1 Original Android Development] munjeni:
Argument sent from bootmenu to multiboot.sh is full path to zip including zip name.
[Xperia Z1 Original Android Development] Ashray_Vk:
Hi, can someone make a general discussion thread for the multiboot??

And can anyone give a detailed tutorial on how to use doomkernel and a stock based custom rom as main rom?

Thanks in Advance
[Xperia Z1 Original Android Development] abbychauhan:
Why not discuss here only.. and u ll get Expert Dev. Advice also.. i dont think munjeni will say no to that..
[Xperia Z1 Original Android Development] ntmohammad:
i did somthing that it make possible using doomkernel (v18) for mainrom kernel :D

i unpacked kernel with pc , it gave me ramdisk.lzma . i renamed it to initrd.lzma , and edited settings.ini . to this :

then only thing we need , is zImage-dtb . like patching second rom , patch the zip including only doomkernel . now u will find zImage-dtb for doomkernel . replace it with mainrom zImage-dtb , and copy initrd.lzma into mainrom folder . reboot .it must work now :D

i used "Android Kitchen 0.3.1" for unpack the kernel . serch it in google .it exists on xda . i dont know the rules , so i cannot link it here
[Xperia Z1 Original Android Development] munjeni:
You forgot one important thing! Important thing is:

- do not forget to replace kernel modules in /system/lib/modules if you using another kernel! Every kernel have his own kernel modules which is paired with kernel!!!
[Xperia Z1 Original Android Development] munjeni:
Here is general discusion thread! :) You can ask whatever you want here! DoomKernel... simple put boot.img from domkernel rom to the mainrom folder, delete old zImage-dtb and old initrd.gz, proced main rom step trought bootmenu, it will generate you all you need! After you boot these rom do not forget to replace kernel modules "/system/lib/modules" since every kernel is paired with his own modules (you can not use modules unpaired)

Detailed step:

1. install custom rom (if you were unable to install custom rom since you have installed bootmenu than simple flash boot image of these rom, reboot to recovery, flash rom)

2. prepare everything before you going to install bootmenu (mean: copy all your zips to an folder on your externl storage (remember to use external storage!)

3. you want DooMkernel?? Ok, copy DooMkernel boot.img and /system/lib/modules folder to main rom folder in bootmenu folder on your internal storage

4. install bootmenu

5. continue to here -> http://xdaforums.com/showpost.php?p=51901049&postcount=1

If you are unable to install custom rom, simple go to forum thread of these rom and carefully read about how to install them, when you complete custom rom installation than go back here and read tutorial from first post, I am sure you will success! If you have more questions, simple ask, someone will help you I am sure!
[Xperia Z1 Original Android Development] munjeni:
Thats no need in latest bootmenu + latest bootmenu_honami! I do not understand why you guys complicate things? Is tutorial from first post not enought for things? :( Simple delete old zImage-dtb and old initrd.gz from mainrom folder, put DooMkernel boot.img to the mainrom folder, reboot to bootmenu, perform main rom step, done. If kernel modules located in /system/lib/modules of the your main rom not have DooMkernel modules than simple install DooMkernel modules by extracting them from DooM zip, reboot and you are done. Allways remember to replace modules if your rom have diferent kernel ! Remember... every kernel is paired with kernel modules, you can not use an kernel with another kernel version modules! You need to replace kernel modules if kernel version is diferent than your kernel modules!
[Xperia Z1 Original Android Development] ntmohammad:
i remember u do not have z1 , u have z1 compact . (correct me if im wrong) and i guess u do not test the mainrom step with doomkernel yourself for our device . i did it many times . after putting boot.img into mainrom folder and patching mainrom.zip , no zImage-dtb and no initrd.gz will be made in mainrom folder , i can complete this step only with official sony kernel . after patching doomkernel v18 as second rom ( not mainrom kernel) . it will give u a initrd.gz with 84 b( look at the picture). i dont know anything of your script . but i guess the reason is the ramdisk of doomkernel has been compressed in lzma.( im not sure , i just guess).

hope this can be usefull .

thanks a lot for ur hard work . multibooting was my wish and this is first time i experience it

edit: i know ur script will modify ram disk and the ramdisk mading for second rom can not be used for the main kernel . i just want to explain the script can not unpack doomkernel . also adv stock kernel , made by doomlord ,can not be used for mainrom step . it's ramdisk is not compressed with lzma .i do not know anything more :D
[Xperia Z1 Original Android Development] munjeni:
Did you used Z1-DooMKernel-v18.zip ?
[Xperia Z1 Original Android Development] ntmohammad:
not for a rom . just for making zImage-dtb .
[Xperia Z1 Original Android Development] munjeni:
Hey guys, BIG SORRY! Kernel_dump tool which I made was primary made for dumping boot image from /dev/block device but I added support for dumping boot image from boot.img, so tool dumped boot.img by overwriting boot.img byself and making boot.img empty :o, Bug afected only main rom step - boot.img only so no one was abble to dump any boot.img :o Now tool is fixed and every boot.img can be dumped now, SOOOORYYY! :o Simple redownload bootmenu_honami.rar and replace whole bin folder in your bootmenu folder by bin folder from archive! DooMkernel boot.img and any other will proced sucesfully!
[Xperia Z1 Original Android Development] Chocolatetrain:
Thank you! It finally works, i felt so stupid aha.
[Xperia Z1 Original Android Development] munjeni:
Sorry man, I doing my best to make things better and better, the whole idea is very comprehensive and sometimes things going very comlicated so everybody makes mistakes including me, I am so sorry to all who lost his time in making stupid main step, sorry again! Hope things in main step going easy now after bug solved. Thanks [MENTION=4502957]ntmohammad[/MENTION] for pointing me to the right direction by explining in detail about a bug, by your help bug is located and solved!
[Xperia Z1 Original Android Development] munjeni:
Now I thinking to add support for stock and stock based roms, there is only one problem:

- since stock or stock based roms have cwm inside /system/bin folder instead of cwm in boot image ramdisk like cm and cm based roms, I have no idea how to complete these problem. Probably we need to add an "on the fly" cwm injecter which will patch stock ramdisk by injecting cwm into stock ramdisk. Anyone have good idea?? Maybe we can improve booth (cm and stock based roms) ?? How? How multiboot is working on twrp based multiboot, anyone analysed?
[Xperia Z1 Original Android Development] guddu2011:
I have DoomKernel as my mainrom, it is working fine but it is taking nearly a minute to load up kernel screen.
[Xperia Z1 Original Android Development] munjeni:
You mean android screen? If yes than thats ok since kexec can not load them faster.
[Xperia Z1 Original Android Development] Chocolatetrain:
The splash screen.
[Xperia Z1 Original Android Development] munjeni:
Its related to DooMkernel only?
[Xperia Z1 Original Android Development] Chocolatetrain:
I didnt have this problem when i used the official .sin file, i don't know if it happens with advanced stock kernel, probably so.
[Xperia Z1 Original Android Development] munjeni:
Ok but how can I help since I am Xperia Z1 Compact owner, on my phone there is no these problems, so I can not help. You can try DooMkernel without bootmenu and see if problem is related to kexeced kernel or problem is related to the kernel itself, I don't know...
[Xperia Z1 Original Android Development] munjeni:
Did you tried stock kernel? What is happening than?
[Xperia Z1 Original Android Development] guddu2011:
havnt tried it yet.

can u please tell me y cm11 as my other rom is not getting mobile network, wifi bluetooth and all stuffs are working fine just mobile network isnt working
[Xperia Z1 Original Android Development] munjeni:
You have installed cm and you have no mobile network? Did you configured "access point names" in mobile data settings?
[Xperia Z1 Original Android Development] munjeni:
What about if problem is kernel related? :rolleyes: Try with stock kernel!
[Xperia Z1 Original Android Development] guddu2011:
i mean there is no signal of my carrier on cm but it is working on stock main rom
[Xperia Z1 Original Android Development] munjeni:
Our thread is not CM related, but did you tried to change network mode? Did you maybe changed something for example used another kernel...? Please ask in proper forums, our forum is bootmenu related.
[Xperia Z1 Original Android Development] guddu2011:
used it as main rom, network is good but for secondary rom, there is no network
[Xperia Z1 Original Android Development] munjeni:
Did you read what I asking you? I asked you ...did you tried to change network mode in mobile network settings (mean - did you tried 2g 3g...etc mode) ?
[Xperia Z1 Original Android Development] guddu2011:
tried lte, 3g 2g. and not using any other kernel
[Xperia Z1 Original Android Development] munjeni:
Ok, did you tried the same rom by installing them as a main rom (just to make sure rom is working corectly) ? Wich rom you have installed, what is version?
[Xperia Z1 Original Android Development] guddu2011:
installed the same rom as a main rom and its working perfectly. CM11 21-05
[Xperia Z1 Original Android Development] munjeni:
And the same rom running as a seccond rom is not working ? Ok, but are you 100 percent sure you have not missed something? I not believing from one reason - because the same rom working as a main rom. How many times you have installed the same rom... There is a lot of questions, probably I will not reaply because I believing negative until someone comfirm problem like you have. Did you tried another cm version? Did you tried to remove whole cm folder in boot menu and try fresh downloaded cm rom...?
[Xperia Z1 Original Android Development] guddu2011:
tried cm11, pacman and paranoid android, no signal on all of them on secondary rom, but working on main rom
[Xperia Z1 Original Android Development] munjeni:
What is bootloader and baseband version on your phone? Did you updated your phone oficially to the latest kitkat version (mean by sony pc companion)? I have no idea why thats happening to you!
[Xperia Z1 Original Android Development] munjeni:
Probably your phone hw version is a bit diferent than most of other models so something kexec related is a bit confused, probably kernel load address, hmm, by now thats what I thinking only. Please let me know if you found something true from our 2 posts!
[Xperia Z1 Original Android Development] Chocolatetrain:
I had a lot of problems but they were all fixed by fully flashing a .757 ftf and restoring the ta then re-rooting and this fixed it.
[Xperia Z1 Original Android Development] munjeni:
Probably latest partition layout, baseband and bootloader was missing :)
[Xperia Z1 Original Android Development] abbychauhan:
Most probebly because C6902 Users have to flash Modem Zip files to get the C6903 Roms working (And all Z1 ROMs are made for C6903) .. Plz check with flashing of Modem.. It might solve ur Signal problem.

Use any of these ..

http://xdaforums.com/devdb/project/dl/?id=953

or

http://xdaforums.com/showthread.php?t=2614645

or

https://mega.co.nz/#F!gUcSjQQJ!KRtooymqMvSII2hHvOoATA
[Xperia Z1 Original Android Development] guddu2011:
tried all 3, still no network

is it working for u?
[G2 General] Klementh:
I just registered because I made a discovery which I think is worth sharing here, and that is, as the title says, that having Knock On enabled drains the battery considerably. Also I'm pretty sure it started happening after the KitKat upgrade, so it's not an inherent problem.

I can't post a thumbnail or normal link as a new forum user, so please paste this into your address bar to see the proof pic:

i.imgur.com/pqtUlSM.png (only 60kb)

In that image, the blue bubbles mean the times when I disabled Knock On, and the red one when I enabled it. The phone had Wi-Fi enabled and was idle almost all the time with light usage after the last bubble, but it's not the most relevant part.

My G2 is a 32GB D802 from Vodafone Spain, and it's unrooted and untouched, except I disabled all the bloatware I could. I don't use any app for battery or software management.

That's all, check for yourselves and let's hope LG fixes it in the upcoming Knock Code update.

Edit: realized about attachments.
[G2 General] LenAsh:
It's a little like saying the battery is used more when I'm not in Airplane mode, or if I have the screen on...

These are Smartphones and are designed to be used. Certain features may consume a little power, but that's why we have a huge battery. I'm not sure if you see this as a problem or not, but I get 2-3 days of moderate usage with everything on and syncing. With Knock on - I've never turned it off. Great feature.

I attach my KK battery life for reference - very acceptable.

And yes, Knock code (for what use that gimmick will be - remember the fuss over the now-forgotten Face Recognition?) will obviously use a little battery.
[G2 General] Klementh:
Sounds logical LenAsh, but you ignored the part when I said It started happening with KK. See the almost straight line before the red bubble? that's how it looked like on JB after a night with Knock On enabled.
[G2 General] simms22:
edited
[G2 General] ECrispy:
Might be true! Almost everyone on KK says that -

1. KnockOn is much more responsive

2. battery life has gone down

Its quite possible that LG increased the current draw and/or polling period of KnockOn to get #1 which causes #2.
[G2 General] khaytsus:
So it uses like .2%/hr vs .1%/hr or something? Meh.