yashsingh1/xdaforums huggingface dataset:
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] weimerd:
Hi mates,

here we go with the persists.img for Lenovo ZUK Z2 Pro.

So if you deleted them by accident you can try to reflash these:

new added file host for all files: https://www.androidfilehost.com/?w=files&flid=243937

persist.img ZUI 1.9.104:

https://mega.nz/#!0dxzwRrD!0DjKphWCRU-vv4yb1clTqrppVPGzbdaLEc4P7ItX6Ek

persist.img ZUI 2.3.044:

https://mega.nz/#!9QAE3J4I!wMNuXJ9430ihNKUgAmfJJqaB7a13v8qHtTGhCb-3hOE

persist.img ZUI 2.5.462:

https://mega.nz/#!MVZEnQCb!KvKYcHFdxvQEjlRC3zKsvQH316YY3iyNJEV3HE63cDU

persist.img ZUI 3.1.194:

https://mega.nz/#!oURh0ARA!JvliKwO6-bvdobG1qZoXg9CrH1u0zmtLsjFuoCIBoFk

persist.zip FLASHABLE zip ZUI 4.0.233 ST:

https://mega.nz/#!8RJ3hCpS!8cjVHyoOoa6yg9uvgTht71WB1CVCNoQi07GEZMxUR6M

All credits to [MENTION=4723116]crisps[/MENTION]

WARNING: these files are not tested. All use to your own risk.

Anyway if you accidentially deleted your persist partition it is worth a try ;)

Flashable by fastboot or twrp. Note: Twrp 3.2.0.0 is not giving you the option to flash persist img. Use a previous Twrp version or flash by adb/fastboot.

TWRP 3.1.0.0 for Z2 Pro:

https://mega.nz/#!ABACiBKD!jPpLuguCoPU58Wq667D3H-YnsoyyXQ505ih0sapAOUY

Enjoy :)

_______________________________________

HowTo flash with fastboot:

- Download correct adb and fastboot drivers

(look into sticked thread "how to flash stock rom")

- put Persist.img in same folder like your adb/fastboot installation

- reboot your phone into fastboot mode

(hit volume when phone starts, select fastboot)

- open command line in the folder where your drivers / ADB-Fastboot installation is located.

- enter command:

fastboot.exe flash persist Persist.img

- you can reboot phone by select via volume buttons(not recommended) or type command:

fastboot reboot

!!! Dont / never ever / at no time ever select "reboot to ffbm"

Dont touch that!!!!

So my suggest is to enter command:

Fastboot reboot

(avoid missclick to that ffbm mode)

_____________________________________

experiences:

persist.img of 3.1.194 is not good with AEX 5.0. Produces black screen / blue led freeze.

persist.img of 2.3.044 is good with AEX 5.0

_____________________________________

experiences by crisps:

persist.img of 3.1.194 no problem with LineageOS by cosme 20171125
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] weimerd:
OP link added to 1.9.104 and 2.5.462 persist.img.

Added link to Twrp 3.1.0.0 where you can flash persist.img to persist partition.

With twrp newer than 3.1.0.0 the option to flash to persist partition is no longer available.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] weimerd:
added new file host in post #1
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Jb boin:
What are those containing?

Is there any benefit to upgrade the image?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Oriwen:
These are containing core drivers for sensors (correct me if im wrong).

No real benefit, flash only if you screw up your phone by formatting persist partition.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] weimerd:
yep, use these persist partitions only if you deleted them by accident or experience problems with sensors.

Not necessary to use them if there is no problem.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] dimitar.petrunov:
I have a problem with AEX, getting BLODs since 5.0. I've never used qpst and went straight from ZUI 2.5.462 to AEX. Tried all the basebands with no result(well I'm on the latrest 3.5.444 now for a couple hours still no BLODs). The recommended baseband doesn't allow me to unlock the phone as if UI restarts right after pattern entering and then asks me to draw it again. I wonder whether flashing 3.1 could help and aren't there newer persis images?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Terminator.J:
So between this post and the one where you asked me about not needing to do QPST/QFIL flashes any more since there's unofficial Treble support in the AEX thread, I get the feeling you're hoping someone will tell you that there's a simple answer that doesn't involve using QFIL to flash a factory ZUI QPST package.

There isn't.

