yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] Aswin08:
Any solution for Layers issue??(regarding vendor..)

thanks for the mod.
[Nexus 6P Android Development] UniX1rm:
I am using elementalx patched kernel

my primary is pure nexus cmte

my secondary is cm13 nightly.

originally installing pure nexus as primary and screwed as the secondary, it booted up fine, but with screwed it is aosp not cm, and when i flashed supersu for the secondary, it bootlooped, also when I installed any cm based rom, it would not boot up (wouldn't go past the google logo and unlocked lock sign). The trick was to flash the kernel after going through with the installation , and cm booted up for me just fine.
[Nexus 6P Android Development] 500 Internal Server Error:
SuperSU not working is a known issue. As for the kernel issue, I use Stock 6.0.1 as the primary and CM 13 nightly as the secondary and I haven't seen this.
[Nexus 6P Android Development] 500 Internal Server Error:
Shouldn't the Gapps log say "Changing mounts to ROM DU_Angler_6.0.1" instead? It seems that you're trying to flash the Gapps package as a separate ROM; try tapping the ROM in the MultiROM view, then select Flash Zip; that will flash the zip in the existing ROM.
[Nexus 6P Android Development] dsmitty166:
SuperSu 2.52 is the only one that appears to successfully install on secondary
[Nexus 6P Android Development] galza:
Whats thw thing with usb support? I have a usb otg type c with my backup roms.after i flash multirom would i be able to restore roms to primary or secondary? Or in the modified recovery i cant mount any usb otg? Glad to hear answers guys...i think i will wait for usb support because i put all my rom setups and stuff on my usb and not in internal storage
[Nexus 6P Android Development] dsmitty166:
This is how I did it initially. However, I tried again later and it worked via the same method. So I might have had some personal issues during that time :)
[Nexus 6P Android Development] andythesk8r:
Just a quick question. Do I have to flash the recovery with fastboot? Just dont feel like turning on the computer if I dont have to.
[Nexus 6P Android Development] Swamphound:
No you can flash the IMG in TWRP then reboot recovery.
[Nexus 6P Android Development] andythesk8r:
Thats what i thought. I remember doing the same thing back in the s4 days but didnt know if anything had changed or if this phone was By different. thanks for the quick response.
[Nexus 6P Android Development] 500 Internal Server Error:
I was going to try to write a guide, then I realized that you're probably better at writing guides than than I am, so here's some info about running kexec from the command line:

kexec-hardboot patch

Kexec-hardboot patch is a modification to a kernel that allows it to boot other kernels by putting the new kernel in memory, doing a reboot (hence the "hardboot" part), and jumping to the new kernel. NPJohnson has a great explanation of how it works here.

Doing a hardboot manually on an arm64 device:

1) Get a kexec-tools-arm64 from your device's prebuilt MultiROM zip, or build kexec-tools-arm64 from your device's Multirom source. (Currently kexec-tools-arm64 has hardcoded offsets, so must be built for each device individually. In the future this restriction will be removed and I'll post a precompiled kexec-tools)

To build kexec-tools-arm64:

- Setup a tree to build MultiROM for your device. See https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM. You will need the device tree and multirom source specific to your device.

- run `make multirom` to build kexec-tools-arm64.

- the compiled kexec binary is located at out/target/product/angler/system/xbin/mrom_kexec_static.

- Use adb to transfer that file to your device as kexec.

2) Prepare the kernel Image and ramdisk to hardboot. I recommend using a recovery image. If you've got a boot.img, follow NPJohnson's guide to split it into a kernel zImage and ramdisk.

Use adb to transfer the zImage and initramfs.cpio.gz to your device.

3) the command to actually run the kexec is pretty much the same

su
cd /sdcard/PathToYourFolder/
kexec -l --load-hardboot --ramdisk initramfs.cpio.gz zImage.dtb

To run the new kernel

kexec -e

My own script for testing kexec is

#!/bin/bash
echo "pushing"
adb push swag.gz /
adb push system/xbin/mrom_kexec_static /
adb push ramdisk-recovery.img /
adb shell /mrom_kexec_static -l --load-hardboot --mem-min=4 --reuse-cmdline --ramdisk /ramdisk-recovery.img /swag.gz
echo "waiting"
read
echo "execing"
adb shell /mrom_kexec_static -e

where my kernel is named swag.gz and my ramdisk is named ramdisk-recovery.img.

