Database Develop

[Official] crDroid 9.0 TISSOT 05-11-19 Security patch

crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Feature list https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Rom folder + screenshot -> https://drive.google.com/open?id=1GYVVJ2GVC-MCN-dL84x8Z2uPkhcUd3cY
Instructions :
Backup all before flash!!
Check if you have unlocked bootloader and updated firmware if not download and flash it with twrp and reboot recovery before start flash
https://drive.google.com/open?id=1FfYb6hWviggupkQRBNfE-ah85MSl-1aB
First of all you need to flash or boot @Giovix92 TWRP (I recommend)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
or official twrp
Boot into twrp and factory reset
Flash the rom zip
Flash twrp installer (skip if you use twrp survive option)
Reboot recovery
Flash opengapps nano or pico
If you want to root, flash Magisk
Reboot to System.
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES :
You tell me
Some QS theme maybe have color problem but default QS works. Source bug,I can't fix for now
A very special thanks to @Giovix92 and my telegram friends https://t.me/XiaomiMiA1Italia and who tested this rom.
Source
https://github.com/crdroidandroid
https://github.com/LineageOS/android_device_xiaomi_msm8953-common/tree/lineage-16.0
https://github.com/LineageOS/android_device_xiaomi_tissot
https://github.com/LineageOS/android_kernel_xiaomi_msm8953
https://github.com/RevengeOS-Devices/android_vendor_xiaomi_tissot
https://github.com/LineageOS/android_device_xiaomi_msm8953-common/tree/lineage-16.0
https://github.com/LineageOS/android_device_xiaomi_tissot
https://github.com/LineageOS/android_kernel_xiaomi_msm8953
https://github.com/RevengeOS-Devices/android_vendor_xiaomi_tissot
XDA:DevDB Information
[Official] crDroid 9.0 TISSOT, ROM for the Xiaomi Mi A1
Contributors
samuele94, Giovix92, https://t.me/XiaomiMiA1Italia users for support!
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 firwmare (check my profile)
Based On: LOS
Version Information
Status: Stable
Created 2019-10-23
Last Updated 2019-11-28

Goodjob!

Hope 6.0 for 10

Nickinfinity said:
Goodjob!
Click to expand...
Click to collapse
Thanks,I'll keep it updated!
manchirua said:
Hope 6.0 for 10
Click to expand...
Click to collapse
Yes but for now I wait stable public trees for us,for now I keep android 9 updated and I try to build 6.0 soon!
until the situation of android 10 remains "beta" I will stay on android 9 for stability.
android 10 is a great working in progress, right now I don't feel the need to go to 10 but I'll work on it willingly! The development of tissot needs people who keep it alive!

Awesome, unless q stabalises pie will do dont rush for q, btw why not take official maintainership, its abandoned afaik.

Good, thanks bro

Sohil876 said:
Awesome, unless q stabalises pie will do dont rush for q, btw why not take official maintainership, its abandoned afaik.
Click to expand...
Click to collapse
You're right but I'm learning. I only claim to continue building this rom for my only smartphone because I want to keep an updated rom 9.0. For now the tag isn't essential for me but I'll see what I can do!

Any particular opengapps recomended? I've found some trouble installing latest opengapps builds in LOS 16. Latest opengapps is working fine in crDRoid?
Thanks for your effort.

samuele94 said:
Thanks,I'll keep it updated!
Yes but for now I wait stable public trees for us,for now I keep android 9 updated and I try to build 6.0 soon!
until the situation of android 10 remains "beta" I will stay on android 9 for stability.
android 10 is a great working in progress, right now I don't feel the need to go to 10 but I'll work on it willingly! The development of tissot needs people who keep it alive!
Click to expand...
Click to collapse
Yeah, thank you
BTW, i can use MindTheGapps?

manchirua said:
Yeah, thank you
BTW, i can use MindTheGapps?
Click to expand...
Click to collapse
Not tested but why not? you can try,rom works fine with opengapps but i think you can change type of gapps. I like opengapps nano (or pico) but MindTheGapps for arm64 and android 9 should work properly

Mendibil said:
Any particular opengapps recomended? I've found some trouble installing latest opengapps builds in LOS 16. Latest opengapps is working fine in crDRoid?
Thanks for your effort.
Click to expand...
Click to collapse
Last i tried all gapps build before 6 oct worked fine so download older than 6 oct release, its not los problem.

