Database Develop

Decryption and F2FS

This thread should be deleted.
Hello together,
as I wanted to see if I get F2FS and decryption running, I want to share my progress and exchange with others.
I got both working but there are a few issues once the system is running, at least if decrypted. When encrypted, everything seems running nice on f2fs.
Here's what I did:
ENABLE F2FS AND DISABLE ENCRYPTION (IF NEEDED)
1. Flash full fastboot rom to make sure everything is clean
2. Boot to stock recovery and wipe /data so it gets cleanly formatted as ext4 (not really needed)
3. Boot and install TWRP (blu_spark) and reformat /data as f2fs
I chose latest blu_spark recovery as I think it's more stable and I don't need recovery decryption for this matter
4. Reboot to recovery
5. Flash custom kernel with f2fs support or keep stock
blu_spark didn't work for me for some reason but Smurfkernel and ElementalX were fine, also STOCK KERNEL SUPPORTS F2FS BY NOW
6. Flash the universal dm-verity and forceencryption remover by zackptg5 found here
Only if you really need it! NOT RECOMMENDED AND NOT NEEDED FOR HAVING F2FS WORK
7. Flash Magisk v18.0
8. Reboot
9. Profit (or not)
Even if hard to believe with the already amazing speeds of the OP6/T, I think I could feel a little improvement in boot time and app opening times.
Update: I wouldn't recommend doing this as of now to anyone. Maybe results with an AOSP based rom are better (please try and report), but using OxygenOS in combination with currently available kernels, the system turns out unstable and is not usable reliably. There are different weird glitches etc. Do this on your own resposibility and please share if you make any progress making OOS and/or AOSP run stable (recovery versions, file patches, kernels, settings, etc). I'm not an Android developer myself.
ENCOUNTERED ISSUES
1. Can't use any unlock method. Deleting gatekeeper and locksetting files through TWRP works but setting a new PIN results in not being able to unlock again. The PIN is entered correctly but still it reports "wrong password". But actually it detects that the PIN is correct since it doesn't trigger a lockout time. Logcat occurences can be found below.
FIXED BY NOT DECRYPTING DATA (?)
2. On first boot there will be some app crashs and lags. They settle after a few minutes and one or two reboots.
ALSO FIXED BY NOT DECRYPTING DATA (?)
3. One time I had to reflash Magisk after the first boot
UNLOCK BUG LOGCAT OCCURENCES - HELP NEEDED!
Here are some logcat lines which I think are related to the unlock bug.
HTML:
E GatekeeperHalDevice: verify
E GatekeeperHalDevice: ret: 0
E GatekeeperHalDevice: resp->status: -24
E GatekeeperHalDevice: verify
E GatekeeperHalDevice: ret: 0
E GatekeeperHalDevice: resp->status: -30
I LockSettingsService: Device doesn't implement AuthSecret HAL
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.password.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/password.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)
E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)
E keystore: Changing user 0's password while locked, clearing old encryption
E JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
E JavaBinder: java.lang.RuntimeException: android.os.RemoteException: Non-OK response verifying a credential we just set: -1
E JavaBinder: at android.os.Parcel.writeException(Parcel.java:1779)
E JavaBinder: at android.os.Binder.execTransact(Binder.java:765)
E JavaBinder: Caused by: android.os.RemoteException: Non-OK response verifying a credential we just set: -1
E JavaBinder: at com.android.server.locksettings.LockSettingsService.setUserKeyProtection(LockSettingsService.java:1602)
E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1483)
E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1397)
E JavaBinder: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:141)
E JavaBinder: at android.os.Binder.execTransact(Binder.java:752)

Nice work, I discovered these very same errors while decrypting myself. I just flashed the dm verity disabler by zackptg after a format. Yeah same exact issues. I am on the fence whether I felt any difference in speed etc. Unfortunately it seems we need encryption for this device to offer any security, unlike previous phones that didn't have a/b partitions

jacksummers said:
Nice work, I discovered these very same errors while decrypting myself. I just flashed the dm verity disabler by zackptg after a format. Yeah same exact issues. I am on the fence whether I felt any difference in speed etc. Unfortunately it seems we need encryption for this device to offer any security, unlike previous phones that didn't have a/b partitions
Click to expand...
Click to collapse
You won't notice and difference in disabling encryption as it's hardware based now instead of software like on the Nexus's and then it was a slight performance increase nothing else.

jacksummers said:
Nice work, I discovered these very same errors while decrypting myself. I just flashed the dm verity disabler by zackptg after a format. Yeah same exact issues. I am on the fence whether I felt any difference in speed etc. Unfortunately it seems we need encryption for this device to offer any security, unlike previous phones that didn't have a/b partitions
Click to expand...
Click to collapse
Yeah well I updated the thread. Without decrypting everything seems running great until now, even with stock kernel which supports f2fs by now. Also, if someone really wants it decrypted, I updated the post with your method, the disabler by zackptg5, which I didnt know of until now (way easier, thanks)
Also thanks @liam_davenport for mentioning the hardware based encryption, didnt know of that as well.
This means: I'm perfectly happy. Encryption in place, f2fs working and no issues yet.

