[ROM] DivestOS 18.1 for m8 - One (M8) Android Development

[ROM] DivestOS 18.1 for m8 - One (M8) Android Development

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-m8
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#m8
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_htc_m8, https://github.com/LineageOS/android_device_htc_m8-common, https://github.com/LineageOS/android_device_htc_msm8974-common
- Kernel: https://github.com/LineageOS/android_kernel_htc_msm8974
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/....1/CVE_Patchers/android_kernel_htc_msm8974.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----

SkewedZeppelin said:
View attachment 5326025
DivestOS is a more private and more secure aftermarket system.
HTC One (M8) Notes:
- This image is untested. I do not have this device and no users have reported its status. Please test it if you can. Thanks!
- 17.1 builds were however previously tested working.
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
Extra Features (not installed by default):
- Mull, our hardened fork of Fenix
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-m8
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#m8
- Screenshots: https://divestos.org/index.php?page=screenshots
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_htc_m8, https://github.com/LineageOS/android_device_htc_m8-common, https://github.com/LineageOS/android_device_htc_msm8974-common
- Kernel: https://github.com/LineageOS/android_kernel_htc_msm8974
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/....1/CVE_Patchers/android_kernel_htc_msm8974.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this ROM.
- This ROM has userdata encrypted by default
- You are intended to relock your bootloader with this ROM (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
Click to expand...
Click to collapse
Boots fine, however on the verizon (M8wl) variant , sim, IMEI all not detected (all show "unknown") , seems like RIL is broken

Btw , I flashed the ROM ZIP with twrp , no issues at all

fela4 said:
Boots fine, however on the verizon (M8wl) variant , sim, IMEI all not detected (all show "unknown") , seems like RIL is broken
Click to expand...
Click to collapse
Hmm, can you post the output of:
adb logcat -b all -d | grep -i audit

Here's the output of adb logcat -b all -d | grep -i audit and adb logcat -d from my device, an m8wl variant.
Flashed divested-18.1-20210509-dos-m8.zip

K3li said:
Here's the output of adb logcat -b all -d | grep -i audit and adb logcat -d from my device, an m8wl variant.
Flashed divested-18.1-20210509-dos-m8.zip
Click to expand...
Click to collapse
Thank you for the logs!
A 20210613 build is up that should fix the error!

Just flashed the new build (20210613) but I'm unable to test.
"To start Android, enter your password" shows on the screen.
Wiped data, cache,dalvik.
The earlier build (20210509) did perform encryption and I could boot into it after it was done. This one goes straight to that password dialog.
Any password I try just returns a "The password you entered is correct, but unfortunately your data is corrupt.." message and offers to erase my data. When I choose this option, it just restarts into recovery performs data/cache/dalvik wipe, then restarts again into that password dialog.

K3li said:
Just flashed the new build (20210613) but I'm unable to test.
"To start Android, enter your password" shows on the screen.
Wiped data, cache,dalvik.
The earlier build (20210509) did perform encryption and I could boot into it after it was done. This one goes straight to that password dialog.
Any password I try just returns a "The password you entered is correct, but unfortunately your data is corrupt.." message and offers to erase my data. When I choose this option, it just restarts into recovery performs data/cache/dalvik wipe, then restarts again into that password dialog.
Click to expand...
Click to collapse
Uh oh.
I've pulled that build. I am not sure what would have caused that.
I will make a 17.1 build, as clearly 18.1 is not ready yet.

K3li said:
Just flashed the new build (20210613) but I'm unable to test.
Click to expand...
Click to collapse
A new 17.1-20210614 build is up, hopefully this one is more functional .

That was fast!
I dig your fast responses, thanks for the good work.
I'll download and test the new build.

SkewedZeppelin said:
A new 17.1-20210614 build is up, hopefully this one is more functional .
Click to expand...
Click to collapse
Download link still points to the 18.1 build.

K3li said:
Download link still points to the 18.1 build.
Click to expand...
Click to collapse
Scroll down to the 17.1 section. The page supports multiple versions.
https://divestos.org/mirror.php?base=LineageOS&f=m8/divested-17.1-20210614-dos-m8.zip

I've flashed the 17.1 build above (20210614) and everything work so far except for the part where I can't turn on mobile data.
I tried restoring a previous TWRP backup of the ROM I was using (Lineage 17.1) but was greeted with the "Android password" dialog I talked about earlier.
So my backup is useless.
Also, the phone becomes unresponsive after a while with this build.
Let me wipe everything then see if I can install my previous ROM.
Tried wiping dalvik/data/cache/android secure but nothing worked. I couldn't boot into my TWRP restored backup. I was being asked for a password.
I restored everything including boot and recovery partitions.

K3li said:
I've flashed the 17.1 build above (20210614) and everything work so far except for the part where I can't turn on mobile data.
I tried restoring a previous TWRP backup of the ROM I was using (Lineage 17.1) but was greeted with the "Android password" dialog I talked about earlier.
So my backup is useless.
Also, the phone becomes unresponsive after a while with this build.
Let me wipe everything then see if I can install my previous ROM.
Tried wiping dalvik/data/cache/android secure but nothing worked. I couldn't boot into my TWRP restored backup. I was being asked for a password.
I restored everything including boot and recovery partitions.
Click to expand...
Click to collapse
That is very strange.
You should be able to flash to anything else, and restore a congruent backup with no issue.
To confirm: you tried formatting /data, rebooting, then restoring your backup?

SkewedZeppelin said:
That is very strange.
You should be able to flash to anything else, and restore a congruent backup with no issue.
To confirm: you tried formatting /data, rebooting, then restoring your backup?
Click to expand...
Click to collapse
After installing this ROM, the recovery flew off, with difficulty restored.

SkewedZeppelin said:
That is very strange.
You should be able to flash to anything else, and restore a congruent backup with no issue.
To confirm: you tried formatting /data, rebooting, then restoring your backup?
Click to expand...
Click to collapse
Reformatted and was able to successfully flash Lineage. Apparently I was doing it wrong. Selecting everything in 'Advanced Wipe' in TWRP isn't enough. I had to format data as well- where you're asked to type 'yes' for anyone following this thread. Encryption is serious business.
My testing itch was still there and I was eager to give it a little scratch, so reflashed divested-18.1-20210509-dos-m8.zip again armed with the knowledge that formatting 'data' was a must when switching ROMs. This time I was able to boot into it.
Yay! It works
Everything seems to work except for mobile data
Even tried setting up a custom apn but it wouldn't connect just like the 17.1 build. You can see from the screenshots i've attached that there's no LTE/H+ indicator next to the network icon.
But at least the sim card is detected and I'm able to make/receive calls. I can also send and receive sms messages
Still testing this new 18.1 build as I'm typing this.. playing music via bluetooth and I'm yet to encounter any stuttering as was the case with Lineage 17.1 (occasionally)
Let it be noted that I really like this ROM, congrats for the good work.
Attached please find some logs for you to look into.

@[email protected] said:
After installing this ROM, the recovery flew off, with difficulty restored.
Click to expand...
Click to collapse
I feel you.
I tried flashing the divest recovery yesterday. That thing threw me into a panic!
The phone kept rebooting trying to enter into a non-functional recovery.
(╯°□°)╯︵ ʎɹǝʌoɔǝɹ_ʇsǝʌᴉp

K3li said:
I feel you.
I tried flashing the divest recovery yesterday. That thing threw me into a panic!
The phone kept rebooting trying to enter into a non-functional recovery.
(╯°□°)╯︵ ʎɹǝʌoɔǝɹ_ʇsǝʌᴉp
Click to expand...
Click to collapse
Strange, if the system boots the recovery should boot.
Do you just see the HTC logo or something?

SkewedZeppelin said:
Strange, if the system boots the recovery should boot.
Do you just see the HTC logo or something?
Click to expand...
Click to collapse
Yes I could see the HTC logo and the "Entering recovery.." text at the top but the phone wouldn't enter recovery.
It would reboot again showing the same "Entering recovery.."
So a bootloop of some sort.
With difficulty (multiple volume down + power tries) I was able to enter fastboot and reflash TWRP recovery.

K3li said:
Everything seems to work except for mobile data
Click to expand...
Click to collapse
Delayed, but latest 18.1-20210617 build fixes the netmgrd error as in your logcat.
Should make cellular work.

Related

[DEV][ROM][4.4.4][KTU84Q] Unofficial CyanogenMod 11 | RC5 | 05/05/2015

Not working
- FM radio.
- Apps that expect newer libOMXVidEnc will not work, Skype is one example. Viber and WhatsApp are working.
- do not use stock browser for serious browsing, although it is working, it has bugs with adreno libs. For 2-step authentication on Google, it will do.
Upstream issues
SDCard not showing unmount option
Trebuchet crashing when you enable CM Home or Google Search as panel
Cyanogenmod stock camera app shows 4.5mp instead of 5 mp - camera works properly with other third party apps and takes 5MP pictures.
Sources: - cm-11.0 branches in each repo:
Device
Kernel
Vendor
Thanks:
CyanogenMod team, legacyMod & KonstaT, HTC Pico development team, TeamHackLg & everyone who's been working on CM11.
Downloads:
CM11 RC5 (194.45 MB)
Android File Host | BasketBuild
MD5: 63ff9995dad6d2f6798f5b6b8b1a8c11
Optional GAPPS:
http://forum.xda-developers.com/showthread.php?t=2779598(thanks @kodirovshchik for suggestion)
How to install:
You must update recovery with this one - TWRP 2.8.6.0 or this one Philz Touch 6.59.0 - ClockWorkMod 6.0.5.1- these two have SELinux support. Philz and CWM do not have support for F2Fs!
Install the recovery trough fastboot
- fastboot flash recovery recovery.img
Reboot to recovery from fastboot
- make a backup of your current ROM to SDCard
- wipe -> do a factory reset
- wipe -> advanced wipe -> select only system and wipe
- install zips (rom and gapps)
- reboot to bootloader
if you are updating from previous CM11, you can dirty flash -> just wipe /system in Wipe -> Advanced Wipe, and install rom and gapps. No guarantees here.
Install boot image
fastboot flash boot boot.img
install boot.img that is inside the ROM that you downloaded
do not do fastboot erase cache
As of RC5, ROM now supports both EXT4 and F2FS in a same installation, and there is an easy way to switch back and forth between full EXT4 and F2FS setup, or any partition layout you would like (why would someone want this, I do not know, but the option is there).
Switching to F2FS from EXT4:
- You must install TWRP 2.8.6.0 with F2FS support.
- install RC5 and gapps (optionally), flash boot.img and restart. Check that the ROM is working properly. Activate advanced reboot in developer options. Reboot to recovery.
- backup - make a nandroid backup of system, data and cache.
- wipe, advanced wipe - select system - change or repair file system - choose F2FS. Repeat this for data and cache.
- settings -> Check use rm -rf instead of format.
- restore -> this will restore your data to existing partitions without format.
- settings -> Uncheck use rm -rf instead of format.
- reboot
You will boot to full F2FS ROM, with all your data and settings intact. Check it out in terminal with
mount | grep f2fs
How to build:
Up to date sources on github. (one patch for legacyMod frameworks_av is missing, will update device tree soon)
1. Follow instructions on initializing a build environment up to a point of downloading the source code.
2. Initialize CyanogenMod 11 repo.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
3. Add local manifest that downloads HTC Desire C device config, properties and kernel source from my github and few CM replacement projects from legaCyMod github.
Code:
curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/high1/android_local_manifest/cm-11.0/local_manifest.xml
4. Sync source code.
Code:
repo sync
5. Update prebuilts
Code:
cd path-to/cm11/vendor/cm/
./get-prebuilts
6. Apply patches
Code:
path-to/cm11/device/htc/golfu/patches./apply.sh
7. Compile.
Code:
cd path-to/cm11/
. build/envsetup.sh
brunch cm_golfu-userdebug -jx
(x is number of your processor cores -+1)
'repo sync' to pull merged changes from upstream.
'make clobber' to clean the build environment.
Repeat step 7 to make a new build.
FAQ:
Q: I can't find developer options and performance settings, why?
A: Settings -> About phone -> Click 'Build number' several times
Q: I don't have reboot options in power menu, why?
A: Settings -> Developer options -> Advanced reboot
Q: Is ART runtime working?
A: Yes it is. Beware, it is not compatible with xposed framework.
Q: How to make fastboot and adb work with Windows 8.1? (Device enumeration failed error)
A: First, make sure you have this update installed - http://www.microsoft.com/en-pk/download/details.aspx?id=43515 . Unzip http://goo.gl/CAXglZ and merge it to your registry. HTC drivers must be installed, compatible with Windows 8.1 here: http://forum.xda-developers.com/showthread.php?t=2714921
Q: USB tethering does not work?
A: Here is a guide: Android USB Tethering In Windows 8.1
Changelog
3.5.2015 changelog:
- one ROM for both file systems - made multiple file system patch work on CM11, and update fstab and updater-script for that,
- fixed black screen in call - updated touchscreen and proximity driver from cyanogen_htc_msm8960 3.4 kernel, and updated board definitions, so that the proximity sensor is now working properly
- switched back to legacy OMX - camera recording is working, and the latest Viber is working properly. Skype is crashing due to old OMX libraries, but does not render the phone useless.
- using adreno libraries from TeamHackLGE - just for testing
- updated libqc-opt.so from TeamHackLGE repo - seems that this fixes some schedulers get stuck on lowest frequency.
- addes sioplus scheduler to kernel.
10.4.2015 changelog:
- released two separate ROMs, ext4 and full f2fs
- f2fs ROM got hand update for updater-script and fstab
- fixed errors reported when installing the ROM - updater-script has hardcoded filesystem, and this was the cause
- fixed the camera regression
7.4.2015 changelog:
Device tree:
- switched to HtcLegacy display-caf, which fixes high idle battery drain
- updated OMX libraries from TeamHackLG msm7x27a vendor repo - this fixes Viber, Skype etc, but video recording is broken
- switched to QCOM power HAL
- bluetooth vendor library is now in /vendor
- switched to Cyanogenmod frameworks_av
- cleaned up patches (down to only three and one replaced repo - this is almost pure CM11)
- switched to TWRP 5.1 branch, and made it compile with CM11 tree
- switched to QACT for audio lib
- compiling nightly again, as CM11 is EOL, and I think no new milestones will happen
- forcing high-end graphics is not default anymore
- moved adreno libs in vendor tree to vendor folder, removed one unneeded fil
Kernel:
- updated touch and proximity drivers from 3.4 kernel
- headset profile from 3.4 kernel
- added lz4 compression to kernel
- Update zram and zsmalloc up-to 3.17 kernel changes (zsmalloc now used instead of xvmalloc)
- enabled lz4 compression for zram
- restored audit support
- further various updates to kernel
20.2.2015 changelog:
- fixed brightness bug by keeping original framebuffer stack
- fixed memory bug (0.00B shown)
- added f2fs support to kernel
- added intelliactive, adaptive and smartassH3 governors, and updated interactive. Enabled all governors in kernel.
- added zen scheduler. Updated BFQ scheduler to v7r7. Enabled all schedulers in kernel.
- updates to block stack, faster I/O
- ROM built pre deoxed - installation will be longer, first boot will be much shorter
- moved all the proprietaries to vendor tree
- added F2FS support to ROM and recovery
15.12. changelog:
- fixed Bluetooth regression
- added surface texture patch
- updated prebuilts
7.12. changelog:
source synced to CM11 M12
switched to pico kernel, ION build
ported ION changes to golfu board
new graphics libraries, latest that support our board
ported golfu panel driver to pico kernel
switched to kernel XZ compression
switched to display-caf - TeamHackLG with patch
removed a lot of legacy repos - only frameworks_av needs to be replaced now
using CM11 chromium webview - applications that call evaluateJavaScript work now
updated touchscreen drivers
simplified camera build
added Philz touch recovery to ROM build
12.11. changelog:
- new wireless driver, ported from samsung kernel
- kernel changes, needed for new driver - new wireless_ath stack, imported compat folder, Makefile tweaks - do not build ath.ko for golfu
- fixes wifi tether
- fixes soft reboot
9.11. changelog:
Remaining audio routing issues are fixed, libaudio updated so no need for patching.
Call recording works
Solved freezing issues (need confirmation)
decreased wake up delay, enabled slow blur, increased ui responsivness
some other tweaks for sleep mode, limiting number of runnig apps
monitoring net usage on proper interface
removed custom wifi, updated wireless definitions and switched to Cyanogenmod private lib for ath6kl
kernel makefile optimizations - proper flags for our device
-O2 optimizations - kernel fits to boot.image so it should also improve speed
24.10. changelog:
Synced with latest CM11 nightly
Fixed video - camera recording, youtube
Disabled haptic feedback by default
Enabled call recording
23.10. changelog:
Fixed Wifi
Kernel with overclocking - capped to 600 at start, overclockable to 900 - One kernel for All!!!
Fixed stock browser with legacyMod patches
legacyMod prebuilts
18.10. changelog:
Fixed camera rotation (excluded definitions for 3M golfu, sensor mount angle is 0, and fixed sensor driver file in kernel - thx to Sachin Thomas)
Fixed media_profiles.xml partially - you can start the video, but it crashes on recording start
Fixed nfc - firmware was missing
Enabled swap to zRAM KitKat style
Re-enabled HTC performance lock, but only during boot
(Fixes yet to be uploaded with next beta)
16.10. changelog:
Android 4.4.4
First public build
A lot of changes and cleanups to the ramdisk and boardconfig
Added SELinux support to kernel
Made a working, stable recovery, first with repacked zImage and then source built
ROM made bootable
Fixed adb
Fixed SDCard
Fixed Bluetooth
Fixed Audio
Fixed RIL
Partially working camera
Added TWRP to ROM build process instead of CWM
Disabled HTC performance lock and limited frequencies on first boot so that one image is usable for all and devices do not crash
Enabled KSM by default
This all would not be possible without help - I looked up alot to KonstaT that makes CyanogenMod for ZTE Blade III, and a lof of this post is taken from his way of posting. KirmaniArslan helped to solve quite a few quirks, and posted patches actively, and started the development - his device tree was made bootable.
I expect logcats from all who will do testing, and hopefully we can fix the remaining bugs and let this device have fully working Cyanogenmod (Omni, Pacman, AOKP hopefully later). Also, with the release, you have full permission to use the source to build other ROMs, only requirement is that if you find a fix, you do a pull request at Github.
Regards, and enjoy the ROM as much as you can.

kirmaniarslan said:
BETA 1 : https://mega.co.nz/#!mBZhHKaZ!jQ7_vJ...F9zzpyvNla5fgQ
Kernel for BETA 1 : https://mega.co.nz/#!KURjUALa!Rj-nlM...A0I7LIq5Xdj2YQ
Click to expand...
Click to collapse
Ok. Enter decryption key. =)

