Related
OmniROM Galaxy 551/Callisto port [OmniARMv6]
Current port status: beta - may not be suitable for daily use. For experienced users only.
Latest Google Apps package: not yet available
Pre-requisites:
ClockworkMod or TWRP recovery
Initial install:
Download the latest build that supports OTA updates from: http://dl.androidarmv6.org/callisto
Reboot to recovery, wipe data and install the update package normally.
How to perform OTA (over the air) update:
Go to Settings -> About phone -> System updates. The latest diff between your current ROM and the latest build will be downloaded, which will be used to create a new update zip in the /sdcard/OpenDelta folder.
If you are using OmniARMv6 TWRP recovery, it can flash the new update automatically [not yet tested].
If you are using CWM recovery, you can flash the patched package (/sdcard/OpenDelta/omni-*.zip) manually.
Source:
Complete project: https://github.com/omniarmv6
Device (note: relies on shared device configuration): https://github.com/omniarmv6/android_device_samsung_callisto
Kernel: https://github.com/androidarmv6/android_kernel_samsung_msm
Reserved #1
Reserved #2
I have tested and found camera is not working , document (file manager) unable to open apk file and need some work on lock screen except that rom is smooth.
Thank for creating thread.
thanks
ROM is very smooth and fast. Works much faster than CM11.
Very thanks
@psyke83 omni rom will be used kernel 3.×.× as per source given above.
@psyke83 omni project has been abanded ? after bunch of ota failed ota disappeared from Jenkins. This rom is smooth and fast except few problems like camera,keyboard back light and lock screen resize.
Last builds (also for other devices) are dated June 15. And the last Android version was 4.4.3. Is it just a build process that got stuck, or is it more serious?
Links are down!
Hey man,
Thank you and others in armv6 team for their incredible work. You guys brought CM11 to a number of devices and that's a BIG DEAL.
Since our device is quite old now, I can see why the project died.
Now, the only thing we want is the links of the latest stable (RC) builds of the devices hosted somewhere. I can (at-least) host (CM11 and OMNI) stable builds of callisto in my GDrive.
Anyone knows what the license for ready-built ROMs is? That is, if the original source goes down, would anyone be allowed to upload a copy?
I'm not thinking about modified images yet - but it'd be easy to make people download something that isn't identical to the original thing, and the md5sum files have also gone - would archive.org be able to help? https://web.archive.org/web/*/http://download.androidarmv6.org/_builds/callisto/* seems to return something at least
Can Someone reupload this?
Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirementsTo run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
DownloadsNo Download as no longer maintained and buggyQR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issuesYou tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06
FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit
I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...
GOOD JOB .....Bro
kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you
Anyone already try this tool? I want download, but size so damn high
zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)
I can´t flash twrp with this toolikt any one have a clue?
Do you have the adb drivers installed? Or is it throwing an error?
Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk
Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.
dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...
Download link is not working. Please re-up. Thanks
godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1
If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.
Motorola Moto E5 Play [James]
XT1921-5 Sprint, Boost Mobile, Virgin Mobile
Stock Android 8.0.0 Oreo ROM
Build No. OCPS27.91-140-3
TWRP Flashable Installer
WARNING: Modifying your device's stock filesystem configuration (rooting, flashing, etc.) can render your warranty null & void, and carries with it the inherent risk of damaging your device (bricking) or rendering it otherwise inoperable. By proceeding further, you acknowledge these warnings and absolve me of any civil liability or responsibility in the event things go wrong. This ROM has been fully tested on my own device. Follow the below instructions carefully and things should go well. New or inexperienced members are encouraged to read and re-read the entire OP prior to performing any steps.
*********************************************
Please help keep this thread on topic. I am not a dev, so please do not request updates or post ETA-type inquiries. However, I will do my best at keeping this thread updated as future OTAs augment the incremental build or ROM version. Please be fully respectful to all members when posting. Keep in mind that language barriers can sometimes cause misinterpretations with intended meaning. Let's try to be tolerant of other members' level of experience, language, nationality, and all that good stuff. I'm here to learn and grow and I know many others are also. Thank you.
*********************************************
SPECIFICATIONS & FEATURES:
Compatible Model: xt1921-5 Only
Providers: Sprint, Boost Mobile, Virgin Mobile
Android Version: 8.0.0 Oreo
Build No. OCPS27.91-140-3
Kernel: 3.18.71-perf-g137d1ed
Radio: M8920_21.11.11.62R
Build Date: December 10, 2018
Security Patch Level: December 1, 2018
Systemless Root: Magisk v18.0-stable
SafetyNet Pass: ctsProfile & basicIntegrity
BusyBox: v1.29.3 /system/bin/busybox (static)
Init.d and su.d Support
AVB/dm-verity Disabled
Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
CHANGELOG:
This ROM is built from a maintenance release OTA from the previous build (OCPS27.91-140-1). This update includes Motorola Mobility's standard bug fixes, stability improvements, and Android security patches through December 1, 2018. The Baseband Version (radio firmware) was not updated and remains at version M8920_21.11.11.62R. Hence, I did not include a Baseband updater in the downloads section. The bootloader partitions and partition index (GPT) were updated via the OTA. However, these were merely maintenance type updates and no substantial changes were made. For those members wishing to fully update their devices to OCPS27.91-140-3, I have included a partition updater in the downloads section.
REQUIREMENTS:
An unlocked bootloader and TWRP custom recovery are needed to install this ROM. If you do not have TWRP installed, visit XDA Senior Member @CodyF86's thread on TWRP for this device here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 Also, be sure and thank @CodyF86 if you use his work.
INSTRUCTIONS:
**It is recommended that you first update your device partitions to the corresponding ROM build. Just download the partition updater below and install it with TWRP.
1. Download the ROM zip from the download link below and store it on your device's internal or external storage;
2. Boot your device into TWRP recovery mode;
3. Wipe System, Data, Cache & Dalvik/ART;
4. Select Install, navigate to the saved location of the ROM zip, select the file, and swipe the action bar to commence installation;
5. Once installation is finished, reboot system;
6. Done.
BUGS:
No known bugs. Please report any bugs in comments, with as much detail and clarity as possible. For members with knowledge on submitting bug reports, those are most helpful. Please so not post about bugs if you are using a custom kernel or if you are running ststem-based mods on this ROM (system-wide Xposed Framework, etc.). These types of modifications make it nearly impossible to properly diagnose a bug, or to determine the true source of the actual instability. Because this ROM is mostly pure stock, there should be no apparent instabilities or bugs outside of those possibly present within the factory stock build.
THANKS & MENTIONS:
I'd like to mention and give thanks to XDA Senior Member @CodyF86 for his hard work building TWRP for the James, and for his tutorials on TWRP & unlocking the bootloader. Also, thanks to the great @topjohnwu for his Magisk Universal Systemless Interface and his systemless root installer. Thanks to @osm0sis for his static BusyBox binary installer and his Magisk Modules.
DOWNLOAD LINKS:
OCPS27.91-140-3
Partition Updater: https://drive.google.com/file/d/1j1RUfGL41NsdLYtYaVQKxhMq6DD5p12V/view?usp=drivesdk
OCPS27.91-140-3 ROM: https://drive.google.com/file/d/1hivvpfy3OB5X3-njvLHQsuvcFhrfztvc/view?usp=drivesdk
Stock Recovery Image
OCPS27.91-140-3: https://drive.google.com/file/d/1dSiXl4ArnlJ9pD9gZtgvDSkjN2t-lKig/view?usp=drivesdk
Stock Boot Image
••Unmodified••
OCPS27.91-140-3: https://drive.google.com/file/d/1RoIGhfk91lDtyo3z_wzPT4S7Trc4OI8y/view?usp=drivesdk
Previous Builds:
OCPS27.91-140-1 ROM: https://drive.google.com/file/d/17steuhe7DUJEzYpbcuIqjlzQnwO3O0M3/view?usp=drivesdk
The download links require login. I want to try the rom but cannot download.
New Links?
The links above are password protected. I requested permission a few days ago for access, as Google Drive recommended, but I haven't heard anything back.
Did anyone get the files before the links went private? I would be very grateful for any help or advice.
I requested permission also, haven't heard back...
Anyone got a link for XT1921-3 Moto E5 Play (James)
again with password bad very bad
I just want to let you know that i am going to turn this into the government because
I just want to let you know that i am going to turn this into the government because you have given a link that doesnt work
lenovotech said:
motorola moto e5 play [james]
xt1921-5 sprint, boost mobile, virgin mobile
stock android 8.0.0 oreo rom
build no. Ocps27.91-140-3
twrp flashable installer
warning: Modifying your device's stock filesystem configuration (rooting, flashing, etc.) can render your warranty null & void, and carries with it the inherent risk of damaging your device (bricking) or rendering it otherwise inoperable. By proceeding further, you acknowledge these warnings and absolve me of any civil liability or responsibility in the event things go wrong. This rom has been fully tested on my own device. Follow the below instructions carefully and things should go well. New or inexperienced members are encouraged to read and re-read the entire op prior to performing any steps.
*********************************************
please help keep this thread on topic. I am not a dev, so please do not request updates or post eta-type inquiries. However, i will do my best at keeping this thread updated as future otas augment the incremental build or rom version. Please be fully respectful to all members when posting. Keep in mind that language barriers can sometimes cause misinterpretations with intended meaning. Let's try to be tolerant of other members' level of experience, language, nationality, and all that good stuff. I'm here to learn and grow and i know many others are also. Thank you.
*********************************************
specifications & features:
Compatible model: Xt1921-5 only
providers: Sprint, boost mobile, virgin mobile
android version: 8.0.0 oreo
build no. Ocps27.91-140-3
kernel: 3.18.71-perf-g137d1ed
radio: M8920_21.11.11.62r
build date: December 10, 2018
security patch level: December 1, 2018
systemless root: Magisk v18.0-stable
safetynet pass: Ctsprofile & basicintegrity
busybox: V1.29.3 /system/bin/busybox (static)
init.d and su.d support
avb/dm-verity disabled
kernel source code: https://github.com/motorolamobilityllc/kernel-msm/releases/tag/mmi-ocp27.91-23
changelog:
This rom is built from a maintenance release ota from the previous build (ocps27.91-140-1). This update includes motorola mobility's standard bug fixes, stability improvements, and android security patches through december 1, 2018. The baseband version (radio firmware) was not updated and remains at version m8920_21.11.11.62r. Hence, i did not include a baseband updater in the downloads section. The bootloader partitions and partition index (gpt) were updated via the ota. However, these were merely maintenance type updates and no substantial changes were made. For those members wishing to fully update their devices to ocps27.91-140-3, i have included a partition updater in the downloads section.
Requirements:
An unlocked bootloader and twrp custom recovery are needed to install this rom. If you do not have twrp installed, visit xda senior member @codyf86's thread on twrp for this device here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 also, be sure and thank @codyf86 if you use his work.
Instructions:
**it is recommended that you first update your device partitions to the corresponding rom build. Just download the partition updater below and install it with twrp.
1. Download the rom zip from the download link below and store it on your device's internal or external storage;
2. Boot your device into twrp recovery mode;
3. Wipe system, data, cache & dalvik/art;
4. Select install, navigate to the saved location of the rom zip, select the file, and swipe the action bar to commence installation;
5. Once installation is finished, reboot system;
6. Done.
Bugs:
No known bugs. Please report any bugs in comments, with as much detail and clarity as possible. For members with knowledge on submitting bug reports, those are most helpful. Please so not post about bugs if you are using a custom kernel or if you are running ststem-based mods on this rom (system-wide xposed framework, etc.). These types of modifications make it nearly impossible to properly diagnose a bug, or to determine the true source of the actual instability. Because this rom is mostly pure stock, there should be no apparent instabilities or bugs outside of those possibly present within the factory stock build.
Thanks & mentions:
I'd like to mention and give thanks to xda senior member @codyf86 for his hard work building twrp for the james, and for his tutorials on twrp & unlocking the bootloader. Also, thanks to the great @topjohnwu for his magisk universal systemless interface and his systemless root installer. Thanks to @osm0sis for his static busybox binary installer and his magisk modules.
Download links:
Ocps27.91-140-3
partition updater: https://drive.google.com/file/d/1j1rufgl41nsdlytyavqkxhmq6dd5p12v/view?usp=drivesdk
ocps27.91-140-3 rom: https://drive.google.com/file/d/1hivvpfy3ob5x3-njvlhqsuvcfhrfztvc/view?usp=drivesdk
stock recovery image
ocps27.91-140-3: https://drive.google.com/file/d/1dsixl4arnlj9pd9gztgvdskjn2t-lkig/view?usp=drivesdk
stock boot image
••unmodified••
ocps27.91-140-3: https://drive.google.com/file/d/1roighfk91ldtyo3z_wzpt4s7trc4oi8y/view?usp=drivesdk
previous builds:
Ocps27.91-140-1 rom: https://drive.google.com/file/d/17steuhe7dujezypbcuiqjlzqnwo3o0m3/view?usp=drivesdk
Click to expand...
Click to collapse
Hi. guys.
This is the Firmware dump for Android Q.
Include 4 scripts who flash the FW into both slots ( A and B) (choose only one... "
USE AT YOUR RISK
Use it only if you are on Q .63 version or after.
Official source Android Q Here
To be sure you have 50% battery min before....
Do touch anything before script is finish
So reboot to bootloader
Use the good script into the folder extracted:
For Linux users, if you want a full flash use:
Code:
./script
or if you're on custom ROM and want only needed files, use:
Code:
./Update_script
For Windows Users, click on for all partitions
Code:
flash-all-partitions-fastboot.bat
or if you're on custom ROM and want only needed files, use:
Code:
Update-partitions-fastboot.bat
Enjoy with Android Q and Customs Roms
ZS630KL software Image：WW_17.1810.1910.63 for WW/IN only, *EU/RU/JP exclude int this FOTA version
*Special notice: This upgrade patch only allows to upgrade from Android P 16.1220.1909.194 version to Android Q 17.1810.1910.63 version. The other firmware version can't use this upgrade patch to upgrade.
Improved Item:
1.Upgrade to Android 10
2.Support Google Play System update
3.Added fully gestural navigation in Display setting
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please buckup your important data before system upgrading.
Click to expand...
Click to collapse
Version .68
System update
Optimized the mechanism of system update.
Optimized the system stability.
Audio
Improved the sound quality.
Click to expand...
Click to collapse
Download Link
My FW Dump .68
OP updated with .68 version
Add 2 new scripts for only one Update if you're on custom ROM.
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 Pro (Raven)
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)
Anonfiles Download | 1fichier Download | SourceForge_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
Build based on release#2022111800 (2022-11-18)
Anonfiles Download
Build based on release#2022111000 (2022-11-10)
Anonfiles Download
Build based on release#2022101800 (2022-10-18)
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 | 1fichier_Download | SourceForge_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
Patched OTA based on release#2022111800 (2022-11-18)
Anonfiles Download
Patched OTA based on release#2022111000 (2022-11-10)
Anonfiles Download
Patched OTA based on release#2022110800 (2022-11-08)
Anonfiles Download
Click to expand...
Click to collapse
Builds for Pixel 6 (oriole)
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
Isn't there already an official build for graphene for Raven?
iBe.Jacob said:
Isn't there already an official build for graphene for Raven?
Click to expand...
Click to collapse
Yes. But not for a rooted version of it.
New Release 2022111800
Changes since the 2022111000 release:
don't skip ahead-of-time (AOT) compilation of apps that weren't recently used since we depend on full AOT compilation being done for performance rather than JIT compilation with background JIT profile guided AOT compilation like Android
battery usage UI: use fallback name for unknown components
change minimal value of battery saver schedule to 5% again as it was before Android 13
enable the post-upgrade "Optimizing apps" progress indication UI
app crash UI: show process uptime and optional extra text
Sandboxed Google Play compatibility layer: show version of GmsCompatConfig in the crash UI
Sandboxed Google Play compatibility layer: stop splitting multi-package PackageInstaller sessions
Sandboxed Google Play compatibility layer: improve handling of activity starts
Sandboxed Google Play compatibility layer: bugfix: Parcel position wasn't reset by dynamic stubs
Sandboxed Google Play compatibility layer: bugfix: missing handling of ListSlices in dynamic stub
GmsCompatConfig: make sure Play Store PhenotypeFlags are overridable by Gservices flags (further deterring Play Store trying to update Play services / Play Store beyond supported versions)
Pixel 7, Pixel 7 Pro (adevtool): drop unused face unlock components since we have no plans to enable support for an insecure face unlock implementation incapable providing reasonable security due to lack of dedicated face unlock hardware (Pixel 4 and Pixel 4 XL had dual infrared cameras, IR dot projector and IR flood illuminator providing a more secure biometric unlock system than fingerprint unlock as opposed to simply using the front camera in a way that could be done on any device)
Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro: include gril library to avoid qns crash on Pixel 7 and Pixel 7 Pro
Pixel 7, Pixel 7 Pro: include vendor_kernel_boot partition requirement in factory images metadata to force an error with an incompatible fastboot such as the currently buggy Arch Linux package
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro): update GKI to Linux 5.10.150
Auditor: update to version 66
Click to expand...
Click to collapse
Download in Post #2
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
96carboard said:
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
Click to expand...
Click to collapse
Sorry but I am not interested in arguing about this stuff
I didn't create this thread to argue about potential security issues or how secure phones really are
it seems you have more of an issue with the security of Android in general
I would recommend everyone who just wants to share opinions like this which are essentially unrelated to the ROM, please just don't
I am not claiming rooting your phone to be perfectly secure and I am not interested in arguing about it
Although as explained here https://forum.xda-developers.com/t/...pdated-november-9-2022.4343431/#post-85733797
there are advantages to using a locked bootloader, even with root.
optimumpro said:
The rom could be used on locked bootloader with ROOT (donate feature) with or without Gapps.
The benefits of LOCKED BOOTLOADER combined with WORKING AVB-2 protection are:
Get back your DRM L1 certificate. Most banking apps will work regardless of Magisk.
Security: Nobody and nothing can modify Kernel, Recovery and Virtual Partitions without triggering a red screen of death with the message 'your device is corrupted and cannot boot'.
At that point, the only option is to unlock bootloader. But, if a user had previously disabled OEM unlock in Developer settings, then unlocking becomes unavailable, and so does flashing via fastboot. In other words, if your phone gets into the hands of an adversary, their only option is to use MSM tool to make the phone work again, but no access to your data or any other partition.
Why prebuilt Magisk? Because you can't modify kernel or recovery on locked bootloader post installation, and that's exactly what Magisk does.
Click to expand...
Click to collapse
I am offering this as a free feature, not a donate feature and I have also created a guide so that anyone is able to build the rom and sign it using their own keys for even greater security than trusting me.
Magisk isn't just some unknown third party, Graphene, Magisk, AVBRoot, they are all open source projects
FireRattus said:
Sorry but I am not interested in arguing about this stuff
I didn't create this thread to argue about potential security issues or how secure phones really are
it seems you have more of an issue with the security of Android in general
I would recommend everyone who just wants to share opinions like this which are essentially unrelated to the ROM, please just don't
I am not claiming rooting your phone to be perfectly secure and I am not interested in arguing about it
Click to expand...
Click to collapse
I'm not talking about the utility or security of root (hint: Its perfectly safe and secure when used RESPONSIBLY). I'm talking about the value of using a security hardened OS with modifications made by someone who you don't know and can't trust. Doing so throws away ALL security because there is no way to tell what else someone has changed.
96carboard said:
I'm not talking about the utility or security of root (hint: Its perfectly safe and secure when used RESPONSIBLY). I'm talking about the value of using a security hardened OS with modifications made by someone who you don't know and can't trust. Doing so throws away ALL security because there is no way to tell what else someone has changed.
Click to expand...
Click to collapse
So just follow the guide I provided so you can build the rom yourself, you can inspect all the source code and work out exactly what it's all doing if you are so inclined
https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
FireRattus said:
So just follow the guide I provided so you can build the rom yourself, you can inspect all the source code and work out exactly what it's all doing if you are so inclined
https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
Click to expand...
Click to collapse
Yes exactly!
@FireRattus is there any chance we can see pre-build images for Oriole in the future? I'm having trouble building it myself.
KainoaK said:
@FireRattus is there any chance we can see pre-build images for Oriole in the future? I'm having trouble building it myself.
Click to expand...
Click to collapse
What are the troubles you are having with building it yourself? I can try my best to help
I would be able to build images for Oriole probably but I wouldn't be able to test them myself and building for more variants would take more time making updates slower so I don't want to invest in that currently.
I do think it's best to build it yourself if you are able so I am glad you have tried already
> What are the troubles you are having with building it yourself? I can try my best to help
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
KainoaK said:
> What are the troubles you are having with building it yourself? I can try my best to help
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
Click to expand...
Click to collapse
I will try to build it for you, since the pixel 6 and 6 pro share the same Build ID, I should be able to build it without needing to download everything again
New Release #2022112500
Changes since the 2022111800 release:
Sandboxed Google Play compatibility layer: fix missing handling of APEX ListSlices in dynamic stubs (improves compatibility when granting Nearby devices permission to Play services with a WearOS device connected)
Sandboxed Google Play compatibility layer: mark PackageInstallerStatusForwarder as not exported
Settings: avoid OBB toggle unnecessarily force stopping app
extend original-package renaming to static launcher shortcuts to fix Vanadium new tab shortcut for users with an install predating the package rename
Camera: update to version 57
Vanadium: update Chromium base to 107.0.5304.141
Contacts: add support for dark mode
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro): restore fix for CVE-2022-3176 which was reverted upstream (GKI LTS branch) due to not being marked as a security fix and changing the GKI ABI
Pixel 4, Pixel 4 XL: set frozen patch level string to 2022-11-01 (has been provided since the 2022110800 release but we initially left the patch level string at the previous value)
port GrapheneOS changes to Linux 5.15 GKI LTS branch in order to prepare for 6th/7th generation Pixels potentially moving to the Linux 5.15 LTS and late 2023 devices which will be based on it
Click to expand...
Click to collapse
Download in Post #2
KainoaK said:
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
Click to expand...
Click to collapse
I am not able to test them myself but I have provided a patched, signed build which should work
just check post #3 for the download links, I would appreciate a donation if you feel it's worth it but no pressure
Edit: Moved it to post #2 with the other downloads
96carboard said:
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
Click to expand...
Click to collapse
To be fair you'll always be using something done by a third party, including android itself, unless it's you writing and compiling your own OS.
MidnightDevil said:
To be fair you'll always be using something done by a third party, including android itself, unless it's you writing and compiling your own OS.
Click to expand...
Click to collapse
Android is open source. Open source code is auditable. Compiled binaries are NOT.