Lartsch said:
Yeah well I updated the thread. Without decrypting everything seems running great until now, even with stock kernel which supports f2fs by now. Also, if someone really wants it decrypted, I updated the post with your method, the disabler by zackptg5, which I didnt knwo of until now.
Click to expand...
Click to collapse
Good to share ideas man, that furthers the development of Android.

nevermind!

So twice now (the first was above, but it's easy, while incredibly annoying, to fix after a reformat, so I edited the post thinking it was a one-time thing) I've rebooted my phone with data as F2FS only to boot directly into recovery. TWRP doesn't ask me to decrypt; I get the error "init_user_0 failed." I have to reformat my SDcard to get out of this error.
I don't know how to get recovery logs without decrypted data. damn TWRP saves them in /data/media/0 which is useless since it's encrypted.
Another issue i encountered which may be related: I've woken my phone up to have my unlock method reset to "swipe" as if the pattern doesn't work anymore. I can reset the pattern no problems. I think the next reboot after this error happens is when you run into the bootloop.
So, users beware: You get some tasty performance improvements when you switch to F2FS, but one day later you may reboot and be ****ed.
Maybe some smarter people can get on board and figure this out. F2FS is definitely a faster file system for flash devices such as our internal sdcard.
EXT4 for now though!

Lartsch said:
Hello together,
as I wanted to see if I get F2FS and decryption running, I want to share my progress and exchange with others.
I got both working but there are a few issues once the system is running, at least if decrypted. When encrypted, everything seems running nice on f2fs.
Here's what I did:
ENABLE F2FS AND DISABLE ENCRYPTION (IF NEEDED)
1. Flash full fastboot rom to make sure everything is clean
2. Boot to stock recovery and wipe /data so it gets cleanly formatted as ext4 (not really needed)
3. Boot and install TWRP (blu_spark) and reformat /data as f2fs
I chose latest blu_spark recovery as I think it's more stable and I don't need recovery decryption for this matter
4. Reboot to recovery
5. Flash custom kernel with f2fs support or keep stock
blu_spark didn't work for me for some reason but Smurfkernel and ElementalX were fine, also STOCK KERNEL SUPPORTS F2FS BY NOW
6. Flash the universal dm-verity and forceencryption remover by zackptg5 found here
Only if you really need it! NOT RECOMMENDED AND NOT NEEDED FOR HAVING F2FS WORK
7. Flash Magisk v18.0
8. Reboot
9. Profit (or not)
Even if hard to believe with the already amazing speeds of the OP6/T, I think I could feel a little improvement in boot time and app opening times.
Update: I wouldn't recommend doing this as of now to anyone. Maybe results with an AOSP based rom are better (please try and report), but using OxygenOS in combination with currently available kernels, the system turns out unstable and is not usable reliably. There are different weird glitches etc. Do this on your own resposibility and please share if you make any progress making OOS and/or AOSP run stable (recovery versions, file patches, kernels, settings, etc). I'm not an Android developer myself.
ENCOUNTERED ISSUES
1. Can't use any unlock method. Deleting gatekeeper and locksetting files through TWRP works but setting a new PIN results in not being able to unlock again. The PIN is entered correctly but still it reports "wrong password". But actually it detects that the PIN is correct since it doesn't trigger a lockout time. Logcat occurences can be found below.
FIXED BY NOT DECRYPTING DATA (?)
2. On first boot there will be some app crashs and lags. They settle after a few minutes and one or two reboots.
ALSO FIXED BY NOT DECRYPTING DATA (?)
3. One time I had to reflash Magisk after the first boot
UNLOCK BUG LOGCAT OCCURENCES - HELP NEEDED!
Here are some logcat lines which I think are related to the unlock bug.
E GatekeeperHalDevice: verifyE GatekeeperHalDevice: ret: 0E GatekeeperHalDevice: resp->status: -24E GatekeeperHalDevice: verifyE GatekeeperHalDevice: ret: 0E GatekeeperHalDevice: resp->status: -30I LockSettingsService: Device doesn't implement AuthSecret HALE LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.password.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/password.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.pattern.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gatekeeper.gesture.key: open failed: ENOENT (No such file or directory)E LockSettingsStorage: Cannot read file java.io.FileNotFoundException: /data/system/gesture.key: open failed: ENOENT (No such file or directory)E keystore: Changing user 0's password while locked, clearing old encryptionE JavaBinder: *** Uncaught remote exception! (Exceptions are not yet supported across processes.)E JavaBinder: java.lang.RuntimeException: android.os.RemoteException: Non-OK response verifying a credential we just set: -1E JavaBinder: at android.os.Parcel.writeException(Parcel.java:1779)E JavaBinder: at android.os.Binder.execTransact(Binder.java:765)E JavaBinder: Caused by: android.os.RemoteException: Non-OK response verifying a credential we just set: -1E JavaBinder: at com.android.server.locksettings.LockSettingsService.setUserKeyProtection(LockSettingsService.java:1602)E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1483)E JavaBinder: at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1397)E JavaBinder: at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:141)E JavaBinder: at android.os.Binder.execTransact(Binder.java:752)
Click to expand...
Click to collapse
Hi, I have OnePlus 6t, when I flash the system clean the data section, then format it, flash the script from encryption, then the system boots to a new state, but because of the script, when I want to create a password, it is created, but immediately will not be true when you first start the phone or lock the screen. and I can't get over it, have you figured it out?

