• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[MOD][Z2] MultiROM v33d

Search This thread

Diewi

Senior Member
Jul 7, 2008
378
243
Here we go again :(

I'am on latest MM by Sony (.291) with fresh MR V33c, but now with N as secondary I cant run stock because it show me failed to mount /appslog

Other things working for me very good, but thats freak something broke after few days @Diewi

Any idea?

Hmm, this is strange.

Could you upload the content of the fstab.* file (* = shinano or sirius) after booting the N rom somewhere, e.g. pastebin? The fix for the appslog problem is that the fstab is modified when booting the N rom such that it is not mounted in the "/misc" folder. If the fix fails then there would be an entry in the fstab.
 
Hmm, this is strange.

Could you upload the content of the fstab.* file (* = shinano or sirius) after booting the N rom somewhere, e.g. pastebin? The fix for the appslog problem is that the fstab is modified when booting the N rom such that it is not mounted in the "/misc" folder. If the fix fails then there would be an entry in the fstab.

Sure, i can upload it. Just tell me where it is? And is it possible to fix my stock rom? I have very important files there:rolleyes:
 
It's in the root directory, i.e. "/fstab.shinano". If the problem is caused by the "appslog partition problem", you can wipe it using flashtool: it has a switch for that, but please ensure that everything else is unticked :D

Ok, wiped and flashed appslog.sin and rom boot correctly now - huge thanks mr.

Now i'am going to send you that file, wait a moment... :silly:

EDIT: Here is my Fstab.shinano, maybe it helps you @Diewi

http://pastebin.com/z2ggVmhg
 
Last edited:

Diewi

Senior Member
Jul 7, 2008
378
243
Ok, wiped and flashed appslog.sin and rom boot correctly now - huge thanks mr.

Now i'am going to send you that file, wait a moment... :silly:

EDIT: Here is my Fstab.shinano, maybe it helps you @Diewi

http://pastebin.com/z2ggVmhg

Many thanks, it's like I thought. Line 5 should not be there. I am a bit surprised that it is still exists, since I actually made a fix for that which also removed this line when I tested it... :confused: Anyways, I will test this next week again and fix it ASAP. Thanks for reporting.
 
  • Like
Reactions: itsnie
Many thanks, it's like I thought. Line 5 should not be there. I am a bit surprised that it is still exists, since I actually made a fix for that which also removed this line when I tested it... :confused: Anyways, I will test this next week again and fix it ASAP. Thanks for reporting.

No problem, its nice to help you dev. Thanks for your hardwork!!! :highfive:

And little offtop from me: is there any other way to boot stock without wiping /appslog partition in flashtool? Idk maybe if i cut this file named apps_log from dev/block/bootdevice/by_name/ it will boot succesfully...? How you think @Diewi?
 

Diewi

Senior Member
Jul 7, 2008
378
243
No problem, its nice to help you dev. Thanks for your hardwork!!! :highfive:

And little offtop from me: is there any other way to boot stock without wiping /appslog partition in flashtool? Idk maybe if i cut this file named apps_log from dev/block/bootdevice/by_name/ it will boot succesfully...? How you think @Diewi?

If you have this problem, unfrotunately not. The fstab file is contained in the boot image and is extracted to the Ram during boot, so I need to patch it on the fly with multirom.
Of course, you could still extract the boot image modify the fstab and repack it. But that's not what I expect from Multirom in terms of usability :D
 
  • Like
Reactions: EugenStanis

akshay2shah

Senior Member
Mar 10, 2016
733
855
Pune
@Diewi - same problem here..
Using
1. Primary stock
2. Nougat

Need to wipe apps_log via flashtool everytime when i boot back to stock.

I had reported this problem to @Myself5 & @rcstar6696 earlier.
Myself5 told that it should br fixed from multirom side.

I didn't know you are the offcial maintainer now or else i would have reported u earlier.

Anyways read all comments above. Happy to know u gonna fix it.

PS: @rcstar6696 made some changes to Pure nexus so it works fine.

If u wanna reproduce issue u can install Carbon rom as secondary N.

Thanks !
Regards.
 
Last edited:
@Diewi - same problem here..
Using
1. Primary stock
2. Nougat

Need to wipe apps_log via flashtool everytime when i boot back to stock.

I had reported this problem to @Myself5 & @rcstar6696 earlier.
Myself5 told that it should br fixed from multirom side.

I didn't know you are the offcial maintainer now or else i would have reported u earlier.

Anyways read all comments above. Happy to know u gonna fix it.

PS: @rcstar6696 made some changes to Pure nexus so it works fine.

If u wanna reproduce issue u can install Carbon rom as secondary N.

Thanks !
Regards.

So, maybe its my fault because i have installed LineageOS 14.1 bulid as secondary N rom from "experimental" rcstar mega folder :eek:

And one more question: if i install Carbon or purenexus as secondary i will not have /appslog partition problem?
 

akshay2shah

Senior Member
Mar 10, 2016
733
855
Pune
So, maybe its my fault because i have installed LineageOS 14.1 bulid as secondary N rom from "experimental" rcstar mega folder :eek:

And one more question: if i install Carbon or purenexus as secondary i will not have /appslog partition problem?
1. Its not your fault.
2. @rcstar6696 made some twick in Pure Nexus rom so it works.
3. LineageOS, Carbon Rom dont have twick rcstar6696 made.
4. More technically Apps_logs issue should be fixed in multirom as @Diewi said.
5. All N rom will support multirom once deiwi fix it.
 
  • Like
Reactions: EugenStanis

rcstar6696

Senior Member
Dec 21, 2013
2,468
8,475
Kassel (Hessen)
1. Its not your fault.
2. @rcstar6696 made some twick in Pure Nexus rom so it works.
3. LineageOS, Carbon Rom dont have twick rcstar6696 made.
4. More technically Apps_logs issue should be fixed in multirom as @Diewi said.
5. All N rom will support multirom once deiwi fix it.

my builds all have the tweak for apps log partition only official carbon not
 
my builds all have the tweak for apps log partition only official carbon not

LineageOS too? :p
I installed LineageOS (your bulid) as secondary N (primary is stock marshmallow. 291 with elite kernel v3) and i cant boot my internal (stock) rom. Trying to boot stock result in never ending bootloop. In T.W.R.P it show me "error cant mount /appslog partition"

:mad:
 

namefaisal

Member
Dec 7, 2015
31
18
Help me with the MultiRom installation plz.
1. Mention a specific rom that will support Multirom(what u, my kind helper is using).
2. Mention a kernel name that will work with that rom.
3. Now, how to install MultiRom.img(not through the app plz). Fastboot method or similar wanted.

Now I should have working MultiRom working.

4.I want LineAge OS as the second Rom. Tell me the flashing instruction(I used Multirom on nexus7 so i know the procedure but here on our z2 here seems to be a new step like flashing kernel with each rom). Just tell me the steps of flashing the LineAgeOS.

Many Many thanks, whoever helps.
 
Help me with the MultiRom installation plz.
1. Mention a specific rom that will support Multirom(what u, my kind helper is using).
2. Mention a kernel name that will work with that rom.
3. Now, how to install MultiRom.img(not through the app plz). Fastboot method or similar wanted.

Now I should have working MultiRom working.

4.I want LineAge OS as the second Rom. Tell me the flashing instruction(I used Multirom on nexus7 so i know the procedure but here on our z2 here seems to be a new step like flashing kernel with each rom). Just tell me the steps of flashing the LineAgeOS.

Many Many thanks, whoever helps.

1. LineageOS by rcstar or any stock of your choice (personally i recommend latest avaiable Sony Marshmallow 6.0.1 bulid 291 CE1
2. You dont need custom kernel now, because multirom does not need hardboot kexec patched kernel (but if you still want custom boot elitekernel v3 is best imho)
3. Flash multirom recovery with official twrp app/multirom app or using fastboot "fastboot flash recovery recovery.img
4. Flash stock Marshmallow by Sony, then Kernel and reboot to fastboot to flash recovery
 
  • Like
Reactions: AK2H

darknessmc

Senior Member
Jul 30, 2013
691
132
Redmi Note 9 Pro
1. LineageOS by rcstar or any stock of your choice (personally i recommend latest avaiable Sony Marshmallow 6.0.1 bulid 291 CE1
2. You dont need custom kernel now, because multirom does not need hardboot kexec patched kernel (but if you still want custom boot elitekernel v3 is best imho)
3. Flash multirom recovery with official twrp app/multirom app or using fastboot "fastboot flash recovery recovery.img
4. Flash stock Marshmallow by Sony, then Kernel and reboot to fastboot to flash recovery
But it's need unlocked bootloader if I need stock as primary? right?

Sent from my D6503 using XDA-Developers Legacy app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 60
    nPOXmb5.png

    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.
    3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
    4. Your device must not be encrypted.
    5. To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
    6. 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. Install the MultiRom Manager app from the store and install the recovery and multirom.
    2. Reboot into MultiROM TWRP and flash the MultiROM installer --> Sould be done automatically.
    3. Make sure you are on a Rom compatible with one of these kernels and flash it
    4. In order to boot a secondary rom you MUST enable the "kexec workaround" option in the MultiRom settings found in the recovery.
    5. That's it. You can now go to "MultiROM menu" (Top right corner in the recovery) to start flashing other ROMs.

    Alternative installation method (if installation via the above method fails)
    1. Download the files named multirom-<date>.zip and recovery-<date>.img from here.
    2. You should use md5sum to validate the downloaded files using the provided xyz.md5 files in the same download location.
    3. Copy the files to the sdcard of your device.
    4. Use "adb shell" to open a shell on the device and use "su" to obtain root rights (adb must be set up on your computer, instructions are found on xda).
    5. Adjust the following command and enter it in the shell: "dd if=/sdcard/recovery-<date>.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
    6. Reboot into recovery (shutdown, then VolDown + Power).
    7. Flash the multirom zip from the sdcard.
    8. Enjoy.



    Adding ROMs
    Go to recovery, select "MultiROM menu" (Top right corner in the recovery) -> 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 "MultiROM menu" (Top right corner in the recovery) in recovery and do Inject curr. boot sector. if it is not done directly during installation of the Rom.
    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 "MultiROM menu" (Top right corner in the recovery) -> List ROMs and select the ROM you want to update.
    • Select "Flash ZIP" and flash ROM's ZIP file.

    Install a stock rom as secondary

    This only works if you are using MultiRom version 33c or larger (excluding 33x-z).

    1. Existing primary stock rom
    Use these instructions if you plan to move an existing stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
    • Shutdown the device.
    • Start the device into multirom recovery (VolDown + Power).
    • MAKE A BACKUP!
    • Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
    • Select the option "Copy primary rom to secondary/internal" and start the operation.
    • Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
    • Reboot.

    2. Fresh stock installation
    Use these instructions if you do not have a stock rom installed as primary. This guide assumes that multirom recovery is properly installed.
    • Shutdown the device.
    • Start the device into multirom recovery (VolDown + Power).
    • MAKE A BACKUP!
    • Install the stock rom via an install zip of via an FTF. NOTE: For the FTF method you need to shutdown the device and boot into download mode (VolDown pressed while connecting the USB cable; cable connected to the PC). Use for instance flashtool to flash ONLY the kernel, system, and cache image. In addition, you MUST select "Wipe apps_log"!
    • When the device reboots, let it boot up and finish the first time setup procedure.
    • Shutdown the device.
    • Start the device into multirom recovery (VolDown + Power).
    • Go to "MultiROM menu" (Top right corner in the recovery) in recovery and tap "Swap roms".
    • Select the option "Copy primary rom to secondary/internal" and start the operation.
    • Wait until the operation finishes and flash your desired rom. (Alternatively you can also use any secondary rom to be the primary rom using the "Swap option" mentioned above.
    • Reboot.

    CHANGELOG
    Code:
    === Version 33d (Bugfix release) ===
    - Fix the apps_log issue for good (FINALLY).
    - Support for LOS in combination with stock.
    
    === Version 33c ===
    - Sync with XperiaMultiRom repository: cleaner implementation of some patches & extends the rom support w.r.t. old builds.
    - Improved compatibility of custom N roms (AOSP init system) with stock roms: Allows to use stock roms as secondary rom.
    - Bug fix: Set the version number in the Mrom binaries (for automatic updates).
    
    === Version 33b ===
    - Small maintenance update to support "embedded/combined ramdisks" of secondary roms.
    
    === Version 33a ===
    - Fixed booting Stock after starting secondary N rom.
    
    === Version 33z ===
    - Fixed boot image injection of stock roms.
    
    === Version 33y ===
    - New nokexec version 4 (previous: version 2).
    - Support for AOSP 1.3.3 kernels (1.2.2 based kernels are also supported).
    - Support for Android N (>= 7.0).
    - Support for Sony Z2 stock roms as primary rom (I am investigating the installation as a secondary rom: it's installing, but not yet booting).
    
    === Version 33x ===
    - Update Multirom from version 32 to 33.
    - Update Multirom TWRP from version 2.8.7.0 to 3.0.2.

    Detailed Xperia-Multirom Changelog
    MultiRom
    MultiRom Recovery

    General Multirom Changelog
    To be found here.


    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
    • Myself5
    • AdrainDC
    • Olivier
    • Garcia98
    • Thunder07
    • skin1980
    • Envious_Data
    • [NUT]
    • AndroPlus
    • Panic Brothers

    I do not accept donations. But you may consider donation to Myself5 who did the original port, or to Tassadar who envisioned Multirom and did most of the implementation. We just jumped on the rolling train ;)

    Myself5:



    Tassadar:



    Thanks a lot to those who have donated!


    XDA:DevDB Information
    MultiROM for Sony Xperia Z2, Tool/Utility for the Sony Xperia Z2

    Contributors
    Myself5, Diewi
    Source Code: https://github.com/XperiaMultiROM/multirom/tree/master


    Version Information
    Status: Testing

    Created 2015-01-13
    Last Updated 2018-01-23
    23
    DOWNLOAD

    I still need to fix touch inside the MultiROM menu, for now you need to use the volume buttons to navigate.
    https://diewald-net.com/files/public/MultiRom/sirius
    The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
    17
    Reserved

    General Informations about Kexec are coming here soon.
    9
    I just started a build on my finally completed jenkins setup. Be prepared for TWRP 2.8.5 and MultiROM v31x. Build should be up in ~15 min, and MultiROMMgr should be updated automatically too.
    Edit: It's up :p

    Regards
    9
    It appears like I fixed MultiROM (at least on the Z3 Compact) yesterday (both, graphics and booting secondary Roms with a different boot.img) . Going to do some more tests with it today and then publish it for Z3C followed by pushing an updated Version for Z2 and Z3. Sorry for letting you guys wait that long.

    Sent from my Xperia Z3 using Tapatalk