{
"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
1. I'm not responsible for anything, you do all this on your own risk.
2. 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.
3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
4. I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
5. Your device must not be encrypted.
6. To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
7. 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
1. Make sure you are on a rom compatible with these kernels.
2. Flash the required kernel zip.
3. Flash MultiROM_TWRP-xx-xx-xxxx.img on fota partition.
4. Flash MultiRom_xx-xx-xxxx-v31x.zip
5. Done1Adding 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 Rom
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 old)
Modified TWRP - https://github.com/XperiaMultiROM/an...table_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/aweosomeabhijeet/android_kernel_sony_msm8x27 (cm-Kernel)
CREDITs
Tasssadar
Alvinhochun - without his kexec patch, it would have been impossible for me, kudos to him :highfive:
Xperia Multirom
Myself5
Every other dev behind this
If you think my work is good, please consider a small donation
Donate to me
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the M
Donate to Tasssadar
XDA:DevDB Information
MultiRom for Xperia M, Tool/Utility for the Sony Xperia M
Contributors
aweosomeabhijeet, alvinhochun, XperiaMultirom
Source Code: https://github.com/XperiaMultiROM/multirom/
Version Information
Status: Stable
Current Stable Version: v31x
Stable Release Date: 2015-08-13
Created 2015-08-07
Last Updated 2015-08-13
BUGs
NO BUGS as of now
LIMITATIONs
1. For MTP to work in TWRP you need to disable and enable it again.
CHANGELOG :
Code:
2015-08-13
Stable release!
Fixed minor touch issues present in the kernel by [email protected] !
2015-08-07
Beta version
Fixed erasing primary rom with secondary
Fixed wifi
2015-08-07
Initial release!
DOWNLOADS
Kernels with kexec-hardboot support :
XMS-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XMD-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XM_CM_kexec-08-13-2015.zip(has touch screen issue)
Other kernels with kexec-hardboot support:
1. NUI kernel(kudos to dev.)
Instructions to use NUI kernel
MultiROM TWRP :
recovery.img(To be flashed on fota-partition)
MultiROM-zip :
multirom-20150813-v31x-UNOFFICIAL-nicki.zip(To be flashed in recovery)
Use sdcard class 10 to boot cm11, run very smoothly
Great work, thang's ..
Sent from my waifu
Superb job @aweosomeabhijeet
And u can even add XMD in thread title bcoz it even works on it.. I am XMD user.. It's working well
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
SUCCESS
so today i successfully flashed 3 roms on in XMD which run smoothly..the only problem i faced is patience when flashed through recovery i in usbdisk (which is obvious)..so now i dont need to wipe or format my primary rom in oder to test other builds..fabulous job @aweosomeabhijeet
Now mutlirom thread is active almost after one and half year for our xperia m...
All credits to u...
[deleted]
cucumber09 said:
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
Click to expand...
Click to collapse
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
aweosomeabhijeet said:
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
Click to expand...
Click to collapse
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
cucumber09 said:
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
Click to expand...
Click to collapse
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
aweosomeabhijeet said:
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
Click to expand...
Click to collapse
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
cucumber09 said:
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
Click to expand...
Click to collapse
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
aweosomeabhijeet said:
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
Click to expand...
Click to collapse
Okay, that's nice. Sorry if I was too annoying.
Nice dev discussions
Sent from my waifu
itsnie said:
Nice dev discussions
Sent from my waifu
Click to expand...
Click to collapse
Dev and just-advanced-user discussion as I am not a developer. Just enthusiastic and sometimes full of curiosity user, nothing more. (BTW, we should stop OT not to make a mess in the thread)
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
kjinx01 said:
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
Click to expand...
Click to collapse
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Hey bro why does it take so long time to flash in recovery.. Any rom on sdcard takes abt 10 min to get flashed..??
aweosomeabhijeet said:
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Click to expand...
Click to collapse
here u go for it..i uploaded kernel.sin from 15.5.A.1.5 of XMD ftf stock rom
https://www.mediafire.com/?9dobzi8nu2tqzjy
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"
}
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?
August 22: Rom Updated to Beta 0.6 (LP 5.1.1 r13). Latest sources.
TWRP 2.8.7 in boot: Manual brightness is fixed by changing horrendously high back light value (18x Sony's high limit) mistakenly put in by Slim team resulting in no manual brightness and overheating. This is fixed now.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=14141
Dirty flashing is fine if you are on my previous build.
______________________________________________________________________________________________________________
August 10: Rom Updated. This is Beta 0.4 (LP 5.1.1 r9). Latest Slim changes. Updated M5 kernel with CPU and GPU overclock. Kernel size reduced by 2 mb. Also incorporated latest CM commits into device tree to address some screen flickering. http://review.cyanogenmod.org/#/c/105489/
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13920
You can flash dirty if upgrading from the previous build, just keep in mind that if you use Xposed, you must flash it before reboot. This also applies to Supersu. Otherwise, fresh install.
___________________________________________________________________________________________________________
August 6. This is LP 5.1.1 release 9. No heat issues. Also includes M5 hardened kernel with overclocked CPU to 2457 and GPU to 600.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13858
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
___________________________________________________________________________________________________________
August 3: Guys. Stay away from July 25 build. It does cause overheating. I had an episode where my phone shut down and refused to boot for an hour. I guess Slimroms still have problems. Pitty. I have removed the download link...
July 29: Update addressing wifi disconnect after 15 min of sleep and excessive battery drain caused by arp packets related wakelocks
Download and description: http://forum.xda-developers.com/showpost.php?p=62102698&postcount=15
No need to wipe anything if you were on my previous build.
_____________________________________________________________________________________________________________
July 25: Rom updated to LP 5.1.1 r8. This is my change, since Slimrom team still uses earlier releases. They have substantially improved the rom sources, so, whatever I said about them in the past no longer applies.
1. Latest Google AOSP changes
2. Latest Slim changes
3. All my regular hardened features including hardened kernel, removed nefarious IPs, full network selection in Network, disabled wifi background scanning are in
4. Modified M5 kernel
5. Twrp 2.8.7 as a Fota image. The reason I put 2.8.7 in fota is that Slimteam still uses version 2.8.6, which has major bugs. In 2.8.7 most were fixed.
Instructions: Note that the boot.img does not include any recovery to prevent a collision with fota recovery
1. In TWRP format Data, then format System/Data/Cache
2. Flash the rom (don't reboot in system unless you already have recovery in fota)
3. Reboot in Bootloader
4. Flash TWRP.img like this: fastboot flash recovery twrp.img
5. Reboot
Download links: Removed
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
Credit: AOSP, Slimroms, Myself5
__________________________________________________________________________________________________
Rom updated to 5.1 version alpha. All hardened/security features are in. TWRP 2.8.6 is integrated into kernel.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12197
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Here is the latest Slimrom Lollipop built on February 18.
Main changes:
Disabled creepy Selinux and activated Tomoyo as main security provider
Enabled all ciphers, as opposed 2 or 3 in standard releases
Enabled all hashes, digests and compression modes
Enabled all hashes for random number generation to result in a speedier device
Enabled 256 (as opposed to 128) bit encryption for device encryption
Increased weak 2048 RCA key length to 4096
Changes are implemented on kernel level and in /system/core/vold. As a result, you have a more secure and faster device with real protection for you; whereas Selinux, in my view, apart from being developed by an entity known for spying on people on mass scale, "secures" the device from you - meaning you are prevented from interfering with the constant flow of data from your device to their servers ...
Bugs: up-to-date Slimrom bugs
Credit: Slimroms
Modified Sources:
https://github.com/optimumpr/kernel_sony_msm8974
https://github.com/optimumpr/android_system_vold-1
Install Instructions:
1. Be on Kitkat, have root and recovery
2. Enter recovery, wipe Data/Cache/System
3. Flash the rom
4. Don't reboot yet: for some reason Documents.app does not appear anywhere and there is no file manager to handle app install; therefore
5. Flash Slim file manager from kitkat (see Download links at the bottom of this post), which works on lollipop.
6. Now, reboot and enjoy
Download links for Main rom and Slimfilemanager are at the bottom of this post.
Read about getting recovery on honami here: http://forum.xda-developers.com/xperia-z1/general/recovery-solution-lollypop-roms-t3000822/post58127334#post58127334
TWRP is now integrated, see post #5 for download.
Warning: I am not responsible for the destruction of your device and damage to surrounding areas. You are at your own peril. Also, if you don't care about security, stay away from this thread and get the regular version of this rom, which is available in Original Development or on Slimroms website. Comments or discussion about necessity for security, especially by those who have no idea what they are talking about, won't be tolerated. You have been warned.
DOWNLOAD LINKS:
Rom http://d-h.st/dfo
Slim File Manager http://d-h.st/Aqu0 flash it right after the rom before rebooting
XDA:DevDB Information
Slim Lollipop Hardened Secure, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Based On: Slimroms
Version Information
Status: Alpha
Created 2015-02-19
Last Updated 2015-08-22
Reserved
screenshoots?? http://cdn3.xda-developers.com/images/smilies/smile.gif
kriswal123 said:
screenshoots?? http://cdn3.xda-developers.com/images/smilies/smile.gif
Click to expand...
Click to collapse
Sorry, I played with the rom for a day and went back to kitkat.
The looks are the same as in the latest Slimrom LP, which is posted on Slimrom website, as well as in the original Android Development thread...
Kernel with integrated TWRP
Here is SlimLP kernel with integrated TWRP recovery. From now and on, you don't need to reflash your device when changing roms, especially from Lillipop to kitkat or deal with the FOTA partition.
Just unzip the attached file and flash it in Fastboot:
fastboot flash boot boot.img
fastboot reboot
For those of you who already have TWRP in FOTA partition, as you know, this recovery collides with the integrated recovery. So, if you have TWRP in FOTA, do this after installing my kernel:
fastboot erase recovery
fastboot reboot
This will get rid of TWRP in FOTA
Do you plan to update this ? (I am sorry I have posted in almost all your threads but all lollipop rom (Except CM12) keeps on freezing for me
and I want to use a rom with selinux disabled (so that i can use xprivacy)
I tried RR hardened and validus. Both freeze...
never saw any freeze in 4.4.4
ggs2 said:
Do you plan to update this ? (I am sorry I have posted in almost all your threads but all lollipop rom (Except CM12) keeps on freezing for me
and I want to use a rom with selinux disabled (so that i can use xprivacy)
I tried RR hardened and validus. Both freeze...
never saw any freeze in 4.4.4
Click to expand...
Click to collapse
I think Slimrom team is no longer updating lollipop 5.0. They are working on 5.1. Nor are they updating kitkat. But you can use any kernel from my lollipop roms, as selinux is disabled there. You can also use my kernel with cm12, although, I am not sure CM12 would work with xprivacy. Out of all lollipops, only SlimLP and RR5.0 work with Xprivacy. RR works straight. Validus works for me with data partition restored from RR5.0. What I did was to first install RR5.0+Xposed+Xprivacy (confirmed it worked), then backed up data, then full wipe, installed Validus , then without reboot xposed, then without reboot restored data from RR5.0 and it works...
optimumpro said:
I think Slimrom team is no longer updating lollipop 5.0. They are working on 5.1. Nor are they updating kitkat. But you can use any kernel from my lollipop roms, as selinux is disabled there. You can also use my kernel with cm12, although, I am not sure CM12 would work with xprivacy. Out of all lollipops, only SlimLP and RR5.0 work with Xprivacy. RR works straight. Validus works for me with data partition restored from RR5.0. What I did was to first install RR5.0+Xposed+Xprivacy (confirmed it worked), then backed up data, then full wipe, installed Validus , then without reboot xposed, then without reboot restored data from RR5.0 and it works...
Click to expand...
Click to collapse
I tried all of your roms.. Xprivacy worked in all of them but i have this screen freeze issue which makes my phone particularly unusable.
I think i would revert to kitkat for now. That was smooth and solid... Thanks....
Rom Updated to 5.1
See OP for SlimLP 5.1.
{
"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"
}
my wifi kept dropping out and i cannot turn it on except rebooting, is this a known problem ?
New build is up
Rom updated. See OP for download and description.
@Diewi
I thought we could move our discussion on wifi to this thread. Here is a little dirty secret: that qcom binary file is found in kernel too. So, if you change it in /etc/firmware/, you also have to copy the changed file to your kernel's /drivers/staging/prima/firmware_bin/ directory and then recompile the kernel. As usual, the entries there will go to kernel wifi module, which is actually not a module anymore, but a built-in in kernel. Otherwise, the changes won't work. Hence, there goes your android framework messing up things...
I have done it and am back to Kitkat level of battery drain with no disconnect. Here is my file: I did return to gEnableSuspend = 3 and made some more changes.
optimumpro said:
I thought we could move our discussion on wifi to this thread.
Click to expand...
Click to collapse
Fine with that.
optimumpro said:
Here is a little dirty secret: that qcom binary file is found in kernel too. So, if you change it in /etc/firmware/, you also have to copy the changed file to your kernel's /drivers/staging/prima/firmware_bin/ directory and then recompile the kernel. As usual, the entries there will go to kernel wifi module, which is actually not a module anymore, but a built-in in kernel. Otherwise, the changes won't work. Hence, there goes your android framework messing up things...
I have done it and am back to Kitkat level of battery drain with no disconnect. Here is my file: I did return to gEnableSuspend = 3 and made some more changes.
Click to expand...
Click to collapse
Sorry, I have to disagree. Here, things are a bit different from the android framework. Please have a look at the file "CORE/HDD/src/wlan_hdd_cfg.c" of the prima driver, especially the method "hdd_parse_config_ini". The comment clearly states that the ini-file is parsed:
/*
* This function reads the qcom_cfg.ini file and
* parses each 'Name=Value' pair in the ini file
*/
This also matches my experience that modifying the cfg.ini on the device does indeed have an effect.
Just one more note: By the concept accessing external files), it should not make any difference on reading external file if you compile modules inside the kernel or as "seperate" modules. However, there exist quite a lot device drivers out there which require to be build as modules to load their firmware (due to being depend upon some "external" firmware loader etc.). The prima driver obviously does not belong to these kind drivers.
Nevertheless, those changes should be pushed upstream (cm), then they would reside in the driver directory of the kernel anyways
Regards,
Diewi
Diewi said:
Fine with that.
Sorry, I have to disagree. Here, things are a bit different from the android framework. Please have a look at the file "CORE/HDD/src/wlan_hdd_cfg.c" of the prima driver, especially the method "hdd_parse_config_ini". The comment clearly states that the ini-file is parsed:
/*
* This function reads the qcom_cfg.ini file and
* parses each 'Name=Value' pair in the ini file
*/
This also matches my experience that modifying the cfg.ini on the device does indeed have an effect.
Just one more note: By the concept accessing external files), it should not make any difference on reading external file if you compile modules inside the kernel or as "seperate" modules. However, there exist quite a lot device drivers out there which require to be build as modules to load their firmware (due to being depend upon some "external" firmware loader etc.). The prima driver obviously does not belong to these kind drivers.
Nevertheless, those changes should be pushed upstream (cm), then they would reside in the driver directory of the kernel anyways
Regards,
Diewi
Click to expand...
Click to collapse
I don't dispute that the file is being parsed, my point is that because the same file with different entries is in kernel, we really don't know how they would interact.
Update to fix wifi disconnect and battery drain
Here is a recompiled kernel as well as a separate file to flash. This takes care of wifi disconnect after 15 minutes of sleep as well as excessive battery drain caused by a barrage of arp packets that create wakelocks.
Instructions:
1. Flash WIFI_DRAIN_FIX in Recovery
2. After that reboot in Bootloader and flash kernel (unzip boot.img): fastboot flash boot boot.img
3. If you have fota recovery, don't reboot and erase fota recovery, because this boot.img has twrp: fastboot erase recovery.
TWRP 2.8.7 has a bug preventing backing up roms. So, it is no good, unfortunately. I have returned to an earlier build.
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
Warning: Don't use this for any other rom, because this kernel is specific to SLimrom.
optimumpro said:
I don't dispute that the file is being parsed, my point is that because the same file with different entries is in kernel, we really don't know how they would interact.
Click to expand...
Click to collapse
I get your point, but please have a look at the Android.mk file in the directory of the prima driver. There it is clearly stated that the files in the firmware_bin sub directory are just copied to the dir "${OUT}/system/etc/firmware/wlan/prima/". Hence, the "same" file does not exist in the kernel. BTW, beware, if you modify the file directly in your kernel folder as it will not be copied to the ${OUT} directory if the file exists there already. This is a serious weakness of the android build system IMHO.
The cfg-file will be parsed when the driver loads.
Sorry, for being that insistent
Diewi said:
I get your point, but please have a look at the Android.mk file in the directory of the prima driver. There it is clearly stated that the files in the firmware_bin sub directory are just copied to the dir "${OUT}/system/etc/firmware/wlan/prima/". Hence, the "same" file does not exist in the kernel. BTW, beware, if you modify the file directly in your kernel folder as it will not be copied to the ${OUT} directory if the file exists there already. This is a serious weakness of the android build system IMHO.
The cfg-file will be parsed when the driver loads.
Sorry, for being that insistent
Click to expand...
Click to collapse
Well. This same file resides in sony_rhine_common overlay. So, what I do is put the changed file in both directories. Anyway, this is the first time on lollipop that I have absolutely no wifi disconnection. And wifi range has increased too (I increased the tx cap to 80).
I have very very strange issue (only on this slim rom)!
My charging sometime stops, and i have to reboot phone to get it back to charging. anyone has same issue?
ggs2 said:
I have very very strange issue (only on this slim rom)!
My charging sometime stops, and i have to reboot phone to get it back to charging. anyone has same issue?
Click to expand...
Click to collapse
I don't think anyone else has it. In case you are talking about charging through usb: some linux distros drop usb connections during sleep and then have trouble reconnecting, because the phone is sleeping. You may have a similar behavior in Windows...
Just a remark, It seems that the file ending is a bit messed up. Or rather missing.
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 5. 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.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-armani.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_armani_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
Currently dual booting MIUI isn't working! So DO NOT try to dual boot MIUI with LP/KK ROMs.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 676mb of space.
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.
Source code
MultiROM - https://github.com/multirom-armani/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/multirom-armani/android_kernel_xiaomi_armani/tree/multirom(branch multirom)
MultiROM device tree - https://github.com/multirom-armani/android_device_xiaomi_armani/tree/multirom (branch multirom)
Credits
@Tasssadar (for making this awesome utility!)
@KINGbabasula (armani's multirom is possible cz of him!)
@akhilnarang (He's the person who's always present to help! Cheers!)
@vasishath (For pointing out the fix for white glitch)
All my dear testers! Thanks for testing!
XDA:DevDB Information
MultiROM for Xiaomi Redmi 1S, Tool/Utility for the Xiaomi Redmi 1S
Contributors
TheStrix
Source Code: https://github.com/multirom-armani/
Version Information
Status: Stable
Current Stable Version: 32a
Created 2015-09-05
Last Updated 2015-09-25
Downloads
1. Main downloads
MultiROM: multirom-20150925-v32a-armani.zip
Modified recovery (based on TWRP): TWRP_multirom-armani_20150925.img
MultiROM Manager Android app: Google Play or link to APK (NEW!)
Kernel w/ kexec-hardboot patch (LP ROMs): LP_kexec_20150925.zip
Kernel w/ kexec-hardboot patch (KK ROMs): KK_kexec_20150925.zip
You need to have kernel with kexec-hardboot patch only in your primary ROM!
2. third-party kernels with kexec-hardboot patch
Yet to come!
Nicely ask your kernel developer to merge kexec-hardboot patch.
3. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Changelog
Code:
04/09/2015-MultiROM v32
==========
* Initial stable release for armani
25/09/2015-MultiROM v32a
==========
* Fix white noise while booting secondary ROMs
* Added new updated KK and LP kexec patched kernels
Recoveries:
Code:
04/09/2015
==========
* Initial stable release for armani
* MultiROM TWRP 2.8.7
25/09/2015
==========
* Upstream changes
FAQ and other notes
Device encryption
Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.
I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Installation Video
Thanks to YouTuber Dhananjay Bhosale (@TheDj408) for making this awesome installation video!
Awesome Work Buddy
This is a outstanding work buddy
Keep it UP
Thanks for MultiROM
Great work @TheStrix
Sent from my A0001 using Tapatalk
GREAT WORK , THANKS BUDDY !!
Can you upload some Screenshots/Images/Video for better understanding
Something new for our device after a long time.
Awesome work @TheStrix ! Guys Smash that Thanks button
Nice work mate @TheStrix now armani users can enjoy two roms
Sent From My Yuphoria Using Tapatalk
Gunikmaliwal said:
GREAT WORK , THANKS BUDDY !!
Can you upload some Screenshots/Images/Video for better understanding
Click to expand...
Click to collapse
Screenshots added in "Screenshots" tab
And for installation video, I'll wait for some great YouTuber's to make one. Till that you can see multirom installation video for other devices which are using manual method and not Multirom app method to install multirom.
Wow ... Awesome dude
Wow more boot option ... Lets break this phones guys !!!! You god dang flasholic !!!!
The only mod which was missing from redmi
Thanks a lot
Awesomeeeeeeeeeeeeeeeeeeeeeeee.
Thank you @TheStrix . Awesome work and something this device needs with tons of ROMs. Waiting for MIUI + CM dual boot . Would love to see that . And with the upcoming of sailfish OS redmi is gonna rock .
Awesome work @TheStrix! This is gonna rock!
Dude sweet u managed to port it to our device. Was enjoying it on my hammerhead.
Sent from my HM 1S using Tapatalk
I've contacted Dhananjay Bhosale ( https://www.youtube.com/user/dhananjaybhosale1 ) for Video on Installation !
Its working flawless...waiting for devs to include hardboot patch in beast and xecelerate kernel
Sent from my HM 1S using Tapatalk
Great work ... Will this support r the same with the other project like EFIDroid? Its like having native grub loader into the phone
Sent from somewhere on earth
elmumtaz said:
Great work ... Will this support r the same with the other project like EFIDroid? Its like having native grub loader into the phone
Sent from somewhere on earth
Click to expand...
Click to collapse
Yes, functions same as Grub/EFIDroid
You'll see multirom menu to choose the system you want to boot into.
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xperia Z1. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.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, daily prebuilt image files to install Ubuntu Touch 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
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* 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 messing with boot sector and data partition. 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.
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_n7-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_n7_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
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.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code
MultiROM - https://github.com/XperiaMultiROM/multirom (branch master)
Omni TWRP - https://github.com/lj50036/platform_manifest_twrp_omni (branch twrp-6.0)
Donations
[MENTION=3418703"Tasssadar[/MENTION] would be glad if you could spare a few bucks. You can use either paypal or Bitcoins, his address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris. And if you want to donate me for porting the updated version of MultiROM, PM me .
Thanks to all donors, it is much appreciated
XDA:DevDB Information
MultiROM Xperia Z1, Tool/Utility for the Sony Xperia Z1
Contributors
aquaboy11
Version Information
Status: Testing
Created 2016-04-11
Last Updated 2016-04-12
Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk
drakonizer said:
Have you managed to get it to work? I've tried to port it myself, and got the recovery to work, but it always fails to boot any secondary ROM for me. Did you use the XperiaMultiRom sources?
Sent from my MI PAD using Tapatalk
Click to expand...
Click to collapse
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.
aquaboy11 said:
Yes I did. Multirom works, but as soon as I select a second ROMit tells me the kernel doesn't have a kexec patch. I am trying to build it with the android 5.1 sources this time (used 6.0 for this build).
Edit: Same result with the 5.1 sources. I've provided the multirom.log in the main post. Maybe someone with more experience could take a look at it.
Click to expand...
Click to collapse
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?
drakonizer said:
Are you using a 5.1 ROM with kexec as your primary ROM (I assume you already are)? I had similar issues with booting secondary ROMs, http://pastebin.com/mkYhMrBJ is my log. What value of kexec_mem_min are you using? Also, if you can't boot into a secondary ROM, what part of multirom is actually working for you?
Click to expand...
Click to collapse
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.
aquaboy11 said:
Yes, a 5.1 stock ROM with kexec as my primary ROM. The value I am using for kexec_mem_min is 0x25000000. The part of multirom that works is the part that allows me to change settings and install/manage ROM's.
Click to expand...
Click to collapse
So you mean the recovery? I've got that working too, seems like we're both stuck at the same point...unfortunately we don't have the sources of the old multirom v30x.
Is it only me? I cannot find download links for your version
Hitman73 said:
Is it only me? I cannot find download links for your version
Click to expand...
Click to collapse
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs
drakonizer said:
Its not even working yet. This is more of a placeholder thread (which technically isn't allowed by XDA rules), but it also can be considered a development thread. I suggest OP add dev to the title.
Sent from my Xperia Z1 (AOSP) using XDA Labs
Click to expand...
Click to collapse
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.
aquaboy11 said:
As soon as I saw the MultiROM selection screen I posted it. But that might have been a bit too quick as I did not try loading a secondary rom yet . I have added [DEV] to the title.
Click to expand...
Click to collapse
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.
drakonizer said:
That was a little premature.
Can you share your device tree? I would like to take a look. Also, did you try using the new Multirom recovery to flash the old v30 and see if it boots? In that case, we only need to port kexec to MM to have dual boot. (not an easy task either).
I've also contacted Tasssadar for info on what the logs (mine at least) mean, but he hasn't responded.
Click to expand...
Click to collapse
MultiROM v30 boots fine.
I used Sony's device tree
mr_init_devices.c
Everything from BoardConfig.mk after line 41.
I could give porting kexec to MM a shot when I have some spare time.
Hi. I experienced a problem entering the recovery. My device stuck at the Sony symbol displayed an the orange LED when I try to enter. Before I updated my recovery I used the one from v30 thread without any problems. Any idea where the problem is?
Thanks in advance!
LB multirom
Hello, I have a small question ...
If I install MultiROM v33 on my Xperia Z (LB) "locked bootloader",
can i install secondary ROMs for unlocked bootloader ???
thank you
Is this still being worked on?