What you're realizing is that you need to update more than just /system, /boot, and /persist... there's a lot of potential partitions that could've been messed up or accidentally wiped or overwritten, depending on which recovery you've been playing with and what the many various custom ROM installer scripts tell it to do... and the best way to make sure that ALL the partitions are healthy and have current, works-well-together data in them is by using QFIL to flash a current ZUI package (3.1.194 as of this writing) then use the factory recovery to install the latest ZUI Oreo OTA. With this phone, it's not an optional step; using QFIL to go back to a standard, factory image is literally step 1 in any of the upgrade or troubleshooting guides.

It's time to make sure you have it installed, USB drivers working, a good USB 3.0 type C cable that works reliably for data transfer, 7-zip installed, and at least 2 gigs of drive space available so you can decompress ZUI 3.1.194 into a folder at the root level of your drive. This isn't a phone you can work on without a computer unless you're ready to only stay on official ZUI releases with a locked bootloader & no root so that you can't accidentally mess anything up trying to get custom ROMs to work. If you want to re-lock your bootloader in that case, be sure you download the ZUI 1.9 QPST package and start from that instead of 3.1.194.

It's not that scary, and I'm happy to answer questions in PM if you need some help.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] dimitar.petrunov:
It's been over a day without a blod now with latest baseband. I don't want to qfil anything because I'm sceptical of the outcome.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Terminator.J:
And that's your choice, but if you've been flashing partitions piecemeal since ZUI 2.5.x and AEX 5.0 instead of a clean QFIL flash & bring-up to eliminate potential unknown causes of instability, please don't waste time submitting bug reports or asking for help with blue LED hard crashes since there's no way to know what state your phone is in.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] dimitar.petrunov:
Well, I have only reflashed the firmware partition until now, which according to your own criteria makes me eligible for bug reporting. Jokes aside, here's why I believe it doesn't make sense what you recommend. It's been reported that the only way to recover from nonworking device sensors is by going back to zui 1.9 which you don't do. So your partitions have to be in a mixed state since you start from zui 3.1. Since your device works I assume you never ran into sensor problems and respectively reflashing zui 3.1 on your phone just gives you the illusion of a clean slate start( since there is nothing wrong with your phone in the first place)

Having said that, I haven't had a blod since firmware .344 which makes me think I'm right about that.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Oriwen:
Actually I suffered from non-working sensors and full wipe (or you can say total factory reset) by QFIL of ZUI 1.9 solved it. I softbricked my phone between these two states trying to solve it without QFIL btw.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] dimitar.petrunov:
[MENTION=5900575]Terminator.J[/MENTION] thanks for the input. Still I'm coming from the fact that If I've only flashed AEX and AEX is the culprit of my partition problems then reflashing it once again won't solve them. And AEX is the only ROM I've ever flashed on this phone. I haven't understood you correctly about ZUI 1.9, my appologies. I haven't reported BLODS in the ROM's thread only asked if anyone experiences it since I'm aware of my personal setup. Btw If I remeber correctly NYE version was BLOD free on my phone too.

[MENTION=5720882]Oriwen[/MENTION] That's exactly what I wonder how is it possible to wipe your persist partition by flashing a custom rom? Since the cure is going to zui 1.9 and then flashing the same ROM how do you not loose your persist partition again? I'm trying to understand why flashing has such side effects or is just because of flashing random partition images like the ones in this thread?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Oriwen:
I probably flashed recovery partition badly, rewritten wrong partition and boom .... thats only possible culprit for me as far as I know.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Terminator.J:
All an installer script (any of them - rom, gapps, magisk, supersu, whatever) has to do is touch something in /persist. And there's legitimate reasons to do that, like survival scrips for things that you want to persist across a system wipe/update (someone correct me if I'm wrong, but I know it's for more than just sensor configs), like google apps install info.

It seems like a number of folks either got too happy with wiping things in TWRP trying to clean their phone (rather than using QFIL to flash a factory QPST image, which does all the partitions!) or otherwise some custom ROM or systemless root or botched flashing attempt put garbage data into /persist. Some of the TWRP versions available, like the LR.Team ones, allow you to wipe a LOT more than just /system, /data, /cache, /dalvik-cache, /boot, and internal storage... the Chinese one will let you mount & wipe /persist, /efs, and a bunch of others you reeeeeally don't want to touch. Or maybe it just gets crusty with several months' worth of various installations (again, not just a ROM, but any installation script could actually touch it) doing different things to it and leaving ultimately incompatible data.

