where I can download rom from official servers ? no 3rd app or something?
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
Oxygen Updater
Oxygen Updater is an open-source app for OnePlus devices that allows you to install official OTA (over-the-air) updates ASAP. Ensure your device is up-to-date — it's quick, easy, and free!
oxygenupdater.com
LuisCarlosHK said:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
Oxygen Updater
Oxygen Updater is an open-source app for OnePlus devices that allows you to install official OTA (over-the-air) updates ASAP. Ensure your device is up-to-date — it's quick, easy, and free!
oxygenupdater.com
Click to expand...
Click to collapse
thank for the reply there isn't a link download for stable version in the oneplus community
I don't want use oxygen updater
I'm paranoid about this
is there a direct link from oneplus official server?
LuisCarlosHK said:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
Oxygen Updater
Oxygen Updater is an open-source app for OnePlus devices that allows you to install official OTA (over-the-air) updates ASAP. Ensure your device is up-to-date — it's quick, easy, and free!
oxygenupdater.com
Click to expand...
Click to collapse
OnePlus 10T is getting its stable Android 13 update with OxygenOS 13
With an outdated security patch.
www.xda-developers.com
Just FYI, even the above link does not contain official OTA mirrors. OnePlus does not provide those anymore, the only way is to use Oxygen Updater. The App devs reversed engineered the OTA servers endpoints and are mirroring the download links.
You have to thank the Oppo merger for this nonsense. The last Phones they released full firmware for, directly on their site, is the 9pro. It's the same reason that MSM Tools ain't available either and we dont have an unbrick package for this phone.
seanwlk said:
Just FYI, even the above link does not contain official OTA mirrors. OnePlus does not provide those anymore, the only way is to use Oxygen Updater. The App devs reversed engineered the OTA servers endpoints and are mirroring the download links.
You have to thank the Oppo merger for this nonsense. The last Phones they released full firmware for, directly on their site, is the 9pro. It's the same reason that MSM Tools ain't available either and we dont have an unbrick package for this phone.
Click to expand...
Click to collapse
If i had known there was no more MSMtool for current oneplus devices i wouldn't have bought my 10T 5G but alas it's too late already paid and got it, great phone ....bad company the way they've gone down the pay to unbrick route...shame on them. Oneplus does not exist anymore. Kinda glad i still got my mint 7T as a safe backup!.
seanwlk said:
Just FYI, even the above link does not contain official OTA mirrors. OnePlus does not provide those anymore, the only way is to use Oxygen Updater. The App devs reversed engineered the OTA servers endpoints and are mirroring the download links.
You have to thank the Oppo merger for this nonsense. The last Phones they released full firmware for, directly on their site, is the 9pro. It's the same reason that MSM Tools ain't available either and we dont have an unbrick package for this phone.
Click to expand...
Click to collapse
there are official links for android 12 but no for 13...
embarrassing
Related
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
You most probably will not. Snapdragon phones have better development, for example, the Redmi 4A did not have kernel source till recently, yet we had bugless Nougat ROMs, and now with source we have Oreo. It all depends on developer support, Oppo is not a brand that interests developers, on top of that it is a Mediatek phone, your custom ROM dreams may well be shattered. A few ported ROMs may be made if any developer decides to make it but will most likely be too buggy.
SouradeepB said:
You most probably will not. Snapdragon phones have better development, for example, the Redmi 4A did not have kernel source till recently, yet we had bugless Nougat ROMs, and now with source we have Oreo. It all depends on developer support, Oppo is not a brand that interests developers, on top of that it is a Mediatek phone, your custom ROM dreams may well be shattered. A few ported ROMs may be made if any developer decides to make it but will most likely be too buggy.
Click to expand...
Click to collapse
True.But oppo has never released a phone like this.
This phone has the same chipset(helio p60) of oppo f7 which is two times more costly than the realme 1.Therefore it offers immense value for money.And this will attract a lot of customers.Normally when a device has a huge customer base and if it is a value for money device, developers usually become interested in those devices.
Also I know know that both mediatek and oppo have violated GPL many times by not releasing the sources.But since this device is treble compatible,it should solve that problem to a certain extent right?
I am open to discussion...
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
Yes it will help, as project treble is a initiative by Google to help developers create custom roms without approaching Vendor(Oppo) or the Manufacturer(Mediatek).
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
Their response shown below,
We understand that you want to give root access to the device and we apologize for the inconvenience caused.
As per the policy, it is not suggestible to root the device. However, if you want to root the device, you can root it using any third party boot-loader on your risk. We won't be able to assist you with any information regarding the rooting of device.
nisanthu said:
Their response shown below,
We understand that you want to give root access to the device and we apologize for the inconvenience caused.
As per the policy, it is not suggestible to root the device. However, if you want to root the device, you can root it using any third party boot-loader on your risk. We won't be able to assist you with any information regarding the rooting of device.
Click to expand...
Click to collapse
I don't need root access, but there are issues with Color OS 5.
Like:
1. New notification pop appear for 3-4 seconds and you cannot swipe and close them, you need to wait to automatically close them, hampering your work. In other OS you can simply swipe left/right/both to close popup.
2. If you enable development option, then yellow notification will show constantly to close it, until you close mode. Why can't I use function like mock location, etc.
3. If you use app which use accessibility services (like Greenify) then it will constantly show notifcation bar sign to close, it means you cannot use Developer Mode or Accessibility Services Apps.
Hope Oppo will fixes these issues with Color OS in future updates.
""1. New notification pop appear for 3-4 seconds and you cannot swipe and close them, you need to wait to automatically close them, hampering your work. In other OS you can simply swipe left/right/both to close popup.""
HERE IS SOLUTION FOR YOU> SWIPE UP to CLOSE
Ayyshjaju said:
I don't need root access, but there are issues with Color OS 5.
Like:
1. New notification pop appear for 3-4 seconds and you cannot swipe and close them, you need to wait to automatically close them, hampering your work. In other OS you can simply swipe left/right/both to close popup.
2. If you enable development option, then yellow notification will show constantly to close it, until you close mode. Why can't I use function like mock location, etc.
3. If you use app which use accessibility services (like Greenify) then it will constantly show notifcation bar sign to close, it means you cannot use Developer Mode or Accessibility Services Apps.
Hope Oppo will fixes these issues with Color OS in future updates.
Click to expand...
Click to collapse
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
It confirmed via email. The reply is given below:
"Thank you for writing to RealMe Customer Service regarding Project Treble inquiry.
We are delighted to inform you that your RealMe 1 device supports Project Treble. It is already enabled in your device."
But after some researchs i realised that even if it could support project treble, we still can't flash GSI rom with a locked bootloader. (Correct me if it is a wrong findings)
best customm rom
which is the best custom rom available for realme 1 ?
mygadgetreviewer said:
which is the best custom rom available for realme 1 ?
Click to expand...
Click to collapse
rightnow none..
root is not possible yet..
Any chances of custom roms that may pop up for realme 1
I am buying a new phone soon. I would like to know if realme 1 will get a custom rom? Please reply quick. Also when do you think the custom rom will be available?
custom rom
kindly worked custom rom,how can flash twrp?
Firmware
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
Is realme 4gb version firmware available? Please provide the link of stock firmware.
Any update on bootloader unlock and rooting..?
Realme 1 support project terbel
:good:
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
The realme 1 support project terbel I used the to check and it's shows that it support
confirmed the realme 1 and 2pro are getting bootloader unlock
Confirmed by realme CEO madhav Seth realme 1 and 2pro are getting bootloader unlock and kernel source code confirmed on twitter by him
Sailfish os
I want sailfish os for our realme device
Bootloader unlocked finally
Realme 1 has got bootloader unloccked when can we expect to get custom rom now
Imrans123 said:
Realme 1 has got bootloader unloccked when can we expect to get custom rom now
Click to expand...
Click to collapse
You need to wait for kernel sources to get released so devs can work on custom roms. If we get a TWRP recovery, you can try out the A/B GSI roms which are good but slightly buggy. If you want a bugfree rom, you need to wait a while, maybe a month or so.
Thanks bro when can we expect releases of kernel source another quarter
Hi, Will We Get Oreo update officially by MiUi ?? And if we do get the update , Will We Get Official Treble Support For Our Vince??
imgh0st said:
Hi, Will We Get Oreo update officially by MiUi ?? And if we do get the update , Will We Get Official Treble Support For Our Vince??
Click to expand...
Click to collapse
These are official releases https://forum.xda-developers.com/redmi-note-5/how-to/rom-miui-10-global-links-t3812118 just in beta phase, soon will appear stable releases.
About official treble support is highly unlikely that we get it; devices that will be released in the future running oreo out of the box they´ll have probability but miui and in general all brands are not very interested, they want that client buy a new device as fast as possible and they don´t pay many attention to after-sale for customer care.
SubwayChamp said:
These are official releases https://forum.xda-developers.com/redmi-note-5/how-to/rom-miui-10-global-links-t3812118 just in beta phase, soon will appear stable releases.
About official treble support is highly unlikely that we get it; devices that will be released in the future running oreo out of the box they´ll have probability but miui and in general all brands are not very interested, they want that client buy a new device as fast as possible and they don´t pay many attention to after-sale for customer care.
Click to expand...
Click to collapse
Thanks for sharing the news...
I usually run LOS without GAPPS to have as little Google in my life as possible. LOS because it has active development, seems like a professional operation, gets security updates every months and supports many devices, and it seems the majority of other ROMS are based on LOS.
But there are so many other ROMs available for F1 so I'm wondering if there are any other serious ROMs for F1 that aren''t based on LOS that have been degoogled, are good for privacy, and have stable support.
Maybe in future some dev might port Sailfish OS. That's the most privacy friendly mobile OS.
For now Lineage 16.0 without Gapps is number one.
ubuntu touch is grt ...linux based community support
/e/, but I don't know whether Poco is supported. See the e.foundation website for further details.
guhvanoh said:
/e/, but I don't know whether Poco is supported. See the e.foundation website for further details.
Click to expand...
Click to collapse
supported oreo
i m afraid to flash that coz mi anti-rollback feature
I'm almost sure the anti rollback feature is disabled on our beloved poco but you can still check on with fastboot according to a reddit thread I cannot link for some reason.
SerpentSpirale said:
I'm almost sure the anti rollback feature is disabled on our beloved poco but you can still check on with fastboot according to a reddit thread I cannot link for some reason.
Click to expand...
Click to collapse
ya! i checked it.score 1,means no anti- rollback
type fastboot getvar anti
if it show no 1-3 then no anti rollback enable
above 3 means rollback enable for pie
above 4 means rollback enable for Q beta
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
2) I also noticed that TWRP is not available for Moto G Power (2021), is there a good alternative or I have to use adb fastboot?
Thanks!
Edit:
I just found the thread:
[RECOVERY][UNOFFICIAL] TWRP 3.6.0-11 [BORNEO] Android 11 Based (updated 12/11/2021)
I can try that for question 2
Efone said:
Hi guys,
I am forced to upgrade my moto G5 plus due to a network update
In my moto G5 plus I have installed dotOS with android 11 and I am really happy with it, and I would like "clone" it on a Moto G Power.
Here are some questions:
1) since Moto G Power (2021) is not listed on dotOS but a GSI ARM64 available, has anyone experienced with that? I am also open to other custom ROMS (also Lineage OS doesnt have this devicelisted)
Click to expand...
Click to collapse
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
1) unlock bootloader
2) flash twrp in recovery
3) flash blankflash.zip (or official?) through twrp
4) flash magisk through twrp
5) restore my old phone dotOS android 11 backup through twrp
and I should have all the apps and data as in the old device?
Efone said:
Hi Onoitsu and thank you for the reply,
so I guess I could go with the stock ROM. I noticed that I can use https://mirrors.lolinet.com/firmware/moto/borneo/ has an official and blankflash (not sure what the difference is). If I understand the process correctly I could:
Click to expand...
Click to collapse
The blankflash is only if you can no longer flash anything by usual methods
Blankflash and EDL Mode
Is my device in EDL Mode?
How to boot into EDL Mode
Thanks for the info!
Should the reasoning above work if I use official instead of blankflash?
Efone said:
3) flash blankflash.zip (or official?) through twrp
Click to expand...
Click to collapse
Neither the blank flash nor official firmware are twrp compatible.
Thanks sd_shadow for the info, it is really helping me out.
I saw your post for using LSMA, but I couldnt find a Linux version. Is there one? Or the only other option I have is going through the fastboot process?
Can anyone tell me if there is going to be custom roms made for Borneo?
Hatrackman said:
Can anyone tell me if there is going to be custom roms made for Borneo?
Click to expand...
Click to collapse
Still the reason I cite in post 2 above, indeterminate, sadly.
Onoitsu2 said:
Still the reason I cite in post 2 above, indeterminate, sadly.
Click to expand...
Click to collapse
Mostly concerned because google has said they're going to stop their 'less secure app' thing at the end of this month and it might mean textnow will stop working outright for people that don't use play services.
Hopefully anyone working on making a custom rom for Borneo will see this thread and maybe give an idea if its going to happen.
Does this help?
If I wanted to start from scratch what would I need to know to make my own custom rom? Don't need a phone, will only ever use wifi. Just need microg basically.
The following statement is on the dotOS FAQs:
Q: My device is not supported! What should I do?!A: First reason can be that our development team doesn't have your device to support it or we no maintainer applied for this device. You can always use our GSI builds if your phone supports Treble Project.
Here we have this statement:
... Google requires every Certified Android device launching with Android 8.0 Oreo and above to support Treble.
Here borneo is listed as a supported device.
Does this mean dotOS GSI supports MotoGPower 2021 without the need of vendor blobs?
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
@sd_shadow
Two sites that potential rom developers may want to check out:
1) https://github.com/moto-common
check out: https://github.com/moto-common/andr...ernel/blob/12/dtb/bengal-moto-base-borneo.dtb
2) https://github.com/moto-sm6115
Scroll through the list of repositories, particularly in the moto-common site
@sdembiske that looks promising, I am willing to give it a shot and contribute to the community. Is there a good guide on how to build the kernel with vendor tree/blobs etc...?
Reference "Moto G Power 2021 XT2117-4 Firmware Extractions" - You will find the extracted kernel etc. in the boot.img extracted link that you can download - there are many other extractions that you hopefully can use to build a custom or AOSP rom.
Your best bet would be to add a pre-built kernel in the build - you can google that for how-to's.
Onoitsu2 said:
Presently I don't believe it is possible to have a custom rom as we need the kernel be released for it to have a chance, or a compatible similar device and its kernel.
Click to expand...
Click to collapse
The Xiaomi poco m3 has the same SoC and other innards as the Moto G Power 2021 and it also has unofficial Lineage OS 19 support. I am considering hitting them up and using their code as part of the build. I'm also requesting Motorola Mobility LLC to release the kernel source for Android 11. I already have a device tree for Borneo on my github. Me and Fazwalrus have a telegram chat set up for the ROM development here
Magisk Patched Unofficial GrapheneOS for the Pixel 6 / 6 Pro (oriole/raven)
This ROM will allow you to lock the boot loader. Do not ever disable the OEM unlocking checkbox when using a locked bootloader with root.
This is critically important. With root access, it is possible to corrupt the running system, for example by zeroing out the boot partition.
In this scenario, if the checkbox is turned off, both the OS and recovery mode will be made unbootable and fastboot flashing unlock will not be allowed.
This effectively renders the device hard bricked.
I am not responsible for any harm you may do to your device, follow at your own risk etc etc, Rooting your device can potentially introduce security flaws, I am not claiming this to be secure. If you would like to have more security and peace of mind then I highly recommend you follow This Guide to build this rom using your own encryption keys.
GrapheneOS is a privacy and security focused mobile OS with Android app compatibility developed as a non-profit open source project. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. It was founded in 2014 and was formerly known as CopperheadOS.
The features page provides an overview of the substantial privacy and security improvements added by GrapheneOS to the Android Open Source Project (AOSP). Many of the past features were contributed to AOSP, Linux and other projects to improve privacy and security for billions of users so they're no longer listed on the features page.
More info:
Official releases are available on the releases page (Not Magisk Patched) and installation instructions are on the install page.
GrapheneOS also develops various apps and services with a focus on privacy and security. Vanadium is a hardened variant of the Chromium browser and WebView specifically built for GrapheneOS. GrapheneOS also includes our minimal security-focused PDF Viewer, our hardware-based Auditor app / attestation service providing local and remote verification of devices, our modern privacy / security focused camera app, and the externally developed Seedvault encrypted backup which was initially developed for inclusion in GrapheneOS.
No Google apps or servicesGrapheneOS will never include either Google Play services or another implementation of Google services like microG. It's possible to install Play services as a set of fully sandboxed apps without special privileges via our sandboxed Google Play compatibility layer. See the FAQ section for more details on our plans for filling in the gaps from not shipping Play services and Google apps.
Installation Instructions: Fashing-factory-image
Locking the bootloader is Optional but does increase the device security Locking-the-bootloader
Update Instructions: simply follow these instructions Updates-sideloading to sideload the latest patched OTA update package (You can update from any previous version if using full ota update)
Android OS Version: 13
Current Version: See Post #2
Download: See Post #2
Sources: GrapheneOS - AVBRoot - Magisk - Patch Guide
PayPal Donation Link
Builds for Pixel 6 (Oriole)
Magisk-Patched GrapheneOS Factory Install Build
Full system install builds for clean and new installs
Build based on release#2023061402 (2023-06-14)
SourceForge_Download
Build based on release#2023050100 (2023-05-01)
SourceForge_Download
Build based on release#2023041100 (2023-04-11)
SourceForge_Download
Build based on release#2023032000 (2023-03-20)
SourceForge_Download
Build based on release#2023022300 (2023-02-23)
SourceForge_Download
Build based on release#2023020600 (2023-02-06)
SourceForge_Download
Build based on release#2023020200 (2023-02-02)
SourceForge_Download
Build based on release#2023012500 (2023-01-25)
SourceForge_Download
Build based on release#2023011000 (2023-01-10)
SourceForge_Download
Build based on release#2023010300 (2023-01-03)
SourceForge_Download | 1fichier_Download
Build based on release#2022122000 (2022-12-20)
Anonfiles Download | 1fichier Download
Build based on release#2022121400 (2022-12-14)
Anonfiles Download | 1fichier Download
Build based on release#2022121100 (2022-12-11)
Anonfiles Download | 1fichier Download
Build based on release#2022120300 (2022-12-03)
Anonfiles Download | 1fichier Download
Build based on release#2022113000 (2022-11-30)
Anonfiles Download
Build based on release#2022112500 (2022-11-25)
Anonfiles Download
Click to expand...
Click to collapse
Magisk Patched OTA Update packages
Full OTA Builds will let you update from any older version
Patched OTA based on release#2023061402 (2023-06-14)
SourceForge_Download
Patched OTA based on release#2023050100 (2023-05-01)
SourceForge_Download
Patched OTA based on release#2023041100 (2023-04-11)
SourceForge_Download
Patched OTA based on release#2023032000 (2023-03-20)
SourceForge_Download
Patched OTA based on release#2023022300 (2023-02-23)
SourceForge_Download
Patched OTA based on release#2023020600 (2023-02-06)
SourceForge_Download
Patched OTA based on release#2023020200 (2023-02-02)
SourceForge_Download
Patched OTA based on release#2023012500 (2023-01-25)
SourceForge_Download
Patched OTA based on release#2023011000 (2023-01-10)
SourceForge_Download
Patched OTA based on release#2023010300 (2023-01-03)
Anonfiles Download | SourceForge_Download | 1fichier Download
Patched OTA based on release#2022122000 (2022-12-20)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022121400 (2022-12-14)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022121100 (2022-12-11)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022120300 (2022-12-03)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022113000 (2022-11-30)
Anonfiles Download
Patched OTA based on release#2022112500 (2022-11-25)
Anonfiles Download
Click to expand...
Click to collapse
Builds for Pixel 6 Pro (Raven)
Always do a backup of your data before flashing any updates, just in case.
I make no promises that this works or that I will provide regular updates. I will attempt to provide updates when they are available and I have time, you may have issues with this rom, you could lose your data or brick your device (although it's very unlikely if you follow the instructions and use common sense)
#reserved
Thanks for this!
New Release #2022120300
Changes since the 2022113000 release:
kernel (Pixel 4, Pixel 4 XL, Pixel 4a): add back our change enabling ARM64_SSBD now that upstream issues with it are resolved for this branch
Sandboxed Google Play compatibility layer: avoid chain crash of GmsCompat app following process death from OOM killer, etc.
Vanadium: update Chromium base to 108.0.5359.79
kernel (Generic 5.15): update to latest GKI LTS branch revision including update to 5.15.76
kernel (Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro, Generic 5.10, Generic 5.15): update to latest GKI LTS branch revision
kernel (Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro): update Mali GPU driver to r37p0 (current release is r41p0 but there are substantial changes to the driver for the Tensor SoC on Pixels and it will take substantial work to upgrade all the way)
remove broken, obsolete upstream code causing install permissions defined by user install apps not being automatically granted for user installed apps installed before the app defining the permissions unless the app is reinstalled
Messaging: update MMS configuration database based on Google Messages 20221115_01_RC01
Dialer: update visual voicemail (VVM) configuration database based on Google Phone 90.0.477356402
Dialer: adjust VVM configuration database entries for compatibility with AOSP
Click to expand...
Click to collapse
Download in Post #2
does the full system install include the android 13 boot loader? if someone was still on A12 should they do a full oem update first?
nutzfreelance said:
does the full system install include the android 13 boot loader? if someone was still on A12 should they do a full oem update first?
Click to expand...
Click to collapse
I think you should upgrade to stock android 13 first just to be safe
brilliant thanks!! can i ask a reallly random stupid question please. if i have a stock pixel 6 rom, can i just run the ota update to keep present apps/data in place and to upgrade it to graphene or would that break my phone if not already running graphene?
Ictcreations said:
brilliant thanks!! can i ask a reallly random stupid question please. if i have a stock pixel 6 rom, can i just run the ota update to keep present apps/data in place and to upgrade it to graphene or would that break my phone if not already running graphene?
Click to expand...
Click to collapse
You must install Graphene OS first, and if you want to lock the bootloader then you will need to erase your data anyway
People from GrapheneOS will permanently suspend your account on their forums for simply telling people that it is in fact possible to ROOT Graphene and Lock the Bootloder
They like to LIE to people and tell them it's impossible, while preventing anyone from contradicting them
I flashed the oriole image flawlessy, everythings seems to be fine except for the magisk manager that keeps crashing. I need to do something in order to make it works?
Edit: my bad, i was installing a super old version of magisk Sorry.
Thank you so much for you hard work
i cant find any information if its possbile to use google pay and android auto again with a rooted grapheneos and working magisk modul.
i like graphene and the features but it sucks to use an iphone for my car and cant use my galaxy watch for paying something :/
any1 got an idea or is the only possibility to flash stock google for both apps
timuh said:
i cant find any information if its possbile to use google pay and android auto again with a rooted grapheneos and working magisk modul.
i like graphene and the features but it sucks to use an iphone for my car and cant use my galaxy watch for paying something :/
any1 got an idea or is the only possibility to flash stock google for both apps
Click to expand...
Click to collapse
You cannot use google pay with official Graphene, I mean it works with loyalty cards but not NFC payment cards
So you should not expect it to work with a magisk patched Graphene, maybe you can find some magisk module and a configuration to get safety net passing and google pay working. But I am not aware of anything that works with Graphene
Why so much headache as go trough build for such simple task as resign especially for Graphene? Just get ota, follow instruction in readme.txt avbroot and that it.
I understand if you do any changes to source (patches, unneeded apps, own apps, implement of root). But just for locked bootloader? Bootloader locked or not doing it job.
If you loose and somebody stole your device how locked bootloader helps? Get your data from recovery (it stock, not custom) over adb shell if you use pass not possible. Find device or location not on graphene build. You can't pass Safetycheck or use phone for contactless payments (NFC)
So all that wind just not allow to thief reflash and use device?
boom15 said:
Why so much headache as go trough build for such simple task as resign especially for Graphene? Just get ota, follow instruction in readme.txt avbroot and that it.
I understand if you do any changes to source (patches, unneeded apps, own apps, implement of root). But just for locked bootloader? Bootloader locked or not doing it job.
If you loose and somebody stole your device how locked bootloader helps? Get your data from recovery (it stock, not custom) over adb shell if you use pass not possible. Find device or location not on graphene build. You can't pass Safetycheck or use phone for contactless payments (NFC)
So all that wind just not allow to thief reflash and use device?
Click to expand...
Click to collapse
If you think it's too much headache, that's fine, it's not for you.
I prefer to build it from source myself using my own keys for the whole process, it may be possible as you say just to patch the provided ota with avbroot, but I haven't tested this and don't have any plans to
I don't want to argue about the potential security benefits or downsides, If you don't believe it's secure and you don't feel safe using it then just don't use it. I like my data being secure and not easily accessible, regular backups are important
You can't pass safetynet or use google pay for contactless payments on official graphene, so please take it up with them to fix that as rooting it isn't going to make you more likely to pass safetynet
The thief can always just reflash and use the device unless you disable OEM unlocking in the developer settings
But you should not do this, because if something happened and your phone started to boot loop or something then there would be no way to fix it and you will brick your device, but at least your data will be safe if you had the bootloader locked
FireRattus said:
If you think it's too much headache, that's fine, it's not for you.
I prefer to build it from source myself using my own keys for the whole process, it may be possible as you say just to patch the provided ota with avbroot, but I haven't tested this and don't have any plans to
I don't want to argue about the potential security benefits or downsides, If you don't believe it's secure and you don't feel safe using it then just don't use it. I like my data being secure and not easily accessible, regular backups are important
You can't pass safetynet or use google pay for contactless payments on official graphene, so please take it up with them to fix that as rooting it isn't going to make you more likely to pass safetynet
The thief can always just reflash and use the device unless you disable OEM unlocking in the developer settings
But you should not do this, because if something happened and your phone started to boot loop or something then there would be no way to fix it and you will brick your device, but at least your data will be safe if you had the bootloader locked
Click to expand...
Click to collapse
Read one more time my comment
I'm not said that I will or plan to use your guide to build. I said that it to much work for average person.
I saw your post where you clearly state that you wanna locked bootloader. I pointed to easiest way to do that. Don't like it? Do what you like.
For patching ota by using avbroot. I did it and tested on my own pixels(6a,2 -6, not pro) and not pushing you to do that. As all here I wanna show people another option.
I don't need rom signed you or any one else. It personal rom and I do not have time and willing to inspect it. For me enough that I trust graphene team! I already build rom for my self with implemented of root, patching some graphene code, remove some apks and replaced it with mine and settings that I need. Of cause I sign but that rom it for me and my family not for public. So no any need in secondhand roms.
I did't tell that you responcible for NFC, Saftynet pass just wanna point out that locking bootloader not helps with these issue.Not expect you fix that. You said that you didn't touch code. It's Graphene and it on their side. I used Graphene long enough to know advantages and disadvantages.
And I as you don't intend to start security discussion here or with someone else. Don't worry and have a good day!
boom15 said:
Read one more time my comment
I'm not said that I will or plan to use your guide to build. I said that it to much work for average person.
I saw your post where you clearly state that you wanna locked bootloader. I pointed to easiest way to do that. Don't like it? Do what you like.
For patching ota by using avbroot. I did it and tested on my own pixels(6a,2 -6, not pro) and not pushing you to do that. As all here I wanna show people another option.
I don't need rom signed you or any one else. It personal rom and I do not have time and willing to inspect it. For me enough that I trust graphene team! I already build rom for my self with implemented of root, patching some graphene code, remove some apks and replaced it with mine and settings that I need. Of cause I sign but that rom it for me and my family not for public. So no any need in secondhand roms.
I did't tell that you responcible for NFC, Saftynet pass just wanna point out that locking bootloader not helps with these issue.Not expect you fix that. You said that you didn't touch code. It's Graphene and it on their side. I used Graphene long enough to know advantages and disadvantages.
And I as you don't intend to start security discussion here or with someone else. Don't worry and have a good day!
Click to expand...
Click to collapse
1.I already know this, I thought this would be obvious. I think using Graphene OS at all is too much for the average person, the average person will just use their phone as it comes and never put a custom rom onto it. This was never intended for the average person.
2. I appreciate that there is an easier way to do it, But I already said I was going to do what I like instead.
3. I appreciate that you have tested this works, I will likely update the guide I have created with this information for people who don't want to build it from source but would also prefer to patch official builds with magisk themselves
4. I do highly recommend everyone does build it themself, I think you should not rely on and trust graphene to always provide updates that have not been modified in some malicious way, it's always possible they could get hacked and an update build could be silently replaced with a malicious version
5. Locking the bootloader has nothing to do with safetynet for me, It's more about the other protections that locking the bootloader enables, like making it much harder for someone to be able to access my data or use the phone without erasing the data
Thankfully there is several banking apps which work and even let you use NFC for payments, while you do not pass safetynet
6. I appreciate it, thank you. I hope you have a good day also.
FireRattus said:
1.I already know this, I thought this would be obvious. I think using Graphene OS at all is too much for the average person, the average person will just use their phone as it comes and never put a custom rom onto it. This was never intended for the average person.
2. I appreciate that there is an easier way to do it, But I already said I was going to do what I like instead.
3. I appreciate that you have tested this works, I will likely update the guide I have created with this information for people who don't want to build it from source but would also prefer to patch official builds with magisk themselves
4. I do highly recommend everyone does build it themself, I think you should not rely on and trust graphene to always provide updates that have not been modified in some malicious way, it's always possible they could get hacked and an update build could be silently replaced with a malicious version
5. Locking the bootloader has nothing to do with safetynet for me, It's more about the other protections that locking the bootloader enables, like making it much harder for someone to be able to access my data or use the phone without erasing the data
Thankfully there is several banking apps which work and even let you use NFC for payments, while you do not pass safetynet
6. I appreciate it, thank you. I hope you have a good day also.
Click to expand...
Click to collapse
I spent half of my week following your guide because with my old ass I7-3770K running Debian within VMware takes days since I didn't know there was another way. The main building part (m target-files-package took 6,5 hours to complete) Reading what boom15 said I'd be very happy if I never had to go down this route ever again.
Thank both of you gentlemen for spreading information about this, I wound't be able to figure it out by myself.
I guess I only have to download the OTA from grapheneos.org/releases and follow avbroot's readme, right? (I feel like a retard right now for wasting that much time setting up my VM, it running out of disk space, reinstalling it, etc.. )
Klavaro said:
I spent half of my week following your guide because with my old ass I7-3770K running Debian within VMware takes days since I didn't know there was another way. The main building part (m target-files-package took 6,5 hours to complete) Reading what boom15 said I'd be very happy if I never had to go down this route ever again.
Thank both of you gentlemen for spreading information about this, I wound't be able to figure it out by myself.
I guess I only have to download the OTA from grapheneos.org/releases and follow avbroot's readme, right? (I feel like a retard right now for wasting that much time setting up my VM, it running out of disk space, reinstalling it, etc.. )
Click to expand...
Click to collapse
I do completely understand and sympathize, I have already updated the guide with this simple method of patching graphene for those who are unable to or don't want to build it from source themselves
I think you have gained some valuable experience and knowledge though which will likely help you in the future with other endeavors.
At least you didn't spend a good couple of weeks trying to patch graphene with magisk manually before I even discovered AVBRoot was a thing, so glad that exists
FireRattus said:
I do completely understand and sympathize, I have already updated the guide with this simple method of patching graphene for those who are unable to or don't want to build it from source themselves
I think you have gained some valuable experience and knowledge though which will likely help you in the future with other endeavors.
At least you didn't spend a good couple of weeks trying to patch graphene with magisk manually before I even discovered AVBRoot was a thing, so glad that exists
Click to expand...
Click to collapse
I understand your side too, my end goal would be using only self built opensource software on every device I have, but you gotta start somewhere, right? Maybe once I'll have nothing better to spend money on I'll build myself a newer pc and dual boot linux so it doesn't take ages to build graphene.
I'm all about doing new things, getting experience and knowledge, so I'm not even mad, but just feel relieved that I'll be able to update it easily. Atleast now I'm getting familiar with Debian, which will come in handy when I'll get myself to continue setting up my VPS, so I can selfhost everything I need..
Well I didn't try that, mainly because I'm curious if I'll be able to use my banking app if I root my phone and lock the bootloader, since that sucker won't even let me use contactless payment with a stock os combined with an unlocked bootloader.
New Release #2022121100
Missed a couple of update releases due to build errors then other errors I have finally resolved so
Changes since the 2022120300 release:
resolve upstream bug in Android 13 QPR1 causing screen brightness dimming on user profile changes
Settings: replace hard-wired refresh rate in the text for the smooth display toggle with the actual max refresh rate used for the device model (Android has the string hard-wired to say 90Hz and expects the device to provide an overlay with the correct string which isn't present in AOSP for Pixels)
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Generic 5.10): update to latest GKI LTS branch revision including update to 5.10.156
kernel (Generic 5.15): update to latest GKI LTS branch revision including update to 5.15.77
Sandboxed Google Play compatibility layer: new infrastructure for controlling Play Store updates of Play Store and Play services with a max version of Play services and the Play Store set via GmsCompatCompat and an override toggle for allowing it to update to any version
Sandboxed Google Play compatibility layer: hide GrapheneOS Auditor variant (app.attestation.auditor) from the Play Store so it doesn't try to update it (note: we plan to fully switch to app.grapheneos.auditor.play for the Play Store and we can remove this workaround once we unpublish the GrapheneOS variant of the app there and stop updating it)
Pixel 7, Pixel 7 Pro: remove unused Google Camera SELinux policy
Auditor: update to version 67
Camera: update to version 58
2022120700
Launcher: fix Recent Apps activity crashing when using the TalkBack screen reader due to an incorrect port of the Storage Scopes shortcut to Android 13 QPR1
2022120600
full 2022-12-01 security patch level
full 2022-12-05 security patch level
rebased onto TQ1A.221205.011 release, which is the first quarterly maintenance/feature release for Android 13
Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro: rewrite under display fingerprint scanner integration
Sandboxed Google Play compatibility layer: set GmsCompat versionCode to 1000 (v1) to prepare for defining dependencies on the compatibility layer version for the Google Play apps mirrored in our app repository
Pixel 6, Pixel 6 Pro, Pixel 6a: use Scudo instead of hardened_malloc for camera service for consistency with the Pixel 7 and Pixel 7 Pro until memory corruption issues with it are resolved
add back support for OS device controls and wallet quick tiles
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Generic 5.10): update to latest GKI LTS branch revision including update to 5.10.152
Click to expand...
Click to collapse
Download in Post #2