uhh186 said:
So twice now (the first was above, but it's easy, while incredibly annoying, to fix after a reformat, so I edited the post thinking it was a one-time thing) I've rebooted my phone with data as F2FS only to boot directly into recovery. TWRP doesn't ask me to decrypt; I get the error "init_user_0 failed." I have to reformat my SDcard to get out of this error.
I don't know how to get recovery logs without decrypted data. damn TWRP saves them in /data/media/0 which is useless since it's encrypted.
Another issue i encountered which may be related: I've woken my phone up to have my unlock method reset to "swipe" as if the pattern doesn't work anymore. I can reset the pattern no problems. I think the next reboot after this error happens is when you run into the bootloop.
So, users beware: You get some tasty performance improvements when you switch to F2FS, but one day later you may reboot and be ****ed.
Maybe some smarter people can get on board and figure this out. F2FS is definitely a faster file system for flash devices such as our internal sdcard.
EXT4 for now though!
Click to expand...
Click to collapse
Use adb while booted in twrp to pull recovery.
adb pull /tmp/recovery.log

uhh186 said:
So twice now (the first was above, but it's easy, while incredibly annoying, to fix after a reformat, so I edited the post thinking it was a one-time thing) I've rebooted my phone with data as F2FS only to boot directly into recovery. TWRP doesn't ask me to decrypt; I get the error "init_user_0 failed." I have to reformat my SDcard to get out of this error.
I don't know how to get recovery logs without decrypted data. damn TWRP saves them in /data/media/0 which is useless since it's encrypted.
Another issue i encountered which may be related: I've woken my phone up to have my unlock method reset to "swipe" as if the pattern doesn't work anymore. I can reset the pattern no problems. I think the next reboot after this error happens is when you run into the bootloop.
So, users beware: You get some tasty performance improvements when you switch to F2FS, but one day later you may reboot and be ****ed.
Maybe some smarter people can get on board and figure this out. F2FS is definitely a faster file system for flash devices such as our internal sdcard.
EXT4 for now though!
Click to expand...
Click to collapse
I get init_user0_failed randomly as well wish there was a fix
edit - reflashing ROM seems to get past it

Was looking at https://source.android.com/security/encryption/file-based and came across an idea,
It says it's possible to add exceptions to prevent certain directories from being encrypted.
In this manner, if the rom Dev is able to add exclusion to /data, isn't it possible that the device would work with pin set, on a decrypted op6t?

when i follow these steps OOS wont boot, it just forces back to recovery.

[Question] OTA Updates on rooted phone when /system was mounted RW

Hey,
according to the Magisk OTA tutorial (https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md) you should never RW mount the /system or /vendor partition. Otherwise a verification will be broken and OTA updates will fail.
I had to mount my /system partition in the past and now Android won't find any OTA updates.
Does anybody knows if there's a way to repair the verification so that OTA updates will be working again?
Thanks
Jas

You'll have to reflash at least the system image, or the entire factory image/firmware package/ROM. Depends on your device.

Don't update a rooted phone!
Sent from my SM-A605FN using Tapatalk

Didgeridoohan said:
You'll have to reflash at least the system image, or the entire factory image/firmware package/ROM. Depends on your device.
Click to expand...
Click to collapse
That was also my first thougt, but it seems not working.
I got my Pixel 3 in December. Right after the first boot it found and installed the December OTA without any problem. Then I rooted the phone with Magisk.
In January it didn't find any OTA. Therefore I've installed the factory image manually with fasboot. That was nearly at the end of January. I didn't RW mount the /system partition after then. But the phone is not finding the February OTA.
I've just flashed the whole January factory image again to be sure that the partitions are fine. But no luck.
When I install Magisk it mount the system partition to patch the image, I'm right? Do this break the verification too?
What else could cause that my phone won't find any OTAs anymore? According to a tcpdump the connection to the Google servers are fine.

Apologies, I did not read your post properly... That your device suddenly stopped recieving OTA has nothing to do with editing or mounting /system rw (Magisk does not alter /system at all, unless you have a ROM with addon.d and then it doesn't matter anyway). The issue with having an altered /system and OTAs will only manifest itself when you're actually trying to install the OTA (when it tries to verify the integrity of your device).
I've seen several reports of similar behaviour on Pixel devices and it might very well be related to rooting or modding your device, but I have not seen anyone presenting anything about what it could be caused by.

Good to know that I'm not alone
I've started catlog and every time I press the "Search for Updates" button I see the following errors:
Code:
02-09 14:57:03.215 813 7853 E DrmWidevineDash: tz api version = 14
02-09 14:57:03.215 813 7853 E DrmWidevineDash: OEMCrypto_APIVersion: ends! returns version 14
....
02-09 14:57:03.248 813 7853 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware_mnt/image/widevine.mdt errno = 13
...
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Cannot open the file /vendor/firmware/hdcpsrm.mdt errno = 2
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Loading image failed with ret = -1
....
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Cannot open the file /system/etc/firmware/hdcpsrm.mdt errno = 2
02-09 14:57:03.314 813 7853 E QSEECOMAPI: Error::Loading image failed with ret = -1
I'm not sure if this is related to the issue. I've also not found any hints or something like that.

JasMan78 said:
Good to know that I'm not alone
Click to expand...
Click to collapse
I'm not getting those errors in logcat, but you're definitely not alone; I haven't received any OTA updates on my Pixel 2 since I flashed the Pie factory image in August 2018. Prior to that it all used to work fine on Oreo.
As per a previous post of mine, I found other reports of the same issue and the common factors seemed to be Pixel devices, Pie and Magisk.
I'd love to help track down the cause of the problem but I wouldn't know how, other than posting a logcat recorded during a check for updates. Anyone have any ideas?

JasMan78 said:
Good to know that I'm not alone
I've started catlog and every time I press the "Search for Updates" button I see the following errors:
I'm not sure if this is related to the issue. I've also not found any hints or something like that.
Click to expand...
Click to collapse
That is to be expected and should not prevent you from getting ota updates. The missing file is your devices L1 widevine cert. Widevine is Google's DRM software and just unlocking your bootloader causes that file to disappear. But it's done by the software on the device (I think something in trustzone does it but don't quote me on that), not by Magisk or anything you did in rooting.
That file being missing is why rooted phones can't seem HD content from Netflix

I've updated my phone to Android 10 and Magisk Canary last month. Today I got my first notification that a new OTA is available.
I've installed it successfully (restored the original boot image in Magisk, installed the OTA update and installed Magisk into the inactive slot. Reboot. Done.).

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |

{
"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"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
Note - According to HMD global Nokia 7 Plus launched in 2018 march with Oreo out of the box.
Well in my official twrp thread one of my user posted a photo during when he tried to boot twrp of mine on his Nokia 7 Plus phone turns in to white screen with some lines & he underlined that his phone having different display ( pure display ) . According to HMD employee He undelined that " they changed the screen provider of Nokia 7 Plus from some period of time"
Well to make these things clear ?
I introduced a separate infra for this Nokia 7 Plus phones and we call them as
OOB & POB
Means The people who got Oreo out of the box can actually use the twrp builds named with
OOB ( Oreo out of the box )
&
The people who got Pie out of the box phones can actually use the twrp builds named with
POB ( Pie out of the box )
.
1 . Download twrp-3.4.0-0-B2N_sprout_sprout.img & twrp-installer-3.4.0-0-B2N_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-B2N_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp
Download Android 11 Twrp-3.4.0-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
Download Android 9 Twrp-3.3.1-0 From Here
​For More Information About Status Official Click Here​
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7 Plus
Contributors
Raghu varma
Source Code:
https://github.com/TeamWin/android_device_nokia_B2N_sprout
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Beta Version: 3.4.0-0
Created 2019-06-16
Last Updated 2020-06-25

* Reserved

[DELETED]

Tenshou170 said:
Silly question, but will it work with locked bootloader?
Click to expand...
Click to collapse
No mate

Is that means my phone will be rooted and i can install another system ?

GrandLuLu said:
Is that means my phone will be rooted and i can install another system ?
Click to expand...
Click to collapse
No,without unlocked bootloader nothing.

Thank you for compiling and shearing this. I'm really excited to test it out, especially the crypto part if it works properly !
I've been looking through your repositories and I've noticed you've build B2N tree from DRG tree. How much are they alike, with emphasis on audio part, eg mixer paths ?
Also I'm the owner of an bl-unlocked B2N , if you ever need someone to beta test PM me.

>> Remove lock screen password , pin , pattern
but this remove crypt from internal_storage or not?? anyway this step is i hope need only if i want acces to internal_storage from TWRP, if i not need and use (same as with https://forum.xda-developers.com/nokia-7-plus/development/recovery-twrp-3-2-3-0-t3892644) USB-C where store Magisk.zip for install, then is this step not need?
>> this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
sure? for boot only is not need same TWRP version as installed SecurityPatch, and twrp-installer is not "only" patching/adding TWRP to actual/stock/any_sec_patch_version??

ban.codrut said:
Thank you for compiling and shearing this. I'm really excited to test it out, especially the crypto part if it works properly !
I've been looking through your repositories and I've noticed you've build B2N tree from DRG tree. How much are they alike, with emphasis on audio part, eg mixer paths ?
Also I'm the owner of an bl-unlocked B2N (by you), if you ever need someone to beta test PM me.
Click to expand...
Click to collapse
Sure thanks

Share some screenshots. Do you mean we install without even unlocking bootloader?

Stuck at Spash Screen after installing TWRP
Title says it all.
Using fastboot boot works properly and I'm presented with the decrypt page after a couple of seconds.
Using the installer.zip and trying to boot into recovery ends up being stuck at the spash screen, with no decrypt page showing up. I've uploaded recovery.log
View attachment stuckspash.log with permanent installer stops at line 81
View attachment fastbootrecovery.log with fastboot boot continues after line 82 with key management : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
on a side note: other issues / small annoyances
a) While fastboot boot into it, on the decrypt page there is some graphical glitches: flashing yellow on top bar, and other color errors. Touching the screen first time fixes it. Also (maybe a TWRP thing) the aspec ratio is 16:9 with gap on top.
b) Display locking doesn't work properly. It's unable to actually turn off the screen, instead it only dims the screen and stays on with the last frame on it (no picture update), instead of actually turning off the screen.
Both can be seen in fastbootrecovery.log:
a) line 15 - 25 :
Code:
Starting the UI...
setting DRM_FORMAT_BGRA8888 and GGL_PIXEL_FORMAT_BGRA_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
RECOVERY_BGRA
b) line 26 - 33:
Code:
framebuffer: 0 (1080 x 2160)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 1.083333x, offsets x: 0 y: 80 w: 0 h: -80

ban.codrut said:
Title says it all.
Using fastboot boot works properly and I'm presented with the decrypt page after a couple of seconds.
Using the installer.zip and trying to boot into recovery ends up being stuck at the spash screen, with no decrypt page showing up. I've uploaded recovery.log
View attachment 4780973 with permanent installer stops at line 81
View attachment 4780979 with fastboot boot continues after line 82 with key management : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
on a side note: other issues / small annoyances
a) While fastboot boot into it, on the decrypt page there is some graphical glitches: flashing yellow on top bar, and other color errors. Touching the screen first time fixes it. Also (maybe a TWRP thing) the aspec ratio is 16:9 with gap on top.
b) Display locking doesn't work properly. It's unable to actually turn off the screen, instead it only dims the screen and stays on with the last frame on it (no picture update), instead of actually turning off the screen.
Both can be seen in fastbootrecovery.log:
a) line 15 - 25 :
Code:
Starting the UI...
setting DRM_FORMAT_BGRA8888 and GGL_PIXEL_FORMAT_BGRA_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
RECOVERY_BGRA
b) line 26 - 33:
Code:
framebuffer: 0 (1080 x 2160)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 1.083333x, offsets x: 0 y: 80 w: 0 h: -80
Click to expand...
Click to collapse
as i said this will work only on June 2019 security patch due to decryption works according to security patch
may be you may forgot to read that line
{ Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month & if you get password error in twrp just get back to system and Remove lock screen password , pin , pattern and keep in swipe mode and follow the procedure }
and thanks for posting logs

