Database Develop

[ROM][SNAPSHOT][7.1] LineageOS 14.1 for Xperia TX

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org​
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Xperia TX (Hayabusa) - 14.1 : https://mega.nz/#F!O19HlahT!cY17UTilVThss5RD9TwSRQ
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.0 : http://forum.xda-developers.com/xperia-t-v/t-development/recovery-twrp-3-0-0-touch-recovery-t3319588
Informations and references :
Kernel CVEs : Security patches status https://cve.lineageos.org/android_kernel_sony_msm8x60
About LineageOS updates : ChangeLog available on https://download.lineageos.org/hayabusa/changes/
About LineageOS device side : See my GitHub trees linked below​
Unification of the user partitions into UserData
Read more about the UserData unification :
- https://wiki.lineageos.org/devices/hayabusa/​
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS official upgrade from older builds :
- (Information) Read the following post : Update & Build Prep
- (Optional) Backup your applications and / or ROM
- (CM / UNOFFICIAL) Flash the EXPERIMENTAL migration build and reboot to Android
- Flash the latest LineageOS ROM and reboot to Android
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot​
About the builds
Device tree : https://github.com/LineageOS/android_device_sony_hayabusa
Common tree : https://github.com/LineageOS/android_device_sony_blue-common
Kernel sources : https://github.com/LineageOS/android_kernel_sony_msm8x60
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony​
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example​
Q&A - FAQ
LineageOS 14.1 Hayabusa Regular Questions and Answers : Q&A Thread
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!​
LineageOS available for Hayabusa also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing​
XDA:DevDB Information
LineageOS 14.1, ROM for the Sony Xperia T
Contributors
Adrian DC
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Snapshot
Created 2016-12-31
Last Updated 2020-08-15

Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- Partitions (Data, Cache) : Ext4 and F2FS supported
- ROM Recovery : Broken for signed official (see below)
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently based on Huashan kernel
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok (RTC real hardware clock, in TWRP recovery too)
- Powered-off alarm : Ok
- Offline Charging : Ok
- Encryption : Works but system gets slower
- UserData Unification : Ok
- SEPolicies : Fully enforced

Reserved
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open the ROM recovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
Current local manifest of the ROM build
Code:
<!-- https://github.com/AdrianDC/laos_development_sony8960/blob/local_manifests/hayabusa.xml -->

What's new in 08.01 update? Where I can read about changes?

Missing root.. i have to flash it?

currently using this lineage-14.1-20170115-UNOFFICIAL-hayabusa.zip, and its really good
but what if i install stock rom gapps, is there any problem?
---------- Post added at 10:50 AM ---------- Previous post was at 10:10 AM ----------
Muhammad Amirul said:
currently using this lineage-14.1-20170115-UNOFFICIAL-hayabusa.zip, and its really good
but what if i install stock rom gapps, is there any problem?
Click to expand...
Click to collapse
not enough space?

Stock won't fit into the system partition.
I recommend micro (or pico if wished), additional apps you need are directly flashable and updated anyways by the Play Store.
Informations about root default removal will be shared soon.

Well, SuperSU flashes in systemless mode, and didn't work. What do we have to do to gain root access?

Lion_Heart9x said:
Well, SuperSU flashes in systemless mode, and didn't work. What do we have to do to gain root access?
Click to expand...
Click to collapse
Flash boot bridge with supersu

- UserData Unification no longer included inside the ROM release.
- New unify_userdata package generated to handle the same purpose
- restore_sdcard updated & both rehosted in a new folder
- Reliable CyanogenRecovery from Snapshot 13.0 kept online as safe working recovery
- Lineage Wiki informations updated and will be merged soon with the informations needed

Official Lineage releases are online and working fine so far.
Please read the informations I shared about the upgrade, migrations and the site post.
Also read the Features list, the ROM's Recovery is for now unable to flash our signed builds...

First I flash the rom, and i flash unify_userdata-20170128.zip. While flashing unify_userdata-20170128.zip, phone rebooted into CM recovery and showing error. And now, I have only 2GB usable. And when I try again to flash unify zip, it shows already unified and showing error 7. Any IDEAS????

