yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] STKO74:
I did but for some reason after down loading the file they both were corrupted mid matched md5.. I even inserted a brand new formated SD card still no go. I even cleared every cache I could find in my phone reset my router and and monitored the download using es file pro downloader ..
[Galaxy S 4 Q&A, Help & Troubleshooting] STKO74:
I was kinda hoping maybe a forum member had one lying around. That way I know its a reliable and verified source.. I hate using file hosts that limit your DL speed and amount of downloads per hour.. For example the second link in ibuprofen's response limits to 1 DL per hour AMD when I got to the link ASA it started to DL I hit my home button and lost the DL.. Tried to DL again and said to many connection s try again later lol
[Galaxy S 4 Q&A, Help & Troubleshooting] Stratton_Nation:
Any Luck?

Let us know if you find it, I'm in the same boat and trying to find a legit and "Actual" Stock ROM for the SM-S975L is Dangerous business, guaranteed to make you become Postal! Made the standard nand backup of course but go figure, when you need storage to work it always seems to spit Corrupt out at you !!??
[Galaxy S 4 Q&A, Help & Troubleshooting] audit13:
The model #s can't change from one to another; i.e. sml to sgh. To confirm the phone motherboard's actual model #, boot into download mode.
[Galaxy S 4 Q&A, Help & Troubleshooting] _throwbackkk:
I'm having the same problem with my sm-s975l galaxy s4

---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------

Same , I need to revert my phone back to stock

---------- Post added at 06:26 AM ---------- Previous post was at 06:25 AM ----------

I am having trouble with reverting to stock ??
[Galaxy S 4 Q&A, Help & Troubleshooting] audit13:
Before flashing anything, I recommend confirming the model # in download mode.
[Galaxy S 4 Q&A, Help & Troubleshooting] chowland1967:
Check my signature for the stock ROM. Links are there
[LG V20 Themes, Apps, and Mods] BySezerSimsek:
Download All Wallpapers

https://drive.google.com/drive/folders/0B1TGY84XYJfWa3Npb0V1VjBHclE?usp=sharing

https://postimage.org/index.php?lang=turkish
[Google Pixel Accessories] falcon26:
I am looking for a thin white case with no logo on it, or at least a very tiny logo. I can find tons just not a white one. Can someone point me in the right direction :)
[Google Pixel Accessories] BlueSilence:
There is another topic about ultra thin cases. There were many suggestions including mine.
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
Hi people of XDA. I'm on a SM-G530FZ, and when I install a new custom ROM (built for the Galaxy Grand Prime), I always have a problem: the touch screen. The ROMs go well, but the touchscreen doesn't works anyways. )': All the buttons do work. I tried with Resurrection Remix (Android 6.0), Lineage (6.0 I think), a custom ROM on Android 7.1.1 (Resurrection Remix was a part of the ROM) and a modded SM-G530H, Android 5.0.2. In the first three situations, all went good except the touch screen. In the fourth situation, all went good, but the custom ROM was very buggy (no Wi-Fi, no GPS, no audio recording, no camera), then I don't know what to do. Do I have to install some particular kernel? Thank you :')

EDIT: In Download mode, the mobile says "QUALCOMM SECUREBOOT: ENABLE (CSB)", could this be the cause?
[Galaxy Grand Prime Q&A, Help & Troubleshooting] aurelio.9581:
Because you install "fortuna3g" version. This version is for 530H.

You do install "Fortunafz" version and all works.
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
You were right! Thank you :')
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
Ok, now I installed the custom ROM. (Android 7.1.1, Resurrection Remix for SM-G530FZ). I can do a lot of things, but no audio in out-put and in-put during the phone calls. I tried with the original dialer and one on the PlayStore (drupe), but nothing happens. And the 3G doesn't work. I can go on Internet just by Wi-Fi connection. Which could be the problem?
[Galaxy Grand Prime Q&A, Help & Troubleshooting] kamil79123:
The problem is devs does not care for FZ (in my opinion).
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
Maybe... But I hope not ):
[Galaxy Grand Prime Q&A, Help & Troubleshooting] sibok:
Hi, how did you fixed the issue? Did you install any particular rom? I'm trying with resurrection remix rom but none of the versions, 6.0.1 and 7.1.1, work fine. Version 7.1.1 had no sound on incoming outgoing phone calls and on 6.1.1 touch screen didn't work at all.
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
No, I solved just the initial problem. Now I'm in the same situation like yours. In 6.0.1 doesn't work the touchscreen, in 7.1.1 don't work data connection and phone calls :/
[Galaxy Grand Prime Q&A, Help & Troubleshooting] sibok:
By now I just went to lineage OS rom.
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
Lineage doesn't work on my phone. Or better, it doesn't exist an available versione for my phone :/
[Galaxy Grand Prime Q&A, Help & Troubleshooting] aurelio.9581:
In all Nougat rom there is a mobile data bugs.

