yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] jpearn:
Works well for me thanks!
[Nexus 7 (2013) Original Android Development] nkk71:
That version may not work for encryption, just FYI everyone. (builds after March 5, and before March 26)
[Nexus 7 (2013) Original Android Development] ajeje93:
With this version I cannot flash zip to secondary ROM (it is LOS 14.1) or better all seems to go fine and without errors, but after booting into system nothing has flashed in reality. Any solutions?
[Nexus 7 (2013) Original Android Development] alex2534alex:
Where can I found deb-version of Captain_Throwback's MultiROM recovery? I can't install deb-ROM because of error ("This ROM is for deb, your device is flo")
[Nexus 7 (2013) Original Android Development] drewski_1:
Did you search?
[Nexus 7 (2013) Original Android Development] alex2534alex:
Yes, of course. But I've founded only this
[Nexus 7 (2013) Original Android Development] jpearn:
Did anyone manage to solve the Ubuntu Touch not booting issue ?

Edit - Downgraded to the old Captain Throwback version 20160505 and seems to be booting Ubuntu OK with stock 6.0 rom as primary with Glitch Kernel. Just need to check what other things I have broken on the way !

Edit 2 - Looks like I have to switch between old and new Multirom to get 7.0+ roms booting. Extra step but at least I have Ubuntu back !
[Nexus 7 (2013) Original Android Development] spadival:
Can you please explain how to do this?
[Nexus 7 (2013) Original Android Development] jpearn:
Have both sets of Multirom old and latest downloaded / in a folder so you can boot to recovery, flash the recovery and corresponding zip file for the ROM you want to boot. I have 6.0 factory as my primary ROM so it will boot when either is installed; flash the latest Multirom set to boot 7.0+ roms, flash the old version to get Ubuntu back.
[Nexus 7 (2013) Original Android Development] mrv2002ptrz:
faulty eMMC

It seems my internal mmc card go bad. Booting system stucks on Google logo but I still able to boot into bootloader and recovery. In TWRP mount /system /data and /cache failed with error (Invalid argument) and dmesg shows multiple errors: mmcblk0: error -110. So I tried Multirom for booting system from USB-OTG flash memory. But when I "fastboot flash recovery TWRP_multirom_flo_20160210.img" and reboot into recovery it stucks on Google logo. If i do "fastboot boot TWRP_multirom_flo_20160210.img" it stucks on "MiltiROM TWRP v.3.0.0-0" logo. I think thats because of accessing to the internal storage. Can this somehow be overcome on a tablet with faulty eMMC? I mean, there shouldn't be any read/write operations from/to internal storage neither in installation zip nor in Multirom TWRP. They must be replaced by operations with USB-OTG flash.
[Nexus 7 (2013) Original Android Development] JT1510365:
No they didnt
[Nexus 7 (2013) Original Android Development] Catbirby:
I've now spent several days on this. Trying multiple things like going hunting down and reverting to older multiROM versions, and trying every branch of utouch. When referring to 20160505, would be the version that can be found in the archive of the basketbuild posted earlier (post 1375) that will show up under the multiROM manager as v33a? What version and/or branch of utouch are you using?
[Nexus 7 (2013) Original Android Development] iamdsilver:
hello,I use deb for nexus 7 2013 (LTE)

and always fail to flash a secondary rom

I use Multirom app on google play

its version is v33 trwp just for "flo"(wifi)

of course flash rom fail.

then I try" multirom-20170314-v33b-UNOFFICIAL-flo.zip"

and" TWRP_3.1.0-0_multirom_flo_20170314.img"

or "TWRP_3.0.2-0_multirom_deb_20161018.img"

the result are the same

flash lineage os 15.1 ,14.1…

will had error 7 on TWRP

and I edit "ROM.zip/META-INF/com/google/android/updater-script" to ignore the error 7

every rom will boot first time success

and have some errorr(trebuchet has error,google play service has error…)

I must flash the new rom as first rom (internal) that will success, but never successfully flash any rom by secondary rom