Raghu varma said:
as i said this will work only on June 2019 security patch due to decryption works according to security patch
may be you may forgot to read that line
{ Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month & if you get password error in twrp just get back to system and Remove lock screen password , pin , pattern and keep in swipe mode and follow the procedure }
and thanks for posting logs
Click to expand...
Click to collapse
Admittedly I haven't payed much attention to that line.
I read it but didn't understood it, mainly because there is no June SP out there yet.
So you are saying that we must wait for the SP to come out before trying the permanent zip installer ?
For my own reading, could you please share a link to the decryption changes ? I've tried to look for something related in Android Security Bulletin but couldn't find. Maybe I missed it

I have the last security patch (May 2019), will this TWRP work in it? The June security patch is not still avaibable.

TWRP 3.3.1-0 for May Security Patch
With Varma's guide here is a repacked version of his TWRP for May SP. This is temporarily until June SP arrives to stock gsi.
View attachment twrp-installer-3.3.1-0-B2N-May.zip use this installer

@k3dar7 you might be interested in my post above. Apparently TWRP and the installer has security patch version hardcoded, meaning it is not taken from what you have.

ban.codrut said:
With Varma's guide here is a repacked version of his TWRP for May SP. This is temporarily until June SP arrives to stock gsi.
View attachment 4781656 use this installer
Click to expand...
Click to collapse
Thanks for posting links

