yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] thecdn:
I've been using multirom for some time now with no issues but a problem came up when I updated to the latest version. The 'swipe' button isn't there anymore - I can't initiate any actions like backup or install because I can't do the swipe to start it. The word swipe is in the normal place, and the line is partially there but not the button.

I used flashify to download and install both philz recovery, and plain cwm, then downloaded and installed straight twrp. In both cases philz and cwm worked fine, but the install of twrp still showed the multirom option (can't remember if it's supposed to do that or not), and still had the problem with the swipe button not being there. I just remembered that last night I also flashed normal twrp using fastboot and that didn't change anything.

Is there a way to 'zero out' the existing twrp/multirom settings so I can get a clean install with the swipe button? I was surprised that after flashing two different recoveries, philz and cwm, that a fresh install of twrp/multirom still had the no button issue.

Any ideas would be appreciated.
[Nexus 7 (2013) Original Android Development] z31s1g:
Update the theme:

https://basketbuild.com/devs/z31s1g/1200/TWRP 286X_v1
[Nexus 7 (2013) Original Android Development] thecdn:
I used flashify to update with the dark multirom theme but that didn't change anything. I noticed that flashify offers the option to download stock recovery. Any idea what that would do for me? Would it zero things out and allow a fresh install of twrp/multirom to work properly.
[Nexus 7 (2013) Original Android Development] mdamaged:
Delete the theme, and see if it solves it.
[Nexus 7 (2013) Original Android Development] thecdn:
Duplicate post - computer froze....

---------- Post added at 01:42 PM ---------- Previous post was at 01:34 PM ----------

How/where do I delete the theme?
[Nexus 7 (2013) Original Android Development] mdamaged:
/TWRP/theme, just use a file manager or whatever.
[Nexus 7 (2013) Original Android Development] thecdn:
That did it, thanks a lot. I had forgotten what the original looked like :)
[Nexus 7 (2013) Original Android Development] drewski_1:
you don't flash the theme. you copy it to the folder /twrp/theme and rename to ui.zip

EDIT: looks like you solved it. that folder where you deleted is where you should copy the theme zip to, if you want to go back to themed. make sure theme version matches TWRP version.
[Nexus 7 (2013) Original Android Development] lapocompris:
After having installed Clean ROM as primary, Screwed's and Grogg's as secondary, I have only 1GB remaining flash memory on my 32GB Nexus.

I have no movie nor music, no heavy game just the usual apps.

Is it normal ?
[Nexus 7 (2013) Original Android Development] thecdn:
I would say no. Get the diskusage app, run it, and see what is taking up so much space. I've seen games leave behind large footprints even after being uninstalled. Something is not right with only 1gb left in that situation.
[Nexus 7 (2013) Original Android Development] drewski_1:
doesn't sound right, but all your apps are going to be duplicated in each ROM install so a lot of apps can kill space rapidly. what are "the usual apps"?
[Nexus 7 (2013) Original Android Development] iaTa:
I'm getting a google logo bootloop after flashing MR and 5.1 stock kernel with kexec on fresh clean install of 5.1 factory image which I rooted.

Any ideas?

EDIT: Flashed stock 5.1 kernel back and it boots fine but without MR boot menu obviously. Something wrong with the stock 5.1 kernel with kexec mod?
[Nexus 7 (2013) Original Android Development] Gorgtech:
I had the same experience. The 5.1 MR Kernel seems to be broken. Luckily I had a elementalx 3.05 Kernel left on my device and tried it in the recovery ( though it was built for 5.0.2 ) and the device started again.

Well, the kernel works somehow but I see some ugly laggs in comparison to the Stock Kernel. I hope there will be a update soon :p
[Nexus 7 (2013) Original Android Development] Tasssadar:
That's weird, it's just stock kernel Oo. The build must've been borked somehow, I took it down for now.

EDIT: Fixed, the kernel apparently didn't like being built with newer gcc(?).
[Nexus 7 (2013) Original Android Development] Gorgtech:
I flashed the new 5.1 MR Kernel and this one works like a charm :o:good:
[Nexus 7 (2013) Original Android Development] Tasssadar:
CyanogenMod 12.1 nightlies are broken as secondaries due to the LZ4 compression they implemented. I got a fix for that already done, but the compression still breaks normal TWRP backups, fixing that will take a while - so until then, don't flash CM 12.1 nightlies from 2015-04-17 and newer.
[Nexus 7 (2013) Original Android Development] geo78:
Can someone help me?

I have stock rom for primary and i get the message for the ota update to 5.1.

what is the procedure to update? after restart i get the message