what should i do?

is multirom v33 do not support nougat and oreo?

i see the log only supprort to mushmallow……

thanks
[Nexus 7 (2013) Original Android Development] EclipseGT:
any new MultiROM versions available?

Is there a multirom version that will work with TWRP 3.2.1-0 and Oreo 8.1 builds? I would like to continue to use my Marshmallow rom as primary and install Oreo rom as secondary.
[Nexus 7 (2013) Original Android Development] vgnmnky:
I picked up a Nexus 7 2013 specially to install Linux, alongside Android. I've spent hours a day over the last few days struggling with all of the different components, but have made a bit of headway.

I've unlocked, rooted, and installed Multirom Manager etc. I'm using:

multirom-20170314-v33b-UNOFFICIAL-flo.zip

TWRP_3.1.0-0_multirom_flo_20170314-01.img

ElementalX-N7-6.17.zip (from stock 6.01)

I can install Ubuntu Touch, various versions, in the Multirom app. However, when selecting at boot, it gets stuck in a Google/blank-screen boot loop.

I've tried other kernels, and other versions of Multirom and TWRP, with the same results. With that combination above though, I did manage to install LineageOS 14.1, and that works fine. With plain v33 and 3.0.0, I didn't even get that far.

Is there a step I'm missing? Has anyone got it working recently with those files, or with different ones? Or with a different version of Linux? Doesn't even have to be touch-friendly, as I'll be using it with a mini-keyboard.

Thanks for any guidance!
[Nexus 7 (2013) Original Android Development] iamdsilver:
I use deb device

recovery:TWRP_3.0.2-0_multirom_deb_20161018.img"

multirom:v33b

Question 1:

is the someone install Android 8.1 in secondary ROM successfully? like

[ROM] Resurrection Remix-OS 6.0.0 [8.1.0]

I always meet "System UI has Stopped"

Question 2:

Is xposed compatible MultiROM?

when I install xposed, no matter Primary ROM or secondary ROM, every secondary ROM was dead, even then I flash xposed install.zip, all the secondary ROM can not resurrection and boot loop.

ALL my ROM in device

primary : Resurrection Remix-OS 6.0.0 (8.1)

secondary :

1. CM11(4.4)

2. MoRom(6.0)

3. Resurrection Remix(7.1)

4. NetHunter(6.0)
[Nexus 7 (2013) Original Android Development] ShadowEO:
I'm not sure as to the first question, though MultiROM shouldn't cause APKs to crash, however Xposed IS compatible with MultiROM. You may have better luck with Magisk and the Xposed module instead however.

Your primary is an 8.1 ROM, does your 8.1 Kernel have kexec support? I noticed the nokexec doesn't always boot well, so if you do not have Kexec support with your primary, your secondaries may not boot as iirc nokexec uses your current kernel and ramdisk, which means that it may be attempting to load Xposed on the secondaries (and I assume you didn't flash Xposed to your secondaries) and it would fail to boot as Xposed's files wouldn't be installed to inject into Zygote during it's startup, making Zygote crash as it won't find XposedBridge installed (thus causing your boot loop)
[Nexus 7 (2013) Original Android Development] iamdsilver:
I have a new issue

I meet this situation when flash NetHunter

the NetHunter package is well, it can be flashed on primary rom

but when I flash it on secondary Rom

it will appear something like attach picture

I think maybe it is because of kernel

my primary ROM use CM15.1 with ElementalX kernel and xposed

other secondary Rom work well(from 4.4 to 7.1)

then I flash "android 6.0 kernel" for NetHunter marshmallow

I had tried

1. ElementalX kernel(for android 6.0)

2. Kernel w/ kexec-hardboot patch (Stock 6.0 and 6.0.1):

Still can not boot NetHunter

this situation sometimes happen when I flash a new ROM and I don't know why cause this

How could I solve it

thank you

ps

I use deb device

recovery:TWRP_3.0.2-0_multirom_deb_20161018.img"

