yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
Unzip the update to the folder with your fastboot tools. Open the flash-all.bat and toward the bottom you'll find the "-w" and delete only that. Save the file. Next boot the phone into fastboot mode, connect to PC with the USB cable, click in the fastboot folder you have open on the desktop and double click "flash-all.bat". It should then run the batch file and perform the update.

If I have missed anything someone feel free to chime in.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Github for PN hasn't been touched in a while
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
PN should be touched.....it likes it [emoji7]
[Google Pixel ROMs, Kernels, Recoveries, & Other De] nashnative:
RIP Pure Nexus
[Google Pixel ROMs, Kernels, Recoveries, & Other De] udahy.manna:
It was a great ROM though..!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
There is no proof PN has been stopped.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
There has been no work on it at all, and android p is coming out in a few months with no android o release, I'd say its dead. Will it come back for android p? Who knows. Its dead at this time. Can we stop bumping this thread, thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
This firmware is dead.......stop lying to yourselves.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clothednblack:
By continuing to comment "thread is dead", you yourself are bumping the post not to mention, trolling as well. Let it go if you don't have anything constructive to add.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maxwell0312:
I am on Pixel OG 5" with Stock Oreo 8.1, May 2018 OTA update. Planning to put this ROM on, so I guess first thing would be to restore to stock 7.1.2, then unlock bootloader, then TWRP, then flash? The only reason I'm doing this is because current Stock is too bad on battery, 3hr SOT on normal use. If anyone has tried this, please let me know if its worth it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] deepss1:
I just wonder with curiosity, why you want to flash a ROM which has been not updated since long ?

Just because of a brand of PN or something else ?

Please lighten up me.

Thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maxwell0312:
Actually, my main goal is to go back to Nougat to see if battery life improves. But Nougat is an older OS for this phone, so I figure: While downgrading, why not go for a custom ROM? And Pure Nexus showed up during my search, so i would like to give it a try.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Novakingwai:
I would like to remove Super User. If I go into Settings and then Super User, I see an option to remove it completely. Is it safe to do? will it mess up the ROM? I also get an option to restore Stock image, I should click no?

Also I want to install Magisk. Do I just download and install? Or do I have to flash in recovery mode?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Personally, I'd remove it manually by reflashing PN.

As for Magisk, yes. You must install it in recovery.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Novakingwai:
I'm trying to flash Magisk trhough TWRP, but it says error I must reinstall stock image first. Can you not do this with Pure Nexus ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Guess not... It's been a while since I've used the ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
I had the same issue when trying to install magisk. I ended up finding SuperSU. Let me know if you find a solution
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Novakingwai:
This is my error log when trying to install
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mbk17:
I havent flashed a new ROM in a while and have had 07/25/17 since its release. What releases for 8.1 are similar to this ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ezrem:
I've been using the FireHound release, which has most of the same features as Pure Nexus does.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] k3ss3n:
I keep getting a bootloop after installing this (the phone just stays on the Google screen). Anyone have any ideas?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Use a different rom because this is over a year old
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Just thought I would post this here, an update on the status of Pure Nexus by [MENTION=4395895]BeansTown106[/MENTION] on the Pure Nexus Google Plus page. https://plus.google.com/communities/103055954354785266764
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tomoya06:
Most stable one till now

Trying custom ROMs now on my Pixel. And this is the most stable one -- easily installed, no STOP-RUNNING stuffs and containing GAPPS. Thanks:laugh:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] xaoup:
I'm on a stock android pie right now. Rooted with twrp. Can i just flash this ROM without flashing the included vendor image?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
You realize this rom is still running nougat right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] xaoup:
Yep.. that's why i'm asking if it's okay to flash it on top of Pie. Thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Donz7733:
Is anyone facing the 'No sound during calls' issue in this rom?

I am facing it on Android Pie, so want to downgrade, if this version is working fine
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PGHammer:
I wouldn't say It's Dead, Either

