[CLOSED][ROM][UNOFFICIAL][9.0][Daredevil] LineageOS 16.0 [2019/11/28] - Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel

[CLOSED][ROM][UNOFFICIAL][9.0][Daredevil] LineageOS 16.0 [2019/11/28] - Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
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 , Perf-Stock-9.0-DDV_sprout.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
7. Now tap on reboot and tap on recovery now your phone reboots in to twrp again
8. 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
9. Now flash Gapps.zip
10. Now flash Perf-Stock-9.0-DDV_sprout.zip
11. Wipe all except system & vendor
10. Tap on reboot bootloader
11. Now your phone boots in to bootloader mode
12. 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 )
13. 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 Stock Pie kernel
Download vbmeta
Download Gapps
Download Official Twrp
Android OS version: 9.0.0_r46
Security patch level: October 2019
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

Whats working?
Ril
Wifi
Mobile data
Double tap to wake
Double tap to sleep
Adaptive brightness
Dark theme
Ambient display
Flash light
Sound / vibration
Camera
Volte
Selinux - permissive
Fingerprint
Known issues
All fixed for now . comment below if you face any bugs
FLASH GAPPS MANUALLY

Awesome work.. Great work..!

Thank you. Works good

Works like a charm!! ????

This is just awesome. Thanks for being that fast!
I ordered a Nokia 7.2 as business phone. First thing I'll do is unlock and flash this rom. Wouldn't have ordered without LOS support.

How is the battery life compared to stock? Somebody who is currently using this, could someone pls let know about this? Thanks.

Hey! I guess I messed up... bootloader is unlocked but when I tried to flash with TWRP, for any reason I still having the "original" boot running and now I have no wifi... Any one can provide me a guidance?

JoSoFer said:
Hey! I guess I messed up... bootloader is unlocked but when I tried to flash with TWRP, for any reason I still having the "original" boot running and now I have no wifi... Any one can provide me a guidance?
Click to expand...
Click to collapse
Here twrp file will perform as two ways
Boot & twrp
If you know what exactly a/b partition phone does you won't get this doubt.

Do you HAVE to flash Gapps if you dont want them?

Talon Pro said:
Do you HAVE to flash Gapps if you dont want them?
Click to expand...
Click to collapse
Why? I have been using LineageOS on different devices without Gapps for years. So there is no need to flash them if you don't want them.

Ungewiss said:
Why? I have been using LineageOS on different devices without Gapps for years. So there is no need to flash them if you don't want them.
Click to expand...
Click to collapse
Just checking, oddly, Android is new to me...

Do we need or can we lock the bootloader after to keep the warning showing every time you reboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:04 AM ----------
BUG- Double tap to wake not working, the slider is set to ON. I tried turning it off and back on and rebooting the phone and that didnt work on this ROM.

Talon Pro said:
Do we need or can we lock the bootloader after to keep the warning showing every time you reboot?
Click to expand...
Click to collapse
Hi, please understand how bootloaders work. The locked bootloader ensures that secure boot is in place and the device will deny to boot if it notes any tampering from the OEM's hashes. So, never lock the bootloader on a custom software - the device will more or less become a brick ?

singhnsk said:
Hi, please understand how bootloaders work. The locked bootloader ensures that secure boot is in place and the device will deny to boot if it notes any tampering from the OEM's hashes. So, never lock the bootloader on a custom software - the device will more or less become a brick
Click to expand...
Click to collapse
All you had to say was "no".

Talon Pro said:
All you had to say was "no".
Click to expand...
Click to collapse
I just tried to explain it a bit.

nvm

Any idea on the DTTW issue?

Will this ROM become official?

BigFatTony said:
Will this ROM become official?
Click to expand...
Click to collapse
Not even interested to follow their rules & regulations towards official tag. Due to i don't know when i will do builds. & I don't know when i will update or bug fixes. completely depends on my schedule So not interested towards official tag & also iam not ready to follow their rules as well.
Main reason - my schedule and my infra

Related

[CLOSED][ROM][OFFICIAL][10.0][Dragon] Havoc-OS 3.8 [2020/08/18]

Download Rom
Download Official Twrp
Android OS version: 10.0.0_r41
Security patch level: August 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/Havoc-OS
ROM Developer: Anushek Prasal