Thanks - compiled and uploaded. I haven't tested this though.
[Nexus 6P Android Development] DJBhardwaj:
If MultiROM installer is working, the uninstaller will definitely work. Thanks for uploading, though the least amount of people will use it :highfive:
[Nexus 6P Android Development] npjohnson:
Can, and will do! Should have it up this weekend.
[Nexus 6P Android Development] PCWright86:
Franco kernel now has support for multirom...
[Nexus 6P Android Development] TheStrix:
How about adding dtb.img support for arm64 devices as [MENTION=3418703]Tasssadar[/MENTION] did it here for arm devices?

Other arm64 have dtb.img and zImage separately. So would be good for those devices :)
[Nexus 6P Android Development] npjohnson:
Okay, lets clarify this right now. MultiROM DID NOT. Brick your 6P.

If you can boot to bootloader, and are still unlocked, you aren't bricked, and if you can't boot to bootloader, it isn't MultiROM's fault, just a sad coincidental hardware failure.

MultiROM touches nothing but the boot image. It doesn't modify any part or function of the bootloader, making a brick impossible.

Did you flash a bootloader while in fastboot, or do anything with dd before the incident in question?
[Nexus 6P Android Development] skorux:
No, I didn't flash a bootloader while in fastboot. Never did anything with dd. Just added a secondary ROM and restarted my phone when completed to get... nothing. No on-screen feedback, no vibration, only "Unknown Device" appearing in my Device Manager on Windows. Nothing shows up. The only thing I had used 'new' when flashing was MultiROM, which spectacularly screwed my device.
[Nexus 6P Android Development] kiamo:
Installed Multirom Manager from play store

Installed multirom automatically

Tried to install Android-N [NPD35K-ANGLER] from androidfilehost

ERROR 7

Rebooted the phone. Failed to boot primary rom.

Tried to boot into recovery. Recovery wont boot. Sits at MultiROM recovery splash screen.

Decided to flash normal TWRP recovery, plugged into pc, device completely undetected.

Tried all my USB ports. Undetected

Rebooted. Undetected.

Uninstalled all android drivers +reboot. Undetected.

Installed Google USB device drivers. Undetected

Windows does not notice anything has been plugged in whatsoever. I guess tomorrow I'll try plugging it into someone elses computer.

Advice greatly appreciated. I'd rather not need to buy a new phone. :(

PS: I realize I was a sleepy lazy careless tool and tried to flash a vendor image instead of an actual rom. :/
[Nexus 6P Android Development] npjohnson:
Ah. I see the problem. Which partition did you flash the vendor image to?
[Nexus 6P Android Development] npjohnson:
Well, MultiROM doesn't touch anything below the boot image, so, if you hold all buttons, for 30 seconds, you should be able to boot bootloader, and flash the factory image.

You aren't bricked, unless you flashed a bad bootloader.

What ROM did you flash? And what ROM was your Primary?
[Nexus 6P Android Development] skorux:
I was flashing and using PureNexus (intended for a "work" and "home" mode).

Again, I could be holding these buttons all day. I don't get a response from the device. I'll hear connection and disconnection sounds in Windows, but flashall doesn't recognize the device and the phone has NOTHING on it. (No Google logo, no android logo, no anything)
[Nexus 6P Android Development] kiamo:
I don't really know. Just the default add secondary rom location. :S

---------- Post added at 08:50 AM ---------- Previous post was at 08:01 AM ----------

The system failing to boot is low on my worry list. If I can get the USB interface working again then I can repair it all with fastboot. After sleeping for a while, I'm thinking I might need to replace the USB daughterboard thing. :/
[Nexus 6P Android Development] npjohnson:
Hold the buttons all down for 30 seconds. See if you can get the bootloader screen.
[Nexus 6P Android Development] npjohnson:
So, any number of hardware things could have happened. But, you can look at the code. MultiROM didn't cause this, as, MultiROM is physically incapable of touching anything that could cause your device to brick in this way.

I'm extremely sorry to hear about your devices apparent problem. Contact Google. If you tell them it stopped booting, they'll likely RMA it for free.
[Nexus 6P Android Development] kiamo:
I can load the bootloader, however it is unable to connect with my computer and thus fastboot does not work. It is not even listed in device manager as unknown. The computer in no way recognizes the device.