Great rom, Working flawlessly.
Btw any solution for green slow-motion recording?

Mendibil said:
Any particular opengapps recomended? I've found some trouble installing latest opengapps builds in LOS 16. Latest opengapps is working fine in crDRoid?
Thanks for your effort.
Click to expand...
Click to collapse
Yes you can use latest opengapps nano or pico 9.0 arm64 but if you have problem you can download older version here https://sourceforge.net/projects/opengapps/files/arm64/ gapps are nightly, I don't know if it have bugs/problems
Stealtherthreat said:
Great rom, Working flawlessly.
Btw any solution for green slow-motion recording?
Click to expand...
Click to collapse
Try a good GCam and see if it fix, I don't use this feature sorry
Added on my Gdrive folder changelog about this build. I'll update file after new build,when new build? when I can see difference to previous build!

Hi to all! Rom is now official,check here!
https://crdroid.net/tissot Add Telegram group https://t.me/crDroidA1
Tested today opengapps nano 25/10/19 works perfect and encryption works too

Messed up
Not sure what happened but everything is messed up after trying to flash the new ROM.
not able to run twrp properly,
Not able to install gaps
I keep getting a message that some partition is not there and...
Looking for a new handset...

teoasv said:
Not sure what happened but everything is messed up after trying to flash the new ROM.
not able to run twrp properly,
Not able to install gaps
I keep getting a message that some partition is not there and...
Looking for a new handset...
Click to expand...
Click to collapse
Steps? Twrp used? Here works fine,tested by me and other people. Without info I can't help you

samuele94 said:
Steps? Twrp used? Here works fine,tested by me and other people. Without info I can't help you
Click to expand...
Click to collapse
Tried to do everything by the book:
Was running the previous cdroid version.
BAckuped everything.
Wipe clean (not the Data)
Flashed the new one with twrp
After that I could not load the twrp recovery anymore and it kept loading the lineage recovery tool which I have not seen before.
I ADB flashed the twrp but not on recovery partition. Recovery was not found and therefore I flashed it on boot(the command that worked: fastboot flash boot twrp.img) But then I could not flash any Gapps . It gave me a message that a partition was missing or something.
What seemed to work but not quite:
Wiped everything with the lineage recovery tool
AdB sideload the new rom
After no success on any Gapps package with this method, I tried the MindtheGapps and it sort -of - works: I got google but cannot restore my google data

teoasv said:
Tried to do everything by the book:
Was running the previous cdroid version.
BAckuped everything.
Wipe clean (not the Data)
Flashed the new one with twrp
After that I could not load the twrp recovery anymore and it kept loading the lineage recovery tool which I have not seen before.
I ADB flashed the twrp but not on recovery partition. Recovery was not found and therefore I flashed it on boot(the command that worked: fastboot flash boot twrp.img) But then I could not flash any Gapps . It gave me a message that a partition was missing or something.
What seemed to work but not quite:
Wiped everything with the lineage recovery tool
AdB sideload the new rom
After no success on any Gapps package with this method, I tried the MindtheGapps and it sort -of - works: I got google but cannot restore my google data
Click to expand...
Click to collapse
You shouldnt flash img from fastboot only boot that, fastboot boot twrp then flash installer.zip file of twrp from the hotbooted twrp, then do reboot to recovery.

Sohil876 said:
You shouldnt flash img from fastboot only boot that, fastboot boot twrp then flash installer.zip file of twrp from the hotbooted twrp, then do reboot to recovery.
Click to expand...
Click to collapse
Sorry I don't get what you are saying. I did this:
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If your asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp-2.8.x.x-xxx.img
└ Here modify twrp.img with the name of your TWRP recovery .img file.
Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot

teoasv said:
Tried to do everything by the book:
Was running the previous cdroid version.
BAckuped everything.
Wipe clean (not the Data)
Flashed the new one with twrp
After that I could not load the twrp recovery anymore and it kept loading the lineage recovery tool which I have not seen before.
I ADB flashed the twrp but not on recovery partition. Recovery was not found and therefore I flashed it on boot(the command that worked: fastboot flash boot twrp.img) But then I could not flash any Gapps . It gave me a message that a partition was missing or something.
What seemed to work but not quite:
Wiped everything with the lineage recovery tool
AdB sideload the new rom
After no success on any Gapps package with this method, I tried the MindtheGapps and it sort -of - works: I got google but cannot restore my google data
Click to expand...
Click to collapse
Previous version? It's the first version!
Your firmware is up to date? you need to update it and hotboot again twrp,flash installer reboot recovery and follow op step.
No you need to fastboot boot latesttwrp.img boot not flash,for flash you need twrp installer