Package expects build fingerprint of google/razor/flo:5.0.2/LRX22g/1649326:user/release-keys or google/razor/flo:5.1/LMY470/1783956:user/release-keys;

this device has Android/omni_flo/flo:5.1/LMY47D/tassadar04101119:userdebug/test-keys

E:Error executing updater binary in zip '/cache/update.zip'
[Nexus 7 (2013) Original Android Development] mdamaged:
It looks like you're using a different ROM than stock, if that is the case, ask or wait for an update from the devs of that ROM.

If you want stock 5.1.0 then grab the images from google, extract boot.img and system.img, and fastboot flash them, then fastboot format cache, reinstall normal twrp, flash supersu, install BB, then reinstall MR. Then redo whatever you do to system, like xposed, etc.
[Nexus 7 (2013) Original Android Development] geo78:
Thanks for the answer.

No i have the stock updated image (ota update before installing MR)... Has changed something?

Anyway I will try to do as you tell me with a fresh image. What about my second rom in MR that i use as primary? Is there a way not to loose it as it is?
[Nexus 7 (2013) Original Android Development] mdamaged:
The secondary image will remain untouched, once you re-install MR, as outlined in my previous post, the second ROM will still be there. Flashing from fastboot will only flash to the primary, it's just that when you flash boot.img from stock images, it takes out MR (and TWRP) and puts back stock recovery, but does not affect the secondary.
[Nexus 7 (2013) Original Android Development] madbat99:
Stock 5.1.1? Where is that img hiding?
[Nexus 7 (2013) Original Android Development] mdamaged:
Sorry, I mean of course 5.1.0.

(fixed)
[Nexus 7 (2013) Original Android Development] geo78:
thanks a lot!

if i replace the secondary with the primary rom, and delete the old android 5.02 image (now as secondary), is there a way to fresh install android stock 5.1 as a secondary?
[Nexus 7 (2013) Original Android Development] madbat99:
Try scrosler's stock rooted 5.1 rom .zip.
[Nexus 7 (2013) Original Android Development] geo78:
Thanks a lot! I'll try that I think is faster than sideload 5.1 to primary

Edit ->worked great.easy and fast!
[Nexus 7 (2013) Original Android Development] rulk:
Hello, I have an ASUS Nexus 7 (2013 Wifi only) that I installed Multirom on when it originally came out for my tablet.

As listed on the Multirom App:

MultiRom v32a

Recovery 2015-04-10

Kernel: Stock 4.4.1 and 4.4.2

I have the Stock Rooted 4.4.2 ROM on this device as my Primary Rom.

Primary Rom Kernel (from "About tablet" ) is :

3.0.4-g45e759d

tassadar@nymeria #184

I believe I got this kernel so I can do OTG host while charging.

My secondary rom is a Cyanogen 11 rom but I will likely delete this since I have not used it.

My third rom is a pwned pad rom which is obsolete now too..

I will be deleting the 2nd and 3rd roms and replacing them but I would like to update the primary rom to the latest Lollipop stock rom and keep the applications I have now. Just as if I had used the OTA upgrade... I just don't know where to find the proper images and know how to do the upgrade and hope I don't have to read through the MANY pages of this thread hoping to find the right answer... Can someone please help or atleast point me in the right direction? Thanks!

Rodney
[Nexus 7 (2013) Original Android Development] mdamaged:
https://developers.google.com/android/nexus/images

And since you do not want to read (xda may not be for you then): Extract, remove -w, flash.

This, and anything else related to basic flashing is out of the scope of this thread, everything else can be found here.
[Nexus 7 (2013) Original Android Development] metalblaster:
I know this question has been beaten to death at this point but has qualcom ever come out and released the drivers to allow for full variants of Linux to be used on the N7(2013) or has anyone found a way around this?
[Nexus 7 (2013) Original Android Development] wapvirus:
I had the same issue with my 32gb clean Rom made my device 16gb ,to fix it downloads stock Rom from Google unzip and run the bat file that will put you back to stock but your 32gb is back I used this opportunity to upgrade to 5.1.1 relock then unlock bootloader this fully wipes everything
[Nexus 7 (2013) Original Android Development] pretty pixel:
Installation

My N7 2013 WiFi device is unlocked, rooted and running Lollipop 5.1.1. Please can someone advise me on the best way to install Multirom? Is it better to install the components manually? Or, simply install the Multirom app and let it install the necessary components? Also, do I need a patched kernel for the stock ROM? If so, will the Multirom app flash this as part of the install process? Thanks in advance :)
[Nexus 7 (2013) Original Android Development] mdamaged:
I am on 5.1.1 and just used the install method via the app, it worked perfectly.
[Nexus 7 (2013) Original Android Development] pretty pixel:
That's great :) Thank you for the reply.
[Nexus 7 (2013) Original Android Development] minhaz.sourav:
I installed CyanogenMod 12.1 ROM as secondary ROM. But when I booted the rom it was just Glowing the CM logo...Waited few minutes but no progress... Whats the prob there actually?

