Database Develop

ZTE Axon A2016 brick

Please, help! I have a total zte axon brick on my hands... Windows recognizes it only like qualcomm HS-USB QDloader 9008. I've tried Qfil programm and msm9894download tool, but have no success.
Qfil output such as:
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I'll appreciate any help in my situation!
P.S. Sorry if my english is not right, it's not my native language.
P.S.S As far, as I undestend after reading a lot of guides, I need one of files - MPRG8994.hex or MPRG8994.mbn. Can anyone know where I can get them?

saardukar said:
Please, help! I have a total zte axon brick on my hands... Windows recognizes it only like qualcomm HS-USB QDloader 9008. I've tried Qfil programm and msm9894download tool, but have no success.
Qfil output such as:
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I'll appreciate any help in my situation!
P.S. Sorry if my english is not right, it's not my native language.
P.S.S As far, as I undestend after reading a lot of guides, I need one of files - MPRG8994.hex or MPRG8994.mbn. Can anyone know where I can get them?
Click to expand...
Click to collapse
Have you tried to go into recovery mode and install any rom from there?

Crazyhat said:
Have you tried to go into recovery mode and install any rom from there?
Click to expand...
Click to collapse
Recovery is not available. Nether fastboot or adb.

[ Software to install Virtual Gyroscope sensor in a easy way]

Hi!
I create this litle software to install Virtual Gyroscope sensor in a easy way!
Just follow what is write in software!
I test it with TWRP and work 100% :good:
To use it just download it and extract the folder, open it and execute the shortcut, follow what is write in there!
Install_Virtual_Gyroscope_sensor.zip
https://mega.nz/#!RsZz3CyJ
Key: !gW5uVBsQDPtiRdElmkTlXHzD5Q3Xfin1RqDGCGJa0_E​
Enjoy it! :highfive:

I think in this case, it would be easier to just link the zip, so that we could just flash it with TWRP. I'm guessing you got it from sokobans Blog?

Vinnipinni said:
I think in this case, it would be easier to just link the zip, so that we could just flash it with TWRP. I'm guessing you got it from sokobans Blog?
Click to expand...
Click to collapse
This?
No, i create this one.
.

It works in 7.1?
Enviado desde mi ALE-L21 mediante Tapatalk

peligropowers said:
It works in 7.1?
Enviado desde mi ALE-L21 mediante Tapatalk
Click to expand...
Click to collapse
7.1 gyroscope is enabled afaik

Ok.thnx
Enviado desde mi ALE-L21 mediante Tapatalk

Getting this.
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.

wackyleaks said:
Getting this.
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
Click to expand...
Click to collapse
Phone is not recognised by adb. Try enabling USB-Debugging in Developer settings.

