yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
Oh sweet Jesus I am so sorry. That was not what I meant to say. I use gesture on Google keyboard. I should proofread what I post. That was suppose to say can't figure out how to"fast boot" install on the pixel. I can't get any info on flashing to a and b without doing a flash-all.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] robocuff:
To flash the boot.img file to slot a, you use "fastboot flash boot.img boot_a" (without the quotes).

To flash it to slot b, fastboot flash boot.img boot_b.

To flash the vendor image to a, fastboot flash vendor.img vendor_a

Slot b.... fastboot flash vendor.img vendor_b

And so on.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
I've tried doing everything step by step and nothing seems to stick. Minus the _a and b. I just had to go back to stock because after doing boot to root, super su, weta, I either get a boot loop or just going straight back to original recovery. I've been doing this for years. Having to relearn something that use to be simple is frustrating.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nednednerb:
Use TWRP RC1 and SuperSU 2.79 SR1

Boot to root doesn't work on "Q" firmware.

First off boot into stock and setup device so you can see home screen before flashing.

Fastboot boot twrp-rc1.img

Install twrp-RC1.zip

Reboot recovery

Flash SU 2.79 SR1.

Reboot to device, see home screen.

Return to recovery, install WETA.

Should take 20 min or less.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
ohhh. I might not have waited long enough before. i waited 10 minutes with the dots going back and forth. I'll update once complete

---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------

another observation. it looks like they put the 'recovery' partition in the boot according to cmd commands. is that correct?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Correct. Recovery is in the kernel img

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
that's freaky. why do things have to be so weird these days :(

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

should i install weta in both slot a and b?

---------- Post added at 09:53 PM ---------- Previous post was at 09:34 PM ----------

now i feel silly. Thank you very much for your patience with this. All this time, I just wasn't rebooting to system after flashing SU. Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
You can certainly flash to both slots. But if you know which slot you are on then there really isn't any point.

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
It seems as though no matter what I'm always on slot a. It's that normal?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nednednerb:
Installing WETA to slot b doesn't switch your bootloader to slot b. So yes I am pretty sure normal.

Also i do not recommend you do that switch without reading a lot about people bricking their phone cos slot b had no bootloader. It is an issue it seems. Don't switch before planning that it should work!

If it is a "no matter what" need for your phone to work unbricked......... Just use the slot that works successfully.

I wouldn't worry until or unless you want a dual ROM setup, which is NOT supported with ANY official dev support at this time.... Risk is yours.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Noticed that on one of my flash-all trips LOL my system switched to slot b on its own,,,good thing is that TWRP is fully working with restore and backups,,,but I am noticing that I am having some heat and battery drain issues on the exact same rom with no changes at all? Dont want to flash-all again but might have to if this heat and drain continues.

Read a couple pages on the TWRP thread that restoring system_img instead of system helped? I backed up everything except efs,,,,then restored only system, data, vendor, and boot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
You can flash weta 2.2.1 over 2.3 to eliminate drain issues

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
Heat and drain, experienced that too, unless I was doing absolutely nothing. Took 30 to drop to "not as hot". Had to go back. But this has been a learning experience. Stock affects it very little when setting up.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Thanks brother,,,I ended up flashing the same back up and using system_image and vendor_image instead of just system and vendor and all is fine now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
Finally gave it a shot! Working great so far (except that it removed the Google Keyboard initially, so I had to use the voice keyboard to search for Gboard on Google Play).