Device : Nexus 7 LTE (razorg/deb)

Rom : Stock 5.1 (Rooted and TWRP/Multirom installed)

Kernel : ElementalX N7 4.0
[Nexus 7 (2013) Original Android Development] madbat99:
Just gotta wait longer. If it still doesn't boot, just boot to recovery then boot back to system and wait. Sometimes it takes 10 minutes or more.
[Nexus 7 (2013) Original Android Development] minhaz.sourav:
Well, How can I add gapps or any flashable zip to secondary ROM? Just flash zips in Multirom>Add ROM?
[Nexus 7 (2013) Original Android Development] mdamaged:
TWRP>Advanced>MultiROM>List ROMS, select ROM, tap the rom you want to install to, the rest is obvious.
[Nexus 7 (2013) Original Android Development] minhaz.sourav:
TQ. :)

Now CM12.1 booted.

BUT IT IS GIVING SYSTEM STORAGE WARNING & working SLOW.
[Nexus 7 (2013) Original Android Development] madbat99:
Do you have enough free storage? You have to limit your apps a little if you're running multiple Roms. Make sure you flashed the right gapps. It should run perfect.
[Nexus 7 (2013) Original Android Development] TheC92:
Update!!

5.1.1_r6 (LMY48G)

https://developers.google.com/android/nexus/images#razor
[Nexus 7 (2013) Original Android Development] lapocompris:
After flashing, the unlock slider is hard to activate and need several attemps to work.

Is it normal ?
[Nexus 7 (2013) Original Android Development] furtom:
I had the same problem. Disabling the TWRP theme fixed it for me.
[Nexus 7 (2013) Original Android Development] z31s1g:
The problem on flo is that the ui runs with low fps. It's sluggish. Using the stock lockscreen (with "invisible" slider) can be painful, as one can't see if the slider keeps up with the swipe. One needs to do it slowly. Or use the "alternative lockscreen" (option in the theme settings). Well, or remove the theme, of course (but that should be the very last resort... ;)).
[Nexus 7 (2013) Original Android Development] drewski_1:
I read in a TWRP thread that the slider issue is a known TWRP bug. I've seen this on a few of my devices.

There's supposed to be a fix in the queue.

Sent from my Nexus 10
[Nexus 7 (2013) Original Android Development] w2vy:
I have a rooted Nexus 7 (flo) and was able to install via the app store and everything is working well.

When I install Ubuntu Touch from the dev-proposed channel the newest version is #275 (Aug 2 2015).

If I load that version and perform an OTA update then it will stop working.

Can someone else please verify this for me? (so I know it is not just me)

What info can I capture to help fixing the problem?

Tom
[Nexus 7 (2013) Original Android Development] osm0sis:
I just updated from within UbuntuTouch from r274 to r280 (the most current) and it also doesn't boot anymore. :confused:

I guess we should try to figure out which build onward doesn't work from a fresh install.
[Nexus 7 (2013) Original Android Development] w2vy:
I did that, 275 works, 276 and above does not

It is nothing to be confused about... the Ubuntu Touch is a moving target...

I am sure this can be resolved...

tom
[Nexus 7 (2013) Original Android Development] osm0sis:
Yup. Already r281 almost works again, getting past the Google logo to the Ubuntu loading animation, but it seems to get stuck and loop from there.
[Nexus 7 (2013) Original Android Development] w2vy:
And r282 works! :good:
[Nexus 7 (2013) Original Android Development] w2vy:
I had one user PM me that he was seeing the same issue in r282 as I saw in r281

Anyone else get r282 on Nexus 7 (flo) running?

tom
[Nexus 7 (2013) Original Android Development] osm0sis:
Updated no problem from r275 to r282. Google logo took a little longer than usual but it booted up fine! :good:
[Nexus 7 (2013) Original Android Development] w2vy:
When I was running an touch update (to 286 in this case) I have seen a message

"Temporary swap setup failed"

It does not seem to be a problem, is it normal?

Tom
[Nexus 7 (2013) Original Android Development] doniks:
stable channel for deb

Hi Tasssadar!

It seems that Canonical has added a stable channel for Nexus 7 flo with the