Reserved for testbuilds

kodirovshchik said:
Ok. Enter decryption key. =)
Click to expand...
Click to collapse
Links updated.

So. As for me.
Adb doesnt work at first boot, so i can't get logcat. All logs what i have - TWRP log.
Cyclic reboot. It works for 2-3 sec and reboots. ANd i cant even look at settings or enable debugging. 2sec and reboot. One thing i'm shure its not from overheating =(
upd:
ok... boot in safe mode gives me 2 extra seconds.. and... there is no developers menu. it is locked. and i cant unlock it.
upd2: nope. i definitely can't attach rom Log and Ksmg.

kodirovshchik said:
So. As for me.
Adb doesnt work at first boot, so i can't get logcat. All logs what i have - TWRP log.
Cyclic reboot. It works for 2-3 sec and reboots. ANd i cant even look at settings or enable debugging. 2sec and reboot. One thing i'm shure its not from overheating =(
upd:
ok... boot in safe mode gives me 2 extra seconds.. and... there is no developers menu. it is locked. and i cant unlock it.
Click to expand...
Click to collapse
Have you wiped everything properly ?

kirmaniarslan said:
Have you wiped everything properly ?
Click to expand...
Click to collapse
idk coz in the HOWTO there is only "do a factory reset". What is the proper way?
Upd: for me it looks like overclock problem =)

