Database Info

adb android not support on security

Hello, when im trying to change charge mode with command "fastboot oem off-mode-charge" i got message
Minimal ADB and Fastboot>fastboot oem off-mode-charge disable
...
FAILED (remote: not support on security)
finished. total time: 0.013s
Phone is unlocked (checked in fastboot getvar all unlocked: yes)
Phone is Alcatel 1x 2019 with android 6.0
Anyone can help me with it?

I also have the same problem with Hotwav (wheatek) H1 device. Unlocked the bootloader, but when trying to disable off-mode-charge I get the same error. Maybe there is some security setting that needs to be disabled first?

You both are speaking of FASTBOOT, and not of ADB as cited in this theads header.

Yes, but this is changed in fastboot, no? It should work, bu doesn't

I get the same error. And when I enter "adb devices" I get "1023456789ABCDEF unautorized". "fastboot devices" does not show anything

To fix this "unauthorized" error you
1. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" .
2. Restart ADB Server:
Then restarted adb server
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
It is now authorized!

Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
{
"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"
}

time2fly said:
Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
View attachment 5899259
Click to expand...
Click to collapse
First of all: The command fastboot is for fastboot. The command adb is for adb. When booting into fastboot then adb doesn't work.
To use it in your car as GPS tracker. With an additionally mobile connection? Or only pure GPS? Where is the phone? Somewhere outside the car on the top or well hidden inside the glove box?
Let's assume your phone is able to get a GPS signal. How to track it?

Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.

Looking at it, this seems intentional from manufacturer's side. They can enable it and you updated firmware if you pay a large sum of money. I've tried all the tricks and hacks mentioned in this forum – nothing helped. I don't know why these Chinese phones are so "secured". Trying to force businesses to pay when they discover that something rarely used by ordinary people but essential for some business project is disabled in the stock firmware?

Well, I don't consider "boot on charge" as rarely needed. Everyone who goes to bed at night and uses his phone as an alarmclock needs this. It's not understandable that this is not an option in the settings. And we're talking about Android 9 here!

0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.

time2fly said:
Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.
Click to expand...
Click to collapse
Try fastboot oem help to see the available options/features. Maybe there is another corresponding option that needs to be enabled.

alecxs said:
0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.
Click to expand...
Click to collapse
Yes, that was my backup strategy. But how do I root it? There is no TWRP version for the Soyes XS12, and I have no other knowledge of how to root phones. I can seem to send adb commands, but not fastboot.

either with WwR MTK v2.51 beta + SP Flash Tool or with mtkclient. your first goal: dump the para partition or the ROM/boot.img off the phone while in preloader mode. once you have it, you can modify it or root the phone.
mtk-su could also work.

There is nothing you can do even if you root the phone. The system partitions cannot be mounted in r/w mode.

don't need to mount system rw on systemless-root.

Is the Alcatel 9029W rootable?

I just got this tablet a few days ago so I was wondering if it was possible to root it as I already have a primary phone that I use.

Search the WEB for "root any MTK device"

jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
Will the method still work even though it's not a MTK device? On CPU-Z it says it's a ARM Cortex device.

ARM Cortex is a processor technology,, what in your case is used by MediaTek when they developed and produced the chipset for your phone.

That seems to make sense. I'll try the method when my laptop charges back up. Thanks for the help

jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
The method doesn't seem to work because after doing
adb reboot bootloader
The device just reboots and when I do
fastboot oem unlock, it gets stuck on waiting

What's the method you always are referring to?

jwoegerbauer said:
What's the method you always are referring to?
Click to expand...
Click to collapse
The mtk one you told me about

I was following this to be more specific

The steps to prepare programmatically unlocking a phone's bootloader by means of fastboot what most people do - me included - are
Code:
adb devices <- your phone must be listed here
adb shell "getprop ro.oem_unlock_supported" <- The return value must be 1, if not then don't proceed
adb reboot fastboot <- or: fastboot reboot bootloader
fastboot devices <- your phone must be listed here
to verify the phone is succesfully connected and acting in fastboot ( aka bootloader ) mode.
If phone isn't shown then a fastboot connection doesn't got established.