If you want a Nougat rom with mobile data you do install a xcu version"fortunave3g", but the sensor will not works

In MM rom 6.0 i remember that all works
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Wilsonb:
" no audio in out-put and in-put during the phone calls."

Did anyone ever fix this when it came up or have any ideas on it?

I installed Noble Nougat Experience 2.0 STABLE, yesterday..

Everything was beautiful

UNTIL

(after spending a lot of time customizing) I answered a call on my phone... No audio to hear them or they hear me.

The call recorder records the audio.. ANYONE ELSE on 920T see this?﻿
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Cherryello:
I solved by installing LineageOS 14.1 for SM-G530FZ. Everything works, but it could be a bit laggy sometimes. Sometimes I play Pokémon GO, but it is impossible due the lag.. This didn't happen with the stock ROM. Except this, it's a very good custom ROM
[Android Apps and Games] mohamad_ibrahim:
Hi; my tablet lenovo A3500 HV can't boot correctly and always open on recovery mode directly and begin wipe system automaticlly but always failed and can't find internal storage from the recovery

beside i want to backup my data before doing anything .

I don't know what to do !!
[Samsung Galaxy S7 Edge Questions and Answers] alehawk:
HI, I got autobrightnes on and sometimes stops working, is there any way I can reset it without restarting the phone?

Thank you
[Xperia Z4/Z3+ Android Development] DiscMan55:
Changelog

2017-02-27:

- Initial release

2017-02-28:

- Embed minimum crypto blobs directly in recovery, now it is completely independent from /system and /firmware. Commented out /firmware from fstab to prevent accidental damage by users.

- Removed accidentally left debug messages in firmware_class.c in previous release.

2017-02-28-02:

- Moved qseecomd binary and libs outside /system to avoid becoming affected by mounting /system.

- Enable qualcomm hardware encryption engine (thanks to [MENTION=6979267]nailyk[/MENTION] and [MENTION=1162986]Captain_Throwback[/MENTION] for help).

- Use busybox instead of toolbox/toybox to avoid problems with scripts due to missing functions.

2018-03-04-01:

- Sync'd to latest ivy / kitakami sources.

- Updated to latest TWRP on android-7.1 branch.
[Xperia Z4/Z3+ Android Development] DiscMan55:
Developer notes

- Encryption depends on binary blobs in phone "modem" partition: keymaste.* and kmota.* (shipped with firmware FTF). These blobs have now been embedded in the recovery image itself, so recovery runs completely standalone.

- Also needed are cmnlib.* files from /system/etc/firmware but they are embedded in this recovery image to allow crypto to work completely independently of /system.

- Sony firmware package can be flashed with [MENTION=2807379]Androxyde[/MENTION] flashtool.

Future ideas

- Generalize the changes needed for TWRP to make it compatible with Kitakami in general (z5 / z5 premium) and make the tree cleaner. If any devs want to help, please reply, I'm a noob myself at this :)

- Implement charging LED.
[Xperia Z4/Z3+ Android Development] DiscMan55:
Updated 2017-02-28.
[Xperia Z4/Z3+ Android Development] DiscMan55:
Now trying to get cryptfs hw encryption working!
[Xperia Z4/Z3+ Android Development] EverCH:
Please!!! Help me....

I'm with boot loop in twrp, how to solve this? I have Dual version on stock ROM V278
[Xperia Z4/Z3+ Android Development] DiscMan55:
What does boot loop in twrp mean ? If you mean you are unable to reboot from TWRP to system, just go to reboot in menu and power off and then power on. It will go to system.

