• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][Marlin][7.1.1] WETA 2.3 [NMF26Q][AudioPhile][21st.Dec]

Mentalmuso

Recognized Developer
Mar 20, 2012
7,547
8,494
113
Austin

You flash this rom at your own risk,
i take no responsibility for any mishaps.​

Subscribe to update notifications and general chat by clicking the button below
WETA Pixel TELEGRAM CHANNEL


This here is my personal setup and thought i'd share. Usually i test extensively before releasing to public, but if you do find something detrimental to the usage of your device that is either Force Closing or simply not working, let me know and i will in turn inform whether that is something i will tend to.

WETA is made for Music geeks like me, its main focus is stability and Audio. It is Based off latest firmware currently, and will always be using the most up to date firmware base.

Audio mods...

ViPER4Android 2.3.4.0 with Super quality audio driver or the new 2.5.0.5 with driver pre-installed (credit to @viper520 + @zhuhang)
- for more info on V4A, visit the WEBSITE or XDA thread
Sony Xperia� Z5 Premium audio system
Beats� libraries and effects
Dolby Atmos�
All mods are System Wide


Rom also includes...

3Minit Battery Mod Option - (credit to @gharrington)
- for more info on 3Minit Battery, visit the WEBSITE or XDA thread
Center Clock
QS tile options
Navbar swap back and menu buttons
All display rotations
Navbar size options
Headphone volume warning disabled


How to install...
See post #4 - HERE


Changelog...



V1.0
Initial release, based off NDE63V
WETA Audio
- V4A 2.5.0.5
- V4A 2.3.4.0
3Minit Battery
Center Clock
QS tile mods*
SystemUI tuner mods
- navbar tuner
- brightness slider toggle

V1.0.1
Fixed V4A 2.3.4.0 install bug

V1.0.2x
Added Boot slot options

V1.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!

V1.0.3
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 Walkman Music Player
Added V4A convolvers and profiles
Added Adblocking hosts file
Added Tethering hack (may work)
Added 1 Verizon apk to debloat

V1.0.4
Added AdAway adblocking app
Added Busybox install to system
Added System tweak scripts, zipalign + sqlite

V1.0.5
Added Verizon sim option
- hopefully eliminates update nag

V2.0
I firmly recommend updating to full stock NMF26O, and booting into it. Then rooting before flashing the ROM
Based off Dec update NMF26O
All mods working

V2.1
Added Remove NavBar option
Updated Google TTS
Updated/Added GBoard (First boot GBoard will crash, fine after its libs are initialized)
Added Dark Boot Animation option

V2.2
Updated to NMF26Q

V2.2.1
Fixed V4A convolver and profile permissions
� FYI this will wipe out your /sdcard/ViPER4Android folder



V2.3
Deodexed Framework (smaller zip size)
Debloated apps available on playstore
Zipaligned all apks
Different system install method
- No more need for 1.8gb of tmp space for install
*GoogleTTS will still crash on first boot on a clean install until you update all your google apps. Thats just the way it is. If you ask about this, i slappa yo face.
**Flash a fresh vendor.img BEFORE the rom. Just do it. If you don't, and you post about V4A or Dolby issues, i slappa yo face.
***Volume control issues are related to janky google tts updates. Not a rom issue


Flashing of vendor.img should be done BEFORE flashing the rom if you want all functionality! The WETA rom zip modifies files on the vendor partition. Meaning if you flash vendor after the rom, you will break WETA features.

Do not flash Gapps with this ROM!
Because this is based off of stock android, gapps are included.

See pot 2 for more info and FAQ

ROM Download Page


Wiping data, cache and dalvik is recommended.
Wipe Data if you are coming from another rom or version base, have crashes or other issues before reporting.


Kernel source - https://android.googlesource.com/device/google/marlin-kernel/
WETA Reboot source - https://github.com/daxgirl/6thGear-Reboot-App


If you like my work, please consider buying this poor guy a craft beer for his efforts


This rom is built from a stock google rom image and doesn't require source links.

------------------------------------------------------------>

XDA:DevDB Information
WETA Marlin, ROM for the Google Pixel XL

Contributors
Mentalmuso, mentalmuso
Source Code: [url]https://android.googlesource.com/device/google/marlin-kernel/[/URL]

ROM OS Version: 7.x Nougat

Version Information
Status: Testing

Created 2016-11-17
Last Updated 2016-11-16
 
Last edited:

Mentalmuso

Recognized Developer
Mar 20, 2012
7,547
8,494
113
Austin
Welcome....

I just wanted to start by saying, we all know things are a little bit different with the setup of a pixel device. I think i have a handle of things though there is always a chance of death... i mean crash. Just please, always backup.
Also i am pointing scripts etc to partition slot system_a. Im still not exactly sure if you will come across problems when things update but i suppose we will see.