adb devices - works
adb shell "getprop ro.oem_unlock_supported" - I get a 1
adb reboot fastboot - device just reboots normally
fastboot reboot bootloader - says <waiting for any device>
fastboot devices - just shows a empty line of text

{
"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"
}

You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.

jwoegerbauer said:
You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.
Click to expand...
Click to collapse
I've finished doing 1 and 2. Do I retry going into fastboot again?

Oskii said:
I've finished doing 1 and 2. Do I retry going into fastboot again?
Click to expand...
Click to collapse
Do what you think is right ...

It seems that the device is still unable to go into fastboot mode.

I will double check to make sure

In @Oskii 's defense, I've had some Alcatel devices that somehow seemed to have fastboot disabled (namely the Alcatel 1 / Orange Rise 54, IIRC), I don't know how though. It's just impossible to boot into any bootloader/fastboot mode (or at least I never found out how).
I *did* manage to (sort of) root them using a method I don't remember (sorry ; it was an obscure app), but it was unreliable : root wouldn't always "get applied/stick" after boot and I had to reboot and cross my fingers to make it work again.
I know it's not of much help, but still…

It's still not working :v

It cannot without booting to fastboot mode.

Zeblaze Thor 6 TWRP

Zeblaze Thor 6 TWRP 3.4.0.0 (unofficial)
99% complete
>Settings >About watch >Build number
>Click on the build number
>Developer options enabled
>Back
>System >Developer options
>OEM unlocking
>USB debugging
Open Minimal ADB and Fastboot folder
Paste the recovery.img file inside the Minimal ADB and Fastboot folder
Open Minimal ADB and Fastboot
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
Note: TWRP can read but not modify the contents of dynamic partitions. You cannot modify an apk file. But you can modify a super.img partition. I'm thinking of converting dynamic partitions in the future. So we can get the full benefit of TWRP. I hope it will be successful.
if you want to delete/add an apk file edit the super.img section using crb_v3b10. Flash the super.img partition using TWRP and don't forget to run the following command using the Bootloader.
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
recovery.img
drive.google.com
{
"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"
}

friend would it be possible to make a version for Kospet Optimus 2?

I am neither a programmer nor an editor. I'm just an enthusiast. I don't have any information. I just analyze and modify it. It actually belonged to TWRP Lemfo lem12 pro. I analyzed it and adapted it for Zeblaze Thor 6. Then I analyzed the UI. I tried to save the user interface from its boring appearance and turn it into a beautiful and useful interface. This job took 2 months. I have not yet received a positive response feedback. Maybe nobody liked this new UI.
I don't have Kospet prime 2 to do an adequate analysis. All I can do is replace its core. They have similar hardware. So there is a chance it will work. Now it's up to you to try it. Please give feedback if it works or not.
Follow the above procedures for installation.
Good luck amigo.
recovery_KP2_TWRP.img
drive.google.com

AYALTUN said:
Zeblaze Thor 6 TWRP 3.4.0.0 (unofficial)
99% complete
>Settings >About watch >Build number
>Click on the build number
>Developer options enabled
>Back
>System >Developer options
>OEM unlocking
>USB debugging
Open Minimal ADB and Fastboot folder
Paste the recovery.img file inside the Minimal ADB and Fastboot folder
Open Minimal ADB and Fastboot
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
Note: TWRP can read but not modify the contents of dynamic partitions. You cannot modify an apk file. But you can modify a super.img partition. I'm thinking of converting dynamic partitions in the future. So we can get the full benefit of TWRP. I hope it will be successful.
if you want to delete/add an apk file edit the super.img section using crb_v3b10. Flash the super.img partition using TWRP and don't forget to run the following command using the Bootloader.
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
recovery.img
drive.google.com
View attachment 5475289View attachment 5475293
View attachment 5475285View attachment 5475283View attachment 5475287View attachment 5475295
View attachment 5475279View attachment 5475277
Click to expand...
Click to collapse
can you please send me link to crb_v3b10 i cant not find it anywhere and beta12 and 14 do not work for me