Now when i try again im getting this.
- exec '/system/bin/sh' failed: No such file or directory (2) -
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.4 MB/s (806 bytes in 0.002s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.

wackyleaks said:
Now when i try again im getting this.
- exec '/system/bin/sh' failed: No such file or directory (2) -
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.4 MB/s (806 bytes in 0.002s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
Click to expand...
Click to collapse
Unlcok phone, there should be a USB-Debugging Pop-up. You need to allow the conection from your computer. And from what I see, you need root acces. No root = No Gyroscope. There is another way, but you need TWRP recovery. If you have TWRP, you could try rebooting to it and then go to mount and check system. Then try to run the programm again.

Vinnipinni said:
Phone is not recognised by adb. Try enabling USB-Debugging in Developer settings.
Click to expand...
Click to collapse
Its enabled the device is running twrp and is rooted
---------- Post added at 07:31 PM ---------- Previous post was at 07:29 PM ----------
Vinnipinni said:
Unlcok phone, there should be a USB-Debugging Pop-up. You need to allow the conection from your computer. And from what I see, you need root acces. No root = No Gyroscope. There is another way, but you need TWRP recovery. If you have TWRP, you could try rebooting to it and then go to mount and check system. Then try to run the programm again.
Click to expand...
Click to collapse
Its rooted USB debugg is enabled so i should just load twrp and plug usb in then run the software? Thats what I have done.

wackyleaks said:
Its enabled the device is running twrp and is rooted
---------- Post added at 07:31 PM ---------- Previous post was at 07:29 PM ----------
Its rooted USB debugg is enabled so i should just load twrp and plug usb in then run the software? Thats what I have done.
Click to expand...
Click to collapse
well, acually you should run it from the system. But if that doesn't work, you could try to go to twrp, mount system and then run the program.

Vinnipinni said:
well, acually you should run it from the system. But if that doesn't work, you could try to go to twrp, mount system and then run the program.
Click to expand...
Click to collapse
Tried both still getting
mount: Operation not permitted
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions/android.hardware.sensor.gyroscope.xml': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.2 MB/s (806 bytes in 0.004s)
chmod: /system/etc/permissions/android.hardware.sensor.gyroscope.xml: No such file or directory
umount: not root
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
You dont have it as a .zip file so we can flash it?

wackyleaks said:
Tried both still getting
mount: Operation not permitted
adb: error: failed to copy 'android.hardware.sensor.gyroscope.xml' to '/system/etc/permissions/android.hardware.sensor.gyroscope.xml': remote Permission denied
android.hardware.sensor.gyroscope.xml: 0 files pushed. 0.2 MB/s (806 bytes in 0.004s)
chmod: /system/etc/permissions/android.hardware.sensor.gyroscope.xml: No such file or directory
umount: not root
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
You dont have it as a .zip file so we can flash it?
Click to expand...
Click to collapse
https://yadi.sk/d/XjR7KlYPtSf4G Flash this zip. It's from sokoban, not from OP. It always worked fine for me.

Will this work for the p9 lite?

Vinnipinni said:
https://yadi.sk/d/XjR7KlYPtSf4G Flash this zip. It's from sokoban, not from OP. It always worked fine for me.
Click to expand...
Click to collapse
thank you !

how to install it?

why the sensor is not calibrated?

hi um installed it but my apps dont detect the gyro i got this output btw while installing
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
mount: '/dev/block/mmcblk0p38'->'/system': Device or resource busy
android.hardware.sensor.gyroscope.xml: 1 file pushed. 0.0 MB/s (806 bytes in 0.019s)
chmod: /system/etc/permissions/android.hardware.sensor.gyroscope.xml: Not a directory
umount: /system: Invalid argument
Done!!!!
Reboot the phone then test Virtual Gyroscope sensor with cpu Z
in sensors options. You can download from Google Play Store.
Press Enter to reboot the phone now.
In aida64 the gyro entry is blank
{
"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"
}
and btw i also tried an xposed based virtual sensor but that doesnt work with the app i want to use it with pls help

Bricked Samsung S8 (TMO version) showing Qualcomm HS-USB QDloader 9008

Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Thanks a lot in advance

taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Thanks a lot in advance
Click to expand...
Click to collapse
This thread may be old, but for now, the only option you have is getting a replacement. I had that qualcomm HS-USB composite identity on my hard bricked lg g stylo and i couldn't do anything about it but get it replaced.

taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Thanks a lot in advance
Click to expand...
Click to collapse
If this is still an issue you face PM me and i will help you unbrick the device!

TimelessPWN said:
If this is still an issue you face PM me and i will help you unbrick the device!
Click to expand...
Click to collapse
I'm ready to help for unbrick my S8

I have the same exact hard brick on my S8, did you guys ever figure out a solution?

TimelessPWN said:
If this is still an issue you face PM me and i will help you unbrick the device!
Click to expand...
Click to collapse
I have the same error, could you solve it?

did you get it fixed? I think TimelessPWN would have used EDL mode.

mweinbach said:
did you get it fixed? I think TimelessPWN would have used EDL mode.
Click to expand...
Click to collapse
I have not fixed it ye, i need help.

FUBUKY said:
I have not fixed it ye, i need help.
Click to expand...
Click to collapse
ok. from what i am reading, you have a hard brick. that QDloader 9008 is EDL mode. the EDL files that we got from QUALCOMM must be sent to you, and you have to run a QUALCOMM software and apply those files through EDL. I currently have the files but I am not 100% sure how to use them. I recommend contacting https://www.facebook.com/GSMCHEN.up for help. he 100% can.

mweinbach said:
did you get it fixed? I think TimelessPWN would have used EDL mode.
Click to expand...
Click to collapse
FUBUKY said:
I have not fixed it ye, i need help.
Click to expand...
Click to collapse
mweinbach said:
ok. from what i am reading, you have a hard brick. that QDloader 9008 is EDL mode. the EDL files that we got from QUALCOMM must be sent to you, and you have to run a QUALCOMM software and apply those files through EDL. I currently have the files but I am not 100% sure how to use them. I recommend contacting for help. he 100% can.
Click to expand...
Click to collapse
thx man, i am retry repair.

mweinbach said:
ok. from what i am reading, you have a hard brick. that QDloader 9008 is EDL mode. the EDL files that we got from QUALCOMM must be sent to you, and you have to run a QUALCOMM software and apply those files through EDL. I currently have the files but I am not 100% sure how to use them. I recommend contacting https://www.facebook.com/GSMCHEN.up for help. he 100% can.
Click to expand...
Click to collapse
Do you mind sharing the files sir? I have this issue and need the files please
Regards,
.:112:.
Sent from my SM-G928T using Tapatalk

stuntman112 said:
Do you mind sharing the files sir? I have this issue and need the files please
Regards,
.:112:.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
I have been told not to. Sorry.

I hope soon a solution comes out, while I continue with my brick.
GSMCHEN apparently can repair them, but you have not answered my messages.

I found the files needed. Will upload a link tonight
Sent from my SM-G928T using Tapatalk

stuntman112 said:
I found the files needed. Will upload a link tonight
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
thank you very much, I hope the link to try to unbrick my s8 +

Some of the files are in plain sight at AFH. The developer has all the required QCOM tools at the link.
Prog_UFS_Firehose_8998_ddr.elf file:
https://androidfilehost.com/?fid=961840155545585810
Notice it is UFS storage, not EMMC so make sure you have the latest QPST software. Thanks to the developer (hazmat) for the prog file but i believe we will need others also such as .XML's
Messed around with it for a little but didnt figure it out. Hopefully this is a start to dead boot repair for the SM-G955..The Dream2 awakes..
Sent from my SM-G928T using Tapatalk

stuntman112 said:
Some of the files are in plain sight at AFH. The developer has all the required QCOM tools at the link.
Prog_UFS_Firehose_8998_ddr.elf file:
https://androidfilehost.com/?fid=961840155545585810
Notice it is UFS storage, not EMMC so make sure you have the latest QPST software. Thanks to the developer (hazmat) for the prog file but i believe we will need others also such as .XML's
Messed around with it for a little but didnt figure it out. Hopefully this is a start to dead boot repair for the SM-G955..The Dream2 awakes..
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
without the xml files it does not help us.
I had already tried it, the xml files that it has shared (hazmat) are from xiaomi.

mweinbach said:
I have been told not to. Sorry.
Click to expand...
Click to collapse
That's the right thing to do,
Anyway, we have to protect these documents, right

Could not get the device un bricked. Thanks GSM CHEN for help. Possible CPU hardware problem. Seems stuck in EDL
LOG
Programmer Path:C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf
Image Search Path: C:\Users\User1\Desktop\nhlos\common\tools\emergency_download
RAWPROGRAM file path: C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\rawprogram0.xml
PATCH file path:C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\patch0.xml
Start Download
Program Path:C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf
***** Working Folder:C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf
11:44:18: Requested ID 13, file: "C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\prog_ufs_firehose_8998_ddr.elf"
11:44:18: 599432 bytes transferred in 0.172000 seconds (3.3236MBps)
11:44:18: File transferred successfully
11:44:18: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:UFS
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
11:44:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM11 --sendxml=rawprogram0.xml --search_path=C:\Users\User1\Desktop\nhlos\common\tools\emergency_download --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
************************************************
11:44:22: INFO: Current working dir (cwd): C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11\
11:44:22: INFO: Showing network mappings to allow debugging
11:44:22: INFO:
11:44:22: INFO: Trying to store 'rawprogram0.xml' in string table
11:44:22: INFO: Looking for file 'rawprogram0.xml'
11:44:22: INFO: User wants to talk to port '\\.\COM11'
11:44:22: INFO: Took 0.00000000 seconds to open port
11:44:22: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
11:44:22: INFO: If you don't want this, use --dontsorttags
11:44:22: INFO: Looking for file 'gpt_main0.bin'
11:44:22: INFO: Looking for file 'gpt_backup0.bin'
11:44:22: INFO:
Total to be tansferd with <program> or <read> is 44.00 KB
11:44:22: INFO: Sending <configure>
11:44:22: INFO: TARGET SAID: 'Binary build date: Jun 1 2017 @ 14:29:30'
11:44:22: INFO: TARGET SAID: 'Chip serial num: 4294967295 (0xffffffff)'
11:44:22: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
11:44:22: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
11:44:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
11:44:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
11:44:22: INFO: In handleProgram('gpt_main0.bin')
11:44:22: INFO: Looking for file 'gpt_main0.bin'
11:44:22: INFO: =======================================================
11:44:22: INFO: {<program> FILE: 'C:\Users\User1\Desktop\nhlos\common\tools\emergency_download\gpt_main0.bin'}
11:44:22: INFO: {<program> (24.00 KB) 6 sectors needed at location 0 on LUN 0}
11:44:22: INFO: =======================================================
11:44:22: INFO: TARGET SAID: 'ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0'
11:44:22: INFO: TARGET SAID: 'ERROR: ufs_open_error_code 0 :: 0x27c'
11:44:22: INFO: TARGET SAID: 'ERROR: last ufs_open_error_code 16 :: 0x27c'
11:44:22: INFO: TARGET SAID: 'ERROR: Failed to open the device 3 slot 0 partition 0'
11:44:22: INFO: TARGET SAID: 'INFO: Device type 3, slot 0, partition 0, error 0'
11:44:22: INFO: TARGET SAID: 'WARN: Get Info failed to open 3 slot 0, partition 0, error 0'
11:44:22: INFO: TARGET SAID: 'storage_device_get_num_partition_sectors FAILED!'
11:44:22: INFO: TARGET SAID: 'parseSectorValue could not handle start_sector value'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
11:44:22: {ERROR: program FAILED - Please see log}
Writing log to 'C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11\port_trace.txt', might take a minute
Log is 'C:\Users\User1\AppData\Roaming\Qualcomm\QFIL\COMPORT_11\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
Sent from my SM-G928T using Tapatalk

a me has not helped me yet.

Redmi Note9 Codename Merlin -- Cant find the Testpoints for EDL - see Picture

Hello, i need some Help for the EDL Flash on Redmi Note9 Codename Merlin.
Fastboot and Recovery does not work. Reboot after Redmi Sign.
Bootloader is open, Backcover is open. What must i do now?
Please help me for finding Testpoint.
{
"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"
}

First, close your device and keep it untouched.
Next, follow this guide:
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com

VD171 said:
First, close your device and keep it untouched.
Next, follow this guide:
Click to expand...
Click to collapse
Thanks but i have a mistake at the end from the bat.
[2021-08-05 06:32:01.748392] Waiting for device
[2021-08-05 06:32:19.245436] Found port = COM9
[2021-08-05 06:32:19.429782] Device hw code: 0x707
[2021-08-05 06:32:19.429782] Device hw sub code: 0x8a00
[2021-08-05 06:32:19.429782] Device hw version: 0xca00
[2021-08-05 06:32:19.429782] Device sw version: 0x0
[2021-08-05 06:32:19.429782] Device secure boot: True
[2021-08-05 06:32:19.438464] Device serial link authorization: True
[2021-08-05 06:32:19.438464] Device download agent authorization: True
[2021-08-05 06:32:19.438464] Disabling watchdog timer
[2021-08-05 06:32:19.438464] Disabling protection
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 36, in exploit
udev._ctx.managed_claim_interface = lambda *args, **kwargs: None
AttributeError: 'NoneType' object has no attribute '_ctx'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 213, in <module>
main()
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 58, in main
result = exploit(device, config.watchdog_address, config.payload_address, config.var_0, config.var_1, payload)
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 38, in exploit
raise RuntimeError("libusb is not installed for port {}".format(device.dev.port)) from e
RuntimeError: libusb is not installed for port COM9
Drücken Sie eine beliebige Taste . . .

Frettchen-Kalle said:
Thanks but i have a mistake at the end from the bat.
[2021-08-05 06:32:01.748392] Waiting for device
[2021-08-05 06:32:19.245436] Found port = COM9
[2021-08-05 06:32:19.429782] Device hw code: 0x707
[2021-08-05 06:32:19.429782] Device hw sub code: 0x8a00
[2021-08-05 06:32:19.429782] Device hw version: 0xca00
[2021-08-05 06:32:19.429782] Device sw version: 0x0
[2021-08-05 06:32:19.429782] Device secure boot: True
[2021-08-05 06:32:19.438464] Device serial link authorization: True
[2021-08-05 06:32:19.438464] Device download agent authorization: True
[2021-08-05 06:32:19.438464] Disabling watchdog timer
[2021-08-05 06:32:19.438464] Disabling protection
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 36, in exploit
udev._ctx.managed_claim_interface = lambda *args, **kwargs: None
AttributeError: 'NoneType' object has no attribute '_ctx'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 213, in <module>
main()
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 58, in main
result = exploit(device, config.watchdog_address, config.payload_address, config.var_0, config.var_1, payload)
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 38, in exploit
raise RuntimeError("libusb is not installed for port {}".format(device.dev.port)) from e
RuntimeError: libusb is not installed for port COM9
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
Did you install the python module pyusb?
Did you try to run as administrator?

thank you VD171
it works perfektly now.
i trie it with 12.04 global, then auto update to 12.08 und at last auto update to 12.01 (android11)
bootloader is 2nd time open now .-)
it try 3.41 recovery with admin fastboot command and all seen fine - but not so is.
Cant boot in twrp - there is no twrp? and now?
//edit
i think this was it (no twrp) that me brick the phone the first time flash custom rom ;-)

