Develop Bugs

[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X

/*
* Your warranty is... still valid?
*
* 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.
*
*/
Click to expand...
Click to collapse
Project Treble
Important!
Recommended for installation only for advanced users​***What is Project Treble? ***
Project Treble allows to install - Generic System Images on our device with a minimum number of bugs.
Vendor - this is partition where proprietary files and drivers are stored, which are separate from the system.
***Userful Information***
Project Treble XDA Thread
Generic System Image (GSI) list
***Development and bugs***
Development has been started about 3 months. backwards During this time, dozens of errors were corrected and millions of nerve cells were lost.
Vendor is based on the stock firmware UOS273C with a large number of edits.
The kernel is used from vm03 with driver edits for working on Project Treble.
Bugs in Generic System Images:
On Oreo and Pie GSIs don't working SafetyNET.
My Magisk Module: Wileyfox Swift 2 SafetyNet Pass
Bugs in Vendor:
SELinux Permissive
For the fingerprint scanner to work correctly before being added to Settings, it is necessary to “poke” 5-6 times into it, for the driver to load correctly.
***Preparing device for support Project Treble***
Download TWRP Treble
Repartition script 16GB or 32GB
Download Treble Vendor
Download Treble Boot
Mirror on Google Drive
Mirror on Cloud Mail.ru
If you want get back default partition table just flash:
Download Revert - 16GB
Download Revert - 32GB
You need to copy all the necessary information to an external memory card or PC, since the internal memory will be formatted and devided into special partitions for Project Treble can work.
​
Install TWRP Treble in a convenient way for you.
Install Repartition script in TWRP. Depending on your internal memory size.
After installing repartition script, device will automatically reboot into Recovery, where you must do:
Format Data (Wipe > Format Data)
Wipe Vendor (Wipe > Advanced Wipe > Vendor)
After that necessarily to reboot the Recovery (Reboot > Recovery)
Flashing Treble Vendor (Just install zip archive)
Flashing Treble Boot (Select the option in the lower right corner Install Image, select Boot_Treble_new.img and flash it as Boot Image)
Install your favorite firmware (about this below). (Select the option in the lower right cornerInstall Image, than flash it as System Image)
***Installing Android Oreo or Android Pie GSIs***
Flash any GSi from Generic System Image (GSI) list or XDA Thread
always choose arm64 A-ONLY!
* If camera don't working on Pie flash:
Camera Pie GSI patch
* If the NFC item in the settings hangs, or the NFC does not turn on (this is usually the case in the old October GSI), flash:
NFC all GSI Patch
* Patch for fix fingerprint scanner on some Pie GSIs
Folder with patches
For ArrowOS GSI, HavocOS 2.0, AEX 6.1 fix not needed.
***Google Apps***
Install GApps only before the first launch of the ROM!
Open GApps Project
***Thanks***
Testing and moral support:
Kirill_MegaFon (4PDA)
xyzmean (4PDA)
Zent16 (4PDA)
backspace696 (4PDA)
Help in bug fixes and kernel sources:
vm03 (XDA)
Mirrors for download files:
anatoliy-is (4PDA)
Fingerprint overlay:
creativchic (4PDA)
XDA:DevDB Information
[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X, ROM for the Wileyfox Swift 2
Kernel Sourses
DevelopedInside
Contributors
fx-mod
ROM OS Version: Android 8.1.x and Android 9.x
Version Information
Status: Beta
Created 2018-09-30
Last Updated 2018-09-30

Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?

fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
To return the phone to stock, just install Factory Firmware.

fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
Done!

i installed treble according to your instruction and flashed a AOSP 8.1 image (system-arm64-aonly-gapps-su.img.xz) which should include gapps and su.
unfortunately the su-part wasnt available, so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
[edit]
installed another rom which had the option in developers to reboot directly into the recovery - that worked.
---------- Post added 5th October 2018 at 12:12 AM ---------- Previous post was 4th October 2018 at 11:43 PM ----------
Now i installed the latest Oreo Resurrection-Remix from https://downloads.resurrectionremix.com/arm64aonly/ and during startup:
{
"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"
}
Another thing is, that on all GSI-Images i installed so far the system-fonts are very tiny - like it's using a too high screen-resolution.

fred0r said:
......so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
Click to expand...
Click to collapse
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.

fred0r said:
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
Click to expand...
Click to collapse
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.

xXxSAMIxXx said:
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
Click to expand...
Click to collapse
vendor miscmatch message is a warning. Not an error!

a great work ..soon i will get this device

I'd like to try out Android P. Has anyone tried this with a Swift 2 device and can recommend a GSI to use?
Edit: I couldn't get Pixel Experience (9.0) to boot succesfully but phhusson's AOSP 9.0 works. It's very barebones indeed. Someone made an overlay that makes adaptive brightness possible but I still can't adjust the LED for notifications. Not being able to turn off the charging/low-battery LED is a bummer. Otherwise it runs fine but I'll try a different GSI today.

Did you use the arm64 a-only image? I tried the arm a-only and that wouldn't boot but I'm (quite) happily buzzing along with the former.

fx-mod said:
* Patch for fix fingerprint scanner on some Pie GSIs
Phh AOSP 9 v106 [02/10/2018] only
ArrowOS 9 [23/09/2018] only
Pixel Experience P [20/09/2018] only
Click to expand...
Click to collapse
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.

erasmuswill said:
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
Click to expand...
Click to collapse
it is done!

wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone

waver1967 said:
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
Click to expand...
Click to collapse
32 GB of course

failed to mount system
after doing all the steps twrp says no os installed

oeps my mistake..
forgot to unrar gsi file

Is it possible to patch at least one of Pie GSI's to work almost perfectly? Right now it is not possible to use any of GSI's for more than a week because every one have some annoying bugs

puszekkk said:
(
Click to expand...
Click to collapse
What does not suit you?

anatoliy-is said:
What does not suit you?
Click to expand...
Click to collapse
Broken hotspot, dumped fingerprints after reboot, broken wifi, broken audio routing :/

[GUIDE][A/B][A505x] Guide on How to flash GSI

I'm not responsible for whatever damage this could possibly cause to your device.
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to GSI For Galaxy A50 ONLY FOR A505F/A505FN/A505GN​
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
If any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide Guide that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
All Sensors
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A/B_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
- STEPS FOR INSTALLING GAPPS
Download the appropriate OpenGapps.org
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- FOR INSTALLING FIXES:
Camera Fix (Flash only on NON Working GSIs)
- KNOWN BUGS:
Fingerprint
Bluetooth calls are broken
May be more, Let me know
Downloads. F.A.Qs below
XDA:DevDB Information
Guide on How to flash GSI, ROM for the Samsung Galaxy A50
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-05-26
Last Updated 2019-05-26

{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Generic System Image (GSI) : Github
Treble folder : Gdrive
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps

F.A.Q
Q : Do i need to format internal storage ?
A : No
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only AB_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above

But our device is A only right? why flash AB

Lynjun002 said:
But our device is A only right? why flash AB
Click to expand...
Click to collapse
your device is System-as-root, which is somewhat similar to A/B, so AB GSI will boot on your device.

Lynjun002 said:
But our device is A only right? why flash AB
Click to expand...
Click to collapse
for more information : https://source.android.com/devices/bootloader/system-as-root

Lynjun002 said:
But our device is A only right? why flash AB
Click to expand...
Click to collapse
yes its A, flash A only

kamalkiraa said:
yes its A, flash A only
Click to expand...
Click to collapse
You can even flash A only gsi, but it will not boot, so prefer A/B

does anyone try any GSI?

kamalkiraa said:
yes its A, flash A only
Click to expand...
Click to collapse
Hi thanks for response

kamalkiraa said:
does anyone try any GSI?
Click to expand...
Click to collapse
It's great for the novelty but without fingerprint recognition and bluetooth calls, not to mention other bugs that will crop up, this isn't going to be a daily driver. Custom ROMs are still the best bet but without any developers on board, it doesn't seem like much development will be happening for this device.

t3chg33k said:
It's great for the novelty but without fingerprint recognition and bluetooth calls, not to mention other bugs that will crop up, this isn't going to be a daily driver. Custom ROMs are still the best bet but without any developers on board, it doesn't seem like much development will be happening for this device.
Click to expand...
Click to collapse
Ultra Wide Angle work on GSIs ?

Arnaud Créative Studios said:
Ultra Wide Angle work on GSIs ?
Click to expand...
Click to collapse
No as you wont have the stock samsung camera and gcam or any other 3rd party camera does not support the wide angle lens on our devices *yet*.

Doubt
Do the in display fingerprint scanner work? Or does even does face unlock work? I am very curious

bobandar said:
No as you wont have the stock samsung camera and gcam or any other 3rd party camera does not support the wide angle lens on our devices *yet*.
Click to expand...
Click to collapse
Ok I think they'll add support in future,a lot of phone have Wide Angle cam
---------- Post added at 07:49 PM ---------- Previous post was at 07:48 PM ----------
Pratham Gajjar said:
Do the in display fingerprint scanner work? Or does even does face unlock work? I am very curious
Click to expand...
Click to collapse
Face Unlock work on all devices for Fingerprint I can't answer you I haven't buy A50 yet I'll do next month for my birthday

Just inquisitive as I have rooted my device with stock recovery only. From what I have read, TWRP doesn't work with the latest kernels, so how are all the patches going to be flashed assuming the system image is flashed using fastboot?

t3chg33k said:
Just inquisitive as I have rooted my device with stock recovery only. From what I have read, TWRP doesn't work with the latest kernels, so how are all the patches going to be flashed assuming the system image is flashed using fastboot?
Click to expand...
Click to collapse
I think this is a good beginning please keep the good work

Any update please :angel: ?
Maybe someone has tried which roms is the best for our lovely A50 ?

Pratham Gajjar said:
Do the in display fingerprint scanner work? Or does even does face unlock work? I am very curious
Click to expand...
Click to collapse
as i mentioned in bug list FP will not work
xsleena said:
Any update please :angel: ?
Maybe someone has tried which roms is the best for our lovely A50 ?
Click to expand...
Click to collapse
Do u have twrp installed ?

prashantp01 said:
Do u have twrp installed ?
Click to expand...
Click to collapse
not for now

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 (Snapdragon)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S10 G9730, G973U, G973U1 and G973W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10: beyond1qlte.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
10.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
16.02.2021 - Initial R build for Android 11
31.12.2020 - Update TWRP to 3.5.0
14.11.2020 - Initial Release

Seems to be working properly! Thank you!

wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!

robocopvn said:
wow we can unlock Bootloader and install Custom recovery on the US Galaxy S10 now, great!
Click to expand...
Click to collapse
It isn't free, but yes. Mine is and rooted. Verizon variant here.

abranson said:
It isn't free, but yes. Mine is and rooted. Verizon variant here.
Click to expand...
Click to collapse
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.

superturtlr19 said:
Can you elaborate on how you unlocked the bootloader on the Snapdragon variant? I waited 7 days, but the oem unlock option is still not showing.
Click to expand...
Click to collapse
I had to pay and had it done remotely. Sampwnd. . Google it

abranson said:
I had to pay and had it done remotely. Sampwnd. . Google it
Click to expand...
Click to collapse
Oh wow, these are pricey. Well thank you for your time.

Deleted

afaneh92 said:
Note: download link is down, will make new build tomorrow then will fix the link. Please do not share older builds.
Edit: new builds are up, US devices are not supported anymore, only devices already unlocked before 9 November are.
Click to expand...
Click to collapse
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it

illspiritX said:
Any chance US model support coming? Any insight why it's so much harder? I don't know anything about it
Click to expand...
Click to collapse
Read notes on OP

afaneh92 said:
Read notes on OP
Click to expand...
Click to collapse
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?

abranson said:
I'd like to request to use the new twrp builds. I got unlocked after November, though. what do I need to provide if you are to grant the green light to use?
Click to expand...
Click to collapse
Will contact you on telegram

Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?

fabiokino said:
Thank you very much @afaneh92, I followed the procedure and was able to install TWRP and magisk, and everything is working fine.
The only thing that I'm not able to do is to re-encrypt the phone at the end. The encription procedure starts, but then it is stuck for hours on the "encrypting..." screen and nothing happens. I tried to temporarily remove magisk and also to restore the recovery partition, but nothing seems to work. Do you know if there is any workaround?
Click to expand...
Click to collapse
To encrypted the the data partition again need to do factory reset from stock recovery.

afaneh92 said:
To encrypted the the data partition again need to do factory reset from stock recovery.
Click to expand...
Click to collapse
Thank you for the answer. My idea was to make a TWRP image once I completely personalized the system and then encrypt the device, but I understand that it's not possible...
So the alternative solution is to find a way yo make an image of the encrypted device after the personalization...
Is there a way to make an image of the encrypted data partition apart from using dd? Since it is encrypted with fbe I was wondering if there's a method which doesn't require to save the whole partition but only the actual (encrypted) files.

Changelog:
16.02.2021 - Initial R build for Android 11

Does anyone with a SM-G9730 wanna try a US rom I made for it?

how to disable AVB in s10 9730?

jrkruse said:
Does anyone with a SM-G9730 wanna try a US rom I made for it?
Click to expand...
Click to collapse
9730 module can flash us version? I wanna try

LIR GSI Rom for Nord N10 5g

For these of you who wanna try good custom rom instead buggy roms filled with same google ****. I got good expierience with these GSI roms. On my Nokia 7.2 I'm running Bless 306 and on Nord N10 5g i'm using LIR as my daily drive. Keep in mind I'm not gamer.Here is the link to the rom:
[UNOFFICIAL] LineageOS R Mod //LiR
L i R < 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...
forum.xda-developers.com
Installation;
First at all my cell was already on Android 11, not sure about 10. 2nd it's my expirience and my opinion.
fastboot flashing unlock and then fastboot flashing unlock_critical
dev mode enabled
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
If you got error like these
Code:
fastboot flash system.img
Invalid sparse file format at header magic
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
DON"T DO as same advised fastboot delete-logical-partition product you will got problems when return back on stock ,with Magisk or installing diff roms. If you already did read guide about phones with dynamic partitions https://forum.xda-developers.com/t/tutorial-magisk-on-gsi-on-devices-with-dynamic-partition.4311045/, download product_gsi.img form there and do.
fastboot flash product product_gsi.img
fastboot flash system lir-v313+211012-arm64-bvZ.img. I used image w/o google staff
fastboot -w
fastboot reboot
Setup and enjoy
Root avalible in Settings/Misc features/SuperUser or use Magisk 23
For SMS/MMS I installed ims apk for Qualcomm vendor .You find it in Settings/Phh Treble Settings/Misc (see pics)
{
"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"
}

Well put, I flashed and booted the crdroid11 gapps gsi with oxygen 11 firmware following this, booted on the first attempt, twenty minutes after oneplus gave unlock token. twrp does not go into fastbootd, had to use stock recovery after initial backup. Sanity returns, been without rooted device over two months.

Glad it helps. Yes twrp not fully working avoid it. I forgot to mention to use stock recovery or recovery from any roms posted in this forum (derpfest,oneplus or lineage). They are same.

Wow, do biometrics work on this GSI?

It based on PHH's AOSP R and AndyYan Lineage GSI. All errors same, but fingerprints working.They have versions with Gapps but I don't use them. I'm don't need custom ROM with Google. Pointless! Rooted and debloated stock OxygenOS in my opinion is best way in that case.
Buy the way I'm thesting right now latest Phh AOSP 400.d with Android 12. It works flawless on my phone.

boom15 said:
It based on PHH's AOSP R and AndyYan Lineage GSI. All errors same, but fingerprints working.They have versions with Gapps but I don't use them. I'm don't need custom ROM with Google. Pointless! Rooted and debloated stock OxygenOS in my opinion is best way in that case.
Buy the way I'm thesting right now latest Phh AOSP 400.d with Android 12. It works flawless on my phone.
Click to expand...
Click to collapse
If A12 GSI has fingerprint working on N10 5G, it'll be a perfect daily driver. Getting annoyed with all bloat. Does 5G work properly too?

UsedNametag said:
If A12 GSI has fingerprint working on N10 5G, it'll be a perfect daily driver. Getting annoyed with all bloat. Does 5G work properly too?
Click to expand...
Click to collapse
I don't have 5g plan, can't tell you. On last version of android 11 it used to show you option to change to 5G/LTE/3G/2G. On Android 12 it not shows on my phone.Fingerprints working.
And couple glitches if you try it. In my case after setup preferred mobile network setuo on 3G, so change it . Install ims. Check post above.BT,Camera,Sound, Storage,Tethering,OTG,Seedvault, AdAway, Google Maps and su working. I'm using arm64-ab-vndklite-vanilla on top of Android 11 with unlocked bootloader,stock boot and recovery. Not sure about any fancy stuff and banking apps.

Yes five 5G works on this one and all the gsi's on that source forge. And it works on a11 firmware(I haven't tried 10 firmware), I keep reading we're stuck on 10 for gsi's, that has not been my experience at all! Also the product_gsi.img is the proper method over deleting the product partition.
You can install Google's 12 gsi(on 11 firmware as I tested it), I grabbed the image from /data/gsi/dsu after downloading it through dsu loader in developer setting. The gsi's it seems attempt dsu install, I think OnePlus would need to enable it, it ends up booting whatever system you have installed with the new blank userdata image. The would-be Google 12 gsi system will flash with fastboot.

mrbox23 said:
Yes five 5G works on this one and all the gsi's on that source forge. And it works on a11 firmware(I haven't tried 10 firmware), I keep reading we're stuck on 10 for gsi's, that has not been my experience at all! Also the product_gsi.img is the proper method over deleting the product partition.
You can install Google's 12 gsi(on 11 firmware as I tested it), I grabbed the image from /data/gsi/dsu after downloading it through dsu loader in developer setting. The gsi's it seems attempt dsu install, I think OnePlus would need to enable it, it ends up booting whatever system you have installed with the new blank userdata image. The would-be Google 12 gsi system will flash with fastboot.
Click to expand...
Click to collapse
Thank you for advise. I tried google before phh.Prefer phh.Maybe because of name goo.... Long time using phones without less google stuff if possible. Used CalixOS on my last Pixel until it decided to jump from cliff!
But any way I build my own using phh code, implement some changes related to phone and provider (ims, mobile network detection, ril, bt headset connection,MicroG).

boom15 said:
Thank you for advise. I tried google before phh.Prefer phh.Maybe because of name goo.... Long time using phones without less google stuff if possible. Used CalixOS on my last Pixel until it decided to jump from cliff!
But any way I build my own using phh code, implement some changes related to phone and provider (ims, mobile network detection, ril, bt headset connection,MicroG).
Click to expand...
Click to collapse
I somehow disabled my accelerometer, and proximity sensor. I did the usual msm restore, to no avail. I'm stumped. It broke after a botched fastboot flashing. How might you approach such a situation? You might have experience with something like making an overlay specific to a device? I am so stumped with this, I have reflashed every partition I can find from payload bins and ops files....I use one of those sensor apps(the one in phh settings shows nothing at all, or crashes) more than one says simply "this device has no sensors"

mrbox23 said:
I somehow disabled my accelerometer, and proximity sensor. I did the usual msm restore, to no avail. I'm stumped. It broke after a botched fastboot flashing. How might you approach such a situation? You might have experience with something like making an overlay specific to a device? I am so stumped with this, I have reflashed every partition I can find from payload bins and ops files....I use one of those sensor apps(the one in phh settings shows nothing at all, or crashes) more than one says simply "this device has no sensors"
Click to expand...
Click to collapse
Check if you have /persist/sensors first. If you on stock try factory mode as someone sugested here on these forum.

[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!