<dazinism "If its booting with verified boo"> Worked for me when I had WiFi memory leaks, that caused the phone to crash every time I tried to turn on WiFi, a couple of months ago.

Autopsy: interesting, my guess is that something you did post install changed something that caused this. Had you tried a device reset first (if so I'm a bit surprised / confused)

Only thing I can think of that I've heard thats caused something to be different is when someone had flashed a beta of Android R

Think they ended up with some newer firmware somewhere

Which made Auditor fail on Audits

GrapheneOS installation/updates should give you the latest stable firmware on components - but can't necessarily downgrade if they've already have a alpha/beta firmware upgrade.

There a chance I'm misunderstanding something, but thats currently how I think it all works on the Pixels....

dazinism: you can't downgrade a beta build unless the stable is newer

you are correct

it has to do with what is signed

if something older was signed as newer it would work ofc

<dazinism "Autopsy: interesting, my guess i"> Nope, didn't do anything whatsoever. Followed the guide on the website and I was getting memory leaks. I then updated to the latest Google Stock and then reflashed GrapheneOS and it has been fine since. I did try a device reset, but it didn't help - I was still getting memory leaks.

I didn't even set any private DNS settings. It was just crashing. Anyways, that was two months ago

Interesting. You mean it was doing this on a fresh install of the latest GrapheneOS?

(latest at the time)

Autopsy And you reflashed with the same factory image?

Yep, all on fresh install and yeah it was the exact same factory image (I did download another one, but I checked the hashes, signified it and it was fine).

Oh.... wonder what happened there then

The ONLY thing I did differently was: the first time, I updated to latest Google Stock on OTA. Second time, I used their website installer.

You used source.android.com/setup/contribute/flash ?

Or you mean you downloaded a factory image from them?

Or the Pixel Repair Tool ?(possibly only works in the US - although guess you could fool it with a VPN)?

dazinism using this site developers.google.com/android/images you can flash through the browser. This is for coral: flash.android.com/welcome?continue=…5%3Ftarget%3Dcoral-user%26signed%3D

* dazinism using this site developers.google.com/android/images you can follow the links to flash through the browser (you can also download the files from there, too). Following the "flash" link for your specific device, you can flash stock Google straight onto a Pixel or Nexus devices. This is for coral: flash.android.com/welcome?continue=…5%3Ftarget%3Dcoral-user%26signed%3D

So yeah, Android flash tool

trying to flash grapheneos on pixel 3a, booting it into fastboot and all commands from my pc to phone return as failed, immediately. the phone is visible to pc in fastboot, fastboot ver 30, oem unlocked, usb debugging turned on, but i cannot get to the step where i have the bootloader unlocked, and i assume i will not be able to flash anything on it as well. advice?

i dont live in USA, device was bought from one store selling electronics, didnt come with any plan etc. BUT, my device does have ONLY ONE IMEI when i go for barcode readout. does that mean it's still a blocked version?

belay_that_order: you managed to flip the OEM unlocking toggle in developer options?

<dazinism "belay_that_order: you managed to"> i managed

the thing is that it's behaving as if i didn't

I would suggest trying different usb lead or port

even though i am able to transfer files via this lead and port, and give commands via adb?

Yeah I think its definitely worth trying that still

Think fastboot is a bit more demanding on all the usb stuff being right than adb or file transfers

If your using usb C to USB C, try A - C

Often usb C isnt set up correctly in PCs

i did try, but it wasnt even visible to my os

Try what?

do you have any bullet proof cables to susggest?

try another cable

it was a - c

If you can try different cable(s). Also different port(s)

Maybe even try and flash from a different computer

ok, that would be a much softer solution than having to change a phone

do you have any bullet proof cables to suggest?

I've had success with the cable that came in the box from Google

Which was a - c

Sorry no I lie

That was c-c

I used a genuine anker a-c (there are bootlegs about)

<belay_that_order "do you have any bullet proof cab"> Official Sony ones, USB A to C have worked for me. The one from the box didn't work.

<Autopsy[m] "Official Sony ones, USB A to C h"> have a link handy?

Mine came in an Xperia box, so no.

To try and ensure I got genuine Anker I bought off them via Amazon.

But why genuine Sony one should be fine.

Anker are top quality too tbh

Recently got a genuine usb a - c adaptor from ebay as my friends 2 year old magicked my original into a different dimension

Of course the new one isnt genuine

And doesn't work with my usb key (so no seedvault backups)

😠

🎻

But I hear Amazon dont really care about bootlegs. Hopefully getting one sold via Anker on Amazon would mean you get an original...

thank you all for your inputs

Maybe anker a-c via eBay is my next move....

I mean via amazon

dazinism: yeah looking it up now

do you have another phone?

try flash.android.com via that - it'll unlock the phone

i dont actually have another phone

i am going to go with a cable first, as i am afraid that after unlocking, flashing of the image might go wrong

<belay_that_order "i am going to go with a cable fi"> It won't

Thanks to the devs for the custom ROM 👍 just wondering when the 3aXL should expect the next security update?

<lickidysplit[m] "Thanks to the devs for the custo"> Something something it's not a ROM, it's an OS. Secondly, when it's ready.

are pro's on device porting to graphene OS ?

I have a device and all the sources (mtk based), would pay for the effort of course

Logs from two days ago in this channel have: "MTK devices are a security nightmare would be a waste of time"

I cant flash GrapheneOS in my Pixel 3a XL. Everything works fine but the flashing itself. Any ideas

<rip_mca[m] "I cant flash GrapheneOS in my Pi"> Follow the instructions and you're good to go. Download the link given in that instructions.

I strictly followed the instructions in the GrapheneOS Website.

Everything should run the latest version. Your Pixel OS.

You should check Techlore's video for GrapheneOS Error installation.

rip_mca: that's not powershell

follow the instructions on the website, and put a thumbs down on whatever video you used

since you are not setting fastboot on the path, if you open new windows that don't have the path to it set, it will not appear

so dont open new windows while following the steps on the website

This is what I said before about the documentation

Download platform-tools to downloads. Extract it. In terminal (or PowerShell) type $env:Path = "$pwd\platform-tools;$env:Path" in the actual downloads folder, NOT in the platform-tools folder.

When I get home, I'm gonna write a GrapheneOS Installation for Dummies lol

jpds, by default that may be the case, but replacing the aosp to graphene is a step in the right direction

the rest of the security will be replaced too

kkkkk: freenode.logbot.info/grapheneos/20200906#c5012781

yeah that was me actually

Thanks for your help. The hint with Powershell was the solution!!!

The rest was easy

jpds, are you good with device porting ?

Could someone enlighten me about GrapheneOS and filesystem encryption. When I recently installed GOS I just gave a pattern to unlock the phone. Now when I look in settings the phone tells me that it is encrypted. But I wonder if there is enough entropy in that pattern. Could I have one strong password to unlock the phone at boot and a simpler

pattern to unlock the screen?

Also could I have an other pattern that would encrypt the filesystem, i.e. one would have to enter the strong password again?

Realisticly, how much do I gain by switching to graphene, from omni when Im already using only foss apps? Apart from the obvious security enhancements that is..

... is privacy ;) no google services!

