Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications,
*/
About:
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction:
This is the unofficial Lineage OS thread for the Motorola G7, codename river.
We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
ROM:
lineage-16.0-20191001-UNOFFICIAL-river.zip
Stock Firmware:
Official Firmware
Recovery:
Unofficial TWRP
Copy Partitions: (To setup slot_b)
copypartitions.zip
(courtesy of @filipepferraz)
Open GApps:
http://opengapps.org
Preparation for A/B Roms:
01. Download TWRP and the Firmware for your variant from the links above.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader Instructions here.
04. Flash your factory firmware image on slot_A
Hold power + Volume down untill you reach bootloader (fastboot mode)
In your extracted firmware folder open a terminal and flash your firmware files with these commands.
NOTE-1: This last step installs vendor.img to slot_b as well.
05. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
06. ## Take a backup of EFS, Persist1, Persist2 then store this on your computer in a safe place!! ##
07. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
08. While in TWRP choose Reboot > bootloader
09. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM, TWRP and GApps from the links above.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Flash ROM.zip + TWRP_Installer.zip
04. Reboot > Recovery
05. Install Gapps + Magisk (if you choose)
06. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. fasboot boot twrp.img
03. Install ROM.zip + TWRP_Installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must use 'fastboot -w' to erase it before using ROMS
XDA:DevDB Information
Lineage OS 16.0, ROM for the Moto G7, ROM for the Moto G7
Contributors
SyberHexen, erfanoabdi, LineageOS Team
Source Code:
[url]https://github.com/LineageOS[/URL]
android_kernel_motorola_msm8953
android_device_motorola_river_prebuiltvendor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Stock Vendor.img
Version Information
Status: Testing
Created 2019-08-19
Last Updated 2019-10-01
BUGS
====
1. Mobile Data can be intermittent (potentially carrier specific)
2. LiveDisplay: Default mode causes screen inversion
- Please Switch under Settings > Display > LiveDisplay > Color Profile > To Hal_Native/Standard
Release Notes:
(09/17/2019)
Device:-
* Adoptable Storage Support
* Added support HBM support for all known panels
(fixes non boot with certain screen suppliers)
Kernel:-
* Upstream Kernel [4.9.112] --> [4.9.165]
(09/08/2019)
* Included Patch for Magisk Support
* Different IMS/Telephony Implementation
(which should allow calls on VoLTE)
* LiveDisplay Adjustments
Can you share .repo/local_manifests/roomservice.xml that you use to build the rom?
I'd like to build too.
Thanks.
Great work.
Irrelevant reply, mostly due to error in OP thread;
In the first paragraph of the About it says this LineageOS is for Android Oreo (8.0) while at the bottom it is claimed for Android Pie (9.0)
Will be installing soon for better feedback, but just thought you'd like to be aware of that.
Also, would this include the Security Patch of the most recent official release or is that something not to concern myself over with LineageOS releases?
zenful said:
Irrelevant reply, mostly due to error in OP thread;
In the first paragraph of the About it says this LineageOS is for Android Oreo (8.0) while at the bottom it is claimed for Android Pie (9.0)
Will be installing soon for better feedback, but just thought you'd like to be aware of that.
Also, would this include the Security Patch of the most recent official release or is that something not to concern myself over with LineageOS releases?
Click to expand...
Click to collapse
Gotta love xda thanks for letting me know that xda reverted all my corrections to the main post over night.
So it's android 9.0 built with latest sources
Does this work for the Amazon variant of the Moto g7?
Hi, I apologize if this isn't the best place to post this, but I get an error when following installation instructions. While flashing stock firmware to slot A, I run the command `fastboot flash partition gpt.bin` and get the following output:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
zsh: abort (core dumped) fastboot flash partition gpt.bin
I tried googling for the error, but wasn't able to come up with a clear idea of what to do to fix it. If anyone can point me in the right direction, I'd really appreciate the help. Thanks a lot.
jleprincehoff said:
Does this work for the Amazon variant of the Moto g7?
Click to expand...
Click to collapse
Last i knew Amazon Devices couldnt not be Boot Loader Unlocked
Yes they can be unlocked my g7 power Amazon is unlocked
A lightning said:
Hi, I apologize if this isn't the best place to post this, but I get an error when following installation instructions. While flashing stock firmware to slot A, I run the command `fastboot flash partition gpt.bin` and get the following output:
I tried googling for the error, but wasn't able to come up with a clear idea of what to do to fix it. If anyone can point me in the right direction, I'd really appreciate the help. Thanks a lot.
Click to expand...
Click to collapse
Try updating adb drivers or using different version
Cam Work!!! I can Capture Images and Record Video
Google Gapps - OpenGapps ARM64 Work Fine!!!
Magisk Not Work But the addonsu arm64 for lineage os 16 work!!! :good:
SyberHexen said:
Try updating adb drivers or using different version
Click to expand...
Click to collapse
I'm using the latest Android platform tools on Linux. I should have included this in my first message, but this is a Project Fi phone. I tried both builds in the Fi folder of the lolinet link in the OP, and both had the same problem. The model numbers on these do match my phone. (XT1962-1) I'm really struggling to find an explanation for my error message anywhere online.
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
zsh: abort (core dumped) fastboot flash partition gpt.bin
A lightning said:
I'm using the latest Android platform tools on Linux. I should have included this in my first message, but this is a Project Fi phone. I tried both builds in the Fi folder of the lolinet link in the OP, and both had the same problem. The model numbers on these do match my phone. (XT1962-1) I'm really struggling to find an explanation for my error message anywhere online.
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
zsh: abort (core dumped) fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Post result of
Code:
fastboot --version
adb --version
ptn107 said:
Post result of
Code:
fastboot --version
adb --version
Click to expand...
Click to collapse
Code:
1% fastboot --version
fastboot version 29.0.2-ArchLinux
Installed as /usr/bin/fastboot
% adb --version
Android Debug Bridge version 1.0.41
Version 29.0.2-ArchLinux
Installed as /usr/bin/adb
In addition to my Linux distro's package, I also tried downloading platform-tools with Android sdkmanager and got the same errors,
I've used lineageos 14 in the past but it's been a while.
What advantages does lineageos 16 bring compared to Moto's pie?
ptn107 said:
I'm using the latest Android platform tools on Linux. I should have included this in my first message, but this is a Project Fi phone. I tried both builds in the Fi folder of the lolinet link in the OP, and both had the same problem. The model numbers on these do match my phone. (XT1962-1) I'm really struggling to find an explanation for my error message anywhere online.
Click to expand...
Click to collapse
I'm on FI with the same model.
Have you tried using older fastboot drivers or a different USB-c /USB port?
I sent the OP a pm asking if they would like any help or if they are willing to link us github information so we can start building and improving this for the River device.
Waiting to hear something back
Hell-Razor said:
I sent the OP a pm asking if they would like any help or if they are willing to link us github information so we can start building and improving this for the River device.
Waiting to hear something back
Click to expand...
Click to collapse
https://github.com/SyberHexen Here is his work.
flintman said:
https://github.com/SyberHexen Here is his work.
Click to expand...
Click to collapse
Thats not a guarantee its all the work he has done. He may still be pulling from multiple gits in a script. I would much rather talk to the op and check before trying to jump through loops that could easily be there.
EDIT: I sound like a **** there, I dont mean to be. I am just not great at this stuff so it may be nice to get a little help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS for Nokia 7.2
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Whats working?
Wi-Fi
RIL
Volte
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint
FM radio
Sound
vibration
Bugs ?
Let me know if you see anything else. Especially please mention the issue and attach the logcat.
Installation process
Click Here for Installation process
Credits
* LineageOS Team for rom source
* Nokia for kernel source
Download Rom
Download TWRP
Join Community Group
Android OS version: 13.0
Security patch level: 2023-01
Build author: Raghu varma
Kernel source code : android_kernel_nokia_LC-SDM660
Source code: https://github.com/LineageOS
Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Sun Jan 22 19:01:23 UTC 2023
============================
• Initial Android 13 build
• Based on android-13.0.0_r20
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
• Selinux enforced
• Vendor built from Source
• Imported CTS profile patches
• Safety net pass by default & no need zygisk
• Updated build fingerprint from Pixel 7 Pro (cheetah)
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!
Awesome..!
Any chance it would run on Nokia 8.1 after unlocking/rooting with Hikari files ?
I'm mean ... someday / when updates are over .
Changelog Sat Apr 3 08:41:31 UTC 2020
===================================
1. Initial stable build
2. March security patch
3. Comes with stock kernel
4. Linux version 4.4.194
5. Vendor image from 2250
6. System blobs from 2250
7. Ota support available
Note- Installation process changed so please go ahead and follow the instructions as I mentioned in installation section
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
overclockA said:
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
Click to expand...
Click to collapse
Thanks, saved me some time. Defeats the entire purpose for me.
xe500linux said:
Thanks, saved me some time. Defeats the entire purpose for me.
Click to expand...
Click to collapse
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
overclockA said:
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
Click to expand...
Click to collapse
Ah I see. Any chance you still have a copy of your non-g build?
xe500linux said:
Ah I see. Any chance you still have a copy of your non-g build?
Click to expand...
Click to collapse
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
overclockA said:
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
Click to expand...
Click to collapse
Much appreciated!!
i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.
so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.
what did i do so far is:
*flash twrp 3.4.0
*boot up to twrp 3.4.0
*use adb shell twrp remountrw
*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it
*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally
*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)
*reboot without wiping system partition and installing lineageos only brings up normal stock rom
*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again
*wiping system partition and reboot only brings up android one loading screen endlessly
so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.
oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.
what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"
edit again.
I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:
*reflashed via fastboot the stock rom
*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)
*booted to fastboot, flashed newest twrp to boot
*booted to recovery
*adb shell twrp remountrw
*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)
*adb shell
*entered in adb shell mount /system
*adb shell twrp wipe data
*adb push lineageos.zip /data/
*adb shell twrp install /data/lineageos.zip
*adb push ddv.zip /data/
*adb shell twrp install /data/ddv.zip
*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)
*adb reboot bootloader
*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)
*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
*fastboot reboot
*then the phone - now on lineage - asked me to factory reset, i did
*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine
if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme
in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.
Hello Together,
i've installed LineageOs yesterday and i realy like it . I just can't find an camera App that supports the wideAngle Camera at the back.
Open Camera only recognizes 2 Cameras, and GCam 7.0 Nokia 7.2 Mod can't seem to access it either.
Is there a solution to this?
Best regards
Alex
Changelog Fri Nov 13 23:24:47 IST 2020
==============================
- based on latest lineage sources
- November 2020 security patch
- fixed bluetooth audio
- fixed mic
- fixed RIL
- fixed headset
- based on android 10 prebuilt vendor for now ( DDV2.340 )
- Comes with stock kernel
- linux version 4.4.192
- compiled using gcc
- fixed battery drain
- fixed styles and wallpapers
- selinux enforced
- banking apps working
- use NikGapps
Got brand new nokia 7.2 yesterday, developer loaded old android build 1_130 and unlocked bootloader, didnt recommend twrp as this wol break wi-fi. Can I flash this OS on my phone directly without twrp ? will wifi and camera work as it should? Sorry for the questions I am new here and just started reading this Thank you
Nokia is nowadays very slow in giving security patch updates to its devices. Its a high time we switch to custom rom..?
I'm waiting for my phone's warranty to get over. Anyways, do anyone have any eta on when this rom will get official?
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
dariuslapsys said:
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
Click to expand...
Click to collapse
I agree for tapp to wake up and selinux.
Nevertheless, bluetooth and microphones and fingerprint sensors are working like a charm.
NFC is not mentioned anywhere, but I don't need this function at all.
I installed the build from 14/11.
@Raghu varma: Can we help you out sending logfiles for some issues? Do you need testers?
Raghu varma said:
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip & vendor.zip
7. Now tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )
9. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
10. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
Join Nokia 7.2 Community
Download Rom
Download Vendor
Download vbmeta
Download GApps
Download Official Twrp
Android OS version: 11.0.0_r17
Security patch level: November 2020
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix Q
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to, the LineageOS team, Omni team , SlimRoms and of course to all the supporters.
Flash 10.0.12 OOS firmware via fastboot. Link is below in Downloads
Clean flash (RECOMMENDED IF COMMING FROM ANOTHER ROM):
INSTRUCTIONS
• Unpack the payload.bin using Payload Dumper
• Make sure you have the latest fastboot installed
Reboot to Fastboot mode with key combinations or using adb reboot bootloader
Reboot to fastbootd using fastboot reboot fastboot (from active device use : adb reboot fastboot to boot directly to fastbootd)
Follow all the next instructions carefully
vvvvvvvvvvvvvvvvvvv
Code:
[/B][/CENTER][/B][/CENTER][/B][/CENTER]
[B][CENTER][B][CENTER][B][CENTER]• fastboot reboot fastboot
• fastboot devices
• fastboot -w[B][COLOR="darkred"] (THIS WIPES INTERNAL STORAGE SO BACKUP YOUR DATA)[/COLOR][/B]
• fastboot erase system
• fastboot erase boot
• fastboot erase odm
• fastboot erase product
• fastboot erase vbmeta
• fastboot erase vbmeta_system
• fastboot erase vendor
• fastboot erase dtbo
• fastboot flash system system.img
• fastboot flash boot boot.img
• fastboot flash odm odm.img
• fastboot flash product product.img
• fastboot flash vbmeta vbmeta.img
• fastboot flash vbmeta_system vbmeta_system.img
• fastboot flash vendor vendor.img
• fastboot flash dtbo dtbo.img
• fastboot reboot
-UPDATE INSTRUCTIONS-
- Download the latest build of Resurrection Remix ROM
• Unpack the payload.bin
No Need for fastboot -w as this wipes data and internal storage
Follow carefully
vvvvvvvvvvvvvvvvvvv
Code:
[/B][/CENTER][/B][/CENTER][/B][/CENTER]
[B][CENTER][B][CENTER][B][CENTER]• fastboot erase system
• fastboot erase boot
• fastboot erase odm
• fastboot erase product
• fastboot erase vbmeta
• fastboot erase vbmeta_system
• fastboot erase vendor
• fastboot erase dtbo
• fastboot flash system system.img
• fastboot flash boot boot.img
• fastboot flash odm odm.img
• fastboot flash product product.img
• fastboot flash vbmeta vbmeta.img
• fastboot flash vbmeta_system vbmeta_system.img
• fastboot flash vendor vendor.img
• fastboot flash dtbo dtbo.img
• fastboot reboot
ROM Download links and change-logs are below
ROM
FIRMWARE : 10.0.13
GAPPS Already included
Sources :
ROM
Device Source Code
Kernel
Major thanks to
-> RR Team <-
XDA Developers
Phhusson for Treble trees
LineageOs Team
Omni Team
DU Team
AICP
Crdroid
Special Thanks to : MR ACAR (former RR team member)
And Of Course To All The Supporters, Donators And Users
-> Reporting bugs <-
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
After downloading the Catlog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
Join our Telegram channel : https://t.me/resurrectionremixofficial
Check FAQ on POST #2
Show your support to Resurrection Remix ROM
XDA:DevDB Information
Resurrection Remix, ROM for the OnePlus 7T Pro
Contributors
varund7726
Source Code: https://github.com/ResurrectionRemix/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest OOS 10.0.13
Based On: LOS
Version Information
Status: Stable
Created 2020-04-12
Last Updated 2021-05-17
FAQS {READ BEFORE POSTING}
Q1 Why can't I reboot to fastbootd?
Because you don't have the latest fastboot tools from google. Get them HERE
Q2 Fastboot -w is not recognized as a command
You are not on fastbootd . You are on regular fastboot(bootloader)
Reboot to fastbootd with fastboot reboot fastboot( from bootloader) or adb reboot fastboot (from system).
Fastbootd looks like OOS recovery and not like regular fastboot
Q3 I can't pass safetynet/I can't get cts profile to be valid.Now?
Flash Magisk and enable Magisk Hide
Learn how HEREhttps://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351
Q4 OTA updater doesn't work? FIXED
On purpose. Because we don't have a twrp.
Q5 My Device is stuck in Booloop / Stuck on 1+ logo
Either you have not done a clean flash if coming from another rom (fastboot -w) or you have missed something in flashing.
Make sure you follow all the steps. and make sure you have the latest fastboot tools from the link above to access fastbootd
Q6 Fingerprint scanner causes screen glitch
Known issue in all roms NOT ANYMORE. FIXED!!
Q7 Google pay won't work. Says my device is rooted. What do I do?
Flash Magisk then follow these instructions
Q8 WIll This work for Mclaren Edition of the phone?
Yes. Im personally using a HD 1913 McLaren edition. Altough I have heard reports of the t-mobile one (HD1915) having issues with RIL.
Other variants should be fine.
HD1915 I'm not sure about the 5G being retained .if it works on LOS 17.1 it works here too. Same rules apply
Q9 Why isn't X feature there? Its there in xyz rom
I have recently worked on this due to the quarantine situations that gave me time to work on it. I have worked alone and currently I am working on my own because everyone is busy with their own lives right now. If you have a feature request, I will not guarantee adding it because I may get busy.
I built this ROM for personal use but since evryone is sitting at home now I thought to publish it.
Q10 Why didn't we develop RR Q this year?
Same reason. Everybody busy with real life.
Q11 Will we be back in the next Android version?
Sure.
Q12 Will this Rom get updates?
Yes. Regular upto some point
Q13 Does this ROM come with OOS CAM?
Yes although video recording is broken. Everything else works fine . Use Snap (stock) cam for this.
FIXED!
Q14 Can I build this rom from source?
Currently no as only I have access to that. I want to keep it this way for Android 10 to avoid all the hastle.
Q15 Any other supported devices?
None as of now and I dont plan to. This rom is only for the Oneplus 7T Pro, OnePlus 7 pro and OnePlus 6T fajita as the others have a lot of roms anyways. Although I might just make this build for Oneplus6 (enchilada)
Special Notice
Code:
Hi guys, I hope you guys are home and safe. These are crazy times and everybody is at home. This ROM is a little gift for those who are bored and want to have a little fun. Enjoy, be safe & take care
Screenshots
Can I use this one the OnePlus 7t pro 5g McLaren from tmobile and still get 5g if so how would I will I be able to flash this and is there a different steep I need to take to have it work
NickMidd91 said:
Can I use this one the OnePlus 7t pro 5g McLaren from tmobile and still get 5g if so how would I will I be able to flash this and is there a different steep I need to take to have it work
Click to expand...
Click to collapse
Please read FAQ
Like I said , if it works on LineageOS it will work with this rom as the kernel is the same
varund7726 said:
Please read FAQ
Like I said , if it works on LineageOS it will work with this rom as the kernel is the same
Click to expand...
Click to collapse
Ok thanks but I have not tried it on that rom
Holy **** that's awesome.
Any luck on future fixing oos camera recording?
kubek1334 said:
Holy **** that's awesome.
Any luck on future fixing oos camera recording?
Click to expand...
Click to collapse
Try this, go in OOS Camera, Enable Wide angle lens, then go to video.
Worked for me in other AOSP roms that had problems with video mode
New build is up
Main changes
--
Code:
--- added scrolling screenshot
-- added 2 new accents in themes ( lime and rich red).
-- fix screen recorder audio
-- added faceunlock (settings-> security -> face unlock)
--added AOD tile
-- Minor fixes
didn't expect this coming! good old RR mate tell us if gcam works with photo and video and if autobrightness works as it should? Lineage has this issue and this rom is based on Lineage, so is this working properly? thanks man for your hard work, I see you push builds today with fixes, I hope RR will shine on our beloved device
autobrightness is working fine,
could you add ambient display settings? (i dont see such option on settings)
When selecting a notificantion from the lockscreen doesnt let me use the fingerprint to unlock the device, only the pattern
Just booted for me, everything seems to work except of fingerprint sensor
thank's for your work
Fingerprint is working except fact that it causes screen to flash (usually issue on custom roms)
However autobrightness is too Darka.
Anyway awesome rom
cant get magisk to work
hey guys cant get magisk to work put boot img in internal storage and when to install it does nothing and cant twrp as it doesnt work atm oneplus 7t pro sorry noob david
There is no twrp. Read manual once more time
heardd11 said:
hey guys cant get magisk to work put boot img in internal storage and when to install it does nothing and cant twrp as it doesnt work atm oneplus 7t pro sorry noob david
Click to expand...
Click to collapse
you must patched first the boot img in magisk.
then boot the patched img in fastboot and if its boot go to magisk and do direct install. and reboot.
Verstuurd vanaf mijn OnePlus 7T Pro met Tapatalk
beaverhead said:
you must patched first the boot img in magisk.
then boot the patched img in fastboot and if its boot go to magisk and do direct install. and reboot.
Verstuurd vanaf mijn OnePlus 7T Pro met Tapatalk
Click to expand...
Click to collapse
you must patched first the boot img in magisk did this and it doesnt do anything were im stuck its weird done it on oxygen os david
Can we flash on regular 7p not t
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DivestOS is a more private and more secure aftermarket system.
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-walleye
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#walleye
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_google_muskie, https://github.com/LineageOS/android_device_google_wahoo
- Kernel: https://github.com/LineageOS/android_kernel_google_wahoo
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...1/CVE_Patchers/android_kernel_google_wahoo.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
Thanks for DivestOS and support of the Pixel2 walleye.
I had some confusion installing it before I succeeded.
Here are the generic instructions from the DivestOS website: https://divestos.org/index.php?page=bootloader
I copy pasted the instructions below and left only the instructions specific to walleye plus a few steps I took.
Here are the steps from those instructions which I used (I removed unnecessary steps for walleye)
Enable 'Allow OEM unlocking' under 'Developer options' in Settings if available
Reboot to the bootloader via key combination or $ adb reboot bootloader
$ fastboot flashing unlock
$ fastboot update divested-version-date-dos-device-fastboot.zip
Be ready to hold down volume down button so reboot (after flashing from previous step) will be to bootloader again
$ fastboot -w to wipe data (not sure if necessary, but I did it)
$ fastboot set_active a (if current Boot-slot is b or vice versa)
I then repeated step 4 and after flashing was finished, I let the phone boot into Android system
re-enable developer-options and then $ adb reboot bootloader
Then set the custom operating system key:
$ fastboot erase avb_custom_key
$ fastboot flash avb_custom_key avb_pkmd-device.bin
After this, I relocked the bootloader $ fastboot flashing lock , then rebooted into Android system.
The official DivestOS instructions recommend to leave the OEM unlocking setting to ON to reduce the risk of a permanent brick after a bad update in the future.
After a couple of weeks, I'll see what happens after an OTA update arrives so I can be confident that both slots A and B are functioning correctly.
Any feedback is welcome on whether some of my steps are a bad idea or unnecessary. This is not a guide, just my feedback on what I did to get DivestOS working with the bootloader relocked on my walleye phone.
zpunout said:
Thanks for DivestOS and support of the Pixel2 walleye.
I had some confusion installing it before I succeeded.
Here are the generic instructions from the DivestOS website: https://divestos.org/index.php?page=bootloader
I copy pasted the instructions below and left only the instructions specific to walleye plus a few steps I took.
Here are the steps from those instructions which I used (I removed unnecessary steps for walleye)
Enable 'Allow OEM unlocking' under 'Developer options' in Settings if available
Reboot to the bootloader via key combination or $ adb reboot bootloader
$ fastboot flashing unlock
$ fastboot update divested-version-date-dos-device-fastboot.zip
Be ready to hold down volume down button so reboot (after flashing from previous step) will be to bootloader again
$ fastboot -w to wipe data (not sure if necessary, but I did it)
$ fastboot set_active a (if current Boot-slot is b or vice versa)
I then repeated step 4 and after flashing was finished, I let the phone boot into Android system
re-enable developer-options and then $ adb reboot bootloader
Then set the custom operating system key:
$ fastboot erase avb_custom_key
$ fastboot flash avb_custom_key avb_pkmd-device.bin
After this, I relocked the bootloader $ fastboot flashing lock , then rebooted into Android system.
The official DivestOS instructions recommend to leave the OEM unlocking setting to ON to reduce the risk of a permanent brick after a bad update in the future.
After a couple of weeks, I'll see what happens after an OTA update arrives so I can be confident that both slots A and B are functioning correctly.
Any feedback is welcome on whether some of my steps are a bad idea or unnecessary. This is not a guide, just my feedback on what I did to get DivestOS working with the bootloader relocked on my walleye phone.
Click to expand...
Click to collapse
Please follow the steps as on the site.
Developer options has NO effect on whether on not fastboot or adb is enabled in the recovery.
Do not manually swap the slots, instead use the slot sync script after the `fastboot update command` as laid out in the steps.
Do flash the OTA again, as fastboot zip does not contain firmware!
Do not immediately lock, you are supposed to verify boot first so you don't end with locked brick.
I've personally tested taimen working.
SkewedZeppelin said:
Please follow the steps as on the site.
Developer options has NO effect on whether on not fastboot or adb is enabled in the recovery.
Do not manually swap the slots, instead use the slot sync script after the `fastboot update command` as laid out in the steps.
Do flash the OTA again, as fastboot zip does not contain firmware!
Do not immediately lock, you are supposed to verify boot first so you don't end with locked brick.
I've personally tested taimen working.
Click to expand...
Click to collapse
Thanks for the quick reply. I have a taimen I want to install DivestOS onto as well. I recall that on the walleye device, I couldn't get adb sideload to work in recovery, so couldn't run the slot sync script.
I'll try the steps outlined in the official guide again with the taimen device.
zpunout said:
Thanks for the quick reply. I have a taimen I want to install DivestOS onto as well. I recall that on the walleye device, I couldn't get adb sideload to work in recovery, so couldn't run the slot sync script.
I'll try the steps outlined in the official guide again with the taimen device.
Click to expand...
Click to collapse
If adb shows no devices try running with sudo.
Also Pixel 1/2 has broken USB, so make sure to use a USB 2.0 port or hub.
SkewedZeppelin said:
If adb shows no devices try running with sudo.
Also Pixel 1/2 has broken USB, so make sure to use a USB 2.0 port or hub.
Click to expand...
Click to collapse
Thanks for the tip about using a hub. It solved my headaches in recovery with the sideload command. Now the official instructions work perfectly after flashing back to stock and then DivestOS.
An experimental 12.1 based build is up with near full feature parity.
I've tested it working quite well on my taimen, should be fine on walleye.
SkewedZeppelin said:
I've tested it working quite well on my taimen, should be fine on walleye.
Click to expand...
Click to collapse
The Google Pixel 2 (walleye) with divested-19.1-20220411-dos-walley Experimental has been successfully tested on April 15, 2022, and here documented. Meanwhile, I'm running build divested-19.1-20220613 with relocked bootloader.
any new update for walleye?
galibalmasanick said:
any new update for walleye?
Click to expand...
Click to collapse
Regarding?
All devices get updates once, sometimes twice, per month.
The August ASB isn't even public yet, and I won't start a build until after.
See the news page: https://divestos.org/index.php?page=news
SkewedZeppelin said:
Regarding?
All devices get updates once, sometimes twice, per month.
The August ASB isn't even public yet, and I won't start a build until after.
See the news page: https://divestos.org/index.php?page=news
Click to expand...
Click to collapse
Ok,Thank You
Hi.
I have a Pixel2 with Grapheneos already installed.
Should I re-flash the stock rom before installing Divestos?
Thankyou.
altromass said:
I have a Pixel2 with Grapheneos already installed.
Should I re-flash the stock rom before installing Divestos?
Click to expand...
Click to collapse
Nah, you can just flash over to DivestOS.
Hi.
How is it supposed to be used the copy-partitions-walleye-release.zip file?
Is it someting to do with copying the OS to both slots?
I used the command fastboot set_active a to install divestos on the other slot as well.
Would it be ok?
Thank you!
altromass said:
Hi.
How is it supposed to be used the copy-partitions-walleye-release.zip file?
Is it someting to do with copying the OS to both slots?
I used the command fastboot set_active a to install divestos on the other slot as well.
Would it be ok?
Thank you!
Click to expand...
Click to collapse
No you don't either of those steps.
Firmware is included on taimen/walleye.
Bootloader - DivestOS Mobile
divestos.org
You only need steps 1, 2, 3, 4, 5, 6, 7, 9, 11, 12, 13, 14, 15
I'd like to use this ROM but there's one tiny feature I need root for: the app Battery Charge Limit which modifies a single, specific system file. Is there any way around it?
It sounds like a neat ROM for a spare device used solely for crypto operations, but unfortunately not for banking apps based on SafetyNet (because SafetyNet won't work without Google services).
There is no way around that.
There is no proper solution for an integrated battery charge limit.
And root is not supported: https://divestos.org/index.php?page=faq#rootSupport
Kirisakura-Kernel for the Pixel 6/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 6 Pro aka Raven and the Pixel 6 aka Oriole, together Raviole.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
The kernel aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance!
This includes Linux-Stable, F2FS-Stable and kernel/common!
If that got you curious, have a read about linux-stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Features:
Main Features:
- Based on latest A13 kernel sources from Google, Kernel is made for Android 13
- Linux-Stable-Upstream included to 5.10.183
- Compiled with prebuilt Google clang 17.0.2
- Backport entire RCU subsystem to Linux 6.0
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- Backport Maple tree from Linux 6.1
- improve preallocations from maple tree (affects especially android)
- reduce necessity to rewalk the maple tree
- Per VMA-locks in conjunction with Maple Tree RCU-Mode (improve app launch time, this feature in general benefits greatly from lazy rcu!)
- further improve maple tree/per-vma locks introduced in an earlier release
- make TEO-Cpuidle util-aware (improves latency, performance and decreases energy consumption for certain workloads, more information here)
- FHD Support for Pixel 6 Pro (display is able to run at 1080p), more info here and here
- merged kernel/common (improvements to android-common-kernel straight from google)
- MM subsystem reworked (more info and some patchsets linked in this post)
- Multi-gen LRU backported/reworked and enabled (more info here, here as well and here) to improve mm and reduce cpu cycles, latest V15 state
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- Utilize an additional kswapd thread to increase throughput for memory reclaim
- pelt multiplier tied into powerhal to speed up scheduler during interaction (more info here)
- prevent frequency spikes caused by small transient tasks when the device is idle(more info here)
- tie mechanism to prevent frequency spikes caused by small tasks also into powerhal
- scheduler improvements for RT (realtime) tasks
- introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads, more information here)
- improve camera performance by tuning the powerhal during recording
- bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions
- improve app launches via powerhal
- improve trusty driver performance which connects to fingerprintscanner-hal by using high perf wq during fp unlock
- restrict maximum CPU-Freqs during screen off/ idle to 1.1GHZ for all clusters to save power
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf under heavy load
- fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
- enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
- F2FS-Stable updated
- merge and enable f2fs block_age-based extent cache (improve the accuracy for data temperature classification, reduce the garbage collection overhead after long-term data updates)
- TCP backports from mainline
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- Scheduler updates from linux-main
- use improved energy model for exynos cpu cooling/thermal control
- allow GPU to scale down to 150mhz, but boost to higher value in case of interaction via powerhal
- affine IRQS to CPU 7 during camera usage for improved performance as it tends to overload the little cores
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- include bbrv2 from google, more info here
- Enable support for TTL spoofing
- Include LRNG, see here and here for more info, bump to v45 with 3.0.0
- important patches from kernel/common for 5.10 (here are more details)
- CleanSlate Features from @tbalden, big applause here! (s2s, notification booster, battery saver, flashlight notifications. Please note: cleanslate features that work otherwise with rooted devices like kadaway (adblocking) are not implemented on this kernel since I´m running rooted)
- dirty pipe exploit fixed
- supports direct usb access for hi-res playback over USB-C DACs
- improve ZRAM usage
- reduce overhead
- improve performance and efficiency by properly wiring up pixel_sched with teo util awareness (thanks @ada12 for spotting this!)
- update to cpuset/cgroup subsystem (speeds up camera launches, device unlocks etc as cpusets are switched on those conditions, patches reduce overhead in those conditions)
- flashing the kernel will preserve root
Various Optimizations:
- update several drivers to use power efficient workingqueues (for example wlan driver)
- kernfs: use buffer from the stack space
- printk: use buffer from the stack space
- kthread: use buffer from the stack space
- bpf: avoid dynamic memory allocation for small value buffers
- binder: Reserve caches for small, high-frequency memory allocations
- kernfs: use kmem_cache pool for struct kernfs_open_node/file
- cgroup: use kmem_cache pool for struct cgrp_cset_link
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- mm: vmstat: use power efficient workingqueues
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
AK3 Helper Module:
- restrict little cluster to 1,19ghz mid cluster to 1,19ghz and big cluster to 1,1ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- tie pelt multiplier into the powerhal (more info here)
- prevent frequency spikes caused by small transient tasks during idle operation (more info here)
- boost scheduler using the pelt multiplier during fingerprint unlock operation
- setup and control PMU limiter via powerhal (more info here)
- dynamically adjust target load for memory interface during interaction
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
DOWNLOAD:
Download is always located in this folder:
4.2.0, 4.3.0, 4.4.0, 4.4.1, 4.4.2 are attached to the release posts linked below as AFH is wonky at the moment.
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Changelog:
Android 12.0.0
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85910621
1.0.5 https://forum.xda-developers.com/t/...r-pixel-6-pro-aka-raven.4358435/post-85924419
1.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-85976139
1.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86109665
1.5.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86259863
1.7.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86390563
1.8.4 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86541727
Android 12.1.0 Stable (March feature drop and more recent)
2.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86617873
2.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86637233
2.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86695911
2.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86821331
2.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86834981
Android 12.1.0 Stable (June feature drop and more recent)
3.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86992705
3.0.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86996237
3.0.17 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87127695
Android 13.0.0 Stable (not QPR beta!)
4.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87290247
4.1.6 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87399635
4.2.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87524609
4.3.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87697425
4.4.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87823333
4.4.1 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87944879
4.4.2 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88118201
Raviantha 1.0.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88316223
Raviantah 1.0.2 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88399941
Raviantah 1.1.0 https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-88645115
Android 12L QPR Beta - Deprecated
Spoiler
Build for Android 12 QPR Beta: https://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-86857033
Requirements
- the kernel is made for the stock firmware provided by Google, pay attention to flash a kernel release matching the firmware (flashing on custom roms might work, but you may need workarounds!)
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment so you can flash back to stock in case something goes wrong
- working magisk environment (a device rooted with latest magisk stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13! (take a look here)
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the correct kernel.zip depending on your device (Pixel 6 = oriole || Pixel 6 Pro = raven)
2. Flash the correct kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved. The AK3 magisk helper module will be automatically installed during flashing the kernel.zip and be present on next reboot.
Do not remove or disable the AK3 Magisk Helper Module otherwise the device will bootloop.
3. Reboot and profit.
Manual installation is no longer supported starting with release 3.0.0, as there´s a free open-source option to flash kernel.zips now.
Instead use the free kernel flasher, which can be found here.
Spoiler: Manual Installation for 1.4.0 and higher
Manual installation without relying on paid apps like fkm/exkm:
Please have a look at the linked post.
Spoiler: OLD Instructions - 1.3.0 and older - Use only on November Firmware
Check post #5
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea/beer
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@capntrips for all his work on the pixel 6!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
Source Code: https://github.com/freak07
F.A.Q:
Question: How do I update my phone to a new monthly update if this kernel is installed?
Answer: The easiest solution is to just use any full firmware package to update your phone to the new stock firmware. You can do so with the android web flash tool, a factory image or a full OTA image.
An excellent guide on how to use the factory image to do so was posted by @roirraW "edor" ehT on this thread. Feel free to use this as a reference.
This also serves as the easiest way to return back to stock, if you don´t like the kernel and feel not comfortable flashing anything via fastboot.
Question: How do I return back to stock?
Answer: Extract boot.img, dtbo.img, vendor_boot.img, vbmeta.img and vendor_dlkm.img from the matching factory image provided on googles download page.
If you disabled verity/verification previously there´s no need to flash the vbmeta.img when restoring.
If you want to stay rooted make sure to flash a boot.img that has been patched with magisk.
Flash those images via fastboot/fastbootd and you will be back on stock kernel. If you don't know the fastboot commands to flash the images, check the instructions how to flash those images in post #4.
Alternatively dirty flash the whole firmware without wiping by using either the android web flash tool, a factory image or a full OTA image. If you disabled the vbmeta flags, don't forget to disable them again (or tick the correct options on the web flash tool) after flashing a full firmware package and re-root.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a supported firmware. Usually I'm announcing in the release post, the firmware the kernel.zip is compatible with, but most of the time the kernel is updated when a firmware update drops.
Please make also sure you're running a stock configuration.
That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. (kernel flashing apps usually support exporting logs of flashes too) If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself, reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?
Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".
Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.
If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.
I recommend taking a look at this excellent collection of helpful threads from @roirraW "edor" ehT!
It can be found following this link!
Question: I get a device corrupted message after flashing the kernel or just reboot to bootloader. How to get rid of it?
Answer:
There seems to be an issue with verity on Pixel devices that can trigger randomly. That means even if the expected hashes match the device refuses to boot due to this bug.
A workaround for A12 has been shared in the following post linked here. It seems this issue happens randomly on devices without the vbmeta flags for verity/verification disabled.
Essentially flashing/booting (booting should be enough) a boot.img from an older firmware, letting it attempt to boot but fail, and then restore boot.img from the matching firmware clears the message.
If you´re doing this while having the kernel installed don´t forget to flash back to stock completely, which is also described in the FAQ.
There seem to be cases on A13, where this verity bug is still triggered during some flashes, essentially booting straight back to bootloader. It seems all cases reported here were solved by reflashing the firmware via the web flash tool from google, without wiping data. Interestingly flashing back an older boot.img was not needed there.
AOSP Build Environment and Standalone Kernel builds (monolithic builds)
I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.
You can find more information about GKI following this link.
What does that mean for custom kernels and this custom kernel?
The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.
However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.
On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)
On the Pixel 6 I wasn´t able to achieve this yet. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.
What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.
Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.
The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.
Fastboot commands:
Flash the images in this order:
Boot to bootloader:
Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command while in the OS:
or type:
Code:
adb reboot bootloader
Now in fastboot flash boot.img, dtbo.img, vbmeta.img (vbmeta can be left out if you disabled verity/verification) and vendor_boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
caution with the vbmeta.img, if you disabled verity/verification flashing this images without the flags will re-enable both verity and verification! If you disabled verity/verification on your device there´s no need to restore it.
fastboot flash vbmeta vbmeta.img
Now boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit![/SPOILER]
Spoiler: Deprecated. Just here for collection.
Manual Installation:
Note:
Manual Installation will not be supported and updated since 3.0.0 and going forward.
There´s a free and open source alternative to FKM or EXKM that supports flashing kernel.zips.
You can find it following this link.
Spoiler
This is for advanced users or users that don´t want to rely on paid apps to flash the flashable kernel.zip introduced with 1.4.0.
These instructions are not to be mixed with those in the first post and do apply for kernel releases 1.4.0 and more recent!
1. Download the boot images provided in the downloads section under the version you want to flash and then manual install to your PC. Make sure to use the correct ones for your device. Patch the boot.img with magisk.
Download the zip matching your device from the download folder and the version you want to flash.
From the zip extract dtbo.img, vendor_boot and vendor_dlkm.img
1.a : Download the powerhint magisk module found in downloads section and flash it via Magisk Manager like any other magisk module. Don´t forget to flash it, it´s tied to changes in the kernel. It´s crucial for the kernel to work. Without the module flashed before flashing the images the device will not boot!
2. Flash the provided images using fastboot/bootloader and fastbootd (these are seperate modes, see instructions below)
2a. Don´t forget to patch the provided boot.img in magisk manager prior to flashing it via fastboot. Of course you need to adjust your command to flash like you did when rooting the device.
3. vendor_dlkm.img needs to be flashed in fastbootd, while the other images need to be flashed via fastboot/bootloader
Flash the images in this order:
Boot to bootloader:
Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command
or type:
Code:
adb reboot bootloader
Now in fastboot flash boot.img, dtbo.img and vendor_boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
Now boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!
Instructions for flashing Release 1.3.0 or below.
These kernel releases are only for November firmware. They will bootloop on anything that´s more recent.
Spoiler: Instructions - Release 1.3.0 and older -Only for November Firmware
0. Do not use this if you´re on any firmware more recent that November 2021!
1. Download the images provided in the downloads section to your PC.
1.a Optional: Download the powerhint magisk module found in downloads section and flash it via Magisk Manager like any other magisk module.
2. Flash the provided images using fastboot/bootloader and fastbootd (these are seperate modes)
2a. If you want to stay rooted patch the provided boot.img in magisk manager prior to flashing it via fastboot. Of course you need to adjust your command to flash like you did when rooting the device.
3. vendor_dlkm.img needs to be flashed in fastbootd, while the other images need to be flashed via fastboot/bootloader
How to boot to fastbootd
From running phone:
Code:
adb reboot fastboot
From fastboot/bootloader:
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
Boot from fastbootd to fastboot/bootloader to flash dtbo.img and boot.img:
Either select Reboot to bootloader option via buttons
or type:
Code:
fastboot reboot bootloader
Now in fastboot flash boot.img and dtbo.img
Commands:
Code:
fastboot flash dtbo dtbo.img
fastboot flash boot boot.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!
So glad to see you here. Such a staple in this community.
Let the Development Begin for the Pixel 6 Pro! kudos
Please post in pixel 6 forum also I will test when I get home
great to you made good progress
Confirmed working on pixel 6, testing now! thanks for the hard work
I have the error FAILED (remote: No such file or directory) for flashing vendor_dlkm in fastbootd mode, does anyone has any clue why?
edit: Never mind, used a different fastboot/adb and it works.
Can confirm works perfectly on Pixel 6 now for one of us to get a working twrp or other recovery.img
allenjthomsen said:
Can confirm works perfectly on Pixel 6 now for one of us to get a working twrp or other recovery.img
Click to expand...
Click to collapse
Works here perfectly as well here too.
I know the kernel is barebones but i wanted to know if there's any Wireguard implementation within the kernel. Thanks dev for your hard work.
@Freak07 My goodness great work sir! The first custom kernel for the OnePlus 6 Pro.
So far running very well!
Just some few early unusual observations, and this might be my only unit doing this:
1) Device is slightly snappier now. But this seems to come at the cost of fluidity. Doesn't feel quite as smooth as stock kernel.
2) When the device is charging, the charging device vibration haptics randomly buzzes from time to time - when a cable is plugged in. It would never do this on stock kernel. Again. Might be just some sort of weird fluke as I just literally flashed this.
Is it possible you could implement KCAL color commits to alter saturation white point controls? If there's ever a device that needs it, I'd say it's this one. That yellowish piss hue on the screen is simply gross. The six Pro has the clearest screen I've ever seen, but the color reproduction looks nothing short of horrendous. I don't understand why Google doesn't implement white point or wide color gamut support on Pixel devices. It's a night and day difference to your eyes. I love that dopamine kick from seeing beautiful, vibrant colors.
EDIT: Also, I can't stress enough. This first build is nothing short of amazing. I know it's super tough because this is all new stuff.
Could you possibly consider adding some CAF boost controls sometime in the future? It's so awesome to build and make the device a little bit snappier on command^
EDIT 2: this might be far too early to tell, but there seems to be a bug with charging. Along with the random vibrations going off, the charging speed is unusually slow. Again, this might be only my device doing this (Fluke) so maybe other people can concur.
EDIT 3: just noticed another bug. Again. This might be only my device. LTP0 doesn't seem to work. Everything is locked at 120 Hertz. Not sure would have caused that. I've rebooted a few times and it's still there. I can provide any logs of necessary.
Zilla0617 said:
I know the kernel is barebones but i wanted to know if there's any Wireguard implementation within the kernel. Thanks dev for your hard work.
Click to expand...
Click to collapse
Wireguard was implemented by Google in the Android 12 kernel.
Google adds WireGuard VPN to Android 12's Linux Kernel
Google just made a big move to bring WireGuard VPN kernel acceleration to Android 12 by merging support in Linux Kernel 4.19 and 5.4 trees.
www.xda-developers.com
vassosman said:
Wireguard was implemented by Google in the Android 12 kernel.
Google adds WireGuard VPN to Android 12's Linux Kernel
Google just made a big move to bring WireGuard VPN kernel acceleration to Android 12 by merging support in Linux Kernel 4.19 and 5.4 trees.
www.xda-developers.com
Click to expand...
Click to collapse
I prefer to activate it without the slower VPN key method. If you have a custom kernel, you can activate it in the background (without the VPN key). Right now if try to activate Wireguard on the stock kernel the tunnel is created via the key.
I just had a reboot. I've attached my pstore folder.
same getting random reboots every so often
ill get my pstore and upload it for you in a few
Awesome, now a reason to get root.