kodirovshchik said:
idk coz in the HOWTO there is only "do a factory reset". What is the proper way?
Upd: for me it looks like overclock problem =)
Click to expand...
Click to collapse
Try the boot.img inside the ROM then. But it should not behave like that. Wipe the system along with the factory reset.

I'm having problems with TWRP v 2.8.0.0 recovery. I was using clokwork before and after flashing my log gets spammed with couldn't mount emmc. Adding full log
Adding link to pastebin, because for some strange reason I got error in forum that file was invalid
http://pastebin.com/iRgFm13z
Sorted out this issue, but rom seems to be stuck on bootloop.
Added logcat

doweeez said:
I'm having problems with TWRP v 2.8.0.0 recovery. I was using clokwork before and after flashing my log gets spammed with couldn't mount emmc. Adding full log
Adding link to pastebin, because for some strange reason I got error in forum that file was invalid
http://pastebin.com/iRgFm13z
Sorted out this issue, but rom seems to be stuck on bootloop.
Added logcat
Click to expand...
Click to collapse
Could you try image packaged with the ROM? Seems that I must leave HTC Performance boot lock, as a lot of phones crash.

h1gh1 said:
Could you try image packaged with the ROM? Seems that I must leave HTC Performance boot lock, as a lot of phones crash.
Click to expand...
Click to collapse
Thanks. Got it booted

doweeez said:
Thanks. Got it booted
Click to expand...
Click to collapse
OK. Will post another test kernel image once I fix the boot performance lock.