If you mean something else, please provide more details.
[Xperia Z4/Z3+ Android Development] EverCH:
I do this, but when I try to restart the system, it goes back to the twrp, even if it turns off the phone and calls again, it starts directly in twrp, it does not start the OS, it stays in loop in recovery.
[Xperia Z4/Z3+ Android Development] DiscMan55:
Unplug phone. From inside TWRP go to reboot menu, and choose power off. Wait for few seconds after screen turn off, then power on using power button only.

Otherwise, try to go in fastboot mode again by doing vol. up + plug in, and then from console do fastboot reboot.
[Xperia Z4/Z3+ Android Development] Fauzi alaik:
Work great on dual version:victory:
[Xperia Z4/Z3+ Android Development] EverCH:
I just did this however I got the same result, it never starts the OS, even turning it off for a few minutes when connecting it enters the twrp, remembering that I am with ROM 32.3.A.0.376 dual version
[Xperia Z4/Z3+ Android Development] DiscMan55:
At this point, I don't know what can be wrong. I would try to reflash with sony flashtool all partitions (except userdata), then flash twrp again from fastboot. Maybe that will reset it.
[Xperia Z4/Z3+ Android Development] DiscMan55:
To anyone familiar with BoardConfig.mk syntax:

I am trying to get TARGET_HW_DISK_ENCRYPTION working. There is a problem with TWRP, it expects libcryptfs_hw.so to be found in $(TARGET_OUT_VENDOR_SHARED_LIBRARIES)/libcryptfs_hw.so but in sony tree, libcryptfs for qualcomm comes from default LineageOS qcom opensource cryptfs driver (which delegates to libQSEEComAPI.so which is pulled from blobs) in https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw/

In the Android.mk in that driver https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw/blob/cm-14.1/Android.mk LOCAL_MODULE_PATH_32 and LOCAL_MODULE_PATH_64 are not defined, so libcryptfs_hw.so gets built to default /lib and /lib64 location, so it is not found by TWRP (https://github.com/omnirom/android_bootable_recovery/blob/android-7.1/prebuilt/Android.mk#L172) .

Is there a way in my device BoardConfig.mk where I can make ninja understand to build libcryptfs_hw.so like normal and then have it copy it to where TWRP expects it before building TWRP ?

I'm trying to have my tree "just work" without having to fork the lineage os repo just to add 2 lines. If I add:

# in vendor/qcom/opensource/cryptfs_hw/Android.mk
LOCAL_MODULE_PATH_32 := $(TARGET_OUT_VENDOR)/lib
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR)/lib64

It builds and works successfully, but I don't want this ugly hack.
[Xperia Z4/Z3+ Android Development] nailyk:
Weird way to include it into twrp. Is it the same into 6.0 branch or does they use dependencies system?

You can try to replace with something like:

ifneq ($(strip $(TARGET_ARCH)),arm64)
LOCAL_MODULE_PATH_32 := $(TARGET_OUT_VENDOR)/lib
else
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR)/lib64
endif

but I think a better way would be to change the include into twrp.
[Xperia Z4/Z3+ Android Development] DiscMan55:
When I modify vendor/qcom/opensource/cryptfs_hw/Android.mk as I quoted, ninja picks up that it is dependency, and it compiles libcryptfs_hw first, and then copies to where TWRP wants, but I can't make it understand to "alias" or build it manually in its default location and then put it where ninja wants to be still recognized as dependency.

I don't want to hack qcom source because I want my same BoardConfig to work for LineageOS build as well as TWRP (I want to make 100% compatible encryption in LineageOS 14.1 with stock sony rom with best performance and lowest battery with hw crypto).
[Xperia Z4/Z3+ Android Development] nailyk:
Does TARGET_RECOVERY_DEVICE_MODULES := libcryptfs_hw get the module be built at the right location?

(it should be something like LOCAL_DEPENDENCIES += TARGET_RECOVERY_DEVICE_MODULES into twrp makefiles but can't find it again. I hope they don't remove it...)

