yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Original Android Development] Myself5:
Just a quick headsup. MultiROM Manager App just got updated. This means Z3 and Z2 are now supported by the App available in the Play Store.

Updated TWRP version with a fixed device name so CM12 Nightlys install is about to come soon too.

BTW: The newest AndroPlus Kernel should fix the touch in the MultiROM Menu.

Also, there is a small chance that I might get a Z3 soon, I just need to find some way to raise some money for it :/..

Regards
[Xperia Z3 Original Android Development] torjohron:
Great work

Could you please also port this to z3c?
[Xperia Z3 Original Android Development] JamesK852:
Just downloaded the on my Z3 Dual (D6633) and it says "This divice is not officially supported!". Is it because I have a variant of the Z3 or because my local Play Store is slow to update?
[Xperia Z3 Original Android Development] Myself5:
I already have problems with the Z3 support as it is hard to maintain it without actually having the device, I'm not willing to add more pain to these problems at the moment. Let's see when I can fix the Z3, then we can talk about adding a new device to the supported device list.

D6633 should be supported fine, check the Apps Changelog in the App Store and see if it contains the Z2 and Z3 update already.

EDIT: Do you maybe own a D6653? (Just came up with this as a Z2 user flashed the Z3 Rom on his Z2 (yes this works lol), with the codename D6653, which I did not added to the supported devices. (because I just too all the devices which are supported by the CM12 flashable zip).)
[Xperia Z3 Original Android Development] JamesK852:
Just checked its definetly a D6633 and the change log does say Z3's are supported is there any additional info I can give you to help diagnose why this is coming up as unsupported?

About My Device:

I've rooted it using giefroot by zxz0O0 tool after downgrading the firmware and subsequently upgraded the firmware using PRFCreator. Other than that no other changes have been made to the ROM.
[Xperia Z3 Original Android Development] mudnightoil:
Would also be willing to donate for Z3C support.
[Xperia Z3 Original Android Development] Myself5:
Can you send me your build.prop please? You can find it in /system/build.prop ;)

Gimme time :P I'm still working on a z3 version which has z3 instead of leo as it's device name so that the CM12 Nightlys flash fine. Most likely will get a testbuild till the end of the week (not sure if it will work, so be warned). If I managed to get this working I'll try porting it to the Z3C. I'll PM you guys if I need some testers.

EDIT: Can you guys do me a huge favour and test if this build of MultiROM is working for you when installing CM12 Nightlys?

http://testing.myself5.de/z3/MultiROM/

I am not sure if this is working at all, as you know I don't own a Z3 .. Should work tho as I only renamed things in the device tree.

Thanks in advance and Regards
[Xperia Z3 Original Android Development] cajunflavoredbob:
When the test build (multirom-20150212-v31x-UNOFFICIAL-z3.zip) is flashed in the new recovery (TWRP_multirom_20150212-00.img), recovery immediately crashes and reloads. The older version 30 zip (multirom-20150121-v30x-UNOFFICIAL-leo.zip) flashes perfectly fine. Due to the crash and reload, it is not possible to capture the recovery logs.
[Xperia Z3 Original Android Development] Myself5:
so when you install the older Multirom zip, does flashing the CM Nightlys work ? I'll try figuring out why flashing the newest zip fails.
[Xperia Z3 Original Android Development] panzerscope:
I just tried flashing the new version and upon doing so it seems to immediately reboot the recovery as the TWRP logo comes up and im back at the main menu.
[Xperia Z3 Original Android Development] cajunflavoredbob:
I was able to flash the CM12 nightly from 05 Feb 2015 (20150205). I have not been able to successfully flash an update yet. The last few nightlies have had issues with the dialer crashing when receiving a call, so I haven't bothered to try lately.

In any case, I attempted to install all the CM12 nightlies I have again (05-11 Feb 2015) through the multiROM recovery. I was unable to install any of them. They all gave the typical error in the updater-binary. However, somehow, I was able to get CM12 installed with MultiROM on the 5th along with Validus. Validus only does a bootloop, being stuck forever in the boot animation. CM12 20150205 nightly works perfectly fine as my secondary ROM, with the stock *.77 as my main ROM.