latest UT release. Any chance that you could somehow extend your offering of channels for deb to include a stable channel as well?
[Nexus 7 (2013) Original Android Development] geo78:
Noob question: I ve installed a second rom and the pc cannot see the tablet storage when booted from it.

Is that possible?
[Nexus 7 (2013) Original Android Development] madbat99:
Does the second rom have a kernel with USB fastcharge? That has to be off to see files from a pc. Also make sure mtp is selected in storage.

Sent from my Nexus 9
[Nexus 7 (2013) Original Android Development] geo78:
Don't know about the first, can't see the second...
[Nexus 7 (2013) Original Android Development] madbat99:
Check in settings/storage, then tap the three dot button in the upper right corner. It will say USB computer connections. Tap that, then make sure mtp is checked.
[Nexus 7 (2013) Original Android Development] geo78:
Thanks!!!
[Nexus 7 (2013) Original Android Development] w2vy:
I have a stock Nexus 7 with TWRP and MultiROM 32a (that's stock, right??)

I just got the latest OTA update and it is not installing properly.

I've had this configuration running for a couple of months and I thought I recently had another update, but I could be wrong.

It looks like my default.prop is wrong, how could this happen? it says I have ver 5.1 and when I boot I see 5.1.1 (which matches my build.prop)

I attached the prop files (as txt) and the latest update.zip

Should I copy the proper settings from build.prop to default.prop?

tom
[Nexus 7 (2013) Original Android Development] mdamaged:
No, that's no longer considered stock, don't bother with OTA, it's not going to work, just extract and flash boot.img and system.img from the factory images, wipe caches, and you'll be updated. Of course you will have to reflash twrp, reroot, intstall multirom and whatever other things you did to system or kernel, but that's easy peasy.
[Nexus 7 (2013) Original Android Development] w2vy:
What about the other ROMS I have installed? Will they be wiped out too?

Tom
[Nexus 7 (2013) Original Android Development] mdamaged:
Nope, they will still be there when you finish reinstalling multirom, the process only affects the primary ROM.
[Nexus 7 (2013) Original Android Development] w2vy:
So, what should I expect to lose in my system if I use the MultiROM 32a app and Update/Install Kernel?

Which in my case says "Stock 5.1.1" (reverting my system back to stock)

Will that trigger a Factory Reset or will the system just revert to what I had before?

(with the kexec-hardboot patch removed)

allowing me to run the update as normal (or manually with TWRP)?

I guess the key question is will the prop's files be cleaned up?

Tom
[Nexus 7 (2013) Original Android Development] madbat99:
You will just get the stock system and kernel. And yes you will then be able to ota update. But you can flash the system.img and boot.img from the new factory image and you will be updated. You will not lose any data. You can then re root and re install multirom (with multirom manager app) and you will be right back where you were, but now updated.
[Nexus 7 (2013) Original Android Development] mdamaged:
You will loose the kernel with the kexec patch (when you flashed boot.img), and any alteration you made to system (root, busybox, things like v4a, anything that altered system), and it will put stock recovery on, which is why you need twrp after the flashing, it dos not trigger a factory reset, I do it all the time, all your userdata is untouched.

If you grab the latest factory image, there is no need to accept any update, you will already be updated, again, forget the OTA, it makes no sense to flash an older system only to wait for an update, when you can just flash the latest straight away.

Here are the steps I use (I just did my flo last night):

I download the latest factory image, then extract the contents, then go into the directory it made and look for (in my case) image-razor-lmy48m.zip, then I extract that, then I go into that directory, and copy boot.img and system.img to a new directory I make, then I copy the adb and fastboot files to it, I grab twrp image too, the directory looks like .

I plug the device into the PC, accept the fingerprint, open a command prompt in that directory do the following:

adb reboot bootloader

fastboot flash boot boot.img

fastboot flash system system.img

fastboot format cache

...reboot to system using menu

...let system build apps, verify the system is working properly, then download latest supersu (I had 2.49 beta) put it on your SD card:

adb reboot bootloader

fastboot flash recovery twrp-2.8.7.0-flo.img (you can probably extract the multirom twrp image and use it instead, but I do it this way)

...reboot into recovery using menu, it will be twrp, flash supersu, now you're rerooted, you can boot up and reinstall busybox, and multirom (this will replace that other twrp with its own), your choice of kexec'd kernel (in my case, I use elementalx so I just do that through his app) via their respective apps, then redo v4a (if you use it) and so on.

You do not need to wait for the OTA, you will already be updated assuming you grabbed the latest factory image. All your user apps and settings, and accounts will be there, so will your other roms.
[Nexus 7 (2013) Original Android Development] axxxel46:
Hi guys,

is there any linux distro (except ubuntu touch) working on nexus 7 2013 deb?

Thank You!
[Nexus 7 (2013) Original Android Development] EggZenBeanz:
Hi,

I have an issue with the Ubuntu Touch roms hanging at the google boot screen with the padlock. Nothing happens after that. This is the first attempt at boot of Ubuntu Touch.

I've tired a couple of ROMs from the various dev channels 301 (from memory) and they all react the same. I can boot into MultiRom selector OK and my CM12.1 rom just fine. Recovery works too.

Kernel is ElementalX and is returned patched

Recovery is latest installed by App

Any ideas?
[Nexus 7 (2013) Original Android Development] mdamaged:
Sounds like you should be posting this to the Ubuntu touch support forums.
[Nexus 7 (2013) Original Android Development] axxxel46:
Hi Guys

Can I update Ubuntu Touch by OTA??

Thanks you all

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 7 (2013) Original Android Development] magarto:
Could anyone flash Android 6.0 with Multirom? How? Thanks in advance!
[Nexus 7 (2013) Original Android Development] ShadowEO:
I wasn't able to get it to load, main_init threw security errors unless it was on the Internal ROM and MultiROM was not in the boot.img.
[Nexus 7 (2013) Original Android Development] sickboy82:
Yes. I flashed the latest bootloader/radio zip first on primary. Then I flashed a stock unrooted 6.0 as my secondary. Keep in mind to root your secondary you will need a custom kernel that supports marshmallow installed on the 6.0 rom, and then flash SuperSU beta 2.50. If you flash supersu with out the custom kernel the secondary will not boot.
[Nexus 7 (2013) Original Android Development] magarto:
Thanks!!!

