yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] S3NTYN3L:
Yeah, I found out that hard way last night after much weeping and gnashing of teeth. :(

My phone really didn't like TWRP 3.2.0 nor 3.2.1. I just could NOT get recovery to decrypt stock 8.1 (with or without a pin set).

At one point, I tried just reverting TWRP back to 3.1.0-RC2 from 3.2.0/3.2.1 thinking maybe that would fix the decrypt issue, but that just screwed things up even more.

I ended up flashing EVERYTHING back to stock 7.1.2 and then;

fastbooted into temporary TWRP 3.1.0-RC2

installed TWRP 3.1.0-RC2

flashed PN 7.2.1

reinstalled TWRP 3.1.0-RC2

rebooted into system

rebooted back into TWRP

flashed SuperSU 2.79-SR3

rebooted back into system

This installed everything to slot B and made it active since I happened to be on slot A at the start.

I then went back into TWRP and;

flashed PN 7.2.1 again

flashed TWRP 3.1.0-RC2 again (just to be safe)

rebooted into system

rebooted back into TWRP

flashed SuperSU 2.79-SR3 again

rebooted back into system

Now both slots are running PN 7.2.1 and have root.

After all that frustration, I'll just stick with PN 7.2.1 for now.

Hopefully someone can guide us through an upgrade process when Beans drops PN 8.1 on us.

Now to get my wife's Pixel 2 rooted whilst doing away with that annoying "There's an internal problem..." nag screen. ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
I flashed 3.2.0 on stock 8.1 3 weeks ago. Seemed to work flawlessly for me. I have since dropped my phone in the pool and had it replaced last week so I haven't tried again yet.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
Yeah guys it's coming, just take a look at the github link in the description.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] b00ster23:
Yup! Seen that the other day.... Thought about posting, but trying to keep the torches and pitchforks away from Nate. :p :D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roblav96:
Ergermergerrrrrrdddddd SO EXCITED :D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
I can't get SuperSU working on this. Ideas?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
You gotta give us a little more than that lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
Anyone know how to prevent apps from accessing the internet like on LineageOS?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
Figured it out. I needed to flash TWRP and then SuperSU
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
so, was in recovery and noticed it said i was booting from slot B, so i thought hmm lets boot slot A. now it loads and i get it moaning about vendor something ( if i recal it the baseband image being old) but i thought oh ill just boot back to B. Twrp seems to have gone, cant get back into it. Any ideas? was unplanned so not go ta recent back up so a wipe would be extremly undesirable. please help
[Google Pixel ROMs, Kernels, Recoveries, & Other De] b00ster23:
Try booting directly from the IMG with ADB commands. Instructions from the link below

If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:

fastboot boot path/to/twrp.img

https://xdaforums.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
erm it seems i cant get into the recovery, when i try i get a ramdump then it reboots and loads up into insta crashy slot A telling me that the vendor image is wrong.

what am i doing wrong here?

would it be a wise to try using the twrp app from the crashy slot A to flash it? if so do i go with the installer.zip or the .img? been so long since ive played about with this stuff its all forgotten
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Okay I also have had problems with ramdumping and getting to fastboot. Remember, you're not trying to boot to recovery right now. Let the phone ramdump. As soon as the screen flashes to black, hold Power + Volume Down. This should get you to bootloader mode. Now you can follow those fastboot instructions to boot a TWRP img from your computer.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
okay got into twrp and told it to boot from slot B, so fingers crososd its all good, its booting up very very slowly but seems okay

thank you v v v v much for the assistance

---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------

crap, so, no moaning about the vendor being out of date but everything is still force crashing like crazy, any ideas?

---------- Post added at 12:21 PM ---------- Previous post was at 12:01 PM ----------

update, so wont back into twrp and installed it from the zip and now it just reboots and goes right into twrp, no system. slightly freeking out now that i just murdered the phone or at least all the data on it

---------- Post added at 12:28 PM ---------- Previous post was at 12:21 PM ----------

****, it seems its failed to decrypt everything so everything now shows as giberish and would explain why it now cant boot

---------- Post added at 12:44 PM ---------- Previous post was at 12:28 PM ----------

trynig to push the img from adb in the bootloader results in the computer saying failed, partition (recovery) doesnt exist, Help!!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] b00ster23:
Sorry to hear about the woes you're having. Just so as long as you haven't factory reset, your data will be intact if you're concerned with it. At this point I would probably start at square one. From what I've heard you say you were able to boot into the phone at one point with some FC's. Perhaps a few things were botched during the TWRP boot, I've seen some timing issues with TWRP causing incorrect boots. This is the process I would try

