[MOD][FEB 10] MultiROM v33

[samteeee]

Greetings;

I installed ubuntu touch through the "multirom manager" and all went smooth but It
won't pass Google screen. Any suggestion?
Thank you.

 

[osm0sis]

Greetings;

I installed ubuntu touch through the "multirom manager" and all went smooth but It
won't pass Google screen. Any suggestion?
Thank you.

Read the post before yours?

 

[samteeee]

Read the post before yours?

Thanks for replying.
I tried the others as well to no avail!
It must be my set up, right?

 

[Oicebot]

Read the post before yours?

Sorry to be a pain here. I've got the same issue(stuck at google logo) when install Ubuntu Touch in my Nexus7(2013) stock 6.0.1 with multirom.
Yes, I've read the previous posts between page 126 to 129, it seems that this issue was come with the latest TWRP multirom v3.0.0, right?
So I wonder where can I download the latest working version of TWRP multirom img( I tried the latest build v20160210, no luck), thank you for your time.

EDIT: Strange... I found the old TWRP_multirom_flo_20150212.img (v2.8.5), so I use fastboot to flash that recovery into my device. But still I got stuck at google logo after I re-install the UbuntuTouch (devel-proposed,v467) ...

 

[osm0sis]

Sorry to be a pain here. I've got the same issue(stuck at google logo) when install Ubuntu Touch in my Nexus7(2013) stock 6.0.1 with multirom.
Yes, I've read the previous posts between page 126 to 129, it seems that this issue was come with the latest TWRP multirom v3.0.0, right?
So I wonder where can I download the latest working version of TWRP multirom img( I tried the latest build v20160210, no luck), thank you for your time.

EDIT: Strange... I found the old TWRP_multirom_flo_20150212.img (v2.8.5), so I use fastboot to flash that recovery into my device. But still I got stuck at google logo after I re-install the UbuntuTouch (devel-proposed,v467) ...

As I said in my post, use rc-proposed/ubuntu (currently r397) or devel/ubuntu (currently r8). It all works fine for me with the latest MR TWRP3.

 

[knopancakes]

As I said in my post, use rc-proposed/ubuntu (currently r397) or devel/ubuntu (currently r8). It all works fine for me with the latest MR TWRP3.

Hello,

I seem to also be having the same issue as Oicebot. I have tried both devel r8 and r7, and some older utopic builds, and in all cases the tablet simply reboots after sitting at the Google screen for a moment. I'm on the 2013 Nexus 7 (LTE/deb) stock 6.0.1 with multirom. I have been using the images for |deb| from Tassadar's server.

I've also tried installing Ubuntu Touch from several of the channels on Tassadar's sever by using the ubuntu-device-flash utility, and each time Ubuntu starts up, the Ubuntu logo displays for a few seconds before it changes to a picture of a chip with an "X" through it and a message directing to connect to a PC for recovery.

From this I've gathered that there may be something wrong with the Ubuntu Touch builds for my target platform, but I find it strange that using the same images through Multiboot does not even yield a loading screen for Ubuntu before the device resets.

Any insight would be greatly appreciated.

 

[osm0sis]

Might be something up with deb support then, since devel r8 and rc-proposed r397 both install and boot fine from the MultiROM app for me on my flo.

 

[knopancakes]

En Taro @Tasssadar, I will send you cookies if you fix this or suggest a viable workaround.

 

[Pawel01]

As I said in my post, use rc-proposed/ubuntu (currently r397) or devel/ubuntu (currently r8). It all works fine for me with the latest MR TWRP3.

Strange. I try to install devel r8 as secondary Rom, and it also stucks at the Google Logo. Cm13 as primary and stock rooted 5.0 as secondary allready there, with ElementalX. Latest Multirom- and MR-TWRP-Version.

 

[erikieperikie]

I'm getting the infamous ‘Unfortunately, Setup Wizard has stopped.’ problem. I've read about it in numerous threads all over the web, but I can't fix it using the proposed solutions, e.g. fixing the permissions of the Setup Wizard app: they are already granted. Ungranting and regranting them doesn't work either.

I'm trying to install CM13 as a secondary ROM with Multirom. I've downloaded the latest stable release and the opengapps micro package. I go into TWRP-MR recovery -> MR -> Add ROM -> flash CM13 zip -> flash gapps -> reboot system. I've tried all kinds of dalvik/cache/data wiping of the ROM in between and after the gapps installation. Nothing seems to work.

 

[klaust58]

I read, the actual opengapps packages are broken...

Gesendet von meinem HTC One_M8 mit Tapatalk

 

[knopancakes]

Strange. I try to install devel r8 as secondary Rom, and it also stucks at the Google Logo. Cm13 as primary and stock rooted 5.0 as secondary allready there, with ElementalX. Latest Multirom- and MR-TWRP-Version.

Are you on the LTE model? It seems something is wrong with the images being held on Tassadar's server that supports the packages for deb. I got Ubuntu Touch working on mine just now by switching to the images for flo, the wifi-only model. I was able to do this by going into the MultiRom Manager options menu and tapping the version number until it gave me developer options, then changing the device name from deb to flo. There is also an option to change the server address.