Thanks for a good ROM. I'll report back after a bit of use!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
The stock keyboard is still in the ROM. Not sure what happened to you there.

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
I love the features, but I can't do the battery drain (1800 mAh just to "Android System"), so I'll switch back to stock with the WETA Mod until it gets sorted out (or try a clean flash next week when I'm back at home with good internet).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mariano3113:
I did clean Flash (from Factory image NMF26Q)

Android Keyboard was present in Google Factory Image (had not yet updated to GBoard via store)

Flashing Weta 2.3 removed virtual Keyboard (Might be a Gapps issue)

In regards to Battery Drain and slight heat...This was not present in 2.2.1

I will be Flashing back to previous WETA as some others have done.

Side note (Not ROM related):

Spoiler content hidden.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
This is such a known issue, and it's been mentioned to just use 2.2.1 Until I take time away from family to update the OP, 2.3 is a step to slimming down the ROM zip. It has one qmi crash that is invisible but visible as battery drain.

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Don't take time away from your family, your kids will never get it back.

(PS: Why don't some folks read? Rrrrr!)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
WPSA Rom development

Development on WETA Rom for pixel devices has halted as of right now for a few reasons. One being I've decided to focus on a simple aroma mod installer, I'm seeing a lot of pointlessness in making a complete ROM at this point of time, as the best results arise from flashing to a stock base anyway. What is the point of flashing again in TWRP...

Two.. my wife is preggers, so time will diminish.

Three.. the pixel is finally starting to see some progress in the AOSP rom circles. This is great news, and I feel there will be other devs moving into these forums soon.

I will still update the system UI mods whenever there is a new base update. Just to keep things working. Unless someone else comes in and starts doing exactly the same thing. It's important to have some development, but pointless to have duplicate mods. I only want to give people options and don't want to abandon the device just yet.

Also... I am here for any questions if anybody feels the need to dive into modding, I'm not going to teach you the basics but there are quirks with this device that I'm happy to share.

Also, I'm not disappearing. Just not making big gigabyte zip files anymore

Thanks

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Well, [MENTION=4553200]Mentalmuso[/MENTION], thanks for having been the first for these Pixels. I'm still running 221, with long battery life and snappy although I reduced clock speed to 950 Mhz. I like this ROM for the removal of the nav buttons. I also appreciate that it only takes up one slot. I've been following your convo with Superr Kitchen, so I know how hard you've been trying to get 23 going. Thanks for that effort.

Enjoy your family!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] b00ster23:
Thanks for all of the hard work! Congratulations on expanding your family.

I believe you're making the smart move here. The versatility of the Google stock image, IMO, really negates additional STOCK image creation (at this point.) The logical approach of developing a MOD that adds the topping to the cake seems to make the most sense to me as well. As long as you can parallel updates and your mods to play nice together, this streamline effort will be a great addition the community.

Good Luck!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] skawtnyc:
Very much looking forward to this. I really like your work, and prefer a stock ROM with mods. I can imagine how much more difficult it is to do an entire ROM.

If I may, I'd like to request a small AM/PM next to the clock (70% height) and the ability to select a color for the clock and icons on the status bar (except for 3minit). [MENTION=5346465]Tulsadiver[/MENTION] has been doing this for Nougat on Nexus and Pixel devices.

Thanks again for all your work. I'm glad I donated. :D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I've always been meaning to look into this.

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Another thank you for your hard work, good luck in your next adventure.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Huge congrats on the baby!! Thank you for the roms and hope you do keep the mods going,,,love 3 minit battery mods!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Thanks for getting this kicked off for the Pixel, looking forward to future mods. Congrats on your new blessing!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] davidisflash:
Congrats on the news about having a baby! Best wishes to you and your family. Thanks for your contributions here.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
Thx for all your work and congrat's on the baby [MENTION=4553200]Mentalmuso[/MENTION]. Hope to see you continue developing on future phones.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
Comgrats on the news of the "little one". Hope he/she is happy and healthy...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
There's a test zip for WETA Mod in the telegram channel for anyone interested. It's based off U firmware

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

This ROMs mods have been combined into the WETA Mod thread here - https://xdaforums.com/pixel/themes/mod-weta-ui-mods-t3491159

No more development on a full rom is planned. I will updated mods for each firmware release.

--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sanogueralorenzo:
I ended up discovering this ROM due to Pixel's crackling issues when playing some audio at high volumes.

It should happen on all devices if you try out the perfect piano app for ex. I experienced this on whatsapp audios and also on some youtube videos which is quite annoying.

https://www.youtube.com/watch?v=A9ttOOPBsAU

Apparently it is fixed using viper4android or this ROM but it requires root and I use Android Pay a lot now a days.

From my understanding this ROM has aroma and installs viper4android, but in order to have it installed you have to be root right?

Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
I use magisk for root and I have viper running great and also I use google pay all the time.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sanogueralorenzo:
I didn't know magisk could trick Android Pay!

Are these instructions correct?

Flash Custom Rom

Download the latest Magisk zip file

Reboot to TWRP and Flash Magisk zip

Reboot. Update the stub Magisk Manager to the latest from Play Store