h1gh1 said:
Try the boot.img inside the ROM then. But it should not behave like that. Wipe the system along with the factory reset.
Click to expand...
Click to collapse
Ok. For me "How to install" must looks like:
1. Install the recovery trough fastboot
2. Reboot to recovery from fastboot
3. install zip
4. reboot to bootloader
5. Install boot image
6. reboot
Mb is is caused by S-OFF, but I rly need to flash kernel only after flashing zip. Work with "normal" kernel.
Upd1: Does ART works? Cause it looks like it works.
Upd2: OMG ART rly works. Can't belive it =)

kodirovshchik said:
Ok. For me "How to install" must looks like:
1. Install the recovery trough fastboot
2. Reboot to recovery from fastboot
3. install zip
4. reboot to bootloader
5. Install boot image
6. reboot
Mb is is caused by S-OFF, but I rly need to flash kernel only after flashing zip. Work with "normal" kernel.
Click to expand...
Click to collapse
Flashing the ROM does not affect boot partition, because of S-OFF. Order of instalation (boot image first) should not affect booting. I enabled zRAM kitkat style in latest build, as you requested - we are compliant with Google recommendations for low RAM devices now. I forgot to say, yes but ART is working without any problems, as long as apps work with it.

h1gh1 said:
Flashing the ROM does not affect boot partition, because of S-OFF. Order of instalation (boot image first) should not affect booting. I enabled zRAM kitkat style in latest build, as you requested - we are compliant with Google recommendations for low RAM devices now. I forgot to say, yes but ART is working without any problems, as long as apps work with it.
Click to expand...
Click to collapse
ART it's rly cool surprise =) Nice =)
As for S-OFF, i rly think u cant make changes with boot if u phone is S-ON. When u swith it to S-OFF u can make changes from recovery. Any way i have no other explanation, why order is important for me. i'll try to test it =)
UPD: is there any trick in win8 for adb? cause for me adb works only from my linux laptop.

kodirovshchik said:
ART it's rly cool surprise =) Nice =)
As for S-OFF, i rly think u cant make changes with boot if u phone is S-ON. When u swith it to S-OFF u can make changes from recovery. Any way i have no other explanation, why order is important for me. i'll try to test it =)
UPD: is there any trick in win8 for adb? cause for me adb works only from my linux laptop.
Click to expand...
Click to collapse
Yes, there is. Import this in your registry - you must have a patch with workaround installed, http://www.microsoft.com/en-pk/download/details.aspx?id=43515
extract reg file from attached zip and merge it to your registry.

I'm having problems with USB mass storage. First time when I click to turn it on, it unmounts sd card, but I'm not able to access sd-card file on PC. Second time I click loading loops forever.
Have anyone encountered similar problems?

doweeez said:
I'm having problems with USB mass storage. First time when I click to turn it on, it unmounts sd card, but I'm not able to access sd-card file on PC. Second time I click loading loops forever.
Have anyone encountered similar problems?
Click to expand...
Click to collapse
It's ums file setting, looks like it. I chose MTP as default, as mass storage requires mounting, unmounting etc... Will be fixed in the next build. Thx.

h1gh1 said:
It's ums file setting, looks like it. I chose MTP as default, as mass storage requires mounting, unmounting etc... Will be fixed in the next build. Thx.
Click to expand...
Click to collapse
MTP seems to work. It detects as HTC EVO 4G LTE .

{UPDATED}[RECOVERY][UNOFFICIAL]Red Wolf Recovery Project[09/07/2018][enchilada]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.2
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-8.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
4) password protection doesn't work.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-installer-enchilada-3.2.2-0.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-installer-enchilada-3.2.2-0.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery(MTP) for enchilada(OnePlus6)
RedWolf-Recovery(NO-MTP) for enchilada(OnePlus6)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
A big thanks to @joemossjr for fixing the issues with recovery not booting
@notsyncing on github for the fixes
@Titokhan for helping me with a and b
me for compiling and testing and fixing Haptic Feedback on RedWolf

So guys the builds and testing are finally done.
As told i have uploaded two builds with mtp and without mtp
Based on twrp 3.2.2 source
Bugs:
1)Flashlight doesnt work (only on recovery)
2)Aroma Installer doesn't work
3)If flashing MTP build, on boot if you enter wrong pattern it causes it to crash wherein you'd need to reboot by long pressing power button.
Fixed:
1) Vibration/Haptic Feedback has been fixed
2) encryption/Decryption now work
Glitches
1) Sometimes mtp doesn't work dircetly when booted into recovery. For MTP to work, once booted into recovery go to mount, and tap on disable mtp and then tap enable mtp.
2) When you select any option in reboot, it redirects to recovery. Do the same again and it will work
(For ex: you tap on reboot>system, it redirects to recovery. then again tap reboot>system it will work)
CREDITS
A big thanks to @joemossjr for fixing the issues with recovery not booting
also thanks to wuxianlin and Dees_Troy for the sources @notsyncing on github for the fixes
The Download links and Instructions will be updated in OP
Dated : 09-07-2018

Is Aroma Installer working?
Regards

Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work

Only for the One Plus 6? Any plans on expanding to other devices?

Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
It should, Not tried though

joemossjr said:
Lol I built this a few weeks ago
---------- Post added at 03:08 AM ---------- Previous post was at 02:52 AM ----------
encryption doent work
Click to expand...
Click to collapse
Damn I didn't notice that.... my bad
Updated for now in OP

jdmst77 said:
Only for the One Plus 6? Any plans on expanding to other devices?
Click to expand...
Click to collapse
That's not dependant on me mate

pranavasri said:
Damn I didn't notice that.... my bad
Updated for now in OP
Click to expand...
Click to collapse
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?

joemossjr said:
Np it's probably due to the 7.1 branch your using btw why are you using the 7.1 branch again?
Click to expand...
Click to collapse
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )

pranavasri said:
their 8.1 sources gave issues while compiling(probably due to device sources, so i went with 7.1 source )
Click to expand...
Click to collapse
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol

joemossjr said:
Ah. Yeah that's where you messed up what was the errors? I've got about every single one lol plus the 8.1 branch has the proper decryption for us lol
Click to expand...
Click to collapse
Shall i PM

pranavasri said:
Shall i PM
Click to expand...
Click to collapse
I'll do you one better hit me up on Hangouts @ [email protected]

Eliminater said:
Is Aroma Installer working?
Regards
Click to expand...
Click to collapse
No, aroma is not working and even core functionality like decryption of the data partition don't work.

xXx said:
No, aroma is not working and even core functionality like decryption of the data partition don't work.
Click to expand...
Click to collapse
Chill man we will get it working

is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri

virtyx said:
is DM verity and force encrypt disabled? how'd you achieve this? is it only for installing rom after recovery? (format data) or another way?
can you please explain @pranavasri
Click to expand...
Click to collapse
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question

pranavasri said:
I wouldn't say they are disabled but yes they might not work, (looks like it's because i've used nougat source) i didn't get thelast part of your question
Click to expand...
Click to collapse
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.

@pranavasri
Thank you for sharing.
I'm gonna give it a try!