screenshots

Havoc-OS initial build is Up
For Nokia 6.1 Plus
Code - Dragon
Changelog
1. Initial Q beta build
2. Based on Q beta vendor.img
3. System blobs from 4040
4. October security patch
5. for Installation procedure go through installation section once

When I boot up TWRP there's no option to type "yes," just the swipe to allow modifications.

@Raghu varma, Please Make this rom for Nokia 6.1 (Pl2)
your work with 6.1 plus is very admirable and I'm currently using the PE rom you built for 6.1 . it would be great if you look into pl2 and build havoc for it

FatinX said:
@Raghu varma, Please Make this rom for Nokia 6.1 (Pl2)
your work with 6.1 plus is very admirable and I'm currently using the PE rom you built for 6.1 . it would be great if you look into pl2 and build havoc for it
Click to expand...
Click to collapse
Let's see

Wonderfull

Do not show USB link with PC. Unable to transmit data. Enter recovery mode, then transfer the data norm
ally

PvTuan said:
Do not show USB link with PC. Unable to transmit data. Enter recovery mode, then transfer the data normally
Click to expand...
Click to collapse
Did you flash Q kernel?

PvTuan said:
Do not show USB link with PC. Unable to transmit data. Enter recovery mode, then transfer the data norm
ally
Click to expand...
Click to collapse
check now. issue with your pc or your phone or your usb port so please dont post your personal phone stuff blindly please

attach microphone without sound, speakerphone still plays sound
---------- Post added at 06:13 AM ---------- Previous post was at 06:06 AM ----------
Raghu varma said:
check now. issue with your pc or your phone or your usb port so please dont post your personal phone stuff blindly please
Click to expand...
Click to collapse
rom before, data transfer is still normal so there is no reason pc has problem. and really sad. I experienced and had suggestions for the best rom. You said I was blindly. Sorry. i will not comment anymore.

PvTuan said:
attach microphone without sound, speakerphone still plays sound
---------- Post added at 06:13 AM ---------- Previous post was at 06:06 AM ----------
rom before, data transfer is still normal so there is no reason pc has problem. and really sad. I experienced and had suggestions for the best rom. You said I was blindly. Sorry. i will not comment anymore.
Click to expand...
Click to collapse
Check new build. For that micro phone stuff
Coming to this " i will not comment anymore "
Note before posting something related to bug check twice or thrice. If you blindly post something which is not related to bug. That actually makes me triggered for something without any valid reason. here not only you few people will do for spamming the board. Hope you got this point

volte not working
jio outgoing call{call ended error} and sms not working ,only incomming call working

In the today build, there's no double tap to wake?

Sorry, I try Headset Bluetooth is not working. There is solution?

New builds are up
changelog
* Based on latest havoc sources
* Comes with prebuilt vendor.img
* Linux version - 4.4.165
* November security patch
* Flash open-gapps-10.0-nano

Bootloader Unlocking
How do I unlock the bootloader on nokia 6.1 plus? There appears to be only one source, which claims to unlock the bootloader but, they charge money and I don't think it is a credible source. Can anyone help me?

nisarg13 said:
How do I unlock the bootloader on nokia 6.1 plus? There appears to be only one source, which claims to unlock the bootloader but, they charge money and I don't think it is a credible source. Can anyone help me?
Click to expand...
Click to collapse
Visit https://techmesto.com or https://hikaricalyx.com/product/hmd-nokia-bootloader-unlock/ to get information regarding bootloader unlock. Both of them charge money, and till Nokia allows official bootloader unlock, you only have those two options.

Changelog
15/12/2019
1. 3rd party apps calls fixed
2.Whatsapp video calls & 3rd party apps video calls fixed
3. Vendor blobs updated from Nokia 7.1 android Q stable build
4. Global network issues also fixed
5. Nuked OnePlus camera & shipped with stock Snapdragon camera.

Changelog
* shipped with Google apps
* No need to Flash Gapps from Now

[CLOSED][ROM][UNOFFICIAL][9.0][Starlord] LineageOS 16.0 [2019/11/09]