Now with regards to TWRP and Root. Please read up carefully on these two subjects as they are both pretty young at the moment. Flashing TWRP will be the first thing you need to do. After that, flashing a kernel as i am not including one at this point. Maybe later... If you have come from the same firmware then you wont need to flash a kernel, or vendor etc for that matter. Just boot into TWRP and flash the rom. If you wipe data, you will need to flash SuperSU SR4 after the rom, just to get the SuperSU app back into your app drawer. If you dont wipe data, then the SuperSU apk should still be there along with root binaries.

The zip is big, and will get smaller as time goes on. At this stage there is no real debloating, unpacking and repacking of the system.img hasnt been done yet, so the whole thing is in there at this stage. Also because this rom is based off of stock a stock google android prebuilt image, this means you dont need to flash Gapps. In fact dont, itll break things.

On a wiped data, first boot, i did notice Google TTS crashes though after the play store updates, this goes away. Also if other google apps are crashing because you're lazy and didn't wipe data. Then try uninstalling the apps updates in the play store and reinstalling.

EDIT - One more caveat, you are going to need an extra 1.7gb of free space just for the rom flash, this is on top of the actual size of the zip. I have had to have the system.img extract to a tmp folder before flashing, this gets wiped on boot, so you get that space back after reboot.

I think thats all....

--->
 
Last edited:

Mentalmuso

Recognized Developer
Mar 20, 2012
7,547
8,494
113
Austin
Odds and Ends, Tricks to getting broken things working again

This is a very general post, and can possibly be used on other phones and roms.

My SystemUI keeps crashing, even after a fresh stock install...
If SystemUI is modified, and this modification causes a crash, this can damage the runtime data for systemui. This means that even though you flash a bone stock systemui, it may still crash on boot. Wiping all data fixes this, though that is a pain in the butt. All you need to do is go to, and delete /data/system/users/0/runtime_permissions.xml. You can do this in TWRP file manager. Reboot, job done. This will reset your wallpaper but who cares.

V4A keeps asking to install drivers, or V4A stops processing...
This is a constant issue people have, except for me...... what does this mean? it means i, as a rom dev, am constantly and consistently wiping data and sdcard for testing purposes. This tells me one thing i think is obvious, but of course i may be wrong, bad data will kill V4A. But i will say that flashing a stock vendor.img AFTER the rom will break V4A and Dolby (flash vendor.img before rom). SuperSU is crucial. If in doubt, flash the supersu zip again after rom install. V4A and Dolby both need selinux to be set to permissive. This is achieved with SuperSU and its boot scripts. Also Spotify will stop processing sometimes if a track plays through to the next by itself. (Skipping tracks isnt affected). This bug can be remedied by turning off gapless playback.

--->
 
Last edited:

Mentalmuso

Recognized Developer
Mar 20, 2012
7,547
8,494
113
Austin
<--- Installation Instructions --->

This is a dynamic post, or in other words, it may change from build to build, when it does, i will inform users with the new ROM link post.

First off, this post is a little late, i should have done this earlier but it is what it is and its here now. At this time this is directly related from updating from WETA 1.0.5a (may work on others) to WETA 2.0.

- Boot Slots -
If you are new to the Pixel and are about to start flashing, there is something you need to realize. The Pixel devices have two sets of partitions to boot from. This allows seamless updating on googles part. Google it.. Anyway, in the ROM aroma menu you will notice options to select which boot slot to flash to, A or B. You need to flash to the correct slot, which would be the slot you are already booting into. You need to check this by booting into bootloader and it will be listed there. It states your boot slot in TWRP also when you select reboot. Though i would trust Bootloader more at these early stages.

Both methods below will work also if you are coming from stock. You just need to get yourself TWRP'd and Rooted.

Method #1 - No Wipe (dirty)
This method isn't usually recommended when jumping bases, but worked ok this time around. These are the steps i took that were successful for me.
I started out being on NDE63V WETA 1.0.5, TWRP, Rooted

1. Boot into bootloader and check what boot slot is active, take note of it.
2. Boot into TWRP
- dont do any wiping whatsoever.... the weta install automatically wipes dalvik and cache.
3. Flash NMF26O vendor.img using TWRP
4. Flash WETA 2.0 selecting the correct boot slot from step one in aroma.
5. Reboot system, this can take 5-6min as it rebuilds Dalvik

--->

Method #2 - Clean install (Wiped data) or (img flash only no wipe)
OK, so we are jumping from 7.1 to 7.1.1. There are going to obviously be some changes, thats why i was surprised that Method #1 actually works without issue.. Having said this, when using the method above (method #1) but wiping all your data instead.. This creates a problem with acore crashing constantly on boot. This led me to trying to understand the system apps a little better, and from what i can see, all the system apps are odexed but the odex files live on another partition that gets loaded up on first boot. With changes between the old and the new firmware and its apps there is a good chance the odex file from the old firmware doesnt play well with the updated apk. And the only way to get those odex files onto your device is to flash the firmware package. Regardless... if you want a clean install this time around, follow these steps

