yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] magicfajita:
I feel like this is a stupid question, but if I install a ROM to slot a, and then boot to slot b, will I have stock Android on slot b and the rom on slot a?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Hey just flashed Rom and it's awesome, I'm getting the IO error when trying to install Viper. Any idea what's causing it, busy box installed and rebooted, same issue.

Edit: All good now sorry! Feels good to be rooted and Rom'd again, thanks for the work! Wanted to ask if ur emoji mod will work in this Rom.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Emoji will work
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Quick question regarding Viper, I noticed in root explorer there isn't a Viper folder in SD card. Are we not able to use the extras zip so do we can choose profiles and such?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
There is no extras zip with Pixel. But just create and place the folders and files manually
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SwayART:
I have the Verizon pixel, but I am using tmobile. Should I use the regular rom or the one for Verizon?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
It really doesn't matter. I've used all versions on ATT and had no issues. Google fi also, which uses sprint and T-Mobile networks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
This ROM never boots up for me. Stays on the boot animation forever. First boot supposed to take a very long time?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I suggest you do some reading in this thread.

Also I need information to help you. If it's on the boot animation forever it usually means it's trying to encrypt your data. Make sure you are using latest twrp and supersu sr4.

Check you boot slot and flash to the correct slot.

That's all I have without knowing your process of flashing, what firmware version you were on previously, google vs Verizon.

Did you flash a kernel.. if you did, did you flash SuperSU afterward.

Did you flash vendor before the rom? Bootloader and radio?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
Thanks for reply. I think I need to start over. I think I'm getting hung up on the duel slots. I think I'm flashing to one and booting another or something.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Can I flash 1.0.2 to my non active slot and be able to boot stock and this ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I second this question...seeing as I have already bricked one pixel, I won't be the test subject for this but if it can be done I would love to know!

And if someone successfully does this, please describe all steps used to do it and if you had to flash the bootloader to both slots
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
How did you brick it?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Boot into the wrong slot... The phone sits at a black screen no matter what I do
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jimbop98:
I also want to know about this. I bricked my device also and had to use fastboot to reload a stock image. Thankfully I lost nothing important. I have made sure not to have anything important on my phone until I get it fully set up the way I want it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
When I said brick, I meant hard bricked! The phone won't turn on... No bootloader, no recovery, no anything... Whomever undertakes this task is a brave soul
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jimbop98:
Ouch. That sucks. Fastboot would not even connect to it then huh?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Nope... Nothing works on it
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JCBiznatch:
No that's rough.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
So how did you do that? You must've flashed the wrong bootloader or something? What were you doing when it bricked?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I booted into slot a when slot b was active

Slot a only had system_other flashed to it and I wanted to see what was on it...it's like it didn't have a bootloader or anything on it
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Did you send the phone back or do you still have it?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Just sent it off today...no button combination would work...just stayed at a black screen no matter what I dif
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
They should be able to fix it. There is a method of getting the correct img files onto the device using Linux without fastboot, in case they send it back to you unfixed.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I got a new one at Verizon for 1/2 price and getting a refund on the Google one

Already unlocked my bootloader and have a few things going on with twrp and root, so I'm good for the moment...

I'd like to flash weta to slot a and keep my current setup on slot b but I'm really nervous to try and change boot slots again
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I've changed my slots but nothing bad happened just would not boot on the other slot. Shouldn't brick it.... I don't know what happens to your device.

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

These guys are doing it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I don't think I had the bootloader flashed to slot a on my other phone...I have my phone dual booting perfectly now
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I'm not really sure where you went wrong last time, but I've never touched or flashed the system_other.img. just make extra sure you download the Marlin firmware and not the sailfish. Did you maybe flash boot.img to bootloader by accident?

I've been pretty reckless with changing slots and flashing this and that and haven't bricked yet. The other thing that can brick is locking the bootloader while having a modified system. Not sure how this can happen without realizing it though. Unless you are using some kind of tool that has a bug
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I have the sailfish, I believe I just flashed wrong and forgot to flash a bootloader to slot a before I booted...I'm successfully dual booting now and I'm stoked about it!!! Thanks for any and all help!!!