Dead - no. The issue, however, is that stock 9 AND stock 10 are both available for the Pixel (and successors thereof); thus, it's harder to stay put. My Mom has a refurbished original Pixel and is running Android 10 (for example). However, I'm looking at the same phone to throw Pure Nexus on; however, I'll be comparing it directly to my dead-stock Pixel 3a. The 3a can't run Android 7; the hardware is too new; however, the original Pixel can (and in my Mom's case does) run Android 10; how can you compare old ROMs to new when very little hardware can span the gap? (The original Pixel is easily the oldest hardware left that CAN span that gap; fortunately, the price lets such testing be done.)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PGHammer:
Moribund, But NOT Dead (and why it's not).

I pointed out (in an earlier post in this thread) why older ROMs like this are not dead; the end of the stock road for this phone merely drives it home with a sledgehammer. While there will be more development merely because stock is not an option going forward, there still remains the "comfort factor" older versions of Android still have - look at how much of a beatdown Pie (and even Oreo) are getting in threads for other Pixel phones - not just this one. I used to RUN this on my Google Nexus (if it weren't for an apparent battery issue, I could today) - since my Pixel 3a is too new to do so, I'm looking at grabbing a used original Pixel for comparing it to Android 10 (not just on my 3a, but on Mom's original Pixel, which is ALSO running Android 10 currently).

Actually, I would (in your place) drop all the way back to Android 7.1.1 (instead of 7.1.2) before unlock/TWRP/crossgrade.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] damagi123:
honestly nougat was the last version that wasnt outrageously buggy all day every day. My phones been freezing 40 times a day since oreo
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
[MENTION=694833]Quatra[/MENTION]ng1

I tried booting inactive slot. Black screen, constant system ui force close. Booted back to Pure Nexus, black screen system ui force close. Clean flash. Back in the game
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mac796:
Yes correct me if I'm wrong but if you just flash all. It only keeps one active boot image in one slot. So if u want to jump from a to b you have to manually flash all images to a and b?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Right, but I did and will continue to do that. Might be Franco in one slot and stock boot on the other that screwed me?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ne0ns4l4m4nder:
That's weird the January update factory image and new fastboot files flashed stcok bootloader and recovery to both slots a and b
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Chronzy:
Right click on flash-all.bar and edit. Remove the -w near the end.

Or a QS tile ☺

Using action launcher as well and would love to use the gestures for screen off if it weren't for the extra security due to device admin policy. Would love to find a way around that. Currently flar's 1.03 with navbar sweep 2 sleep is working well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Not mine, recovery is inside the boot image.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mac796:
I would not try to boot into the other slot. could end up in a boot loop. Unless u manually flashed images to both a and b
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
I second that. Had to clean flash to get back. No bootloop, black screen and constant system ui force close on both slots.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mac796:
Man I got lucky then. I was dumb enough to try it twice. The last time went into a 10 minute boot loop it finally came out of on it's own
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
Haha yeah, my bad. Had an old sdk location in my path so I wasn't actually using my updated version.

But even still, after updating to the newest version, the commands from the bat would only flash active bootloader and radio:

X:\Android_Dev\pixel_sailfish\sailfish-nmf26u>fastboot flash radio radio-sailfish-8996-012511-1611190200.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57192 KB)...
OKAY [ 1.770s]
writing 'radio_b'...
OKAY [ 0.564s]
finished. total time: 2.336s

X:\Android_Dev\pixel_sailfish\sailfish-nmf26u>fastboot --version
fastboot version 0e9850346394-android

Though I did find that you can specify slot "all"

X:\Android_Dev\pixel_sailfish\sailfish-nmf26u>fastboot flash radio radio-sailfish-8996-012511-1611190200.img --slot all
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.835s]
writing 'radio_a'...
OKAY [ 0.561s]
sending 'radio_b' (57192 KB)...
OKAY [ 1.838s]
writing 'radio_b'...
OKAY [ 1.448s]
finished. total time: 5.685s

The logging when trying that for bootloader doesn't give me much confidence that it actually works though, as it says it flashed the active slot twice:

X:\Android_Dev\pixel_sailfish\sailfish-nmf26u>fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img --slot all
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 1.093s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.142s]
sending 'bootloader_b' (32980 KB)...
OKAY [ 1.060s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.152s]
finished. total time: 10.449s

Even trying to specify the other slot gives me the same logs:

X:\Android_Dev\pixel_sailfish\sailfish-nmf26u>fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img --slot a
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32980 KB)...
OKAY [ 1.078s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.153s]
finished. total time: 5.231s

I wonder if having TWRP in the mix affects it somehow -- but I'm too lazy right now to go back to completely stock.

