yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] doniks:
I have that same problem on my nexus 7, deb, where the Ubuntu Touch installation seems to be stuck at the Google Logo. It had worked in the past.

I can't find how to turn on these developer options you speak of. Where is this "options menu"? I see two pages in the MultiRom Manager ap:

"Install/update" which has the three sections: "Status", "Install/Update" and "Install Ubuntu Touch", and

"Manage ROMs" which lists the primary&secondary roms that are installed.

I am using CyanogenMod 11 - the MultiROM Manager app is the latest from the Play Store : version 1.188.

Not sure about the manifest.json you are looking for, but looking at the ubports server I see similar json files as on tassadars or canonicals servers:

system-image.tasemnice.eu/channels.json

https://system-image.ubports.com/channels.json

https://system-image.ubuntu.com/channels.json

Does that help in any way?

I've also tried to replace Android completely and install Ubuntu Touch via ubuntu-device-flash as described here, but both tassadars server as well as ubports lead to an error “This phone needs restoring from a PC or service center.” like shown here.
[Nexus 7 (2013) Original Android Development] doniks:
My bad, found it ... top right ... :p

Got it ... this one: http://tasemnice.eu/multirom/manifest.json

That's indeed a very different file than the channel.json's I mentioned. Not sure how one would teach multirom an alternate channel.json. Mhm. After overwriting the device name to "flo", multirom offers various flo channels and images. Since none of these can be found on tassadars server (http://system-image.tasemnice.eu/ubuntu-touch/) it seems that the app is transparently switching between these two: system-image.tasemnice.eu/channels.json

https://system-image.ubuntu.com/channels.json
[Nexus 7 (2013) Original Android Development] langeveld024:
[MENTION=7365581]knopancakes[/MENTION]

I tried to install Ubuntu (stable and devel) as secondary using multirom manager on my flo.

(with cm13 and elementalX kernel as primary)

Stuck on Google splash.

So I changed flo to deb after I read your post, same story. It just won't boot.

But while installing in TWRP, the log shows some error "failed: kernel supports no swap" or something like that.

I'll try to upload the log as soon as possible.
[Nexus 7 (2013) Original Android Development] osm0sis:
Like I've said a few times by now.. rc-proposed/ubuntu is your best bet. I just let it auto-update from r397 to r428 and it all worked and boots fine.
[Nexus 7 (2013) Original Android Development] osm0sis:
While we wait for [MENTION=3418703]Tasssadar[/MENTION] to come back and pull the trigger on a new official build, luckily [MENTION=2605798]nkk71[/MENTION] and [MENTION=1162986]Captain_Throwback[/MENTION] have agreed to make us some updated unofficial builds! I've tested them out for them so now we're ready for a more public release. :D

MultiROM v33a + MR-TWRP 3.0.2-0 (20160505-01):

https://basketbuild.com/devs/Captain_Throwback/Nexus 7 2013/MultiROM

All credit to them both for the new commits and the actual builds. Thanks guys! :good:
[Nexus 7 (2013) Original Android Development] osm0sis:
All your script does is extract the

file

system.img to your system mount.. so there's nothing there to boot, only the actual

file

system.img, i.e. "/system/system.img".

system.img isn't like boot.img, I don't believe you can flash it directly to a partition block in recovery and have it work, plus, with MultiROM it's not a real block device, so even if that could work, it likely wouldn't work for MultiROM.
[Nexus 7 (2013) Original Android Development] followmsi:
It works on Flo Hardware .. for internal.

Like on other devices too.

If you look a few threads above there is the complete script.

Of course with boot.img too.

Formating works well .. just the extract of the system.img fails.

Where is the difference when you format the same "block" partition inside update.zip scripts ?
[Nexus 7 (2013) Original Android Development] osm0sis:
Ah! Cool to know that works with a normal block partition device. Still though, MultiROM just redirects the /system mount/device to a directory in /data/media/0/MultiROM/roms/.../system, so since it's a directory not a true block device I'm guessing that's why it doesn't work.

Go in with adb shell into the directories I mention above after a flash attempt and you'll probably see the system.img as a whole single file in there.
[Nexus 7 (2013) Original Android Development] followmsi:
write_raw_image is normally used for "real" block device flashing.

extract_package_file is just extracting the .img file.

After simg2img the system.img is just ext4 filesystem anyway.

I will check the data folder as well ..

But where is the difference if you format the block device in Update.zip ?

Can this be fixed/changed in next multirom release ? ;)

