Develop Bugs

How to install Xposed Framework on the Huawei GX8/G8.

I was curious to know to how xposed framework can be installed on the Huawei GX8 so I went through different sites to find at least an easy way to do that but honestly i didn't find any easy steps. They are more or less complicated depending on the individual attempting the procedure. ok
It is advised to take complete backup before deodexing so that you can replace the deodexed apps with the odexed backups in case you face some Apps crashing. Deodexing is important in order to make xposed framework install successfully and use some modules as well.
Warning: You attempt this procedure at your own risk, bare in mind that I will not be held responsible if you brick your device for attempting this procedure.
Prerequisites:
Rooted device.
Fully functional TWRP recovery or any other recovery with File manager support.
Backup all your data & apps.
Download this APP for deodexing:https://docs.google.com/uc?id=0BwSanb5zBfFiaHN5MGV2ZnFqcVU&export=download
Deodexing the ROM:
Step 1: Extract the BatchAPKTool to your preferred location.
Step 2: Open BatchAPKTool.exe. Set Language to English when prompted.
Step 3: The tool will now ask you to chose task.
Step 4: Type 83 and set smali version to smali-2.1.2.jar by entering 2. Now type 84 and set Android API level to 21 (Android 5.0), 22 (Android 5.1.1) or 23 (Android 6.0). This value must match with the firmware you have currently installed on your device.
Step 5: Now connect your device to PC. Make sure USB Debugging Mode is enabled and necessary Huawei Drivers are installed.
Step 6: In BatchAPKTool window, type 13 and then enter 4. This will pull all files from /system/app , /system/framework , /system/priv-app from your device. This may take some time so wait patiently. (You might also do it manually using Root Explorer)
Step 7: Once it’s done press Enter to return to main BatchAPKTool Menu.
Step 8: We’ll now deodex the apps. Enter 01 in the tool. It will now ask you for your ARM version. Enter “arm” and press Enter. Wait for the process to be completed.
Step 9: In the directory where you have extracted BatchAPKTool, you’ll find three folders named _priv-app, _app and _framework. Remove the underscore from the folder names so that they are now priv-app, app and framework respectively.
Step 10: Create a new SYSTEM FOLDER and name it DEODEXED SYSTEM and copy those three folders inside it. Now copy the System folder to your SD card or Internal Memory.
Replacing Odexed Apps with Deodexed Apps:
1: Boot your device into recovery and backup System partition
2: Using the built in file manager in recovery, delete the app, framework and priv-app folders from your system partition.
VERY IMPORTANT: Make sure that in twrp in the "Mount" section the "Only mount system read-only" is unchecked in order to copy the files to system.
3: Now copy the app, framework and priv-app folders from system folder (which we copied to SD card or Internal) and paste them to the SYSTEM partition i.e. /system/
4: When done, reboot your device. First boot will be extremely long. Might take 20-30 minutes so be patient.
ALTERNATE METHOD:
NOTE: It may not be possible to copy files from one folder to another in recovery mode, so this is what i did...
1. Create a NEW FOLDER in your internal memory and name it ORIGINAL SYSTEM.
2. Copy PRIV-APP, APP and FRAMEWORK from the ORIGINAL SYSTEM FOLDER and paste it in the ORIGINAL SYSTEM FOLDER in the memory of your device.
3. Now copy the THREE files in the DEODEXED SYSTEM FOLDER to the ORIGINAL SYSTEM FOLDER in the root of your device.
4. Your device will reboot immediately the files are copied. The boot may take 20-30 minutes so be PATIENT..
Installing Xposed Framework.
1. Go to the official thread and download the latest version(xposed-v86-sdk23-arm64) for Marshmallow
2. Download the apk and the uninstaller arm zip just in case anything goes sideways you can flash the uninstaller to unistall xposed framework.
3. Install the apk file and flash the v80-sdk23-arm zip in recovery. Again device might take 20-30 minutes to boot.
4. For Android 6.0:
Open build.prop
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
For Android 5.0-5.1.1:
Open local.prop (in system/emui/base/prop/local.prop)
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
The commands is to ACTIVATE the framework.
Thanks to mfbcool for the guide and Rockchip for Batch tool.

OK I have successfully installed xposed installer and some xposed modules, however some of the modules seem not to be working.

Partially working modules....
N-ify
Not working.......
Gravitybox
Lockscreen Mods
Qs tiles per row
xnotifications
Working.......
YouTube Adaway
Greenify
Maxlock
Flat Style Bar Indicators
Jit Screen On

Has anyone tried this method and had some success .....?

Ok. I'm now on cyanogenmod so I will be releasing xposed modules that are working perfectly on the rom. Stay tuned.
Its been a while. Yeah, have been busy with school and work.
Ok, here's a list of xposed modules working flawlessly with cyanogenmod.....
Gravitybox MM
Flat Style Bar Indicators
Android N-ify
Blurred System Ui MM
ifont
Youtube adaway
Maxlock
USB for Marshmallow
Adblock
Greenify
The list will be updated with time. If I helped you in any way, don't forget to hit the like button... Thanks
Sent from my HUAWEI GX8 using XDA Labs

Good joob BRO

bro i have LAG after install xposed its work 100% but there is some lag in apps

Ahmed-Iraq said:
bro i have LAG after install xposed its work 100% but there is some lag in apps
Click to expand...
Click to collapse
Sorry for the late reply....which apps are you experiencing lags with???
Sent from my Nexus 6 using Tapatalk

[DEBLOAT] Wileyfox Debloater - Quickly clean your Nougat-based Wileyfox device!

Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!

I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...

rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there

I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source

Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT

rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.

Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.

linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT

MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions

linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/

MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.

linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?

MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse

linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?

MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!

Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change

I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?

Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly

If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?

digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?

[O] [G8141] [G8142] 47.1.A.12.179 Xposed patched rom, lightly debloated

version 2 out now~~~
After researching the framework info, I found out MEA G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=11050483647474827606
(version 2, replaced google apps, more debloat, more stable system)
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
3.4 install keyboard
https://androidfilehost.com/?fid=818070582850495399
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot

Where is the build.prop file?

amakuramio said:
currently uploading! done in few hrs
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download ANY G8141 or G8142 ROM that is 179 version, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get force close
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. recover my system backup using twrp, for g8142 you have to follow step 4
uploading currently, isdone within 15 mins
to recover, simply make a backup of anything, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files 2, 3, 4, xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.

Blackghosthm said:
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Click to expand...
Click to collapse
on wifi I get 8 hrs to 8.30
on 4g, drains very fast
but newer versions are faster (after march, sony use 8.1 compiler for faster apps)
its 89% upload
its also possible that I combine system from 179 with turbo rom 75, it should be compatible and easy to do.

jianlin3062 said:
Where is the build.prop file?
Click to expand...
Click to collapse
the build.prop file is in ''root/system/build.prop'' I use notepad++ to edit it on pc then push it back to the phone
twrp file manager, copy build.prop to sd card, copy to pc, replace maple with maple_dsds and g8141 with g8142, its easy to do