Flashing the bootloader doesn't affect to the first installed rom?

And, how do you flash both? img files from the recovery directly or using TRWP app?
[Nexus 7 (2013) Original Android Development] osm0sis:
trampoline injection seems to disagree with Marshmallow kernels, even ElementalX in Permissive mode causing the boot to just return to recovery.
[Nexus 7 (2013) Original Android Development] sickboy82:
My primary is rooted stock 5.1.1, so in my case no.
[Nexus 7 (2013) Original Android Development] magarto:
Hi, I have two questions:

1) After flashing the new official bootloader, Multirom doesn't work, also if I inject it (also it doesn't work because trampoling injection does not work). How did you fix it? Are you flashing chainfire modified bootloader instead? It stuck in the initial Google boot screen

2) How do you do install Marshmallow in a second rom?

I do the following:

In TWRP/Advanced/MultiROM/Add ROM

Then, I choose Android ROM and Next.

I have only 3 options: zip file, backup or ADB sideload.

If I choose zip file, the image-razon-mra58k.zip gives me an error because it is not in a cwm/twrp flashable zip.

Img flashing is only possible for boot or recovery images, not system, userdata or cache

To third people, before installing Marshmallow bootloader, make a backup of the boot partition in TWRP.
[Nexus 7 (2013) Original Android Development] muschiu35bv:
Hello Guys!Will Multirom support the latest Android Marshmallow?Thank You!
[Nexus 7 (2013) Original Android Development] silvan g:
No your primary data partition will not be wiped, and they can't read data from a other room because the system partition is not shared. But you can seed pictures from other roms because data partition is shared. Please correct me if I am wrong because I am pretty new to this mod myself!
[Nexus 7 (2013) Original Android Development] teacherhh:
Thanks! Just went back to Stock Rom an reinstalled MultiRom to use Firefox OS....now waiting for 4.4, Ubuntu Touch and OmniRom :)
[Nexus 7 (2013) Original Android Development] StrangerWeather:
Thanks for your reply, yes it's OmniRom, so I can't enable adb+apps in dev settings. Any ideas?
[Nexus 7 (2013) Original Android Development] borxnx:
OmniRom does not have an effective root method yet. Check out the forum. Some say you can do it after you flash a particular kernel, others say that's a load of bull.

Either way, it's the ROM, not the mod.
[Nexus 7 (2013) Original Android Development] AL2000EX:
Yup, I meant is Data being shared between Roms, thank you
[Nexus 7 (2013) Original Android Development] robdroyd:
That's great news!

For those using previous versions of MultiROM to upgrade to the new version- do we just "download the ZIP file from second post and flash it in recovery"?

Thanks!
[Nexus 7 (2013) Original Android Development] flash5000:
Yes, but that's for doing a MultiROM update (for example v16->v16a). What you would need to to is update the recovery (using fastboot or Flashify) to get the auto-injection...

Gesendet von meinem Nexus 4 mit Tapatalk