Frettchen-Kalle said:
thank you VD171
it works perfektly now.
i trie it with 12.04 global, then auto update to 12.08 und at last auto update to 12.01 (android11)
bootloader is 2nd time open now .-)
it try 3.41 recovery with admin fastboot command and all seen fine - but not so is.
Cant boot in twrp - there is no twrp? and now?
//edit
i think this was it (no twrp) that me brick the phone the first time flash custom rom ;-)
Click to expand...
Click to collapse
Good work, my friend.
I suggest you to try all recovery project you can, and then you can choose one:
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G Warnings: - This is not a development thread. This is a help thread. - I didn't build any of them. Use at your own risk. - I don't have the source code for any of them. Use at your own...
forum.xda-developers.com

Traceback (most recent call last):
File "main.py", line 3, in <module>
from src.exploit import exploit
ImportError: No module named src.exploit
Для продолжения нажмите любую клавишу . . .

Question Stuck on Bootloader after Miui13 Update (India)

Stuck on Bootloader after Miui13 Update (India)
Stock Rom-12.5+Magisk 24.3, After update is received installed & flashed magisk on other slot to restart & stuck on MI Logo
Stock miui13 Recovery noticed, Twrp can be loaded but touch is not working
Any suggestions

djkrish5610 said:
Stuck on Bootloader after Miui13 Update (India)
Stock Rom-12.5+Magisk 24.3, After update is received installed & flashed magisk on other slot to restart & stuck on MI Logo
Stock miui13 Recovery noticed, Twrp can be loaded but touch is not working
Any suggestions
Click to expand...
Click to collapse
You have to update it from fastboot as you are already rooted.
Boot it to fastboot and flash the fastboot ROM. I will go with MMX ROM as it's already rooted and debloated further from xiaomi.eu. Have been using for a day and works very well!
XIAOMI 11T PRO | UPDATES
#MIUI #MMX #MIUI #S #Vili #ROM MiuiMix V13.0.2.0 [MIUI 13] | Android 12 Updated:18/03/2022 ▪️Download: AFH | SF ▪️Flashing instructions By MMX Team Follow @Xiomi11TProUpdates Join @mi_11t
t.me