I do not know how I was able to install CM12 successfully the first time.
[Xperia Z3 Original Android Development] panzerscope:
Well I just Flashed the most recent CM12 nightly (12/02/15) on my internal storage and so far it seems to have flashed correctly. As such I can only guess that V31 of Multirom did flash, even though it looks like it just reboots recovery when you install it. Installing on External Storage does not work if you set the Data partition to Maximum (9999) and give Cache 1024 as well as system 1024, it states there is not enough space to unpack the image basically, but there is.
[Xperia Z3 Original Android Development] Myself5:
I guess your SDCard is formatted in fat32. Max File size on that File system is 4096MB, therefore you wont be able to set a 9999MB Data partition ;)

As the answers of you guys confused me a bit: Summary of the testbuild: MultiRom 31x does crash recovery (same on sirius BTW), but the updated recovery is actually able to flash CM12 nightlys as secondary Rom? I'll try compiling a build using cm11 as base instead of carbon again then, let's see if this helps.
[Xperia Z3 Original Android Development] panzerscope:
I was fairly sure it was ExFat but perhaps not as I have re-tested and it does work flashing a secondary rom to the external storage so long as you abide the limits of Fat32.

So in summary it would seem the new recovery allows for flashing CM12 on internal and external memory. One thing I did notice is that Multirom when creating folders for the secondary rom still names the Folders as "Multirom Leo" when one would expect Multirom Z3.

Thanks again for your hard work!
[Xperia Z3 Original Android Development] Myself5:
this is because your multirom is still v30x (with the leo name). Seems like 31x fails to flash on leo as also on sirius. I wait for some other XperiaMultiROM devices to confirm (for example Xperia Z by [MENTION=4329876]Olivier[/MENTION])
[Xperia Z3 Original Android Development] cajunflavoredbob:
Sorry for the confusion. I'll try to explain in order.

I first flashed a CM12 nightly on 05 February 2015 using MultiROM v30. I do not know how I was able to do this without an error, but I have not been successful in doing so since then. At the same time, I also tried flashing Validus and Candy ROMs. Candy failed and gave the updater-binary error, while Validus was successful. Validus fails to boot, however, being stuck at the boot animation screen forever.

When you asked for testers of the new version, I flashed the new recovery.img, then attempted to flash the new MultiROM zip. The zip crashes recovery and forces it to reload. I tried this a couple of times just to be certain. Now, something you should be aware of is that I am also unable to open the zips on my computer. They seem to be corrupted. I downloaded them a second time with the same result. Something may have gone wrong with your compiling process.

In any case, I then attempted to flash another CM12 nightly, but it did not work. Even my original CM12 nightly (20150205) does not flash. I don't know how I was able to get around the problem with flashing CM12 zips last week when I did this originally, but it is no longer possible, it would seem.

Hopefully this better explains my previous post.
[Xperia Z3 Original Android Development] Myself5:
Just uploaded a new build to the testing page, installing the 31x zips should be fixed now. If I get good feedback I'll move it to the dl page and update the MultiROM Manager manifest.

P.S. It works fine on Z2.
[Xperia Z3 Original Android Development] dc416:
where do we find the testing page ?
[Xperia Z3 Original Android Development] cajunflavoredbob:
Error with the updater-binary. It doesn't crash recovery anymore, so that's a plus. I'm unable to download the newer recovery from your testing server. All other files download fine. I am, therefore, using the previous testing recovery (TWRP_multirom_20150212-00.img). Recovery log is as follows:

Installing '/sdcard/Download/multirom-20150214-v31x-UNOFFICIAL-z3.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: assert failed: getprop("ro.product.device") == "z3" || getprop("ro.build.product") == "z3"
assert failed: getprop("ro.product.device") == "z3" || getprop("ro.build.product") == "z3"
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/multirom-20150214-v31x-UNOFFICIAL-z3.zip'
Error flashing zip '/sdcard/Download/multirom-20150214-v31x-UNOFFICIAL-z3.zip'
Injecting boot.img with MultiROM...
Extracting boot image...
rm: can't remove '/tmp/boot': No such file or directory
Decompressing ramdisk...
Ramdisk uses GZIP compression
27317 blocks
7583 blocks
strings: standard output: Broken pipe
strings: standard output: Broken pipe
No need to inject bootimg, it has the newest trampoline (v14)
Updating partition details...
I:Data backup size is 1302MB, free: 5161MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done

So the error tells me that it is looking for the device name in the build prop, but if you're using a stock ROM as your main ROM, then this will have the device model name (D6603). Removing this line from the updater-script or modifying it to the correct model name allows the zip to flash properly. However, the new TWRP does not see any internal storage or installed ROMs. The recovery does not recognize that any OS is installed. However, booting normally is possible, and the installed version of MultiROM on my device is now v31.