---------- Post added at 11:44 AM ---------- Previous post was at 11:30 AM ----------

Checked the */data/media/0/MultiROM/roms/.../system folder .. it's completely empty !

Not even the full system.img file.

Would be very cool if you guys can include "this" way of Update.zip too.

Thanks
[Nexus 7 (2013) Original Android Development] doniks:
Seems our friendly neighbours have figured it out! The following works for me:

Where, I'd say that should be Feb 10 and for deb, I'd say the sensible choice is vivid.
[Nexus 7 (2013) Original Android Development] nkk71:
that particular method was never supported, nor is it [really supported now], we thought about addressing it, including some other unconventional "scripts / deletes" as well

but since it seems that/those methods have become quite scarce we never bothered... this is MultiROM after all :D
[Nexus 7 (2013) Original Android Development] followmsi:
This is edify code.

I don't see this as unconventional and also not as a retired function. ;)

This is a nice and still used way to install system.img quickly !

Without bothering about detailed file rights and symlinks inside System.img.

As I really like MultiROM I would be happy to use this way in the future too.

Do you see any chance for implementation from your side ?

Thanks
[Nexus 7 (2013) Original Android Development] nkk71:
Possible yes... is it going to be added, dunno, i'm not working on mrom for a while

there are several ways how this can be approached, and since i dont want to go into an elaborate discussion about it, here's a question:

how big is your system partition

how big is that system.img

how big are the actual "files" within that system.img

example: the system.img was created using a TWRP backup / dd / etc., so it's the real full system partition size (let's say 2GB), the actual ROM (files) within it is only 200MB... result: 1.8GB of wasted space on internal storage

(if used as is)

guess, there are other methods to work around it, but not sure it's worth the implementation atm
[Nexus 7 (2013) Original Android Development] followmsi:
You can just make a resize2fs -M system.img and it's back to 200mb - the real size.

Do e2fsck -f system.img before and you are happy.

In my update.zip i am using resize2fs the other way around to enlarge file system to full partition size.

Works well ..

Here are we talking about Flo stock system.img anyway .. latest May Update.

Why is .img file size important ?

If you have enough space on /data left the MultiROM system.img could also be 2gb, even with 1.8gb empty space.

Thanks for your help !
[Nexus 7 (2013) Original Android Development] nkk71:
i was just giving an example of system.img size... (eg, HTC M9 4GB, so i really wouldnt want 4GB img's hanging around when even the largest HTC Sense ROMs are well below that, and other ROMs, can be just a few hundred MBs)

whereas a normal partition would have a constant size, and the files within it can take as little or as much as they like, since the rest of the space is not [usually] used,

mrom on the other hand "prefers" (so to say), a "file" ordered system, not a "partition" system (well okay, the latter is done when flashing to non ext partitions, so yeah, to an extent we can even use a full system.img .... i guess)

my thoughts would be more along the lines, of mounting your system.img, then extracting the files to the mrom fake system folder..... kinda what the installer script is supposed to do ;)

like i said, i can think of quite a few "methods"... dunno which would work best, etc

but, as i mentioned, i really didnt want to get into a long discussion about it

basically... is it feasible, yeah, i do think so;

how hard is it; what's the best method, etc? dunno... maybe just as simple as "copying" the the system.img file, and using it as such :cyclops:
[Nexus 7 (2013) Original Android Development] followmsi:
For example in Tassadar Update.zip he is using ..

format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");

It's even more radical ;)

How do you "wrap" this block device format command into multirom ?

The same way it should work with package_extract_file("system.img", ......

The update script is taking care of deploying files .. but in another way expected. ;)

As said before, on hardware for "internal" rom, it works fine.

Looking forward for next MultiROM version .. I am happy to test anything related to this topic ;)

Thanks again for all your help !
[Nexus 7 (2013) Original Android Development] nkk71:
that particular command (iirc), just get's "replaced" / mrom-edified by rm -rf

others dont, depends, each is quite separate
[Nexus 7 (2013) Original Android Development] nikk95:
(OP) Indeed, vivid is a better option, utopic is dated and vivid proposed lags a lot. your welcome :)
[Nexus 7 (2013) Original Android Development] g4_e:
I'm attempting to dual boot pure Nexus as the primary rom and Kali nethunter as the secondary. I'm using the elemental x kernel for the primary rom. So I add the Kali zip and the installation goes perfectly fine. I reboot and I select kali. The Google logo shows up and then a black screen with logs shows up saying it failed. I press power button to reboot and I reboot back into pure Nexus. Any ideas?