1. make sure you are on the latest bootloader, radio, vendor image - I would use the same factory image from google found here. If you have data you're trying to preserve ENSURE YOU DON"T RUN THE .BAT THAT WIPES YOUR PHONE OUT. You can stop the wipe by removing the "-w" and running the the update.

Don't boot into the phone at this point yet. And go to the bootloader https://developers.google.com/android/images

2. install twrp via the instructions in twrp forum - Sounds like you're familiar here with this process, and you will need to use the image with ADB

3. I would try and flash the rom at this point

4. Lastly flash twrp zip again as the rom overwrites twrp and try to go into the phone... remember to give the phone some time to boot.

GOOD LUCK!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
well seems i didnt do the make it not wipe thing. data all go by bye.

assuming is doesnt over write the blocks, any way to recover sstuff? nothing on there that was cruicial but just so much pain reinstalling and logging into everything
[Google Pixel ROMs, Kernels, Recoveries, & Other De] b00ster23:
Nah....sorry bud it's gone. You needed to remove the "-w" switch in the .bat file. At the very least you've got an updated radio, bootloader, etc
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
This doesn't help you now, but for future tinkering purposes I really recommend getting a Titanium Backup + Box cloud sync setup on your phone for apps you don't want to start at square one with.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] b00ster23:
Agreed. Backups are the utmost important to have. Combine that with the understanding that any of the development stuff that's done here runs the risk of "whacking" the phone... I probably should have been a little more specific in the steps up there, but sometimes forget that everyone's mileage will vary.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
oh i do have the pro version of Titanium. i was just not expecting to need it so i was being lazy and didnt create a new back up. though curious why specificaly mention Box as the storage location? it do anything special?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
No specific reason. I just use Box exclusively for TB since it's 10GB free storage which is more than enough for my 64GB Pixel's backups. I was just emphasizing the scheduling/cloud uploading feature--I have mine backup any changes to existing backups twice a week and upload to Box in the middle of the night and it's very convenient.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Xdevillived666:
Cant get this rom to boot at all. CCame from stock 8,1, flashed stock 7,1,2, then tried using latest twrp. Gave me a "no digest found error". The tried the previous twrp. It flshes the rom and then says no os installed when trying to reboot. Good lawd , this is way more difficult than my bullhead days
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
Try twrp version 3.2.0-0 or 3.1.1-1

---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
[Google Pixel ROMs, Kernels, Recoveries, & Other De] billiepreks:
Use TWRP 3.2.0.0 without any lockscreen (Fastboot TWRP 3.2.1.0.img then flash 3.2.0.0.zip if you can't find the fastboot img of 3.2.0.0)

"no OS installed" is a usually message. When you flash a rom.zip when you're on slot A on your Pixel, the device automatically switch to slot B after reboot. So you need to do:

- Boot TWRP 3.2.0.0 without encryption, and look at what slot your Pixel use

- flash your rom

- flash TWRP again because flashing your rom has deleted it

- reboot to recovery (here is the message "no OS installed")

- once rebooted, make sure you're on the opposite slot you were before

- if needed, flash gapps here, then reboot to system
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Beanstown posted an Update over in the XL area

https://xdaforums.com/pixel-xl/development/rom-pure-nexus-substratum-fi-wifi-t3533539/page563
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
Any word on Oreo?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Really??? Literally the last post on the thread before you posted is to much searching...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
Sweet!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] daver68:
I was really hoping that it was meant to be a sarcastic post... but then seeing their follow up post, and I stopped chuckling...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
No I was serious sorry. I went through the G+ forum for PN and didnt see anything so I asked here. I didn't realize he posted.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Senliast:
It is possible to enable encryption on this ROM? Thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Darkknight512:
Mine has always been encrypted on this ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mark2410:
so, err, i installed an xposed module and now the phone is just stuck forever trying to boot. if i get into twrp and tell it to boot from slot b instead all i get is ram dumps. is there anyway to fix without flashing the rom and wiping everything?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Nope. Not as far as I know, unless you have NANdroid backups.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Marc199:
The Xposed uninstaller zip should remove the framework and I think the phone should boot after that.

http://dl-xda.xposed.info/framework/uninstaller/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ansontyl96:
just reinstall the rom without formating system data.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ryanstfl:
Anybody experience a bug where if your phone powers down at zero; all texts erase upon reboot?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
No? What SMS app are you using?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ryanstfl:
Android messenger, the stock Google one
[Google Pixel ROMs, Kernels, Recoveries, & Other De] daver68:
I don't know if the app is what's causing that issue. Aren't SMS/MMS stored in a central sqlite database somewhere in /data, and SMS apps just access that?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pennywaltz:
Thanks this worked for me coming from stock 8.1 back to PureNexus.. is there a particular version of Magisk I should use?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] infectedorganism:
Is Pure Nexus it worth the downgrade from 8.1? If so, which build?