As of this the May repack is not needed anymore.
I know it hasn't rolled out fully yet, but you can still use stock recovery and sd card update method.
So after some days after this post I will remove the link to May repack as it will not be needed.

ban.codrut said:
@k3dar7 you might be interested in my post above. Apparently TWRP and the installer has security patch version hardcoded, meaning it is not taken from what you have.
Click to expand...
Click to collapse
thanks, understand and confirm that twrp from #1 work with june security update installed with data decryption
only question for clarify, if i (or other who this read) not want in twrp decrypt data partition (with using usb-c flash or push zip from pc to /tmp), is possible use actual version with older/newer than june ota update?

that means the device will be easy to root by using our trp steps ,.,..,write
it will grant root permission

TrebleGSI crDroid Android 11 ROM for x606f - Updated 5/26/21

None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
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
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.

Oddities:
Tablet is unencrypted. You can reencrypt, but TWRP will not be able access data partion.
Must re-register GSF everytime you wipe data.
SafteyCheck fails ctsProfile. - Thread updated with info to fix
More to come as I explore the ROM

Tired it myself and works great. It can be also used with other project treble roms but some features might be broken for example face unlock. I would also add that sometimes the message "This device isn't...." might still appear in Google play, because of that you have to clear cache for this app.

Thanks for writing this up @snickle ! I followed your instructions, DRM Info shows Widevine L1, and disney+ and discovery+ install, but they won't play. "something went wrong", etc.

I just installed the latest android 11 phh-aosp arm64-gapps gsi on top of a fully working, Magisk-rooted,, stock android 10 system, by installing a new gsi system image, and leaving all other partitions, including data, alone. Nothing was wiped. I also removed the android lock screen in TWRP by installing a lockscreen remover zip. Other than the fact that you have to reinstall Magisk.zip, you don't have to do a thing. It just works.

Do you have widevine L1? Are you able to play Disney+ or discovery+? I'm having lots of issues that seem to be codec related

I don't use those apps, so I can't comment on how phh-aosp would handle them. I do know that phh-aosp is the most fully developed gsi available, so it might be worth trying.