The cure doesn't cure /persist by wiping it, but by making sure that it only has good data in it (particularly the configs for the sensors), and that those config versions match the drivers that depend on those configs. So if you've got configs from an ancient (ZUI 1.9 = Android 6 marshmallow) version in /persist but drivers for that hardware from Oreo (taking the ZUI 3.5 blobs), it's likely that some things aren't going to behave correctly, wouldn't you agree? When someone's having trouble with their setup, QFIL of the latest full factory package (which includes fresh /persist partition images), followed by as few OTA updates as needed, is the fastest way to get good data back in all the places so you can start loading a custom recocovery & ROM from a known-good state.

Yeah, you're right; AEX 5.2 and earlier (including NYE beta and some other non-Treble custom ROMs worked okay with the ZUI nougat basebands (like the ZUI 2.5.462 you had), and they were even recommending coming from 3.1.194 because the early 3.5 DEV basebands were unstable. But in AEX 5.3 & up it REALLY needed an oreo (3.5.x) one in order to work... I was running into that same problem of constant BLOD crashes right after a QFIL flash of ZUI 3.1 and fresh TWRP 3.2.1 & AEX 5.3 install from there. Reflashing ZUI 3.1 via QFIL then updating with the 3.5.316 OTA package via factory recovery, then loading TWRP , wiping, & installing AEX 5.3 again took care of it and 5.3 has been basically solid for me in all the important ways since then (and with the latest 3.5.344 baseband update).

Again, please feel free to PM me if you'd like to compare more notes on things or are having issues... I really do want to be a resource for you & everyone here in making the most of these phones, and avoiding some big headaches. Setting up QPST/QFIL is a little headache, but it helps prevent much bigger ones in the long run.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] mlkj5002:
By flash Twrp:

Witch partition i select?

Boot

Recovery

Système image

Firmware
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] crisps:
Read OP
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] diogooskamarada:
"persist" lenovo z5

Hi everyone, I could get the file persist.img for lenovo z5. I am trying to use twrp but always the error because of the persist folder
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] weimerd:
new flashable persist sensors zip from ZUI 4.0.233 ST online, see first post.

Enjoy mates, all for Z2 Pro only.

Tested with latest twrp and RedWolf twrp. Tested with Android 8.1 and upcoming versions.

All credits to [MENTION=4723116]crisps[/MENTION] who did all the work and let me upload it ;)
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Starchm:
Let me ask from where did u get st version? on zukfans my thread is only for dev versions.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Terminator.J:
So yeah, tried updating with the 4.0.233 zip file... and now I have no sensors. That's on top of a recent clean install of QFIL ZUI 1.9, QFIL ZUI 3.1, OTA ZUI 3.5.388, unlock bootloader, latest official TWRP 3.2.3, factory2vendor.zip, AEX 6.0 Oct 9 alpha, opengapps nano+ for ARM64/Pie, Magisk 17.2, and Radio/Modem 4.0.233. Unfortunately I never booted TWRP 3.1 to copy my old persist.img from that fresh install, and don't know which else to try going back to in order to get proximity & other sensors back, since I don't see an image file for Oreo (ZUI 3.5) in this list.

Update: Tried a few others, and still no working sensors. Tried wiping /system and reinstalling AEX + GApps & so forth without touching /data, and still no sensors (gyro, proximity, etc.) Any bright ideas short of a clean install?

Update 2: I tried flashing all the different versions to see if there was anything different in them, none of them were working, so I booted back to TWRP 3.2.3, flashed the 4.0.233 persist .zip one more time and did a backup of system, boot, data, efs, etc. in preparation for trying to QFIL & OTA again and try to restore on top of that... then realized I needed to text someone so I cleared cache & dalvik again and rebooted. Now sensors are back to working again so...

(╯°□°）╯︵ ┻━┻
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] doktor29:
@up

next time just flash sensor.zip file.. was on this forum somewhere ;)
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] tiggerle666:
Came here for the same problem. Took me the whole Saturday and multiple flashs until it finally worked. The sensor.zip has in fact the /persist path inside, you just have to open and check as I did. But uploading /pesist from here (or any other backup I had) didn't change a ****.

