[MOD][FEB 10] MultiROM v33

[osm0sis]

Glad it is :good::good:

took quite some work, testing, and such
hope we didnt miss anything, but the new changes will allow for easier merges rebasing, in the future

Hmm, not working here trying to install or update Ubuntu Touch..

Unable to find partition for path '/data'

Edit: Not working in recovery to add another Android ROM either, not even after I deleted /data/media/0/multirom and started over with a fresh MR install flash.

 

[Ænimal]

Adding secondaries without issues here :good:

 

[nkk71]

Hmm, not working here trying to install or update Ubuntu Touch..

Unable to find partition for path '/data'

Edit: Not working in recovery to add another Android ROM either, not even after I deleted /data/media/0/multirom and started over with a fresh MR install flash.

Can you pull the /tmp/recovery.log after the failed flash, please

Also my devices don't have Ubuntu Touch, so there was/is no way for me to test those



Sent from my HTC One M9 using Tapatalk

 

[drewski_1]

Hmm, not working here trying to install or update Ubuntu Touch..

Unable to find partition for path '/data'

Edit: Not working in recovery to add another Android ROM either, not even after I deleted /data/media/0/multirom and started over with a fresh MR install flash.

i am able to add a secondary Android ROM (Pure Nexus 20160203 build) fine.

have not tried Ubuntu Touch

 

[osm0sis]

Adding secondaries without issues here :good:

i am able to add a secondary Android ROM (Pure Nexus 20160203 build) fine.

have not tried Ubuntu Touch

Weird. I wonder what the hell is going on..

Can you pull the /tmp/recovery.log after the failed flash, please

Also my devices don't have Ubuntu Touch, so there was/is no way for me to test those

I just booted a fresh download of TWRP_multirom_flo_20160207.img, sideloaded multirom-20160207-v33-flo.zip and attempted to add back my Firefox OS secondary ROM (which adds just like Android). Still getting that /data error that breaks Ubuntu Touch OTAs but the secondary ROM otherwise appears to add okay. :cyclops:

http://pastebin.com/VgGYYUeU

Edit: @nkk71 Here's a failed UbuntuTouch install:
http://pastebin.com/HJgemj96

The "Unable to find partition for path '/data'" error occurs even with the old multirom-20151113-v32-UNOFFICIAL-flo.zip where it did previously work 100% with it so it must be some issue with the MultiROM TWRP 3.0.0-0 build.

 

[nkk71]

Weird. I wonder what the hell is going on..



I just booted a fresh download of TWRP_multirom_flo_20160207.img, sideloaded multirom-20160207-v33-flo.zip and attempted to add back my Firefox OS secondary ROM (which adds just like Android). Still getting that /data error that breaks Ubuntu Touch OTAs but the secondary ROM otherwise appears to add okay. :cyclops:

http://pastebin.com/VgGYYUeU

Edit: @nkk71 Here's a failed UbuntuTouch install:
http://pastebin.com/HJgemj96

The "Unable to find partition for path '/data'" error occurs even with the old multirom-20151113-v32-UNOFFICIAL-flo.zip where it did previously work 100% with it so it must be some issue with the MultiROM TWRP 3.0.0-0 build.

Unfortunately, I know very little (make that an overstatement.... I know absolutely nothing about Ubuntu Touch installs, or Firefox OS); from the looks of it, the second pastebin is an OTA/ORS script, which [possibly / probably] fails due to:
line 1003: sh: system-image-upgrader: not found


the first pastebin, looks like a normal install , but a few things do seem weird, about "resource busy"... something I encountered while debugging systemless SuperSU,
but to be honest... not sure how that affects the installs, or if / what I may have broken along the way

unfortunately, there is no way atm for me to duplicate the problem (since I have neither access to these devices, nor those OSs), but i'll look into it.

sorry for the trouble :angel:

 

[osm0sis]

Unfortunately, I know very little (make that an overstatement.... I know absolutely nothing about Ubuntu Touch installs, or Firefox OS); from the looks of it, the second pastebin is an OTA/ORS script, which [possibly / probably] fails due to:
line 1003: sh: system-image-upgrader: not found


the first pastebin, looks like a normal install , but a few things do seem weird, about "resource busy"... something I encountered while debugging systemless SuperSU,
but to be honest... not sure how that affects the installs, or if / what I may have broken along the way

unfortunately, there is no way atm for me to duplicate the problem (since I have neither access to these devices, nor those OSs), but i'll look into it.

sorry for the trouble :angel:

Yeah, the UbuntuTouch installs are initiated by the MultiROM app, so it may be ORS.

