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

Another fastboot loop

Hi everyone! I hope everyone is okay. Yesterday I finally unlocked the bootloader on my Xiaomi Redmi 8 and I wanted to install Havoc OS on it. Since there isn't a Havoc OS version for Redmi 8 I downloaded the arm64-aonly version. I also installed orange fox recovery. When I opened the Havoc OS folder I saw a .img file, but wherever I looked I saw that rom needs to be a .zip file. Nevertheless, I tried to install it with orange fox recovery. When I selected the file I needed to select one option. I really don't know that much about phones and ROMs so I clicked the "System" option or something like that and then I swiped the screen for it to install. It said it was successful. I rebooted and it was just a boot loop. No problem, I tried it again with a different option when I wanted to flash (I really don't remember what was it), and it didn't work, and then again, and again. I saw that I couldn't install it so I looked how do I install any custom rom on my Redmi 8 and I saw this link: https://forum.xda-developers.com/t/...pixel-experience-rom-for-redmi-8-gsi.4121741/. (I don't say that the person who posted this meant something bad, but I got a fastboot loop when I installed something from this link). I downloaded everything and the first thing I did was installing TWRP recovery. I did it the same way I did with the orange fox. I placed the .img file of TWRP in the ADB folder and entered "flash boot flash recovery ...img". When it was done, it started looping in fast boot mode. I am currently trying to install the official Xiaomi rom for my phone with the MiFlash tool but whenever I clicked on "Refresh" it says "The application was unable to start correctly (0x00007b). Click OK to close the application" and after that "fastboot.exe has stopped working". I tried using flash_all.bat but it doesn't work. I really want to fix this and I think that even sending it to a repairman won't work. I really don't know what to do so if you can help me I would appreciate it! P.S. (sorry for the bad English)

Omg stay on the fastboot logo.
Then do fastboot flash recovery orangfoxrecovery.img
The image should be the old one u were sure that works.
Then try booting into recovery.
If fastboot still breaks reinstall adb and fastboot.