Reboot to TWRP again and flash the latest mod

Will I be able to install AdAway? Do you have SuperSu installed with magisk and Android Pay still isn't triggered?

Thank you (:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
you boot into twrp install the latest magisk ( 1.6 I believe ) then flash twrp then reboot. if you don't flash twrp u will lose it. you don't need to have SuperSu installed at all. I would suggest if you do reflash your rom so it will wipe away supersu.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sanogueralorenzo:
Edit: Link for Pixel is an edited 11.6: https://drive.google.com/file/d/0B1xZ4VKT4JKZZ2RYQ3NwQlhRUlU/view

Now I have to figure out how to adblock and viper4android, they are just modules and you install them from the manager?

Thank you again for your help (:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] LEGOMYEGGO:
can't find the rom

on mega it brings me to note 9 roms
[Google Pixel ROMs, Kernels, Recoveries, & Other De] LEGOMYEGGO:
can you help me im getting a bootloop after installing successfully its stuck on the dots screen
[Google Pixel ROMs, Kernels, Recoveries, & Other De] LEGOMYEGGO:
Its not working

all i se is the loading screen it does not want to boot fully what am i doing wrong
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
This rom is dead for pixel

[emoji450]--->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JohnnyMcG:
oh i see (said the blind man). so switching to a works so long as you flash supersu to that assignment. :) cool . thanks for the help. EDIT( just switching to a and flashing supersu doesnt work)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] EvertorN:
It just says NDE63V
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jayfried:
Funny how much you miss things like this on stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Thanks for this ROM, working good here. ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
I have twrp installed - went thru the process described by the TWRP Thread and had Super SU working as well. I attempted to flash this rom and failed - read about needing to flash to "A" - and have tried several times but it never seems to work. I confirm after flashing that it apears to be flashed on A - (I changed it first in TWRP and then went to the same place to confirm it was still selected - it was - flashed Super SU - rebooted - bootlooped a few times and finally rebooted stock. Did the same thing with a custom kernel - seems like I am flashng on A - but booting on B and I am not sure what to do to make this work.

It is either someting I did or didn't do - or it is the result of TWRP being in beta and still buggy - but others have had success so I am confused about what I may be doing wrong.

Is there anyone here who when they checked initially the partician was set on B - but then succesfully changed it to A - flashed the rom and Supersu and booted up correctly? If so - can you give me your step by step actions so I can see if I am missing someting?

I am also curious why some people seem to be set on A by default - while others are set on B - ? (not that it matters - but it seems like no matter what I flash on A - when I try to boot up it won't so it switches to B - that is just a guess but it seems like that is what is happening.

Anyone ? (sorry if I sound like a noob - I have been around for years - but this is really my first go with a NON-Samsung phone and I am learning ..... your help is appreciated.)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GeekMcLeod:
I haven't had this issue but on the last page someone posted
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
I did see that post but over looked the step where he flaashed the full stock image after changing the partician to a - I did everything else except that step - so I will start over and I will give that a try -

thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Artnig:
So I finally got this ROM working. However, upon reboot I always get an error pop up saying "Android System: There is a problem with the internal settings of your device. Please contact device manufacturer" but the phone works fine
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aoe2king1:
I am on Verizon service with a Google bought Pixel and used the NDE63V image and I was having the same issue, I believe it was when I installed the update through system updates in Pixel settings (16.1 mb file that would switch the phone from NDE63V to NDE63X) it would cause the phone to switch from partition a to b the next time I booted into bootloader. I ended up downloading the full image of NDE63X and it remained on partition a after each reboot to bootloader. I am now running Weta 1.0.1 with ElementalX kernel without any issues.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Where did u download the full NDE63X img from
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aoe2king1:
https://developers.google.com/android/images

Fixed the link, accidentally put the OTA update instead of the full image.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Artnig:
I managed to get rid of this by reflashing stock and going through all steps again. But now I am having an error with V4A drivers not installing. Also I get an "unmont of /vendor failed" when I would flash the ROM. Any ideas? i get an error "Driver Install Failed: I/O error, please reboot and try again"

OK: Started from scratch once again and I'm finally all good to go. Thank you for the ROM friend
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
You have the wrong vendor
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Artnig:
Had to flash vendor a few times in order to get it working but all is well now
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
V4a needs some entries in the vendor partition. So if there was an error it probably links up with that vendor error you had
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
I had trouble when I originaly attempted to flash this rom several times and could not get it work - I was flashing but the flash didnt stick and nothing changed.

someone (sorry I forget who) posted their steps a few pages back and following them to a T they worked beautifully ....- these are not my solution but rather one I read a few pages back -

Rom has to flash on partician a - for some this isnt an issue - a seems to be their default partician for flashing - it has been an issue for me and a few others flashing seems to default to partician b - but I found you cant just change this and then expect it to work if you have already flashed on Partician B - you have to do a few things first to set A as the default partician.

I won't try to give a tutorial here - there is one already a few pages back and if you are having problems, I beleive it should help you a s much as it did me.

The challenges of flashing on a beta TWRP with a new device - are well, interesting to say the least and I have to admit I personally learned alot - but this clearly is not for everyone - and some may want to wait until a more final release of TWRP is availalbe. I assume things will be much easier when it is.

Huge thanks to the OP for his ROM - thanks also to Chainfire and Team TWRP for their work - and the many I have read and learned from in this thread and others about fastboot flashing - and particularly the steps for flashing this rom succesfully - thanks to all!

---------- Post added at 06:13 PM ---------- Previous post was at 05:36 PM ----------

You have to make sure you original rom is on A first - change to a - reflash stock - twrrp - root - rom - viola!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
I have modified the script on the Marlin build to be able to choose slot a or slot b to flash to. I'll make the changes to the sailfish version tomorrow
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
WETA 1.0.2x

Added options to flash to either boot slot a or b. Check your boot slot in bootloader, then flash to the appropriate slot.

ROM Download Page

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
Loving the rom. Sent you some beer money :good:

---------- Post added at 12:49 PM ---------- Previous post was at 12:39 PM ----------

I did the same but I reflashed stock, twrp, kernel, rom then root. Rom is banging.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
Went to download but the AFH download page says it is still WETA 1.01 ? have you uploaded the new version yet or is the name on the download page wrong?

I think you got your files mixed up - looks like you get V1.01 at the download page for the non verizon varient - and you get 1.02 on the verizon download - Unless I am looking at it wrong - please advise? If I am mistaken forgive me - but that is what it looks like to me...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
X is the Verizon variant. And is the one I updated
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
My mistake sorry - I must have missed that in your post, I didn't realize the update was limited to the Verizon Varient. thanks for letting me know. (I also confused myself when I noticed the other file has a V in the name - totally my misunderstanding but I thought that must have meant that this was the Verizon file ..my mistake - my apologies. By the way, thanks for an awesome rom - flashed yesterday and it is running very smoothly. No issues.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
Don't know if this is the right place but anyway to add screenshot to your WETA Reboot?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Good idea. It may take a couple weeks, but I'll note it.

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
Yeah it confuses me also haha. I can't find any differences between the firmwares internally. It's all radio.img differences which you can flash separately.

? --->
[Google Pixel ROMs, Kernels, Recoveries, & Other De] drocny87:
i to have the verizon variant currently on nde63x. how has battery life been compared to stock being that u flashed this with a different kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] forgiven90:
Anyone else having a problem with the clock app force closing?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jayfried:
It did once on me I uninstalled all the updates from the Play Store and reinstall it seems to work. If it does it again I'll use titanium to uninstall it completely and reinstall it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
That would be awesome.

---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------

Battery is great with kernel and WETA together.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] drocny87:
What slot did u flash the rom on?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
You should check what slot is activated for you in bootloader and flash to that slot. That would be the most reliable. Also don't bother flashing kernel unless you know that you need to flash twrp and supersu again
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
Installed to slot a.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] UK_Wildcats_Fans:
Is it possible to add the WETA Reboot to the power button?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Sorry if this has been answered buy does adaway work on this Rom?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Works here, in the app settings, check systemless
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Quadman:
Is Headphone warning disabled baked into the rom or is it in the mod somewhere?.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
If it was, I would've done it. This rom is not built from source.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Mentalmuso:
It's baked into any framework mod. In other words, if you choose a custom navbar height. I will add it to stock next week.

Edit.. you could essentially flash the weta stockuimod mod in the apps and mods section to achieve this.