Myo Thu Htet said:
First I flash the rom, and i flash unify_userdata-20170128.zip. While flashing unify_userdata-20170128.zip, phone rebooted into CM recovery and showing error. And now, I have only 2GB usable. And when I try again to flash unify zip, it shows already unified and showing error 7. Any IDEAS????
Click to expand...
Click to collapse
this might mean a lot of flashing, I would try:
1.fastboot flash recovery-13.0-20161220-SNAPSHOT-ZNH5YAO3XM-hayabusa.img
2.in CWM factory reset
3. install restore_sdcard-xxx.zip, follow instructions
4. reboot recovery
5. install unify_userdata-xxx.zip, follow instructions
6. fastboot flash twrp-3.0.2-20170108-boot-hayabusa.img
in TWRP look for partitions, if all is fine install rom and twrp.zip
else start over from 1

lobotron said:
this might mean a lot of flashing, I would try:
1.fastboot flash recovery-13.0-20161220-SNAPSHOT-ZNH5YAO3XM-hayabusa.img
2.in CWM factory reset
3. install restore_sdcard-xxx.zip, follow instructions
4. reboot recovery
5. install unify_userdata-xxx.zip, follow instructions
6. fastboot flash twrp-3.0.2-20170108-boot-hayabusa.img
in TWRP look for partitions, if all is fine install rom and twrp.zip
else start over from 1
Click to expand...
Click to collapse
where is the back key for CM recovery??
I followed your instructions and there still showing system partation has 14GB usage. Is that normal?? Can somebody show me screenshot( setting> storage) after unification.

Myo Thu Htet said:
where is the back key for CM recovery??
Click to expand...
Click to collapse
4 phones without hardware buttons the +++go back+++ item would have been nice ..., but you can always pull out the battery which has the advantage that you really reboot the bootloader
Myo Thu Htet said:
I followed your instructions and there still showing system partation has 14GB usage. Is that normal?? Can somebody show me screenshot( setting> storage) after unification.
Click to expand...
Click to collapse
I can't screenshot.
Unification still failed, you can check in twrp if you select storage, for example in install. You may add a factory reset in between 4-5.
Better first check the system space and if it's fine install the rom. Good luck!

This is the storage setting after clean flash and I cant install apps. Always showing storage is full. Plz Help. i did unification but the result is still the same. The storage are showing in TWRP. Any Idea???

Myo Thu Htet said:
This is the storage setting after clean flash
Click to expand...
Click to collapse
some general clarification, in the hope I got it right:
The unification just changes the amount of memory available to the system and data.
The rom will be stored in system, so what you see in (for example):
TWRP -> Install-> select storage-> Internal Storage
is the amount the user might use for apps and general usage, system will not appear.Your Phone has 16GB I would expect round about 10000MB, it's a guess as I have a different model out of the same family.
As long as there is something tiny it does not make much sense to install the rom as it's the wrong layout which will leave you with very little space to use.
So you will have to install the unification zip in TWRP.
If this fails CWM (1.) should help you out, first try if it can complete the unification - install unify_userdata from CWM.
If it reports the error 7 you will have to revert, to get rid of this error:
reboot CWM, factory reset, install restore_sdcard-xxx.zip, follow instructions, it will reboot itself. Afterwards reboot CWM again, factory reset, install unify_userdata, follow instructions, it will reboot itself.
Now unification should have succeeded.
Reboot into flashmode, flash twrp.img. Install the rom if storage has a reasonable value.
else try to fetch and tell what failed, the storage reported by the rom is calculated on the basis of a successful unification and therefore without any helpful information.

lobotron said:
this might mean a lot of flashing, I would try:
1.fastboot flash recovery-13.0-20161220-SNAPSHOT-ZNH5YAO3XM-hayabusa.img
2.in CWM factory reset
3. install restore_sdcard-xxx.zip, follow instructions
4. reboot recovery
5. install unify_userdata-xxx.zip, follow instructions
6. fastboot flash twrp-3.0.2-20170108-boot-hayabusa.img
in TWRP look for partitions, if all is fine install rom and twrp.zip
else start over from 1
Click to expand...
Click to collapse
That s work
Thanks sir