{
"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"
}
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 , Perf-Stock-9.0-SLD_sprout.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
7. Now tap on reboot and tap on recovery now your phone reboots in to twrp again
8. 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
9. Now flash Gapps.zip
10. Now flash Perf-Stock-9.0-SLD_sprout.zip
11. Wipe all except system & vendor
10. Tap on reboot bootloader
11. Now your phone boots in to bootloader mode
12. 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 )
13. 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 6.2 community Thank you all for your massive support Again
Join Nokia 6.2 Community

Whats working?
Ril
Wifi
Mobile data
Double tap to wake
Double tap to sleep
Adaptive brightness
Dark theme
Ambient display
Flash light
Sound / vibration
Camera
Volte
Selinux - permissive
Fingerprint
Known issues
All fixed for now . comment below if you face any bugs
FLASH GAPPS MANUALLY

Very nice rom [emoji1]
Sent from my [device_name] using XDA-Developers Legacy app

Installation experience
First of all, thanks for releasing a ROM on the same week that I purchased the new device!
At first I tried to just the stock ROM, running with TWRP and Magisk, and that worked with one reboot, but after select reset to factory settings in booted OS, it booted back to recovery in a recovery.
I had a problem with Magisk v20.1, which decided to leave my phone in a recovery bootloop (seems like it is a common issue on other phones too).
As I didn't have a backup of the original ROM (yes, I know I should have done this as soon as I had TWRP booted!), I had to install this ROM.
So far the installation went really well, but the switching between _a and _b seems a necessary step for some reason ? What will happen in future? Do we need to keep switching between _a and _b half way through the installation process ? Why do we need to do this between the ROM install and gapps install ?
If I want to install TWRP again after this ROM, should I overwrite boot_a and boot_b with your latest TWRP ?
Again, thanks for the ROM, it saved me from the recovery bootloop!

tusker said:
First of all, thanks for releasing a ROM on the same week that I purchased the new device!
At first I tried to just the stock ROM, running with TWRP and Magisk, and that worked with one reboot, but after select reset to factory settings in booted OS, it booted back to recovery in a recovery.
I had a problem with Magisk v20.1, which decided to leave my phone in a recovery bootloop (seems like it is a common issue on other phones too).
As I didn't have a backup of the original ROM (yes, I know I should have done this as soon as I had TWRP booted!), I had to install this ROM.
So far the installation went really well, but the switching between _a and _b seems a necessary step for some reason ? What will happen in future? Do we need to keep switching between _a and _b half way through the installation process ? Why do we need to do this between the ROM install and gapps install ?
If I want to install TWRP again after this ROM, should I overwrite boot_a and boot_b with your latest TWRP ?
Again, thanks for the ROM, it saved me from the recovery bootloop!
Click to expand...
Click to collapse
Hy there well your question
Why do we need to do this between the ROM install and gapps install ?
Here is my answer
We all know that what exactly a/b concept does
If we flash a zip from slot a automatically the zip installation will be done on alternative slot means inactive slot ( if you flash from A obviously inactive will be slot B ) now what next?
You question is why we need to switch slot after flashing ROM and flash gapps ?
Yes you have to switch because ROM has been installed on slot B here if you don't switch the slot and if you flash gapps automatically gapps will be installed on empty system because ROM flashed on slot b . so you have to switch and flash gapps so that gapps Will be installed on a particular ROM.

Build source code structure
Thanks for the explanation!
Would it be possible to share your build script changes that allows you to build this ROM ? I'd like to build it myself, to fix things such as enabling NFC, proximity sensor timeout (both of which I am having problems with).
Cheers,
Damien

Should I install this? this is my first time installing a ROM and im a bit worried that i might break something,

Good
Bluetooth is not working, it connects but cannot get audio out from bluetooth headset.

[CLOSED][ROM][UNOFFICIAL][9.0][Daredevil] Pixel Experience [2019/11/28]