blaze2051 said:
can you please send me link to crb_v3b10 i cant not find it anywhere and beta12 and 14 do not work for me
Click to expand...
Click to collapse
I deleted crb_v3b10. Even if you reinstall crb_v3b10, it still won't work. Even if you reinstall crb_v3b10, it still won't work. The problem is not the versions. The problem is that you did the installation incorrectly. Delete all versions. Download the latest version. Run crb.exe. Select the Unregister distro option. Select the Import distro option. Select the test distro option. Close the window. Crb will open automatically. Tried on the latest version for windows 10. I don't know if it works on older windows 10 versions. It also works on Windows 11.

AYALTUN said:
I deleted crb_v3b10. Even if you reinstall crb_v3b10, it still won't work. Even if you reinstall crb_v3b10, it still won't work. The problem is not the versions. The problem is that you did the installation incorrectly. Delete all versions. Download the latest version. Run crb.exe. Select the Unregister distro option. Select the Import distro option. Select the test distro option. Close the window. Crb will open automatically. Tried on the latest version for windows 10. I don't know if it works on older windows 10 versions. It also works on Windows 11.
Click to expand...
Click to collapse
ill try that but all the options are blacked out and the only one i can select is enable wsl before it will let me choice anything else which would be import distro after a reboot of windows

@AYALTUN How did you unlock bootloader? When I type fastboot flashing unlock I have info on my watch screen about pressing vol button but non of them works. I have Thor 5 smartwatch and only power and back buttons. When I press them nothing happens. Pls help me i am confused.

ktl20 said:
@AYALTUN How did you unlock bootloader? When I type fastboot flashing unlock I have info on my watch screen about pressing vol button but non of them works. I have Thor 5 smartwatch and only power and back buttons. When I press them nothing happens. Pls help me i am confused.
Click to expand...
Click to collapse
I'm sorry. If you get a warning saying press the volume button, there is nothing you can do. You will not be able to unlock bootloader.

Create lineageos custom rom for any device

hi, I own several Chinese tablets. precisely because they are Chinese they are stuck with their Android (8-9) and will never be updated. I intend to understand how to unlock these devices and understand how they work, and create a custom rom based on lineageos to try to do this. I've seen several threads on this forum but I've never figured out how to actually work with it.

do you have kernel source code and binary blobs for that tablet?

no. its china tablet. can i extract it?
my tablet: Vankyo S20 matrixpad

no, you can't extract kernel source code from tablet.

so what i can do?

nothing. you can port precompiled ROM, but that only works on between same android version.
you can run GSI but requires treble device (separate vendor partition) or DSU loader

ok, can you give me the istructions?

instructions for what?
https://www.google.com/search?q=rom+porting+guide+site:xda-developers.com
https://forum.xda-developers.com/t/what-is-treble.3815957
https://www.xda-developers.com/dsu-sideloader-boot-custom-android-gsi

my device supports treble and VDNK 28.0. I checked with the app. https://play.google.com/store/apps/details?id=com.kevintresuelo.treble

so unlock bootloader, disable avb/dmverity (vbmeta) and flash system.img from fastboot
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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...
forum.xda-developers.com

Thanks!
i can also flash on the chinese tablet (treble compatible as the app), right? Can I already insert android 12/13 or risk weighing down the tablet and it is better that I use 11?
what is avb dmverity? how i can disable it?
and for the Gapps?

after unlocking, create vbmeta_disabled.img with this python script avbtool.py and flash it from fastboot
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta_disabled.img
then you can install GSI. I personally prefer android 10 because higher versions are too restricted for me.

how can i execute the script? I tryed to execute it in Python but gives me error.
this can work? https://forum.xda-developers.com/t/guide-unlocking-bootloader-and-disabling-verifiedboot.4104045/