Btw, have you been using fastboot to change boot slots or twrp?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I've been using twrp. I've found though that you want to change it, then bit into bootloader to double check it changed. If it didn't, boot back into twrp and try again, then check in bootloader again. Usually works the second time.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Alright...thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Do you have TWRP flashed to boota and bootb? You are able to boot both stock and WETA?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I have yet to try weta...for the moment I have stock modded with center clock , root, and fk kernel and the other slot is stock, no mods, no root, and elemental x kernel to pass safety net...seems to work rather seamlessly
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Sweet! Just to ask again did you flash TWRP on both sides to be able to switch partitions easier?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Twrp automatical flashes on both partitions.

If you just fastboot boot twrp.img then twrp is temporary

But if you flash the twrp.zip after boot twrp.img, then twrp flashes to both slots
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Didn't know it flashed both partitions. Cool.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
This is an interesting idea. If I currently have TWRP, root via flashing SuperSU, and elemental on Slot A and wanted to be able to boot stock/safety net, does the following sound correct:

/fastboot flash system_b system.img

/fastboot flash boot_b boot.img

And then I should be able to boot from slot b via recovery? If I originally flashed SuperSU from TWRP, do I need to reflash stock boot.img onto Slot B (/fastboot flash boot_b boot.img)?

EDIT: currently, if I boot Slot B, I just get bootloops...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
I'll assume a is you active slot since b is giving you bootloop...in the bootloader use these commands for your boot looped slot

fastboot flash --slot _b bootloader (bootloader.img)

fastboot flash --slot _b radio (radio.img)

fastboot flash --slot _b vendor (vendor.img)

fastboot flash --slot _b system (system.img)

That will flash slot_b without making any changes to slot_a...if you already have twrp, then don't flash the boot.img as it's already there and has twrp on both slots
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
Is the boot_b unrooted then if I flashed SuperSU via TWRP? Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
If you want to pass safety net, then one slot can't have root...the slot without root must have ElementalX kernel flashed to it because it has a patch the makes safety net work...so if your rooted slot is b, the slot_a must be uprooted with ElementalX kernel on it
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
Great thank you. Then I assume you boot into recovery, go to reboot, slot b, then flash elemental kernel to? or is there another way to flash elemental kernel to slot_b to bypass safetynet?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
System and vendor both have to be unmounted to change boot slots...and always reboot bootloader after changing slots to make sure it changed and then reboot recovery and flash
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
Got it. Unmount partitions, reboot-->slot b, reboot bootloader, load recovery, flash elemental kernel.

Thanks again!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Np...only rebooting bootloader to make sure it's booting in the slot you want
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ragzz03:
Does anyone know how to turn off the stock battery icon for this ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
In system UI tuner

Press and hold the settings cog in the notification pulldown

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] schweigster:
I successfully flashed this ROM on my Verizon Pixel along with twrp, root and elemental x kernel. However, on boot Google text to speech crashes and I cannot open it in settings. I flashed vendor, bootloader and radio from OP before flashing ROM. Any suggestions? Thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
It will do that on full stock time to time...after your device is set up, it should stop
[Google Pixel ROMs, Kernels, Recoveries, & Other De] schweigster:
I can't use text to speech at all, after reboot or otherwise. It immediately crashes when opened.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Well that's strange

Try wiping data and cache for the app...if that don't work, uninstall it's updates and open it to make sure it works...if it works update through the playstore
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
It needs to update. Go into play store and update it

ðŸŽ¸ --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
WETA 1.1 beta

Based off NPF26J

includes double tap to wake etc

No status bar mods at this stage - process broken

Navbar height included

Be sure to flash the new vendor.img BEFORE the rom!

Another thing.. the OTA originally was intended for the V version of firmwares. I'm not sure if any issues will arise from flashing this over an installation of an X firmware. I doubt it but you never know. If you need to flash radio or kernel then use the V imgs. vendor.img is special to the J firmware so you need to flash it.