I will be flashing back to a working recovery tonight, but if you need help troubleshooting, I'll be around tomorrow. Just @ mention me, and I'll get an e-mail. I'm getting some sleep for now, though.
[Xperia Z3 Original Android Development] Myself5:
[MENTION=2543015]cajunflavoredbob[/MENTION]

I uploaded a new testbuild (same name as before but new stuff), would be cool if you can try it again. TWRP mount points should be fixed, I hope the same about the installer issue.

[MENTION=6072408]dc416[/MENTION]

the testing page is http://testing.myself5.de

EDIT:

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.

Regards
[Xperia Z3 Original Android Development] cajunflavoredbob:
Ok, it does work now, but only when I manually remove or modify the line in the script that tries to getprop. As mentioned before, the stock based ROMs being used as the main ROM have the device model number in the build.prop, so doing a scripted getprop isn't going to work. It's going to fail to flash every single time. My suggestion is to simply remove this getprop line completely. List the devices it works on, and that's that.

Beyond that minor issue, flashing CM nightlies works perfectly fine now. No issues with any of the other CM based ROMs either. Everything flashes normally. The TWRP mount points are normal again as well.

EDIT: Touch works in this version of MultiROM.

EDIT 2: MultiROM Manager found the updated recovery and flashed it with no problem.
[Xperia Z3 Original Android Development] Myself5:
getprop should actually get it's values from the recoverys files, not from the hostrom at all (else it would not work if you formatted system before flashing a zip), so that's why I was hoping it works with the newest build.

glad to hear.

because AndroPlus fixed it in the kernel. Updated the Downloads post just right now.

was not expecting anything else :P
[Xperia Z3 Original Android Development] panzerscope:
Great work but for some reason it will not flash and states there is an Error in the update script, this is from using V31 in the first post.

---------- Post added at 10:18 PM ---------- Previous post was at 10:15 PM ----------

Also trying to download V31 from Multirom Manager fails, but it will download and install latest recovery

---------- Post added at 10:28 PM ---------- Previous post was at 10:18 PM ----------

Ok. So I went back in order to get you a full and accurate error message. Please see below.

E: Error executing updater binary in zip 'Sdcard/Download/Multirom-20150214-v31-unofficial-z3.zip
[Xperia Z3 Original Android Development] cajunflavoredbob:
Edit the updater-script and remove the line at the beginning.

assert(getprop("ro.product.device") == "z3" || getprop("ro.build.product") == "z3");

After you remove this line, repack the zip and flash it normally.
[Xperia Z3 Original Android Development] panzerscope:
Ok will give that ago...my first time but should be nice and easy. Will we have to make edits for future releases or just this one ?

Thanks to all for hard work
[Xperia Z3 Original Android Development] cajunflavoredbob:
This may have been fixed in the newer recovery. You should mention this in the OP. I tried again, and you are correct. I was able to flash it in the updated TWRP 2.8.5 with no issue without changing the script.

---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------

If you need help, I can just upload a modified zip for you. Once you are on the current recovery, you won't have this issue again.
[Xperia Z3 Original Android Development] Myself5:
so to clearify, flashing the newest MultiROM zip works with the newest recovery? So everything is fixed then I guess? If so, thank you very much for your help and your tests :) P.S. I edited the changelog for the MultiROMMgr and added the changelog links in the op.
[Xperia Z3 Original Android Development] panzerscope:
Would be very helpful if you could :) oddly though I did update my recovery to the latest according to the Multirom Manager, wonder why I still get the issue.
[Xperia Z3 Original Android Development] Myself5:
try downloading and flashing the recovery manually please. Might be caused by me updating the recovery files but you still have a older recoveryimage locally.
[Xperia Z3 Original Android Development] panzerscope:
Yeah will give that a go once im home as I don't have my laptop in order to do it...booo lol

---------- Post added at 02:03 AM ---------- Previous post was at 01:27 AM ----------

Good news, I flashed the image manually via an android app called flashr, pretty Handy, through it flashed the recovery to my Fota partition..not sure if thats normal but it worked and I was able to flash v31
[Xperia Z3 Original Android Development] cajunflavoredbob:
Yea, flashing the newest version of MultiROM zip using the newest recovery works perfectly fine.

Try installing MultiROM manager and installing the latest recovery from there. You should be able to install the zip normally after that. If you still can't, use the zip I've attached below. that has no getprop in the script. No other changes were made.