without knowing what error I can't help you with python script.
if python don't work for you, you can try with stock vbmeta instead. the fastboot --disable-verity --disable-verification flag will change a byte during flashing process so avb becomes disabled. I do not recommend to flash random vbmeta of foreign devices.
you can backup own stock ROM off device with spd-research-tool (do your homework, I never used and can't assist)
https://androidmtk.com/download-spd-research-tool

so i need to write --disable-verity --disable-verification flash "image.img" in the flashing fastboot command?

yes, for vbmeta partition (like post #12, #13) once you have unlocked bootloader.

ok
when trying to unlock the bootloader with "fastboot flashing unlock" this happens
{
"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"
}
FAILED (remote: Not implemet.)
finished. total time: 0.001s
i have an already unlocked bootloader? or i cannot unlock it?
edit: i executed this command: fastboot getvar unlocked
-----------
unlocked:
finished. total time: 0.001s
----------
????
i cannot determine if is locked or not XD

you can determine by doing something that is only allowed in unlocked state, such as formatting cache partition (does not harm)
Code:
fastboot format:ext4 cache
you can try different cmd
Code:
fastboot oem unlock
make sure in android you have set oem unlocking allowed in developer options as prerequisite for fastboot unlock.

aIecxs said:
you can determine by doing something that is only allowed in unlocked state, such as formatting cache partition (does not harm)
Code:
fastboot format:ext4 cache
you can try different cmd
Code:
fastboot oem unlock
make sure in android you have set oem unlocking allowed in developer options as prerequisite for fastboot unlock.
Click to expand...
Click to collapse
Ok, i try.
I already tried oem unlock, but it does not recognize the command.

some OEMs use different command (like Vivo fastboot bbk vivo_bsp unlock_vivo) some use special app or other tools (Xiaomi Unlock tool) and some devices aren't unlockable at all.
try to dump ROM with SPD research tool for further analysis, maybe bootloader lock state can be modified offline (like devinfo frp or config partition)
you can examine android bootloader (aboot/sboot/lk/...) for hidden fastboot commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com

ZS670KS rawprogram() and patch0

Dear all, my ZS670KS-2A014EU Asus Zenfone 7 flip has bricked. As well known now, an update in Android has caused some issue to his motherboard and I got the dump loop. Now it sticks on bootloader loop. Unfortunately I have never set an oem unluck and all flash via adb or fastboot have been run unsuccessfully. I have only one shot: put the phone in EDL and QFIL for flashing it.
Now: i miss the firers files *.mbn and the
rawprogram() and patch0 fire.I have also tried to use Python GPT tool to create partition.xml (from gpt_both0.bin) but I have got a parse error! I'm desperate!! Might someone of you, please support me giving more indications how to operate? Thanks in advance!

read in proper section for your device.
test points
ROM
prog_firehose_ddr_lp5.elf.E
EDL tool for creating rawprogram0.xml
if fastboot is working you can try to flash with unofficial Asus Flash Tool first. it may also possible to boot into EDL mode from fastboot.
Code:
fastboot oem enter-dload

aIecxs said:
read in proper section for your device.
test points
ROM
prog_firehose_ddr_lp5.elf.E
EDL tool for creating rawprogram0.xml
if fastboot is working you can try to flash with unofficial Asus Flash Tool first. it may also possible to boot into EDL mode from fastboot.
Code:
fastboot oem enter-dload
Click to expand...
Click to collapse
Thanks for your support.
I have tried
fastboot oem enter-dload
But it doesn't work.
An AFT is stucked in "Disconnected" process --> not working.
Finally I follow the original process with EDL and as before I'm stucked in point 4) creating the rawprogram () and patch0. The python job is blocking in this edl --serial and fhloadparse newstuff Loaders. It shows error that edl and fhloadparse are not known commands.
Any additional instructions?
Thanks in advance. BR

you can pass the loader directly from each cmd line
https://forum.xda-developers.com/t/4548939/post-88104871
or find the fhloaderparse in tools directory
https://forum.xda-developers.com/t/4531349/post-88029447

too many errors on python commands...I changed namesadding py (edl.py), changed the path, system variables...I followed all instructions in the link but I got " edl.py The system cannot execute the specified program". I will try under linux if it goes better than windozzz. Let's see

I have tried livecd and even Rom2Box too but I had no luck, I have several error "ssd.bin"missed.. etc. I was able to do rowprogram but I'm not sure if it's correct (i got several warnings). Ijust need to 2 files: rawprogram() and patch0. Can somebody provide me them fot my ZS670KS-2A014EU Asus Zenfone 7 flip? Thanks. BR.

no xml files needed for linux. what is the exact command that failed, and what error message?

You can always try my native Windows EDL client. http://www.temblast.com/edl.htm
The command arguments are different, but simple enough.
Editorial: This mania for rawprogram.xml is overblown.
Those stupid files are so much blah-blah-blah.
You only need to know 1) what file goes to 2) what partition.
"Lemme see, where would a recovery.img go?"
Disclaimer: Ok, if you were programming this in a factory and you want to program GPT and everything else without even reloading the GPT, this makes some marginal sense when you have a million to do.