{
"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"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI crafted by @SKULSHADY.
Many useful features that provide a smooth premium experience.
Just flash and enjoy...
https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6
Founder & Lead Developer:
SKULSHADY (Anushek Prasal)
DevOPS & Scaling:
Irongfly (Sukeerat Singh Goindi)
Support Team:
theo.j22 (Tushar Jain)
If you like our work and would like to support this project then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
ROM: https://download.havoc-os.com
About Us: https://havoc-os.com
Recovery: https://twrp.me
Magisk:https://github.com/topjohnwu/Magisk/releases
Telegram Support Group: https://t.me/havocofficial
Telegram Announcements Channel:https://t.me/Havoc_OS
Code Review: https://review.havoc-os.com
1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.
2. Wipe System, Data, Dalvik, Cache.
3. Flash the ROM, GApps (Optional), Magisk (Optional).
4. Reboot and Enjoy.
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
Whatever I got above is from a forum post in XDA.
This has the proper zip. In the havoc os website in links click -olive- which is the codename of your phone.
This is for after you get back into recovery.
TWRP is optional since you have orangefox.

[TOOL][Windows][Script]Get & Install Latest Official ADB & Fastboot Drivers
Most ADB-FASTBOOT installers are provided in UPXed .EXE-file format hence it's not transparent what they are internally doing unless you decompile it. So I decided to write the whole thing as a Windows CMD script thus everyone should can read...
forum.xda-developers.com
You can try this fastboot software if you like!

Thanks for your help but it didn't work. When I again installed orange fox it still fastboots and this software you recommended doesn't work, but again thanks for your help!

and you tried fastboot boot recovery.img
?
Did that work?
Ive heard of
fastboot reboot recovery
Working on some devices.

This shows up

And what happened with your phone during that time.

Nothing. It's still on fastboot screen

havoc was recently released officially on our phones, but no forum thread yet, only in telegram announcement
olive • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
most of the time, we also need the custom vbmeta. try installing it to see if recovery works
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
upd sorry, didnt see the new replies saying you are currently stuck beyond the bootloop

fonzacus said:
havoc was recently released officially on our phones, but no forum thread yet, only in telegram announcement
olive • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
most of the time, we also need the custom vbmeta. try installing it to see if recovery works
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yea but his fastboot is erroring with no reason.
Something faulty flashed idk

Kenora_I said:
Yea but his fastboot is erroring with no reason.
Something faulty flashed idk
Click to expand...
Click to collapse
yeah i just saw the new replies, sorry
whats the adb/fastboot version? our phone needs at least >29, what version is that?
TBH, the flash_all.bat (for windows, .sh for linux) is better than that tool. thats like the last silver bullet. if youve allowed adb/fastboot, try using it, and hope it.

oh, for the time being, try staying with TWRP because it should support A11, orfox hasnt been updated yet IIRC
Download TWRP for olive
Download TWRP Open Recovery for olive
dl.twrp.me
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
try fastbooting the vbmeta ive attached, TWRP, and booting to recovery. if that doesnt work then i guess a full flash is required.
note, IIRC our phone does support fastboot reboot recovery

Yeah actually, maybe he should try Linux instead. I've hit issues with windows before.
Try installing a Linux distribution like ubuntu and try flashing with that?

fonzacus said:
oh, for the time being, try staying with TWRP because it should support A11, orfox hasnt been updated yet IIRC
Download TWRP for olive
Download TWRP Open Recovery for olive
dl.twrp.me
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
try fastbooting the vbmeta ive attached, TWRP, and booting to recovery. if that doesnt work then i guess a full flash is required.
note, IIRC our phone does support fastboot reboot recovery
Click to expand...
Click to collapse
What is the issue with MiFlash tool too?
Idk what causes miflash tool to error.
Maybe something with the computer itself not the phone.

Kenora_I said:
What is the issue with MiFlash tool too?
Idk what causes miflash tool to error.
Maybe something with the computer itself not the phone.
Click to expand...
Click to collapse
i havent used miflash tool yet, but i remember the mi unlock tool kept me spinning around in circles (also windows only).
i cant find an answer for 'failed remote unknown reason'
i hope @p_vujic07 replies, im kinda sleepy ATM

First thank you guys for helping me with this, sorry I didn't see what you have been suggesting. I was looking at this post: https://forum.xda-developers.com/t/guide-restore-to-stock-firmware-using-fastboot-method.4005779/. I tried to use it and when I entered the first command it said that the partition table doesn't exist. Now I have experience with Linux and overall computers but this is the first time I did something like this on my phone. Because the partition table doesn't exist I booted up Rufus and put elementary-os on my flash drive (because I have only that distro right now). I opened Gparted to create a partition table but GParted doesn't recognize my phone. Sorry again!

fonzacus said:
havoc was recently released officially on our phones, but no forum thread yet, only in telegram announcement
olive • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
most of the time, we also need the custom vbmeta. try installing it to see if recovery works
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
upd sorry, didnt see the new replies saying you are currently stuck beyond the bootloop
Click to expand...
Click to collapse
Thank you! I did this and now I broke the loop! It's just booted in orange fox recovery. Thank you both! You saved my life! I just don't know what to do now, but you don't need to answer immediately

p_vujic07 said:
Thank you! I did this and now I broke the loop! It's just booted in orange fox recovery. Thank you both! You saved my life! I just don't know what to do now, but you don't need to answer immediately
Click to expand...
Click to collapse
Ahh thats great well you see the havoc OS post above?
download the zip from here
olive • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
Then format system data cache and dalvik.
Then flash the zip normally.
Magisk and Gapps can be installed optionally

I am literally scared of pressing anything. Is this what I need to wipe?

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16]

{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are 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.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing

Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!

Reserved

Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why

Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake

Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use

Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing

Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.

Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.

kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...

double tap to wake works while aod is on?

I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.

GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.

Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.

Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.

Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting

All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.

Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"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"
}

I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix

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