No gapps C:

anyone here who would port graphene for money ? :(

<renex "Could someone enlighten me about"> The real encryption key is on the Titan chip. The pattern only unlocks that chip.

Titan chip?

Titan M is the full name. Basically it is a separate chip that stores the encryption key for the phone. This article explains it better than I can: wired.com/story/google-titan-m-security-chip-pixel-3

Ok, thanks

When you change your screen PIN or pattern, the actual encryption keys do not change (re-encypting the phone would take a long time) but because it is really hard to access the tiny Titan M chip the encryption keys are still safe.

I have been thinking about getting a pixel and installing graphene. In my search, I came across the following site freedomphones.net which offers graphene preinstalled on a pixel and am curious if they are known in the graphene community?

Price tax too expensive

And not affiliated to GrapheneOS in any way

Ok. Thanks.

Not sure if they even donate such price tax, we can just offer to help you flash it

"Can I have you pre-load some of the secure apps on my phone before shipping so I can use them right out of the box?"

That is also not good

There is a premium. I am just beginning my research but I would have to buy a used phone and then install it. I don't yet have a sense of what the risks of bricking the phone are if I were to install it myself.

<cdesai ""Can I have you pre-load some of"> Yeah, it's probably modified too

<adsfasf "There is a premium. I am just be"> Well, bricking risks is next to nonexistent

Due to A/B partition scheme

Iirc?

(Somebody needs to confirm this)

<adsfasf "There is a premium. I am just be"> Not much of a risk if you ask me. Make sure you either have a usb C port, or have a working A to C cable

And also just reading the instructions properly

Thanks.

You're welcome

Since I would have to purchase a phone, my inclination would be to go with a Pixel 4 or Pixel 4XL with 128 gig. Is this reasonable?

<adsfasf "Since I would have to purchase a"> Yes

Depends on your needs and budget but yeah

Thank you for your help!

Love the project

:)