No worries! I've just gone back to running normal TWRP for now (since I was only really using MultiROM for the UbuntuTouch support while otherwise running stock + custom kernel). Maybe @Tasssadar could also take a look since it does seem to be an issue with the updated recovery build rather than the MultiROM zip; it all still works perfectly with TWRP MultiROM 2.8.7. Let me know if/when you guys want me to test a new recovery build.

 

[nkk71]

Yeah, the UbuntuTouch installs are initiated by the MultiROM app, so it may be ORS.

No worries! I've just gone back to running normal TWRP for now (since I was only really using MultiROM for the UbuntuTouch support while otherwise running stock + custom kernel). Maybe @Tasssadar could also take a look since it does seem to be an issue with the updated recovery build rather than the MultiROM zip; it all still works perfectly with TWRP MultiROM 2.8.7. Let me know if/when you guys want me to test a new recovery build.

oops

don't laugh too much, epic fail

since I don't use/have any Ubuntu/Firefox/Chrome OS, I left out the entire recovery/phablet/ things

edit: guess will have to take a look at that again then, sorry for the inconvenience

---------- Post added at 21:50 ---------- Previous post was at 20:56 ----------

Yeah, the UbuntuTouch installs are initiated by the MultiROM app, so it may be ORS.

No worries! I've just gone back to running normal TWRP for now (since I was only really using MultiROM for the UbuntuTouch support while otherwise running stock + custom kernel). Maybe @Tasssadar could also take a look since it does seem to be an issue with the updated recovery build rather than the MultiROM zip; it all still works perfectly with TWRP MultiROM 2.8.7. Let me know if/when you guys want me to test a new recovery build.

so i rebuilt my tree, and added it, no major complications; but obviously untested

...
-rwxr-x---    1 root     root         14637 Jan  1  1970 system-image-upgrader
...

~ # system-image-upgrader
Command file doesn't exist: 

~ # system-image-upgrader --help
Command file doesn't exist: --help

~ # system-image-upgrader blarp-run-me
Command file doesn't exist: blarp-run-me

~ # gpg --help
gpg (GnuPG) 1.4.13
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB

Syntax: gpg [options] [files]
Sign, check, encrypt or decrypt
Default operation depends on the input data

Commands:
 
 -s, --sign [file]             make a signature
     --clearsign [file]        make a clear text signature
 -b, --detach-sign             make a detached signature
 -e, --encrypt                 encrypt data
 -c, --symmetric               encryption only with symmetric cipher
 -d, --decrypt                 decrypt data (default)
     --verify                  verify a signature
     --list-keys               list keys
     --list-sigs               list keys and signatures
     --check-sigs              list and check key signatures
     --fingerprint             list keys and fingerprints
 -K, --list-secret-keys        list secret keys
     --gen-key                 generate a new key pair
     --delete-keys             remove keys from the public keyring
     --delete-secret-keys      remove keys from the secret keyring
     --sign-key                sign a key
     --lsign-key               sign a key locally
     --edit-key                sign or edit a key
     --gen-revoke              generate a revocation certificate
     --export                  export keys
     --send-keys               export keys to a key server
     --recv-keys               import keys from a key server
     --search-keys             search for keys on a key server
     --refresh-keys            update all keys from a keyserver
     --import                  import/merge keys
     --card-status             print the card status
     --card-edit               change data on a card
     --change-pin              change a card's PIN
     --update-trustdb          update the trust database
     --print-md algo [files]   print message digests

Options:
 
 -a, --armor                   create ascii armored output
 -r, --recipient NAME          encrypt for NAME
 -u, --local-user              use this user-id to sign or decrypt
 -z N                          set compress level N (0 disables)
     --textmode                use canonical text mode
 -o, --output                  use as output file
 -v, --verbose                 verbose
 -n, --dry-run                 do not make any changes
 -i, --interactive             prompt before overwriting
     --openpgp                 use strict OpenPGP behavior
     --pgp2                    generate PGP 2.x compatible messages

(See the man page for a complete listing of all commands and options)

Examples:

 -se -r Bob [file]          sign and encrypt for user Bob
 --clearsign [file]         make a clear text signature
 --detach-sign [file]       make a detached signature
 --list-keys [names]        show keys
 --fingerprint [names]      show fingerprints

Please report bugs to <[email protected]>.

obviously, i need to add a new pull for that, and I personally can't test it, beyond the above
neither any of the other guys, as most of us have HTCs

---------- Post added at 22:09 ---------- Previous post was at 21:50 ----------

https://github.com/Tasssadar/Team-Win-Recovery-Project/pull/25

but I have no way of testing this, nor do I build for these devices, that's all I can do for that issue.

 

[Voklav]

Hmm, not working here trying to install or update Ubuntu Touch..