MD5 Sum: 3E79BC5544FE306DBE1DB6E2E3B422C9
[Xperia Z3 Original Android Development] panzerscope:
Thanks bud. I have already sorted as per the edit to my last post :)
[Xperia Z3 Original Android Development] cajunflavoredbob:
Awesome. Glad you were able to get it sorted. Sorry for the slow replies. Today has been busier than usual.
[Xperia Z3 Original Android Development] Leoshen:
HI,

I have problem when flash the MultiROM v31 (attach)

Anyone can help me please..

Thanks

Regards,

Leo
[Xperia Z3 Original Android Development] cajunflavoredbob:
Read back a few posts for the answer.
[Xperia Z3 Original Android Development] Leoshen:
hi cajunflavoredbob,

thanks for your reply.

yes i already try to download ****//testing.myself5.de/ but still failed...

sorry imnewbee, could you explain more?

thanks

regards

Leo
[Xperia Z3 Original Android Development] Myself5:
you shall use the newest twrp you can get from dl.myself5.de, flash it and THEN flash the multirom v31x.
[Xperia Z3 Original Android Development] erikhh92:
It's possible to install Stock ROM .77 and a experimental CM12 ROM? And... it's possible to restore DRM keys when both ROMs are installed?
[Xperia Z3 Original Android Development] JamesK852:
build.prop sent...although I kinda realized this is all a little pointless since there is no kexec hardboot kernel out there for a D6633 :p Thanks so much anyway for your hard work!
[Xperia Z3 Original Android Development] cajunflavoredbob:
Not possible. When you restore the DRM keys, it will relock your bootloader, which isn't possible on a custom kernel.
[Xperia Z3 Original Android Development] panzerscope:
Yes you can. Multirom Recovery allows you to make changes to a stock rom and secondary rom separately. I am running Stock .77 and Cm12
[Xperia Z3 Original Android Development] nscxp2005:
How would you restore the DRM keys to a stock rom if it relocks the bootloader?
[Xperia Z3 Original Android Development] erikhh92:
Restore DRM keys, lock the bootloader? I don't know that
[Xperia Z3 Original Android Development] nscxp2005:
Cajunflavouredbob says it will relock the bootloader.
[Xperia Z3 Original Android Development] cajunflavoredbob:
The process which restores the /TA partition, which is where your DRM keys are stored, relocks the bootloader in the process. You cannot have your DRM keys AND unlocked bootloader at the same time. Restoring the DRM keys relocks the bootloader. Unlocking the bootloader erases the keys. There is a thread where someone found a way to restore the functions of the DRM keys without restoring them. It tricks the system into thinking that the keys are there, when they are not. I don't have a link handy, but it's not difficult to find.
[Xperia Z3 Original Android Development] nscxp2005:
Here is the link cajunflavouredbob.

http://xdaforums.com/showthread.php?t=2930672
[Xperia Z3 Original Android Development] Leoshen:
Dear Myself5,

Thanks, now MultiRom Work =)

But i still have problem when i install OS on (dev/block/mmcblk1p1 (vfat)) the installed is succeeded but its not show on multirom or multirom app. i have 3 partition on my card

1. dev/block/mmcblk1p3 (swap)

2. dev/block/mmcblk1p2 (ext4)

3. dev/block/mmcblk1p1 (vfat)

My partition is correct? or any format to install OS on my card?

Thanks

Regards,

Leo
[Xperia Z3 Original Android Development] Myself5:
SDCard is not acting nicely. I still need to figure out why. For now install it on your internal storage.
[Xperia Z3 Original Android Development] Leoshen:
ic.. ok noted... thanks for you info... waiting your next update :)
[Xperia Z3 Original Android Development] SC_Studios:
Wait

Do I just download the modded trwp image, flash it so on so forth install roms bladdy blahhdy blah or do I have to download more files?
[Xperia Z3 Original Android Development] Myself5:
not sure how you managed to skip this part in the OP. It clearly says

-Flash TWRP

-flash multirom installer zip