Flashing to 1.9 and 3.1 (I had no interest in OTA-updating anymore because that's what I've been doing the past week to get Android 10 to run; with 4.0. I had problems with the modem), installing AOSPv6.7/Android 9 (the older AOSP Oreo couldn't get installed, ended with an error on /vendor update) and then dirty flash (clean would not work...) did it.
[Xiaomi Mi Max 2  Questions & Answers] binser:
Hello,

I am using China Stable MIUI 9.

Is there any way to use a USB Ethernet Adapter with the Mi Max 2?

Is there any ROM that would support it?
[Xiaomi Mi Max 2  Questions & Answers] brasscupcakes:
To use the plugable adapter, I think it requires driver support for ASIX AX88179 chipset -- nobody in the Xiaomi forum could tell me whether it did, so I'd like to know. too. I'm also trying to find out whether the displaylink software enables connection to a displaylink equipped monitor, since it lacks MHL. There's definitely a software solution, or I wouldn't be able to get display out with usb screencasting apps (unfortunately, the only ones that work properly require a log in and monthly subscription -- I'd be glad to buy an app, not one I can't use without being online).
[Xiaomi Mi Max 2  Questions & Answers] binser:
Yes, the kernel must definitely have the driver included for the USB ethernet adapter chipset.

Is there any ROM/kernel that supports it?
[Xiaomi Mi Max 2  Questions & Answers] serene_step:
did you manage?

Hi, one and a half year after you, I'm facing the same problem. Did you find the solution?
[Xiaomi Mi Max 2  Questions & Answers] binser:
No. My conclusion is that AFAIK there are none.
[Xiaomi Mi Max 2  Questions & Answers] boredgeek:
I'm not a Linux expert, but I think the kernel should have drivers for whatever Adapter (chipset) you use. I use TP-LINK USB to gigabit adapter with USB C OTG adapter and it works in MI Max 2. But my USB C to gigabit ethernet Belkin adapter doesn't work with MI Max 2. In the hw diagnostics menu the Belkin adapter gets detected as OTG, but looks like the chipset drivers are not there in the kernel.
[Xiaomi Mi Max 2  Questions & Answers] binser:
Could you please help us by giving us links to the adapters that work with your Mi Max 2?

And please also give us the exact MIUI or alternate ROM version, Android version, and kernel version you got them running on?

You're right ~ the drivers are mainly in the kernel, but to keep the kernel lean, the manufacturers remove drivers they think are not needed.

I'm very frustrated with that, too.
[Xiaomi Mi Max 2  Questions & Answers] JustBasic:
Did you find the solution? Im also interested in ethernet connectivity on my Mi max 2
[Xiaomi Mi Max 2  Questions & Answers] binser:
I haven't actually tried it yet, but from my research it could be the TP-Link UE300 adapter that is working. Even in its description it claims compatibility with Android (but you also need an adapter USB - A female to USB - C male).

Please let us know if you succeed.
[Xiaomi Mi Max 2  Questions & Answers] binser:
I have found that all USB Ethernet GB adapters that are compatible with the Nintendo switch (f. e. several ugreen or baseus models) are working with Smartphones that contain a relatively modern Qualcomm SoC (at least 2 years, maybe even 3+ years old).

Reason is that these adapters are powered by an Asix chip, whereas the Realtek chips in many USB to Ethernet adapters do not have the driver in the Android / Linux kernel present by default.

Adapters with Asix chip are just plug and go. Do it in airplane mode and then after a minute you will have internet connectivity. You won't get an icon in the status bar like the Wi-Fi icon, it will just work unannounced. Much faster and more reliable internet connection than Wi-Fi and no radiation - just the same speed as if you plug an ethernet cable into a computer. Play store works like that too. Tested with Xiaomi Mi Max 2 & 3, RN9s, R5+ on standard global Roms and other models from different manufacturers.

Disadvantage: They use a good amount of battery juice, around 120-200mA. You also cannot extend the USB cable too much, maybe 30-40 cm is okay, otherwise the adapter will stop working.
[Xiaomi Mi Max 2  Questions & Answers] adereto181096:
please have a link of those adapters?
[Xiaomi Mi Max 2  Questions & Answers] binser:
€ 12,68 36%OFF | Baseus USB Type C Ethernet Adapter USB-C to RJ45 Lan Adapter Network Card USB A 3.0 Converter for Windows 10 Macbook Pro Switch

https://a.aliexpress.com/_BOZKXN
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Tkkg1994:
Changelog:

IronMan-Rom V1.0.0

- Initial release on XDA

IronMan-Rom V1.1.0

- Updated the base from the rom to latest BQK6 release

- This base includes the Krack fix (Krack explained: https://www.krackattacks.com/)

- Fully remodded with all romcontrol features (There are no new features added for now in the RC)

- Updated kernels to latest BQK6 source code (version 1.2.0)

- Updated included csc to BQK6

- Updated all bootloader and modem files to latest for their model

- Added SM-G955N, SM-G950N and SM-N950N bootloader/modem to aroma. So they can also update directly via recovery!

- Updated modded Youtube vanced to most recent version

- Updated patched camera bins thanks to Noxx!

- Added vision to the bixby debloat section, means if you don't select bixby in aroma you also won't get bixby vision this time

- Added a new "edge" debloat feature, if you don't choose it you get the system without all edge functions

- Updated the modded camera thanks to zeroprobe (based on BQK6 release)

- Updated all included recoveries to 3.2.0-0 (except the note 8 didn't got an update yet)

- Removed many google apps from aroma, you can download them via the playstore, this prevents an issue people had with "symlink failed"

IronMan-Rom V1.2.0

- Rebased upon latest BRA8 release

- Updated all kernels to version 1.3.0 (which include latest source code of course)

- Updated magisk to v15.4

- Updated xposed to 89.2

- Updated busybox to latest release

- Updated S7/S7e BL/CP to DRAG

- Updated adaway host files

- Readded OEM switch even to modded settings

- Prevent RMM State Lock (thanks to [MENTION=632404]blackmesa[/MENTION])

- Update GBWhatsapp and GBInsta to most recent versions

- Update modded youtube to most recent version

- Added a new ironman theme for the aroma installer thanks to Karan_Tamboli

- Fixed RomControl links in "about the rom" not being correct (telegram and xda links)

- Fixed systemui crashing as soon as you are in roaming mode

- Added flipboard and upday to debloat

- Updated all libs and bins to DRAG base

- Updated kernels to DRAG source/ramdisk

- Fixed resolution bug by taking libs from another 7.1.1 base (first boot screen may look a bit weird, I had to change the dpi in developer settings to 360 to get a good value for the s7 screen, default was 480)
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Tkkg1994:
Just as a small addition:

If you are using any 3rd party kernel (not the included IronKernel) you may want to ask your developer to include this wifi hotspot fix. Using 3rd party kernel will break the hotspot function!!

Please, again. If this issue happens it's not an issue with the rom BUT the kernel. I hope all devs will include it for n8 ports
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] jamesbond007uk:
Is VoLTE working on S7 Edge?
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Beefheart:
Lovely, downloading now. Can I ask if the SPen options in the settings menu have been removed? And is it worth dirty flashing over Batman 1.5 or would you expect issues?
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] mackeftw1:
Supersmooth rom, great work as always TKKG1994! Thank you very much for this! :)
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Tkkg1994:
Yes for sure with the right csc installed