{
"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"
}
PixelExperience for Nokia 7.2 [Daredevil]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 9.0
Whats working?
Ril
Wifi
Mobile data
Double tap to wake
Double tap to sleep
Adaptive brightness
Dark theme
Ambient display
Flash light
Sound / vibration
Camera
Volte
Fingerprint
Known issues
comment below if you face any bugs
DON'T FLASH GAPPS, ALREADY INCLUDED
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 , Perf-Stock-9.0-DDV_sprout.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
7. Now tap on reboot and tap on recovery now your phone reboots in to twrp again
8. 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
9. Now flash Perf-Stock-9.0-DDV_sprout.zip
10. Wipe all except system & vendor
11. Tap on reboot bootloader
12. Now your phone boots in to bootloader mode
13. 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 )
14. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* Pixel Experience & 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 Stock Pie kernel
Download vbmeta
Download Official Twrp
Android OS version: 9.0.0_r47
Security patch level: November 2019
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/PixelExperience

reserved

I was going to give this a go and see how folks liked it. Any feedback yet?

jumpup said:
I was going to give this a go and see how folks liked it. Any feedback yet?
Click to expand...
Click to collapse
I used it for about an hour and it felt snappier than stock

I'm now having the infamous issue where the Wifi toggle switch. When Wifi is enabled, it immediately disables.. I believe this is because I need to perform another session following instructions to the absolute letter.
Fortunately, I always make a TWRP image along with Titanium Backup sets, copied externally, before testing.
Is there any reliable means to resolve this pervasive wifi bug?

jumpup said:
I'm now having the infamous issue where the Wifi toggle switch. When Wifi is enabled, it immediately disables.. I believe this is because I need to perform another session following instructions to the absolute letter.
Fortunately, I always make a TWRP image along with Titanium Backup sets, copied externally, before testing.
Is there any reliable means to resolve this pervasive wifi bug?
Click to expand...
Click to collapse
I'm having this same wifi issue with stock image. It has appeared since September update. Also faced same kind of problem with bluetooth but it disappeared after December update.

Richard Lamm said:
I'm having this same wifi issue with stock image. It has appeared since September update. Also faced same kind of problem with bluetooth but it disappeared after December update.
Click to expand...
Click to collapse
I've found a method to permanently resolve it, so long as the modified monthly image matches that of the ROM. Let me know if you'd like a write-up.

jumpup said:
I've found a method to permanently resolve it, so long as the modified monthly image matches that of the ROM. Let me know if you'd like a write-up.
Click to expand...
Click to collapse
The issue dissappeared for now after Google's security patch for January 2020 (build 00WW_1_400). Hope so that it won't come back:fingers-crossed:

doubts of installing
I am planning to install this Pixel Experience ROM to my Nokia 7.2, i just want to know the latest info about the ROM like today, cuz i'm having doubts to install it, maybe cuz it will not run or work properly (newbie to this kind of thing)

[ROM][11][RMX215X][RMX216X]CrDroidv7.3[UNOFFICIAL]

Nice

What can we use recovery for realme 7?

Google pay not working

vimal102029 said:
Google pay not working
Click to expand...
Click to collapse
Safetynet passes out of box, if u rooted then dont forget to use magisk hide

any roms for narzo 20 pro?..
rmx 2161?

y16032001s said:
any roms for narzo 20 pro?..
rmx 2161?
Click to expand...
Click to collapse
yes... all roms work for Narzo 20 Pro too

ashuk1109 said:
Safetynet passes out of box, if u rooted then dont forget to use magisk hide
Click to expand...
Click to collapse
Which nikgapps package should I use core/basic/omni/stock/full

Can i install this rom using realme recovery

Dynamic user said:
Can i install this rom using realme recovery
Click to expand...
Click to collapse
Nope

does this fix the unresponsive touch issue and tons of other ****ty issues of realme, i am really disappointed with this phone, the company sucks hard

It is all good, but there is still no way to unlock the bootloader of RMX2155 (realme 7). No in depth testing app or other way.
Anyone has managed to unlock one of these? How?

Adpnt said:
It is all good, but there is still no way to unlock the bootloader of RMX2155 (realme 7). No in depth testing app or other way.
Anyone has managed to unlock one of these? How?
Click to expand...
Click to collapse
I unlocked my bootloader successfully
Here is how
Go to developer option and enable oem unlocking then complete the in-depth testing form(apk attached), it will approve in 5 minutes (mine is approved in just 2 min) then click on start in-depth testing, it will reboot to bootloader then connect phone to pc and type this command "fastboot flashing unlock"
Press volume up to unlock the bootloader & then "fastboot reboot"
Done bootloader unlocked.

