Delete the file ".twrps" in the TWRP folder. Its a hidden file, so make sure that your file manager also shows hidden files.How to delete twrp settings?
Delete the file ".twrps" in the TWRP folder. Its a hidden file, so make sure that your file manager also shows hidden files.How to delete twrp settings?
eng.stk already said he only supports the CAF way of loading modules, ie. as a module and not inline. So, it'll only work with Omni based custom ROMs.r161-custom cannot turn on WiFi on Lineage 16.0 official
Anyone same issue?
- sync with OOS 9.0.5
- Revert "KLAPSE: adapt to work with kcal for mdss_mdp_v1_7"
- K-lapse: initial implementation for MDSS kcal
- Revert "include: asm-generic: do not hard code HZ to 100"
- defconfig: set hz=300
- Update wifi module to OOS 9.0.5 (custom)
- AnyKernel2 updates
- Misc runtime fixes and responsiveness improvements
Can this be updated within twrp-3.2.3-x_blu_spark_v9.96 using the image flash function? Or is it better to flash it using "fastboot flash recovery twrp-3.3.0-x_blu_spark_v9.100_treble-op5_op5t.img" when in fastboot?All right crew!
Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-9.0 branch (including more recent upstream than official TWRP) and some specific device fixes.
Fully synced with TWRP 3.3.0+, name changing to reflect base 9.version, full compatible with Pie stuff (you need Pie fw also).
TWRP blu_spark edition is unified, works for both OP5/5T.
Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
This build is treble ready, allowing /vendor partition operations. If you don't use treble enabled ROMs, ignore any vendor errors that may appear, TWRP will work just fine.
twrp-3.3.0-x_blu_spark_v9.100_treble-op5_op5t
Yes it simply can be updated with your current recovery like you described.Can this be updated within twrp-3.2.3-x_blu_spark_v9.96 using the image flash function? Or is it better to flash it using "fastboot flash recovery twrp-3.3.0-x_blu_spark_v9.100_treble-op5_op5t.img" when in fastboot?
I am not able to flash " no-verity-op5(T)_V3_treble_.zip" using new TWRP but flashed back old version & now I was able to update, tried couple of times, does anyone faced the issue.All right crew!
Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-9.0 branch (including more recent upstream than official TWRP) and some specific device fixes.
Fully synced with TWRP 3.3.0+, name changing to reflect base 9.version, full compatible with Pie stuff (you need Pie fw also).
TWRP blu_spark edition is unified, works for both OP5/5T.
Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
This build is treble ready, allowing /vendor partition operations. If you don't use treble enabled ROMs, ignore any vendor errors that may appear, TWRP will work just fine.
twrp-3.3.0-x_blu_spark_v9.100_treble-op5_op5t
Wakelock blocker info and example script
I'm just sharing my personal mods since people asked, meaning no support will be given (don't bother post about it).
If your cat get's on fire you're on your own ;p
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free![]()
Yes, see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79439548 FF and the OB31 thread.I am not able to flash " no-verity-op5(T)_V3_treble_.zip" using new TWRP but flashed back old version & now I was able to update, tried couple of times, does anyone faced the issue.
Never tried to adjust the max frequency before but I too am noticing that when I try to set to 2457 it resets to 2361 automatically within a few seconds.I'm loving the kernel and the recovery, I just have one doubt, why does my max cpu freq keep coming down to the default value. I can't keep it at 2457. I'm using kernel auditor
If you have MSM touch boost on then 2361 is the max. Default settings touch boost is on.Never tried to adjust the max frequency before but I too am noticing that when I try to set to 2457 it resets to 2361 automatically within a few seconds.
Had to look for TouchBoost, i never really played much with Kernel Auditor settings before. It appears to have been and remains off, but the max freq issue still occurs. See screenshot.If you have MSM touch boost on then 2361 is the max. Default settings touch boost is on.
Sorry i was wrong it is not touch boost it is qualcomm caf boost framework that limits the cpu if u want to remove it you must delete vendor/etc/perf folder in recovery and after you have max available. Backup vendor before doing this or you have to reflash rom to get it back.Had to look for TouchBoost, i never really played much with Kernel Auditor settings before. It appears to have been and remains off, but the max freq issue still occurs. See screenshot.
Oof, is it worth all that trouble for a such a small boost? How does one go about deleting a folder while in recovery? Why would one want to have this folder back without having to reflash rom or just restoring a nandroid backup?Sorry i was wrong it is not touch boost it is qualcomm caf boost framework that limits the cpu if u want to remove it you must delete vendor/etc/perf folder in recovery and after you have max available. Backup vendor before doing this or you have to reflash rom to get it back.
For me it indeed is not worth it and in recovery advanced you have a filemanager. And if you backup only vendor it is enough to get caf boost back of you for some reason want it back after you deleted the folder.Oof, is it worth all that trouble for a such a small boost? How does one go about deleting a folder while in recovery? Why would one want to have this folder back without having to reflash rom or just restoring a nandroid backup?
And it appears I can't simply create a zip of /vendor in an app like X-Plore and that I would have to do this in recovery as well -- how does one go about backing up only a specific root folder in recovery?For me it indeed is not worth it and in recovery advanced you have a filemanager. And if you backup only vendor it is enough to get caf boost back of you for some reason want it back after you deleted the folder.
Damn I think I'm happy with the default value then, it just bugged me that I couldn't reach the max potential but nah not worth all thisFor me it indeed is not worth it and in recovery advanced you have a filemanager. And if you backup only vendor it is enough to get caf boost back of you for some reason want it back after you deleted the folder.
- build: TWRP 3.31-x | blu_spark v9.101
- ext4crypt: support synthetic keys v3 on May update
- Fix symlink creation
- Switch between dependencies and modules
- Digest: Create digest for each subpartition and not just the first.
- 3.3.1
- Add option to uninstall TWRP app from /system
- Flash both A/B partitions when flashing recovery ramdisk
- Resolve e2fsdroid failure in certain cases
- Update help manual in orscmd
- toolbox: Avoid linking toolbox tools to dd
- language: update Chinese translations
- NTFS-3G: use newer libfuse-light in pie.
- English language: Remove duplicate value.
- bsd dd: include prebuilt bsd dd in twrp for Nougat and greater
- toybox: fix build in 6.0 tree
- awk: add awk for trees including one-true-awk
- mkshrc: remove post-install cmd and use LOCAL_MODULE_STEM
- Clean up logd init file
- Use BSD grep for builds with toybox
- ext4crypt: add missing cflag
- Pass file_contexts path to e2fsdroid
- Device specific changes here
- build: use new and improved blu_gcc-9.1.0
- makefile: disable a couple gcc-9 warnings
- stune: Remove Dynamic SchedTune Boost
- adrenoboost: disable by default
- adrenoboost: finetuning algorithm - scale it a bit down
- msm_adreno_tz: add adrenoboost parameter
- further blu_spark settings tweaks to improve UX
- AnyKernel2 updates
Thanks.All right crew!
Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-9.0 branch (including more recent upstream than official TWRP) and some specific device fixes.
Fully synced with TWRP 3.3.1+, name changing to reflect base 9.version, full compatible with Pie stuff (you need Pie fw also).
TWRP blu_spark edition is unified, works for both OP5/5T.
Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
This build is treble ready, allowing /vendor partition operations. If you don't use treble enabled ROMs, ignore any vendor errors that may appear, TWRP will work just fine.
twrp-3.3.1-x_blu_spark_v9.101_treble-op5_op5t
Wakelock blocker info and example script
I'm just sharing my personal mods since people asked, meaning no support will be given (don't bother post about it).
If your cat get's on fire you're on your own ;p
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free![]()