I know they get encryption working because pixel is encrypted and afaik it is qcom arm 64 too.
[Xperia Z4/Z3+ Android Development] DiscMan55:
Nope, it gets built but at the default location (which is wrong for twrp) as the normal behavior for android.mk without explicit local_module_path.

Now I am only stuck on how to just copy it to /vendor/ before TWRP builds (how to say that in BoardConfig.mk)

Here's the relevant part of my BoardConfig.mk:

TARGET_HW_DISK_ENCRYPTION := true
TARGET_CRYPTFS_HW_PATH := vendor/qcom/opensource/cryptfs_hw
TARGET_SWV8_DISK_ENCRYPTION := true
TARGET_RECOVERY_DEVICE_MODULES := libcryptfs_hw
# latest attempt, doesn't work, still complains file is missing
PRODUCT_COPY_FILES += ${TARGET_OUT_SHARED_LIBRARIES}/libcryptfs_hw.so:$(TARGET_OUT_VENDOR_SHARED_LIBRARIES)/libcryptfs_hw.so
[Xperia Z4/Z3+ Android Development] Captain_Throwback:
Cherry-pick this: https://gerrit.omnirom.org/22096
[Xperia Z4/Z3+ Android Development] nailyk:
Product copy_files on Lineage is parsed only at bacon time. The only way is to create a dummy target like:

LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_SRC_FILE := out/target/product/device/xxx/yyy/zzz/libcryptfs_hw.so
LOCAL_MODULE := libcryptfs_hw64
LOCAL_MODULE_PATH := $(TARGET_RECOVERY_ROOT_OUT)/lib64/
LOCAL_POST_INSTALL_CMD += \
ln -sfT libcryptfs_hw64.so $(TARGET_RECOVERY_ROOT_OUT)/lib64/libcryptfs_hw.so;
include $(BUILD_PREBUILT)

Or to put it as prebuilt into device/sony/ivy/recovery/root/lib64/ (symlink doesn't get copied, that was my problem :) )

Maybe you should try the twrp IRC chan, probably somebody had already solved this.

Haha Captain is here your are in good hands now :)
[Xperia Z4/Z3+ Android Development] Captain_Throwback:
You missed my post ;).
[Xperia Z4/Z3+ Android Development] nailyk:
Yes, you are still too fast for me ;) you post this before my edit :p
[Xperia Z4/Z3+ Android Development] DiscMan55:
Updated 2017-02-28-02.
[Xperia Z4/Z3+ Android Development] nailyk:
You fixed it? Nice!!
[Xperia Z4/Z3+ Android Development] DiscMan55:
Had to fork twrp to cherry-pick the commit [MENTION=1162986]Captain_Throwback[/MENTION] mentioned. Not the most ideal solution but forking twrp itself temporarily is better than modifying lineage os.

Next challenge: LineageOS itself!
[Xperia Z4/Z3+ Android Development] ccxex29:
Is getting into recovery can only granted with Power+VolDown?

Is it possible to enter recovery by Voldown in Boot Load(OEM logo)?
[Xperia Z4/Z3+ Android Development] DiscMan55:
Button on logo is a custom behaviour added by custom kernel. Original Sony bootloader only works with power and vol down
[Xperia Z4/Z3+ Android Development] Fauzi alaik:
Tried aroma file manager but stuck at installing, and cant do anything
[Xperia Z4/Z3+ Android Development] DiscMan55:
This can only and absolutely only be installed using fastboot to the FOTAKernel. Other tools that try to be clever and live dd write to the partition from within running OS, I don't know anything about them. Sorry, just use fastboot.
[Xperia Z4/Z3+ Android Development] ch3mn3y:
Can it be flashed to recovery partition?
[Xperia Z4/Z3+ Android Development] Fauzi alaik:
Any news about 3.1.0 version?
[Xperia Z4/Z3+ Android Development] SH1M4BD3:
What if flashed throughh current twrp, install img, will it works??thanks
[Xperia Z4/Z3+ Android Development] DiscMan55:
This is not twrp flashable zip. You will get error and it will fail.
[Xperia Z4/Z3+ Android Development] DiscMan55:
About 3.1.0 I built it but it is very buggy. Already bugs were found in adb backup and restore. I will wait till bugs are solved before releasing. This still works fine even for flashing nougat Rom.
[Xperia Z4/Z3+ Android Development] DiscMan55:
I need to implement file based encryption.
[Xperia Z4/Z3+ Android Development] nhojeric214:
hmmmmm where did i go wrong guys? here's my log for fastboot