Is there a specific area of focus for development at the moment for the os?

Probably android 11

Which just dropped today

i would like to say thank you

really

my pixel 4 not XL stayed for almost 10 days on stand by with 4g on

only graphene preinstalled apps

Has anyone tried algo vpn on graphene (github.com/trailofbits/algo)?

So when approximately is GrapheneOS getting Android 11?

a0e0e753: It just uses other open-source VPN tooling like WireGuard and IPsec

Exactly

So it should not be a problem

Not at all

Great!

What are people finding is the best use of the camera on graphene? Open camera do a good job at things and what are peoples thoughts on the use of Google camera within graphene? Does that then nullify too much of what graphene brings to justify its use?

Saying that as a pixel 3 user who does quite like the quality and features of the stock camera etc

faxing: the source code hasn't even been pushed for AOSP yet

faxing: in general, we don't offer timelines for development, but you're asking for a timeline for something that couldn't have even started development yet

if you want it to happen soon you should work on it

AOSP support has to be brought up for each device along with porting all of the GrapheneOS changes to the new Android 11 tags (that are not yet available)

devices without maintainers / developers to do the porting work will be dropped

features that aren't ported will go away

so it's likely the Pixel 2 will be dropped this month, and perhaps other devices, and many features will probably be dropped, only what people are interested in keeping will be kept

Having used stock 9 on my OG pixel and 10 on my newly acquired pixel 3 which iv just jumped onto beta channel 11 preview doesn't feel like a huge amount of features are there that make it that intriguing yet

that's not really relevant

migrating to Android 11 is important and time sensitive

Oh for sure

if the project lacked the resources to do it quickly, it would be discontinued because it would no longer be providing something useful or sensible to use

<3

it's possible that going forward not as many devices can be supported since there aren't maintainers for most

and most features will initially be lost to keep things going

help wanted

I haven't decided if there will be another release based on Android 10, I don't think there are the resources to do that

so development will be fully focused on bringing up the new version of the OS based on Android 11

definitely not going to be a timeline or a clear idea of which devices will be supported going forward

Well up until the other day I was just on an OG pixel and once I got a chance to make a bit of an upgrade financially found a great deal on a pixel 3 (£190 boxed in basically new condition) I would like to try and help on that front. Not to say I am streaks ahead on the knowledge front but have had experience over the years with custom ROM stuff and testing stuff in early stages etc.

atm not much that can be worked on yet since it's still in the process of being released

other than what could have already been worked on based on the earlier previews

For sure

most devices don't have maintainers so there weren't people doing the preparation work

I didn't even realise it was now into the wild having just got the beta 3 build to have a nose around

it was possible to get the kernels ported based on the beta tags along with getting android-prepare-vendor ready

Well if I knew coding then I'd help but I can't code.

unfortunately there is not much interest in contributing like that

so please do not expect a quick turnaround when the preparation work that was needed is incomplete and most devices lack maintainers

and by the time I learned how to, and to a standard of the project, it very well may be useless at that point.

my time and energy is currently focused on dealing with attacks being made on the project and myself by malicious people

so I'm not focused on development right now

not the priority for me

there are other people that started working on the preparation work for porting

they need more help working on that especially if it's going to get finished any time soon

<strcat[m] "my time and energy is currently "> Where those attacks are being made? I meant on an online forum or something?

that's not what I'm talking about

I suggest reading the history section on the site for some background

read past logs here

not going to go through all of it for you sorry

I am aware of the Copperhead - Graphene situation.

I remember we had some trollers here in matrix in last month posting gore stuff.

I've been up all night working on stuff so I'm about to finally go to sleep and when I wake up hopefully the new tags will be pushed and I can start directing people who are interested in working on it

The situation on that front sounded like horse crap. Always seems to be the case on good ideas by good people getting dragged into a whole mess that could have basically been avoided and so on. Seen similar albeit less overt things happen between Foss community members on custom ROM stuff in the past and just found it all a bit saddening

Sadly the world we live in makes those situations more frequent and often times more dramatic/detrimental than they really need to get. Props to you for the project though. Piqued my interest just based on the ethos along with the ease of installation so far etc. Lot more straight forward than was expecting when I started out

I have a pixel 4a and would like to be a guinea pig for the Android 11 version of GrapheneOS. Is there somewhere I can be contacted if someone needs me to test features etc?

hi

I don't know what the following statement means. Please tell me.