djkrish5610 said:
Stuck on Bootloader after Miui13 Update (India)
Stock Rom-12.5+Magisk 24.3, After update is received installed & flashed magisk on other slot to restart & stuck on MI Logo
Stock miui13 Recovery noticed, Twrp can be loaded but touch is not working
Any suggestions
Click to expand...
Click to collapse
Start to restore the phone to its original configuration:https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Then install a custom rom .

It Shows me as flashing done on both roms A11 & A12
{
"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"
}
MiFlash Logs as below:
[23:05:05 4b9da9b0]:MiFlash 2021.2.26.0
[23:05:05 4b9da9b0]:vboytest index:1
[23:05:05 4b9da9b0]:Thread id:13 Thread name:
[23:05:05 4b9da9b0]:image path:\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global
[23:05:05 4b9da9b0]:env android path:"C:\MiFlash\Source\ThirdParty\Google\Android"
[23:05:05 4b9da9b0]:script :\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global\flash_all.bat
[23:05:05 4b9da9b0]hysical Memory Usage:3936256 Byte
[23:05:05 4b9da9b0]:start process id 6236 name cmd
[23:05:05 4b9da9b0]:begin FlashDone
[23:05:05 4b9da9b0]:errMsg is null
[23:05:05 4b9da9b0]:no need checkPoint
[23:05:05 4b9da9b0]:flash done
[23:05:05 4b9da9b0]rocess exit.
[23:05:10 4b9da9b0]:flashSuccess True
[23:05:10 4b9da9b0]:isFactory False CheckCPUID False
[23:05:10 4b9da9b0]:before:flashSuccess is True set IsUpdate:True set IsDone True
[23:05:10 4b9da9b0]:after:flashSuccess is True set IsUpdate:false set IsDone true
Manual Flash is working fine, but after reboot stuck on fastboot only