vimal102029 said:
I unlocked my bootloader successfully
Here is how
Go to developer option and enable oem unlocking then complete the in-depth testing form(apk attached), it will approve in 5 minutes (mine is approved in just 2 min) then click on start in-depth testing, it will reboot to bootloader then connect phone to pc and type this command "fastboot flashing unlock"
Press volume up to unlock the bootloader & then "fastboot reboot"
Done bootloader unlocked.
Click to expand...
Click to collapse
Thank you for sharing!
Unfortunately it does not work on my phone. It said the phone is not supported.
Is yours RMX2155?

First of all thanks to developer. This rom is so smoothAF and solve UI & other bugs that I was facing in Realme f**king UI everything is working smooth except video recording but it doesn't affect me because I rarely record video from my phone, all I love is smooth UI & UX thanks again.

vimal102029 said:
First of all thanks to developer. This rom is so smoothAF and solve UI & other bugs that I was facing in Realme f**king UI everything is working smooth except video recording but it doesn't affect me because I rarely record video from my phone, all I love is smooth UI & UX thanks again.
Click to expand...
Click to collapse
Thank you for giving a brief review of this rom. Can you please tell me which custom recovery you installed and where it is available?

Anirudh_9393 said:
Thank you for giving a brief review of this rom. Can you please tell me which custom recovery you installed and where it is available?
Click to expand...
Click to collapse
I installed pitch black recovery
{Mod edit}

vimal102029 said:
I installed pitch black recovery
{Mod edit}
Click to expand...
Click to collapse
Thank you

I'm on crDroid, and really like it. The smoothest one I've ever used until now. Just wondering will you guys develop it to be the official one since the realme 7 community is quite big and many of us are looking forward to having crdDroid as official ROM.
BTW, thank you guys for good an amazing work!