snickle said:
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
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
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
Greetings!
I was able to use these same steps to install Lineage OS 18.1 with no problem. I retrieved rom from:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
No issues with features so far (camera works, wifi works, even gestures seem to work).
Thank you so much for sharing your steps. It's much appreciated!

ZorgonPeterson said:
Greetings!
I was able to use these same steps to install Lineage OS 18.1 with no problem. I retrieved rom from:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
No issues with features so far (camera works, wifi works, even gestures seem to work).
Thank you so much for sharing your steps. It's much appreciated!
Click to expand...
Click to collapse
Did you pass security checks?
i am having trouble passing them with LineageOS 18.1

snickle said:
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
I used the above fingerprint, I even tried the fingerprint from a stock install (which is the same by the way) and it still fails CTS safety check. I rebooted after adding the fingerprint. Everything worked great up to this part.
I used the crdrom that has gapps embedded (I think it was the bgZ version). Could that be an issue?
I wish there was a full rom for this tablet, but I do not have enough experience building these to build one from scratch.

dpn982 said:
I wish there was a full rom for this tablet, but I do not have enough experience building these to build one from scratch.
Click to expand...
Click to collapse
I tried building Lineage 18.1 using the device tree, vendor, and kernel repos I found on GitHub for this tablet and it failed building the kernel. Admittedly, I'm not good with such things or troubleshooting the errors but maybe someone around here can.

First of all thanks for these steps...
Just a quick report that I was able to use them to do a clean install of LineageOS 19 (Android 12) using Andy Yan's GSI Build:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
lineage-19.0-20211106-UNOFFICIAL-treble_arm64_bvS-vndklite.img.xz
And using NikGapps for android 12 GAPPS:
NikGapps - Browse /Releases/NikGapps-S/18-Oct-2021 at SourceForge.net
A Custom Google Apps Package that Suits Everyone Needs!
sourceforge.net
NikGapps-core-arm64-12-20211018-signed.zip
For bleeding edge stuff I can say it is running VERY smoothly. I figured I would try the latest thing and then downgrade to Android 11 or even 10, but so far 12 is running so well, I think I will leave it. Pretty big design evolution for Android.

Just a question from someone who's had a break from xda.
This rom is a universalrom for the chip, not a specific tablet? or a jump of point?
sixshooterz said:
I tried building Lineage 18.1 using the device tree, vendor, and kernel repos I found on GitHub for this tablet and it failed building the kernel. Admittedly, I'm not good with such things or troubleshooting the errors but maybe someone around here can.
Click to expand...
Click to collapse
can you share your steps and sources?
I'd love a lineage for the tp-x606f and if i have to build myself the initially i could not find other thatclickbait for this tab & lineage

This is a generic for the chip. Not my work, I just figured out the steps to get it to work on our tablets. I don't know where source is. I just download updates from sourceforge

scottyrick2 said:
I just installed the latest android 11 phh-aosp arm64-gapps gsi on top of a fully working, Magisk-rooted,, stock android 10 system, by installing a new gsi system image, and leaving all other partitions, including data, alone. Nothing was wiped. I also removed the android lock screen in TWRP by installing a lockscreen remover zip. Other than the fact that you have to reinstall Magisk.zip, you don't have to do a thing. It just works.
Click to expand...
Click to collapse
Is there anyone who has tried this way to flash phh or another Rom? It seems much less tricky than the proposed one on this thread.

aftnoon2 said:
Is there anyone who has tried this way to flash phh or another Rom? It seems much less tricky than the proposed one on this thread.
Click to expand...
Click to collapse
With new version of twrp, it has gotten easier. Magisk has changed also. I am out of town but will update op when I return next week

I'd like to try to flash Phh 11 Rom. Which one is good for my TB-X606F? Those with vdlnklite or without? Floss or no Floss?
This is a new world of flashing to me, sorry for this questions.