Spen not removed because the same rom can be installed on n8 devices. I think n8 users would kill me :D

Dirty flash over a complete different base? Not recommend...

Thanks man!

Sent from my SM-N950FD powered by IronMan
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] sinkoo1979:
Very Nice Rom!!!!!

Will post result for the battery but everything else holy cow the best N8 Rom!!!!!!

Thank you to the Developers.

Update: The battery life is same as S7 edge stock.... I guess my battery is deteriorated from charging the phone too much.....
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] romano19:
Rom did not install Applock although I found it in Aroma. It is not selected
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] JasontheKep:
I wish you could make this for my N910T.
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] Tkkg1994:
Thanks for your feedback! Appreciate it a lot!

I'm sorry to tell but there is no applock in this rom. Why?

Note 8 csc are encrypted and can't be edited to add csc features such as applock

I'm sure a talented developer for your device can get this to work. Nothing is impossible!

Sent from my SM-N950FD powered by IronMan
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] habboy24:
Keyboard gif please

GRAZIE!! Thank you for such a beautiful Rom. We should all be greatfull for all the developers for these wonderfully roms.

Anyways, this Rom is beautifully done. I'm just wanting gif in keyboard please. I hate adding third party apps.

Thank you again
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] romano19:
Yes, i tried to copy "cscfeature.xml" & applock.apk from another rom (Note 8 DX port rom) and it work fine :)
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] p_a_r_s_a7:
Thanks for your great job [MENTION=5899304]Tkkg1994[/MENTION]

Everything is okay on my phone s7 flat

If it's possible can you add smart lock new one, i mean face unlock without ant touch to unlock

Sendt fra min SM-N950F med Tapatalk