I suspect this is an older problem that I have just now been forced to take notice off. As far as I can tell, without fastboot the device is totally bricked. T_T
[Nexus 6P Android Development] npjohnson:
Yeah. If it gets to fastboot, but isn't even Revgnized in device manager, it's probably a USB connection issue (possibly the USB Daughter board as you mentioned earlier). Good to hear it isn't bricked at least!
[Nexus 6P Android Development] jnewberry1:
Viper works fine. Remember if you flash a new vendor if swapping from M to N or whatever you have to delete system/vendor/etc/audio_effects.conf file and install Viper again. Proof its working....
[Nexus 6P Android Development] marbertshere:
Do you guys know if the DU kernel is MultiRom compatible? They're not really fans of mods there.
[Nexus 6P Android Development] phanitej:
One way is to look at their GIT. The second way (my noob way as im lazy to go through the git logs) is to install multirom app and open it. It would say if the kernel has the patch or not.
[Nexus 6P Android Development] AndrewM3:
can anybody confirm that my moto 360 will stay connected when I switch roms between multirom. As of now when I flash a new rom I have to factory reset my moto 360.
[Nexus 6P Android Development] npjohnson:
I won't stay connected, and that is not a bug, but the way that android wear works.
[Nexus 6P Android Development] SuperJuDicousCat:
Hei friend,how to make the N preview 4 or 5 secondary?The bootloader is different from MM...
[Nexus 6P Android Development] jnewberry1:
Just either leave the MM bootloader or flash N. Both bootkoaders make no difference. Just make sure the one you choose is unencrypted.
[Nexus 6P Android Development] SuperJuDicousCat:
I'll try it after backup.. thx
[Nexus 6P Android Development] alahkel:
Hi, thank you for porting MultiRom to our beloved device.

I'm experiencing a weird thing.

I installed the multirom manager app through the play store, installed multirom recovery, multirom ecc all automatically via app.

Basically I want to dual boot between Android N dp5 and a MM rom (DU right now).

I'm not new with rom flashing and multirom (had it on my old nexus 7, nexus 5 and others).

At first I was having vendor image problems.

I flashed N as primary and DU as secondary, flashed a multirom capable kernel (ex kernel) on primary and proper vendor image for each rom each time I was switching between N and MM.

The problem was that the secondary rom (flashed with correct MM vendor image, it was DU rom) was booting but couldn't even connect to sensors like gyroscope etc.

Same issue you would have when you don't flash the correct vendor, but I actually did. Also tried with older MM vendor images, same result, while the N rom had the sensors working pretty good.

Now it started to just fail flashing Roms.

So multirom twrp says failed, but then I can switch to secondary rom which, of course, isn't booting.

Any advices? Thank you!
[Nexus 6P Android Development] KLit75:
Due to some battery issues &other glitches i cant really diagnose Id like to start over. Think this means flashing system images in fastboot. Is it safe to do that with multirom twrp installed?

BTW--eventhough Im currently just running one rom (pure nexus) I still like having the option of adding a secondary so Ill be returning.

Just a clarification-i CAN flash factory images from here right? Thanks
[Nexus 6P Android Development] gqukyo:
If you can boot into fast boot, you can always flash back the stock images. If you want to keep your data then don't use the flash all bat file and skip the format userdata command.
[Nexus 6P Android Development] KLit75:
Thanks. I never use the flash all but monthly i flash vendor and bootloader, radio if applicable. So that being said all I need to do is flash the img file and Ill be back to unrooted clean slate ( minus internal storage)? This will also give me a stock recovery?
[Nexus 6P Android Development] gqukyo:
To get back the stock recovery, you have to flash the recovery.
[Nexus 6P Android Development] DJBhardwaj:
Exactly. Just skip userdata, and everything else go back stock. :good:
[Nexus 6P Android Development] kjcmusic17:
Another MM/N question. I understand that each time I switch between a MM and an N rom/build, I need to flash the appropriate vendor img. Am I also correct in my understanding that the Nougat vendor img doesn't play nice with MR recovery/TWRP recovery? I need to flash back to MM to get into recovery. Is there a way I can flash those .img's without fastboot? I know I can flash .img's from MR/TWRP, but if coming from Nougat, and I can't get into recovery then that puts me back to using fastboot to do so. Anyone know of a way around this so that I can swap between the two on the fly without fastboot flashing the vendor .img every time? So far I haven't found any options.
[Nexus 6P Android Development] DJBhardwaj:
Vendor image has nothing to do with the recovery. Okay, so the best way here is to have your device decrypted. Once it is, you will easily be able to access TWRP and flash appropriate vendor before booting into MM or N.
[Nexus 6P Android Development] pringled:
Hey guys, sorry if this has already been asked but I didn't see anything when I searched.