multirom:v33b
[Nexus 7 (2013) Original Android Development] iamdsilver:
thank you for reply

I had crossover trial many times, more than twenty times.

I still don't know why my secondary rom use android 8.1 always has "System UI has Stopped".

no matter I flash xposed in primary Rom or secondary Rom,

or even, I never flash any xposed moudle.

My solution is made android 8.1 in primary Rom, it is the only way for me.

and, if possible , could you please tell me

what is those function mean in TWRP?

1. inject boot section

2. inject boot.img

3. inject MultiROM after installation

I think "inject MultiROM after installation" means that I flash a .zip file, the file(like xposed moudle) will work not only on this ROM but alos all ROM, am I right?

when I select a secondary Rom

there is still

1. remove boot.img

but secondary Rom only can flash a zip file, if I remove boot.img, how could I flash a new one .img file?
[Nexus 7 (2013) Original Android Development] SGH-i200:
LineageOS 14.1 as secondary ROM

How do you do it? I have the same line up, but when I select 'LineageOS 14.1' at the boot screen, the device gets stuck in a Google/blank-screen boot loop.

lineage-14.1-20180726-nightly-flo-signed.zip + open_gapps-arm-7.1-pico-20180802.zip
[Nexus 7 (2013) Original Android Development] vgnmnky:
Hi. I can't remember doing anything special. But I didn't install any version of gapps - it's Google free, only the Lineage ROM. If you've only tried once though, it's usually worth going through it all again another time or two.
[Nexus 7 (2013) Original Android Development] SGH-i200:
ElementalX-N7-6.17 - For LineageOS-based Android 7

Thanks for the hint:

https://elementalx.org/devices/nexus-7-2013/
[Nexus 7 (2013) Original Android Development] SGH-i200:
I can't get the last build to boot. Can you try it once for me?
[Nexus 7 (2013) Original Android Development] EclipseGT:
any chance there is a MultiROM version that will work with Unlegacy 8.1 rom?
[Nexus 7 (2013) Original Android Development] ShadowEO:
I believe that for 8.x to work as a secondary room, you would still need an 8.x kernel in the primary slot, I'm not entirely sure about that though, since technically we should be kexec-ing the kernel in the secondary slot.

Inject current boot sector, injects MultiROM into the currently installed boot image on the device.

I am not entirely sure as to what exactly "Inject Boot.img" does though, perhaps someone more knowledgeable can answer this and give me a lesson so I can learn! But I believe the Inject MultiROM after installation item ensures that MultiROM is present after say, a kernel swap that completely overwrites the boot partition (meaning the ramdisk edits are gone).

You should use Inject MultiROM after Installation when installing items such as Magisk or Xposed, as those modify the boot partition's ramdisk, and MultiROM may need to be reinstalled at times.

When you use the remove boot.img button though (I am pretty sure on this one!), It removes the simulated boot partition stored under