---------- Post added at 03:13 AM ---------- Previous post was at 02:36 AM ----------

When I got into the black screen it also created a log file so I put it on paste bin http://pastebin.com/YzZC5mz4 All help is appreciated:)
[Nexus 7 (2013) Original Android Development] marsaltito:
What rom you use for nethunter ?
[Nexus 7 (2013) Original Android Development] g4_e:
I resolved the problem a bit ago. Started using dirty unicorns for nethunter and it's working fine:) thanks
[Nexus 7 (2013) Original Android Development] PlatinumG:
Hey guys is there any way this would work with oppo find 7a? I installed multirom manager and it said my phone wasn't supported so is there any other way to do it ? Thanks
[Nexus 7 (2013) Original Android Development] drewski_1:
Always a possibility, but this is a N7 forum
[Nexus 7 (2013) Original Android Development] badhon_raj:
Is there any way to install ubuntu desktop? I hate ubuntu touch.

The image files are available here:

http://old-releases.ubuntu.com/rele....04-preinstalled-desktop-armhf+nexus7.img.gz
[Nexus 7 (2013) Original Android Development] osm0sis:
Have you tried switching the recent UTouch builds to desktop mode? They're sort of unified now.
[Nexus 7 (2013) Original Android Development] badhon_raj:
you can do that? I didn't know. How to do that?
[Nexus 7 (2013) Original Android Development] osm0sis:
I don't have access to my tablet right now to tell you, but it's in the settings. Install the latest build from rc-proposed/ubuntu via the MultiROM app and it shouldn't be too hard to find. :good:
[Nexus 7 (2013) Original Android Development] thadrumr:
I have tried all the methods mentioned in this thread and I am unable to boot the latest rc/proposed/ubuntu build on my Nexus 7 2013. It just hangs on the Google boot screen logo.
[Nexus 7 (2013) Original Android Development] osm0sis:
I just went from rc-proposed r456 to r494 with no issues. Sure you didn't use devel-proposed by mistake? Make sure you're using the latest MultiROM I posted a few pages back.

This should roughly be the list of channels you should see in the MultiROM app for install:

https://system-image.ubuntu.com/ubuntu-touch/

And just to reiterate, be sure you're choosing rc-proposed, which should be up to r494 as of this posting:

https://system-image.ubuntu.com/ubuntu-touch/rc-proposed/ubuntu/flo/

So I double checked, and it's in the System section of the status/notification bar pulldown; a toggle called "Desktop mode".
[Nexus 7 (2013) Original Android Development] thadrumr:
I have updated to the Multirom version you posted version 33a and updated to the TWRP version posted as well versin 3.0.2. I am still unable to get ubuntu touch to boot it just sits at the Google bootloader screen. I just wiped the secondary rom and re-installed it using rc-proposed/ubuntu and it sitll will not boot. I also tried to inject the boot secot using TWRP and it still won't boot Ubuntu. It will boot Cynogenmod just fine.
[Nexus 7 (2013) Original Android Development] osm0sis:
If CM is your primary ROM that might be the issue right there. Is it CAF or AOSP-based? The UbuntuTouch MROM install might be using the primary ROM's boot.img to create its own, and CAF might not be supported. I am using Stock ROM and franco.Kernel and as I said, UbuntuTouch is working great on the rc-proposed channel, and I also have Firefox OS, Sailfish OS and Kali Nethunter as other working secondary ROMs. ;)
[Nexus 7 (2013) Original Android Development] thadrumr:
I am using the Official Cyanogenmod 13 Nightlies as I have been for a while. It worked dual booting CM 12 official and Ubuntu touch. I took it off for a while when I was on CM12 but came back to it recently with CM13 as the base.

Update I just setup my Nexus 7 Exactly like yours with Stock 6.0.1 with the Franco Kernel and the TWRP and MultiRom from this thread and I was finally able to boot Ubuntu Touch. Whew what the heck.
[Nexus 7 (2013) Original Android Development] BreckZeBoulay:
I just want to PM the Captain, but he doesn't accept PM.