1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...

saved-j said:
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
Click to expand...
Click to collapse
you did something completely wrong
backup your data (if you want, prefer clean) flash a 179 stock firmware erase all otherwise force close, then restore my system, then flash the 4 zips, reboot after the first one, then flash last 3 zips I posted in the link up there, then xposed, then reboot
I really have 0 problems here. I thought I kept swiftboard in it? hmm. I will make a patch zip with keyboard in it, hopefully it helps. you can also push a keyboard app in system/app/Appname/app.apk 0644 permission
https://www.apkmirror.com/apk/swift...swiftkey-beta-7-0-8-363-android-apk-download/
can you do me a favor? make a screenshot of the system app scroll down, then send me. Maybe I uploaded wrong system?

do you can xposed patch on turbo final v2 rom?
it stucked.

amakuramio said:
you did something completely wrong
Click to expand...
Click to collapse
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Also am gonna try:
-AndroPlusKernel 12 -
-Magisk 16.4 (instead of 16.0) -
-OpenGapps (instead of included) -
-Magisk-Systemless-Xposed (instead of flashing /system included) - works either way

saved-j said:
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Click to expand...
Click to collapse
pushing a keyboard into the system will also help, but that is the way to do it, yes
do you have g8141 or g8142? google play issue is related to not updating proper build prop to your device

amakuramio said:
g8142
Click to expand...
Click to collapse
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.

lGIKDk said:
do you can xposed patch on turbo rom?
Click to expand...
Click to collapse
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.

saved-j said:
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
Click to expand...
Click to collapse
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
https://www.apkmirror.com/apk/googl...2-8-66-090400-200774163-android-apk-download/
GmsCore.apk with permission 0644
same with phonesky
https://www.apkmirror.com/apk/googl...6-08-all-0-pr-200628961-android-apk-download/
then reboot with dalvik and cache removed (2 things only) there may be LIB compatibility issues.
Hell if google play doesnt work for g8142, I can also do nanomod! which is very light on the battery
nanomod needs xposed, but it works with xposed, so

amakuramio said:
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
Click to expand...
Click to collapse
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
amakuramio said:
Hell if google play doesnt work for g8142
Click to expand...
Click to collapse
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC too. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
*trying one more time while you're thinking*

saved-j said:
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
Click to expand...
Click to collapse
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
1. in xposed install http://repo.xposed.info/module/com.thermatk.android.xf.fakegapps (do this first, just enable it, dont reboot in recovery yet)
2.delete the following
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
/system/app/GoogleAnalyticsProxy/GoogleAnalyticsProxy.apk
/system/app/GoogleExtShared/GoogleExtShared.apk
/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
/system/priv-app/GmsCore/GmsCore.apk
/system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk
/system/priv-app/GoogleExtServices/GoogleExtServices.apk
/system/priv-app/GoogleFeedback/GoogleFeedback.apk
/system/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
/system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
/system/priv-app/Phonesky/Phonesky.apk
3. then flash nanodroid https://downloads.nanolx.org/NanoDroid/Stable/ then reboot. you might want to go options of google play then clear data afterwards.
(4. extra, see if settings folder in app is same permission as other folders, and if apk inside is also same as other apk in the different folders)

cant google login. it just black screen

amakuramio said:
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
Click to expand...
Click to collapse
The difference between them is minimal. Somehow it worked for me with OpenGapps. I'll set the phone up and leave it as it is, as it's 4:00 am already. I'm glad it worked somehow.
I'll test it during the week, though i've already found several issues, like, in Album app it doesn't allow to move from the internal memory to the folders on the SD card already existing (don't know why?? - Google Photos app does it with no problem)
lGIKDk said:
cant google login. it just black screen
Click to expand...
Click to collapse
Did you read the conversation here before posting your message? You're not alone in this problem.
Try flashing .179 again, with all the wipes, etc - following the instruction.
And flash Open Gapps right before you boot up in the system. It has JUST worked for me when I tried it in the last time, though it hadn't worked for me yesterday!
Active Screen, XZ2 Camera and some other XZ2 features, Xposed, WiFi, data, everything works just fine.
Had to spend two nights to achieve it, though.
Attaching a video of working Xposed. My device recognizes as Pixel XL because I have a Daydream Enabling magisk module.

amakuramio said:
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
Click to expand...
Click to collapse
ok. i wait.
i hope completly version

amakuramio said:
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=674106145207498283
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).

Blackghosthm said:
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Click to expand...
Click to collapse
though the rom is made by sony I got it from MEA version from XPERIFIRM and modified by me I did include HIS xposed fix (not directly).
What I did copy was the framework intents those are the same as his. If I modified framework myself and installed his xposed then because of mismatch the whole thing would crash so I had to force the same intents to match the signature.

Local Upgrade for Rooted Users

Hi All. Just thought I'd quickly mention the method of updating OOS if you are rooted for anyone new to this or to anyone who's forgotten.
Disclaimer: This works for me, I've just done it. Backup your phone just in case. I'm not responsible for your actions or the consequences of your actions. You merely adopted the dark, I was born into it etc etc.
Process:
1- Disable or uninstall all Magisk modules and Overlays (Substratum etc). Otherwise you may end up in a bootloop.
2- Download the FULL version of the ROM (it will be around 2gb). Make sure it's the correct version for your device/region. (eg Global, EU, India etc).
3- Move the downloaded file to your internal storage (root directory).
4- Open the system update app under Settings -> System -> System Updates.
5- Select the cog icon at the top left and select Local Upgrade.
6- Choose the file you've downloaded and let the phone update.
7- DO NOT REBOOT!
8- Open Magisk Manager and select Install (for Magisk not Magisk Manager)
9- Select Install and on the next popup screen make sure you select Install to Inactive Slot (After OTA).
10- Reboot after Magisk has installed
11- Profit :good:

Works great as usual. Thanks.
bowlandspoon said:
Hi XDA peeps. Just thought I'd quickly mention the method of updating OOS if you are rooted for anyone new to this or to anyone who's forgotten.
Disclaimer: This works for me, I've just done it. Backup your phone just in case. I'm not responsible for your actions or the consequences of your actions. You merely adopted the dark, I was born into it etc etc.
Process:
1- Download the FULL version of the ROM (it will be around 2gb). Make sure it's the correct version for your device/region. (eg Global, EU, India etc)
2- Move the downloaded file to your internal storage (root directory).
3- Open the system update app under Settings -> System -> System Updates.
4- Select the cog icon at the top left and select Local Upgrade.
5- Choose the file you've downloaded and let the phone update.
6- DO NOT REBOOT!
7- Open Magisk Manager and select Install (for Magisk not Magisk Manager)
8- Select Install and on the next popup screen make sure you select Install to Inactive Slot (After OTA).
9- Reboot after Magisk has installed
10- Profit :good:
Click to expand...
Click to collapse

Don't forget to disable or uninstall all magisk modules and overlays (Substratum etc). Otherwise you can end in a bootloop.