Unable to find partition for path '/data'

Edit: Not working in recovery to add another Android ROM either, not even after I deleted /data/media/0/multirom and started over with a fresh MR install flash.

+1
Same here.

 

[nkk71]

+1
Same here.

did you actually the read the post just above yours?

 

[Voklav]

did you actually the read the post just above yours?

O hahah it was not loading.... Sorry hahaha - I didn't see any of this post

Personal note : back to opera.
Edit:
LOL that fix was a quick !
Everiting work fine

 

[samsungf6500]

hello,

several times I tried to activate encryption on secondary aosp rom without success.
primary rom was always the same as secondary aosp rom during test.
i tried different stock android roms 4.4.4 , 5.1.1 and for the moment 6.0.1.
The disk is ext4 format.

i am using the lte version of the nexus 7

maybe some of you have an idea what i need to take care about

thank you

 

[osm0sis]

Nice, OP updated with a 0210 recovery build for those who didn't notice. Thanks @nkk71 and @Tasssadar.

I'm at work but I'll do some testing in a bit to make sure Ubuntu and the /data error are gone. :good:

Edit: Yup! All good now on both fronts! Great work gentlemen! Fully functional again.

 

[osm0sis]

@nkk71, Sailfish OS icon for the repo?
https://openrepos.net/sites/default/files/styles/thumbnail/public/packages/721/icon-sailfish.png

 

[bmakk2055]

MultiROM v33 and updated recovery was just released. @nkk71 and @z31s1g pretty much made this update possible by their contributions, thanks!

It has some compatibility fixes and updates TWRP to 3.0.0. CM13 now works, as well as system-less su (use BETA 2.67-20160203160253 ( http://bit.ly/m_su ) or newer).

ZIPs made from factory images of 5.1.1 and 6.0.1 can be found on androidfilehost and basketbuild (unmodified stock images, no root, no anything. Forceencrypt and verify is disabled in these).

@Tasssadar could you fix your flashable stock img flo? I keep getting a script update error when flashing as primary rom.

 

[brownstyle]

i got error failed to mount/cache while setting up multirom..my device is asus ze550kl but i edited the build.prop similar to nexus.help pls

 

[drewski_1]

i got error failed to mount/cache while setting up multirom..my device is asus ze550kl but i edited the build.prop similar to nexus.help pls

I don't think you can just modify build.prop and use the N7 multirom on another device

Sent from my Nexus 10 using Tapatalk

 

[samsungf6500]

hello,

several times I tried to activate encryption on secondary aosp rom without success.
primary rom was always the same as secondary aosp rom during test.
i tried different stock android roms 4.4.4 , 5.1.1 and for the moment 6.0.1.
The disk is ext4 format.

i am using the lte version of the nexus 7

maybe some of you have an idea what i need to take care about

thank you

Hello,

I understand that it is difficult to answer my previous question.

Maybe this one is easier,

Is someone of you using the encryption ?
if yes what is your configuration ?

Which primary image do you use ?
Which kernel do you use on the primary rom ?

Which secondary image do you use ?
Which kernel do you use on the secondary rom ?

Thank you for your help.

 

[tiidigital]

encrypted device...

i've installed multirom.. and i did a device encryption using the internal rom, cm13, with a 4x4 pattern...
when the encryption finished and the device rebooted it got stuck in boot loop... i rebooted and it got stuck again in bootloop without asking me for the decryption pattern at boot... next i booted into multirom recovery.. and it asked me for the unlock pattern... i put the correct pattern (i'm 100% sure it is the correct pattern) and it says "wrong pattern.. please try again".. furthermore i gone snooping around inda file manager and also terminal... not doing anything concrete... so i decided to reflash system with a backup that i've done b4... flashed a backup of a aicp rom... wich is cm13 based.. and when i rebooted it appears now onscreen at boot "encrypted device... please enter your password" and it shows the pattern dots though 3x3 instead of 4x4...

/data was formated as f2fs b4 encryption

how can i make multiboot recognize the correct pattern
how can i change the boot screen to show a 4x4 pattern instead of 3x3

so..
i have recovery working (except the multiboot button)
i have adb & fastboot access


can i get some advise from any expert on the subject???

thank you very much in advance

 

[osm0sis]

@Tasssadar, the devel-proposed channel for UbuntuTouch flo disappeared in the in the last MultiROM app update. Can you add it back?

PSA: r455 is broken by the way, doesn't get past the Google logo. Trying to do a fresh install is how I noticed it was missing in the app.

devel r8 works if people want to try the Ubuntu 16.x branch with less chance for breakage, and rc-proposed is good for the latest 15.x fixes.