djkrish5610 said:
It Shows me as flashing done on both roms A11 & A12
View attachment 5573997
MiFlash Logs as below:
[23:05:05 4b9da9b0]:MiFlash 2021.2.26.0
[23:05:05 4b9da9b0]:vboytest index:1
[23:05:05 4b9da9b0]:Thread id:13 Thread name:
[23:05:05 4b9da9b0]:image path:\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global
[23:05:05 4b9da9b0]:env android path:"C:\MiFlash\Source\ThirdParty\Google\Android"
[23:05:05 4b9da9b0]:script :\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global\flash_all.bat
[23:05:05 4b9da9b0]hysical Memory Usage:3936256 Byte
[23:05:05 4b9da9b0]:start process id 6236 name cmd
[23:05:05 4b9da9b0]:begin FlashDone
[23:05:05 4b9da9b0]:errMsg is null
[23:05:05 4b9da9b0]:no need checkPoint
[23:05:05 4b9da9b0]:flash done
[23:05:05 4b9da9b0]rocess exit.
[23:05:10 4b9da9b0]:flashSuccess True
[23:05:10 4b9da9b0]:isFactory False CheckCPUID False
[23:05:10 4b9da9b0]:before:flashSuccess is True set IsUpdate:True set IsDone True
[23:05:10 4b9da9b0]:after:flashSuccess is True set IsUpdate:false set IsDone true
Manual Flash is working fine, but after reboot stuck on fastboot only
Click to expand...
Click to collapse
I see on your post "flash_all.bat" but the flash must end with an error since you don't re-lock the bootloader.
post the Miflash log.
try this rom (fastboot)https://xiaomifirmwareupdater.com/miui/vili/stable/V12.5.2.0.RKDINXM/

Device is still unlocked
Tried V12.5.2.0.RKDINXM (India) & V13.0.2.0.SKDMIXM (Global) Fastboot Rom
For Global V13 Rom everything completed but phone still on fastboot mode
Let me try again for v12 india fastboot rom

djkrish5610 said:
Device is still unlocked
View attachment 5574073
Tried V12.5.2.0.RKDINXM (India) & V13.0.2.0.SKDMIXM (Global) Fastboot Rom
For Global V13 Rom everything completed but phone still on fastboot mode
Let me try again for v12 india fastboot rom
Click to expand...
Click to collapse
Again post your logs for each flash

After V12 rom

Finally MMX OS flashed on fastboot rom & Phone started breathing again
@NOSS8 @RainGater For Helping on this.
I guess flash file need to be followed as MMX rom

djkrish5610 said:
Finally MMX OS flashed on fastboot rom & Phone started breathing again
@NOSS8 @RainGater For Helping on this.
I guess flash file need to be followed as MMX rom
Click to expand...
Click to collapse
That is what I was telling you that flashing MMX is as easy as saying 1-2-3. lol
adb reboot bootloader
windows_fastboot_first_install_with_data_format.bat
Done!

Which recovery will go with mmx rom