Related
Hello everyone
My plan was to get dual boot on my z5c using "multirom": the first would be the stock rom (Nougat), the other one was the aosp rom built by Sony itself, in order to unlock some feature like raw capture and long exposures, that seems possible with aosp based roms and "Freedcam" (look for defcomg developer).
Do you think it's possible to mix these two roms with multirom?
What I'm supposed to do is
-Backup the TA partition
-Unlock the bootloader
-Root with dirtycow exploit (does it work with Nougat, doesn't it? Is there a way to get multirom without unlocking the bootloader?)
-Install multirom
-Flash the roms
It this right? Am I missing something, or is there something I must particularly care about? I wouldn't want to brick my phone, and I'm not too experienced, but I think I can follow instructions. Thank for your attention
Got it to work?
I know, this is an old thread, ok.
But ... did you get it to work?
The x829 which I ordered from TomTop is on its way... and I've only just read about the woes of LeEco in US and IN, where it seems to be a matter of time before both regional ventures go broke. So while I previously thought I'd stick with the phone's stock rom and OTAs, I'm now faced with a foreseeable future with no LeEco official updates. In that case, I figure I might as well start using an alternative rom right off the bat.
So, I need a recommendation for a ROM that hopefully can meet the following criteria:
1. ongoing support with OTA patches and updates from a stable group / recognised devt team
2. all functionality on the x829 should work: fingerprint, VoLTE, 4k video, OIS, EIS, audio, ... and are there any others that may not work in different roms?
3. I'm not so concerned about marshmallow vs nougat. Nougat would be good, but life goes on as long as I get updates on marshmallow.
Based on criteria 1, I suppose that my choices are limited to the following.
a. LineageOS 13.0 - is all functionality working?
b. Resurrection Remix - M - at least VoLTE not working. any others?
Do I have any other options?
c. LineageOS 13.0 by andr68us - only supported by andr68us, would not get ongoing patches right? and if this has extra stuff compared to official lineageOS, does the official fully support the camera, IR remote, etc?
d. LineageOS 14.1 - only supported by cr3pt, would not get ongoing patches right?
d. MIUI??
f. mokkee?
g. stick with stock china rom or india rom?
h. Small EUI by aurel - No ongoing patches right?
Would appreciate your corrections and thoughts.
Custom ROM and OTA is a contradiction for most Custom ROMs
Custom ROM and OTA is a contradiction for most Custom ROMs
webbrowser said:
The x829 which I ordered from TomTop is on its way... and I've only just read about the woes of LeEco in US and IN, where it seems to be a matter of time before both regional ventures go broke. So while I previously thought I'd stick with the phone's stock rom and OTAs, I'm now faced with a foreseeable future with no LeEco official updates. In that case, I figure I might as well start using an alternative rom right off the bat.
So, I need a recommendation for a ROM that hopefully can meet the following criteria:
1. ongoing support with OTA patches and updates from a stable group / recognised devt team
2. all functionality on the x829 should work: fingerprint, VoLTE, 4k video, OIS, EIS, audio, ... and are there any others that may not work in different roms?
3. I'm not so concerned about marshmallow vs nougat. Nougat would be good, but life goes on as long as I get updates on marshmallow.
Based on criteria 1, I suppose that my choices are limited to the following.
a. LineageOS 13.0 - is all functionality working?
b. Resurrection Remix - M - at least VoLTE not working. any others?
Do I have any other options?
c. LineageOS 13.0 by andr68us - only supported by andr68us, would not get ongoing patches right? and if this has extra stuff compared to official lineageOS, does the official fully support the camera, IR remote, etc?
d. LineageOS 14.1 - only supported by cr3pt, would not get ongoing patches right?
d. MIUI??
f. mokkee?
g. stick with stock china rom or india rom?
h. Small EUI by aurel - No ongoing patches right?
Would appreciate your corrections and thoughts.
Click to expand...
Click to collapse
Use the latest official Indian ROM.
Currently all custom ROMs for Max2 are buggy or incomplete in one way or another.
ChingghisKhan said:
Custom ROM and OTA is a contradiction for most Custom ROMs
Click to expand...
Click to collapse
True, but being able to get ongoing patches is a pretty big plug for me. That's why I seem to only really have LineageOS 13.0 official and Resurrection Remix-M official choices meeting this criteria right? Actually, I've never used either. Is the update mechanism OTA, or manual download-and-patch?
I guess I should add that OTA is nice but not strictly necessary as long as the necessary patches are consistently applied, and builds are being made. I can download and apply the patches manually (but OTA would be nice).
ApTeM said:
Use the latest official Indian ROM.
Currently all custom ROMs for Max2 are buggy or incomplete in one way or another.
Click to expand...
Click to collapse
Thanks. Maybe that's what I'll do after all.
on the other hand... which is the least buggy custom rom? If the bugs are something I can live with, and it gives me an easier future migration path (or removes the need to migrate firmware altogether) I might take it.
Actually, all of this was on the premise that LeEco US & IN would go bust and no further pacthes will be available. Does this assumption look correct, or maybe I don't need to worry about this?
LeEco is pretty popular in India. I guess its their most valuable territory at the moment, because their attempt to infiltrate the US market has clearly failed and in China they barely make the list of top ten Android vendors.
You shouldn't have bought this phone in the first place if you expected any decent support for it. Too bad, I made the same mistake.
I'm on mokee, with the Chinese 23s modem and gapps flashed on top of it. Everything works, it has OTA.
webbrowser said:
The x829 which I ordered from TomTop is on its way... and I've only just read about the woes of LeEco in US and IN, where it seems to be a matter of time before both regional ventures go broke. So while I previously thought I'd stick with the phone's stock rom and OTAs, I'm now faced with a foreseeable future with no LeEco official updates. In that case, I figure I might as well start using an alternative rom right off the bat.
So, I need a recommendation for a ROM that hopefully can meet the following criteria:
1. ongoing support with OTA patches and updates from a stable group / recognised devt team
2. all functionality on the x829 should work: fingerprint, VoLTE, 4k video, OIS, EIS, audio, ... and are there any others that may not work in different roms?
3. I'm not so concerned about marshmallow vs nougat. Nougat would be good, but life goes on as long as I get updates on marshmallow.
Based on criteria 1, I suppose that my choices are limited to the following.
a. LineageOS 13.0 - is all functionality working?
b. Resurrection Remix - M - at least VoLTE not working. any others?
Do I have any other options?
c. LineageOS 13.0 by andr68us - only supported by andr68us, would not get ongoing patches right? and if this has extra stuff compared to official lineageOS, does the official fully support the camera, IR remote, etc?
d. LineageOS 14.1 - only supported by cr3pt, would not get ongoing patches right?
d. MIUI??
f. mokkee?
g. stick with stock china rom or india rom?
h. Small EUI by aurel - No ongoing patches right?
Would appreciate your corrections and thoughts.
Click to expand...
Click to collapse
The unofficial lineage os 13 by andr68rus is the best and most stable mm rom. Official one does not support ir. This one does. It has all the features and stability of the official one plus the ir functionality and the option for flashing viper4divine beats which actually broke the volte feature in official one. Using Selinux Mode changer app sucks. After some days apps dependent on it stop working after a few days. And regarding ota updates. Y do u need it when everything is perfectly working without bugs??. Heating is the same as dat on all other mm roms.
Sent from my LEX820 using Tapatalk
ApTeM said:
Use the latest official Indian ROM.
Currently all custom ROMs for Max2 are buggy or incomplete in one way or another.
Click to expand...
Click to collapse
I agree, Indian ROM is the best stock.
This thread may be under construction, watch out!
An introduction to my new Oreo sauce...
This is a modified LineageOS 15.1 ROM meant to fill my personal needs, including my minimalistic Lambda Kernel out-of-the-box and a few customizations to provide a different, privacy-focused, Android experience, just for you.
What are the very best features included?
~> Always latest vanilla LineageOS 15.1 codebase;
~> Root virginity preserved, unrooted;
~> SafetyNet bypass out-of-the-box;
~> Google PlayStore device certification;
~> Privacy oriented Bromite web browser;
~> Compiled with SDClang LLVM 4.0 toolchain;
~> Dex-preoptimization of boot image and system server;
~> Minimalistic Lambda Kernel, more information right down below.
What does this magical Kernel support?
~> Cleanly built on top of the latest QCOM reference Kernel for MSM8996;
~> Up-to-date camera_v2 driver stack according to Nougat (LA.UM.5.5) code base;
~> Proper OEM Kernel code adjusted per target (ZL1/X2) and adapted to the new base;
~> Adjusted headset detection framework to account for Type-C adapter;
~> Optimized and adjusted for the -O2 GCC compilation flag;
~> Minimal configuration with the bare minimum drivers needed;
~> Safe fast charging input, regulated per stock Kernel definitions;
~> A little bit faster panel wake up and touchscreen initialization;
~> Unlocked bootloader state bypass, reports green.
What are the known issues so far?
?> Ambient display feature makes the panel wake up a bit funky, you'll see it when compared to the disabled state, which doesn't have that funkiness.
?> Time registering is broken, the daemon doesn't write properly to the Kernel for some reason and ends up not having the correct time after a reboot with the internet turned off.
?> CDLA sometimes has some pops in the background when not listening to anything, pretty minor though.
Nice, where are the downloads?
The downloads are available in the dev release tag in my Github's lineage_releases repository, there you'll find the zip file for installation and the md5sum for checking the file's integrity.
#WelcomeToOurWorld
XDA:DevDB Information
LineageOS Pro for the Le Max2, ROM for the LeEco Le Max 2
Contributors
GalaticStryder, Sultanxda
Source Code: https://github.com/GalaticStryder/android_vendor_patcher
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Chinese 26S
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2018-05-05
Created 2018-04-05
Last Updated 2018-05-05
Reserved
Mine.
Did anyone mention FAQ?
A series of questions, answers, and wonders about all the things she I said in case you didn't get it already.
&> Q. Why isn't this a new project instead of just a simple variant of LineageOS? There are already a ton of them...
&> A. I think there's already a ton of Android "projects" and I don't feel like nor have time to create yet another one that I probably wouldn't be able to maintain for long.
&> Q. How much time will this "variant" be supported?
&> A. Only future wilt tell us but most likely our brave "variant" will resist at least one Android cycle starting from now, all the way through P, even after LineageOS officially drops it we can still have some OEL support if other developers keep the game going.
&> Q. How does it diverge from official LineageOS builds?
&> A. This one aims at providing a snapshot-like experience - if you remember CyanogenMod gold era - which uses the non-debugging user flavor instead of userdebug as Google keeps pushing their draconian restrictions to have access to their apps and services, we need to fake it to avoid forfeiting.
&> Q. My device is "certified" on Google PlayStore, how?
&> A. The bootloader green check in Kernel and user flavor made it possible. I'm not sure how much longer will it take to Google before they go with something deeper to restrict the access of their services by custom ROMs unconditionally. This is a trick though, your device will never be certified with an unlocked bootloader and non-OEM ROM.
&> Q. Will you ever include root support out-of-the-box?
&> A. No, never. You can flash Magisk if you want it, the latest the better in this case. Not sure about the addonsu from LineageOS itself as I never used it.
&> Q. Will you include Dolby Atmos, ViperFX, $(insert_nice_name_here) out-of-the-box?
&> A. No, not at all.
Heeyo! Are you using official LineageOS trees for building your variant?
prajjwal.laad said:
Heeyo! Are you using official LineageOS trees for building your variant?
Click to expand...
Click to collapse
Synced today, no fools included
Well cause i liked your kernel i will try out this rom also!
Nice timing tbh. Just bricked my current rom rn.
True. I've been using his kernel since 24 hours and damn it is the best kernel for x2. My phone's battery temperature doesn't cross 42°C even though my country's normal temperature outdoors is around 38-40°C these days. I get around 20%/hour drain on medium usage which is awesome for my 15 month old battery. Will definitely flash your rom and give feedback.
Hey. Congratz for your work. Can you give more detail about this please: "Safe fast charging input, regulated per stock Kernel definitions;" So we still would able to charge fastly as up to 4000 mH? The quick charge on/off option is available for your kernel? That feature doesn't work properly on the Oreo ROMs..
This is Awesome! The legend is back!
I am so pumped right now! :d:d
@GalaticStryder
Hello, gapps are included inside the rom?
Works everything?
Thanks in advance
cloche;76136607 [user=6175749 said:
@GalaticStryder[/user]
Hello, gapps are included inside the rom?
Works everything?
Thanks in advance
Click to expand...
Click to collapse
First: Big THX @GalaticStryder for this awesome build.
Tested it for an hour now and everything seems perfect. Sound quality is excellent (through Headphones). Rom itself very smooth.
Will report battery Backup later.
Gapps are NOT included, Root is NOT included.
Heyyo, congrats on the release GalaticStryder! She sounds super promising!
A request
I am going to make a very dumb request, can you create an overclocked kernel for this build? Would it be possible?
Thanks so much
Has same bugs as official (eg slow motion video recording not working)?
Thank you for your work dude. I'm wondering if you would make a kernel with focus fix.
maylton said:
Thank you for your work dude. I'm wondering if you would make a kernel with focus fix.
Click to expand...
Click to collapse
He would end up better adding leeco prefs in settings with quick charge switch, maybe akt and focus switch.
Rom works really well. I didnt saw any bugs in it rn.
Tell me, how about Vulcan drivers? Are they present in yours build? If not, do you plan add them?
Thx 4 ur work
N-Gage4ever said:
Hey. Congratz for your work. Can you give more detail about this please: "Safe fast charging input, regulated per stock Kernel definitions;" So we still would able to charge fastly as up to 4000 mH? The quick charge on/off option is available for your kernel? That feature doesn't work properly on the Oreo ROMs..
Click to expand...
Click to collapse
why the **** you go on ranting on every roms about this, already GalaticStryder has explained u regarding this in his lambda kernel
I've been trying since last night, unfortunately I noticed freez and random reboots.
Fp is very very slowly.
TheMichalos said:
He would end up better adding leeco prefs in settings with quick charge switch, maybe akt and focus switch.
Rom works really well. I didnt saw any bugs in it rn.
Click to expand...
Click to collapse
Yes, that would be the best choice for everyone.
This is more or less a copy-paste from the same thread over the s9 section but whatevs. I thought you guys would like this too.
Pixel Experience ROM for the NOTE 9
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Click to expand...
Click to collapse
Semi-GSI? what's that?
a semi-gsi (at least by my own definition) is a gsi built from source, with heavy patches intended for a specific device that wouldn't make the gsi necessarily as universal as a gsi should be. so in terms: don't flash this on other devices.
How does this differ from any other gsis out there/what are the features?
Well this includes a number of fixes including:
Dual speakers are working.
Ui lag is no more (at least 99.99%).
Aod is working/enabled.
Auto brightness is kinda working.
MTP is working
Other performance fixes and improvments.
What's working/not working?
First up:
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS Pixel Experience. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS PixelExperience.
Click to expand...
Click to collapse
2ndly the semi-gsi has a few quirks of it's own. Nothing major or worth noting but you should check the "anything else i should know?" part in the FAQ. hence why HWC is broken
Instructions:
Make sure TWRP has been installed and functional.
Download the latest build image and kernel linked below
Reboot to recovery
Wipe system, data and cache from the wipe menu
Select flash image in twrp, lower right side on the install menu
Flash the rom image as system (and gapps). DONT flash gapps. they are already included in the rom.
Flash the kernel image corresponding to your model as boot
Reboot and enjoy :victory:
Downloads:
Galaxy S9/S9+ Exynos semi-gsi image link: (G965/N960/F/FD/S/N): here
Kernel image link(important to use this. read more in FAQ):
S9 Exynos: here
S9+ Exynos: here
Note 9 Exynos: here
A pretty good (unofficial) mirror for (some of the) above files and more is this
Providing feedback:
You are more than welcome to provide any kind of feedback here.
(limited only to feature requests; it's called "pixel experience" for a reason and it should stay that way)
You can also msg me anytime on telegram @ Rainbow_Alex_Dash
Telegram group?
I usually like to hang around here . It isn't mine but hey.
For note 9 more specifically i hang around here too
Changelog:
12.10.2018:
Initial release Boi
Troubleshooting/FAQ:
Q:Can i use any other kernels with this gsi?
A:Nah, not really. I built this kernel specifically to work with this gsi and it includes a few major fixes (for example mtp won't work,major ui lag, no dual speakers etc if you switch to another kernel. But again. If you want to use other kernels, they should* boot. Endurance kernel even has my dual speaker patch and i confirm as working. But again expect bugs.
Q: Is there anything else i should know?
A: Ehhhhhhh, not really. I mean there are some stuff i'm really not proud of,for example to "fix" the ui lag i had to set the minimum gpu frequency to 455; this shouldn't create any issues(perhaps some battery drainage when screen is on) but afaik it doesn't impact sleep or anything else.
Q:Would this be preferred over a device specific rom?
A: Overall nah. The reason i didn't set on building device specific los16.....well actually i did and failed. But this is a pretty good placeholder until someone more skilled than me takes over and creates pie device trees.
Q: Safetynet doesn't pass?
A: Yeah, i guess that's a thing. Go into magisk and download some module called props hide or something. Don't forget to run it from terminal. It should work from there
Q: The rom isn't booting/camera doesn't work
A: Flash/make sure you have the BRI4 vendor, the linked kernel and try again.
Q: The rom is in a bootloop/google apps keep crashing
A: You did read the instructions and NOT flash any gapps riighhttt?? smh, wipe /system,/data and /cache and start over
Q: I have another bug; How can i tell it to you while slightly increasing my changes of it ever getting fixed.
A: You can tell me what's going on either here or on telegram WITH A LOGCAT attached(required);if rom isn't booting at all attach /proc/last_kmsg.
Q: I don't know what/how to logcat. Is it really necessary?
A: Logcat or gtfo
Q: How can i support you?
A: Awwww thanks; On most of my posts on the left side there's a "donate to me" paypal button; You can use that,donations are more than welcome, or if you don't have any $ to spare you can also post here about how awesome i am (this surprisingly helps very much)
Credits:
The lineageos team; device maintainers who did a wonderful job at creating device trees
The pixel experience team for creating the rom we so do enjoy
Many good people from the telegram group (linked above) that helped me create this project and spamming for etas
Big thanx to iqbal sareem best creationner ever; great help
XDA:DevDB Information
Pixel Experience 9.0 Semi-Gsi for the S9/S9+, ROM for the Samsung Galaxy Note 9
Contributors
Rainbow_Dash, phhusson,malinathani, eamo5, jesec
Source Code: https://github.com/rainbowdashh/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-10-12
Created 2018-10-12
Last Updated 2018-10-13
Thanks for sharing.
Wonder if this Kernal image will work with other GSI roms to get them running as smooth as this rom.
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
wenjie1234 said:
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
Click to expand...
Click to collapse
Spen does work as a pointer and to tap and even draw..
The spen button does nothing though. And obviously, the spen settings and apps are all Samsung made so they won't be working here. Highly doubt Spen would work ever on aosp like stock due to Samsung apps incompatibility
wenjie1234 said:
Is it possible to add S Pen support in the future? I mean, that's one big reason why people buy the Note 9 rather than the S9+
Click to expand...
Click to collapse
Spen went work without Sammy's framework but there are plenty of apps on play store that offered similar effects to Sammy's own. I used them on my note tablet when I ran any other rom then sammy roms.
Yes! I've been waiting for this. Thank you so much. Flashing right now. Will report back!
---------- Post added at 08:18 AM ---------- Previous post was at 07:39 AM ----------
Flashed it but no dual speaker or data. Do I flash the kernel to the system partition too? Doesn't say in FAQ?
s3xxt0y said:
Yes! I've been waiting for this. Thank you so much. Flashing right now. Will report back!
---------- Post added at 08:18 AM ---------- Previous post was at 07:39 AM ----------
Flashed it but no dual speaker or data. Do I flash the kernel to the system partition too? Doesn't say in FAQ?
Click to expand...
Click to collapse
I don't know what you mean by data but i do know the kernel is supposed to be flashed as boot
Problem with fingerprint here.
Only first touch for new finger is registered.
After that it's not working anymore.
Data as in mobile / cellular data as discussed in telegram.
For anyone who has no cellular manually add your APN info in network settings.
Fingerprint does work and adds, go to settings and add fingerprints the registration bit is a bit finnicky but it adds them and they work.
A theoretical question/crazy idea:
Will installing Magisk's xmlpak module enable us to download and use the Samsung camera and spen features in this mod? So we could get the super slow mo, etc, back? Thanks
I followed the instructions by flashing the proper kernel image without gapps, but still bootloops in the Google Screen.
sam razzy said:
I followed the instructions by flashing the proper kernel image without gapps, but still bootloops in the Google Screen.
Click to expand...
Click to collapse
Quoting tylerrw from the Note 9 Telegram group...
tylerrw:
Wipe data, cache (not system) > reboot recovery > install semi gsi image > install kernel > install no verity > install magisk
Reinstall (ARH6) vendor image too
After installing semi GSI
Click to expand...
Click to collapse
AlfaM03 said:
A theoretical question/crazy idea:
Will installing Magisk's xmlpak module enable us to download and use the Samsung camera and spen features in this mod? So we could get the super slow mo, etc, back? Thanks
Click to expand...
Click to collapse
No, there's no way to get these features to work in Aosp based roms.
Fingerprint is not working, too all other works fine thank you soooo much!
Dan_FFM said:
Fingerprint is not working, too all other works fine thank you soooo much!
Click to expand...
Click to collapse
Same Here
Do we have the gestures like the pixel 3?
wenjie1234 said:
Do we have the gestures like the pixel 3?
Click to expand...
Click to collapse
No, nur you can activate IT via ADB shell command
If I want to flash another rom after flashing this rom and kernel, can this kernel work well with other roms or should I flash another kernel instead?
My number 1 question is: does dual sim work?
wenjie1234 said:
Do we have the gestures like the pixel 3?
Click to expand...
Click to collapse
Yes - Go into gestures in settings and enable the swipe up gesture. It's under Settings>System>Gestures
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