GrapheneOS version 2026061800 released

gh0stcassette

grayway2 It's not up yet.

pizzadequeso

Suggestion to GrapheneOS devs:

Add the 1gb junk file to 2026061600 and call it 2026061610 so side loaders can do their thing.

No need for a workaround since most users can update via OTA. Make the file be deletable after update. Problem solved.

harp

@"wizoatk"#p240424 026061800 has the workaround

You're right in this point, my bad. The workaround which was announced and delayed this release was about the ability for sideloading from this Android 17 release to future releases, not from previous releases to this one. And that's included, right.

So this paragraph of my previous post:

harp I can't speak for GOS, but it seems to be a bit more difficult to provide a workaround, so they decided to publish this release anyway, without that workaround, not letting people wait any longer, who don't necessarily need updating via ADB-sideloading.

is not accurate.

And so related to that:

xxx Sorry I thought there's already a workaround integrated.

https://grapheneos.social/@GrapheneOS/116771724030142359

the workaround is included as announced in that linked Mastodon-post:

Our workaround will provide working sideloading from our initial Android 17 release to a future release. However, it isn't currently possible to sideload from 16 QPR2.

Edit: The cited post above by @wizoatk was deleted(?)

Pocketstar

mio I only update by adb sideload. I really need a 16qpr2 version that could update by adb sideload

Perhaps you can backup everything on the device and start with a new Android 17 installation instead? Updating from Android 16 to 17 may not be possible through ADB, but I believe you can do a new installation by using the full GrapheneOS image of Android 17 when available. (Please correct me if I'm wrong)
It is alot more work though because it requires a factory reset/deletion.

StupidMonkey

Any hope for those stupid monkeys like me who somehow skipped the most important part and sideloaded this update despite the warning: Will a future release allow me to fix my device without a factory reset? 😬 I'm in bloo loop hell right now (coming from 2026061600 on akita).

StupidMonkey

StupidMonkey Just to clear this up. I waited a bit for the the device to boot loop a few times. It then booted into the previous version / rolled back the update. Phew.

Johnnyloans

grayway2 my expectations are 6 to 12 months additional support by GrapheneOS for the Pixel 6 and 6 Pro.

We don't know if that'll happen.

de0u

mio I only update by adb sideload. I really need a 16qpr2 version that could update by adb sideload

That may occur over the next few days, but for the moment I suspect they are mostly focused on testing A17.

de0u

grayway2 My expectations are 6 to 12 months additional support by GrapheneOS for the Pixel 6 and 6 Pro.

That could happen in theory, but I would not make plans based on that happening. They did that for 4's and 5's, but at the time they said it was because those devices had gotten only three years. Also, now they have a lot more device types that are in-support than before.

If Google decides to extend support, that is a different story.

grayway2

de0u You're correct. GrapheneOS is supporting 5 generations of Google Pixels devices. We don't know what Google will do later. They might push a security update in 1 month or 1 year later after October 2026 or just put them in a museum.

GazelleInitial

I assume this will have desktop mode now in graphene?

wizoatk

StupidMonkey

That's what it's suppose to do. If for some reason it was damaged further, then someone would have recommended to try booting into recovery and then sideload the latest android 16 version 202606160(0/1).

wizoatk

mio I only update by adb sideload.

There are more than a few people in this situation. It's being worked on.

From the release notes:

We're working on a resolution to updating via sideload from a previous release. If necessary, we could make a final release based on Android 16 QPR2 with the same workaround solely released for people who only update via sideloading.

AcclaimSublevel19

mio I only update by adb sideload

I've seen many people say this and I've been wondering what the reasoning behind this is. Can you please enlighten me?

Wynnded

AcclaimSublevel19 They may have reasons for not wanting to allow their devices to connect to a mobile service or a WiFi network.

abdullah

Are experimental releases (not alpha) public?

Edit: nevermind, will check matrix

« Previous Page