[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 11 [BETA] - Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 11 [BETA] - Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other

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
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 Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
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:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 11
Beta Release Date: 2020-10-23
Created 2020-10-23
Last Updated 2020-10-23

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, if you getting problems like a not bootable or crashing device.
GCAM Camera App:
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 --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w (Wipes your internal storage and the userdata)
Now you got the AOSP recovery, to please continue with the normal installation

News
09.02.2022
android 12
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [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...
forum.xda-developers.com
Click to expand...
Click to collapse
20.09.2021
android-11.0.0_r43 (September security patchlevel)
OEMv7 support
Click to expand...
Click to collapse
19.09.2021
Revoked the r43 buiild because of error
AndroidRuntime: java.lang.IllegalArgumentException: invokeOemRilRequestRaw failed with rc = -2
We need to wait until the following PRs get merged
[TRANSPOWER] [3/4] Convert all makefiles to BluePrint by MarijnS95 · Pull Request #14 · sonyxperiadev/transpower
Depends on #13 Blueprint is easier to read, has less possibilities for complicated configuration (for the better) and is much quicker to parse by the build system. Note that an extra android_librar...
github.com
[TRANSPOWER] [4/4] [WIP/RFC] Make SDK-28 compliant, use HookMediator for qcrild by MarijnS95 · Pull Request #11 · sonyxperiadev/transpower
Depends on #14 Hi @jzoran, This PR attempts to fix a multitude of things related to recent changes on SODP and Android API compatibility. Let me run through them sequentially: Kumano requires qcril...
github.com
Click to expand...
Click to collapse
17.09.2021
android-11.0.0_r43 (September security patchlevel)
OEMv7 support
Click to expand...
Click to collapse
17.08.2021
android-11.0.0_r40 (August security patchlevel)
OEMv6 support (Now our device uses the same camx camera framework like Xperia 1/5 (I / II / III)
Click to expand...
Click to collapse
25.07.2021
android-11.0.0_r39 (July security patchlevel)
Click to expand...
Click to collapse
10.06.2021
android-11.0.0_r38 (June security patchlevel)
OEMv5 support!
Click to expand...
Click to collapse
10.05.2021
android-11.0.0_r36 (May security patchlevel)
Click to expand...
Click to collapse
08.04.2021
android-11.0.0_r34 (April security patchlevel)
OEMv4 support!
Click to expand...
Click to collapse
12.03.2021
android-11.0.0_r32 (March security patchlevel)
Fixed mobile and wifi
Click to expand...
Click to collapse
13.02.2021
android-11.0.0_r29 (February security patchlevel)
Click to expand...
Click to collapse
12.01.2021
android-11.0.0_r27 (January security patchlevel)
Click to expand...
Click to collapse
12.12.2020
android-11.0.0_r18 (December security patchlevel)
Click to expand...
Click to collapse
14.11.2020
android-11.0.0_r17 (november security patchlevel)
Click to expand...
Click to collapse
23.10.2020
hello android-11.0.0_r4 (october security patches!) for the xz2, xz2c & xz3
Click to expand...
Click to collapse

23.10.2020
Hello android-11.0.0_r4 (October Security patches!) for the XZ2, XZ2C & XZ3
Click to expand...
Click to collapse

Wow..thanks a lot bro. I go test it tomorrow
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk

NYGGAZ said:
Wow..thanks a lot bro. I go test it tomorrow
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
Click to expand...
Click to collapse
You're welcome
And please report back if the dual sim patcher is still working

MartinX3 said:
You're welcome
And please report back if the dual sim patcher is still working
Click to expand...
Click to collapse
Of course bro.. I hope it work. Thanks a lot for your work[emoji6][emoji6]
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk

thank you i am going to try it soon

Thank you very much for the effort to keep this phone alive!

Can I flash oem directly over the LOS 17.1 or need to reflash the latest FW?
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk

NYGGAZ said:
Can I flash oem directly over the LOS 17.1 or need to reflash the latest FW?
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
Click to expand...
Click to collapse
Depends if you booted the latest FW on both slots the last time you came from stock.

Deleted

NYGGAZ said:
All is very VERY GOOD.. thanks Martin.. [emoji6][emoji6]View attachment 5123697
Envoyé de mon Xperia XZ3 (AOSP) en utilisant Tapatalk
View attachment 5123699
Click to expand...
Click to collapse
Thank you
But please hide several numbers in your screenshots.

Is it works with latest october blobs?
Coz my compiled one doesn't. Only works with latest A10 blobs.

zhka said:
Is it works with latest october blobs?
Coz my compiled one doesn't. Only works with latest A10 blobs.
Click to expand...
Click to collapse
Yes, this one only works with the newest OEM released before my builds.

which gapps to use

logan123456 said:
which gapps to use
Click to expand...
Click to collapse
Every
I prefer pico

I have been following the "no recovery" steps.
I have got the payload.bin extracted with this https://github.com/vm03/payload_dumper
Afterwards, I have got all the img flashed with fastboot.
Where should the SW_binaries_for_Xperia_Android_11_4.14_v1a_tama.img be used?

y2kbugleung said:
I have been following the "no recovery" steps.
I have got the payload.bin extracted with this https://github.com/vm03/payload_dumper
Afterwards, I have got all the img flashed with fastboot.
Where should the SW_binaries_for_Xperia_Android_11_4.14_v1a_tama.img be used?
Click to expand...
Click to collapse
Nice!
The OEM step of the normal installation above

MartinX3 said:
Nice!
The OEM step of the normal installation above
Click to expand...
Click to collapse
So I fastboot flash oem SW...tama.img after flashing all ROM images.
Afterwards, do I still need a recovery (TWRP) to flash GApps and dual-sim-patch?
How could I install a recovery? I cannot find one from TWRP official site.
Thanks.

Related

[ROM][13.0][Daredevil] LineageOS 20.0 [UNOFFICIAL]

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

[ROM][10] LineageOS 17.1 [OFFICIAL]

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Change Log
2020.7.30 The end of unofficial version
Support glove mode.
2020.7.25
Strengthen vibration.
Selinux enforced.
2020.7.19
Support Exfat.
2020.7.5
July security update.
Fix stock camera crashed sometimes.
Support 802.11ac wireless hotspot.
2020.6.15
New fingerprint drivers from SODP.
Support dual sim and SD cards at the same time.
Kernel update to 52.1.A.2.1.
June security patch.
2020.5.26
Fix mic when using loadspeaker.
Update to 52.1.A.2.1.
Creator mode ported from Xperia 1. (Livedisplay)
2020.5.25
Wireless display fixed.
Strict thermal config.
Single & dual model detect.
2020.5.24
Sony camera flashable zip.
2020.5.15
1. New notification LEDs.
2. Lineage Update
2020.5.3
1. Fix brightness control bug on 5.2.
2020.5.2
1. Fix notification LEDs.
2020.4.29
Fix USB tethering.

First!
Thank you for providing a stock variant of LineageOS!
We should distinguish them by writing SODP and STOCK in our thread titles or more people will ask questions.

MartinX3 said:
First!
Thank you for providing a stock variant of LineageOS!
We should distinguish them by writing SODP and STOCK in our thread titles or more people will ask questions.
Click to expand...
Click to collapse
Thank you for your effort on SODP as well, I agree with you

If you flashed oem and meet any issues, I could only say you are a hanhan.
You are a hanhan
Hanhan
Dose laowai know what's means of hanhan??
Anyway thank you for your new rom

tainhao said:
If you flashed oem and meet any issues, I could only say you are a hanhan.
You are a hanhan
Hanhan
Dose laowai know what's means of hanhan?
Anyway thank you for your new rom
Click to expand...
Click to collapse
We laowai should know it.
It's just a short google away. :silly:

你好，这个ROM我刷了一下，截个图然后在QQ想发给别人结果找不到，我重刷了3遍仍然无法解决，然后想问一下twrp和migisk应该如何刷入，希望您可以回复我

mingzhenliu said:
你好，这个ROM我刷了一下，截个图然后在QQ想发给别人结果找不到，我重刷了3遍仍然无法解决，然后想问一下twrp和migisk应该如何刷入，希望您可以回复我
Click to expand...
Click to collapse
Please use the english language.
Then more people can help you.
There are useful translators like https://translate.google.com/

sorry,I‘m a Chinese
the question is how to install twp and maagisk in this rom?
and in this rom,i take a screenshot,try to send it in social apps,but I can't find my screenshot
so,can you help me ?

mingzhenliu said:
sorry,I‘m a Chinese
the question is how to install twp and maagisk in this rom?
and in this rom,i take a screenshot,try to send it in social apps,but I can't find my screenshot
so,can you help me ?
Click to expand...
Click to collapse
No problem
It's just that we are an international community and don't want to exclude anyone
(I did learn English, too)
Since it's a stock based ROM and the official stock firmware is one month behind the security patch level, this April security patches lineageOS won't work with the twrp
(Google rollback protection)
But I will release a TWRP without userdata decryption, which should work anyway.
But rooting is still possible.
Just unzip the lineageOS.zip
Use the payload_dumper I linked in the SODP lineageOS thread to extract the boot.img file
Then patch the boot.img file in the magical manager app
And flash it back via fastboot

MartinX3 said:
No problem
It's just that we are an international community and don't want to exclude anyone
(I did learn English, too)
Since it's a stock based ROM and the official stock firmware is one month behind the security patch level, this April security patches lineageOS won't work with the twrp
(Google rollback protection)
But I will release a TWRP without userdata decryption, which should work anyway.
But rooting is still possible.
Just unzip the lineageOS.zip
Use the payload_dumper I linked in the SODP lineageOS thread to extract the boot.img file
Then patch the boot.img file in the magical manager app
And flash it back via fastboot
Click to expand...
Click to collapse
thanks alot

Disadvantages:
camera key:not working
lift to wake(抬起唤醒）：not working
application install:soooooo slow....
and always system crash(死机，卡死)
camera can use hmd camera,but when you try to manuall take photo(手动拍照),no apps can do
advantage:
it's a stable android 10!!!
Hope to fix that

My phone has one sim card but this rom shows two slots. Problems - doesn't detect my sim card. How fix?

tainhao said:
If you flashed oem and meet any issues, I could only say you are a hanhan.
You are a hanhan
Hanhan
Dose laowai know what's means of hanhan?
Anyway thank you for your new rom
Click to expand...
Click to collapse
Hanhan is "憨憨" in Chinese. The two words own tons of imformation. It is difficult to explain it in English.
mingzhenliu said:
你好，这个ROM我刷了一下，截个图然后在QQ想发给别人结果找不到，我重刷了3遍仍然无法解决，然后想问一下twrp和migisk应该如何刷入，希望您可以回复我
Click to expand...
Click to collapse
截图分享问题是Lineage或者QQ的问题，magisk用官方10的方法刷入，twrp没有，但是自带的Lineage recovery可以刷入Gapps，够用了。
If you met any problem about share screenshot, this is a bug of Lineage or tencent QQ. For Magisk, you could patch the boot image as stock 10.0. For recovery, we don't have twrp now, But you could use lineage recovery for Gapps.
mingzhenliu said:
Disadvantages:
camera key:not working
lift to wake(抬起唤醒）：not working
application install:soooooo slow....
and always system crash(死机，卡死)
camera can use hmd camera,but when you try to manuall take photo(手动拍照),no apps can do
advantage:
it's a stable android 10!!!
Hope to fix that
Click to expand...
Click to collapse
细枝末节的小问题我们正在处理，卡死的问题不存在，请检查你的官方固件版本、区域。任何第三方app的问题去反馈给相应的开发者，如果你使用Magisk遇到任何问题，请不要进行反馈，我只对固件负责，不对任何对系统的修改负责。
For some small issues, we are checking it now. System is stable, if you met any crash, try to check your stock FW's version and area. If you met any problem about 3rd apps or Magisk and its modules, pleasedon't feedback, we are only respon for LineageOS, not your hacks.
joro1973 said:
My phone has one sim card but this rom shows two slots. Problems - doesn't detect my sim card. How fix?
Click to expand...
Click to collapse
Our judgement for single model is not completed, you could try to flash stock firmware of dual model, after that you could flash LineageOS. Then sim card work work.
If you need VoLTE, you need to flash the oem.sin for your country/area after flash the dual FW.

The microphone cannot be used in speaker mode:crying:

mingzhenliu said:
The microphone cannot be used in speaker mode:crying:
Click to expand...
Click to collapse
Comfim it. Thanks.

音量大小不太正常，小于50%声音特别小，大于50%声音超级大…
Sound size is abnormal,less than 50% of the sound is particularly small, more than 50% of the sound is super loud ...

我用的H8296，在中国插移动卡，信号比官方版差太多…
My device is H8296，china mobile,signal is too poor

mingzhenliu said:
音量大小不太正常，小于50%声音特别小，大于50%声音超级大…
Sound size is abnormal,less than 50% of the sound is particularly small, more than 50% of the sound is super loud ...
Click to expand...
Click to collapse
音量的线性曲线是有点问题，我检查一下吧。
Ok, It seems that this problem exists, I will check the reason later.
mingzhenliu said:
我用的H8296，在中国插移动卡，信号比官方版差太多…
My device is H8296，china mobile,signal is too poor
Click to expand...
Click to collapse
我这里提个方法，麻烦你回去测试一下。你严格固定手机在同一个位置，在官方和LineageOS下面分别间隔3分钟测试三次信号强度值（一共6个）。信号强度，在设置-关于手机-SIM卡状态-信号强度。如实反馈给我。
Here is a method to dump the status of signal strength, Please make sure the phone keeps the same position when you test. Feedback the value of Setting-About phone-SIM status-Singal strength. Please test it on stock and LineageOS, dump value each 3 min. 6 values totally.

[RECOVERY][UNOFFICIAL][Q-R][picasso] PitchBlack Recovery Project 3.0.0 [STABLE][2020-12-17]

{
"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:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on: TWRP v3.4.0
PitchBlack version: 3.0.0
Device: picasso (all models should work)
Picasso TG general group: https://t.me/XiaomiRedmiK30
Maintainer/Authors build: masemoel and Hadenix
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version/another recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From fastboot
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
From TWRP app
(Ideal if you don't own a PC).
Download Official TWRP app from Play Store.
Extract the PBRP zip.
Flash the recovery.img with the TWRP app.
Reboot to recovery.
Flash the whole PBRP zip (otherwise you won't have PBRP tools working properly).
Enjoy
Changelog
PBRP changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Picasso changelog
Code:
PBRP 3.0.0 2020-12-17 - Android Q and R
- Added nano editor.
- Fixed decryption issues with Android 11 (now it should decrypt even when the password is not a pattern). This makes now A11 PBRP be marked as stable!
- All PBRP changes in the latest month.
PBRP 3.0.0 2020-11-10 - Android Q and R
- Fixed errors when wiping some partitions.
- Touch delay on the first 5 seconds has gone.
- Minor touches on fstabs.
- All PBRP work in the latest week.
PBRP 3.0.0 2020-11-03 - Android Q and R
- Updated vendor, kernel and dtbo to xiaomi.eu 12.0.7.0 ones.
- Fixed wiping errors in [U]Wipe[/U] section.
- Fixed some flags in dynamic partitions.
- (Hopefully) Fixed asking decryption key when it's not needed.
- Fixed flashing failure with multiple Migrate zips.
- Fixed duplicated super partition in backup section.
- Translations updated (PBRP team) and other minor stuff by the team as well :).
PBRP 3.0.0 2020-10-03 - Android R
- Initial XDA release, based on Q tree.
PBRP 3.0.0 2020-10-03 - Android Q
- Update kernel stuff to stable MiUI 12.0.6.
- Remove DTBO partition from Wipe section (it can't be wiped).
- Some PBRP UI fixes by the team.
PBRP 3.0.0 2020-10-01 - Android Q
- Now we don't need to unmount anything before flashing.
- Translation characters are now showed correctly (fixes issue with Asian fonts not showing).
- Some UI fixes and other improvement by the PBRP team.
PBRP 3.0.0 2020-09-19 - Android Q
- Initial XDA release
Bugs
- You tell me!
- Check current issues at the GitHub Issues tracker before reporting one (it may already exist): https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/issues
Downloads
Flashable Android 10/Q zip [MEGA folder]
https://mega.nz/folder/10I1RKgC#onjHUvM4-trZ9qcfkWkLtw
Flashable Android 11/R zip [MEGA folder]
https://mega.nz/folder/EoIHDYIL#kFemXVyMKd53kKCdZm3SUg
Note that this is still experimental as Android 11 source for PBRP hasn't been still released!
Version information
Status: Stable
Created: 2020-09-19
Last updated: 2020-11-03
Beers & coffees (obviously hitting the thanks button is always enough, but this will motivate me 1000%): https://www.paypal.com/paypalme/masemoel

Little reminder here: I abandoned this project in favour of OrangeFox Recovery Project, so don't expect any updates from my side here anymore. If anyone is willing to continue this project, my trees are available as always on my GitHub (see the OP).
OrangeFox Recovery Project for picasso

Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?

Dan Ratia said:
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Click to expand...
Click to collapse
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs

masemoel said:
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.

Dan Ratia said:
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Click to expand...
Click to collapse
Weird... Ensure that you have Redmi K30 5G version, and not normal K30 (aka phoenix).
Sent from my Redmi K30 5G using XDA Labs

Yes, i am sure it is Redmi K30 5G

Dan Ratia said:
Yes, i am sure it is Redmi K30 5G
Click to expand...
Click to collapse
Then it's very weird... No one has reported that the recovery is not booting on their picasso.
Did you flashed that modified vbmeta image by PeterCxy for his LineageOS recovery? (If you flashed it, then flash the original one)
Either that or your outdated vendor base would be the reason why it's not booting for you.
Sent from my Redmi K30 5G using XDA Labs

I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.

Dan Ratia said:
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Click to expand...
Click to collapse
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs

Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.

ThomasRhin said:
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
Click to expand...
Click to collapse
Hello and thanks, Thomas.
The unofficial TWRP is being maintained by Hadenix in GitHub's picasso group right now.
Me I will stay in PBRP as I feel comfortable, safe, and has a lot of features with a nice UI ?
I once built TWRP to ensure that the device tree I did was working as it should, and also to see if an issue in PBRP was happening in TWRP as well.
https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/releases/tag/TWRP
But I won't build it anymore for now, PBRP works flawlessly + there is already another dev compiling and improving it.
Sent from my Redmi K30 5G using XDA Labs

so its only for k30 5g or it will aslo work on k30i 5g?

@tensionless said:
so its only for k30 5g or it will aslo work on k30i 5g?
Click to expand...
Click to collapse
It should work... I haven't tested though as I don't have that picasso variant
Sent from my Redmi K30 5G using XDA Labs

masemoel said:
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?

Dan Ratia said:
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Click to expand...
Click to collapse
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access

masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
Well i wil try again, i flashed ROM, Gapps, start ROM, Format data and Magisk.

masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...

Dan Ratia said:
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Click to expand...
Click to collapse
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Sent from my Redmi K30 5G using XDA Labs

masemoel said:
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Click to expand...
Click to collapse
Ok I got it... You are flashing the forcing encryption disabler... Then you have to flash Magisk 20.3 only, and later you can upgrade if you want...
Flash it after crDroid as well
EDIT: You can look at my AICP build either in the Telegram group mentioned in the OP, or by looking at Redmi-30-5G GitHub.
Sent from my Redmi K30 5G using XDA Labs

[Recovery][Unofficial] OrangeFox Recovery Project [R11.1_3][Android 11/12]

OrangeFox Recovery Project
{
"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.
*
* We're 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 recovery
* 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.
*
*/
OrangeFox is FREE SOFTWARE
Credits:
* TeamWin - for TWRP
* The OrangeFox Team - for their hard work
* @DarthJabba9 for his help throughout the process and for bearing my spam.
* @ me xD
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Support for managing Magisk modules
* Aroma FM
* Password
* Support Custom ROMs
* Superb new UI and themes
* OrangeFox theme engine:
* Choice of theme (black, dark, etc)
* Choice of color scheme
* Choice of splash screen
* Alternative lockscreen
* And many more!
DOWNLOADS
R11.1/R11.1_1:
Official website download link: Here
R11.1_2:
GitHub : Here
R11.1_3:
GitHub : Here
INSTALLATION
1. Download the OrangeFox zip to your device
2. Reboot to your existing OrangeFox/TWRP (or other custom TWRP-based) Recovery
3. Install the OrangeFox zip as a normal zip installer
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
For bugs and changelog see the 2nd post.
FAQ and Guides:
Guides and Frequently Asked Questions
wiki.orangefox.tech
Device Tree:
GitHub - Yilliee/recovery_a51: Recovery device tree for Galaxy A51 4g (SM-A515X)
Recovery device tree for Galaxy A51 4g (SM-A515X). Contribute to Yilliee/recovery_a51 development by creating an account on GitHub.
github.com
Kernel Source:
GitHub - Yilliee/android_kernel_samsung_exynos9611
Contribute to Yilliee/android_kernel_samsung_exynos9611 development by creating an account on GitHub.
github.com
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Samsung Galaxy A51 4G
Contributors (OrangeFox Team)
MrYacha, DarthJabba9
Source Code:
OrangeFox Recovery · GitLab
OrangeFox Recovery | OFR
gitlab.com
Version Information for a51
Status: Stable
Current Latest Version: R11.1_3
Beta Release Date: 2022-26-05
Post details
Created: 2021-02-22
Last Updated: 2021-31-05

Changelogs
R11.0:
- Initial Build for a51.
R11.1:
- Update to R11.1
- Removed system image mount from fstab. (Use Dynapatch)
- Fixed Standalone ADB and ADB sideload.
- Fixed AromaFM.
- Fixed Themes getting reset after rebooting recovery.
- Fixed Vibration.
- Fixed the codename / dtbo errors woth respect to BlueFly.
- Added Vbmeta, Vbmeta_samsung and Dtbo to backup menu and allow flashing images to them.
R11.1_2:
- Fix status bar height ( It is now right till the bottom of punch-hole )
- Add up_param entry in fstab ( You can flash the .bin/.tar files by renaming them to .img and just using the flash image option ).
- Integrate multidisabler by @ianmacd into the build and allow specifying specific things to disable.
- Fix AVB. ( Recovery does not need a patched vbmeta to boot anymore ).
- Switch to Celica Kernel and dtb+dtbo built from source.
- Fix issues with adb, sideload and mtp.
- Fix fastbootd ( Reboot >> fastboot in recovery ).
- Exclude twrp_Apex.cpp. ( Fixes the blinking issue with Android-12 ).
- Skip the Samsung selinux enforce patches as well as creating a .tar file placed within the zip.
- Implement FOX_CUSTOM_BINS_TO_SDCARD. ( Adds nano editor, sed binary, tar binary, unzip binary and xz utils ).
- Don't keep persistent log history.
- Include @phhusson's lptools binary.
- Include HexDump Utility.
R11.1_3:
- Fix the syntax issues with multidisabler script.
- Bump version number to _3 and change status from beta to stable.
- Include app manager and amend it to work with Android 11/12.
- Don't show the warnings
unable to update logical partition
on the console.
- Update kernel to Celicia-v2.0 (Based on A515FXXU5FVC2).
Bugs
R11.0:
- Just ignore the following error/red lines in console for the meanwhile:
E:unable to update logical partition: /system_image
- See the post below for AromaFM fix.
- Haptic feedback aka Vibration doesn't work.
R11.1:
- Decryption
- Fastbootd doesn't work so the configs have been removed for the meanwhile.
R11.1_2+:
- None

Extra Fixes
Only for R11.0:
For fixing AromaFM, download the aromafm.zip from here and replace in Internal Storage /Fox/FoxFiles/AromaFM/ with the one attached here

Great work!!

The error that mentions that it appears seems to me that it is a thing of the fstab (E:unable to update logical partition: /system_image) it may also be that the gsi that were tested were in RO Just what I think, I'm new enough to Samsung to really know

or try to use, but my device goes to Download mode and says vbmeta is missing, any solution?

LichtEstarossx said:
or try to use, but my device goes to Download mode and says vbmeta is missing, any solution?
Click to expand...
Click to collapse
Your android version must be compatible with the recovery.

GrandmaGotGuns said:
Your android version must be compatible with the recovery.
Click to expand...
Click to collapse
according to the tree it is for android

LichtEstarossx said:
according to the tree it is for android
Click to expand...
Click to collapse
Sure but this recovery is specifically for Android R aka android 11 if you device was at android 10 by default i.e. it was shipped with Android 10 and has not been updated to android 11, then it might be the cause. Just update to latest android version and all these issue will go away
U can download one ui 3 from here.
Select the region and it'll show all the one ui roms available, if one ui 3 is not available in your region then change the region, like to Russia.
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com

LichtEstarossx said:
or try to use, but my device goes to Download mode and says vbmeta is missing, any solution?
Click to expand...
Click to collapse
Make sure you are on ONEUI 3 /Android 11 /Android R. And flash a null vbmeta to get it to boot.

LichtEstarossx said:
The error that mentions that it appears seems to me that it is a thing of the fstab (E:unable to update logical partition: /system_image) it may also be that the gsi that were tested were in RO Just what I think, I'm new enough to Samsung to really know
Click to expand...
Click to collapse
That error message shows because system is a logical partition and logical partitions are supposed to be read only but in order to add support for direct gsi flashing, system image has been mounted as rw which causes the error to be displayed.
I had to choose between removing the error or the direct GSI support, and I ended up choosing the latter.

Yillié said:
Make sure you are on ONEUI 3 /Android 11 /Android R. And flash a null vbmeta to get it to boot.
Click to expand...
Click to collapse
what? the tree said it is for Android 10 ._.

LichtEstarossx said:
what? the tree said it is for Android 10 ._.
Click to expand...
Click to collapse
Does the tree says anywhere that the builds will only be for Android 10???
It only mentions that the build system was based on Android 10 not for only Android 10.

Great job thank you

eu
Yillié said:
Essa mensagem de erro é exibida porque o sistema é uma partição lógica e as partições lógicas devem ser somente leitura, mas para adicionar suporte para flashing gsi direto, a imagem do sistema foi montada como rw, o que faz com que o erro seja exibido.
Tive que escolher entre remover o erro ou o suporte direto ao GSI, e acabei escolhendo o último.
Click to expand...
Click to collapse
Is possible flash direct GSI?
Chondoe no necessary in OrangeFox?

hacker812c said:
eu
Is possible flash direct GSI?
Chondoe no necessary in OrangeFox?
Click to expand...
Click to collapse
For the R11.0 build it can be flashed directlyno need for any Addons or anything of that sort. Tho if you wanna flash Gapps right after the gsi without booting even once , try checking out the system_resizer.zip on my sourceforge account.

Yillié said:
For the R11.0 build it can be flashed directlyno need for any Addons or anything of that sort. Tho if you wanna flash Gapps right after the gsi without booting even once , try checking out the system_resizer.zip on my sourceforge account.
Click to expand...
Click to collapse
Thank you
System resizer script separate system and vendor?
Great work

I don t have access to write text in telegram group
Sorry not respost you @Yillié
Send link of script system please

hacker812c said:
I don t have access to write text in telegram group
Sorry not respost you @Yillié
Send link of script system please
Click to expand...
Click to collapse
Ah wait lemme unmute you there and here's the link of the zip;
https://sourceforge.net/projects/yilliee-projects/files/Partition%20Resizer/System-Resizer.zip/download

Yillié said:
Ah wait lemme unmute you there and here's the link of the zip;
https://sourceforge.net/projects/yilliee-projects/files/Partition%20Resizer/System-Resizer.zip/download
Click to expand...
Click to collapse
Explain more system resizer
Thank you

[ROM] AOSP 12.1 - SODP [12.1.0_r11]

Android 12 for Xperia XZ Premium
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.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications. .
What's working :
Boots
Bluetooth
Fingerprint
Wi-Fi
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Encryption
Offline Charging
Whats not working?
Bluetooth
Fingerprint
Sim Detection is Buggy
Permissive
Offline Charging
Notification LED
Half Screen issue(For some users) - Need testing if still persist
Instructions to install up ROM :
Flash latest available Stock ROM(47.2.A.10.107) and boot into it once.
Reboot to Fastboot
Download the latest OEM Image from HERE, Extract and Flash it. (V5B)
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v5b_yoshino.img
Flash the userdata,boot and system image (Will wipe all the userdata).
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
Install Magisk/Gapps(Optional).
Reboot
Downloads :
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.1.0_r11/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.1.0_r11/g8141/
Source Code: https://github.com/sonyxperiadev

Change log :
26th Oct'21 :
* Initial Release
Please refer to First post for what is working and what is not.
Download :
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r2/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r2/g8141/
26th Nov'21 :
Updated to android 12 release 12.0.0_r13
November Security Patch
Kernel up streamed to 4.14.245
Fixed Buggy sim detection
Fixed Offline Charging
Dropped SODP color manager(Need testing if Half screen issue still persists)
Enabled powered menu on holding the power button.
Download :
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8141/
27th Nov'21:
Minor kernel update to fix Bluetooth
Updating the boot.img in same 12.0.0_r13 folder.
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8141/
20th July'22 :
1. Upstreamed to android 12.1.0_R11
2. Bugs remain same as 1st post for now.
3. Make sure you are using the binaries mentioned in first post, else you will get sensors and sim detection issues.
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.1.0_r11/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.1.0_r11/g8141/

legend !!! tq shujat!! in my G8141 working no half screen, power button in UI cant work.. so for shutdown or restart via QS (Quick Setting)

God

Thank you

nice

platypuzz said:
legend !!! tq shujat!! in my G8141 working no half screen, power button in UI cant work.. so for shutdown or restart via QS (Quick Setting)
Click to expand...
Click to collapse
Thats the android 12 Feature.
There are ways to enable power menu via the power button,
Will look into it for next update.

Thanks

Shujath said:
Thats the android 12 Feature.
There are ways to enable power menu via the power button,
Will look into it for next update.
Click to expand...
Click to collapse
Hi Shujath! i just installled your A12 rom, it's awesome for to be a first release but i found 2 bugs: there is not fingerprint and twrp stuck to the first image and don't go on!

i think it need a new twrp for A12 rom!

do you release for xz1 . Thank you

Thank you!

arpias said:
Hi Shujath! i just installled your A12 rom, it's awesome for to be a first release but i found 2 bugs: there is not fingerprint and twrp stuck to the first image and don't go on!
Click to expand...
Click to collapse
try aroma twrp...

May I ask what do you modify in AOSP12 to make it bootable with latest oem? I'm trying to boot XZ2.
OVERRIDE_PRODUCT_COMPRESSED_APEX := false

Hi first thank you .blease can you tell me what the way to flash this rom.. Twrp or flash tool sony or adb from pc blouse step by step blease reply me

please build sailfish os for xz premium

Android 18 eta?

ROM Updated :
Nov-26'21
Changelog :
Updated to android 12 release 12.0.0_r13
November Security Patch
Kernel upstreamed to 4.14.245
Fixed Buggy sim detection
Fixed Offline Charging
Dropped SODP color manager(Need testing if Half screen issue still persists)
Enabled powered menu on holding the power button.
Download :
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8141/

Shujath said:
ROM atualizada:
26 de novembro de 21
Changelog:
Atualizado para o Android 12 versão 12.0.0_r13
Patch de segurança de novembro
Kernel enviado para 4.14.245
Detecção de Sim Buggy corrigida
Carregamento offline corrigido
Gerenciador de cores SODP removido (precisa ser testado se o problema de meia tela ainda persistir)
Menu ativado ativado ao segurar o botão liga / desliga.
Download :
G8142: https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8142/
G8141: https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8141/
Click to expand...
Click to collapse
o Bluetooth está corrigido? obrigado pelo seu trabalho

Update :
Bluetooth is now fixed.
Please re download and flash the boot.img
G8142 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8142/
G8141 : https://sourceforge.net/projects/xzp/files/SODP12/12.0.0_r13/g8141/

Develop Bugs

welcome