the solution of this error is simple.
just install proper qualcomm drivers from latest qpst setup . cause it includes the drivers too.
now just short the name of firmware folder to short form.
now open qpst or qfil, select firmware folder and select
rawprog_emmc_ufs_firehose_Sdm660_ddr.elf
then rawprogram unspare no nfc no fsg.xml '
then patch0. xml file
after that this is the main thing.
press vol + and vol- buttons together and put it into edl mode
and now connect it to the pc with cable . don't do anything till qpst or qfil not recognize it byself.
it took 30 sec to recogniz for my time.
it will take more for you may be. now download button will become available .
just click on it and now flashing will start without any error .
i was getting this error cause i was putting the device edl mode and connecting it to pc before opening of qfil or qpst.
you had to connect it after opening the qfil or qpst then you will not get any shara errror.
and have to wait at least 30 sec don't do anything till then . and after that windows will sound of connecting and that's it.
start flashing without shara error.
another solution:-
Copy firmware folder (imges) into
cdrive/programmer files/qualcomm/QPST/bin
2- Than open QFIl Select Programme Files .mbn
then both .xml Files From Cdrive where U copy
3- Now Close QFIL
4- Now Connect Handset Into Quacomm Mode (hs-usb , edl , download etc )
5- Open QFIL Again
Already Post Selected
6- Now Press Download
SUCCESS
latest qpst download from this site:-https://androidmtk.com/download-qpst-flash-tool
also try this in offline mode like remove all internet connection or wifi disable or enable airplane mode on your pc or lapto
Can post a link of QPST that you used
DJ AJB said:
Can post a link of QPST that you used
Click to expand...
Click to collapse
still getting shara error which version of winodws you using
if using windows 10 disable driver signature enforcement first then install qualcomm drivers perfectly included in qpst
after that open qfil or qpst now select all files and after that boot device in edl mode and connect it now to the pc rember dont connect with pc before qfill or qpst open now with usb cable wait for atleast 40 sec if it get recognize . download button will become available ,just click on it and start flashing
Thanks a lot it has successfully finished
When I do this I always receive:
2021-07-13 14:27:51.932 Download Fail:FireHose Fail:FHLoader Fail: process fail
Can someone give me any advice?
I also included my log.file
I waited for long, i had to selec the port as it says
im lost
Related
On russian forum's 4pda Mirial flashed his Dexp w5 with help qfil on android.
Don't working 2g/3g service.
Dexp firmware with windows and android firmware
instruction for installation android on windows phone:
1 a)You should download android firmware and unzip on c:\firmware.
b) installing QPST_2.7.422.
c) should mode cabel and normal usb cabels.
d) installed qcom drivers without driver signing
shift and reset and f7
2 Run C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe
Select Programmer Browse choose prog_emmc_firehose_8x10.mbn and Load XML choose rawprogram_unsparse and open patch0 .
3 Removed micro sd and sim card. and connection phone to pc with mode cabel micro usb, after connecton to pc with normal usb cabel. You should see new device QDloader 9008 in device Manager.
4 In qfil press download.
5. finish and on phone.
6. Restore your imei with WriteDualIMEI(W+G_eMMC), but it don't working normal(
I can flashed this phone on Windows or android forever alone now?
All other functions of the phone works fine, besides modem.
Anyway to do this on Lumia devices like Lumia 625?
Rivo17 said:
Anyway to do this on Lumia devices like Lumia 625?
Click to expand...
Click to collapse
unsophisticated
I would like a Custom Rom for Lumia Nokia and Microssoft Lumia
and respect to this is a great work.....
power on modem(2g) on dexp w5 on android:
1. restored imei with WriteDualIMEI(W+G_eMMC)
2. Restored modem with qfil on picture.
3 power off phone and closed windows, and remove usb cabel and reboot phone and restored your imei with WriteDualIMEI(W+G_eMMC)
Hello Everyone !!
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
reserved
@vasu97
We already have a dedicated thread on the same topic.
what can i edit so it won't relock the bootloader? or does it relock it?
vasu97 said:
Hello Everyone !!
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
Click to expand...
Click to collapse
Holy crap! I literally spent the last 12 hours trying to get my phone fixed. This was the only solution. Thank you so much!!!
If anyone had problems with the MSM tool "Sahara communication failed," unplug your phone. Turn it off by holding the power button for a while. Hold the power up for 10 seconds, then keep holding the volume up and plug your phone in to the PC. The MSM tool should automatically detect and restore your phone.
vasu97 said:
reserved
Click to expand...
Click to collapse
thank you so much
I've tried all the steps on multiple ports and different computers but I got always the errno 258 while loading the cache.img. Don't know what else to do...
Hi there I am writing this guide as I have had hit and miss with windows 10 getting out of qcom 9008 mode, some times it works sometimes it don't, when windows is in normal mode you sometimes get I/O errors trying to blank flash
check list check you phone is in qcom 9008 mode if you have a blank screen go to device manager and click ports (COM & LPT)
in there you should see the 9008 mode is connected on one of the com ports if so your good to go.
1. Open a CMD prompt with admin privileges. Type in search CMD right click and select run as administrator.
in command prompt type Bcdedit.exe -set TESTSIGNING ON and hit enter, once complete restart you computer you will now be in test mode indicated in the bottom right hand corner.
2. Grab the blank flash file for N or O from here https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
some have reported that even though they were running oreo that the oreo blank flash did not work and the Nougat blank flashed worked (I also had this problem and still have).
Create two folders (I use the names blank N and blank O but you can use whatever you like) extract the files from the blankflash zips to your named folders. once extracted run the Blank-flash.bat (windows batch file)
If this works you should be back too your bootloader.
3. Grab the prep file rootjunky.com created drop box link https://www.dropbox.com/s/ca62gr9aowdndzu/FlashAll_XT1789-05.zip?dl=0
don't worry that its for the xt1789-05 it should do the same for any variant
4. Grab the firmware for your device either from https://mirrors.lolinet.com/firmware/moto/nash/official/ or https://mirrors.lolinet.com/firmware/moto/nash/official/ (2nd link is the Z2 play folder our device has not got its own folder just make sure you get the file name starting with NASH and your Variant)
5. create a folder where you desire and extract the files from the prep file and your firmware to that folder (I name them flashall N or flashall O but you can use whatever you like ) once both extracted in that folder run the preparation.bat (windows batch file) this will create a flashfile.bat (windows batch file) from the flashfile.xml document from your firmware zip you extracted in this folder.
6. click the flashfile.bat (windows batch file) sit back and relax this will take a little while hopefully It has flashed everything correctly and your phone should reboot and your phone should be back to a working state
to get back out of test mode on windows follow instruction from number 1 and change ON for OFF
Hope this worked It did for me
Thanks to all from XDA for your help and all who provided the files on the links.
I will add some pictures next time I get back to qcom 9008 which I am sure I will.
The reason driver signing verification is disabled on windows during a blankflash is so that the qualcomm drivers can be installed, the previous ones weren't signed. However, in the other xt1789-05 thread there is a link to signed drivers that are win 10 compatible, so you shouldn't need to enable test signing or disable verification at all. I haven't tested it personally, but with signed drivers it should simplify the process a little. Might be worth a look, you know the full process so you could verify it easily.
41rw4lk said:
The reason driver signing verification is disabled on windows during a blankflash is so that the qualcomm drivers can be installed, the previous ones weren't signed. However, in the other xt1789-05 thread there is a link to signed drivers that are win 10 compatible, so you shouldn't need to enable test signing or disable verification at all. I haven't tested it personally, but with signed drivers it should simplify the process a little. Might be worth a look, you know the full process so you could verify it easily.
Click to expand...
Click to collapse
Thanks for this information. I may have missed that one with the signed drivers. I'm sure I had the ones from that thread. For some reason it just would not flash on both my laptop and desktop, I've used the blank flash on both desktop without being in test mode about 4 times and then all of a sudden it would not work. I'll have a go at reinstalling the drivers before I try next time.
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
sbsoft said:
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
Click to expand...
Click to collapse
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
sarath medithi said:
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
Click to expand...
Click to collapse
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
QFIL Flashing Procedure
sbsoft said:
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
Click to expand...
Click to collapse
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
sarath medithi said:
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
Click to expand...
Click to collapse
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
can you share the qfil log or screenshot
sarath medithi said:
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
can you share the qfil log or screenshot
Click to expand...
Click to collapse
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
{
"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"
}
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
sbsoft said:
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
Click to expand...
Click to collapse
Try to update your QFIL.i think there is a new version available. update it and try again. may be it is giving an error due to the programmer file which is an elf file. earlier it is .mbn or .bin file. hope you understand.
Did you succede in using QFIL ? @sbsoft
Situation:
shows redmi logo for 10 -12 seaconds then black screen for 3-4 seaconds then redmi logo again
i cant boot into fastboot mode by holding volume down button or volume down and power button and cant boot to to recovery either.
Edit: this will work even if your phone shows black screen and dosen't seem to boot or even vibrate. Just press all three buttons(volume and power) and hold while its connected with pc, for a second it will boot to bootrom while showing nothing and keep rebooting,then you can use bypass.bat,when cmd window (of bypass.bat) shows some more text,just release all buttons and it will stop rebooting in the background, then use sp flashtool to flash firmware
Solution:
you need to have adb,fastboot drivers
Download daa and sla bypass tool from : https://romprovider.com/disable-daa-sla-authentication/
also install all of the drivers mentioned on that page
now,extract the it and run bypass.bat, it will show 'waiting for brom device in cmd window
now connect your device to yout pc and hold both volume buttons
when device reboots this time it will show black screen and cmd window will show you some text
if it says protection disabled you are good to go otherwise use tools from this guide : https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
if you still cant flash using this auth file might help (this is not mine, i downloaded it off the internet)
Useful Links In Next Post
use 7z to extract rom files
use dda file given in rom
use scatter file given in rom/images
if you see error expected 0x5f got 0xa0 (or simply 0x) try using diffrent tools i experienced the same error but somehow seemingly randomly it worked
if main.py closes after split second, try opeaning it in edit mode and run it from there using F5
here are fixes to some common errors : https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
other useful links :
https://www.reddit.com/r/Xiaomi/comments/p3bak1