snickle said:
None of this is my work, just the steps to get it to run for me.
The steps are fairly step by step and some seem redundant, but they work. I had lots of failures.
Start with TWRP and Magisk Installed
Note: This will process will complete erase device, so make sure google backup is up to date and using titanium (or something else) for any other backups.
Download the following files and copy to sdcard
Device ID
Device ID.apk | by xda-developers.com for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Nikgapps
https://sourceforge.net/projects/nikgapps/files/Config-Releases/NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip/download
Force Decrypt
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
TrebleGSI Image (Make sure to extract image from xz file)
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.05.21/crdrom-v308-210521-arm64-bvZ-lite.img.xz/download
Latest Magisk APK (Make sure to change extension to .zip)
Reboot to recovery
Goto Wipe
Format Data
Advanced wipe - Select System and wipe
Install cdrom-c306-210428-arm64-bvz.img to system
Reboot recovery
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Reboot system
Press and hold power button when Eye icon shows up. Select restart - Recovery
Goto Wipe
Format Data
Reboot recovery
Install Magisk zip
Install Disable_Dm-Verify_ForceEncrypt_11.02.2020.zip
Install NikGapps-R/24-May-2021/NikGapps-emriza-myfav-arm64-11-20210524-signed.zip
Reboot system
Click start
Skip Mobile network
Select and login to wifi
On Copy apps & data click next
Select a backup from cloud
Enter PIN
When you get "This device isn't Play Protect certified" select "Got It"
Click More and accept through google services
Select Face unlock + PIN
Enter PIN twice
Setup Face lock
Click Done
Click Next
Click Skip
Click Start
Ignore Play Protect errors
Setup sdcard as portable storage
Install Device+ID.apk from sdcard
Open Device ID and accept permissions
On PC goto https://www.google.com/android/uncertified/ and enter GSF.
Wait 2 minutes - PLEASE!!!
Reboot
Goto Settings - Accounts
Add your google account.
Either restore from account setting or wait to be prompted to finish setup. This will restore apps, contacts, etc.
When Setup complete run Magisk and complete its setup.
In Magisk, enable MagiskHide and Hide Google Play Store
Run safetycheck. It should fail.
Load module MagiskHide Props Config
Reboot
From terminal window (I use TermUX),
Run:
su
props
Select 1
Enter fingerprint value: Lenovo/LenovoTB-X606F/X606F:10/QP1A.190711.020/TB-X606F_USR_S300177_2103041623_V9.56_BMP_ROW:user/release-keys
b to go back
4 for custom props
n for new custom prop
Property: ro.build.version.security_patch
Value: 2021-02-05
e to exit
Reboot
Go to magik and rerun safetycheck. It should pass and restricted apps now available in store (Disney, Netfilx, etc.)
Update apps in Play Store
Setup tablet to your preferences
Good Luck.
Click to expand...
Click to collapse
is this the complete procedure of establishing a custom ROM ?

I followed the guide by installing the latest version of the CrDroid, everything went fine except the verification of the CTS, I've already tried with Magisk but it doesn't seem to work, any ideas? Thanks in advance
{
"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"
}

[ROM][11.0.0][TREBLE] LineageOS 18.1 DAILY (2022-01-20)

Hi!
I finally succeeded in having a recent rom on my Zuk Z2 Pro, with Treble. Fingerprints are working, Rooted OK with Magisk, Battery great. This guide can be used for other Treble roms.
Be advised, IT IS NOT EASY. But it's not THAT complicated either. Please read the whole post before attempting anything.
Pre-requisites :
1) twrp-3.2.3-1-z2_row.img installed as your recovery (higher versions are buggy with MTP)
2) Download Arrow-v11.0-z2_row-OFFICIAL-20200919-VANILLA.zip (or more recent)
3) Download lineage-18.1-20220120-UNOFFICIAL-treble_arm64_bvS-vndklite.img (or more recent) UNCOMPRESS IT IF IT'S A .IMG.XZ FILE.
4) Download Magisk-v24.0.apk and rename it into Magisk-v24.0.zip
5) (Optional) Download OpenGapps PICO (Arm64, 11.0, Pico) Heavier versions are too big and won't install.
Installation :
1) Backup your phone. Do it.
2) Go to your recovery, and wipe :
- Dalvik/Art Cache
- Cache
- System
- Data
- Internal Storage
3) Plug your phone on your computer, and move all the files you downloaded on your phone.
4) Install (use install/install zip) Arrow-v11.0-z2_row-OFFICIAL-20200919-VANILLA.zip It will update the vendor partition, necessary to be Treble compatible.
5) Wipe cache/dalvik, Reboot System, go to settings, and save ONE fingerprint (it will allow you to use the fingerprints with the treble rom, very important)
6) Reboot to recovery, then flash (use install/install image)lineage-18.1-20220120-UNOFFICIAL-treble_arm64_bvS-vndklite.img to the System partition, then wipe Dalvik/Art Cache
7) Install (use install/install zip) Magisk-v24.0.zip (Don't wipe dalvik/art cache after)
8) Resize System Partition (Wipe->Advanced Wipe->Tick "System"->Repair of change File System->Resize File System)
9) Install (use install/install zip) opengapps pico (Don't wipe dalvik/art cache after)
10) Reboot System
11) Now the worst part : Registering the new GSF ID. It will take several hours. If you don't use OpenGapps, skip this part.
You might have non-stop annoying notifications about your device not being certified for play protect. Put your phone in "don't disturb" mode or you'll become crazy.
- Get your GSF ID. It will reset every time you reset your phone. I used Device ID, installed it by placing it on the phone when plugged in to my computer in recovery mode, then installed with the "Files" app on the phone.
- Then go to https://www.google.com/android/uncertified/ with your google account, and register your GSF ID.
- WAIT. It will take several hours.
- You might have to force stop and clear storage of those 3 apps : google play services,google play store,google services framework (Display system apps when browsing apps in settings)
You'll then finally be able to finish your phone configuration and restore your settings/apps.
12) Great! You now have to disable the 3 buttons navbar (because our phone already have the physical button for the navigation), you'll need magisk :
[MOD][Magisk] Disable Navbar For 3rd-Party Navigation Gestures
If you're like me, you like using a 3rd party navigation gesture app with the navbar hidden. In Android 11, google disabled wm overscan which makes it difficult to hide the navbar. Luckily, it's possible with Magisk and a little bit of...
forum.xda-developers.com
su (gain root access)
props (open the hideprops menu)
5 (Add/edit prop values)
n (New custom prop)
qemu.hw.mainkeys (the build prop for whether to include softkey navbar)
1 (sets the build prop to disable the softkey navbar)
y (yes to continue with defaults)
y (yes to reboot)
Choose late stage or else it won't work at reboot.
I had it for two weeks and didn't notice any bug. Very happy with it.

