Database Info

Guide to fix "EFS corruption" (no SIM card recognized after April update)

Just follow the steps I gave and download (it will delete your phone) :
Twrp : Download
ADB : Download
Fastboot Rom (v9.6.4.0) : Download
Before you do my steps :
1. Run the 15 seconds adb installer, after that enter your 'C:' drive and enter the ADB folder.
2. Open the fastboot rom (the v9.6.4.0 the we downloaded earlier) with 7zip twice until you'll see a folder, copy all of the files to the ADB folder created earlier (don't copy the folder it self, copy the files inside, so in the ADB folder you'll have lots of file and one of them 'flash_all' if you do you are okay).
{
"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"
}
3. Copy the twrp-3.2.3-0-daisy.img (just rename in to twrp.img) to the ADB folder created earlier.
4. Open developer options on your device and enable OEM unlocking & USB debugging.
Now we can proceed :
1. Open CMD and type 'cd c:/adb' and after that type 'adb reboot bootloader' your phone will show a massage just press allow always and continue, when fastboot screen appear type 'fastboot oem unlock' (don't touch the phone until it boots up to the system after that turn it off and hold down the 'power + volume down' until you are back at the fastboot screen).
Now your bootloader is unlocked and we are ready to proceed.
2. Type in CMD :
fastboot erase modem_a
fastboot erase modem_b
3. We want to go ahead and flash the first Rom ever created for the device so type in CMD 'flash_all' (DON'T USE THE 'flash_all_lock' cause you will have to unlock the bootloader again) and let it work until you greeted by the os after that go back to the fastboot screen like mentioned above.
4. Type 'fastboot boot twrp.img (if you renamed it like I said) and then twrp will boot up, if it ask for a password just hit cancel and proceed.
5. Press Advanced and there should be a Terminal enter it and type these two commands :
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
6. After typing them exit twrp by going back to his home screen using the home button, press reboot and reboot to system (do not install twrp app, there should be an option just don't swipe to install), boot back to the os and see if you have reception, if you have congratulations you have fixed your EFS.
Now we need to lock the bootloader :
1. If everything works correctly type in CMD 'fastboot oem lock' (if you lock it without phone booting up to the system and you don't know if it works correctly you could potentially brick your phone so be carful).
2. I do recommend to set it as new device and install all of the updates all the way to pie, after that factory reset and copy your backup from your backup (Could be Google Drive or whatever you backed up with).
3. Just boot to your phone and enjoy
Credits :
j1505243 For uploading OTAs and Dumps for the Mi A2 Lite.
Snoop05 For creating the 15 seconds ADB installer.
d1ngh For creating TWRP for the Mi A2 Lite and working out with teamwin project to get it official.

easy method for doing this step
https://forum.xda-developers.com/mi-a2-lite/how-to/gsi-tweaks-fix-t3899630
first fix

eremitein said:
easy method for doing this step
https://forum.xda-developers.com/mi-a2-lite/how-to/gsi-tweaks-fix-t3899630
first fix
Click to expand...
Click to collapse
The point in my guide is going also back to stock and reinstalling the first working modem.
Thanks for that guide.

¡THANKS!
Thanks! This worked for me

I've not solved the network problem with your guide
Hi Noam, I'm having the same problem you tried to solve in this thread thread by Le Dam about the problem. I've done all the things you explain step by step:
fastboot erase modem_a
fastboot erase modem_b
twrp and those 'dd' commands in the phone terminal (dunno if it was an error but said 'No space left on device', should be ok btw)
flashed the 9.6.4 global image you linked
but still it doesn't work (I've read on other threads that it can be due to my carrier, but three days ago the network was there and worked fine until I decided to downgrade (this gave me problems that I solved, last problem is this one about network))
I also tried another working sim card from another carrier and still doesn't work.
On settings > Network & Internet > Mobile Network > Sim slot 1 or 2 (doesn't seems to make difference the slot) I find no way to interact (I'm using daisy V9.6.4).
Going in the "*#*#4636#*#*" menu I see IPv6 fail (attached in the photo)
https://gitlab.com/aris997/daisy/-/blob/master/Screenshot_20200511-173649.png
https://gitlab.com/aris997/daisy/-/blob/master/Screenshot_20200511-173659.png
Hope you can help me with this problem, thank you for the excellent guide to solve the problem

aris997 said:
Hi Noam, I'm having the same problem you tried to solve in this thread thread by Le Dam about the problem. I've done all the things you explain step by step:
fastboot erase modem_a
fastboot erase modem_b
twrp and those 'dd' commands in the phone terminal (dunno if it was an error but said 'No space left on device', should be ok btw)
flashed the 9.6.4 global image you linked
but still it doesn't work (I've read on other threads that it can be due to my carrier, but three days ago the network was there and worked fine until I decided to downgrade (this gave me problems that I solved, last problem is this one about network))
I also tried another working sim card from another carrier and still doesn't work.
On settings > Network & Internet > Mobile Network > Sim slot 1 or 2 (doesn't seems to make difference the slot) I find no way to interact (I'm using daisy V9.6.4).
Going in the "*#*#4636#*#*" menu I see IPv6 fail (attached in the photo)
https://gitlab.com/aris997/daisy/-/blob/master/Screenshot_20200511-173649.png
https://gitlab.com/aris997/daisy/-/blob/master/Screenshot_20200511-173659.png
Hope you can help me with this problem, thank you for the excellent guide to solve the problem
Click to expand...
Click to collapse
Redo the thing on Twrp, It doesn't suppose to give you "No space left on device" try a different Twrp if the problem presist.
On the device make sure in network settings it says 4G as recommended, Don't put it on LTE only cause some carriers doesn't work with that at all.
also I have noticed that your "Mobile radio power" is toggled off (Make sure it's on), and about the IPV6 it doesn't really matter just ignore it...

finally solved after 4 days of struggle
Hi, I tried several time with your guide but didn't work so I searched on youtube and find out that my phone was not showing up the IMEI of the two sim slot
doing "*#06#" you should see the Serial No. and the IMEI bar codes but I was getting all zeros
I then followed that guide.
At first try didn't work then I swapped the sim in the second slot and worked (at the beginning I was getting only 2G but in the settings > Network & Internet > Mobile Network > Preferred type of Network choose 4G)
then I 'fastboot oem lock' to get it back to true factory reset
thank you for help, I don't know if needed but thanks

Did all but still no IMEI it shows 0 and "No sim card"

[GUIDE] How to root Oukitel K13 Pro using Magisk [EU version]

If you’re using Oukitel K13 Pro or planning to buy it, this guide is for you. If you’re an advanced user or a developer who customizes, flash files quite often and now want to root your device, you have to follow this guide properly. Here in this article, i will share with you an easy method to root Oukitel K13 Pro Using Magisk.
What is rooting?
Rooting for Android device means access to the root directory of your android mobile system. It will give you the superuser access as an administrator to use your device over an Android subsystem and system apps. It’s quite similar to the jailbreaking. Without rooting your Android handset, you can’t change/edit/delete system files or apps easily. Most of the advanced users or developers perform rooting access for customizations and modifications. This isn’t necessary if you’re a normal user.
Steps To Root Oukitel K13 Pro via Magisk
First of all, you should unlock bootloader on Oukitel K13 Pro
Disclaimer:
Unlocking the device bootloader and installing root will void your device warranty (if applicable). This rooting method is only tested on the EU version of the manufacturers firmware, i can't guarantee it works on the other firmware versions. The bootloader unlocking process will also delete all the device internal data as well. So, make sure to take a complete backup of device data at first before doing anything. I will not be responsible for any kind of bootloops or crashes or any damage to your device while/after following this guide. Proceed at your own risk.
First of all, charge the phone fully.
Next, enable USB Debugging on Oukitel K13 Pro by going to Settings>About>Software>Build Number and Tap on build number repeatedly so that the Developer mode will turn on.
And then go back and click on Developer options.
In the developer options, there is OEM unlock option then enable that option.
Setup ADB and Fastboot on your PC. Download link: shorturl.at/pyJ16
Install procedure For ADB Fastboot :
1. Launch it That Require administrator privileges.
2. Click Yes to install ADB and Fastboot .
3. Press Yes to install ADB system wide.
4. Click Yes to install Drivers.
5. Continue the Driver installation.
6. 15 seconds passed – it will finish the process
Click to expand...
Click to collapse
Take a backup of the necessary data on the Oukitel K13 Pro as this process will wipe the user data.
Connect your Oukitel K13 Pro to the computer.
Now open a command window by typing CMD to the windows search.
You may get a request to authorize USB debugging on the device, accept it.
Once opened, type the following code to see if your device is detected and authorized.
adb devices
Click to expand...
Click to collapse
If you can see your device then type this command to boot it into the bootloader mode.
adb reboot bootloader
Click to expand...
Click to collapse
Your phone should now be booted into the bootloader, to check if its detected type the following command.
fastboot devices
Click to expand...
Click to collapse
As a result, this will show the serial number of the phone, you are ok to proceed if you can see it, if not, then your drivers are not properly installed on the pc.
Finally, type the command below to unlock the bootloader on the Oukitel K13 Pro.
fastboot flashing unlock
Click to expand...
Click to collapse
Now you should see a confirmation screen on your phone, confirm the unlocking on your phone. This will begin the bootloader unlocking process, which shouldn't last more than a couple of minutes.
Your phone should automatically reboot into android but if not, type this command to reboot it.
fastboot reboot
Click to expand...
Click to collapse
Your phone's bootloader is now unlocked and ready to be patched with Magisk.
Go thru the initial setup and double check in developer settings that the unlock bootloader option is greyed out.
Enable USB debugging again.
Open command window again.
Check that your device is detected by using the command.
adb devices
Click to expand...
Click to collapse
Reboot into the bootloader by using the command.
adb reboot bootloader
Click to expand...
Click to collapse
Download the Magisk patched boot img: shorturl.at/pCIMP
Patch the boot.img by typing the command.
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
You can also type the command without the file name and drag the .img file to the command window then press enter.
The flashing process will begin. Once completed, type the following command and press enter:
fastboot reboot
Click to expand...
Click to collapse
Magisk is now patched to your Oukitel K13 Pro, download Magisk Manager on your phone from shorturl.at/hvFK9
You should now see that Magisk is installed, enjoy!
{
"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"
}

Thank you for these very concrete explanations. You made my day.

: [GUIDE] How to root Oukitel K13 Pro using Magisk [EU version]
Thanks for this idea.

Do you think this will work for the OUKITEL WP5?

totallybeachin said:
Do you think this will work for the OUKITEL WP5?
Click to expand...
Click to collapse
No, you need the boot.img file from your phone and patch it with Magisk. Check Oukitel's website if the firmware for your phone is available.

totallybeachin said:
Do you think this will work for the OUKITEL WP5?
Click to expand...
Click to collapse
This is only for Oukitel K13 Pro.

كيف

كيفك

ارييموجي خاص بالايفون

[Main Thread] Ulefone Armor 10 (Flash Stock, Unlock Boot Loader, Root, TWRP )

General Information​
Your warranty is now void.
We are 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.
You are choosing to make these modifications and
if you point the finger at us for messing up your device, we will laugh at you
Click to expand...
Click to collapse
This is follow up session of Systemless root on ulefone armor 10 5g by @kc7gr
This thread will be a guide for my revisit if I happen to screw up my Ulefone Armor 10
Always open for improvements and suggestions. I will update post for fine refinement
Happy to share info and Happy Rooting !!!!!

Flash Stock​
Steps​
1 Download SP tool from Ulefone Drive Link
-SP_MDT_exe_v3.2028.02.00(Client)-Current Tool name
2 Download Stock ROM from Ulefone Armor 10 Stock ROM based on EU or NON EU region
-Non EU GQ5000AF1_KSA101_Ulefone_20210507_V02 -NON EU current Stock ROM file name
3 Run as administrator SPMultiPortFlashDownloadProject application from SP_MDT folder
4 Select DA file name MTK_AllInOne_DA.bin from SP_MDT folder
5 Select scatter file from Stock ROM folder MT6873_Android_scatter
6 Tick/ Enable BootRom+PreLoader COM Sel All, EnableAutoPolling
7 Press Scan
8 Switch off the phone
9 Connect USB C cable end to phone
10 Goto download mode by pressing down the volume button on the phone and connect another end of USB to the PC
11 Wait for 3 seconds and Number 1 below BootRom+PreLoader COM Sel All, Com port with number will be enabled
12 Press start button along COM port line or Start ALL button
13
Important Note: Remove USB from PC with other end connected to phone and plug it back immediately
Click to expand...
Click to collapse
14 Flashing will start in the tool
15 Wait for flashing to complete in the tool (it will take few minutes)
16 Once flashing is completed Press Stop or Stop All button in the tool
17 Remove USB from PC
18 Reboot phone
STOCK ROM should be flashed when the phone boots

Unlock Boot Loader & Root​
Do this at user's risk.​User may lose all data, So backup before doing further steps.​
Click to expand...
Click to collapse
​Steps​
Important Note: If your planning to root, Do this along with Unlocking Bootoader else root may fail later
Click to expand...
Click to collapse
​Enable Developer option and USB debugging​1 Goto Phone Settings>>About Phone>>Tap on Build No for 7 times / till developer options enabled message is displayed
2 Goto Phone Settings>>System>>Developer Option>> Enable OEM unlocking >>Enable USB debugging
Unlock Bootloader​3 Download and install minimal ADB and fastboot tool in C:\adb folder
4 Download and install Driver_Auto_Installer_EXE_v5.1632.00.zip
5 Run Command Prompt as administrator
6 Goto C:\adb folder and enter the following commands
7
adb devices
Click to expand...
Click to collapse
8 Tick/enable allow message which pops on the phone
9
adb devices
Click to expand...
Click to collapse
10 Following message should appear along with Serial no of the phone
{
"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"
}
11 If Adb displays serial no with not authorized message, redo Step 8
12 Enter Fastboot mode
adb reboot bootloader
Click to expand...
Click to collapse
13
fastboot -i 0x0E8D devices
Click to expand...
Click to collapse
Important Note:
WIN 10 PC, include -i 0x0E8D for all fastboot codes
Example for WIN 10 PC : fastboot -i 0x0E8D devices
WIN 7/ XP PC dont include -i 0x0E8D
Example for WIN 7/ XP PC : fastboot devices
Click to expand...
Click to collapse
14 If fastboot mode is entered correctly, following message should appear along with Serial no
If you're not getting serial no (space) fastboot message like above pic, then please check for drivers
Android ADB Devices drivers should appear in Device Manager without a yellow triangle exclamation warning mark.
To clear the yellow warning mark, Download MTK_Android_USB_Driver.zip file
In device manager update driver.Browse to MTK_Android_USB_Driver folder
Redo from step 13
15
fastboot -i 0x0E8D flashing unlock
Click to expand...
Click to collapse
16 Press volume up button on phone - message pop up on the phone
17 Following message should appear
Bootloader is unlocked!!!!
Root​
Important Note:
For rooting i.e below commands to be executed immediately after bootloader is unlocked.
To be done after Step 17 without restarting phone or PC
Click to expand...
Click to collapse
18 Download attached vbmeta_null.img and place it in C:\adb folder
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
Click to expand...
Click to collapse
19 Unzip attached boot-magisk.img and place it in C:\adb folder
fastboot -i 0x0E8D flash boot boot-magisk.img
Click to expand...
Click to collapse
20 Reboot fastboot to system
fastboot -i 0x0E8D reboot
Click to expand...
Click to collapse
21 After System boots up click on Magisk Icon and update
or
Download the latest Magisk manager apk to phone and install magisk apk
22 Open Magisk -Update/install and reboot magisk
23 After boot up, Open magisk >> Module >> Universal SafetyNet Fix . Install and reboot
Ulefone Armor 10 is successfully rooted!!!!

TWRP​no official info about it

Reserved for FAQ with A

Hello, thanks for the guide, very well written.
About 0x0E8D code, is it specific for Armor 10 or can I use the same for my Armor X10 PRO?

Xiaomi Redmi Note 7 pro nv data is corrupted

Hello all,
my phone is redmi note 7 pro - violet_china_images_V11.0.5
I restored by mistak the wrong file R.qcn by QPST Flash Tool
when I restarted the phone I got an error nv data is corrupted and still hangs on black screen with this error.
I tryed to inistall the china and india offical recovery rom in the FastBoot Mod but the problem is still
Does anyone have any ideas how I can solve this problem?
Thanks for all.
{
"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"
}

kinghacker02 said:
Hello all,
my phone is redmi note 7 pro - violet_china_images_V11.0.5
I restored by mistak the wrong file R.qcn by QPST Flash Tool
when I restarted the phone I got an error nv data is corrupted and still hangs on black screen with this error.
I tryed to inistall the china and india offical recovery rom in the FastBoot Mod but the problem is still
Does anyone have any ideas how I can solve this problem?
Thanks for all.
Click to expand...
Click to collapse
The image is broken.

kinghacker02 said:
Hello all,
my phone is redmi note 7 pro - violet_china_images_V11.0.5
I restored by mistak the wrong file R.qcn by QPST Flash Tool
when I restarted the phone I got an error nv data is corrupted and still hangs on black screen with this error.
I tryed to inistall the china and india offical recovery rom in the FastBoot Mod but the problem is still
Does anyone have any ideas how I can solve this problem?
Thanks for all.
Click to expand...
Click to collapse
Flash the proper QCN file.

kinghacker02 said:
Hello all,
my phone is redmi note 7 pro - violet_china_images_V11.0.5
I restored by mistak the wrong file R.qcn by QPST Flash Tool
when I restarted the phone I got an error nv data is corrupted and still hangs on black screen with this error.
I tryed to inistall the china and india offical recovery rom in the FastBoot Mod but the problem is still
Does anyone have any ideas how I can solve this problem?
Thanks for all.
Click to expand...
Click to collapse
This is the Indian varient OCN File.

Kenora_I said:
This is the Indian varient OCN File.
Click to expand...
Click to collapse
how to QCN File Proper Flash error show
plzzzz Help

THAT WAS A TWRP BACKUP!

Restore it dont flash it...

proper restore QCN File but still hangs on black screen and power off

Then reflash the OS after it

Kenora_I said:
Then reflash the OS after it
Click to expand...
Click to collapse
Same problum sir
Kenora_I said:
Then reflash the OS after it
Click to expand...
Click to collapse

tyler200298 said:
mine solution can revive phone but at the end pf process u still have a corrupted imei but maybe we can modify efs1.emmc.win and efs2.emmc.win to restore modemst1 e modemst2 (through hex editor maybe). Or root again with magisk or changing device to DIAG mode and flash with qpst (but with this i had no luck).
what do u need:
twrp image for xiaomi (find it here )
minimal adb and fastboot archive (here )
EFS backup from a working redmi note 8 (download from here)
1) first of all we have to put phone in fastboot mode pressing POWER button and VOLUME DOWN till phone restarts and show mi-rabbit
2) put downloaded twrp image in same folder with adb and rename it twrp.img
3) connect phone to PC through USB and navigate to folder "minimal adb and fastboot", here double click on cmd-here.exe or press shift + right click mouse and click on open powershell here or open command prompt here.
4) digit fastboot flash recovery twrp.img
5) press POWER BUTTON and VOLUME UP till u see redmi logo then left power button and still hold volume up
6) now u are on twrp recovery, PC now recognize phone like mass storage and u have to copy and paste EFS folder decompressed (without subfolders) on "TWRP" folder inside phone
7) on twrp click on "RESTORE" tab and choice "EFS" folder then swipe to restore
Wait till phone restart and configure it
Click to expand...
Click to collapse
Find an EFS backup.

phone is done but iemi unknown baseband version unknown

kinghacker02 said:
phone is done but iemi unknown baseband version unknown
Click to expand...
Click to collapse
I can repair it

Kenora_I said:
The image is broken.
Click to expand...
Click to collapse
Flash this efs file and your problem will be solved

Shahbaz9806150 said:
Flash this efs file and your problem will be solved
Click to expand...
Click to collapse
password please

saifisolutions said:
password please
Click to expand...
Click to collapse
password

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?