I've had my fun with other devices; flashing the latest/greatest is getting old .I just want a stable, daily driver.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pennywaltz:
Stock 8.1.0 worked fine for me with Magisk. I tried a few customs and none of it was really stable.. So I wanted some extra feature and I was on the latest PN before updating to stock 8.1.0
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mathsz:
Dude, I feel your pain.

I wanted to flash roms again and the slot a slot b nightmare + twrp not always working has stopped me.

Just flashing is a pain now. It's not that bad, you just have to follow a certain set of instructions. But it's nowhere as easy as it was pre-nougat. Or Pre Oreo.

BUT at least, you still have options, and root. Which is nowehere to be found on the fruitphone. :D

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

you can restrain background data.

otherwise, you could do firewall rules..
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
Flash everything then TWRP. Worked for me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mathsz:
you do have to fastboot boot in twrp first, flash twrp3.2.0.0, reboot, flash rom, flash twrp, for slot b, then reboot recovery to change slots and reflash twrp for slot a

right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thisoneguy:
Magisk 13.4 had been the only one I've got to work. Love to hear if someone has been able to update. That said this has been the best dd I have ever found, longest I've stayed on any room.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Poebat:
For me I fastbooted twrp, flash the rom, flashed SU, flashed TWRP and TWRP stayed. If that doesn't work try flashing a different kernel like ElementalX and then flash TWRP
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mathsz:
I tried latest twrp which won't flash because of the digest file missing.

the one I can get to flash the rom is 3.1.1.0

which one are you using?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] udahy.manna:
So..no more Pure Nexus for Pixel..?☹️
[Google Pixel ROMs, Kernels, Recoveries, & Other De] DynamicDonkey:
Where did you get that? Take a look at Beans G+ page. There are updates coming, just be patient.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maulich:
Delete
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
I am now remembering that I did a flashall at some point in between the OTAs I think it was but not sure.. So let me know if this makes sense..

Last night I took the NMF26U OTA. Then today when I was stock and first fastbooted into twrp it said I was in slot A. (I'm assuming twrp boots into whichever slot you have been using) So doesn't that mean that my slot A is in fact already on NMF26U??

and can I boot to it or is something messed up that would cause it boot to boot?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Each slot has its own boot image, vendor image, radio, and system image. This can be easily observed when you break down the flash-all steps individually. I executed those commands one at a time, and changed slot back and forth to see what would affect what. Boot, vendor, radio, and system are slot-specific. In other words, a & b have their own images.

Edited: see post #246. (Bootloader, on the other hand, does not support slot. When I issue "fastboot flash --slot _a bootloader bootloader.img", it will say "Slot not supported for this command". That tells me bootloader is executed at boot before anything else, it could even be stored in hardware. I believe jcase had said that there are 2 bootloaders, but I don't see it). I see one bootloader and 2 boot images (one for each slot). That would make sense as each boot image contains specific kernel and RAMdisk to instruct the OS how to mount. That's why you can have different kernels, different root statuses, different vendors altogether for different slots.

TWRP is not shared, but get installed into both slots. I proved this by destroying twrp in slot a, and still able to access it in slot b.

Userdata is shared for both slots.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Thats strange, when I flashed the rom and went to the other slot, I noticed I was on the old bootloader. I fastbooted the new bootloader to slot A and it worked

fastboot flash bootloader_a bootloader image.

Successfully flashed to slot a

Rebooted bootloader and checked version success. You don't have it locked do you with that fastboot command you gave us?

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

U is virtually the same as V. You should be the same in both slots. Except for Pure Nexus. Boot the inactive slot and let me know. Haha! Im not quite there yet.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Great we are back to the OT slot stuff that cluttered the TWRP thread?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I can definitely flash bootloader to both a and b slots separately. That doesn't 100 prove that there are 2 boot loaders. Another developer on XDA said this device has 5 bootloader. It's above me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
I'm loving this ROM on the Pixel - never used it before since the Pixel is my first "stock" Android phone. Thanks [MENTION=4395895]BeansTown106[/MENTION]! I have a question regarding Google TTS as it's implemented in this ROM, though, for anyone who's knowledgeable on the subject.

I was using my HTC 10 as my daily driver and only played with my Pixel since I effectively got it for free - so I don't recall if options for TTS (Text To Speech) were any different on complete stock. To summarize, I have my device language set to English (U.S.) but I normally set my Google TTS to English (U.K.) because I like the sexy British female voice in Google Maps. :)

I don't find a way to do that on this ROM. Normally on other phones/non-AOSP ROMs there's an option to download a particular language for Google's TTS. I have found in recent months that I've had to do a weird workaround sometimes where I had to actually set my device language to English (U.K.) but that doesn't help in this situation since I still can't find where to make it download the English (U.K.) TTS files.

I'm guessing it's a limitation of the particular GApps that are included, although I verified that it's updated to the latest Google TTS version.

Any suggestions?

Thanks.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mac796:
I don't think flash all flashes boot image to both slots. I got brave and went into twrp and saw slot a was active. So I tried to boot into b. It tried 3 times and went back to slot a.Which I think is a safety built in. Maybe manually doing this is the proper way. I thought flash all was good enough. Maybe not
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
If you watch the flashall text in the terminal window it literally says flashing the a and then flashing to b...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] roirraW "edor" ehT:
If this isn't a solution you're looking for, ignore me, but what about the built-in double tap to sleep in the status bar option that the ROM already has? Might've needed enabling in the PureNexus settings. I unlock with the fingerprint after using that all the time.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mac796:
That's what I thought to. Until I tried to boot into the other slot. Now I'm unsure
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Suggestion for notification light.