[Q][BONITO] Descendant X - android ver. 10r32

{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page. Download the zip and *-boot.img for your device.
Sources
Githubhttps://github.com/Descendant-Devices
Backup internal storage, wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/*-boot.img
Reboot into recovery using volume and power buttons and select "Apply update from ADB," then:
Code:
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data on first install. No wipes are needed between updates from Descendant itself, unless specified.
Reboot into the system and you should be good.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct ​
Android OS version: 10.0.0_r32
Security patch level: March​
XDA:DevDB Information
Descendant X, ROM for the Google Pixel 3a XL
Contributors
johngalt1, Dil3mm4
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2020-03-09
Last Updated 2020-03-11

Cool cool some more love coming in

Magisk Question
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.

crypto69 said:
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
Click to expand...
Click to collapse
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.

johngalt1 said:
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
Click to expand...
Click to collapse
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning

crypto69 said:
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
Click to expand...
Click to collapse
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:

johngalt1 said:
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
Click to expand...
Click to collapse
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.

crypto69 said:
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
Click to expand...
Click to collapse
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.

stompysan said:
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
Click to expand...
Click to collapse
Thank you, will do.
If anyone wants to install V4A, I can confirm it works on this ROM. Use this guide and follow steps 1-15.
https://www.the***********.com/install-viper4android-android-10-guide/

What version do I have to download for a 3a xl device ?

Benxxx said:
What version do I have to download for a 3a xl device ?
Click to expand...
Click to collapse
I'm not sure but assuming it's the a/b version to download. I also don't see a boot.img on the download page. Am I missing it somewhere?

Hasn't been updated in like 2 months if I am reading it right

[Discontinued] [ROM][11.0] crDroid 7.6 [OFFICIAL]

{
"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 I am not responsible for any damage you made to your device You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features: https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.2 or newer for root - (Download from here)
First time installation:
Download twrpboot.img & twrp.zip in your pc (link above) and extract zip file
Hotboot twrp from your pc with command fastboot boot boot-recovery.img
Wipe system wipe data wipe dalvik cache
Copy downloaded rom fom pc to your phone and start the installation
After installing flash twrp.zip and reboot to recovery again
Install gapps & magisk (optional) and then reboot your phone
Profit! (Enjoy your rom)
Update installation:
You can choose to update via seamless ota or use recovery mode method
Ota has some issue with gapps atm so after doing ota just reboot to recovery and flash gapps, then reboot to system
For recovery update method:
Reboot to recovery from phone
Flash Rom.zip & Twrp.zip and reboot to recovery
Flash Gapps
Flash Magisk (optional) & reboot your phone
Profit! (Enjoy your rom)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel
Download:
ROM Mi A1 (tissot)
Changelog: Here
Known issues: Random freezes on certain apps
Visit official website @ crDroid.net
crDroid Tissot Telegram
crDroid Community Telegram
Donate to help our team pay server costs

Working:
Camera/Video/Mic
Fingerprint
GPS
IMS (VoLTE)
RIL
Video playback
Wi-Fi
NightLight
CTS
DRM
FM
Encryption
WFD
Broken:
(Nothing Except Random Freezes)
Note: The ROM Does Not Include Gapps Feel Free to flash any gapps of your likings NikGapps Beta are Recommended
Screenshots
Credits:
@mtpiplod
@abhinavagrd_1129
FAQ's
1)Magisk Latest Beta is working?
a)Yes Full magisk is functional as well as you can use magisk hide without issues
2)Like previous Builds does this rom will update weekly?
a)No unless i find it important to do so i will update it bi-weekly or monthly
3)Chrome is freezing randomly?
a)it is because of DRM is crashing, because you are using root, to use it properly with root use latest magisk beta 21.x & hide magisk from settings & then reboot after it should be fixed
4)Random Freezes?
a)On all Android eleven based roms there are freezes issues abhinav managed to minimised them alot his kernel sources are not public but his Lineage OS Boot Image Works Just Fine In crDroid I am linking link for it use it and it should get fine

Reserved

Reserved

Pro

undated via OTA, the boot up screen with the crDroid logo keeps looping forever and I am not sure if ithe phone is frozen or it is working on updating itself.

rockyhlwong said:
undated via OTA, the boot up screen with the crDroid logo keeps looping forever and I am not sure if ithe phone is frozen or it is working on updating itself.
Click to expand...
Click to collapse
Same here, reinstalled gapps and now all is ok. thank you.

ziofester70 said:
Same here, reinstalled gapps and now all is ok. thank you.
Click to expand...
Click to collapse
excellent to know! it worked! thank you for the solution!

Is the device frequently freezing?I mean is it usable as a daily driver now?

ksk006 said:
Is the device frequently freezing?I mean is it usable as a daily driver now?
Click to expand...
Click to collapse
The freezes are random i face like once in a week or two, some face frequent. Youll have to try yourself.

Hi! The bootloop happens when I want to install Magisk, first flash the new update of March 30, I installed gapps, reboot and everything fine, I try to reinstall Magisk and it remains in bootloop. Any solution?

Which version of magisk?
I installed 21.4 without problem then updated through magisk app

Thanks! What I just did is remove the Magisk modules and reinstall ... What if, forced closures have been appearing in some Google Apps. I reinstalled the latest Gapps
My Magisk is the version 22.

Using for 3 days still no freezes...

ziofester70 said:
Same here, reinstalled gapps and now all is ok. thank you.
Click to expand...
Click to collapse
Same loop here, but struggling to resolve. Installed the update OTA, rebooted and stuck, so via Bootloader loaded TWRP and flashed Gapps, though rebooting to System end up back on original version/release.
Sure I'm doing something silly but can't figure it out?!

After last update ok google stop woking, only to me?

Calls won't work for me from mobile phone to mobile phone. Can't hear my dad and he doesn't hear me. It also crashed twice at 0:13 when I tried to activate my speaker.
Only worked sometimes when I called myself via home phone.

Nekromast said:
Calls won't work for me from mobile phone to mobile phone. Can't hear my dad and he doesn't hear me. It also crashed twice at 0:13 when I tried to activate my speaker.
Only worked sometimes when I called myself via home phone.
Click to expand...
Click to collapse
Working here without any problems. May be there is a hardware problem

Hi community! : D
I would like to ask if any of you have experienced frequent freezes, that is, I have been experiencing fairly frequent random freezes, plus some performance drops that can lead to a freeze.
I have seen that very little happens to many of you, there was an occasion for me that they appeared 3 times in one day :C.
I attach some logs (MatLog), hoping they can work.
And the load, do you know why it is being slow?

Link for Logs https://drive.google.com/file/d/1EENNbJZaP27hQnZ69m9EZVrQ1J1r7PN4/view?usp=sharing
Jooshe Danhi said:
Hi community! : D
I would like to ask if any of you have experienced frequent freezes, that is, I have been experiencing fairly frequent random freezes, plus some performance drops that can lead to a freeze.
I have seen that very little happens to many of you, there was an occasion for me that they appeared 3 times in one day :C.
I attach some logs (MatLog), hoping they can work.
And the load, do you know why it is being slow?
Click to expand...
Click to collapse

[ROM][PixelExperience 12.1][A70][FN]

{
"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"
}
View info: https://www.xda-developers.com/pixel-experience-12-hands-on/
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Your warranty is now void!
>I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
>You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
What is working?
-Everything is working (also fingerprint; bluethooth; 1 sim/maybe 2)
-File's Download-
>Vendor: https://forum.xda-developers.com/attachments/vendor_a11-zip.5336611/
>Rom: https://github.com/zainullahk/universal-pixelexperience-samsung/releases
make sure to download the arm64-ab-12.0 and not the arm64-ab-vndklite.
!Optional!
>Kernel: https://opensource.samsung.com/uploadSearch?searchValue=A70.
>Magisk: https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip
-Installation guide-
>Enter recovery (TWPR).
>Press "Wipe"-->"Format Data" -type "yes".
>On PC Extract the rom.
>And copy "Vendor_A11.zip";"PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img";"app-debug.zip" to the external/internal sd storage.
>First install the vendor follow steps below:
>"Wipe"-->"Advanced Wipe"-->Select Dalvik; Cache; System and Vendor -->"Swipe to Wipe".
>Now click on "Install" then select "Vendor_A11.zip".
>Then go back and flash the rom as "System Image".
--------------------
>!Optional!
>Flash magisk (debug.zip) !DON'T DO OTA UPDATES FOR NOW IF YOU USE MAGISK!
--------------------
>Reboot System and it should work for samsung a70.
(I did't created the rom; vendor; magisk i just have found a way to install the rom onto a galaxy A70).
-Pixel Experience 12 v402-
>New update to pe!
>Check the Updater page on Treble App to OTA update.
>Sync with February sources of PE (give a warm welcome to Face Unlock).
>Sync with AOSP 12.0 v402 by @phhusson.
>Fix permissions on dynamic su binary.
-OFFICIAL SITE-
Home - Pixel Experience
Home - Pixel Experience
download.pixelexperience.org
-COMMENT BELOW FOR ANY ISSUE-

USE THE STOCK KERNEL TO BE SURE THAT THE ROM WORKS!

Is volte working with this rom?

MarvinMod said:
Is volte working with this rom?
Click to expand...
Click to collapse
Yes sure the LTE connection is working!

Topo's said:
Yes sure the LTE connection is working!
Click to expand...
Click to collapse
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone

rttxda said:
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone
Click to expand...
Click to collapse
I had read "LTE" and not "VoLTE"

rttxda said:
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone
Click to expand...
Click to collapse
thanks! you are right

Getting "Verifying VBMeta Image error"
Tried flashing with and without Magisk but nothing happened.
Edit: That seemed due to my incorrect TWRP flash. But now I am getting bootloop after install.

Dakshxda said:
Getting "Verifying VBMeta Image error"
Tried flashing with and without Magisk but nothing happened.
Edit: That seemed due to my incorrect TWRP flash. But now I am getting bootloop after install.
Click to expand...
Click to collapse
@Dakshxda remember to have the stock vendor of your device!
Follow my updated guide:https://forum.xda-developers.com/t/rom-gsi-100-working-a70-no-bootloop.4470471/
this 100% work
​

"Verifying VBMeta Image error" to fix the error you must flash stock firmware and then twpr 3.6.0+

Hi. After flashing the system, the /system_root partition is not mounted. Can't change device name in build.prop

removez said:
Hi. After flashing the system, the /system_root partition is not mounted. Can't change device name in build.prop
Click to expand...
Click to collapse
You dont need to change the build.prop..
Why would you need to?

Ive been very busy with work, building a house. I may jave time this evening to flash and confirm Volte working or not.

Can install on a70f?

I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?

MarvinMod said:
You dont need to change the build.prop..
Why would you need to?
Click to expand...
Click to collapse
The Samsung Wear program refuses to work with this firmware. I could change the name of the device and it would work

Jinetty21 said:
I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?
Click to expand...
Click to collapse
I installed it once crookedly and did not start up was a bootloop. Then I flashed the stock firmware and then this one and it started. But magisk worked crookedly, the /system_root partition was not mounted

So here's what I did:
1. Flash stock via Odin
2. Reboot and then power off, then go to download
3. Flash TWRP 3.6.2
4. Reboot to recovery
5. Follow instructions above
6. Got Vbmeta error so I flashed VBMeta.tar from here
7. Rebooted but now it bootloops
Topo's said:
"Verifying VBMeta Image error" to fix the error you must flash stock firmware and then twpr 3.6.0+
Click to expand...
Click to collapse

Jinetty21 said:
I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?
Click to expand...
Click to collapse
1)I have wrote the post and i didn't copied.
2)I have tried this and worked whit my 2 devices (Galaxy a70FN;A70MN)
3)It is a generic system image

Moderator Info,
Thread has been closed at OP's request. @Topo's if you decide to progress further with the ROM, please report the first post and request to have it opened. We will be able to open it for you.
Thanks,
Stephen

[ROM][13.0][OnePlus8T] PixelExperience [AOSP/UNOFFICIAL] - JUNE 24, 2023

YOU MUST HAVE STOCK OOS13 INSTALLED ON BOTH SLOTS TO AVOID TOUCH SCREEN ISSUES. IF YOU ARE ON A11 or A12, THEN UPDATE TO A13. IF YOU ARE ON A13 then you are good to flash this already. Use copy partions if you want to make sure firmware is on both slots.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
PixelExperience for OnePlus8T[kebab]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Their mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
YOU MUST BE ON STOCK ANDROID 13 ON BOTH SLOTS FOR IT TO WORK PROPERLY. IF NOT, THEN UPDATE TO A13.
THANKS TO THE ENTIRE PE TEAM FOR HAVING THEIR SOURCE AVAILABLE FOR USE!!!
What's working?
You tell me
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
DOWNLOAD ROM & RECOVERY FILES HERE
Put recovery files in same folder as your fastboot or platform tools folder.
Install instructions also located here.​
Android OS version: 13.0​
Security patch level: June 2023​
Device Source code: https://github.com/PixelExperience-Devices​
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250​
Source code: https://github.com/PixelExperience​
ROM Developers: jhenrique09, Broly
Maintainer: TheSayaMan
XDADevDB Information
PixelExperience A13 ROM for OnePlus 8t Kebeb
REBOOT TO BOOTLOADER
fastboot -w​fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
fastboot flash recovery recovery.img
Reboot your phone to recovery mode, click "Install update" -> "ADB Sideload"
adb sideload PixelExperience-Plus-kebab-WEEKLY-13.0-20230624-UNOFFICIAL.zip
REBOOT TO SYSTEM TO SETUP. IF YOU WANT ROOT, THEN BOOT BACK TO RECOVERY AND ADB SIDELOAD MAGISK
adb sideload magisk.apk or rename magisk.apk to magisk.zip and adb sideload magisk.zip
IF YOU ARE ALREADY ON PREVIOUS UPDATE, YOU CAN DIRTY FLASH NEW UPDATE. REBOOT TO BOOTLOADER.
IN RECOVERY, SIMPLY ADB SIDELOAD NEW UPDATE.
UPDATES ARE INSTALLED TO INACTIVE SLOT IN CASE OF INSTALL ISSUE, YOU CAN REVERT BACK TO PREVIOUS BOOTABLE SLOT.

Oos12 or oos13 based ?

i try flash on oos13.

diegots said:
Oos12 or oos13 based ?
Click to expand...
Click to collapse
I have tested on 13. No idea if it will work on 12. It definitely will not work on 11.

vallobrescia said:
i try flash on oos13.
Click to expand...
Click to collapse
It will work fine

TheSayaMan said:
It will work fine
Click to expand...
Click to collapse
which recovery did you use? is the twrp from the official site ok?

Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)

SaigoW said:
Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)
Click to expand...
Click to collapse
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.

vallobrescia said:
which recovery did you use? is the twrp from the official site ok?
Click to expand...
Click to collapse
Yes twrp is fine or if your on another custom rom, you can use that one as well. I will post a recovery for this when I can.

TheSayaMan said:
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.
Click to expand...
Click to collapse
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ

logan_007 said:
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ
Click to expand...
Click to collapse
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.

does this one work better or the one on the official site?

TheSayaMan said:
Sì twrp va bene o se sei su un'altra rom personalizzata, puoi usare anche quella. Pubblicherò un recupero per questo quando posso.
Click to expand...
Click to collapse
Good job, I'll run this thread right.

TheSayaMan said:
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.
Click to expand...
Click to collapse
I use Pixel Experience recovery to flash the rom.
I flashed in the official Oxygen OS 13 version，It booted fine and everything works fine.
and then unlocked the OEM, extracted the Pixel Experience 13 recovery and then flash into this Pixel Experience recovery.
Also follow the tutorials to flash the rom
(https://wiki.pixelexperience.org/devices/kebab/install/)
After the first boot devices,the screen touch is not working.
{
"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"
}
Then I followed your instructions and the screen touch did not work either.
-----
I use the same way flash, PE ROM 12 is everything works, and I have used it for half a year.
Also I can't use twrp,I can't use twrp since android 11, even though I flashed in the latest version, it can't decrypt my data correctly and can't identify my data correctly. Maybe it's just a problem with my phone.
So I can't flash the PE rom via twrp either
just now I went to test the latest version of LineageOS android 13, also following the official tutorial to use LineageOS recovery to swipe in, and found the same problem, normal boot up, the result is the same as PE rom is on the new user guide page, the screen touch does not work.
---
I haven't seen too many people report this kind of problem, I think there may be some strange problems with my phone. TAT

vallobrescia said:
does this one work better or the one on the official site?
Click to expand...
Click to collapse
The official hasn't updated the security patch yet.

Thread updated with recovery install instructions.

Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?

M_Power01 said:
Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?
Click to expand...
Click to collapse
It's a known problem. I switched to Nova Launcher and then disabled that.

No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.

Dior DNA said:
No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.
Click to expand...
Click to collapse
Although this is Android 13. It's based on Android 12 so you must have a12 on both slots for it to work properly. Sorry for the confusion. I have updated the instructions, sorry.