xx00xx1990 said:
Don't forget to disable or uninstall all magisk modules and overlays (Substratum etc). Otherwise you can end in a bootloop.
Click to expand...
Click to collapse
Thanks, will add this to OP.

FLAWLESS PROCESS! Thank you!
Sent from my IN2025 using Tapatalk

Just because the "uninstall all magisk modules" seemed to be something passed from long time ago, I tried without touching the modules at all. Booted just fine. Feel free to not disable any modules and try that way. Will save you time

Cubox. said:
Just because the "uninstall all magisk modules" seemed to be something passed from long time ago, I tried without touching the modules at all. Booted just fine. Feel free to not disable any modules and try that way. Will save you time
Click to expand...
Click to collapse
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation

pyry666 said:
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
Click to expand...
Click to collapse
First of all, I'm not spreading misinformation. I'm just telling about my experience. Any user who has a bootloop after upgrading without disabling modules can easily remove them from recovery (after flashing the one with adb enabled). This step to disable all modules is not mandatory for everyone and will make you waste time for nothing.
Second, if the argument is that because some users might get a bootloop, why not just do a data wipe every time you upgrade as well? Being overly cautious can be useful in some situations, but not here. If you get a bootloop, you can fix it easily. If you don't, you saved 10-20m from your life reinstalling everything.

pyry666 said:
And just because your modules didnt cause bootloop everyone elses dont either? Dont spread misinformation
Click to expand...
Click to collapse
This has happened to me on several different devices. I never do an update without disabling my magisk modules.

I've done this 4 times now with zero issues:
Take system update from OnePlus in settings and install as well.
Don't reboot
Reinstall magisk on main slot, then inactive slot from inside the magisk app.
Reboot
That's it.

My 2 cents. The Call Recorder module has been the culprit of the bootloop in my experience.

I had bootloop using these steps bellow:
1- Disabled all Magisk modules.
2- Downloaded the FULL version of the ROM (around 2gb).
3- Used Local Upgrade.
4- Waited and let the phone update.
5- I did not reboot
6- Opened Magisk Manager and Installed it to Inactive Slot
7- Rebooted
8- Worked everyting ok after reboot (root persisted)
9- Reenabled magisk modules
10- Rebooted
11- BOOTLOOP
12- I disabled all modules via TWRP and then system booted correctly.
13- Uninstalled all modules and installed them again.
I had the Call Recorder module so I may cause the bootloop. I think the safest method is to uninstall all modules before update and then install it again after successful update

<3
Just wanted to say, thank you so much for this guide

[ROM][13.0_r43][Official]crDroid Android[v9.5-r2][May 2023 ASB]

