Database Develop

[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
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 restore 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 out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
Torchlight
LED
USB and WLAN tethering
Fingerprint sensor
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8704, https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
2020-03-20
Enable DT2W
Update Lineage code
mailru: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200320.img (source code)
Previous versions:
2019-12-27
Fixed fingerprint scaner issue
mailru: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200316.img (source code)
2019-12-25
Fixed OTG mode
enable target ttl for thethering with some operators
Updated Lineage code
mailru: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
2019-08-11
Fixed insert/remove detection for 3.5'' headset plug
Updated Lineage code
mailru: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
2019-07-14
Initial release
mailru: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F)
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TB-8704V (Verizon)
If you have TB-8704V tablet, you have to additionaly flash boot.img from link above after rom intsallation. This tablet has some hardware differences from x and f and requires custom kernel to work,
Thanks
Big thank to @mistersixt, who donated $$ for device.
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-wip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2019-07-21
Last Updated 2019-08-11

Installed it and everything seems to be working great. Many thanks for your work

Can't seem to get it boot on tb8704v (boot loop). I have unlocked rebooted and made sure oem unlock was still checked and installed twrp-3.2.3-0-tb_8704v and then installed rom and gapps. But it just boot loops on restart. I'm missing something?

Thank you so much for all your hard work.

I am unable to install gapps, its stuck on "mounting /persist /system" is there any work around?

wow! can't wait to flash this! thanks so much!
Just noticed in the OP you have "ROM OS Version: 7.x Nougat" Don't you mean 9.x?

Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.

Acel337 said:
Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.
Click to expand...
Click to collapse
Are you on tb8704f?

hunnia41 said:
Are you on tb8704f?
Click to expand...
Click to collapse
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.

Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
I did the same . but I had stock 8.1 installed. I installed mindthegapps as well as the ROM and rebooted and everything seems to be working fine.

I also had 14.1 installed before. Unfortunately I have the same problem as Acel337. I have the tb8704x.
Has anyone found a solution yet?
14.1 starts without problems after flashing again.

I dirty flashed over los 14. Then flashed openGapps 9 pico. Then reflashed the latest magisk. ROM boots after about 5 minutes without any issues.
Chrome reloads on occasion. I have root, don't have rw. The remount script doesn't work. Netflix casts well. That's as far as I've got.
Thank you for this!
Update: rw now working

Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
For me evrythin works
8.0 stock rom
install magisk
install twrp
system writable
erase system data.
sideload pie and gapps.
Everyhing works perfectly.
Maybe the difference, that I started from 8.1 stock
Just a thought. It could be, that indirectly the (wrong) encryption cause the problem. Since when booting, the program tries to populate the data partition, and if it cannot do it, since it appears as 0 storage, it might just stuck in a loop.

How do you get /system to be writable?

Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014

Hemphiz said:
Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014
Click to expand...
Click to collapse
"I'll be sending a Donation "
I did too. The first time in my life for firmware. I have no problem so far. (Used it 24 hours.)
---------- Post added at 06:51 AM ---------- Previous post was at 06:34 AM ----------
Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
Seemingly you did everything, which had to be done. If it is a problem with the firmware, maybe it has to do with the encryption. (Cannot encrypt the data.) Just a guess, since it works for so many people.
maybe you should reflash the 8.1 stock rom. If it works, try again to reinstall lineage pie. If it still fails, go back to stock until problem is solved.

The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.

Could we get some gamepads working up on this mofo please? That would be the Cherry

same here, TB-8704F stuck on lineage bootanimation too
Acel337 said:
The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.
Click to expand...
Click to collapse
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation

robidick said:
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation
Click to expand...
Click to collapse
I did exactly the same thing with the following exceptions. (whether they are significant or not I do not know.
1. Went into twrp without installing it and unrooted with Magisk. (side load)
(Then I do not remember whether I booted up in stock, to check by magisk whether dm-verify was off. It should be)
then I rebooted into fastboot and installed twrp and in my case I made system writable.
After this I proceeded as you discribed.

[9.0][TREBLE]PixelExperience / PixelExperience Plus Pie [UNOFFICIAL]

{
"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"
}
PixelExperience for Moto Z2 Play [albus]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Install stock oreo before installing Custom ROMs, see notes below for further info
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Moto Mods/Moto Snaps
Encryption
FM Radio
Known issues
VoLTE/VoWIFI
Moto Snap Hasselblad Zoom Camera
Moto Snap Projetor is unknown to work
DON'T FLASH GAPPS, ALREADY INCLUDED
Download PixelExperience from AFH
Download PixelExperience Plus from AFH
Telegram channelD
Z2 Play Custom ROMs Group
Z2 Play Global Group​
Instructions:
Always have a backup of the EFS partition made with TWRP stored somewhere, as you may lose IMEI. Restore it if you get 0 as IMEI when booted into the ROM.
Before installing, make sure oreo was the last stock ROM you installed. See notes below if you come from Stock Pie
Download Official TWRP from twrp.me
Flash the TWRP via fastboot
Enter TWRP, go to wipe menu and Wipe Dalvik, Cache, Data, System and Internal Storage.
In TWRP Wipe Menu, do Format Data, then reboot into recovery
Flash the latest build
Reboot
Notes
TWRP
If the touchscreen doesn't work when rebooting into recovery, press the power button twice to turn off and on the screen. The touchscreen will now work just fine.
GSIs
This LineageOS build ships with Project Treble compatibility (lite VNDK), meaning you can flash a GSI as System Image from TWRP. Please don't report GSI bugs here, report them instead to the GSI's maker. A Format Data from TWRP is required after flashing a GSI in order to avoid problems.
Technical details on our Treble implementation:
This device is a community-treble device, meaning other devs before us made it compatible with Project Treble (lite VNDK), using the oem partion as a vendor. GSIs still have some problems regarding cpu frequency scaling and camera. You have been warned.
Coming from stock pie?
For the sake of simplicity, I said that coming from stock oreo was needed. In reality you just need to flash the oreo modem files. There's a script that does exactly that, made by @juniorpassos: https://mega.nz/file/IRxjGDjL#vkdvh4JcMy-LuWgQz4rHhgpWV80029X4ql0_zcMpVug. The script will erase your userdata and cache.
Before starting this script, make sure you have a backup of your EFS partition stored somewhere safe, outside phone's internal storage. After the backup is done, you can reboot your phone into fastboot mode and start the script. Now reboot into TWRP, go into "Wipe" menu and Format Data. Now you can reboot into the ROM. If you get 0 as IMEI, or any other problem related to RIL, go into TWRP and restore the EFS backup made previously.
Wanna help?
If you find a problem or a bug, please share a logcat with us, alongside an explanation of the problem and steps to reproduce. We won't accept bug reporting without a logcat. Collect logcat with:
Code:
adb logcat -b all > logcat.txt
Thanks
Many thanks to @marcost22 for the pair-working we are doing in this adventure, to @davidsonsjesus for his work on KVT, to @jeferson1979 for his help and teaching. Thanks to all the testers that have helped us testing this ROM.
Sources
Device tree
Vendor tree
Kernel
ROM Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
PixelExperience 9.0, ROM for the Moto Z2 Play
Contributors
EmaMaker, marcost22, rahulsnair, @erfanoabdi @vache @kubersharma @jeferson1979
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Based On: PixelExperience
Version Information
Status: Stable
Current Stable Version: 9.0
Stable Release Date: 2020-09-27
Created 2020-09-27
Last Updated 2020-09-30

Reserved

Changelog
2020-12-08: Cleanup and uprev kernel (3.18.113->3
18.116). Update camera blobs: fix Electronic Image Stabilization, bring back laser focus sensor, fix recording in WhatsApp., fix issues with video recording in Snap cam Fix encryption and decryption (official twrp over at twrp.me is needed for this to fully work). SeLinux is now Enforcing. Update VNDK to full enforcement. Update graphics props. This is the final build for Android Pie 9.0. We will will soon start the Q bringup, and will not be building any Pie ROM anymore, unless some critical bug is discovered:
https://www.androidfilehost.com/?w=files&flid=317960
2020-09-26: Initial build https://www.androidfilehost.com/?w=files&flid=317960

Great! The Z2 is still alive! What's the diference between the normal and the plus version?

Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage

OldUncle said:
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Click to expand...
Click to collapse
Enter TWRP and Format Data, then reboot to TWRP again. You may need to repeat this a couple of times

ramelco said:
Great! The Z2 is still alive! What's the diference between the normal and the plus version?
Click to expand...
Click to collapse
Normal version is plain PixelExperience. Plus version includes some tweaks we all like: a bit of customization for status bar and themes (dark theme included for system and notifications!), some gestures like the three-finger-screenshot, advanced restart and others. I think you can find more info on the PE website

when i flash and then boot to system, it prompts me to enter a password, but...i don't have one.
edit: i have not gotten it to work. i just reflashed it.
when i did that, i wiped the cache and dalvik and all that, but rebooted back to bootloader, then ran the script (i came from 9.0 stock), and it flashed, everything rebooted, i got into the phone, and it doesn't think there's a cellular signal. the IMEI seems fine, it's the right string of numbers, but nothing i do will get it to actually register the sim is in.. or rather, it does read the sim. it knows what phone number is on it, but absolutely nothing else.
is this a case where i have to restore me EFI? when i try to do that, it tells me i failed to select a partition, but there's no partition to actually select...

Tried re installing the script? Or flash the oreo modem file via fastboot

ramelco said:
Tried re installing the script? Or flash the oreo modem file via fastboot
Click to expand...
Click to collapse
yeah. i tried that, and then i even went back to stock 9.0 (no idea how to go back to 8, i've tried just flashing normally through fastboot like you do for 9, but it just doesn't work), flashed the 8.0 modem, nada. even on stock 9 i my cellular radio just doesn't seem to work.
in twrp, when i go to restore my EFS backup, it complains that there was no partition selected, but i don't actually get a partition to select. i honestly have no idea what the hell i did to achieve this, but i did.
edit: i was able to get the radio working in stock pie, by fastboot loading erase modemst1/st2 but that doesn't appear to work on this rom
edit 2: let me describe the steps i'm taking here. i boot into twrp, i wipe dalvik/cache, cache, system, data, storage, reboot back into twrp, format data and reboot back into twrp. flash the rom, reboot to bootloader, run the script, boot back into twrp and flash data.
i don't see anything i'm doing wrong, but maybe i am?

likehelly said:
yeah. i tried that, and then i even went back to stock 9.0 (no idea how to go back to 8, i've tried just flashing normally through fastboot like you do for 9, but it just doesn't work), flashed the 8.0 modem, nada. even on stock 9 i my cellular radio just doesn't seem to work.
in twrp, when i go to restore my EFS backup, it complains that there was no partition selected, but i don't actually get a partition to select. i honestly have no idea what the hell i did to achieve this, but i did.
edit: i was able to get the radio working in stock pie, by fastboot loading erase modemst1/st2 but that doesn't appear to work on this rom
edit 2: let me describe the steps i'm taking here. i boot into twrp, i wipe dalvik/cache, cache, system, data, storage, reboot back into twrp, format data and reboot back into twrp. flash the rom, reboot to bootloader, run the script, boot back into twrp and flash data.
i don't see anything i'm doing wrong, but maybe i am?
Click to expand...
Click to collapse
Why would you go back to stock pie, when the instructions clearly say stock Oreo. There's a tutorial on the forums and everything, flashing any version of stock is the same procedure, you just need the specified Oreo version listed in the firmware section of the OP. Not that hard

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M31

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
I am not responsible for 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 me for messing up your device, I will laugh at you.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.2, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m31-v1.0
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m31
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, exynos-nigg, testers and anyone else who made this possible.

Changelog:
v1.0
Initial Release
More in github release page
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website

FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.

Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro

Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.

Karen3443 said:
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Click to expand...
Click to collapse
nope, you havent bricked. start by flashing stock rom again, the flash twrp, AND BE SURE to flash encryption disabler and format data. thats all and it should boot. if you skip encryption dissabler, then the stock recovery will auto restore itself(which seems your case)

if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.

Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.

drcarlox said:
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Click to expand...
Click to collapse
yes, you'll lose your data. so, backup anthing important

Ahamadmusa said:
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
Click to expand...
Click to collapse
tap tag on the github page of bootlogo patcher and download the latest version

soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
Thanks, it worked. Now waiting for custom rom.

soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
i'm getting 404 page not found error,can you provide link?

kogkita said:
i'm getting 404 page not found error,can you provide link?
Click to expand...
Click to collapse
ok found it by searching through google,thx buddy.

M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install

If any custom rom comes for m31 in future,is there any possibility to decrease cpu and gpu voltage offsets?(custom kernel support ?)

dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache

zrekkab said:
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
Click to expand...
Click to collapse
it might be a mistake here(states android 10),but on telegram page it was mentioned android 11 only,try upgrading to 11 and flash,all modules perfectly worked for me.

ensonahmet said:
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
Click to expand...
Click to collapse
htt ps :/ /github. com/corsicanu /TWRP_Bootlogo_patcher /releases/tag/ v1.3 ,remove the spaces and download this 1.3v file

Thanks
Now build v2

I solved the solution by installing the Indian version of SM-M315F INU M315F XXU2BUC1

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy Tab S6 Lite Exynos

{
"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 a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
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 restore 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl/tree/lineage-19.1

Requirements:
Any R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
I strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
Known issues
LineageOS specific features like livedisplay (for now)
You tell me

I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!

fzzt said:
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
Click to expand...
Click to collapse
Always follow this rule of thumb: it is never safe to dirty flash a completely different build on top of an older build (i.e. flashing 19.0 on top of 18.1, or 18.1 on top of 17.1, etc.). At best, you'll find yourself having random problems all over the place; at worst, the ROM will refuse to load. Best thing to do whenever going from one major release to another (or from one completely different ROM to another) is backup your apps and data, wipe data and caches and perform a clean flash, then restore your apps and data. It's a fair bit of work, to be sure, but it's the best way to avoid problems.

Sim card dont work, IMEI dont show, gapps cant install. Any ideas?

electro_vinyl said:
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
Click to expand...
Click to collapse
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?

Macuway said:
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Click to expand...
Click to collapse
With the latest build, it's all fixed!

Installed Lineage 19 last weekend on my P-610. You can flash the rom.zip, GApps and Magisk in Recovery from SD-card, so no need to sideload with adb. I have a problem with Google Playstore, it lags a lot (pending...) and installing an app like Gmail takes a long time. Now it even stopped working. Will try it later with NikGApps for Android S

Hi, it seems audio is not working.
It's just me?
Any help please.
M

minoltista said:
Hi, it seems audio is not working.
It's just me?
Any help please.
M
Click to expand...
Click to collapse
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9

Linux4 said:
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Click to expand...
Click to collapse
Just installed and it works! Thanks !!!

guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab

langamer101 said:
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
Click to expand...
Click to collapse
got it working guys. no need to help anymore.

Does anyone know why gboard force closes every time i try to install? I cleared all storage, played with permissions. Nothing worked.

First of all, I want to say thank to @Linux4 for this release Secondly, I want to ask comrads how to install MicroG on this build? If you can step by step, I'm new to custom firmware

how is newest recovery

Screenshots please

Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.

lobotomite said:
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
Click to expand...
Click to collapse
I have the same thing with any sound on the tablet This is especially noticeable when playing songs on spotify.

[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.