lobotron said:
some general clarification, in the hope I got it right:
The unification just changes the amount of memory available to the system and data.
The rom will be stored in system, so what you see in (for example):
TWRP -> Install-> select storage-> Internal Storage
is the amount the user might use for apps and general usage, system will not appear.Your Phone has 16GB I would expect round about 10000MB, it's a guess as I have a different model out of the same family.
As long as there is something tiny it does not make much sense to install the rom as it's the wrong layout which will leave you with very little space to use.
So you will have to install the unification zip in TWRP.
If this fails CWM (1.) should help you out, first try if it can complete the unification - install unify_userdata from CWM.
If it reports the error 7 you will have to revert, to get rid of this error:
reboot CWM, factory reset, install restore_sdcard-xxx.zip, follow instructions, it will reboot itself. Afterwards reboot CWM again, factory reset, install unify_userdata, follow instructions, it will reboot itself.
Now unification should have succeeded.
Reboot into flashmode, flash twrp.img. Install the rom if storage has a reasonable value.
else try to fetch and tell what failed, the storage reported by the rom is calculated on the basis of a successful unification and therefore without any helpful information.
Click to expand...
Click to collapse
Thanks sir, now unification is successful and I m enjoying LinageOS. Thank you very much

My Xperia TX LT29i don't wake up when it's idle for some time even power button don't do anything. I've tried both LineageOS and AOSP Nougat but I'm facing same issue. I've to remove battery each time which is very annoying.
Can anybody guide me to solve this issue?

[RECOVERY] [TREBLE] TWRP 3.3.1-0 with Tissot Manager

Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01

Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!

Reserved

Great work.
Sent from my Mi A1 using Tapatalk

Thanks ??

Nice. Bro you carried legacy ?

nice work waiting for shrp version of this ??

Noice :good:
Sent from my Mi A1 using XDA Labs

This is an update of TWRP Comic Dan?

manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op

Any way to flash it using cosmic dan's twrp? I don't have any pc now

Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.

Great job dude ?

Awesome work!
Thank you so much for this.

@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?

sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.

Where is the survival checkbox??

What is this "inject twrp" does ?

oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option

Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?

[ROM][OFFICIAL][enchilada][10.0]crDroid Android[v6.27]