Anyway, if I flash a ROM that force encrypts as my secondary will it force encrypt my whole system like it would as my primary?
[Nexus 6P Android Development] rammy1991:
i am using DP5 as primary rom with latest experimental x kernel, and pure nexus MM as my secondary rom with experimental x kernel, but my secondary rom can't connect to camera, this is still not fixed? as it used to be the case for DP3 also, that's why i went back to single rom setup, now again this issue :( please someone help me.
[Nexus 6P Android Development] npjohnson:
Please read through the thread. This has been answered many times. It isn't an MR issue, its a user issue.

You need to flash the corresponding MM vendor to boot the MM ROM, vice-versa for the N Preview.
[Nexus 6P Android Development] rammy1991:
yes i am aware of that, i do flash corresponding vendor everytime i switch roms, but it's still the issue that i can't get camera work on secondary rom, weather it be MM or N DPs, i asked this earlier also here few months back, but didn't get a solution, couple of other users asked too.
[Nexus 6P Android Development] npjohnson:
Are you sure you are using the right vendor? Also, are you using a custom kernel on the MM ROM? I'm using NP5 right now on primary, and multiple MM ROMs (DU, PN, AOSiP, AOSP, CM). Not one of them has this issue.
[Nexus 6P Android Development] horeabeni:
Here is my current situation.

I have installed N5 preview to get back to stock, including userdata format.

Then I installed elementalx kernel to allow MR. After that I added mr-twrp and proceeded to adding a secondary ROM (pure nexus).

Lastly I flashed the corresponding vendor IMG and booted PN up. The problem I had was that no sensors were available (used an app from PlayStore to check).

Rebooted to recovery, flashed N vendor and booted up N5 and everything was OK.

Went back to recovery, swapped Primary with Secondary ROM. Booted up N5 (this time as secondary) and there were no sensors detected.

Went back to recovery, flashed the latest marshmallow vendor and booted up PN , and all sensors were running just fine.

I have not yet tried another secondary ROM that is using android 6.0.1 to see if that works, but in my case so far I cannot get N5 & PN to play along.

In any case, I still love the work that is being put into the MR project, so keep it up.
[Nexus 6P Android Development] rammy1991:
yes i am sure that i am using right vendor, and i am using custom kernel (Experimental X) on NP5, and on my secondary too (Pure Nexus MM). i am finding those members now who had this same problem, going through the thread.
[Nexus 6P Android Development] Xenotrumpet:
I thought I was the only one with this issue. None of the sensors seemed to work on MultiROM on any secondary ROM. It's one of the reasons why I uninstalled.
[Nexus 6P Android Development] pospower:
Installed MR all fine put pure Nexus on secondary.

Put N v5 preview on main.

Boots up fine all well with N

Lost root. So I can't add kernel or change Roms etc.

What to do.
[Nexus 6P Android Development] opz187:
I too have the same issue regarding the camera, can't connect to camera on any secondary. nd5 primary, correct vendors all around. has happened fora while. thought it was just me
[Nexus 6P Android Development] pospower:
Anybody?

Do I need to wipe.
[Nexus 6P Android Development] iluvamk:
Can u get back into twrp? If so flash SU from there.
[Nexus 6P Android Development] pospower:
No...it freezes at the recovery screen.

I tried reflagging the mutilrom image. I I also thought maybe I needed the special boot loader image for n I saw around and tried that. No go. Then I had no recovery.

Then I did multi image aging back to having frozen recovery screen. So recovery is loaded. I even have the duel boot screen pop up. But can't boot into secondary due to non something kernel. I'm not new just to multi rom.
[Nexus 6P Android Development] iluvamk:
Try using Wugfreshs toolbox. . . http://xdaforums.com/showthread.php?t=3258493. Sounds like u will have to start from scratch. Personally I would try reflashing regular twrp from toolbox and see if u can get to recovery from there. Better do some reading first it sounds like if your going to mess with Multirom.
[Nexus 6P Android Development] dirtyreturn:
Why not delete the secondary rom and try again?

Do you have both vendor images ready to flash via fastboot when switching?
[Nexus 6P Android Development] pospower:
Is it possible without recovery? Freezes up at recovery screen.
[Nexus 6P Android Development] KLit75:
So youre able to boot to primary rom? And you have MR Manager installed? If so u can just delete secondary rom from inside the app.
[Nexus 6P Android Development] dirtyreturn:
Maybe you could try to reflash the recovery with the fastboot command with a pc.

For you reference - http://xdaforums.com/showthread.php?t=3206928

fastboot flash recovery recovery.img rebame the twrp recovery to 'recovery' and place it in the adb platform tools folder (one with adb) if using windows.
[Nexus 6P Android Development] PieOfJustice:
Installed via APK and boots fine but after installing secondary ROMs it just boots to a black screen for all ROMs. It will boot to internal ROM fine. Was I supposed to go complete stock and then go MultiROM instead of installing it to my current ROM? I am running CandySix on main.
[Nexus 6P Android Development] KLit75:
Are u certain its booting to a black screen? How long did you let it stay black before you intervened?

It was a couple of months back but I remember a long delay before the boot logo appeared (cant recall how long). And when you're there its impossible to tell if its just going through a normal boot process or if the phone shutdown.
[Nexus 6P Android Development] opz187:
if i were you I'd probably load your ROM, multi-rom, SuperSU etc onto your CPU and format your userdata via fastboot to decrypt, then flash twrp right after you format, then fastboot whatever modified boot.img for dp5 and go from there. you should be able to access the multi-rom twrp after decrypting and flashing the modified boot (make sure boot.img is for Android N if that's your primary and that force encryption is disabled in kernel)