25/003/2017 00:03:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\DBCOM\Downloads\recovery-2017-02-28-02.img

25/003/2017 00:03:04 - INFO - Flashing selected kernel

25/003/2017 00:03:04 - INFO - target reported max download size of 536870912 bytes

25/003/2017 00:03:04 - INFO - sending 'boot' (16760 KB)...

25/003/2017 00:03:04 - INFO - OKAY [ 0.378s]

25/003/2017 00:03:04 - INFO - writing 'boot'...

25/003/2017 00:03:04 - INFO - FAILED (remote: Command not allowed)

25/003/2017 00:03:04 - INFO - finished. total time: 0.398s

25/003/2017 00:03:04 - INFO - FASTBOOT Output:

target reported max download size of 536870912 bytes

sending 'boot' (16760 KB)...

OKAY [ 0.378s]

writing 'boot'...

FAILED (remote: Command not allowed)

finished. total time: 0.398s

25/003/2017 00:03:04 - INFO - Please check the log before rebooting into system

25/003/2017 00:03:22 - INFO - Device disconnected
[Xperia Z4/Z3+ Android Development] ch3mn3y:
[MENTION=5544543]nhojeric214[/MENTION]

Not sure if Z3+ has this option, but did You enable "OEM unlock" in Settings->Developer