Download Page

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
Flashed the new update - thank yoiu very much - I miss 3 minute but I figure you will work it out eventually - :) thanks for all you do though, rom works beautifully.

I wiped Cache/System and then flashed the Vendor Image followed by Flashing the ROM and all is working beautifully -

Thanks for Everything.

PS - when and if you are able to get 3 Minute Battery working, any chance you might consider adding 3 Minute Clock too? It would be a treat if you can pull it off. If not, no problem - rom works great as is.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] stompysan:
Dirty-flashed from the Verizon X build. No issues so far, and haven't gotten the update nag either. Great job as usual! Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
3minit click hasn't worked with nougat for a couple of months now. I'll check on it though

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
There is a guy who has 3Minit Clock working on S7Edge on Noguat (on the latest Beta 3 release from Samsung) - considering it is completely different phone I imagine that may have a lot to do with it - but I mention it only becuase it is working on NOUGAT (just not on the pIXEL as far as I can tell.

I cam PM you about the rom it is working on if it matters - but don't let that detract from my appreciation for everything you have done - WETA is awesome and it's great that we have at least one rom we can play with on the PIXEL. thanks for your efforts.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I have Roms for the 6p, 5x also and had to pull it out of the ROM. But I haven't tried again for ages. It could have been updated.

Samsung nougat is completely different to the pixel framework. Systemui is a completely different beast. Regardless, I'm still hoping all these mods will work on the December update, as decompiling of systemui is semi broken on the J build. Hoping apktool gets updated.

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tserv95:
I have extensive experience flashing roms but have problems flashing this on my Verizon Pixel. Yes bootloader is unlocked and I have TWRP installed properly. When I got it to finally flash I was getting an acore.android process kept crashing? Any reason for the cause of this? It's like when I tried doing a wipe of data it didn't actually wipe the data? Would you care to give me instructions I could try. I tried with both boot slots a, and b.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
Any chance we can get long press volume key to skip tracks?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
I have not had this issue but normally what I do when I get in situations like this is to simply start over from scratch - relflash the original image file from GOOGLE for your pixel - then boot into twrp - root -and then try to re-install the rom. It usually helps me get past whatever issue I was having.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I'm assuming you are talking about the 1.1beta?..

I can't recall if you were the same person who had this issue earlier, if not then at least someone else had the problem..

This J firmware was an OTA intended for the V firmware. So if you were previously on X make sure you flashed the supplied J vendor IMG. And you may need to wipe data. Hell you may need to flash right back to stock V then flash the rom if that all doesn't work.

To me, honestly. It's not worth jumping through hoops to get J. The double tap feature is intermittent. And there isn't much else there that's an improvement on V or X.

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChugJugThug:
Hey is anyone having issues with v4a driver not processing randomly? I found a weird fix by "uninstalling" the driver, but then after it reboots the driver is still installed and it's magically working again. Then it inevitably stops working a few hours later. I'm wondering if there is a permanent fix for this or if it's a known bug or something.

Running 1.1beta, rooted, with EX kernel.

Edit: drivers were working fine on 1.0.2, after I dirty flashed 1.1beta over it I started having the driver issues.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
In case anyone was wondering Mono navigation and headers working great ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
I had this occasionally happen if I opened Dolby .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tserv95:
On my Verizon Pixel I decided to use the Verizon build you made and that one works perfectly. I had one issue with The Camera crashing but all I did was uninstall the updates and reupdated it and it worked just fine.

---------- Post added at 03:04 AM ---------- Previous post was at 03:03 AM ----------

How did you get those mods man and that clock? I want it :D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Beautiful Widgets, MIUI HD clock ðŸ‘
[Google Pixel ROMs, Kernels, Recoveries, & Other De] gillim74:
i keep getting android.process.acore has stopped when flashing beta on vzw.problem solved had to clear contacts data.nope didnt fix it'
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ej_424:
Dirty flash (cleared cache) from stock and working great. Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Sorry but are you saying you fixed acore crash?

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
WETA 1.0.4

All rom zips, from now on, will be based off of the international/unlocked version of firmware.

This version is based off of NDE63V for instance. You can flash the radio from any version, but you need the V vendor img.

Added AdAway adblocking app

Added Busybox install to system

Added System tweak scripts, zipalign + sqlite

Added Walkman Music Player

Added V4A convolvers and profiles

Added Adblocking hosts file

Added Tethering hack (may work)

Added 1 Verizon apk to debloat

Download Page

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Post #3

Ive started adding some things to Post #3, these are going to be general fixes for things along the way. Some things are hard to pin down such as V4A driver issues. Those driver issues are not rom related, but are a quirk of V4A. I will say, people have more success with V4A 2.3.4.0, and people like the sound of the older drivers (including me). Hopefully newcomers will read this post...

Post #3

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Thanks for the update, is center clock working in this build?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] グリッチ:
I have center clock working from here I just followed directions and it worked perfectly, I haven't installed anything else yet.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I don't know if I overlooked a post or two but I wasn't aware it wasnt working.