/data/media/0/multirom/ROMs/*romname*

There's no actual flashing done to the device. Instead, when MultiROM cannot find a boot.img file for a room, it will attempt to boot using the device's boot partition instead. (This works well with Android ROMs of the same version, but doesn't work well with say a 4.4 ROM in primary, and an 8.1 in secondary. You need a boot.img in the 8.1 secondary otherwise it will fail to boot.)

If you want to replace it, simply use adb to push your new boot.img up into the folder I mentioned above, OR you can install a kernel ZIP, which will simulate flashing, but be redirected to a new boot.img (I believe it copies the current boot partition of the device to file, then redirects all modifications to the file) in the ROM's folder.

Edit: I also wanted to note, that if you want to mess with the files MultiROM uses to boot your room (the system.img, boot.img, etc) you MUST use the path I mentioned above, as it results in denied access under /sdcard or /storage/emulated/0 even under root (at least on my Flo).

I know there wasn't much I could give a concrete answer for, but I hope it helps a little :3
[Nexus 7 (2013) Original Android Development] GCOPL:
Hello,

I've got two questions:

1. Is it possible to install UBports ubuntu touch (not the old one, baked by Canonical) on nexus 7 (flo) with this version of Multirom?Version avaiable in play store had older installation locations (from Canonical).

2. If "yes", is it possible to upgrade already installed version (from play store) to this fork (?) without losing an installed operating systems?Again, If yes, how can I do that?

Thank you very much for help
[Nexus 7 (2013) Original Android Development] Juro.janosik:
running system image upgrader failed

Cant boot ubuntu help
[Nexus 7 (2013) Original Android Development] DrScrad:
MultiROM using Sinless and Nethunter

Let's say I'm using a custom ROM but would also like to install Nethunter alongside it.. is this possible? I've done a little research and saw something mentioned in a post about using MultiROM .. would greatly appreciate any tips or info on successfully undertaking this endeavor.???
[Nexus 7 (2013) Original Android Development] ZoltanG:
I successfully installed Multirom-20160207-v33-flo, kernel_kexec_flo_601 and TWRP_multirom_flo_20160210 on my Nexus 7 2013 Flo Wi-Fi tablet. The primary ROM is a factory reset and rooted 6.0.1 Android from razor-mob30x-factory-52684dff.zip, Build number: MOB30X, Security patch level Aug 5, 2016. Kernel version: 3.4.0-g953af70-00001-g4800650-dirty tassadar@tyene #11 Sun Feb 7 2016.

I tried to put a Validus-flo-8.1.0.Stable.2.7-OFFICIAL-20180812-1135 on it as a secondary ROM (earlier I already successfully installed it as a primary ROM), but I couldn't.

The installation process seems to start, it copies the zip onto the tablet but after that TWRP says:

....

writing 1024 blocks of new data

writing 1024 blocks of new data

writing 1024 blocks of new data

writing 618 blocks of new data

zeroing 1024 blocks

zeroing 830 blocks

wrote 177576 blocks; expected 177576

stashed 0 blocks

max alloc needed was 4096

deleting stash 5a79362318d00cf4c316e86435b3ed38dd35082d

E:unknown command [log]

E:unknown command [log]

script aborted: E1001: Failed to update system image.

E1001: Failed to update system image.

E:unknown command [log]

Updater process ended with ERROR: 7

I:Legacy property environment disabled.

rm: can't remove 'META-INF/com/google/android': No such file or directory

Failed to install ZIP!

(This is copied from the error log. I could send the whole log file if that helps. I also tried with a Lineage-16.0-20190506-UNOFFICIAL-flo, that produced different errors.)

After that I tried and successfully installed a razor-ota-mob30x-54635e45.zip as a secondary ROM. This is just a test but it shows that Multirom works, however I want to install higher custom ROMs as secondaries.

I'm a newbie, never programmed in Android environment, not a developer at all.

What can be the problem and what should I do to fix it?

Any help or idea is appreciated.
[Nexus 7 (2013) Original Android Development] rudals:
I want to try to test dual boot. but all links are dead.

Could you share your materials(Multirom-20160207-v33-flo, kernel_kexec_flo_601 and TWRP_multirom_flo_20160210)?
[Nexus 7 (2013) Original Android Development] ShadowEO:
This IS possible, but you need a modified version of the MultiROM Manager that looks at the UBports system-image-server instead of Canonical's. The devices.xml file needs updated with the proper URL for the UBports system-image-server and then MultiROM Manager needs recompiled and installed. Once done, it will easily install from the UBports repository.

Also, Play Store? There's a MultiROM Manager in the play store? Even still, it likely has Canonical's system-image-server in it.
[Nexus 7 (2013) Original Android Development] palyons:
So, I've tried multiple ways to get MultiROM installed. I've done it in the past on other devices, including my original Nexus 7 (2012) and had no issues. While I can get the multirom zips flashed without issues. I am left with the same problem every time, No Boot Menu. I am running a Nexus 7 2013 LTE model. Any help on this would be much appreciated.
[Nexus 7 (2013) Original Android Development] slapshot2286:
FYI - For those still looking for the zip files for MultiROM, I spent HOURS looking for it, and finally found that the links in this post still work for v33b. Good to know if you need it.
[Nexus 7 (2013) Original Android Development] Mastercodeon:
Could someone please repost the recovery images, all the links are dead, i found the post where the zip is attached, but i cant find the recovery image, i'm looking for the flo variant.

EDIT: This is what happens with light sleep deprivation and trying to set this up, i just realized the recovery image was in the zip file along with the zip to install, man i feel so dumb right now.
[Nexus 7 (2013) Original Android Development] b00b:
does anyone have or know where i can get stock roms zip files for flo can they pls pls pls upload it for us?

searched google for hours and all those basketbuild links here and eslewhere are dead e.g.

lrx21p_flo.zip

:fingers-crossed:
[Nexus 7 (2013) Original Android Development] ojcu:
Hi everyone,

I installed MultiROM via the app, but it didn't boot into system after installation. It only goes into bootloader. From there I can go into MultiROM TWRP so I tried to flash my ROM again but it only gives my an error like in a picture. I also tried fastboot but my laptop doesn't connect to the tablet. It might be bad cable or loose usb in Nexus, still need to check it. Any ideas how I can fix it?
[Nexus 7 (2013) Original Android Development] s2g-unit:
I'm also looking for the modified TWRP with landscape. Does anybody happen to have a link they can share?
[Nexus 7 (2013) Original Android Development] mirzabek87:
помогите мне получить ссылку на этот файл, спасибо![/код]

[/QUOTE]
[Nexus 7 (2013) Original Android Development] Tasssadar:
Yes, you can.
[Nexus 7 (2013) Original Android Development] StrangerWeather:
Update fails for me on a secondary rom, but it is a 4.4 rom so maybe that's why?
[Nexus 7 (2013) Original Android Development] Tasssadar:
How fails, what does it say? Take a screenshot of that installation screen and post logcat in here.
[Nexus 7 (2013) Original Android Development] StrangerWeather:
Basically, it fails to connect, in spite of good connection. Not sure why, I've tried about 10 times.
[Nexus 7 (2013) Original Android Development] Tasssadar:
That's weird, not sure I can do anything about that, seems like the connection to the fileserver just timeouts. Can you access the webserver directly via http://54.194.25.123/ ? It should just say "Welcome to nginx!". Try also it's hostname, http://ec2-54-194-25-123.eu-west-1.compute.amazonaws.com
[Nexus 7 (2013) Original Android Development] StrangerWeather:
No, for some reason I can't, I tried both urls... Strange! By the way I love Multirom. Thanks so much for it!
[Nexus 7 (2013) Original Android Development] sopidos:
Well, i have to try this out :)
[Nexus 7 (2013) Original Android Development] cinco312:
After installing and flashing another ROM, my Wifi doesn't turn on on my default ROM. Wifi works fine on AOKP (secondary ROM) On my default ROM the Wifi just says turning on, left it for an hour and it never turned on. I uninstalled MR and it works fine again, then re-installed MR, AOKP, and PA and the same thing happens.

Any suggestions? Thanks.
[Nexus 7 (2013) Original Android Development] Jewveeski:
Great Work Thanks Again Man!!!
[Nexus 7 (2013) Original Android Development] Tomsgt:
Made a little video on installing this awesome Mod with the google play app. HERE hope you guys like it and please add it to your OP if you want. thanks for you work on android making these devices awesome.
[Nexus 7 (2013) Original Android Development] jessejames44:
I already have some back ups can I restore one for the second ROM on multi manager.
[Nexus 7 (2013) Original Android Development] silvan g:
Yes! :)
[Nexus 7 (2013) Original Android Development] GialanG:
Update to KitKat

If I update to KitKat today, will MultiROM still work? My guess... No...?
[Nexus 7 (2013) Original Android Development] s2k7:
Yes!
[Nexus 7 (2013) Original Android Development] GialanG:
So what kernel works with KitKat compatible with MultiROM?
[Nexus 7 (2013) Original Android Development] jessejames44:
Gone are the days of wiping everything and restoring a ROM.This is a freaking awesome utility keep up the great work and thank you.
[Nexus 7 (2013) Original Android Development] elRadix:
MultiRom does not work with kitkat. MultiRom installs the 4.3 kernel wich breaks the Wifi module.
[Nexus 7 (2013) Original Android Development] s2k7:
I used 4.3（elementX） in internal, kikkat as secondary.
[Nexus 7 (2013) Original Android Development] Tasssadar:
There's a difference between MultiROM installs 4.3 kernel and I specifically selected 4.3 kernel to install into 4.4 ROM. MultiROM should support 4.4 just fine, the only problem is that kernel sources are not out yet, so you can only use it as secondary ROM for now. I honestly have no idea what's taking them so long - the rest of 4.4 code is already in repositories - even prebuilt kernels in device folders. They might want to release kernel sources, factory images and proprietary binaries all at once, but still - kernel is not affected by any licences from manufacturers, so it doesn't make much sense to me.
[Nexus 7 (2013) Original Android Development] roofrider:
Has anyone installed 4.4 as secondary? This is what i'm looking to do currently, haven't used MultiROM previously so i'm still figuring stuff out lol.

*Wondering if "Inject curr.boot sector" aka "Inject MultiROM after installing" should be enabled for every kind of update.zip (gapps, whatnot, etc..) that is flashed to the Primary ROM?

*What are "*.mrom files"?

There is no way to flash the factory images of 4.4 directly as the secondary ROM huh?

Off to find a suitable OTA zip...

---------- Post added at 08:57 PM ---------- Previous post was at 08:43 PM ----------

Pure 4.4 update.zip from factory images? Yes please!
[Nexus 7 (2013) Original Android Development] giorss:
I put up as secondary a kitkat just to try and it worked well
[Nexus 7 (2013) Original Android Development] roofrider:
Which zip did you use?

scrosler's?
[Nexus 7 (2013) Original Android Development] giorss:
I tried this one:

http://xdaforums.com/showthread.php?t=2507725

it was just a try, I'm still using base 4.3 rooted and carbon 4.3

I've tried also the firefox OS (but I don't like it)

all was working well
[Nexus 7 (2013) Original Android Development] roofrider:
Oh thanks.

But I want to use the official OTA/factory image as the secondary and not source built 4.4 ;)
[Nexus 7 (2013) Original Android Development] korkfabrik:
The one from scrosler works just fine with multirom.

Just don't share the kernel from primary!
[Nexus 7 (2013) Original Android Development] Tasssadar:
4.4 factory image repacked into flashable ZIP file: flo_krt16o.zip. Nothing is changed, no root, no anything. Can be used to install 4.4 into MultiROM or to upgrade existing stock 4.3 ROM without losing data.

EDIT: dev-host does not seem to be very fast, uploading to goo.im now too.

EDIT2: uploaded, http://goo.im/devs/Tassadar/stock_zips/flo_krt16o.zip
[Nexus 7 (2013) Original Android Development] xanthrax:
... a zip for deb...?

sent from my Darkside of Nexus 4
[Nexus 7 (2013) Original Android Development] Tasssadar:
Okay, here you go, ZIPs for deb - I can't test them, but they were built exactly the same way as the ones for flo. Note that they don't flash radio from 4.4, I'm not sure whether a ZIP file should be doing that, so if you want it, you have to flash it yourself via fastboot or some other ZIP.

dev-host: http://d-h.st/hZz

goo.im: http://goo.im/devs/Tassadar/stock_zips/deb_krt16o.zip
[Nexus 7 (2013) Original Android Development] jessejames44:
Is there a limit of ROMs that can be flashed as secondary.
[Nexus 7 (2013) Original Android Development] xanthrax:
nope but ... storage limitation
[Nexus 7 (2013) Original Android Development] Grondinm:
Love Multirom on my N7. Sorry i gotta ask will it come to N5?