pranavasri said:
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.
Based on TWRP version: 3.2.1
For device: Enchilada
Features
Translated to EN & CZ
- Password protection
- Flashlight(Currently Broken)
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
* Changes for security reasons *
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated TWRP theme engine
Some differences
- get out of here if you are pirating apps. this recovery is not for you
- compiled on omnirom-7.1 source
- There isn't bug with reboot from recovery to recovery
Changelog
Code:
Initial Build
Bugs
-Mtp removed (same reason as for the official build)(only in recovery)
-flashlight doesn't work
-encryption doesn't work. thnx to @joemossjr for letting me know
******************Installation Instructions******************
1)Flashing through a Custom Recovery
- Download the RedWolf-recovery-installer.zip
- Copy the zip to your phone's internal storage
- Flash the zip and you're good to go
2)People who don't have any custom recovery(through fastboot)
- Download both RedWolf-recovery-installer.zip & RedWolf-027-Unofficial-enchilada.img into your pc.
- Copy RedWolf-recovery-installer.zip to the internal storage of your phone.
- In PC go to the dir where you downloaded the RedWolf-027-Unofficial-enchilada.img
-Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here (or) open powershell here
- Now switch off your phone, connect your phone to pc using the original cable provided.
- Press power button + vol up button to boot into bootloader.
- In thecmd on your pc type :
Code:
fastboot boot RedWolf-027-Unofficial-enchilada.img
- In a few moments your phone will boot into RedWolfRecovery.
- Once booted into recovery immediately press install and locate the redwolfinstaller zip that you copied into your phone and flash it.
- Wait for it to Flash.
- and you've successfully flashed RedWolf-Recovery
DOWNLOADS
RedWolf-Recovery for enchilada(OnePlus6)
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery.
Sources:
DeviceTree
RedWolf
Credits: @dees-Troy && @wuxianlin for their sources
OMNI rom for twrp
RedWolf Team for the RedWolf source
@Titokhan for helping me with a and b
me for compiling and testing
Click to expand...
Click to collapse
If I don't like or want to revert back to TWRP can I flash TWRP from within red wolf?
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
virtyx said:
firstly we need a TWRP with decrypt possible for us to disable encryption
and also the ability to edit the fstab in /vendor partition (/vendor/etc/ there are 2 fstab files we need to edit and remove force encrypt to encryptable)
i have tried this with official twrp and didnt work
i cant seem to mount /vendor as R/W in OS or TWRP my changes dont stick for some reason.
Click to expand...
Click to collapse
As far as decrypting in TWRP check my post here. https://forum.xda-developers.com/showpost.php?p=76845815&postcount=14
I was able to do it. Here's the whole thread. https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112

[RECOVERY][RMX2061][Unofficial]TeamWin Recovery Project [3.5.X]

TeamWin Recovery Project
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
TWRP is FREE SOFTWARETwo versions: for RUI1 (Android 10) and for RUI2 (Android 11)
Features:
• Fastbootd is working;
• Decryption is working
• Using custom themes and fonts (special thanks to [email protected])
• Added custom patches in the Advanced settings (special thanks to [email protected]):
- SafetyNet fix patch
- Google Pay fix patch
- Patch for mount System and Vendor as r/w
• AVB2.0 (vbmeta) disabling special (thanks to [email protected] for his patch)
• Fix stock .ozip installation
• Patch to conversion of dynamic partitions to r/w (special thanks to @lebigmac for his script. Original thead)
• Patch to fix Magisk on RUI2
Download:
From Google Drive https://drive.google.com/drive/folders/1xerR8NmCNEoR1afh4dfbyrLz0ZOuWZPp?usp=sharing
Spoiler: Screenshots
Spoiler: Guides
Spoiler: Convert any ROM to r/w
How to convert ROM to R/W
The process below describes how to transfer the entire firmware to R/W (the ability to change/delete/add files in the system partitions: system, vendor and others ..).
All actions are carried out in TWRP itself i.e. on "live".
Your data is not affected.
Required for a successful conversion:
* free space on the internal memory of at least 25GB.
* charged battery (preferably at least 40%)
The process itself is not complicated:
1. Make
backup a Super partition (optional)
2. Go to the "Advanced" section and select "Convert ROM to RW".
3. In the next window, confirm with a swipe.
4. That's it, we are waiting ... about 5 minutes ...
5. After all the actions, the device will reboot itself into the system ...
6. Go to the explorer with root rights and delete the /data/local/tmp/makesysrw_[version] (/data/media/makesysrw_[version] for Android 11) folder, or do it in the TWRP explorer
To access the system partitions, respectively, you need root rights and a file manager with the ability to mount partitions in r/w.
The test was conducted on RealmeUI 1 A.45 and RealmeUI 2 C.15. But there is no difference, it is possible to convert any Android 10-11 ROM to r/w.
Changelog - current version (Android 11):
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
INSTALLATION
via TWRP-based recovery:
Download the TWRP IMG file to your device
Reboot to your custom TWRP-based recovery
Install the TWRP img file as image in recovery partition
Reboot into recovery after installation
Enjoy!
via fastboot:
Download the TWRP IMG file to your PC
Reboot your device to fastboot mode
Install the TWRP image with command:
Code:
fastboot flash recovery [image name].img
Reboot to recovery with the command:
Code:
fastboot reboot recovery
Enjoy
Notes:
• Installation of OTA packages not working
• ADB doesn't work in fastbootd mode only
CREDITS
• TeamWin - for TWRP
• brigudav - for his TWRP customization
• @lebigmac - for his makeSystemRW script
Version Information
Status: Stable
Current version: 3.5.2_10-1 (Android 10) / 3.5.2_1011-3 (Android 11)
Created 2021-03-18
Last Updated - 2021-09-03