Point of story: for radio using "--slot all" is helpful, for bootloader I would err on the side of caution and flash, reboot, set_active to the other slot, reboot, and flash again
[Google Pixel ROMs, Kernels, Recoveries, & Other De] geoff5093:
Anyone else having an issue where when rooted, if you reboot your phone it will bootloop? If I reboot my phone I'll have to boot into recovery, dirty flash the ROM, reboot then reroot and I'm fine until I reboot again.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Nope
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Yeah, we will have to figure that out. I was running Franco and stock boot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
No, don't have that issue. What version of Super su did you flash?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] crossen0:
Would someone who got V4A working kindly share their process?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
All good. Mine works now! Thx.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Good job on this ROM. Will be my goto Rom for the foreseeable future unless Lineage pulls a rabbit out its ass and out does PureNexus
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
yes, it works fine. I just flashed it in recovery and all is good.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Figured I would share to get some opinions so we can hopefully learn more about these phones.

I was never rooted and never had TWRP install prior to these steps. I had all the steps typed out before I even performed them so this is 100% exactly what happened.

Last night I was stock and took the OTA update to NMF26U (I did not pay attention to the slot at this time)

Today I went through the process to install twrp, root, and flash this ROM

-I did fastboot boot twrp,img and I saw right away I was in slot A. So this would mean the OTA took last night was installed to slot A.

-Factory reset

-Flashed ROM

-Flashed TWRP zip

-Booted into OS and got the error about the vendor image which was expected

-Rebooted to twrp and flashed V vendor image

-Booted into OS so I could log into snapchat

-Rebooted to TWRP flashed SU

-DONE

So after putting the pieces together.. I know the OTA went to slot A because that is what my first boot into TWRP showed. I flashed pure nexus which we know flashes to the inactive slot. So this would mean that my slot A would still be 100% untouched and running NMF26U. So I figured I'd try and boot into just now and see what would happen.

The first boot booted pure nexus so the slot switch didn't take

Back to TWRP and swtiched to slot A again

This time it booted (I could tell by the white startup screen) and then as soon as I unlocked the phone I started getting error messages popping up. "Google app has stop", "Gmail has stopped", etc. Also the icon for the phone app was gone from my dock. I confirmed in settings>about that I was in fact on NMF26U and NOT pure nexus. The interesting part is that is said I was on the V vendor image.

So i rebooted to TWRP and switched slots and rebooted back to pure nexus on slot B. I again got about 3 error messages about apps stopping (google app, gmail, etc). The pop ups have stopped but something is not right. I can't open gmail now I still get that message saying "gmail has stopped". --EDIT-- looks like this is gaaps related as its only gmail, gboard, and google keep that are closing. Strange how they got messed up

Looks like I am going to start from scratch but I don't mind at all. I am more curious to figure out how/why this got messed up. Like I said I was very EXACT with all the steps I did and the order I did them. So I'd love to know other people's opinion if they know what's going on.

Also one thing that makes no sense to me. If you look at the steps I went through, I flashed the ROM (to slot B), booted to the OS, then rebooted to twrp which means it switched slots, and then flashed the V vendor image which would have flashed it on slot B. So HOW in the word does my slot A NMF26U have a V vendor image? Makes absolutely no sense whatsoever because each slot should have it's own vendor image..
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dchurch85:
Thanks. Worked easily.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
This actually makes total sense. The data partition is shared by both boot slots / system partitions. So when you go boot stock after flashing pure nexus, it's the equivalent of dirty flashing stock (because you're keeping the same data partition and cache but changing the ROM). And as we know, things can get hairy when you dirty flash different roms over each other.

With regards to Vendor, that is more interesting. I do recall that there are both a and b vendor partitions. However I can see one of two things happening: either you flashed the vendor and it was inadvertently flashed to both vendor slots (did you flash the IMG via TWRP or fastboot?) OR after flashing a new vendor, this is recorded somewhere on the data partition that displays in "info" in settings but is actually the U vendor.

Thoughts?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Interesting. I flashed the vendor image with twrp. I'm also positive I flashed it once only and it was to slot B. I was in A, flashed PN which flashed to B. Booted the phone and got the error about the vendor, rebooted to twrp so I was now in slot b.. And then flashed the vendor. This one definitely has me puzzled and I'm hoping someone chimes in who can explain it lol