Edit... No mods were working on the 1.1 beta. Hence the beta label. That was for the people wanting the double tap. But was pointless in the end.

ðŸŽ¸ --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Enlighten me why you needed to use that mod? Does center clock not work from the ROM zip?

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] gillim74:
No thought i did

---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------

Im new to this phone only got it yesterday alot different from my htc 10.my question is just so i understand.i flash the vendor image then the rom and then the verizon radio?or if i use it with at&t i dont have to worry about flashing radio? Its a verizon model.thanks for any help you can give me?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Gotcha that makes sense, thanks again!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Weird, just updated to new build and I get this update available? Google unlocked phone with Verizon as carrier.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
You have that because you have a Verizon sim in your phone

This is why I voted to have a build for the Google store phone and one for the Verizon phone...I just flashed the newest weta and I have that damn update notification that won't go away...and yes, auto update is off
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Yeah pretty irritating seeing that update notification and can't get rid of it.

Rom is running great though!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I've never had to flash a specific radio. Just try without flashing that and you should be fine.

Yes flash vendor IMG first. You can do this in twrp, go to install then select img button at the bottom to find the img.

Then flash ROM.

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Hmm. Dunno what that is. Might be a small radio update or something. If you want to turn update notifications off you can do that in dev settings

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Crap that would irritate. Is that even without debloating the Verizon apps? Also have you tried changing the build number in build.prop and vendor/build.prop? Change it to X and see if it still nags you

Edit.. let me make a quick flashable zip to change those entries. And maybe some other things. See if we can squash this issue

ðŸŽ¸ --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
I shouldn't be getting those because of root I thought?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
You'll get the notification regardless. It won't install though

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] gillim74:
Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Changing the /vendor/build.prop and /system_root/system/build.prop to show 63X instead of 63V fixes the issue...no more update notification
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
In system build.prop did you change build id on top and in the middle build.identification or just on top
[Google Pixel ROMs, Kernels, Recoveries, & Other De] gillim74:
Is there a way to remap the recents and back button
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Just changed the build fingerprint...it has 2 place in the /system_root/system/build.prop
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
cool, ill just swap out the build.prop in vendor and system in next update.

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Does Verizon function fine without the update though?

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] BakedTator:
Everything on my end was fine...I never noticed anything going wrong...I have 2 sims right now...1 with at&t and my Verizon sim...so I test around with both and all seems well with both on either firmware...just the update notification wouldn't go away until you suggested the edits...now everything is fine, no notification, no troubles out of the Verizon sim
[Google Pixel ROMs, Kernels, Recoveries, & Other De] グリッチ:
I just haven't downloaded the ROM at all, just needed that one individual mod and it's working great :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Ahhh, good stuff

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
WETA 1.0.5

Added Verizon sim option

- hopefully eliminates the update nag

Download Page

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
404 error
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Try again in a sec. Re uploading

Edit.. fixed

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] gillim74:
Anyway to remap the recents and back buttons?