Default speed is set to custom, which doesn't seem to do anything or work.

I think it should be set to normal.

Awesome ROM.

---------- Post added at 02:07 AM ---------- Previous post was at 02:06 AM ----------

These are good instructions for anyone to follow.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mac796:
Ok I just tried it again. Tried going from b to a . Didn't think it was going to boot. I have been using the flash all for every update. I'm going to manually do it for now on
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piccit:
Where do you see that?

Using the nmf26u as an example, the script contains:

fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
fastboot reboot-bootloader

Then it goes on to do radio and the update zip

And the output from flash bootloader is this:

sailfish-nmf26u>fastboot flash bootloader bootloader-sailfish-8996-012001-1611091517.img
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.054s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
OKAY [ 0.701s]
finished. total time: 1.756s
[Google Pixel ROMs, Kernels, Recoveries, & Other De] k.s.deviate:
No it doesn't, only the system_other is flashed to the inactive partition.

C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat

target reported max download size of 536870912 bytes

sending 'bootloader_a' (32820 KB)...

writing 'bootloader_a'...

(bootloader) Valid bootloader version.

rebooting into bootloader...

< waiting for any device >

target reported max download size of 536870912 bytes

sending 'radio_a' (57048 KB)...

writing 'radio_a'...

rebooting into bootloader...

< waiting for any device >

target reported max download size of 536870912 bytes

archive does not contain 'recovery.img'

archive does not contain 'vendor_other.img'

wiping userdata...

Creating filesystem with parameters:

Size: 26663190528

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 32768

Label:

Blocks: 6509568

Block groups: 199

Reserved block group size: 1024

Created filesystem with 11/1630208 inodes and 146354/6509568 blocks

--------------------------------------------

Bootloader Version...: 8996-012001-1608281716

Baseband Version.....: 8996-012511-1609150631

Serial Number........: xxxxxxxxxxxxxx

--------------------------------------------

checking product...

checking version-bootloader...

checking version-baseband...

sending 'boot_a' (26481 KB)...

writing 'boot_a'...

erasing 'system_a'...

sending sparse 'system_a' 1/3 (523506 KB)...

writing 'system_a' 1/3...

sending sparse 'system_a' 2/3 (524279 KB)...

writing 'system_a' 2/3...

sending sparse 'system_a' 3/3 (512303 KB)...

writing 'system_a' 3/3...

erasing 'system_b'...

sending sparse 'system_b' 1/4 (517263 KB)...

writing 'system_b' 1/4...

sending sparse 'system_b' 2/4 (514150 KB)...

writing 'system_b' 2/4...

sending sparse 'system_b' 3/4 (516790 KB)...

writing 'system_b' 3/4...

sending sparse 'system_b' 4/4 (96127 KB)...

writing 'system_b' 4/4...

erasing 'vendor_a'...

sending 'vendor_a' (234277 KB)...

writing 'vendor_a'...

Setting current slot to 'a'...

erasing 'userdata'...

sending 'userdata' (138957 KB)...

writing 'userdata'...

rebooting...

finished. total time: 128.109s

Press any key to exit...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
You most likely have old adb/fastboot environment. I'm not home to give you the output atm but I'll get a screenshot for you.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Just sharing for those who might have missed these posts

View attachment 3996366

View attachment 3996367
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dchurch85:
How do I flash all? and how do I delete -w to not wipe user data?