Possible way to unbrick the zenfone 3 deluxe or any Qualcomm device all is needed is the a working device of the same model if someone with root can run this command in the terminal emulator ((dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960)) to get the files nneeded to boot into bootloader i will then burn that img to a sdcard boot into bootloader and flash with asus tool please if any one can help it will only take a second thanks i appreciate
This is the link i am relying on http://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html?m=1
dcraffam said:
Possible way to unbrick the zenfone 3 deluxe or any Qualcomm device all is needed is the a working device of the same model if someone with root can run this command in the terminal emulator ((dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960)) to get the files nneeded to boot into bootloader i will then burn that img to a sdcard boot into bootloader and flash with asus tool please if any one can help it will only take a second thanks i appreciate
Click to expand...
Click to collapse
Hey, I checked it out and have followed the instructions. Didn't know this was a thing and thought it would be good to have just in case a flash goes wrong.
Before you download, I'd like for you to confirm that my model was what you asked for: the ZS570KL with a 2.15GHz Snapdragon 820 CPU. If it's correct with you, then this Loader.img should be compatible with your device.
I've removed the old file and am working on a new one.
Good luck and godspeed. Please post an update, and if it works out for you, please document the steps you took to solve the issue!
Zenfone 3
Well i cant say thank you enough for at least trying the 2.15 cpu is the correct device and i still cant thank you enough i appreciate the time and effort
dcraffam said:
Well i cant say thank you enough for at least trying the 2.15 cpu is the correct device the only problem is when i burn the image to the sdcars there is a couple files that dont belong maby if you can move a couple files from your device then try agin the sdcard with files burned to it consit of [Please remove this part] so i believe it will work maby just gotta get some of the files out of there thabks in advance i really do appreciate the effortt
Click to expand...
Click to collapse
Hey! I'm currently in the process of trying to get this sorted out. I don't want to get to into the explanation of it, but would you kindly edit your post to remove that file list. There's nothing personal in it, but I'd rather the contents of my SD card be kept private.
In short, the command you gave me copied the first 165mb of my SD card and created an img file from it. The reason being, mmcblk0 is the SD card. On phones with EMMC, this would normally be the internal memory and mmcblk1 would be the SD card. However, because the Zenfone uses UFS 2.0, it's in a different place and thus acts differently. I'm trying to figure out what the right command is to create what needs to be created. Please give me a moment, and please edit your post and delete the file you downloaded!
dcraffam said:
Possible way to unbrick the zenfone 3 deluxe or any Qualcomm device all is needed is the a working device of the same model if someone with root can run this command in the terminal emulator ((dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960)) to get the files nneeded to boot into bootloader i will then burn that img to a sdcard boot into bootloader and flash with asus tool please if any one can help it will only take a second thanks i appreciate
Click to expand...
Click to collapse
So, I've got bad news, and hopefully good news.
First the bad news. From the research I have done, I believe the method that you've presented here will not work. This is because around the time when the Snapdragon 820 came out, many companies opted to use UFS over EMMC, as it's essentially the next step in flash storage evolution. EMMC and MicroSD cards were treated essentially the same way, and thus some phones were able to "boot" off the SD card using the first 165mb of the bootloader. Since UFS isn't treated the same way and has to be read differently, the ability to boot off the SD card became lost with the change of storage.
Now for the hopefully good news. I looked into your xda post history to see the other methods you tried and noticed you posted in a thread about QFIL looking for the proper files. After some investigation into the process, I've stumbled upon what I think may be what you need. I'm not entirely clear about the process, but I think I have a rough estimate of what needs to be done. I'm not home right now, so I can't confirm some of the steps, but hopefully I can guide you through it. If any confusion occurs, I'll hopefully be able to clarify it while I'm home. Please see my next comment for the process.
qfil
asianflipboy said:
So, I've got bad news, and hopefully good news.
First the bad news. From the research I have done, I believe the method that you've presented here will not work. This is because around the time when the Snapdragon 820 came out, many companies opted to use UFS over EMMC, as it's essentially the next step in flash storage evolution. EMMC and MicroSD cards were treated essentially the same way, and thus some phones were able to "boot" off the SD card using the first 165mb of the bootloader. Since UFS isn't treated the same way and has to be read differently, the ability to boot off the SD card became lost with the change of storage.
Now for the hopefully good news. I looked into your xda post history to see the other methods you tried and noticed you posted in a thread about QFIL looking for the proper files. After some investigation into the process, I've stumbled upon what I think may be what you need. I'm not entirely clear about the process, but I think I have a rough estimate of what needs to be done. I'm not home right now, so I can't confirm some of the steps, but hopefully I can guide you through it. If any confusion occurs, I'll hopefully be able to clarify it while I'm home. Please see my next comment for the process.
Click to expand...
Click to collapse
thanks for the research any thing you can do to help is greatly appreciated
A (Rough!!!) Guide to (Hopefully) Unbricking the ZS570KL from 9008 issue
So let's get started, @dcraffam.
As a *DISCLAIMER* I am not responsible for any damage this may cause your phone (Although how much more damage can really be done when it's bricked?)
This is all based on theory, as my device isn't bricked and I don't intend on attempting to fix a working device. That being said, this is good knowledge to have for the future, so I'm making this to hopefully help those who might need it in the future.
The prerequisites for this, to the best of my knowledge, are as follows:
A ZS570KL that, when plugged into a computer, produces a device in your device manager that has the number 9008 in it
A computer running Windows
9008, to my knowledge, is like Snow White waiting for Prince Charming's lips. It's essentially a brick, but with the right tools, you can kickstart it to a state where it can make a full recovery. I stumbled upon some tools that I think can get the job done, but it will be up to you to test them out. I wish you the best of luck.
The first one you should grab is:
The Qualcomm USB Drivers
https://androiddatahost.com/nbyn6
Pretty straightforward. You'll need these so your computer can properly interact with your device.
The second thing to grab is:
The Qualcomm Flash Image Loader (QFIL) Tool
https://androiddatahost.com/flkn2
This is the program that should be able to bring your phone back, your Prince Charming, if you will. It's not an installer, so just extract the files to a known folder and keep it open. You'll need to access it soon.
I obtained both of these files from this website's guide:
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
In fact, you'll be pretty much following that guide, but with a couple of changes. But before that, you'll need a couple more things.
Stock ZS570KL FRP
https://drive.google.com/open?id=1s4nas0iP_rLcnLLwh348krvLUNP57YF2
And you may or may not need this one but
ZS570KL 8996 elf file
https://drive.google.com/file/d/1GgIDDYofsyn_F__6YveofDgYsXaYFvZr/view?usp=drivesdk
These I also stumbled upon. They're the files necessary to get the QFIL tool to work, and are specifically for your phone. The first one is especially important, as that's the stock firmware that will be loaded onto your phone. Extract that into a separate folder that's easy to locate. The second one is specific to your phone, but there's already one in the FRP zip. Only use it if the one in the FRP zip doesn't work. They seem to be correct for the most part, but I found them in a weird website, so be warned. That website was:
https://addrom.com/rom-stock-asus-zenfone-3-deluxe-z016d-zs570kl/
So to recap:
Download the files
Install the drivers
Extract the files into easy to find places.
https://www.youtube.com/watch?v=JxlMntGp6vs
Now, what follows will be the edited edition of the video above. I believe it needs to be adjusted because it's, by default, in EMMC mode and not UFS mode. I'm home now, so I'm making the proper updates. Hopefully they work for you.
The instructions are as follows:
1. Open up QFIL.exe
2. On the top left, there's a button called configuration. Hit that and then Firehose Configuration.
3. A popup should appear. The important thing to change is a drop down menu that says "EMMC". Change it to "UFS" instead. Hit OK to go back to QFIL.
4. Plug your phone in, and click SelectPort on the top right of QFIL. Your phone should be there. Select it and hit OK.
5. In QFIL, hit Browse, navigate to the extracted FRP zip and select "prog_ufs_firehose_8996_ddr.elf" It should automatically select the folder as the build folder.
6. Next, hit "Load XML...", and "rawprogram0.xml" should pop up. Select that one, and then "patch0.xml"
7. If all goes well, you'll be able to hit "Download" below "Load XML." If you can't, try going through the steps with the 8996 ZS570KL elf file.
Hopefully nothing fails and your phone reboots into stock firmware. From there, I recommend updating to the latest firmware.
If this method fails you, there are some other Qualcomm image flashers that are available to try. Hopefully we can find one that works for you.
Good luck! Please let me know if you encounter any issues or if you're successful!
qfil
so i thank you agin for your research sadly the files did not work for me i have tried maby 5 or 6 qfil roms and my phone wont accept the digital signature its saying binary build date jun 17 2016 but there is no firmware that goes back that far i guess theres no hope for me unless you can try to make a back up with qpst software download and i flash or something i really dont see a save anymore but if you do find somehing else please let mee know thanks i really appreiate it
dcraffam said:
so i thank you agin for your research sadly the files did not work for me i have tried maby 5 or 6 qfil roms and my phone wont accept the digital signature its saying binary build date jun 17 2016 but there is no firmware that goes back that far i guess theres no hope for me unless you can try to make a back up with qpst software download and i flash or something i really dont see a save anymore but if you do find somehing else please let mee know thanks i really appreiate it
Click to expand...
Click to collapse
Darn, was really hoping it would work. Would you mind running it again, and then copying and saving the output text, and then post it here? I'd like to use it to research it further.
Also, what do you mean by make a backup? Do you have more information regarding this process?
qfil port_trace.txt
16:01:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Users\anthony\Downloads\Qualcomm_Flash_Image_Loader_v2.0.0.5\fh_loader.exe --port=\\.\COM4 --sendxml=rawprogram0.xml,rawprogram1.xml,rawprogram2.xml,rawprogram3.xml,rawprogram4.xml,rawprogram5.xml --search_path=C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=UFS
************************************************
16:01:22: DEBUG: Binary build date: Oct 31 2016 @ 22:51:02
16:01:22: DEBUG: Build Version: 16.10.31.22.51.02
16:01:22: INFO: Current working dir (cwd): C:\Users\anthony\AppData\Roaming\Qualcomm\QFIL\
16:01:22: INFO: Showing network mappings to allow debugging
16:01:22: DEBUG: New connections will be remembered.
16:01:22: DEBUG:
16:01:22: DEBUG: There are no entries in the list.
16:01:22: DEBUG:
16:01:22: INFO:
16:01:22: INFO: Trying to store 'rawprogram0.xml' in string table
16:01:22: DEBUG: ==================================================================================
16:01:22: DEBUG: ==================================================================================
16:01:22: INFO: Looking for file 'rawprogram0.xml'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\rawprogram0.xml')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\rawprogram0.xml') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\rawprogram0.xml' (5303 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\rawprogram0.xml') with AccessMode='r'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: ==================================================================================
16:01:22: DEBUG: ==================================================================================
16:01:22: INFO: Looking for file 'persist.img'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\persist.img')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\persist.img') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\persist.img' (4804840 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\persist.img') with AccessMode='rb'
16:01:22: INFO: Reading through sparse file 'persist.img' and pulling out relevant header information...
16:01:22: INFO: File persist.img is a sparse file, being split up into 1 separate XML tags
16:01:22: DEBUG:
16:01:22: INFO: Looking for file 'factory.img'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\factory.img')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\factory.img') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\factory.img' (33554432 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\factory.img') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: INFO: cache.img is a sparse image
16:01:22: DEBUG: ==================================================================================
16:01:22: DEBUG: ==================================================================================
16:01:22: INFO: Looking for file 'cache.img'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img' (6398160 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img') with AccessMode='rb'
16:01:22: INFO: cache.img is a sparse image
16:01:22: DEBUG: ==================================================================================
16:01:22: DEBUG: ==================================================================================
16:01:22: INFO: Looking for file 'cache.img'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img' (6398160 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img') with AccessMode='rb'
16:01:22: INFO: cache.img is a sparse image
16:01:22: DEBUG: ==================================================================================
16:01:22: DEBUG: ==================================================================================
16:01:22: INFO: Looking for file 'cache.img'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img' (6398160 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\cache.img') with AccessMode='rb'
16:01:22: DEBUG: ==================================================================================
16:01:22: DEBUG: ==================================================================================
16:01:22: INFO: Looking for file 'devcfg.mbn'
16:01:22: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\devcfg.mbn')
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\devcfg.mbn') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
16:01:22: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\devcfg.mbn' (40024 bytes)
16:01:22: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\devcfg.mbn') with AccessMode='rb'
16:01:22: DEBUG: Trying get filesize, calling fseek()
[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img' (139675944 bytes)
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: INFO: userdata.img is a sparse image
16:01:23: DEBUG: ==================================================================================
16:01:23: DEBUG: ==================================================================================
16:01:23: INFO: Looking for file 'userdata.img'
16:01:23: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img')
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: DEBUG: Trying get filesize, calling fseek()
16:01:23: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img' (139675944 bytes)
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: INFO: userdata.img is a sparse image
16:01:23: DEBUG: ==================================================================================
16:01:23: DEBUG: ==================================================================================
16:01:23: INFO: Looking for file 'userdata.img'
16:01:23: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img')
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: DEBUG: Trying get filesize, calling fseek()
16:01:23: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img' (139675944 bytes)
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: INFO: userdata.img is a sparse image
16:01:23: DEBUG: ==================================================================================
16:01:23: DEBUG: ==================================================================================
16:01:23: INFO: Looking for file 'userdata.img'
16:01:23: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img')
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: DEBUG: Trying get filesize, calling fseek()
16:01:23: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img' (139675944 bytes)
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: INFO: userdata.img is a sparse image
16:01:23: DEBUG: ==================================================================================
16:01:23: DEBUG: ==================================================================================
16:01:23: INFO: Looking for file 'userdata.img'
16:01:23: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img')
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: DEBUG: Trying get filesize, calling fseek()
16:01:23: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img' (139675944 bytes)
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: INFO: userdata.img is a sparse image
16:01:23: DEBUG: ==================================================================================
16:01:23: DEBUG: ==================================================================================
16:01:23: INFO: Looking for file 'userdata.img'
16:01:23: DEBUG: 1. Calling stat(C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img')
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: DEBUG: Trying get filesize, calling fseek()
16:01:23: DEBUG: Found 'C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img' (139675944 bytes)
16:01:23: DEBUG: 2. Calling fopen('C:\Program Files (x86)\Qualcomm\QPST\bin\[up_vnROM.net]_MR1.2_WW_ZS570KL-4.12.40.1781-rel-user-20170117-secured-ufs-releaseFRP\userdata.img') with AccessMode='rb'
16:01:23: INFO: userdata.img is a sparse image
16:01:24: DEBUG: XML FILE (111 bytes): CharsInBuffer=2861-111=2750
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Binary build date: Jun 17 2016 @ 10:09:02"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'Binary build date: Jun 17 2016 @ 10:09:02'
16:01:24: DEBUG: XML FILE (110 bytes): CharsInBuffer=2750-110=2640
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Chip serial num: 4294967295 (0xffffffff)"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'Chip serial num: 4294967295 (0xffffffff)'
16:01:24: DEBUG: XML FILE (234 bytes): CharsInBuffer=2640-234=2406
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke "/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
16:01:24: DEBUG: XML FILE (139 bytes): CharsInBuffer=2406-139=2267
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="VIP - Validated Image Programming is enabled - Validation is enabled."/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'VIP - Validated Image Programming is enabled - Validation is enabled.'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=2267-108=2159
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Image Total Size = 0xE3 (227)"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'Image Total Size = 0xE3 (227)'
16:01:24: DEBUG: XML FILE (101 bytes): CharsInBuffer=2159-101=2058
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="HeaderIs80Bytes = 0x0"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'HeaderIs80Bytes = 0x0'
16:01:24: DEBUG: XML FILE (138 bytes): CharsInBuffer=2058-138=1920
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.sw_type = 0x3 (DeviceProgrammer *insists* on this)"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.sw_type = 0x3 (DeviceProgrammer *insists* on this)'
16:01:24: DEBUG: XML FILE (101 bytes): CharsInBuffer=1920-101=1819
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.sw_version = 0x0"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.sw_version = 0x0'
16:01:24: DEBUG: XML FILE (102 bytes): CharsInBuffer=1819-102=1717
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.header_len_1 = 0x28"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.header_len_1 = 0x28'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=1717-108=1609
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.code_ptr_1 = 0xF54AC112"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.code_ptr_1 = 0xF54AC112'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=1609-108=1501
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.code_len_1 = 0x6F636E65"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.code_len_1 = 0x6F636E65'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=1501-108=1393
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.x509_chain_ptr = 0x1782EE58"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.x509_chain_ptr = 0x1782EE58'
16:01:24: DEBUG: XML FILE (107 bytes): CharsInBuffer=1393-107=1286
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.x509_chain_len = 0xA3E3F20"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.x509_chain_len = 0xA3E3F20'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=1286-108=1178
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.signature_ptr = 0x5CB92A76"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.signature_ptr = 0x5CB92A76'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=1178-108=1070
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.signature_len = 0x5455223D"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.signature_len = 0x5455223D'
16:01:24: DEBUG: XML FILE (108 bytes): CharsInBuffer=1070-108=962
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="image_info.header_ptr_1 = 0x85E14DA0"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'image_info.header_ptr_1 = 0x85E14DA0'
16:01:24: DEBUG: XML FILE (170 bytes): CharsInBuffer=962-170=792
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="AuthenticateImage() Returning FALSE, secboot_authenticate() returned 0x2 (not E_SECBOOT_SUCCESS=0x0)"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'AuthenticateImage() Returning FALSE, secboot_authenticate() returned 0x2 (not E_SECBOOT_SUCCESS=0x0)'
16:01:24: DEBUG: XML FILE (116 bytes): CharsInBuffer=792-116=676
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR 1: Line 1140: AUTHENTICATE_IMAGE_FAILURE"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'ERROR 1: Line 1140: AUTHENTICATE_IMAGE_FAILURE'
16:01:24: DEBUG: XML FILE (138 bytes): CharsInBuffer=676-138=538
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Failed to authenticate Digital Signature, resetting validation state"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'Failed to authenticate Digital Signature, resetting validation state'
16:01:24: DEBUG: XML FILE (120 bytes): CharsInBuffer=538-120=418
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR 11: Line 790: DIGITAL_SIGNATURE_DID_NOT_PASS"/>
</data>
-------------------------------------------------------------------------------------------
16:01:24: INFO: TARGET SAID: 'ERROR 11: Line 790: DIGITAL_SIGNATURE_DID_NOT_PASS'
16:01:24: DEBUG: XML FILE (79 bytes): CharsInBuffer=418-79=339
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
-------------------------------------------------------------------------------------------
16:01:24: DEBUG: Response was 'NAK'
16:01:24: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
16:01:24: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
16:01:24: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
@dcraffam, what's the version of QFIL that you're using? I don't see any mentions of some of the keywords I was expecting (i.e. Sahara, firehose, rawprogram0.xml)
The QFIL I linked is 2.0.1.1. I think the older one isn't compatible with UFS.
i uploaded the wrong file
asianflipboy said:
@dcraffam, what's the version of QFIL that you're using? I don't see any mentions of some of the keywords I was expecting (i.e. Sahara, firehose, rawprogram0.xml)
The QFIL I linked is 2.0.1.1. I think the older one isn't compatible with UFS.
Click to expand...
Click to collapse
i am using the version you provided 2.0.1.1 that was just a old port trace.. thanks for the help and the interest in the topic
dcraffam said:
i am using the version you provided 2.0.1.1 that was just a old port trace.. thanks for the help and the interest in the topic
Click to expand...
Click to collapse
I took a look at the updated trace. Looks good up to where the computer tries to interact with the device. It seems there's a signature validation it's failing, possibly because the source FRP file isn't official.
In Configure > Firehose configuration, is the option for validation on? If it's on, try running with it off.
When your phone is plugged in and all the files are set, does an "Advanced Options" button show up? If it does, would you mind screenshotting it and posting it on here?
Also, can you search for the log it mentions at the end of the file? No idea where it gets generated, but it's probably in a folder or a file in the same directory called log.
qfil
asianflipboy said:
@dcraffam, what's the version of QFIL that you're using? I don't see any mentions of some of the keywords I was expecting (i.e. Sahara, firehose, rawprogram0.xml)
The QFIL I linked is 2.0.1.1. I think the older one isn't compatible with UFS.
Click to expand...
Click to collapse
asianflipboy said:
I took a look at the updated trace. Looks good up to where the computer tries to interact with the device. It seems there's a signature validation it's failing, possibly because the source FRP file isn't official.
In Configure > Firehose configuration, is the option for validation on? If it's on, try running with it off.
When your phone is plugged in and all the files are set, does an "Advanced Options" button show up? If it does, would you mind screenshotting it and posting it on here?
Also, can you search for the log it mentions at the end of the file? No idea where it gets generated, but it's probably in a folder or a file in the same directory called log.
Click to expand...
Click to collapse
i have to agree with you after trying almost everything i can think of even other programs to just try to send a specific file it all fails to verify so maby the source isnt official as far as the port_trace .txt ill upload it
using the zte axon 7 edl tool it is able to communicate with my phone in edl mode once i replace the firehose prgram in the tools folder if you can get your phone in download mode there is a script to backup some partions includeing the edl boot mode efs reecovery and full maby if you backed up your edl i can restore mine from it if your willing to try it...... that is the zte axon 7 tool kit i couldnt upload the firehose programmer but the on you provided should work its simple just unzip run as admin and its really detailed with info once you open it up thanks aot if you do decide to try i feel like we are running out of ideas lol happy days:good::good:
dcraffam said:
using the zte axon 7 edl tool it is able to communicate with my phone in edl mode once i replace the firehose prgram in the tools folder if you can get your phone in download mode there is a script to backup some partions includeing the edl boot mode efs reecovery and full maby if you backed up your edl i can restore mine from it if your willing to try it...... that is the zte axon 7 tool kit i couldnt upload the firehose programmer but the on you provided should work its simple just unzip run as admin and its really detailed with info once you open it up thanks aot if you do decide to try i feel like we are running out of ideas lol happy days:good::good:
Click to expand...
Click to collapse
I tried the tool, but it was having trouble putting my phone into EDL mode. I tried various methods, like vol+ and vol- while rebooting and changing the fastboot command to send and edl reboot command but it didn't stick. I'll keep trying to get it to work though.
In any case, did you try the Xiaomi Mi Flash tool? Apparently it can work better than QFIL in certain cases.
need fire hose programmer for mi 6x. any idea? or anybody try flash in qdloader9008?
errors from miflash
Code:
Send done packet
[12:01:29 COM20]:file C:\XiaoMi\wayne_images_V9.5.7.0.ODCCNFA_20180429.0000.00_8.1_cn\images\prog_emmc_firehose_Sdm660_ddr.elf transferred successfully
[12:01:31 COM20]:send nop command
[12:01:31 COM20]:send command:<?xml version="1.0" ?><data><nop verbose="0" value="ping"/></data>
[12:01:31 COM20]:get response from target
[12:01:31 COM20]:dump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Binary build date: Apr 28 2018 @ 23:22:35"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Chip serial num: 0 (0x0)"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke "/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Binary build date: Apr 28 2018 @ 23:22:35
"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="fh.attrs.Verbose is set to 0"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Chip serial num: 0 (0x0)"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Supported Functions: program configure sig nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke "/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" />
</data>
[12:01:31 COM20]:send configure command
[12:01:31 COM20]:send command:<?xml version="1.0" ?><data><configure verbose="0" ZlpAwareHost="1" MaxPayloadSizeToTargetInBytes="131072" MemoryName="emmc" SkipStorageInit="0"/></data>
[12:01:31 COM20]:get response from target
[12:01:31 COM20]:dump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
[12:01:31 COM20]:[12:01:31 COM20]:dump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
Not only are you posting in the wrong section, you aren't even in your device's subforum.
NickTheSickDick said:
Not only are you posting in the wrong section, you aren't even in your device's subforum.
Click to expand...
Click to collapse
omg sorry, strange lags)
same problem, any solutions ??? ERROR: Only nop and sig tag can be recevied before authentication
redminote brick ( unblocked and testpoint failed )
Firehouse can not flash, because the programmer prog_emmc_firehose_Sdm660_ddr.elf is waiting for authorization to continue.
I will pass a file to which I have removed the authorization, I do not know if it works, but if you want you can try it.
Replace the file inside the images folder and comment.
Download here: drive.google.com/open?id=1mmpNYOZWYzQXRsLvDB7_TzNydUiZp4Gu
Greetings.
Hello raulmhe,
How you have removed authorization please ?
Can be used programmer for sdm660 for emmc from another producer or another xiaomi product ?
Thank you.
PS: If it works you have made happy all xiaomi users which uses sdm660 programmer and especially Redmi Note 5/Pro users.
raulmhe said:
Firehouse can not flash, because the programmer prog_emmc_firehose_Sdm660_ddr.elf is waiting for authorization to continue.
I will pass a file to which I have removed the authorization, I do not know if it works, but if you want you can try it.
Replace the file inside the images folder and comment.
Download here: drive.google.com/open?id=1mmpNYOZWYzQXRsLvDB7_TzNydUiZp4Gu
Greetings.
Click to expand...
Click to collapse
did you really succeded in removing authorization? did try it practically on a phone?
Me and another miui user have tested raluhme idea but used programmer from miui 9.2.4.0 and 9.5.6.0 for a bricked RN5 AI.
For Redmi Note 5/Pro at least until miui 9.5.13.0 no programmer has auth code.
9.5.19.0 programmer has auth code.
Doesn't ask for auth but when flash starts we have "Cannot read Hello packet ... trying to resetting device " error.
The RN5 phone was not at me it was to the other mi forum user and until now he hasn't been able to bypass/get rid of Cannot read hello packet error.
AngelescuO said:
Me and another miui user have tested raluhme idea but used programmer from miui 9.2.4.0 and 9.5.6.0 for a bricked RN5 AI.
For Redmi Note 5/Pro at least until miui 9.5.13.0 no programmer has auth code.
9.5.19.0 programmer has auth code.
Doesn't ask for auth but when flash starts we have "Cannot read Hello packet ... trying to resetting device " error.
The RN5 phone was not at me it was to the other mi forum user and until now he hasn't been able to bypass/get rid of Cannot read hello packet error.
Click to expand...
Click to collapse
ok plz inform me if u find a solution
AngelescuO said:
Me and another miui user have tested raluhme idea but used programmer from miui 9.2.4.0 and 9.5.6.0 for a bricked RN5 AI.
For Redmi Note 5/Pro at least until miui 9.5.13.0 no programmer has auth code.
9.5.19.0 programmer has auth code.
Doesn't ask for auth but when flash starts we have "Cannot read Hello packet ... trying to resetting device " error.
The RN5 phone was not at me it was to the other mi forum user and until now he hasn't been able to bypass/get rid of Cannot read hello packet error.
Click to expand...
Click to collapse
This is a very late response, but rather late than never I also got this error message in MiFlash. I know that it sounds strange but my solution was to be VERY fast to press the "refresh" and "flash" button after the device entered EDL mode (with battery disconnected) and showed up in Device Manager. If I waited for like 5-10 seconds it was too late. I also red that another possible solution if the device is not in EDL mode is to completely drain the battery before flashing
I used test points on my pad 4 plus and put it in edl. I replaced the fastboot rom emmc file with the one raulmhe shared. I used miflash 2017.4.25.0 and I was able to successfully flash all with a locked boot loader. Completely bypassing xiaomi's authorization.
i have unlock thebootloder
when i use miflash
in devices manager i see qualcomm hs-usb qdloader 9008
i get this error
cannot receive hello packet
or this :<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
how i can flash and unbrick the phone?
kujman123 said:
i have unlock thebootloder
when i use miflash
in devices manager i see qualcomm hs-usb qdloader 9008
i get this error
cannot receive hello packet
or this :<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
how i can flash and unbrick the phone?
Click to expand...
Click to collapse
Hello i assume you want to dwongrade from MIUI 10 to 9 right?
slashray said:
Hello i assume you want to dwongrade from MIUI 10 to 9 right?
Click to expand...
Click to collapse
yes
Contact Authorised Service centre
kujman123 said:
i have unlock thebootloder
when i use miflash
in devices manager i see qualcomm hs-usb qdloader 9008
i get this error
cannot receive hello packet
or this :<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
how i can flash and unbrick the phone?
Click to expand...
Click to collapse
Need not to worry Drop your phone to nearest service centre. i JUST DID IT TODAY
huttui said:
Need not to worry Drop your phone to nearest service centre. i JUST DID IT TODAY
Click to expand...
Click to collapse
we need to pay for it
or its in the warranty
Try your luck
kujman123 said:
we need to pay for it
or its in the warranty
Click to expand...
Click to collapse
Can't comment as i still didn't got my phone back
huttui said:
Can't comment as i still didn't got my phone back
Click to expand...
Click to collapse
you can update me if they fix it
Hi everyone, I kindly request your help because I am completely puzzled whether I have any options to recover my phone by myself or need to visit a repair service (which I do not want really)
So, I out my Phone to run some Youtube yesterday (it was 90% chargfed) and it stopped playback in 5 minutes and I fell asleep. In the morning I could see a display showing youtube at 20% brightness. After I pressed the power button screen went black and after that, I can not power the device up or enter fastboot, there is also nothing after I charge it.
Once connected to PC I can see it in EDL in MiFlash. I found out that there is a restriction by Xiaomi to flash from EDL nowadays. I googled and found the workaround: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
I did it and after some attempts, I am finally stuck with this error which I can not find any refers to:
{
"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"
}
Here are the logs:
XML:
[18:26:24]:lsusb path:"C:\XiaoMi\MiFlash20191206\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[18:26:24]:ls ubs :Standard Serial over Bluetooth link (COM6)
Standard Serial over Bluetooth link (COM4)
Standard Serial over Bluetooth link (COM5)
Qualcomm HS-USB QDLoader 9008 (COM10)
[18:26:24]:vboytest HubPath:
[18:26:24]:vboytest HubPath: USB#ROOT_HUB30#4&73f3995&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[18:26:24]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[18:26:24]:vboytest HubPath: USB#ROOT_HUB30#5&1247dd3&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[18:26:24]:vboytest HubPath: USB#VIA_ROOT_HUB#5&7d0f70f&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[18:26:24]:vboytest HubPath:
[18:26:24]:GetScriptDevices
[18:26:24]:Specified cast is not valid. at XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[18:26:24]:Specified cast is not valid. at XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[18:26:24]:add device COM10 index 10
[18:26:27]:lsusb path:"C:\XiaoMi\MiFlash20191206\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[18:26:27]:ls ubs :Standard Serial over Bluetooth link (COM6)
Standard Serial over Bluetooth link (COM4)
Standard Serial over Bluetooth link (COM5)
Qualcomm HS-USB QDLoader 9008 (COM10)
[18:26:27]:vboytest HubPath:
[18:26:27]:vboytest HubPath: USB#ROOT_HUB30#4&73f3995&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[18:26:27]:Specified cast is not valid.: at XiaoMiFlash.code.Utility.TreeViewUsbItem.AddPortNode(String HubPath, Int32 NumberOfPorts)
[18:26:27]:vboytest HubPath: USB#ROOT_HUB30#5&1247dd3&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[18:26:27]:vboytest HubPath: USB#VIA_ROOT_HUB#5&7d0f70f&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
[18:26:27]:vboytest HubPath:
[18:26:27]:GetScriptDevices
[18:26:27]:Specified cast is not valid. at XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[18:26:27]:Specified cast is not valid. at XiaoMiFlash.code.Utility.UsbDevice.GetAndroidDevices(TreeViewUsbItem item, List`1& outItems)
[18:26:27]:FlashingDevice.flashDeviceList.Remove COM10
[18:26:27]:add device COM10 index 10
[18:26:27]:Thread start,thread id 27,thread name COM10
[18:26:57]:Thread stopped, thread id 27, thread name COM10
XML:
[18:26:40]:10 COM10 12.5074169s [18:26:40 COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
[18:26:57]:10 COM10 30.0098084s Root element is missing.
XML:
[18:26:27 COM10]:MiFlash 2019.12.6.0
[18:26:27 COM10]:flash in thread name:COM10,id:27
[18:26:27 COM10]:flash in thread name:COM10,id:27
[18:26:27 COM10]:[COM10]:start flash.
[18:26:28 COM10]:cannot receive hello packet,MiFlash is trying to reset status!
[18:26:29 COM10]:try to reset status.
[18:26:29 COM10]:Switch mode back
[18:26:29 COM10]:cannot receive hello packet,MiFlash is trying to reset status!
[18:26:30 COM10]:received hello packet
[18:26:30 COM10]:programmertype: 0
[18:26:30 COM10]:vboytest:D:\flash\images
[18:26:30 COM10]:download programmer file: D:\flash\images\prog_emmc_firehose_Sdm660_ddr.elf
[18:26:30 COM10]:download programmer D:\flash\images\prog_emmc_firehose_Sdm660_ddr.elf
[18:26:38 COM10]:Send done packet
[18:26:38 COM10]:file D:\flash\images\prog_emmc_firehose_Sdm660_ddr.elf transferred successfully
[18:26:40 COM10]:send nop command
[18:26:40 COM10]:send command:<?xml version="1.0" ?><data><nop verbose="0" value="ping"/></data>
[18:26:40 COM10]:get response from target
[18:26:40 COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Binary build date: Oct 26 2018 @ 09:56:38"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Chip serial num: 2373905150 (0x8d7eeafe)"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Supported Functions: program configure nop sig firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase "/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Binary build date: Oct 26 2018 @ 09:56:38
"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="fh.attrs.Verbose is set to 0"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Chip serial num: 2373905150 (0x8d7eeafe)"/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="Supported Functions: program configure nop sig firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase "/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="ACK" />
</data>
[18:26:40 COM10]:send configure command
[18:26:40 COM10]:send command:<?xml version="1.0" ?><data><configure verbose="0" AlwaysValidate="0" ZlpAwareHost="1" MaxPayloadSizeToTargetInBytes="131072" MemoryName="emmc" SkipStorageInit="0"/></data>
[18:26:40 COM10]:get response from target
[18:26:40 COM10]:resdump:<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication."/>
</data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
[18:26:40 COM10]:flashSuccess False
[18:26:40 COM10]:isFactory False CheckCPUID False
[18:26:40 COM10]:before:flashSuccess is False set IsUpdate:True set IsDone True
[18:26:40 COM10]:after:flashSuccess is False set IsUpdate:false set IsDone true
[18:26:40 COM10]:no Binary dump
[18:26:41 COM10]:no Binary dump
[18:26:42 COM10]:no Binary dump
[18:26:42 COM10]:edl authentication
[18:26:42 COM10]:GetUserInfo
[18:26:55 COM10]:AuthFlash
[18:26:55 COM10]:need edl authentication.
[18:26:55 COM10]:authentication edl.
[18:26:55 COM10]:send command:<?xml version="1.0" ?><data> <sig TargetName="req" verbose="1"/></data>
[18:26:55 COM10]:get response from target
[18:26:55 COM10]:no Binary dump
[18:26:56 COM10]:no Binary dump
[18:26:56 COM10]:no Binary dump
[18:26:57 COM10]:no Binary dump
[18:26:57 COM10]:System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at XiaoMiFlash.code.bl.SerialPortDevice.dlAuth()
at XiaoMiFlash.code.bl.SerialPortDevice.ConfigureDDR(Int32 intSectorSize, Int32 buffer_sectors, String ddrType, Int32 m_iSkipStorageInit)
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at XiaoMiFlash.code.bl.SerialPortDevice.dlAuth()
at XiaoMiFlash.code.bl.SerialPortDevice.ConfigureDDR(Int32 intSectorSize, Int32 buffer_sectors, String ddrType, Int32 m_iSkipStorageInit)
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[18:26:57 COM10]:no provision exit:COM10
[18:26:57 COM10]:flashSuccess False
[18:26:57 COM10]:isFactory False CheckCPUID False
[18:26:57 COM10]:before:flashSuccess is False set IsUpdate:True set IsDone True
[18:26:57 COM10]:after:flashSuccess is False set IsUpdate:false set IsDone true
Would really appreciate any help here.
Try flashing from EDL by tapping Test Point
Internal flash reported dead here=\