Also i kind of understand what you mean about the dirty flash stuff.. But I also know that people have successfuly dual booted with the slots. They have had stock unroofed on one slot and a ROM/root/kernel on another slot. With the order I did everything I'm confused as to why it gave me issues. What's even more puzzling is why now that I'm back booted in PN am I havong random error messages saying random apps closed. Ones that aren't even open. Wouldn't you think this slot should be untouched since I haven't done anything to it. All I did was switch slott in twrp, boot stock, then switch slots again and boot back to PN
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Keasby:
This slot discussion, isn't it better to discuss it in twrp thread? Vor even in a Q&A thread?

Just my 2 cents...

Gesendet von meinem Pixel mit Tapatalk
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Same thing I suggested in the TWRP thread. Might as well start a pixel slot discussion thread.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Haz3:
New thread in guides and discussion section for Dual Slot matters
[Google Pixel ROMs, Kernels, Recoveries, & Other De] geoff5093:
2.79 SR2
[Google Pixel ROMs, Kernels, Recoveries, & Other De] McMarius11:
Yes but hold a software button for 3 seconds is much more convenient for me. and a other rom for my older device had this feature built in to the rom. :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
Hmm, I'm thinking your issue is not root itself, maybe something you did with it. Rebooting works fine for me (with that same version of Super su)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] peikojose:
I don't know if it is a bug, but if I use expanded desktop when the phone is in ambient display notifications don't show.. probably because the status bar is hidden ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Would it be possible to see the likes of Fdroid, Signal, k9mail, etc intergrated into the Rom?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I doubt it. This ROM is about being close to stock as possible with extra options. Though I'm not in any way connected.

Cant you just set this up your self?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
I wouldn't be in favor of it either. I do not use them and it would just be more bloat to disable/uninstall/delete.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ubelsteiner:
Same here! Seeing this just got me twice as excited for tomorrow!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] McMarius11:
thank you!!!! i installed it and love the sweep 2 sleep <3
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
What does "LTE+" mean on the signal icon? (as opposed to just LTE without the plus)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
I believe it's Volte
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dchurch85:
I started the process over. It worked. I didn't flash all the first time since I was already on the newest software. It is working now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pilotgav:
Where should we be able to turn on VoLTE? I can't find it anywhere.

Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Settings/more/cellular networks - turn on enhanced 4g LTE
[Google Pixel ROMs, Kernels, Recoveries, & Other De] zalcsooo:
I don't have that option, but I heard in another custom ROM thread that the LTE+ sign is an operator-side thing:

"LTE+ is the symbol for carrier aggregation. Basically, you're running on a more advanced network from your carrier. You should contact whoever your carrier is for more info." [MENTION=2489052]NYCHitman1[/MENTION]
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Yeah, I heard both. Volte and carrier aggregation. I thought it was Volte.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
To answer my own question, it was the custom font/display size I had set in the Display settings - it cut off the gear icon beside Google TTS.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
Who is your carrier? On Verizon I can access the setting for VoLTE by dialing *#*#4636#*#* and choosing Phone Info.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
Dude... This ROM runs so freaking well!

One thing I would like to change, though: I miss the Google Phone app. Is there a way to replace the phone apk with Google's?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
You could install it from play and make it the default phone app. After you could also use TiBu to freeze and/or uninstall it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
That did the trick. Thanks! My worry was that placing and receiving calls relied on com.android.phone... Apparently not!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
[MENTION=2026117]FernBch[/MENTION] did you get a chance to read my PM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pilotgav:
I don't see the difference between the two?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Same. Except I couldn't get visual voicemail working on Google phone. Uninstalled and used system phone app, works perfectly.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
The Android Phone has the Marshmallow design (caller's profile pic and all the call options toward the top), Google's has a new design with the call options toward the bottom.

When a call come in, the new phone lets you answer by swiping up and declining by dragging down vs Marshmallow's right/left choices (I prefer the up/down because it matches my Huawei Watch's DP2.0 call screen).

There's also a few Google caller ID options that aren't available through the Android phone.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
Replied
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
You're right. Did you get visual voicemail working on Google phone app?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
Nope, looks like that's the big takeaway there... Thanks for pointing that out. I might have to switch back to the neutered phone app unless someone knows a way to get VM support (I have my work numbers forwarded to my personal Verizon number). :(
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Hopefully [MENTION=4395895]BeansTown106[/MENTION] will see this and add fix into upcoming build. Also I cannot get ok Google to work, tried everything. Assistant works by holding home, but no ok Google detection.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
Yeah, it hasn't been working for me either