1. Backup everything, because you may lose everything, or you may not.
2. You are going to need the stock firmware package and a pc, (aosp download page)
3. You are going to need fastboot drivers, google how to install adb and fastboot. You should already have them if you own this or any nexus devices.
4. OK this is where you flash the whole firmware package. If you do it as is, you will wipe all data on your phone. This includes photos and music. So again backup if you care.
- NOTE, you can preserve all of your data by opening the flash-all.sh(linux) or flash-all.bat(windows) script in a note pad and deleting the (-w) in the line (fastboot -w update image-marlin-nmf26o.zip)
- the process goes like this, open a terminal, cd into the firmware folder, and run the flash-all script (sh flash-all.sh for linux) (double click the flash_all.bat file for windows)
- Now you have all the stock img's flashed to your device on the active boot slot
5. You can now start the rom install process, you are going to need to re flash TWRP and SuperSU.
6. Now all you have to do is Flash the WETA rom. Select the boot slot that you have active in bootloader. Check it first then flash to it.
7. Reboot system, boot may take 5-6min

--->
 
Last edited:

thewebsiteisdown

Senior Member
Mar 18, 2011
722
171
0
My only question is about the kernel part. I am on the latest v verizon rom already, do I need to flash a kernel or just flash the rom then su?

Correction, I'm on the x verizon build.
 

Mentalmuso

Recognized Developer
Mar 20, 2012
7,547
8,494
113
Austin
My only question is about the kernel part. I am on the latest v verizon rom already, do I need to flash a kernel or just flash the rom then su?

Correction, I'm on the x verizon build.
I looked at the aosp images site today and it states that V isn't the Verizon one but in fact that X firmware is. It's pretty confusing. But regardless, if you are already on V, and you are already twrp and rooted, then you can literally just flash the ROM over the top. If you also don't wipe data, then you will keep the SuperSU app.

Edit.. all the firmwares seem to have all the apks needed for Verizon anyway.

Sent from my Pixel XL using Tapatalk
 

thewebsiteisdown

Senior Member
Mar 18, 2011
722
171
0
I looked at the aosp images site today and it states that V isn't the Verizon one but in fact that X firmware is. It's pretty confusing. But regardless, if you are already on V, and you are already twrp and rooted, then you can literally just flash the ROM over the top. If you also don't wipe data, then you will keep the SuperSU app.

Edit.. all the firmwares seem to have all the apks needed for Verizon anyway.

Sent from my Pixel XL using Tapatalk
That's my fault bub. I'm actually on X which is Verizon. Sorry for any confusion.
 
  • Like
Reactions: Mentalmuso

thewebsiteisdown

Senior Member
Mar 18, 2011
722
171
0
Just flashed it and everything went good. I like the installer. Thanks sir!

It's telling me there's a system update. I just turned the auto system updates off in the developer options.
 
Last edited:
  • Like
Reactions: Mentalmuso

thewebsiteisdown

Senior Member
Mar 18, 2011
722
171
0
Really? System update? Were you on V previously? That may be because your were on X.

Sent from my Pixel XL using Tapatalk
Maybe I should take it lol.. It says it's only 18MB. I did wipe data cache and dalvik through twrp just so you know, before flashing.

I get an error saying there's an internal problem with your device contact your manufacturer for details when I reboot for some reason to but, I click ok and everything seems to be working? Verizon pushed their apps to my phone when it all booted up but I removed them and they were not there at first.

Either way I love it so.

Added screenshots in case you want to see what I am referring to. The LTE service kicks in fine just so you know, I see it captured no sim blah. I just captured the screen shot to fast is all.
 
Last edited:
  • Like
Reactions: Mentalmuso

Mentalmuso

Recognized Developer
Mar 20, 2012
7,547
8,494
113
Austin
Maybe I should take it lol.. It says it's only 18MB. I did wipe data cache and dalvik through twrp just so you know, before flashing.

I get an error saying there's an internal problem with your device contact your manufacturer for details when I reboot for some reason to but, I click ok and everything seems to be working? Verizon pushed their apps to my phone when it all booted up but I removed them and they were not there at first.

Either way I love it so.

Added screenshots in case you want to see what I am referring to. The LTE service kicks in fine just so you know, I see it captured no sim blah. I just captured the screen shot to fast is all.
the internal error problem comes from a mismatch with vendor build.prop and system build.prop. This kinda indicates that you didnt flash vendor. Or if you did it didnt flash. Try that again.

--->
 
  • Like
Reactions: Foxgguy2001