ashuk1109 said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
First time installation:
1. Disable AVB with fastboot (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
2. Flash PBRP with fastboot (fastboot flash recovery recovery.img)
3. Reboot to Recovery
4. Wipe Data/Cache
5. Flash the ROM (Could need to unmount system before if it's mounted), then flash GAPPS
6. Format data
7. Reboot to System
Update installation:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash the ROM and GAPPS
4. Reboot to System
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Prebuilt Kernel from A.83
Device: https://github.com/ashuk1109/device_realme_RMX2151
Download:
ROM: From Here
Changelog :
* Initial Android 11 based release
Known issues:
* U tell me
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
Really like the ROM, fast, smooth and full of customization. Hence, I really expecting it becoming Official, so if anything we can help to make the process happens, please inform.
Good work, team!

[SODP][ROM][AOSP] SonyAOSP 13 [Alpha]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Source Code
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony XZ2C (apollo)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
GCAM Camera App:
GCAM Issue
Suggested GCams
Installation with a recovery:
fastboot flash oem _a oem_*.img (Only needed until the device receives mainline support by SODP)
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps (Requires TWRP or a custom ROM recovery)
Dual Sim Patcher (Requires TWRP or a custom ROM recovery)
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot -w (Wipes your internal storage and the userdata; only if needed)
Now you got the AOSP recovery, to please continue with the normal installation
fastboot flash oem_a oem_*.img (Only needed until the device receives mainline support by SODP)
fastboot flash vendor vendor.img
fastboot flash system system.img

News
07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse
08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse
06.09.2022
android-13.0.0_r1 (August security patchlevel)
Click to expand...
Click to collapse

Is there a stock camera app? Is it possible to record 60 fps videos?

Hi,
I installed AOSP 13 successfully, but after starting display don´t respond to touch, any solution?

07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse

Good news! I was not able to boot a single of the 12 versions, but Android started with your last build!
On my model the vbmeta line was needed:
```
fastboot --disable-verity --disable-verification flash vbmeta vbmeta
```
Touch screen is working, I'll check the rest later.

That sounds great, just tried it myself but on my device still touch is not working!
Which model do you have exactly? Which build did you install and which binaries?

bluep said:
That sounds great, just tried it myself but on my device still touch is not working!
Which model do you have exactly? Which build did you install and which binaries?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_12_4.19_v3a_tama.img
aosp-13-20221007_apollo.zip
I don't have the details here but my phone is a dual sims one from Europe.

Ok, same model here and I also used the same binaries and ROM. Unfortunately it doesn't have a working touch for me... :-(

Is it worth to switch from LOS 20 SonyAOSP 13? I have issues with my RAM, it looks like I'm constantly running out of RAM even if there aren't any Apps running in Background (Developer Tools -> Active Processes) :/
EDIT: Or shall I revert to Android 12 or older in generall because maybe Android uses too much RAM?

DrTrax said:
Is it worth to switch from LOS 20 SonyAOSP 13? I have issues with my RAM, it looks like I'm constantly running out of RAM even if there aren't any Apps running in Background (Developer Tools -> Active Processes) :/
EDIT: Or shall I revert to Android 12 or older in generall because maybe Android uses too much RAM?
Click to expand...
Click to collapse
Oh, I thought it was just me.
Since LOS 19 I also have the problem that the RAM gets full and the device slows down.
LOS20 after a full wipe has the same problem.
And I use the 6GB Ram edition.
{
"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"
}
About SODP we need to wait for the OEM A13 binary or mainline to boot the device.
I don't know the release date.
Maybe the next time they release new binaries.

MartinX3 said:
Oh, I thought it was just me.
Since LOS 19 I also have the problem that the RAM gets full and the device slows down.
LOS20 after a full wipe has the same problem.
And I use the 6GB Ram edition.View attachment 5850687View attachment 5850691
About SODP we need to wait for the OEM A13 binary or mainline to boot the device.
I don't know the release date.
Maybe the next time they release new binaries.
Click to expand...
Click to collapse
German BOI, läuft alter
YOU ALSO HAD ISSUES WITH RAM ON LOS 19?!?!
Holy moly and I was deleting, wiping, changing this and that and still f-ed up everything!
What does it mean, we need to wait for OEM A13 binary? Does it mean that Sony is kinda still compiling code for the XZ2 devices but not the full ROM?

DrTrax said:
German BOI, läuft alter
YOU ALSO HAD ISSUES WITH RAM ON LOS 19?!?!
Holy moly and I was deleting, wiping, changing this and that and still f-ed up everything!
What does it mean, we need to wait for OEM A13 binary? Does it mean that Sony is kinda still compiling code for the XZ2 devices but not the full ROM?
Click to expand...
Click to collapse
That are the closed source hardware drivers until the device is fully supported by the mainline kernel.
I don't know the ETA for the next OEM binary release, but I'm preparing a new SODP 13 build.

MartinX3 said:
That are the closed source hardware drivers until the device is fully supported by the mainline kernel.
I don't know the ETA for the next OEM binary release, but I'm preparing a new SODP 13 build.
Click to expand...
Click to collapse
Sounds really great! I hope the memory issue get finally fixxed, I mean...
The Benchmarks with Antutu are still pretty good but cmon Sony... it's so sad that this device with 4GB memory suffers a lot and to be honest, it's size is perfectly for me!

Since SODP and LOS are different, they mostly don't share issues.
So you might get different issues on SODP.

MartinX3 said:
Since SODP and LOS are different, they mostly don't share issues.
So you might get different issues on SODP.
Click to expand...
Click to collapse
Hmmmm.... shall I dirty flash from LOS to SODP? I mean, you still call that ROM alpha which implies that it isn't perfect as a daily driver ^^

DrTrax said:
Hmmmm.... shall I dirty flash from LOS to SODP? I mean, you still call that ROM alpha which implies that it isn't perfect as a daily driver ^^
Click to expand...
Click to collapse
You need a fullwipe and beta isn't perfect as a daily driver.
You're lucky if alpha boots on your device all the time.

Hello thanks for the images !
I installed the rom but it doesn't have a working touch. Otherwise I see the lock screen and can use the volume butons. What should I do?

MartinX3 said:
That are the closed source hardware drivers until the device is fully supported by the mainline kernel.
I don't know the ETA for the next OEM binary release, but I'm preparing a new SODP 13 build.
Click to expand...
Click to collapse
Any news when you compile new SODP 13 build? Should touch work with the current build? Any major bugs know?
Thanks in advance!

Develop Bugs

welcome