then flash the ROMs you want in the MultiROM menu
[Xperia Z3 Original Android Development] Tw1tchy:
Hi I read this thread a bit but couldn't find an answer. I currently have a locked bootloader with drm keys. If I make a nandroid with twrp and unlock bootloader and install multirom. Can I install my nandroid with drm keys as a secondary Rom and still keep my drm keys, PlayStation remote play, and camera tweaks?
[Xperia Z3 Original Android Development] panzerscope:
Odd, Since I moved to CM12 and flashed your TWRP to put Multirom back...when trying to boot into the recovery I am just presented with a blank screen. Hmmmm
[Xperia Z3 Original Android Development] Myself5:
New Update is up. It's just updated from upstream MultiROM and TWPR, which means it should include a fix for Kernels with seperated RAMDisks (e.g. the Sony Stock Kernel).

Oh and the Recovery should include an option to work with F2FS, which means it can be tested with M5 Kernel ;)

Oh², as the Recovery is now compressed with LZMA it should work with M5 Kernel again.

Regards
[Xperia Z3 Original Android Development] know.i.dee:
I'm Bootlooping, followed instructions Added NEW rom

Can access Recovery, ROMs are listed however I dont have any otion for boot

---------- Post added at 03:26 PM ---------- Previous post was at 03:21 PM ----------

ok, copied the Newer ROM via adv. Options to Primary, rebooted and I'm Flying.

This Incredible . . . . . excellent work
[Xperia Z3 Original Android Development] Aronuser:
[MENTION=3816568]Myself5[/MENTION] I assume everyone would be happy if we could use the new lollipop ? stock on multirom recovery too. Thanks in advance.
[Xperia Z3 Original Android Development] Myself5:
I currently have other problems than compatibility with a Stock Rom... Bootimage fails to inject when installing the zip and I got to throw out a new built to fix this. The Stock Rom is not working due to the Stock Kernel having a seperated RamDisk (@olivieer is working on adding compatiblilty for this to MultiRom), till then use a (not yet existing) Custom Kernel which has a builtin Ramdisk (like AndroPlus Kernel).

P.S. [MENTION=4443334]Grarak[/MENTION] Muhaha ;)
[Xperia Z3 Original Android Development] Myself5:
New Version is uploaded guys. It is now installable again. Howver, still no support for external Ramdisks (before anyone comes up with some hopes :P)
[Xperia Z3 Original Android Development] Crosslife:
[MOD][Z3] MultiROM v31x

Do you recommend update it via multirom manager app? I see an update.now...

Also The app is telling me that the multirom recovery is not installed. But everything works properly...

Edit: It's done..No problem.

Enviado desde mi iPad utilizando Tapatalk
[Xperia Z3 Original Android Development] know.i.dee:
Just stopped Working, restarted to Boot to another ROM, just boots to Main (internal) any ideas?!?
[Xperia Z3 Original Android Development] know.i.dee:
I cannot get rid of this, How do You uninstall, I'm using D6603 / Leo I've attempted flashing TWRP 2.8.5 but I believe that this MultiROM is before this:

The multiROM uninstaller does NOT work!

I cant get rid of it . . . . . It hasn't worked for me at all

Really want rid of this!

Any ideas, I do not want to faf about reinstalling ROMs and ultimate;y redo all the apps & settings (thats the real irritant)
[Xperia Z3 Original Android Development] Myself5:
Reflash a Kernel using fastboot or the recovery (but in recovery do NOT tick inject boot.img) then remove the multirom folder in your internal SD Card. No idea why the uninstaller is not working.
[Xperia Z3 Original Android Development] know.i.dee:
Thanks Sir, Gonna ReFlash Everything try a 5.0+ ROM
[Xperia Z3 Original Android Development] Crosslife:
I´m having a problem that I didn't have before. When I add another ROM from "backup", I can' t boot it... The only I have is the recovery when I reboot after the restore is done successfully. Thanks. So I have to make a clean install again, and everything works again...
[Xperia Z3 Original Android Development] mick353:
Im receiving the following.. Im using kk with androplusv32 as internal..

Installed blisspop v2.2 and gapps. Upon install boot I relieve this error.. Any insight??

multirom: kexec call failed, re-running it to get info:

<3>[ 13.714722] multirom: kernel: 0xb5f9e008 kernel_size: 6d53f0

<3>[ 13.714731] multirom: DTB: --boardname was not specified.

<3>[ 13.714737] multirom: Cannot load /zImage

<6>[ 13.844596] mdss_dsi_panel_on: ctrl=f5816010 ndx=0

<6>[ 13.852813] multirom: Pixel format: 1080x1920 @ 32bpp

<6>[ 13.852820] multirom: Pixel format: RGBX_8888

<6>[ 13.875555] multirom: Framebuffer implementation: Generic