Great Work

Hi, thanks for sharing.
I have LineageOS 15.1 in my ZUK Z2 PRO but I was never able to install anything else.
I tried your procedure but I keep getting the "mount /vendor" error with twrp-3.2.3-1-z2_row version.
Tried a different TWRP and I got "success" in the logs installing everything but neither Arrow nor LineageOS will boot, I only get fastboot.
Tried also Arrow-v10.0-z2_row-OFFICIAL-20200831-VANILLA with lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS and those also won't boot.
Also tried starting with TWRP-3.2.3-0929-ZUK_Z2_PRO-CN-wzsx150 and Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst in advance to Arrow and LineageOS and nothing boots.
Had to restore from TWRP.
Any advice please?
Is my hardware different from yours or something?
Logs saying "success" are leaving blind and with no ideas here.
Thanks a bunch, take care.

I would stick to twrp 3.2.3.1, what is your "mount/vendor" error exactly, and when does it happen ? Did you try to go into twrp/mount and tick the vendor partition before ?
Flashing ZUI should restore your vendor partition.
You could also just try ArrowOS 10 (just flash it after wiping caches/system/data), without a treble rom on it, it's a good rom, coming from lineageOS 14.1, and a much simpler install.

Starting from actual LineageOS 15.1 and following your procedure step by step, Arrow10 fails with error "Failed to mount '/vendor' (Invalid argument)" at the beginning and at the end of the installation. I read this is a known issue with TWRP, maybe just with ZUK Z2 PRO. I guessed this is way I had to stay with 3.2.1-0 back when I got LineageOS 15.1 to work.
At the moment, after the restore, I don't have the /vendor folder at all and I didn't find any issue so far after restoring last night.
If I understood you correctly, I tried yesterday flashing Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst and it didn't boot as well.
I tried Arrow10 (with different TWRP so I wouldn't have the TWRP so called known issue) so that I could reproduce your step 5) regarding the fingerprint but no joy, won't boot even though TWRP for Arrow10 said SUCCESS.
My phone was ordered from China a few years ago, is it possible that I am experiencing an hardware incompatibility?
Sorry and thanks again.

Tried again with Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst and if I try to mount vendor and/or factory I can see both full of stuff in Advanced \ File Manager but those won't show in Wipe.
Tried this ZUI, Arrow, Lineage16, Kang, AospExtended, nothing boots.
Back to LineageOS 15.1 with no updates ;(

pringau said:
Tried again with Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst and if I try to mount vendor and/or factory I can see both full of stuff in Advanced \ File Manager but those won't show in Wipe.
Tried this ZUI, Arrow, Lineage16, Kang, AospExtended, nothing boots.
Back to LineageOS 15.1 with no updates ;(
Click to expand...
Click to collapse
Have you flashed factory to vendor?

I did yes, I used factory2vendor_z2_row.zip and didn't noticed any difference to neither new ROM nor LineageOS 15.1 if for example I install it without Restore. Meaning that new won't boot at all and LineageOS 15.1 works correctly with fresh or restored data.

Ok, so I guess I could try to delete all my spam here and just say THANK YOU.
But I believe trying and failing is learning.
Your guide is correct but I assumed that I could resolve any missing pieces flashing Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst with TWRP, because TWRP was not throwing any error.
I did flash it with QFIL and everything after is just following your guidance.
My bad by not doing it earlier, before coming here, but I don't have Windows at hand and QFIL with VM is tricky while passing the USB device.
You guys rock, long live to those who share.
Take care.

Hi, issues found:
SELinux shows Disabled. I believe this is the reason why I can't get some banks to work and get Failed on SafetyNet Status. getenforce says permissive, if I try to setenforce 1 the device shuts down.
Hotspot doesn't seem to work. It switches On and changes to Off and it says Error in the status.
Selecting second SIM Card seems impossible while texting SMS. If set to Ask every time SMS won't send saying No preferred SIM selected for sending SMS messages (weird, found the same in other ROMs - why Android 11 has Ask every time if it is not usable). I later found that to select a different card you should touch the name of the card (on the left of the circles) and not the numbered circle itself - which was what I was doing in LineageOS 15.1 if I remember correctly.
{
"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"
}
Gave it a try to ArrowOS 11 (official), hotspot bug was also there.
Jumped to AOSPExtended 8.4 (official) and no bugs found so far, hotspot working, banks working and ZUK Z2 PRO key working out of the box.
[EDIT] AOSPExtended 8.4 (official) has some bugs. Will try AOSPExtended 9 once there is a version without gapps.

Hello!
I'm right now following this guide on my device, and I get the following errors when trying to flash Arrow v11 using TWRP:
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
…
Patching vendor image unconditionally...
E2001: Failed to update vendor image.
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/.Z2 Pro OS & system files/Arrow-v11.0-z2_row-OFFICIAL-20200919-VANILLA.zip'
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
So well, there's something wrong with my partitioning, I mean, there's no /vendor partition in my device, or the problem is there for some other reason. How can I fix this? By installing factory2vendor.zip? 0K, done; didn't work at all.
I need to somehow manage to flash Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst, then.