Try to change name of the file. Week ago had problem with flashing kernel to my Z2 - boot_Z2.img gave error, but boot.img didnt'''

However why are You flashing Recovery as Kernel? Wont be easier to flash it directly to /FOTAkernel partition?

Not asking about unlocked bootloader, coz think that You have.
[Xperia Z4/Z3+ Android Development] the_brad:
The command for this:

fastboot flash recovery recovery.img (<<rename your TWRP-file to that name)
[Xperia Z4/Z3+ Android Development] nailyk:
Your bootloder doesn't seems to be unlocked.

Also are you trying to flash a z3+ recovery on z3 compact?
[Xperia Z4/Z3+ Android Development] nhojeric214:
No, my it's workmate's z3+ he want to try custom rom on his new phone. Got it already sorted out now. It's a bummer that even just to be rooted, you have to unlock bootloader
[Xperia Z4/Z3+ Android Development] DiscMan55:
Also why are you trying to flash recovery on boot partition! Recovery is not kernel! Flash to recovery or FOTAKernel (on this device the 2 names point to the same physical partition)

And yes bootloader must be unlocked to flash any non Sony thing of any kind
[Xperia Z4/Z3+ Android Development] nhojeric214:
I've been doing this way on my sola and z3c so I've expected it also to work on my workmate's z3+.
[Xperia Z4/Z3+ Android Development] prosnz:
I am currently on lineageos 14.1, z3+single Sim, rooted.

Noob question: can i simply flash this?

Because the last time i tried to flash a twrp I had a bootloop. I had to reflash stock Rom.

My workaround was then only hotbooting the trwp.

But since I am on a nightly rom - I am bored to always start my laptop just for fastboot, when an update appears.

Edit: worked.
[Xperia Z4/Z3+ Android Development] GreyLeshy:
Posted a new TWRP v3.1.0 in the subject.
[Xperia Z4/Z3+ Android Development] SH1M4BD3:
does this TWRP works on latest sony ftf release??, try some (by,quarx,but won't boot into twrp
[Xperia Z4/Z3+ Android Development] MoeDia:
How to remove it from the Fota partition?
[Xperia Z4/Z3+ Android Development] ridwanxperia:
support 7.1 z3+ dual 6533..?
[Xperia Z4/Z3+ Android Development] DiscMan55:
Released 2018-03-04-01-ivy.

Updated to TWRP latest android-7.1 branch (currently 3.1.1-1) and sync'd latest ivy / kitakami sources.
[Xperia Z4/Z3+ Android Development] renan37325:
Cool :good: :good:
[Xperia Z4/Z3+ Android Development] magnulu:
Just to be sure

Hi,

Thanks for all your great effort on this. I am a first time sony flasher, the path to lineage led me here. I have a E6553/Z3+ single sim, 100% stock.

Service menu tells me bootloader unlock is allowed.

Current phone software version is 1292-0963_32.4.A.1.54

All good in the hood to follow your instructions in the first post? Any hidden secret powerknowledge I might need? I have flashed samsung devices some years ago, so I think I'll handle the basics. Experience tells me that the lineageos wiki install page is not always 100% (at least not for samsung devices!). In example, their link to TWRP for this device was dead. Probably because TWRP ended official support I guess.

Thanks!
[Xperia Z4/Z3+ Android Development] DiscMan55:
If you haven't already, you should backup your TA partition (in case you ever want to go back to stock) otherwise you will permanently lose some sony-only features (better camera quality, sound enhancement, ... etc.) which are not supported on lineage anyway.

You have to unlock the bootloader first, follow sony's instructions and get the unlock code and use it in fastboot to unlock your phone. (Note: This will factory reset your phone and erase DRM Keys and TA partition, you will need to backup them up first if you ever intend to go back to stock).

After that just flash as in the first post using fastboot to FOTAKernel. You are already on a recent firmware with the new bootloader, after you flash it you should be able to enter twrp by holding volume and power button as described in the first post.
[Xperia Z4/Z3+ Android Development] magnulu:
Thank you very much for that tip. I will look into it as soon as real life lets me do it :)
[Xperia Z4/Z3+ Android Development] pradeepvg:
anybody please give the working version of twrp for android 5.0.2
[Xperia Z4/Z3+ Android Development] zacharias.maladroit:
just flash the latest TWRP version from https://xdaforums.com/xperia-z4/development/recovery-twrp-v3-0-3-0-encryption-t3564016

to the "recovery" partition

fastboot flash recovery twrp.img

Then reboot to recovery via fastboot

fastboot reboot recovery

Make a backup of your /system , /data , /boot

and copy that backup to your PC.

Have you flashed Nougat ftf before via FlashTool ?

If yes, you can boot to TWRP directly:

Turn off phone,

Hold "Volume Down" + Power Button

Sony Logo -> Keep press "Volume Down" ONLY (release Power Button)

then it should boot into TWRP from recovery partition
[Xperia Z4/Z3+ Android Development] pradeepvg:
i asked for android 5.02
[Xperia Z4/Z3+ Android Development] yellowspirit89:
After unlocking the bootloader, I have installed TWRP using "sudo fastboot flash FOTAKernel recovery-2018-03-04-01-ivy.img" on my Z3+ (E6553 - ivy).

Trying to boot into TWRP fails.

Holding the 'volume down' key, then pushing 'power' and not releasing 'volume down' and 'power' until sony logo appears, the device just boots into stock android.

If I keep pressing 'volume down' longer than I end up in stock android in protected mode.
[Xperia Z4/Z3+ Android Development] dillusi:
I would like to know is there any specific guide for installing TWRP? finding the guides through the forum but did not sure which one is it.

Thanks.
[ZenFone 2 Q&A, Help & Troubleshooting] xalekhinex:
after a normal restart my phone get stuck in a bootloop.

i've restarted in rescue mode to wipe data/factory reset but when i've tried i receive this error message:

formatting /data

formatting /cache

E: failed to mount /asdf (invalid argument)

E: can't mount /asdf/recovery/last_log

E: can't open /asdf/recovery/last_log

data wipe complete

E: failed to mount /asdf (invalid argument)

E: can't mount /asdf/recovery/last_log

E: can't open /asdf/recovery/last_log

i've download the stock firmware WW_21.40.0.1999 and with fastboot i've flash recovery, boot and system but i've get the same error. i've also tried to apply the firmware via sd card and adb but i get the same error

i've boot lock and usb debug not active.

some ideas?

tnx in advance and forgive my bad english :)
[ZenFone 2 Q&A, Help & Troubleshooting] zeiar:
Same problem

I have this problem too. How to fix thjs?!