{
"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"
}
*** Disclaimer ***​I am not responsible for any damage you cause to your device.
I hope you like reading.
You have been warned.
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 you many of the best features in existence today.
​Features:​General:​See our current feature list at our GitHub!
Device-specific:​
OnePlus Camera & Gallery fully working (using APKs directly from OOS 11.1.2.2 or apkmirror.com with verifiable signatures; currently shipping OnePlus Camera v3.14.40 and OnePlus Gallery v4.0.297); including 60fps video recording in 1080p & 4K, watermark, depth effect, smart content detection, actually-working HDR, et al.
DeviceExtras for OnePlus-feature-specific customizations including alert slider modes, DC dimming, High Brightness Mode including customizable Auto-HBM threshold, customizable rendered FPS overlay, digital earpiece/mic gain controls, built-in UI jitter test, and 3-category vibration strength control (thanks to AnierinBliss for all his work on this implementation).
OnePlus-style color modes available through LiveDisplay (6 & 6T have slightly different implementations and you may not notice a difference, but think of "Natural" and "Wide Gamut" like uncalibrated versions of "sRGB" and "DCI-P3").
Ongoing kernel tuning (trying to get the best of both worlds tuning existing QTI perfd & scheduler & lmk, rather than cutting over to Google libperfmgr/powerhints/userspace lmk, definite improvements over vanilla LOS, mostly importing/adapting work by EdwinMoq and mcdachpappe).
Upstreamed updates from 4.9-q branch of Android common kernel for 4.9 LTS (merges courtesy of BananaFunction).
Everything you never wanted to know about slots & A/B devices (but have been forced to find out):​
Spoiler: Show/Hide
"Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip by formatting data.
"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": This used to be synonymous with "factory reset" in TWRP, without formatting the data partition and losing the contents of internal storage. Now, with TWRP being deprecated and using built-in LineageOS-based recovery, "wipe data" and "factory reset" mean the same thing as "format data" (which means, everything in internal storage gets erased).
"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. Is always installed to the currently "inactive slot", and will trigger a slot switch upon the next reboot.
Some partitions are duplicated (system, vendor, boot, and 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 "inactive" upon next reboot; causing it to attempt to boot from the formerly-inactive slot's boot partition.
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 both the stock recovery and 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.
We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, vbmeta, and now vendor as of Android 12. If you are planning on going back to an Android 11 ROM that does not build the vendor partition from source (so everything except SyberiaOS, essentially), you'll need to flash the OOS stock vendor partition to both slots from fastboot before installing the OTA zip.
"Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). We finally got a source-built vendor bringup for OnePlus SDM845 (enchilada & fajita) as part of the Android 12 (lineage-19.1) bringup, so some things work better, and some things work worse, but at least it's possible to fix things and keep moving forward to newer Android versions. However, since we're still dependent upon at least SOME binary blobs copied over from OxygenOS 11.1.2.2, the vendor patch level will remain at the release date for the last release of OOS 11, because we can't know for sure that some component isn't vulnerable, no matter how new all of the source-built components are.
"Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system & vendor partitions in custom ROMs for our device are generally built against a particular version of OxygenOS; in this case OOS 11.1.2.2 was the final release by OnePlus before they announced the end of support & updates for the OnePlus 6 series. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than 11, that doesn't matter when you're talking about installing this custom ROM over it. So please; update to OOS 11.1.2.2 firmware (see instructions below).
Notes on stock recovery & TWRP:​
Spoiler: Show/Hide
TWRP is deprecated & unsupported, for purposes of bug reporting & getting help with crDroid. I liked it personally, and I agree with all the reasons for wanting to try and keep using it; but the source has been described as a hot mess, the official releases for enchilada & fajita have not had good compatibility with Android 12 or newer (trouble with decrypting file-based encryption for userdata), and there are too many variations & unofficial TWRP-based recoveries for me to keep track of.
Meanwhile, the stock crDroid recovery (based on LineageOS) intentionally cannot decrypt userdata, and doesn't correctly process addon.d OTA survival scripts on A/B devices; so after using it to flash any OTA zips, you'll need to reboot to recovery and manually flash things like Magisk or GApps installers. But for all those shortcomings, it has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot") that lets you flash one image to both slots at once with a single command, and unlocks critical partitions... while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "proper" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"), and 3) gets the updater to call backuptool correctly & process addon.d OTA survival scripts on A/B devices. But they're not going to, and since crDroid is LineageOS-based; it's what we've got, and fastbootd is the best way to update firmware.
The takeaway: If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that; it's an unsupported configuration.
For purposes of doing updates, plan on doing your initial installation from bootloader & recovery then applying subsequent system OTA updates using the built-in Updater tool (Settings > System > Updater), both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk canary for several versions, and MindTheGapps & NikGapps on my tester fajita and MinMicroG "system" install package on my daily driver enchilada.
The built-in recovery DOES support use of a USB thumb drive and will mount it in OTG mode, so any place in the instructions you see "adb sideload", you can instead copy all your things to a FAT32-formatted USB stick and then apply the update from there instead.
Flashing Instructions:​Pre-installation prerequisites:​
Spoiler: Show/Hide
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, USB drivers, and a known-good USB cable (see links in post #2).
Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.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.
If you don't KNOW you already have OOS 11.1.2.2 flashed to BOTH slots, follow the "Updating Firmware" instructions below. You may also want a utility like 7-zip in order to extract .tgz files under Windows.
Updating Firmware:​
Spoiler: Show/Hide
Reboot phone to bootloader (no USB cable connected until you've entered OEM bootloader).
If you're not already using the stock crDroid recovery, you'll need to 'fastboot flash boot path/to/boot.img' on the computer, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites listed above.
Reboot to bootloader again (actually loads new bootloader contents that you just flashed).
Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery.
Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/enchilada/fw_update or https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ('fastboot reboot').
If you're only updating firmware and were already on crDroid, you can just 'fastboot reboot' which will go back to booting the system normally. If this is part of coming to crDroid 9.x from another ROM, continue with the first-time installation instructions below.
First-time installation:​(when coming from any other ROM or stock OOS or crDroid 8.x or earlier)
Spoiler: Show/Hide
*Back up anything you want to keep from the phone's internal storage to your computer/cloud storage, because we're going to format the userdata partition in this process.*
Download boot.img & rom zip to computer.
Reboot phone to bootloader.
Flash boot image to both slots ('fastboot flash boot_a boot.img' then 'fastboot flash boot_b boot.img').
Reboot phone to bootloader.
Use vol +/- keys to select recovery mode & press power button to enter recovery.
On phone, choose "Apply update" > "ADB sideload" & then from computer, 'adb sideload path/to/rom.zip' (substituting the actual path to the actual filename) to sideload the installation zip; the orange recovery header graphic will disappear until the process has completed ("error" messages like "no error", or finishing at 47% on the computer are normal).
On phone, choose "Factory reset / Wipe data", and confirm (note: this will erase everything from the phone's internal storage; make sure that you have backed up anything you want to keep first!). If you want to try out f2fs as a filesystem for userdata, give it a shot. It should be stable. If you don't know, just pick ext4; that's what we've been using forever.
On phone, choose "Advanced" > "Reboot recovery" to reboot into recovery on the newly-flashed slot.
Use adb sideload to flash GApps or microG installer zips (MinMicroG installer requires you to choose "Advanced" > "Mount/unmount system" first, others might as well).
Reboot into system.
If you want to root with Magisk, complete the initial first boot setup, then reboot the phone back into recovery, choose "Apply update" > "ADB sideload", and then from the computer, 'adb sideload path/to/latest_magisk.apk' to flash Magisk, and reboot back to System afterwards.
???
Profit!
Update installation:​
Spoiler: Show/Hide
Use the built-in Updater ("Settings > System > Updater") to apply OTA updates as they become available, or to manually flash a ROM zip by going to the three-dot menu in the upper right and choosing "Local update". Seriously, that's it; it processes addon.d survival scripts correctly, including Magisk, MindTheGapps, NikGapps, MinMicroG, and presumably others.
If you must update from recovery, then be aware that the stock crDroid recovery does NOT process addon.d OTA survival scripts correctly on our non-dynamic, non-virtual A/B system-as-root device, so you'll need to do the following:
Reboot phone to recovery.
Choose "Apply update > Apply from ADB" on the phone, and 'adb sideload path/to/installation.zip' from a terminal on the computer (or use a USB drive with appropraite files copied to it and choose OTG as the update source instead).
After installation has completed and the menus have reappeared on the phone, go back, then choose "Advanced > Reboot to recovery" on the phone.
Choose "Apply update > Apply from ADB" on the phone, and 'adb sideload path/to/installation.zip' for each addon like Magisk or GApps installation zip you need in order to match what was initially installed on the phone.
Reboot system.
Please see post #2 for current boot.img files, information about Google apps & microG, release notes, installation notes, known issues, and lots of helpful links.
Please see post #3 for information about bug reporting & troubleshooting.
​Sources:​ROM:​https://github.com/crdroidandroid
Device trees:​https://github.com/crdroidandroid/android_device_oneplus_enchilada
https://github.com/crdroidandroid/android_device_oneplus_fajita
https://github.com/crdroidandroid/android_device_oneplus_sdm845-common
https://github.com/crdroidandroid/android_hardware_oneplus/tree/13.0-op6
Kernel:​https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
Vendor-specific:​https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_enchilada
https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_fajita
https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_sdm845-common
https://gitlab.com/crdroidandroid/android_vendor_oneplus_apps
https://github.com/Terminator-J/vendor_ih8sn
Download:​ROM:​https://crdroid.net/enchilada/9
https://crdroid.net/fajita/9
Changelog:​https://crdroid.net/enchilada/9#changelog
https://crdroid.net/fajita/9#changelog
Links:​Visit the official website at crDroid.net
crDroid OnePlus 6/6T Telegram Group
crDroid Community Telegram Group
crDroid Updates Telegram Channel
Donate to help our team pay server costs (PayPal or Patreon)
Donate to support me in maintaining this device (PayPal or Patreon)

crDroid 9.5-r2 - May 2023 ASB release notes/changelog: ​Changelog since v9.5 (03 June release:
Device trees/hardware/kernel/vendor changes pulled from LineageOS.
Still May 2023 ASB, since the June security bulletin requires merging QPR3, which the ROM team is currently working hard at finishing.
crDroid:
I managed to re-add independent Battery Styles for QS shade compared to statusbar (and battery estimate if you have "turbo", Google's DeviceHealthServices) installed. Enjoy it while it lasts; everything will be ruined again with the QPR3 merge here in a bit.
At least a couple things I'd imagine, I dunno. Haven't been paying attention because I'm always a month behind.
Device-specific:
Updated kernel commits from bananafunction's lineage-20-test branch & upstream LineageOS lineage-20 branch.
Dropped ZRAM writeback (meh, less thrashing on the flash storage pls).
Dropped a few more of the overly-ambitious changes from 9.5 that didn't seem to actually do much, except make it a little more battery-hungry. I think battery life is back where we want it to be.
Re-added the "squash revert" commit in kernel to help with some of the camera usage causing drops to Qualcomm Crashdump mode. But honestly, it's going to keep being a thing with newer Google Camera ports. If you need stability for lots of photos, stick with a GCam port (like DMGC or Urnyx05) based on v7.3 or v7.4 for best results.
"Misc tweaks and bugfixes".
If it feels like it's still slightly too battery hungry, turn on the "GPU Throttling" toggle in DeviceExtras to save a little bit more (may cause a little more jank in gaming).
Other release-specific notes:​
People keep complaining about boot loops or losing their GApps or massive battery drains. I get it, sometimes the "Settings > System > Updater" has issues. But frequently the issue is a reading comprehension failure, and the answer keeps being the same: do a dirty flash from the included LineageOS-based crDroid recovery according to the instructions below, and DON'T FORGET TO REBOOT RECOVERY AFTER FLASHING THE ROM ZIP BEFORE FLASHING GOOGLE APPS. If you read NOTHING else from the first post about slots and stuff, at least FOLLOW THE INSTRUCTIONS.
I now have "elite builds" of my custom NikGapps config available for our device, and 16 June and newer releases of "crDroid-op6" now include a few extra packages in there that should help with some app compability going forward (added DeviceSetup, GooglePartnerSetup, DeviceHealthServices, and CarrierServices). See the "Google Apps" section below.
And if you come to the TG channel, I've got a little something something for you kernel-wise that isn't going into the official release build.
Known issues:
Spoiler: Show/Hide
Upstream crDroid/LineageOS things:
Custom fonts in crDroid Settings don't get reapplied to everything on reboot; need to select a different font & then back to preferred font after restarting.
There might occasionally be icons that don't work when "Themed Icons" is enabled in crDroid Home settings. If home screen keeps going black and then reloading, open Settings, then go to Apps > Default Apps, and click the gear next to "crDroid Home" to open our built-in launcher settings, and toggle off "Themed Icons" for now. Send me the crash report URL (paste.crdroid.net) or MatLog zip and it'll tell me which icon needs to get fixed.
Google Apps: If you have MindTheGapps or older NikGapps and you have SetupWizard installed as part of your Google Apps package, then enable Multiple Users and create a new Guest User, the "Setup Wizard" activity will fail to run at the end of the new profile creation, which will leave a couple props unset that normally tell Android that you've finished initial setup; and you won't be able to interact with the notifications/QS shade & will only have the "back" button in the navbar. You can either wait 10 minutes and it automagically fixes itself, or exit the "Guest session" without deleting data, and the next time you enter it, you'll have full control over navigation & statusbar/shades. This seems to be a limitation on multiple custom ROMs currently.
I don't know if this is an upstream issue or device-specific or certain Google Apps packages, but Google Assistant Hotword Detection/Voice Match causes media playback stutter sometimes. So you can either disable it, or doing an adb sideload installation rather than update seems to help some people (permissions issue in Android 13? who knows).
If you get problems with Google Play Store or Android Setup complaining that you need to connect to wi-fi in order to download updates, go into Settings > Apps > "See all __ apps" > [overflow menu] "Show system", then for Android Setup, Google Play Services, and Google Play Store, get app info and make sure to toggle on Network Access for all of them (or turn it off & back on), clear app cache, and then reboot as quickly as possible after. That should get them to realize they CAN connect to the internet after all.
People don't read documentation.
You tell me, with logs!
Installation notes:​
Spoiler: Show/Hide
In case of bootloop (boot animation stuck for longer than about 2 minutes and never gets to lock screen), reboot to recovery and manually flash the ROM zip via ADB sideload from computer, then reboot to recovery again, and re-flash your same Google Apps/microG/Magisk/whatever install zips (again via ADB sideload), and reboot system. This *should* take care of any lingering errors with old things getting stuck in your /system/addon.d/ directory that might be trying to preserve old privileged system apps without privileged permissions (which is what causes those boot loops in the first place).
The built-in OTA updater in Settings > System > Updater goes a lot faster if you go into Updater preferences and toggle on "prioritize updater process", and make sure the screen stays on by using the Caffeine QS tile, or "never sleep while charging" toggle in Developer Options, or changing your Display timeout to 30 minutes.
If you're installing MinMicroG instead of Google Apps, then before ADB sideloading the zip, from built-in recovery on the phone, you might need to go to Advanced > and choose "Mount/Unmount System" first. Then go back to "Apply update" and proceed with ADB sideloading as normal to install. I've heard this has been fixed in more recent builds this year, but haven't had a chance to confirm.
General Notes:​
Spoiler: Show/Hide
Yes this ROM supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
Tested against latest Magisk canary, works well.
No there won't be official builds with inline GApps; please don't ask. The dev team's policy is vanilla-only whenever possible (and it's very possible with our devices).
Google Apps:​
Spoiler: Show/Hide
Maintainer doesn't often use Google Apps personally as daily driver, but here are some notes gathered from peoples' testing:
TL;DR: If you're doing a fresh install, use this Nik GApps custom version (updated 16 June 2023):
https://sourceforge.net/projects/nikgapps/files/Elite-Releases/crDroid-op6/NikGapps-T/
Otherwise, use Nik Gapps Core + Setup Wizard addon (if you're going to restore from a Google Drive cloud backup during setup; *not* the Pixel one, it breaks our launcher) + GoogleSearch addon (for assistant & hotword integration) + GoogleTTS (more voice integration) + Markup (optional, good screenshot editor that you cannot add from Play Store later as a user app) + DeviceSetup, CarrierServices, GooglePartnerSetup, and DeviceHealthServices for now.
https://nikgapps.com/downloads#downloads
If you're already on MindTheGapps, and it's working fine, then ignore this. If you're on official MindTheGapps and facing weird battery drain issues, try updating to newer official version and doing dirty flash of ROM & MTG zip from recovery. If *that* doesn't work, try my modified build. It seems to vary by person and I don't know why.
Due to intermittent issues with excessive battery drain & missing location or network access permissions after Android 13.0 QPR1 that seemed to correlate with MindTheGapps 13.0 arm64 current official release, but not with NikGapps, I went ahead and made a modified build of MindTheGapps that includes additional allowances copied into permissions, default-permissions, and sysconfig XMLs from NikGapps, and the issues seem to be resolved. If you have battery drain issues with MindTheGapps official, then I recommend this package for everyone until such time as I can get the fixes narrowed down and commits submitted for inclusion upstream to the official MindTheGapps project. I have never been able to recreate the drain issue myself, although I have experienced the permissions problems with failure to pre-grant permissions for network access or location to Play Store and Setup Wizard/Android Setup.
However, some folks have had issues with my build that they didn't have with official, so... I don't even know any more. Use what works best if you're already on MindTheGapps.
https://github.com/TJ-Releases/mtg/releases/tag/tau-20230224
Until we can get a fix submitted, I am NOT recommending the use of official MindTheGapps 13.0, as it has begun exhibiting battery drain & permissions retention problems after Android 13 QPR1 was merged in December 2022. If you still need official MindTheGapps, you can get it here:
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
To switch from official MindTheGapps to my modified build (and back):
- Reboot phone to recovery
- ADB sideload the latest ROM zip
- Choose Advanced > Reboot recovery to reboot phone directly to crDroid recovery again
- ADB sideload desired MindTheGapps zip (use my modified build, unless you're specifically trying to help me trace down permissions/battery issues)
- ADB sideload Magisk (if you're rooting)
- Reboot system
Otherwise, in general, try to go with the lightest weight package you can and don't replace the stock dialer/messaging apps (just download them from Play Store and set defaults).
BitGApps ... exist. No idea how that's going. I hear it works though, so give a shot. Don't know the link, sorry.
Flame Gapps I have no idea about in Android 13.0.
https://flamegapps.github.io/download.html
Since we are LineageOS-based, here are the Lineage team's recommendations & reasoning:
https://wiki.lineageos.org/gapps.html
OpenGApps are not recommended, for reasons outlined in the LineageOS wiki link above.
Please report what worked for you, whether or not it survives updates when using the System Updater, whether or not it survives manual "dirty" update flashing via built-in recovery, and whether it passed SafetyNet, so I can keep this list updated.
Magisk and Google Play Integrity API (SafetyNet):​
Spoiler: Show/Hide
Without root:
We pass SafetyNet/Play Integrity out of the box, avoiding hardware-backed attestation & falling back to basic integrity (using PixelProps in framework).
I also build & ship ih8sn inline, which should cover all sensitive props to keep most apps from being able to detect root or bootloader unlock.
I don't know how to set up everything correctly to sign builds & verify everything needed to safely enable bootloader re-locking. I'm not even sure it's possible. So just don't try it; you're asking for a trip to MSMTool-land.
With root (Magisk):
If you root with Magisk and configure the Zygisk denylist correctly (see below), you should still pass. For fastest "certified" status, wait after initial installation & signing in to Google to update Play Store & Play Services before rebooting to recovery & ADB sideloading Magisk to root.
Be sure you're on an official topjohnwu release; I recommend beta or canary. "Magisk Delta" is unneeded; we already spoof the props you're worrying about.
Do not install kdrag0n's "Universal SafetyNet Fix"; it's not only unnecessary with this ROM but actively causes problems & interferes with other things (like preferences resetting every reboot).
Look, I don't like the idea of "Shamiko" or anything else that employs LSposed techniquies or similar to do framework injection, and I'm not going to troubleshoot bug reports from people using it. It's a Magisk module that's not open source, so there's no way to verify what it's doing with the root access you have given it. But if that's what makes your ****ty bank app work, then do what you gotta do. I would change to a credit union that doesn't try to hold you hostage with crappy apps.
How to configure Magisk & the Zygisk denylist:
1. Hide the Magisk app:
Go to Magisk > Settings, and choose "Hide Magisk app", granting "install from untrusted source" permission along the way if needed, re-open the hidden "Settings" app
2. Enable Zygisk process hiding:
Go to Magisk > Settings
Enable Zygisk, Enable Enforce Denylist
3. Set up Zygisk denylist:
From Magisk Settings, go to Configure Denylist
Tap overflow (three-dot) menu in upper-right, and select "Show system apps"
4. Find "Google Play Services" and select the following:
com.google.android.gms
com.google.android.gms.persistent [needed for Google Pay/Wallet]
com.google.android.gms.unstable
com.google.android.gms.snet
5. Find "Google Play Store" and select the following:
com.android.vending
6. [Optional, for contactless payment] Find "Google Wallet" or "Google Pay" if installed and select the following:
everything, who cares; it's like 2 processes
7. Back out of "Configure Denylist"
8. Get app info for Google Play Store, force stop, and clear app cache
9. Get app info for Google Play Services, and clear app cache
10. Reboot
Use something like YASNAC to verify that you're now passing Play Integrity API attestation with basic integrity.
Other helpful links:​
Download current boot.img files: enchilada / fajita (also attached below)
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA: enchilada / fajita
Firmware update instructions (LineageOS Wiki): enchilada / fajita
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade): enchilada / fajita
MinMicroG (recommend the "Standard" package from "abuse-cl" releases; needs you to "Mount System" in crDroid recovery Advanced options before installing)
Magisk (recommend latest stable/beta v26.1 release; bootloop-to-recovery-after-OTA-update issue appears to have been fixed).

LOGS OR IT DIDN'T HAPPEN​How to make bug reports (and how not to):​TL;DR: if you've got adb set up on the computer and authorized on the phone, plug into a USB cable, run adb bugreport from a terminal, and send me the zip file it generates, ALONG WITH A DESCRIPTION OF YOUR PHONE SETUP AND WHAT THE PROBLEM ACTUALLY IS.
Spoiler: Show/Hide
i appreciate bug reports, but I also need details. If an app is crashing ("FCing", meaning "force closing") then at a bare minimum, copy the crash log URL and share that with your report.
That probably won't be enough, though, which is why there are two main logs that I'm after, logcat and dmseg.
1. logcat​You can either use the built-in MatLog tool to acquire this, or get it via USB debugging and adb on the computer (which was in the prerequisites section of the XDA first post, so you installed platform-tools and have adb & fastboot on your PATH, riiiight? )
Using MatLog
MatLog is shipped built-in, and it works great. It's built for an older API though, so you'll need to manually grant it permission to access all files (it doesn't know enough to ask since it's a system app and assumes itself to be privileged). If you don't, then you can only use the "Sharing" interface to save logs, rather than saving them to internal storage.
To use, open the MatLog app, and go into settings and tick the box for "omit sensitive info" so that you don't end up sharing your IMEI or email addresses with the world. Probably still best if you PM me the logs instead of share to the group.
Ideally if it's a reproducible problem, reboot, open MatLog, do the thing that causes the buggy behavior, switch back to MatLog, tap on the menu and choose "Save Zip", then send me the resulting file (they're saved to /sdcard/matlog/saved_logs/). Otherwise, try to open it as soon after the issue as possible and Save Zip.
Using ADB (Android debug bridge)
Since we're currently building as "userdebug", you can always grab a logcat even without being rooted. I'm assuming you've got adb and fastboot installed & can run them from a terminal.
Enable Developer Options if you haven't already by going to "Settings" > "About Phone" > scroll down to the bottom and tap on the "Build number" field 7 times to enable, then back up to System and choose the new "Developer options" menu, and toggle on "Enable USB debugging".
Connect the phone to computer via USB, then on the computer open a terminal type adb devices to start the server & verify you can see the phone. At this point you might get a prompt on the phone asking if you want to trust the computer with some ID for debugging; tell it yes (probably always yes, in case you need to do troubleshooting later due to a boot loop). You should see your phone's serial number listed under the output of adb devices in the terminal window. If not, you probably need to install OnePlus USB drivers.
Run adb logcat from the terminal and get ready for a wall of text. Ctrl-C to stop the firehose after about 10 seconds. Save the output to a file. Note: this is the stupid way assuming you just opened a command window or built-in PowerHhell in Windows. Any linux shell or current version of PowerShell should instead be able to just run adb logcat > logcat.txt to dump the output directly to a text file in the current working directory without the wall of text; just give it about 10-15 seconds and Ctrl-C to stop the capture.
That's it! PM me the file, with any other details about what's happening and your setup (device, how you flashed, GApps, and so on).
2. dmesg​Requires root, probably USB debugging, platform-tools added to your PATH, and knowledge of what the below instructions mean
Open a root shell on the phone (via local terminal or adb shell via USB).
Run dmesg and save the output to a text file.
PM me the dmesg.txt file, along with a logcat capture as well, and a detailed description of what the problem is, what the behavior is you noticed, how to reproduce, details of your setup (which device, what GApps, what Magisk modules, any custom kernels, how you installed, and so on).
Protip: If you're not rooted, since this is a "userdebug" build, you can go into Settings > System > Developer options, turn on the toggle for "Rooted debugging", and then on your computer, do adb root to restart the adb server process. The next adb shell you run from the computer will get superuser privilege instead and you can run dmesg or do other things without having to root with Magisk.
If you are rooted, I highly recommend installing & using SysLog (by Tortel), available on the Play Store and on F-Droid; it's a GUI app that lets you easily capture both logcat & dmesg & can generate zip archives to send to your favorite maintainer, while allowing for scrubbing potentially sensitive data, and has some other advanced filtering options.
3. A detailed description of the actual problem & how to reproduce​Maintainer is not a mind-reader
Describe what the actual problematic behavior is, compared to what the expected behavior is. Don't just throw a logcat at me and expect me to figure out what you think was actually wrong. Explain how to reproduce the bug, and what you were doing at the time. Give me details about your configuration: are you actually on the most current version, did you clean install, did you use the recommended MindTheGapps package, are you rooted & if so what add ons/modules/root-required utilities are you using regularly, etc.
A picture is worth a thousand words. Moving pictures even moreso. If you can use screenshots, or better yet a screen recording, to show me how something is failing, that helps a TON.
Realize that a number of things are beyond my control. I'm not a software developer, I'm not on the ROM dev team, and some things might never get resolved. It's *still* better than OnePlus though, hey?
Feature requests are not bug reports. If you don't have a stack of tested commits that you can submit as a pull request for the dev team to merge, it's not likely to happen. But you can always ask politely!
Other Notes:​"Supported" status - PLEASE do not do these things if you want help:​
Spoiler: Show/Hide
It's your device to use the way you want of course, but don't expect support for your bug reports if you...
didn't update firmware in both slots.
didn't do a clean flash when first switching to this ROM at this major Android version (13.0).
installed with TWRP/any other custom recovery (or, worse yet, installed that custom recovery after).
aren't using the built-in kernel.
are using extensive root-required modifications & Magisk modules like Project Themer, Lsposed/Xposed/Riru/Shamiko, Dolby Atmos, Viper4A, modified Adreno GPU drivers, etc.
immediately start flashing stuff like "finalize.zip" or migrate restore zips instead of following the actual instructions.
are running decrypted (ugh, just don't).
re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
followed some other installation method different than the steps in the first post.
tried to dirty flash from an earlier crDroid/Android major version (like 8.x) without a factory reset.
Connectivity issues:​
Spoiler: Show/Hide
If you are having problems with wifi or mobile data under Android 13, try some of the following (and please let us know if one/all actually fixed things for you):
Get info for the Google Play Store app, go to "Mobile data & WiFI", and toggle network access off (if on), then on (again). Force close the app, then re-open it; see if it finds the Internet now.
Same as above, except for Google Play Services (you'll have to find it in "Settings > Apps > See all __ apps > overflow menu > Show system" then it should be in the list).
Go into Settings > Network & internet, scroll down to "Private DNS" and choose a different private DNS provider or simply turn the feature off.
Go into Settings > Network & internet, scroll down to "Connectivity check" and turn it off (in case connections to Google are being filtered at the network level).
Go into Settings > Network & internet > Internet, tap the gear icon next to the wifi network you're trying to connect to, and change Privacy to "Use device MAC" (some networks actively reject spoofed MAC addresses).
Go into Settings > Network & internet > Calls & SMS, and make sure your primary SIM is actually selected for calls, messages, and mobile data, then back up one menu level, go into SIMs, select your SIM if needed, and make sure "Mobile data" is toggled on.
Go into Settings > Network & internet > SIMs, select your SIM, and change the radio mode to one of the ones that *doesn't* start with "NR", like "LTE/TDSCDMA/CDMA/EvDO/GSM/WCDMA" (or the one without the CDMA/EvDO stuff if you know you're not on a CDMA carrier).
Go into Settings > Network & internet > SIMS, select your SIM, go into Access Point Names, and make sure you've got the correct APN selected.
Go into Phone (whatever you have for the default dialer), keypad, type in *#*#4636#*#* to open the "Testing" activity, choose "Phone information", then in the three-dot menu in the upper-right, choose "Select Radio Band" and choose the correct region instead of leaving it on "Automatic".
OnePlus Camera & Gallery:​
Spoiler: Show/Hide
It works. It all works, and it's also the only way to get 60fps video recording on this hardware right now, unless there's a GCam mod with configs I'm not aware of.
This version of OnePlus Gallery requires a Google account to actually exist before it will successfully download the expansion pack. If you're running vanilla or haven't signed into a Google account yet, it won't be able to download the thing it wants.
Oops, I dropped something.

Reserved. If I were you, I'd have reservations about this as well.

One huge ass bug report coming right up

Aaaand we're official!
Just in time to merge Android 13.0_r16 qpr1, which is an enormous rebase of android/frameworks/base/ with over 10K commits different, so Neobuddy89 and the rest of the team have been busy trying to redo all our customization/features on top of THAT for a week now. So everything that was finally working is probably broken again, sweeeeeet!

Thanks again for your work.
I know dirty flash isn't the recommended way, but this worked for me:
OTA 8.10 -> 8.11 -> fastboot flash boot.img to both slots (just in case something's changed since I flashed it the last time) -> reboot to recovery -> dirty flash 9.0 -> flash NikGApps Basic (not the recommended GApps, I know, but I found out too late to switch) - > flash Magisk -> reboot to system.
Last time when I tried to dirty flash 7 to 8, I got a bootloop since I was one version behind unlike this guy, so I figured waiting for the latest 8 release might be the right thing.
So far, so good. System feels much more responsive now and all the minor issues I encountered in crDroid 8 are gone (not sure about RAM management yet, I'll see).
I had a few issues initially, but everything's resolved now:
I had a "Settings Services not responding" pop-up after the first boot, which I fixed by clearing the app's storage
My 6T randomly became completely unresponsive after locking a screen (with a double-tap on the default launcher, I think). I've encountered a similar issue on crDroid 8 several times before, but I think that had something to do with the pocket mode. When it happened on 8, I'd have to force reboot with hardware buttons. This time however long pressing the power button showed me the power menu (although it looked like a standard Android one, with a white background and only 3 options, unlike the crDroid one). This has only happened once and hopefully never will again
My only pet peeves (probably upstream issues and not out device-specific) are:
Weather service doesn't seem to be working (neither OpenWeatherMap nor MET Norway, neither on lockscreen nor the OmniJaws widget). Do I need a custom OWM key?
Mobile icon used to hide when data was off. Now there's a permanent data disabled indicator, which is kinda annoying but I guess I'll get used to it

Terminator.J said:
Aaaand we're official!
Just in time to merge Android 13.0_r16 qpr1, which is an enormous rebase of android/frameworks/base/ with over 10K commits different, so Neobuddy89 and the rest of the team have been busy trying to redo all our customization/features on top of THAT for a week now. So everything that was finally working is probably broken again, sweeeeeet!
Click to expand...
Click to collapse
Bluetooth keeps crashing.Any One Experiencing the same?

For some reason, the GPS doesn't work (in google maps for example). Gave all of the apps location access and made sure to turn on the "use location" toggle. All location services are turned on as well (e.g. google location accuracy). However, location data does work in the metadata of pictures taken by the camera app.

Adnan Hussaini said:
Bluetooth keeps crashing.Any One Experiencing the same?
Click to expand...
Click to collapse
Can't say I've had that issue, with my fitness tracker, or multiple headphones/headsets, or mouse/keyboard...
See post #3 for how to take logs if you'd like to send me a bug report!

Awner said:
For some reason, the GPS doesn't work (in google maps for example). Gave all of the apps location access and made sure to turn on the "use location" toggle. All location services are turned on as well (e.g. google location accuracy). However, location data does work in the metadata of pictures taken by the camera app.
Click to expand...
Click to collapse
Depending on how you installed, or Google apps package, or if you did something like clearing storage for Play Store or Play Services, you might need to go into Settings > Apps > "Show all ___ apps" > 3-dot menu > "Show system", find Google Play Services and Google Play Store and re-grant them permissions again (like location).
Never had a problem with GPS working while driving in Waze regularly, or recording locatoin in photos in in OP Camera, Lineage Aperture (the other "camera" app with darker grey icon).
Please see post #3 for details on how to send me a bug report & what kind of logs/information I'll need.

runtosafety said:
Thanks again for your work.
I know dirty flash isn't the recommended way, but this worked for me:
OTA 8.10 -> 8.11 -> fastboot flash boot.img to both slots (just in case something's changed since I flashed it the last time) -> reboot to recovery -> dirty flash 9.0 -> flash NikGApps Basic (not the recommended GApps, I know, but I found out too late to switch) - > flash Magisk -> reboot to system.
Last time when I tried to dirty flash 7 to 8, I got a bootloop since I was one version behind unlike this guy, so I figured waiting for the latest 8 release might be the right thing.
So far, so good. System feels much more responsive now and all the minor issues I encountered in crDroid 8 are gone (not sure about RAM management yet, I'll see).
I had a few issues initially, but everything's resolved now:
I had a "Settings Services not responding" pop-up after the first boot, which I fixed by clearing the app's storage
My 6T randomly became completely unresponsive after locking a screen (with a double-tap on the default launcher, I think). I've encountered a similar issue on crDroid 8 several times before, but I think that had something to do with the pocket mode. When it happened on 8, I'd have to force reboot with hardware buttons. This time however long pressing the power button showed me the power menu (although it looked like a standard Android one, with a white background and only 3 options, unlike the crDroid one). This has only happened once and hopefully never will again
My only pet peeves (probably upstream issues and not out device-specific) are:
Weather service doesn't seem to be working (neither OpenWeatherMap nor MET Norway, neither on lockscreen nor the OmniJaws widget). Do I need a custom OWM key?
Mobile icon used to hide when data was off. Now there's a permanent data disabled indicator, which is kinda annoying but I guess I'll get used to it
Click to expand...
Click to collapse
There's probably permissions issues going on there. You really should plan on backing up your stuff & doing a factory reset (which will wipe internal storage, sorry) or it's just going to have little lingering issues like this that I can't help with.
Pet peeves:
1. The weather service works flawlessly both with MET Norway & OWM even without a custom API key; came right up for me. Likely needs a clean flash/factory reset to work correctly.
2. Not sure what combination of settings caused that bug to happen, but mobile signal strength should be visible even when data is disabled, since calls & SMS still exist. But yeah; lots of UI-related stuff is likely different. Every major release the ROM dev team has to figure out what will actually keep working or not, and tried to bring features back in or drop them because it's buggy now or causes problems elesewhere or so forth. Honestly the statusbar icon customization options were kind of a mess in Android 12 and it does seem like it's more reliable & consistent now than it was before.
But I understand you miss your favorite setup; I get it. Sorry friend.

Meanwhile, having synced Android 13.0_r16 (QPR1/December ASB), the dev team had to redo all our stack of modifications & customizations on top of it again (for the git-savvy, it's because it's a rebase of all the AOSP repos; more than 10K commits difference, can't just merge in monthly changes).
They essentially had to do Android 13 all over again, and now all of us maintainers are checking to see what broke.
It seems not entirely broken though, so I'll probably start putting up December ASB testing builds in the TG group soon!

Terminator.J said:
Depending on how you installed, or Google apps package, or if you did something like clearing storage for Play Store or Play Services, you might need to go into Settings > Apps > "Show all ___ apps" > 3-dot menu > "Show system", find Google Play Services and Google Play Store and re-grant them permissions again (like location).
Never had a problem with GPS working while driving in Waze regularly, or recording locatoin in photos in in OP Camera, Lineage Aperture (the other "camera" app with darker grey icon).
Please see post #3 for details on how to send me a bug report & what kind of logs/information I'll need.
Click to expand...
Click to collapse
Hi first of all thanks for making this amazing rom! I fixed the issue by formatting my data again. I think everything works now. Really love the device-specific additions that are otherwise missing in other roms. Thank you

I just moved from Rice to this ROM and I feel this ROM is better and more polished.
Thanks @Terminator.J

marcioafoliveira said:
I just moved from Rice to this ROM and I feel this ROM is better and more polished.
Thanks @Terminator.J
Click to expand...
Click to collapse
Yes, in my humble opinion it is better and J always cool, he answer every question on telegram.

Hey there's a weird bug that's been going on and it has been happening with all the android 13 ROMs I have been using. The NFC just quits randomly and blanks out the menu in settings until reboot.

marcioafoliveira said:
I just moved from Rice to this ROM and I feel this ROM is better and more polished.
Thanks @Terminator.J
Click to expand...
Click to collapse
any review compared to LOS20 unoficial? I love LOS but really miss the abilty to customize the rom

Nice work,It suit me well,But i can't get OTA updates,I gess it might be a network issue,so I wonder the OTA adress to find out what's wrong,can some one help?

imokpd said:
Nice work,It suit me well,But i can't get OTA updates,I gess it might be a network issue,so I wonder the OTA adress to find out what's wrong,can some one help?
Click to expand...
Click to collapse
Well, so far there aren't any. That might be why. I've only ever made one official 9.0 (Android 13) release.