So I allow my self to paste the PM I can't sent to him
[Nexus 7 (2013) Original Android Development] osm0sis:
Yes, [MENTION=1162986]Captain_Throwback[/MENTION]'s N5 builds are similarly updated. I think he's got an actual thread for them too if you check his profile.
[Nexus 7 (2013) Original Android Development] Captain_Throwback:
I never posted a thread or anything since I don't own these devices. I think I did post the the link in the N5 MultiROM thread some time ago, but it was so long ago I don't even remember, lol.
[Nexus 7 (2013) Original Android Development] Wannabedeveloper:
Any update how to make Android N work in multirom?
[Nexus 7 (2013) Original Android Development] osm0sis:
You can work around it by moving Internal to secondary, then flashing ROM to Internal, rebooting recovery, then flashing SuperSU and GApps to Internal and swapping back to the secondary.

It's an issue with block writing zips. I know there was a fix for that the works but it still doesn't seem do it when I tried on my N5 the other day. Maybe [MENTION=2605798]nkk71[/MENTION] or [MENTION=1162986]Captain_Throwback[/MENTION] have a better idea of it.
[Nexus 7 (2013) Original Android Development] nkk71:
What's the error?

I dont have a Nexus device so can't check it myself, but block_image_update scripts are supported.

If you cold upload some logs, and updater scripts, I could take a look... no promises though, currently trying to get a secondary to boot on my HTC 10 :eek:
[Nexus 7 (2013) Original Android Development] osm0sis:
Absolutely. Thanks for looking into it!

recovery.log

updater-script
[Nexus 7 (2013) Original Android Development] nkk71:
Yeah, that's gonna need a bit of work.

First off, the block_image_update (with check):

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");

is going to be replaced by

ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
# Following line was added by MultiROM
run_program("/sbin/sh", "-c", "mkdir -p /tmpsystem && mount -t ext4 $(readlink -f -n /dev/block/mtdblock0) /tmpsystem && (chattr -R -i /system/* || true) && (rm -rf /system/* || true) && (cp -a /tmpsystem/* /system/ || true) && cp_xattrs /tmpsystem /system");
abort("E1001: Failed to update system image.");

so the "abort("E1001: Failed to update system image.");" will always be triggered.

As for the 'log' command that's only been implemented on andorid-7.0 branch of twrp here

And I'm nowhere even close to merging (or even looking at) all the changes yet :angel:

If you want to workaround it:

1) change the updater-script:

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");

and remove the abort, so it looks like:

block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

2) add a dummy file (possibly a shell program that does nothing ;) ) named "log", but it in /sbin and set proper permission

Once I have MultiROM on the 10 working, I'll start updating TWRP; unfortunately currently I cannot push a fix just for this, as I have too many unpushed changes, that would probably get messed up :p

Good news is I have it "almost" working

MultiROM-TWRP working fine

Encryption working fine :D

Flashing secondaries working fine

Boot Menu working fine

Internal ROM boots fine

EDIT: strike the bad news

Bad news:

Secondary ROMs.... aren't behaving themselves and don't want to boot properly, lol :mad:

And trying to track down the error (yeah it's one tiny error :p) is proving difficult :mad:

Had my first secondary booted a few hours ago :D

guess it's time to make sure things work, then start merging "new" stuff :D
[Nexus 7 (2013) Original Android Development] tungdil:
Since Basketbuild is still down with "... no ETA", is this updated version available anywhere else?
[Nexus 7 (2013) Original Android Development] osm0sis:
I think BasketBuild will be back by tomorrow (edit: nope - they changed their ETA again..), but I believe I saw [MENTION=1162986]Captain_Throwback[/MENTION] has an AndroidFileHost mirror as well? If you search for his posts in the main Materialised TWRP theme thread you'll find the link.
[Nexus 7 (2013) Original Android Development] Captain_Throwback:
Only the hammerhead and m8 builds there have the updated stock theme, though. When I did a repo sync it wiped out my custom theme patch for the other device builds. I haven't updated the device files and run new builds yet.
[Nexus 7 (2013) Original Android Development] Grantah:
any info on why I'm always getting stuck on the "g00gle" screen with this install and everyother ubuntu i've tried to install non will boot thru the google startup screen.
[Nexus 7 (2013) Original Android Development] tungdil:
first experiences with flashing Nougat

After some testing I thought I'd report my experiences...

AOSP 7.0 Nougat as secondary ROM (that's where I started)

Installing Nougat as secondary ROM is possible after editing the updater-script.

v0.4 wouldn't boot without installing Tk-Glitch's kernel. Once "glitched" it'll boot but sensors and camera are broken.

v0.5 (new secondary, i.e. "clean flash") will boot and sensors and camera work fine. Flashing glitch-r251 "N" does not change this.

Rooting does not seem possible. At least BETA-SuperSU-v2.77 and SuperSU-v2.78 both resulted in getting stuck at the Google logo with a hard-reset being the only way out.

Actually I tried a lot of different approaches when trying to root: changed what was flashed, how flashing was performed (e.g. rebooting to recovery before booting), etc.. but without success. This finally left me in a situation where the secondaries wouldn't boot any more. Dirty flashing these didn't help here. Thus I decided to wipe everything including internal storage and start from scratch.

AOSP 7.0 Nougat as primary ROM

Flashing v0.5 --this time on a clean device without MultiROM or anything else-- as primary ROM works (of course) without changing updater-script. Successfully flashed V7 Gapps the "MM way", i.e. flash immediately after the ROM without rebooting.

Rooting with SuperSU works as expected (Note: I rooted after flashing glitch-r251 "N" ) with boot-looping just once.

Flashing MultiROM and [MENTION=3847629]Tk-Glitch[/MENTION] 's kernel does allow flashing and booting secondary ROM's as usual.

Dirty flashing of v0.6 breaks the secondary ROM's again. I.e. these won't boot any more and dirty flashing the secondary does not help. My best guess is; clean flashing will break the secondaries as well.

I haven't checked if backup and restore can be used as a "work-around" when the secondary got broken. Also I haven't tried moving Nougat to a secondary as recommended by [MENTION=4544860]osm0sis[/MENTION] a few posts above.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5098312]tungdil[/MENTION]

Installing Nougat as primary, flashing SuperSU and moving it to secondary works.
[Nexus 7 (2013) Original Android Development] nkk71:
So much text, so little information
[Nexus 7 (2013) Original Android Development] tungdil:
Thanks! Just verified that restoring a TWRP-backup (of a primary or secondary ROM) as secondary works too. As probably should have been expected.
[Nexus 7 (2013) Original Android Development] nkk71:
Well been kinda busy, and i don't think i can build for you guys, but [most] of the "stuff" has been updated:

TWRP (mrom edition): https://github.com/nkk71/android_bootable_recovery/tree/android-7.0-mrom

MultiROM https://github.com/nkk71/multirom

anything fully committed and pushed would also be found on https://github.com/multirom-htc (<- this is kinda the main one, anything on mine, may be still get deleted and forced, i eventually push to that repo)

But yep, can confirm the unofficial CM14 (for the M8) flashed, and booted fine, with no script changes whatsoever:

A quick note: for anybody (hint [MENTION=1162986]Captain_Throwback[/MENTION]) who intends on building this, file_contexts has been changed so this no longer works... but luckily, instead of changing the code, you can just use hook 1 in mrom to fix that ;)

at least for the time being, until we find way to patch the new file_contexts (I havent looked at that part yet) :o
[Nexus 7 (2013) Original Android Development] Captain_Throwback:
Well, I built it. No idea if it works, though.
[Nexus 7 (2013) Original Android Development] nkk71:
Don't look at me, I've never had a Nexus device .... uhm yet :eek:

But i'm guessing, if it's been coded and built.... not long before someone flashes :D

PS: anybody using no-kexec pre version 4, and now using no-kexec version 4.... let me know!

(nah, it works fine, it's just a question of upgrading from the old one to the new on an

existing

secondary ROM)
[Nexus 7 (2013) Original Android Development] .MoHaMaD:
:D
[Nexus 7 (2013) Original Android Development] nkk71:
yeah, i need to fix the version thingy for backwards compatibility, if thats possible :mad::(

anyway, my screenshots look nice too :p

http://xdaforums.com/devdb/project/?id=17079#screenshots
[Nexus 7 (2013) Original Android Development] Startrek852:
The version number worked properly in the September builds, just not in this one.
[Nexus 7 (2013) Original Android Development] nkk71:
it's due to the added functionality, and the official app has no idea about it, sorry about that, i already said i'll try to kinda fix it
[Nexus 7 (2013) Original Android Development] Startrek852:
It's OK, I just wanted to let you know that it worked fine in the September builds.
[Nexus 7 (2013) Original Android Development] nkk71:
thanks, but i know that already, it's due to the added feature, and the official app can't parse that extended version number.
[Nexus 7 (2013) Original Android Development] Startrek852:
OK, thanks for telling me.