Avoid using hidden APs (i.e. APs not broadcasting their SSID) since known hidden SSIDs end up being broadcast to find them again. SSIDs are not broadcast for standard non-hidden APs.

bob52: Don't use hidden WiFi points

<i_am_your_device "I have a pixel 4a and would like"> well, there is no work yet there to begin with

<i_am_your_device "I have a pixel 4a and would like"> Well, the patches and some features have to be ported first and the OS has to be built

Maybe if you are willing to try learn how to port and build an OS, perhaps you can test it yourself

no

look it

wut is it mean?

Avoid using hidden APs (i.e. APs not broadcasting their SSID) since known hidden SSIDs end up being broadcast to find them again. SSIDs are not broadcast for standard non-hidden APs.

I don't understand the above explanation.

bob32: It's saying to never connect to a non-broadcast access point, as every time you go somewhere your device will call out looking for that access point

d64qoc8432li8p9o Is there any work on 4a at all? Even Android 10? I know how to build images and have a lot of programming (javascript) experience but I don't know too much about the android ecosystem. Is there an example (or better yet a git diff) that shows you what's needed to add a new device? :S

What is a broadcast access point?

bob32: Any WiFi point that's not displayed when you open the WiFi list

bob32: You can still connect to hidden WiFi networks by manually entering their name

bob32: If you've never done this - it is not a problem for you

I see. Haven't you seen him in town?

<i_am_your_device "d64qoc8432li8p9ouijtv Is there a"> grapheneos.org/build

bob32: Not sure what you're asking

Anyone else have a hard time getting their laptop to see their pixel is plugged into it? Others phones work fine and I have USB debugging on

Thanks, I will take a closer look and try to get something to build.

<dexlibre[m] "Anyone else have a hard time get"> Is your phone locked?

Negative

When you plugged it

Try replugging when unlocked

And check the security settings and make sure it's at default option

"allow new usb peripherals when unlocked"

It's described in the wiki as something to be aware of when connecting to free wifi, but don't you see that kind of wifi? That's what I'm talking about.

It's not about free WiFi points

Huh? Do you have anything other than a wireless phone? Are you talking about tethering?

> <@d64qoc8432li8p9ouijtv:matrix.org> And check the security settings and make sure it's at default option

> "allow new usb peripherals when unlocked"

Yeah it's set to that :(

bob32: Do you know what an SSID is?

Nevermind, I suppose you've never connected to a hidden WiFi network before

yeah

exactly

<dexlibre[m] "> <@d64qoc8432li8p9ouijtv:matrix"> Is this adb?

Just asking

bob32: It's a network that's there, but the admin has configured it to not be publicly listed in the WiFi list

<d64qoc8432li8p9o "Just asking"> I have adb on this laptop I'm trying to connect the pixel to. It shows up when I run adb devices

That means don't enter the SSID manually to connect, right?

<dexlibre[m] "I have adb on this laptop I'm tr"> It's working fine for me

Not sure if it's port issues

On your side

(Like try cleaning the usb C port?)

<d64qoc8432li8p9o "(Like try cleaning the usb C por"> Will do thank you! It does charge it

Android 11 is out

nice

rip fdroid ?

They aren't using that API level yet

Do you have opsec on irc?

I've got an ip and propider exposed from my irc account.

And now you can see that I'm using a riseup vpn.

<cn3m[m] "Android 11 is out "> meanwhile my old galaxy is still on pie lol

wa[]ge[m]: cn3m[m]inrdrna[m] Why is the gateway to matrix.org hidden?

Hey

Does anybody know where the R factory images are?

Nvm got it

I'll start bringup now

FDroid finally have an issue up for moving to v2 / v3 sigs

we had discussed it, just didn't have an issue

Theres already some SDK30 apps on their repo

Yeah, I know....

I did have a warning put in for that, do you have an example

we do want to get it working soon, there's some other signing related changes going on too which should improve things overall.

Apparently won't be a load of work to get all the apps they build sign with v2 / v3

Appropriately enough SDK Monitor

Also NetGuard

Both on SDK30

thanks

Find it very funny that google needs to give fdroid a kick in the pants to get them to improve their processes

Even funnier that they still rely on sha1

yeah but when will they do it

Is there anyone here today who can tell me if I can verify an untrustworthy device with the Auditor App? Or can you only verify that the software has changed, but not if it is really GrapheneOS?

anyone able to help? i have a fastboot too old error

pheonix3082: read the guide and download android-tools standalone

i did that. i was using techlore to do the install too over powershell but it keeps returning me the error

