Google provides all their Roms online monthly. No problem there.
The challenge at the moment is:
How can we recover pixel device stuck in fastboot mode with developer options disabled?
1 Like
If on linux try fastboot devices with sudo (not normally recommended)
If you get a result I’ll ping you the relevant flashing instructions and roms
I’m enlisting some help from calyx off topic. They are pixel experts.
Agreed, @chrisrg, is why I mentioned “Manufacturer” support – I think it will be device specific, but I think that despite fastboot devices returning an unhelpful response (it won’t disclose device info), debugging mainly affects the system and recovery side of things, so that certain fastboot scripts are allowed to work.
I don’t quite follow…
You think a flashall script may work?
… is certainly a good idea.
I tried a flashall script and it had the same “waiting for any devices” output.
Currently I’m seeing if TWRP will work, as I haven’t found any mention of needing USB debugging tools to boot into, although I could be wrong.
Up to you, but I wouldn’t. I’m worried about that flashing vendor_boot step.
Maybe try just booting twrp, not actually flashing it: fasboot boot
When you were setting up did you have to deal with udev rules?
I’ll try that, thanks
This might need dealing with?
No I dont think so.
on a side note, I did try running “sudo fastboot devices” and I got a different output.
18121JECB13289 fastboot
Cant make any more replies, so I have to use this comment. Thank you very much for the help.
I’ll try doing this tommorow
That’s not a side note. Hang on
I’m not quite sure how this works but you have got fastboot there with sudo so you should be able to run the flashing script with sudo. Maybe.
Or perhaps better to try sudo fastboot boot twrp.img.(replace twrp.img with actual recover.img name obviously)
Indeed. This means almost certainly that you don’t have correct udev rules.
This must be fixed before you do some other damage!
I realise that you cannot reply, but when you get the phone correctly responsive preferably without sudo …
that is sort out udev rules …
I would feel that I would need to get stock Android R on board.
This is not the same output as you reported earlier today.
“no permissions; see [http://developer.android.com/tools/device.html] fastboot”
This is quite significant to the enabelment of proper comms with udev rules 
It is explained here https://developer.android.com/studio/run/device.
I just noticed, this is the link they already gave you!
For a Debian type system it is as simple as
sudo usermod -aG plugdev $LOGNAME
sudo apt-get install android-sdk-platform-tools-common
Edit, @eggnogg this message sounds very harsh or re-reading. I do apologise; it was intended to only stress the importance of the point, in case going too fast did not lead to the best outcome.
Good luck.