It seems someone else has a more up to date server here - [system-image dot ubports dot com]. Sorry about syntax, I'm a newbie so it doesn't let me post link. MultiRom doesn't seem to support adding ROM archives manually, and this alternative server doesn't have a manifest.json like Tassadar's so this might be a dead end.

I notice a major difference in the amount of time it took to install the flo ROM vs the deb ROM, in that flo took much longer. Something is definitely amiss somewhere.

 

[erikieperikie]

I read, the actual opengapps packages are broken...

Gesendet von meinem HTC One_M8 mit Tapatalk

That could be the case, of course. I've found the solution here: use the CM13 GApps from http://www.teamandroid.com/gapps/.

 

[muhammad_fatah]

I installed Ubuntu touch on my deb but the device is just hanging around the Google logo (cause it's not actually installing Ubuntu touch) , I saw some people facing the same problem. Here's my recovery log, hope anybody can help....

Starting image upgrader: Thu Mar 31 11:47:49 CDT 2016
Loading keyring: archive-master-tasemnice.tar.xz
8192+0 records in
8192+0 records out
33554432 bytes (32.0MB) copied, 0.247479 seconds, 129.3MB/s
Setting up swapspace version 1, size = 33550336 bytes
swapon: /cache/recovery/SWAP.img: Unknown error -38
Temporary swap setup failed! Does the kernel support swap?
Processing the command file
Formating: data
Formating: system
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000245 seconds, 0B/s
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
128000 inodes, 512000 blocks
25600 blocks (5) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
16 block groups
32768 blocks per group, 32768 fragments per group
8000 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Loading keyring: image-master.tar.xz
Loading keyring: image-signing.tar.xz
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Keyring expired: /cache/recovery/image-signing.tar.xz

system-image-upgrader failed
I:Set page: 'action_complete'
Iperation_end - status=1

 

[osm0sis]

I seem to recall @z31s1g saying he finished up work on the new TWRP3 dark theme for MultiROM. Hopefully it gets merged in for MultiROM TWRP 3.0.1. :fingers-crossed:

 

[roofrider]

I seem to recall @z31s1g saying he finished up work on the new TWRP3 dark theme for MultiROM. Hopefully it gets merged in for MultiROM TWRP 3.0.1. :fingers-crossed:

I'm waiting for it tooooooooo...but where is tassadar!?

 

[[email protected]]

Hello All,

I have several ROMs installed via MultiROM (Ubuntu Touch, Firefox OS, CM12.1). But weird thing happened to my Nexus 7 (flo, 16Gb) on the weekend.
I wanted to add a new one Bliss Rom 6.0 by Team Bliss as a secondary ROM. At the first time installation failed, and I expected that free space be the same as before but I noticed it has decreased by ~500Mb. So I've tried one more time, failed and again I've lost 500Mb. I tried to google something on that but no success. So yesterday I spent a lot of time trying to find something that may take this place on my device but nothing unusual was found (checked /data/media/0/multirom and explored almost all internal memory). I decided to make one more try to add this ROM. This time installation was successful but as it was Marshmallow ROM it hasn't booted so I've removed it. Nevertheless I looked at the amount of free space that has left after all this manipulations and again - minus 500Mb

So totally I've lost 1.5Gb of internal memory. I haven't tried to re-flash factory images yet. I'd like to figure out what is going on. So I have a couple of questions here :

• Did anybody tried to flash this ROM as secondary via MultiROM ?
• Did anybody faced the similar behavior ever ?
• What can be done to find missing space and get it back ?

Appreciate any response.

Yesss!!! Finally I've managed to fix this!
I tried Resize option of TWRP recovery for /data partition and it gets me back my 1.5 GB. Woohoo!
I hope somebody find this useful. See more details about this option https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html

 

[osm0sis]

I'm waiting for it tooooooooo...but where is tassadar!?

Maybe @nkk71 can make sure everything's up to date again so @Tasssadar can just pull the trigger on an official release? Or maybe even hook us up with an unofficial build if Tas is away for a bit again.

I haven't looked but I presume @z31s1g's theme update would be pull requested or something? :good:

 

[nkk71]

Maybe @nkk71 can make sure everything's up to date again so @Tasssadar can just pull the trigger on an official release? Or maybe even hook us up with an unofficial build if Tas is away for a bit again.

I haven't looked but I presume @z31s1g's theme update would be pull requested or something? :good:

I've been busy rewriting my no-kexec-workaround, so haven't updated 3.0.2, but @Captain_Throwback has here

This not only brings it up to date with TWRP 3.0.2, and the new stock theme by @z31s1g, but also includes many multirom related fixes (post February 10 build)


New theme screenshots:

Splash

Main Menu (notice the MultiROM button is in the top right, to access MultiROM functions)

MultiROM Main

MultiROM Storage Selector

MultiROM Settings

etc

 

[thereal_bigjake]

I've been busy rewriting my no-kexec-workaround, so haven't updated 3.0.2, but @Captain_Throwback has here

This not only brings it up to date with TWRP 3.0.2, and the new stock theme by @z31s1g, but also includes many multirom related fixes (post February 10 build)


New theme screenshots:

Splash

Main Menu (notice the MultiROM button is in the top right, to access MultiROM functions)

MultiROM Main

MultiROM Storage Selector

MultiROM Settings

etc

Sweet thanks ? Works for the N5, will have to try the N7 now

Sent from my Nexus 5 using Tapatalk