{
"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"
}
​
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring many of the best features in existence today.
Features
A quick glossary and primer on slots for A/B devices (like ours):
Spoiler: Show/Hide
- "Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip (usually by either wiping or formatting data, see below).
- "Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
- "Wipe data": Synonymous with "factory reset", accomplished from TWRP recovery by selecting "Wipe", then performing the "Slide to factory reset". Clears user data without erasing any partitions, removing encryption, or deleting contents of internal storage.
- "Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
- "User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
- "OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system.
- Some partitions are duplicated (system, vendor, boot, and probably a couple others, but not data) and have a "slot A" & "slot B" copy.
- "Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
- Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" (and booted from) and "inactive" upon next reboot.
- The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
- You can install multiple OTA zip packages one after the other without rebooting in TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
Prerequisites:
- Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
- Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, with a known-good USB cable (see links in post #2).
- Make sure you've downloaded the most recent full Android 10 OxygenOS OTA installer zip (10.3.12), crDroid zip, matching crDroid boot.img, official TWRP 3.5.2_9-0 installer zip and bootable img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
- Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
Let's get started!
Updating firmware (if already on crDroid):
- Reboot to bootloader (with no USB cable connected).
- Open a terminal on your computer, and run `fastboot flash boot path/to/boot.img`, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites.
- Reboot to bootloader again (actually loads new bootloader that you just flashed).
- Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot into the built-in TWRP recovery. The device's internal storage should now be available for read/write on the computer via MTP.
- Copy the official OxygenOS 10.3.12 full OTA zip & latest crDroid zip into the device's internal storage, then choose "Install", select the current crDroid zip, choose "Add more zips", and crDroid installer zip, then swipe to confirm flash. No TWRP zip required, since it's built in to the boot.img that gets installed.
- Reboot recovery, then choose "Install", and select the OOS zip, then select "Add more zips" and choose the crDroid zip, and swipe to confirm flash again.
- Reboot recovery, and re-flash magisk/gapps if needed.
- Wipe dalvik.
- Reboot system.
First time installing crDroid to your OP6, coming from stock OxygenOS or another ROM (will also update firmware while we're at it):
- Reboot to bootloader, then `fastboot boot path/to/twrp.img` to start up into TWRP recovery.
- Mount System partition read-write, use file manager to delete the /system/addons.d/ directory if it exists, unmount System.
- Choose Wipe > Format data, type "yes" and hit enter to nuke everything in the data partition and clear encryption.
- Choose Advanced > ADB sideload (don't worry about selecting cache/dalvik wipe options yet) and then on the computer, do `adb sideload path/to/OxygenOSOTA.zip` to flash the OxygenOS 10.3.12 full OTA installation zip & make sure you're on the latest Android 10 firmware.
- Go get a drink, this'll be a bit.
- When that's done, hit "back" in TWRP and start ADB sideload again, and this time send the crDroid installation zip (includes TWRP built-in, so don't need separate zip for that at this point).
- Reboot to recovery (this will switch the active slot to use the system partition you just installed those zip files into).
- Wipe data (Wipe > "Slide to factory reset" in TWRP).
- That was so much fun, let's do it again! ADB sideload OxygenOS full OTA zip.
- ADB sideload crDroid zip.
- Reboot to recovery (switches slots again, now we have latest OxygenOS firmware plus crDroid populated in both sets of partitions and won't have to do that again).
- Flash Magisk (if desired).
- Flash GApps or microG package (if desired).
- Wipe dalvik.
- If you copied anything to internal storage instead of flashing it via ADB sideload, delete it now before first boot.
- Reboot system.
- Go through setup wizard.
- Reboot system (for reasons I don't comprehend, it never shows "OnePlus Settings" in the Settings app top level menu on a fresh install until after rebooting once).
- It's gonna harass you to finish setup, go ahead and customize everything to your heart's content.
Updating crDroid from TWRP (preferred):
You don't need to remove device protection; it works fine with PIN. Be sure you have a PIN set, or have looked up whatever that arcane chart of pattern > numeric incantations in case of pattern unlock. It's awful.
- Boot into TWRP recovery.
- Choose install, then select OOS firmware OTA (if needed), then choose select additional zips, then select crDroid.zip, slide to confirm flash.
- Reboot recovery.
- Choose install, then select Magisk zip (if using), select additional zips, choose GApps/microG (if using), slide to confirm flash.
- Please keep off of the grass, shine your shoes, wipe your... dalvik.
- Reboot system.
Updating crDroid from Updater app:
Warning: I don't remember if crDroid 6 even *has* the built-in Updater app function or not, or how well it handles addon.d survival scripts. Use with caution.
- Install update in built-in Updater app (Settings > System > Updater), do NOT reboot yet.
- Go to Magisk app home, click "Install" next to Magisk, and choose the "Install to Inactive Slot (After OTA)" method.
- For GApps/microG: If you use GApps/microG that needs to be re-flashed to /system (as opposed to magisk module GApps/microG), reboot *recovery* at this point, mount the system partition in TWRP, and dig around with the File Manager in system/priv-app/ & system/product/priv-app/ to make sure that everything you expect was copied over to the now-currently-active slot, and if need be re-flash your installer zip, or else your world will be pain when you boot normally. Yes, I expect you to know what your preferred package installs & to keep the zip handy.
- NOW you can reboot to system.
Reporting bugs:
I'm a parent of three young kids whose industry disappeared in the pandemic and is now full-time house husband & parent-in-charge while my wife is teaching full-time, I'm trying to save my small live-event-turned-streaming-studio company in my spare time. I'm doing in-home caregiving for a family member overnight one day a week. This is the back-up spare-spare-time hobby. I'm not a software developer nor do I know any programming languages, I just wanted a ROM with signature spoofing support and more customization than the unofficial microg-compatible LineageOS builds. So if there are bugs or feature requests, I go over to the crDroid dev chat and ask if someone has time to hold my hand & help. Don't make me get yelled for annoying them, mmkay? That said...
- Logs/screenshots/recordings or it didn't happen. Syslog (free, open source, available on Play store and F-droid) is your friend.
- I try to keep an organized notebook of roadmap, feature reqeusts, bug reports, etc. I won't always be able to fix it, but I'll at least look and do my best to ask the actual devs.
- I don't sign into XDA much, so if I haven't said anything, check out the Telegram group. Lots of helpful folks there.
- Please keep your questions in this thread instead of PMing me with them directly, so that the entire class can benefit from the discussion and you can find out if it's just you or if this is a widespread issue.
It's your device to use the way you want of course, and I use Magisk & microG and like to tweak things myself. But don't expect much support if you:
- didn't do a clean flash.
- aren't using the built-in kernel.
- are using extensive modifications (besides Magisk) like Xposed/Riru, Dolby Atmos, Viper4A, etc.
- immediately start using "finalize.zip" or flashing migrate restore zips instead of following the actual instructions.
- are running decrypted.
Donate - Support development!
crDroid Website - Download here!
Telegram Oneplus6/6t group - Share your best cat pictures!
Source Code:
- Device tree: https://github.com/crdroidandroid/android_device_oneplus_enchilada/tree/10.0
- OP6/6T Common device tree: https://github.com/crdroidandroid/android_device_oneplus_sdm845-common/tree/10.0
- OnePlus Common device tree: https://github.com/Terminator-J/crdroid_device_oneplus_common/tree/10.0-test
- Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845/tree/10.0

Notes:
- Yes it supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
- Aux camera doesn't work correctly due to framework issues beyond my control/comprehension. So, still no portrait mode in OnePlusCamera in cr6. But 60fps video recording in OOSCam works great; huzzah!
- Doesn't pass safetynet out of the box, despite many tests with different fingerprints/props. Just use Magisk & enable the Zygisk DenyList & kdrag0n's "safetynet-fix" module and be happy. If your bank's app doesn't work, switch to a local credit union and stop feeding the bougie bankers. Smash capitalism!
- Maintainer does not use GApps, so cannot answer questions about which packages work best from firsthand experience. In general, go with the smallest package you can and then install other Google apps from the Play Store. Please note that if you replace the stock dialer with Google Dialer, you may lose access to the Phone Info menu (*#*#4636#*#*) until you install another dialer. For recommendations, see https://wiki.lineageos.org/gapps.
- Requires OOS 10.3.12 OOS firmware.
- Includes built-in TWRP, pulled from official 3.5.2_9-0 ramdisk, works well.
- Tested against latest Magisk canary (with zygisk instead of magiskhide), works well.
- No there won't be official builds with inline GApps; please don't ask.
crDroid 6.27 - February 2022 ASB release notes/known issues:
Changelog since v6.23 release:
- Merged Android Security Bulletins through February 2022 from upstream.
- Whatever changed upstream in the ROM proper (not likely much; they want to freeze it besides security updates).
- Reimplemented DeviceSettings based on crDroid 7 version (no more greyed-out things that don't actually work in Android 10).
- Backported updated display panel handling in device tree and kernel to match crDroid 7 (panel color modes are in LiveDisplay now). FOD on fajita is still kinda crap with OOS 10 firmware, but oh well.
- Little more tidying/tightening in device tree & kernel for moving to maintenance-only releases.
- Imported current wireguard VPN kernel-mode driver.
Known issues:
- Some screen-off gestures may not work, due to limitations beyond my control; don't use those gestures. Sorry.
- You tell me! With logs!
Other stuff:
- At this point, any little feature bugs will be considered "can't fix/won't fix"; I can't keep working on this one, I'm going to try to only do security-update-only releases of crDroid v6.
- Where do bad rainbows go? Prism. It's a light sentence.
Helpful links:
Download ROM
TWRP (use old official v3.5.2_9-0)
(TWRP is built-in to the crDroid 6 zip, but you might need the img or standalone installer zip in order to get to that point)
Magisk (use latest)
OxygenOS 10.3.12 Full OTA
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade)

Thanks dev. This is a great ROM
When you say latest fw, you are talking about OOS Pie or H2OS Q?

firebird11 said:
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:
To be defined
First time installing crDroid to your Op6, or coming from another ROM:
- Be on the latest firmware
- Make sure you're running latest TWRP
- Copy GApps and crDroid zip to your internal storage
- Disable your screenlocks
- Boot into Recovery
- Wipe cache,data
- Flash crDroid zip
- Flash TWRP zip
- Reboot to recovery
- Flash GApps zip
- Flash Magisk zip
- Reboot system
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such as Xposed!
- have modified system files
DONATE
crDroid Website
Telegram Oneplus6/6t group
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 6
Contributors
firebird11, neobuddy89, gwolfu
Source Code:https://github.com/crdroidandroid
Source Code Kernel:https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LOS
Version Information
Status: Testing
Created 2019-10-16
Last Updated 2019-10-16
Click to expand...
Click to collapse
Any bugs or something not working?
Will try this weekend.

Thank you dev

Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.

veronesi.n said:
Hello, I flashed rom yesterday.
I've got 1 issue. Fingerprint unlock doesn't work. I mean fingerprint sensor works because I can set up a fingerprint. But when phone is locked (screen on or off) I can't unlock it.
Maybe this is Gapps related? (I used Nano beta from october). Not rooted
Rom is fast and responsive. No other bug/ lag or freezes so far.
If anyone can help me with fingerprint unlock it would be much appreciated.
Have a nice day.
Click to expand...
Click to collapse
Same here, I think new magisk 20 breaks it , because with 19.4 working fine

savinjo22 said:
Same here, I think new magisk 20 breaks it , because with 19.4 working fine
Click to expand...
Click to collapse
Sorry I said not rooted ?... I wanted to say that magisk wasn't installed.

i tryed this rom on my htc m8 and i love it and i will try it again on oneplus 6

Is this also implemented already in android 10? TIA

tiga016 said:
View attachment 4847745
Is this also implemented already in android 10? TIA
Click to expand...
Click to collapse
Yes there's some customization settings.

dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?

backtrack292 said:
dev i tried to flash this rom but it says failed because the file for oneplus 5 not oneplus 6 could you check the download link?
Click to expand...
Click to collapse
I assume you used the 'Green Box' link in Sourceforge? That always trips people up. That link is the latest ROM across all crDroid devices. (Currently the OP5 'Cheeseburger') Or next time actually read the file name before flashing.
Ignore that Green Box. Just pretend it doesn't exist. Use the links underneath to get the Enchilada downloads.

a new v6 build is up !
october security and statusbar padding are new

firebird11 said:
a new v6 build is up !
october security and statusbar padding are new
Click to expand...
Click to collapse
does it supports signature spoofing?

just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!

What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
ewong3 said:
just tried moving from havoc 2.9 (pie) to crd6 (q), but unfortunately at this point no twrp can handle Q OOS flashing (to bring firmware to up to Q levels), latest available twrp is Mauronofrio's 3.3.1.4 so if anyone succeeds in flashing stock followed by CrD6 on a later/another twrp, would love to hear the success story...
for now, someone suggested only a local upgrade route within ota, but you end up without a functioning twrp environment which is probably too much hassle for most, so we will wait on the sidelines for a bit longer.
hope this helps!
Click to expand...
Click to collapse
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041

meistr91 said:
What the latest fw is required pie or Q beta 1?
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
There is a way to have a twrp on open beta 1.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-update-to-android-10-beta-1-twrp-t3987041
Click to expand...
Click to collapse
thank you for the suggestion... gone well beyond the link's status by the time i read this (on oos from local update), so may just wait it out for a working twrp solution - been too long since last used OOS anyway!

new v6 builds are up !

firebird11 said:
new v6 builds are up !
Click to expand...
Click to collapse
Can be flashe with oos 10 base ?

[ROM] [Xtended] [Unofficial] [A11 October 1 2021 Security Patch] For S9 and S9 Plus [Exynos]

I am not responsible if you brick your device installing this ROM, you are installing this at your own risk.
Downloads
Mod Edit: DL links removed.
Create device backup first:
1. 1. Boot TWRP/OrangeFox by pressing Bixby+VOL_UP+PWR as you are booting your device.
2. Go tho the backup tab of TWRP/OrangeFox
3. Backup Data, System, Cache, Boot, and System Image
4. Then backup the TWRP/Fox folder on your device to your computer just in case anything goes wrong.
How to install:
1. Boot TWRP/OrangeFox by pressing Bixby+VOL_UP+PWR as you are booting your device.
2. Go do the wipe tab of your recovery of choice, and wipe; DATA, CACHE, SYSTEM, and DALVIK CACHE.
3. Then flash the ROM you copied over to your device, or flash the ROM via ADB, it is up to you.
Reboot and enjoy!
Credits:
Thanks to the arrow-devices github community for the device sources for the S9 series of devices: Their Github Page
Samsung vendor (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Galaxy S9 Plus device tree
Galaxy S9 device tree
Galaxy *9 Series kernel (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Galaxy *9 Series common tree (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Huge thanks to Baddar90 for fixing the battery drain issue this rom was having.
The fix source code: here
His Github: here
Gapps: (credits of the Flame Gapps Team. (Their website)
1.To flash Gapps first download Flame Gapps from here (full gapps package), here (basic gapps package)
2.Then boot TWRP/OrangeFox with the above method.
3. Find the Gapps zip you downloaded, tap on it, and swipe to flash.
4.Reboot and you should have Gapps!
How to get the out of box google setup experience when flashing Gapps (recommended):
1.After flashing the ROM reboot the device once to make sure the ROM boots.
2. On the home screen enter the power menu and then tap on "Reboot" then "Recovery.
3. Once your phone is in the custom recovery of choice, wipe the data partition.
4. Then flash Gapps again.
5. Reboot and you should have access to the the Gapps out of box setup experience!
For those of you who want to use MicroG I will not be covering it here. But the NoGoolag Telegram group as well as r/Privacy on Reddit should be able to help you if you would like to take that route.
r/privacy
NoGoolag Telegram Group
Other Telegram Groups:
(If you would like a Kernel that can help improve battery life you can ask about it here)
P.S Xtended is a great ROM, but it does have a few more bugs than other custom ROMS may have. Not enough to cause any issues but enough for you to notice the occasional hiccup here and there. This ROM is great for people who like A LOT of customizability though. By the way, bur is alos broken to and their is nothing I can do about that sorry. I'd recommend going to Display-Enable Blurs, and toggle it to off. After a device reboot at least you will get some transparency.
I hope you like it!
Also tell me if the ROM works on your S9 Plus as I can then remove that "Untested" badge from it.

Thread closed.

[GUIDE][Install Treble][Only 9.0] Coolpad-LeEco Cool1

Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Instructions for installing Treble-firmware Android 9 based on the vendor from 11/12/2019 for EUI markup.​
1. Install Recovery specifying the vendor section.
1.1 Download: "TWRP_VENDOR1".
1.2 We go into our Recovery - Installation - Installing img - Select the downloaded file - Install as Recovery.
1.3 Reboot in Recovery.
2. Installing a patch that changes the markup and creates a Vendor section.
2.1 Downloading: "repart_vendor".
2.2 Install the patch through Recovery - Reboot in Recovery.
2.3 Go to Cleaning - Selective cleaning - everything is selected except Device memory and cleaning.
3. Restore Vendor and Boot.
3.1 Download the "boot_vendor".
3.2 In the archive from the folder BACKUPS\9ba6452 we take the Folder 2019-11-12--03-11-24_aosp_c106-userdebug_9_PQ3A190705003_0fd956d and put it in TWRP\BACKUP\Folder with tricky code\
3.3 Recovery - Select backup 2019-11-12--03-11-24_aosp_c106-userdebug_9_PQ3A190705003_0fd956d - restore - Boot and Vendor must be checked.
4. Select the desired firmware (type ARM64 A (or A only)) in any available place Link Link2
4.1 If the downloaded firmware is in the archive, unpack it to img.
4.2 Installing img - select the downloaded file and install it as System image.
4.3 Reboot in Recovery (May write that the system is not installed, do not pay attention).
4.4 Install the patch "fix_gsi_r1".
4.5 Install Gapps if needed.
4.6 Reboot into the system.
4.7 If there is no sound - put a patch "sound+treble+final".
4.8 If there is no network, reboot into recovery and repeat step 4.4 again.
4.9 If you don't like the color saturation in Gcam - put a patch "video_play6".
• This manual is designed for installation using a PC, if you do not have a computer, download all the files in advance.
• Format data is not necessary, all data will be saved.
• Not all gsi are equally useful and bug-free.
• This instruction is not suitable for installing ported GSIs such as Miui, Flyme, ColorOS, etc.
Patch for rollback, for the 6th markup "restore_6"
The new kernel is based on 11 sources, in an attempt to run 10-11 gsi: "image-new"
10-11 gsi hang on a bootlogo, maybe someone can fix it.
You do everything at your own peril and risk. I am not responsible for bricks.
Source code
Discussion
Big Thanks:
Ampir-nn