Renate said:
You can always try my native Windows EDL client. http://www.temblast.com/edl.htm
The command arguments are different, but simple enough.
Editorial: This mania for rawprogram.xml is overblown.
Those stupid files are so much blah-blah-blah.
You only need to know 1) what file goes to 2) what partition.
"Lemme see, where would a recovery.img go?"
Disclaimer: Ok, if you were programming this in a factory and you want to program GPT and everything else without even reloading the GPT, this makes some marginal sense when you have a million to do.
Click to expand...
Click to collapse
Hi Renate, I got the error message "this app can not run on your pc"...
even with PowerShell:
edl.exe /l
Program 'edl.exe' failed to run: The specified executable is not a valid application for this OS platform.At line:1
char:1
+ edl.exe /l
+ ~~~~~~~~~~.
At line:1 char:1
+ edl.exe /l
+ ~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
I have tried with Windows7 compatibility mode but nothing to do.
How to proceed?
Thanks.

pingolaido said:
Hi Renate, I got the error message "this app can not run on your pc"...
Click to expand...
Click to collapse
That is very stange. It's the type of error when the file is not even recognized as an executable.
Maybe the download was bad, grab a new copy.
http://www.temblast.com/download/edl.exe
Size=139,776
MD5=c106d7c6f742ec592e3b0636da756317
Mmm, don't you have to do .\edl.exe in PowerShell?
I don't use it.

Renate said:
That is very stange. It's the type of error when the file is not even recognized as an executable.
Maybe the download was bad, grab a new copy.
http://www.temblast.com/download/edl.exe
Size=139,776
MD5=c106d7c6f742ec592e3b0636da756317
Mmm, don't you have to do ./edl.exe in PowerShell?
I don't use it.
Click to expand...
Click to collapse
Hi,
I'm using the windows CMD prompt with Admin grants but I got the following error message:
C:\>edl.exe /l
Found EDL 9008
Could not open device
Could it be that device is locked? As I explaned since begining of the post, "USB debuging" was not enable in Android setting.
Any sugestions how to proceed? Thanks.

pingolaido said:
I'm using the windows CMD prompt with Admin grants but I got the following error message:
Click to expand...
Click to collapse
Your Qualcomm virtual com port drivers are stealing the interface.
Uninstall them and install the Zadig driver as per my EDL webpage.

Thanks for your prompt reply. I'm able to connect but I got this:
Found EDL 9008
Resetting Sahara
Could not write device
I think it's related to oem lock which I'm not able to unlock. Any further advices?

pingolaido said:
Could not write device
Click to expand...
Click to collapse
Do a clean reset back to EDL mode.
Sahara is balky, but it doesn't know anything (or care) about OEM anything.

I have cleaned all Qualcomm and Samsung drivers, re-instal Zadig WCID drivers (as in photo below), I have also put the phone in EDL modus hardwarly (pin connectors) but still got:
Found EDL 9008
Resetting Sahara
Could not write device
{
"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"
}

sorry,after 2 restarts it works... windows!!! I let you know

question about loaders: in the link of EDL.com there are loader in the folder "asus_wingtech" for Asus Zenfone ZS630KL, ZS660KL, zenfone_ares but not for my ZS670KS. Which shall I use? Thanks. BR

pingolaido said:
Which shall I use?
Click to expand...
Click to collapse
You may just have to try a few.
Loaders work for multiple models.
You can use my qcomview.exe to see which with qcomview.exe /m random_loader.bin
If a loader fails to load, you have to start over with fresh EDL mode.
Also, you can't disconnect the USB cable during EDL mode, replug it and expect it to work without another reset.
This is all a limitation of the Sahara implementation, not of the EDL client.

What about if I use prog_firehose_ddr_lp5.elf from raw stock rom? shall it work?

pingolaido said:
Shall it work?
Click to expand...
Click to collapse
I wouldn't know. Be careful. I saw some post about DDR specific loaders where some had the wrong voltage.
Why don't you (why didn't you?) post the HWID and Hash that edl printed out?