---------- Post added at 01:22 PM ---------- Previous post was at 01:18 PM ----------

oh and obviously make sure kernel has the kexec-hardboot patch, most do but if you want to play it safe use flars elementalx kernel or the stock modified one in the general section

---------- Post added at 01:26 PM ---------- Previous post was at 01:22 PM ----------

oops sorry I think I quoted the wrong post, i didnt even read that you're on candy. it might be a vendor issue. make sure you've flashing the correct vendor if you need to when booting secondary and whatnot. maybe try flashing Kylo kernel or elementalx and redo multi-rom install
[Nexus 6P Android Development] KLit75:
I never tried the dev preview because it seemed like a hassle and I like xposed anyway but I would like to try the official update if its possible to run it as a secondary rom. If anyone else is doing this and doesn't mind sharing a working method please let me know.
[Nexus 6P Android Development] shadowstep:
[MENTION=5848265]npjohnson[/MENTION] TWRP has been bumped up to version 3.0.2-1 for the Nexus 6P. Just putting it here for your notice so that whenever you have the time, you can update the MultiROM Recovery base.
[Nexus 6P Android Development] sev7en:
Good morning,

did we have the support for Android N?

Cheers
[Nexus 6P Android Development] dnv_aps:
thanks a lot

with you post ,i have try to port the arm64 kexec hardboot support ,but failed ..

i make need more try .
[Nexus 6P Android Development] DJBhardwaj:
Yes. It is same as you would have done with the N preview. :good:
[Nexus 6P Android Development] kiamo:
Finally got around to replacing the daughterboard. Same problem. Must be a mother board issue. T_T
[Nexus 6P Android Development] :
I can confirm: it's not working in N. Flashed ElementalX kernel for N but at reboot MultiRom stays in boot logo. Waited more than 10 minutes and nothing. Dev, please review MultiRom. THANKS for you work!
[Nexus 6P Android Development] WisdomWolf:
I went ahead and took a look at the source code this weekend to see how difficult it would be to merge the changes into MultiROM. I quickly discovered that I was in over my head, but it looks like some patches were made to a test branch recently, so I have my fingers crossed that that means we'll see an update soon.
[Nexus 6P Android Development] sev7en:
Yes, thanks but it didn't... which one is the correct way to install it?
[Nexus 6P Android Development] gasroca:
The only way I managed to get it working on N was with the GoogyMax kernel.. ElementalX doesn't boot

Actually ElementalX boots up in the end but when you go to add secondary rom it says main rom doesn't have Multirom patch

I've got stock N as main rom and RR as secondary but every time I change rom I have to reflash vendor of course..
[Nexus 6P Android Development] Nochis:
When you have N on primary and M on secondary, does your sensors work on secondary?.
[Nexus 6P Android Development] gasroca:
For now, yep working :)
[Nexus 6P Android Development] Nochis:
Thanks. It's weird I got N on primary with ex kernel all working fine except sensors on secondary but only M roms. I going to give a try the kernel you are using.
[Nexus 6P Android Development] shadowstep:
[MENTION=5848265]npjohnson[/MENTION] TWRP has been been updated to 3.0.2-2. Just an FYI post. Whenever you have the time, you can update the base for MultiROM Recovery. :)

Also, if anyone is using version 3.0.2-1 of the regular TWRP (not the MultiROM one, which is on 3.0.2-0), do note it has a

fatal bug

. Read about it here!
[Nexus 6P Android Development] npjohnson:
The reason I've been quite on this front was I noticied that bug right as it was being discovered. I'll be updating MR-TWRP once this is fixed.