CHANGELOGS
Spoiler: Android 11
Spoiler: 2021-09-03 (3.5.2_1011-3)
• Fixed decryption /data on realmeUI 2.0 (all versions)
• Enabled some patches in the Advanced section
• Updated Magisk and some patches
• Edits in the TWRP interface by @brigudav
• Removed the code that could break the formatting /data
• Updated sources
• And other changes that I forgot...
Spoiler: 2021-05-03 (3.5.2_1011-2)
• Fixed the installation of some ROMs
• Fixed fastboot (it was broken in the last build)
Spoiler: 2021-05-01 (3.5.2_1011-1)
• Disabled non-working patches in the Advanced section
• Enabled the install/remove Magisk feature in the Advanced section
• Added a boot repackaging patch with an oplus.fstab fix for Magisk (now after applying this patch, Magisk booted correctly on RUI 2)
• A small fix under the hood
Spoiler: 2021-04-29 (3.5.2_1011-0)
• Initial build
Spoiler: Android 10
Spoiler: 2021-04-23 (3.5.2_10-1)
• Universal patch disabling vbmeta by [email protected] (thanks to him for the patch)
• Now the internal storage after formatting /data is available without rebooting
• Minor changes in device tree (some libs are now taken from sources, small changes in the fstab, unnecessary system.props and flags are removed, edits in translation)
• Updated and fixed the script for converting firmware to R/W (now temporary files are deleted automatically when the conversion is successful)
• Added logcat copying
• Updated magisk to Canary 22104 (21) in which the SafetyNet check works correctly.
• Languages: Added Indonesian language [android_bootable_recovery]
• Change the missing logical partitions from LOGERR to LOGINFO [android_bootable_recovery]
Spoiler: 2021-04-05 (3.5.2_10-0)
• The list of Firmware-Update partitions for backup is finally changed (It is recommended to delete old "Firmware" backups and make new ones #2)
• Fix a regression error for digest checking [android_bootable_recovery]
Spoiler: 2021-03-30 (3.5.1_10-1)
• Added conversion of dynamic partitions to r/w (see Guides). Special thanks to @lebigmac for his script. Original script thead
• In the Mounting settings you can now mount System and Vendor r/o and r/w (if the partitions are in r/w). Taken fromTWRP by brigudav for Poco X3
• Returned the reboot menu from TWRP 3.3.x. Taken from TWRP by brigudav for Poco X3
• Changed the list of partitions for Modem backup. It is recommended to delete old backups and make new ones
• Changes in languages
• Other changes under the hood
Spoiler: 2021-03-18 (3.5.1_10-0)
• Initial version

Reserved

Can i use this recovery for Flash Android 11 custom roms?

Ayushmak said:
Can i use this recovery for Flash Android 11 custom roms?
Click to expand...
Click to collapse
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2

Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com

Yes you can install it... 'cause i would try.. on RR rom

Zgadnijcie said:
Somebody knows on which RUI is based RR from this thread? There is only "Based on: AOSP". So can I install this twrp or not?
[ROM][10.0] Resurrection Remix v8.6.3 [RMX206X, UNOFFICIAL]
Please Give Update A11 based RROS...
forum.xda-developers.com
Click to expand...
Click to collapse
All Android 10 Custom ROMs based on RUI1. Yes, you can install TWRP

Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the official project thread

lebigmac said:
Good job Ctarchik!
If anyone is looking for more information about my make system RW script here is the
Click to expand...
Click to collapse
Hi, I took this patch from TWRP by brigudav. I didn't find any mention of the creators anywhere other than brigudav, just "Make System to RW for Poco X3". I am always for the preservation of copyright and always indicate the developers of the program. I apologize to you for not finding your original official project thread. I would like to use your script for my recovery, of course, with the condition of saving the author and specifying a link to the original post...

Ctarchik please feel free to use latest version of my script in your project. The more people have system r/w access the better for the open source community.
@brigudav rather than hacking my update-binary and replacing my program's title (!!!) with your own meaningless words and torturing my script's comments section by modifying and removing the original script name, original author name, original version, link to original project homepage, disclaimer, credits, manual and automatic installation instructions, usage examples, (and much more...) I would suggest to try to improve the underlying algorithm of the script itself. And NO that does NOT mean simply renaming my variables and my functions and changing their order as well as injecting your bogus useless function that does absolutely nothing (...)
Please don't be such a lazy ruthless hacker without any morals or respect! Thank you! You have been caught red handed as a cyber thief and now the only right thing to do is to admit your guilt, beg for pardon and STOP IT! Please stop stealing my work and releasing as your own okay? That's just very very wrong on so many levels!
I clearly stated in my disclaimer that by using my script you agree to not abuse my work for criminal illegal purposes. And what you're doing is a perfect example of copyright infringement as well as intellectual property theft which is illegal even in Russia. Don't forget that!

Can you mod this twrp so I can use external sdcard to backup?
Thank you!
Super Partition backup fails when using FAT32 stick (exFAT works) · Issue #143 · TeamWin/android_bootable_recovery
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com

Ctarchik said:
Yes, if you already have installed the RUI1 or ROM's based on RUI1.
You cannot boot the TWRP if you on RUI2 or ROM based on RUI2
Click to expand...
Click to collapse
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11

beaker2 said:
I had to google to know what RUI1 and RUI2 meant - RUI1 is Realme UI 1.0 which is based on Android 10 - RUI2 is Realme UI 2.0 based on Android 11
Click to expand...
Click to collapse
Yes, it is. I just shortened RealmeUI to RUI

The problem I have been having is when I previously installed TWRP on my phone using ADB to install- patched_vbmeta-2 and then TWRP. I could reboot from ADB into recovery to TWRP, but then when I tried to reboot into system I was in a boot loop and phone would only go back to the stock recovery . Then I had to re flash the stock rom to get out of the boot loop and be able to boot into system again.
So can I do the same install from ADB as before but when I reboot , from ADB, into TWRP then I can install this TWRP then I can have the ability to boot into the stock ROM system . Then I could go to recovery and TWRP will still be there so that I could install a custom ROM ?
Thanks in advance, I'm a noob with this phone and its partitioning

Well, I tried the installation described above, installed TWRP from ADB then when booted and rebooted into TWRP and flashed this version of TWRP, seemed fine no errors BUT... the phone just returned to the stock recovery .
Then I tried exactly as described in this thread no error message and all seemed to go smoothly BUT... The phones internal memory was unreachable from any file manager or computer and the stock recovery returned not TWRP. Had to re-flash the phone several times, 1. stock recovery 2.from update 3.from flash tool, to finally get the internal phone memory visible again.
My phones build number is RMX2061_11_A49. Has anyone successfully installed TWRP on this build ?
How?

1. Prevent replacing TWRP:
Flash this file in Advanced Menu in the first time you go in TWRP.
2. Decrypt userdata: do them in order
- Flash this file:
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip | by Droidwin for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
- Wipe / Format Data / yes
- Reboot to TWRP again
- Advanced / Fix AVB
- Reboot to System
Done!
P.S.: You will lost all data after this.

No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery

beaker2 said:
No, that didn't work. Kept getting -twrp error 1- when flashing the Disable dm verity forceencrypt file.
Tried several times.
Tried reinstalling the stock boot.img then installing same error 1
Tried reinstalling the stock rom installing twrp then flashing disable varity same error 1
Tried ignoring the error and going to fix AVB still no luck
Everything I tried it still just returned to the stock recovery
Click to expand...
Click to collapse
Try flash magisk before reboot system

nttuan said:
Try flash magisk before reboot system
Click to expand...
Click to collapse
I gave up and installed Magisk 23 and rooted. I just decided to live with the stock rom (debloated) and the stock recovery

[ROM][11.0][Tissot][OFFICIAL] crDroid v7.17 [13.04.2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 21.2 or newer for root (after first boot) - (Download from here)
First time installation:
Download twrpboot.img & twrp.zip in your pc (link above) and extract zip file
Hotboot twrp from your pc with command fastboot boot boot-recovery.img
Wipe system wipe data wipe dalvik cache
Copy downloaded rom from pc to your phone and start the installation
After installing flash twrp.zip and reboot to recovery again
Install gapps & magisk (optional) and then reboot your phone
Profit! (Enjoy your rom)
Update installation:
You can choose to update via seamless ota or use recovery mode method
For recovery update method:
Reboot to recovery from phone
Flash Rom.zip & Twrp.zip and reboot to recovery
Flash Gapps
Flash Magisk (optional) & reboot your phone
Profit! (Enjoy your rom)
Sources:
ROM Source: https://github.com/crdroidandroid
Kernel Source: https://github.com/neonmicky/kernel_xiaomi_tissot.git
Download:
ROM: Click HERE
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/11.0/changelog_tissot.txt
Known issues:
None !
Visit official website @ crDroid.net
crDroid Mi A1(Tissot) Telegra
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

Reserved

Reserved

Crdroid for Tissot reborn!!! Thank you very much man!!!

Good rom

Thank you neonmicky! Updated seamlessly and for the first time ever with my Mi A1 wifi calling actually works.

New Build 20210810 is Up
Changelog:
- Initial crDroid 7.9 code base
- Updated to August security patches (android-11.0.0_r40)
- Merged LA.UM.9.6.2.r1-04800-89xx.0 CAF Tag in Kernel , Audio and Wlan Drivers
- Added option to instantly/15 seconds/screen off lock app on closing for AppLocker (Settings -> Security -> App locker)
- Updated translations
- Misc Changes and Fixes

Thanks for the good work.

You have any plan support for Mi max 2 offical?

I dirty updated from 7.4 to 7.9 a week ago. It's working nice here. No freezes and no bugs. But call recording doesn't record anymore which is a problem for me. Does it work for somebody?
I use Magisk + Axet's Call Recorder

Just updated to this ROM. Everything is fine and smooth but when I enable Wi-Fi Calling, the person on the other hand can't hear me, but I can hear them.
Anyone else facing this issue or know how to resolve this?

hamishnichol said:
Thank you neonmicky! Updated seamlessly and for the first time ever with my Mi A1 wifi calling actually works.
Click to expand...
Click to collapse
Wifi Calling isn't working for me on my MiA1? Did you do any other settings besides turning Wifi Calling ON?

New Build 20210925 is Up
Changelog:
- Updated to September security patch (android-11.0.0_r43)
- Redesigned notification media player
- SafetyNet fixes and improvements
- Selected custom fonts now applies system wide and also in apps (except for apps that hardcode the fonts used)
- Updated translations
- Misc changes and fixes
Download: HERE
OTA pushed for existing users

neonmicky said:
New Build 20210925 is Up
Changelog:
- Updated to September security patch (android-11.0.0_r43)
- Redesigned notification media player
- SafetyNet fixes and improvements
- Selected custom fonts now applies system wide and also in apps (except for apps that hardcode the fonts used)
- Updated translations
- Misc changes and fixes
Download: HERE
OTA pushed for existing users
Click to expand...
Click to collapse
Thanks for the good work.

I am experiencing a bootloop when installing open gapps after the crDroid image.
Could this be due to my procedure?
I boot into fastboot.
Then:
Code:
fastboot flash boot twrp-3.5.2_9-0-tissot.img
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
Wipe the data. I also proceed the step in which I have to confirm with typing "yes".
Then I activate adb sideload, with whom I call
Code:
adb sideload .\crDroidAndroid-11.0-20210925-tissot-v7.10.zip
When I reboot now, everything is fine. But I would like to have a minimal set of gapps. Therefore with the same procedure without restarting after (4) I install the open gapps package (open_gapps-arm64-11.0-nano-20210929.zip).
Installation proceeds and is successful.
restart
I endlessly see horus' eye flashing in colors...
Any advice what I can try else?
further notes:
also tried pixel experience ROM, which is working fine (but here is no need to install gapps in addition because they are included). I decided against using it because it is bloated somehow, crDroid seems lighter to me.
also tried LineageOS but did also experience the bootloop. Here it was in bootloop also without installing the gapps

The rom works pretty well so far, the latest update to remove blur effect really helps the smoothness a lot! Running it without gapps.
The two issues I've had is volume often spiking when using headphones (basically when moving forward and backwards in songs/videos), and the display turning on to show the clock very often, even if the phone isn't touched or moved (this one is very minor since there was some setting to disable this behavior).

Build date2021-10-17
Updated flawlessly.
Call recording is working again (Magisk & Axet call recording) Great!!!!!
Hey Google not available. Voice match doesn't work? It's only on my phone?

Great ROM. All is working perfect.
Rubén

Flying Pizza said:
I am experiencing a bootloop when installing open gapps after the crDroid image.
Could this be due to my procedure?
I boot into fastboot.
Then:
Code:
fastboot flash boot twrp-3.5.2_9-0-tissot.img
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
Wipe the data. I also proceed the step in which I have to confirm with typing "yes".
Then I activate adb sideload, with whom I call
Code:
adb sideload .\crDroidAndroid-11.0-20210925-tissot-v7.10.zip
When I reboot now, everything is fine. But I would like to have a minimal set of gapps. Therefore with the same procedure without restarting after (4) I install the open gapps package (open_gapps-arm64-11.0-nano-20210929.zip).
Installation proceeds and is successful.
restart
I endlessly see horus' eye flashing in colors...
Any advice what I can try else?
further notes:
also tried pixel experience ROM, which is working fine (but here is no need to install gapps in addition because they are included). I decided against using it because it is bloated somehow, crDroid seems lighter to me.
also tried LineageOS but did also experience the bootloop. Here it was in bootloop also without installing the gapps
Click to expand...
Click to collapse
Follow the Flashing Instructions

neonmicky said:
Follow the Flashing Instructions
Click to expand...
Click to collapse
Thanks for not helping me. I do... I described it.
Do you see any errors in the procedure?

[OFFICIAL][zippo] LineageOS 20 (Android 13) for the Lenovo Z6 Pro

{
"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"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
SUPPORTED DEVICES
- zippo (L78051)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
Please NOTE! As of LineageOS 19.1? We do NOT support bootloader locked! You MUST unlock your bootloader to use this version!
- Make sure your phone is running firmware from at least CN 12.5.332. If not? Please download and install it via recovery. It can be flashed before the ROM
If you want to follow the official instructions for bootloader unlock? Please go to the LineageOS Wiki here:
https://wiki.lineageos.org/devices/zippo/install
If you want to preserve a locked bootloader? Download and follow the instructions in this zip and then follow the official wiki instructions but skip the bootloader unlock section.
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official instructions on the LineageOS Wiki here:
https://wiki.lineageos.org/devices/zippo/update
HOW TO INSTALL LINEAGEOS WITH TWRP
Please NOTE! As of LineageOS 19.1? We do NOT support bootloader locked! You MUST unlock your bootloader to use this version!
- Make sure your phone is running firmware from at least CN 12.5.332. If not? Please download and install it via recovery. It can be flashed before the ROM
- Download the LineageOS and firmware zips. (see Downloads)
- Boot into TWRP.
- Copy the downloaded zip files to the internal storage of the device.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: Do a factory reset (clean wipe)! No support if you didn't! (Wipe Dalvik, system, cache and format data)
- NOTE: If coming from stock ROM? You MUST format data (Wipe > tap "Format Data" button > type "yes" > keyboard checkbox)
- Flash firmware and LineageOS zips.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot to system.
HOW TO UPDATE LINEAGEOS WITH TWRP
- Download the LineageOS zip(s). (see Downloads)
- Copy the downloaded zip files to the internal storage of the device.
- Reboot to TWRP.
- Flash LineageOS. (Wiping Dalvik and Cache is optional, but recommended)
- Reboot to system.
MAIN DOWNLOADS
TWRP for zippo: Official
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Lineage:
- Official:
LineageOS Downloads
download.lineageos.org
- Unofficial:
Package lineage-20 - lineageos-for-zippo - OSDN
Package lineage-20 - lineageos-for-zippo #osdn
osdn.net
GOOGLE APPS (GAPPS) DOWNLOADS
- MindTheGapps:
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
Recommended version:
https://www.celsoazevedo.com/files/android/google-camera/dev-wichaya/f/dl5/
Recommended config:
https://osdn.net/projects/lineageos-for-zippo/releases/76575
FIRMWARE DOWNLOADS
Minimum required versions:
- zippo (L78051) CN 12.5.365
https://osdn.net/projects/lineageos-for-zippo/releases/p17514
DEVELOPER RESOURCES
https://github.com/lenovo-sm8150/local_manifests/
GitHub - LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_lenovo_zippo
Contribute to LineageOS/android_device_lenovo_zippo development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_lenovo_sm8150
Contribute to LineageOS/android_kernel_lenovo_sm8150 development by creating an account on GitHub.
github.com
HOW TO CONTRIBUTE
Send your patches up for review: https://review.lineageos.org/
Read the guides on the LineageOS Wiki: https://wiki.lineageos.org/
Source Code: https://github.com/LineageOS
DONATIONS
Pay Marc Bourgoin using PayPal.Me
Go to paypal.me/ThEMarD85 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com

KNOWN BUGS
Currently only works with bootloader unlocked
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Fingerprint icon is too low compared to actual location of the scanner
Heyyo, allow me to introduce myself. I am Marc "ThE_MarD" Bourgoin and I maintain LineageOS and TWRP for the LeEco Le Max 2 (X2) and was crowdfunded a zippo which I will maintain LineageOS for (with selinux enforcing of course) and maybe assist with TWRP later. I also own a Motorola Edge 30 (dubai) which I maintain LineageOS for, Asus Zenfone 5z (Z01R), and I was also donated a Motorola Moto X4 (Payton) which I maintain LineageOS and TWRP for.
I'd like to take this moment to also thank anyone who donated to the crowdfunding campaign for my zippo! Without you? I wouldn't have this epic device in my hands to work on.
Also MAJOR thanks to Zhenxiang Chen (aka pasta_con_tonno, Lucchetto) for all the amazing work he has done on zippo.
Special thanks to Einar Gednochsson (aka kanstmablason, pete80pro) for organizing the crowdfunding campaign for my zippo and also a new one for KuranKaname so he can revamp our kernel.
Thanks also to hypnz, chema f, gawin and Lucky for also working in zippo and to HighwayStar who started the initial trees for heart (Lenovo z5 Pro GT) which zippo trees are based upon and Art_Chen for working on heart and zippo and also bringing us FOD Dimming and DC Dimming.
Thanks again to Zhenxiang and Chema f for figuring out and implementing the QFIL recovery and vbmeta while keeping the bootloader locked

Heyyo, LineageOS 20 official is out and the first build for zippo is up!

@ThE_MarD ,
Will you be including this commit the hardware fix/support for the camera (camera: Expose aux cameras in third party apps) from Chemas Evo build in your Lineage build? I'd rather not have google services installed to use GCAM in order to access the other lens' and the ZUI camera does not install correctly anymore for 13 (it did for 12, partially). There are other apps that don't rely on g-services that are able to access the hardware (HIDL?) switch to select which lens is used for image processing.

Heyyo @project_2501 , after checking with other devs about that commit and also how aux cameras are set up? I think for that we can just modify our props in the device tree tbh. The problem we currently have is we are limiting it to only a few app names. We could transition to an aux camera blacklist since there's probably only a handful of apps that would screw up (I can't remember if it was here or my Asus Zenfone 5z, but the Adobe Scan app would screw up and fail to initialize any camera) so we could just tackle a blacklist as crappy apps show up lol
As you can see here, we mainly expose aux cameras to a few apps and others have to essentially find out themselves like gcam mods
android_device_lenovo_sm8150-common/system.prop at lineage-20 · LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com

@ThE_MarD ,
Will the blacklist instead of a whitelist be applied on the next scheduled build? Thank you for addressing it.

@project_2501 sorry not yet as I need to test it first and I haven't had time yet

Heyyo, lineage-20.0-20230122-UNOFFICIAL-zippo test build is going up! ! It has a new rebased kernel by MikeNG. Please test all functions. It also has a change to swap the aux camera allowed list to an aux camera exclude list to keep things easier and only exclude apps that don't play well with aux cameras so please test a lot of camera apps
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo - OSDN
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo #osdn
osdn.net
@project_2501 if you could please test this build. You can swap between unofficial and official builds at any time

Switching between the camera lens' works (still don't see 48mp for the main lens' resolution); install almost hanged on patching vendor which I found odd. Camera app believes there are six cameras for some odd reason and will crash if selecting the sixth camera, I'm guessing it's also referencing the video profile because it doesn't crash in video mode when selecting the sixth camera (dual lens for video or mixed up with front lens' maybe)? Can you provide a link to the source for the kernel?

@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there

ThE_MarD said:
@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there
Click to expand...
Click to collapse
Open Camera.
I'm unfamiliar with MikeNG and kernel modifications he may have committed when looking at the source code for the kernel, just wondering since you stated it was using a different kernel (than official LOS?).

@project_2501 oh, Open Camera does things a lot differently than other camera apps so tbh I don't think there's a way to configure it... So I'd recommend just sticking with Aperture or use a gcam mod... But from what you said Open Camera is now seeing more camera apps so the change in aux camera lists commit is working then?

@ThE_MarD , yes I can switch between all the lens'. System stability has not been jeopordized, the app will just crash if trying to process from the sixth camera ID. Do you remember what modes the ZUI camera app had? Was there a dual (both front and back camera) mode? Maybe the sixth profile is for the front camera and the app doesn't switch to it when cycling through the lens' (front camera can still be accessed with a different on screen UI switch anyways). The problem in itself is app related; regardless, the commit works and should be included in the next build for others like myself who enjoy a clean minimalist build with full access to the hardware.

Hi, i'm on firmware 11.0.405 ST.
Now i'm still waiting my SN from Lenovo to unlock bootloader.
Newbie question:
After installing TWRP --> Wipe > tap "Format Data" button > type "yes" > keyboard checkbox > Flash firmware CN 12.5.332 > reboot to recovery or reboot to system ?
Thanks a lot for the rom!

Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.

ThE_MarD said:
Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.
Click to expand...
Click to collapse
@ThE_MarD , thanks for the reply. Appreciated
I'm still waiting file from Lenovo to unlock bootloader.

Finally got the file to unlock bootloader.
I flashed twrp > shut down the phone > hold Volume Up + Power > but it cannot boot to recovery, only show fastboot/bootloader.
Then I tried I flashed twrp > shut down the phone > Volume Down + Power > fastboot mode > then i select recovery mode > phone restarted > only returned to fastboot mode again.
Any help to solve this problem? failed to flash twrp recovery.
Thanks in advance.

@danz852 just to check, you're flashing it to the recovery partition?
The TWRP website has the full instructions too
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Code:
fastboot flash recovery twrp.img
Otherwise you can try first via Lineage Recovery and follow the LineageOS wiki instructions
Install LineageOS on zippo | LineageOS Wiki
wiki.lineageos.org

Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.html to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.

danz852 said:
Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.htmll to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.
Click to expand...
Click to collapse
UPDATE:
Finally it worked out:
I'm still using TWRP 3.4.0. Copy firmware L78051_CN_11_5_229_Q_Stable_recovery to internal storage then flash it. Reboot to System. It said my phone partition is corrupted .
Then i reboot the phone to Fastboot mode. I checked bootloader is Locked > proceed with fastboot flash unlock sn.img > fastboot oem unlock-go > reboot to system. After enable USB debugging in Developer Option > reboot to recovery > Wipe Dalvik, system, cache and format data > flash CN 12.5.332 and LineageOS. > reboot to system > Finally it booted to Lineage.
I'm happy. Thanks again @ThE_MarD for the rom!!!

Database Develop

welcome