why are you following a video when there is a very well, tested and up to date official guide ?

* why are you following a video when there is a very good, tested and up to date official guide ?

because the same error occure

occurs rather

<sandroteem[m] "Is there anyone here today who c"> ?

Hello

BTW

Where's the R source?

<cooperlead "Hello"> strcat

strcat

What a troll

is anyone able to help?

yea the problem is probably because you don't use the official guide

Tbh pheonix3082 if you want remote support I can do it

But you must decide fast. I have 30 mins at best

blueuser: as ive said. I used it. thats the reason i used techlore. and im also using a windows system not mac or linux

<anupritaisno1[m] "Tbh pheonix3082 if you want remo"> i appreciate that but no thankyou

K

<sandroteem[m] "?"> If you look on the release notes, you'll see what devices are supported

sandroteem play.google.com/store/apps/details?id=app.attestation.auditor is the easiest to see what is supported

pheonix3082 where are you getting stuck?

Fastboot too old, just read

pheonix3082 freenode.logbot.info/grapheneos/20200908#c5031424

<Autopsy[m] "pheonix3082 where are you gettin"> i click the flash-all.bat the command line flashes and does nothing. when i try o do it from inside the command line it tells me fastboot is too old. so i removed adb and reinstalled platform tool

Simple fix, don't sweat

So, open PowerShell as Administrator in your Downloads folder. NOT platform-tools. In the Downloads folder on PowerShell, type $env:Path = "$pwd\platform-tools;$env:Path"

And DO NOT close PowerShell. Ever.

Assuming the files are in your Downloads folder ^

they are =]

I would also recommend NOT putting all the files in the platform-tools folder (I think that's what Techlore does in his video, iirc). Just extract them into their own folder.

<Autopsy[m] "So, open PowerShell as Administr"> Once you've done this... Run fastboot --version and see if it matches the most recent one you've downloaded.

<Autopsy[m] "I would also recommend NOT putti"> When I say all files, I mean the GrapheneOS files from the website.

ok

So, in the Downloads folder, you should have..

A platform-tools folder and a folder for GrapheneOS.

yes

Have you run the command in the downloads folder and verified using fastboot --version? $env:Path = "$pwd\platform-tools;$env:Path"

This is the trickiest part imo. Afterwards, the script does the rest for you.

yes

fastboot version is the same platform tools one ive downloaded

Excellent

Now, do not close PowerShell

You can now change the directory to where the GrapheneOS files are stored (the flash-all.bat file)

So, if you made a folder called GrapheneOS in Downloads and your PowerShell is in Downloads already, just type cd GrapheneOS and press enter.

Sorry if I'm teaching you to suck eggs, I don't know your level

no thats ok. ive dealt with noobs for other things before lol

Nice one. So just run the .bat and you should be good to go.

yay!

thankyou very much =]

99 times out of a 100, it is that step that people mess up on.

You're welcome

Now cross fingers you don't get stuck on "waiting for device". That'll mean your USB cable is shite and you'll need to try another port or try another cable.

Hey, Id like to swap to a grapheneos phone. the 3a is too huge for my taste and hands but the 4 is too expensive and lacks the headphone jack. Now when to expect support for the 4a? Would it be worth to get more money for the 4 or should i wait untill 4a will be supported? Thx

hahaha. I luckily have decent wires

<chimeyy[m] "Hey, Id like to swap to a graphe"> At the mo, I believe there isn't a date set in stone. I haven't seen if anyone is currently building for the 4a (I know cdesai is doing it for CalyxOS, but not sure about GrapheneOS).

If anyone has a 4a and wants to help port, feel free to ping me for pointers

cdesai: where's R source

Usual place

Where

Huh

It's there now

Could have swore it wasn't

<Autopsy[m] "sandroteem play.google.c"> My question was not a support question. I try to understand what the protocol can ensure and what not.

hello folks.

Is project-fi pixel2 can be unlocked?

yes, so according to this and the website Pixel 2 is supported, legacy.

I can't unlock it following the instructions and I was wondering if that's a known issue

"fastboot flashing unlock" just says waiting on device. The cable works and I can mount the phone just fine when it boots in a regular manner

I turned on developer options as instructed, unlocked from the setting menu...

overheadscallop

You're up for testing my bs?

I'll join you too on the weekend

if anybody wants to build AOSP R: gitlab.com/-/snippets/2013092

once that's done, a port can start, piece by piece.

anupritaisno1: Yeah, just message me whenever and I'll get around to it.