Develop Bugs

Android - Advanced launcher Error: Cannot create launchers.xml

Hi Guys,
I have been unsuccessfully trying to setup Advanced launcher on my Amazon fire tv running isengard non rooted and need a bit of help as I couldn't find any lead through different forums.
As soon as I create a launcher I get the error: "Cannot create launchers.xml file" ; "cannot do backup"
However I have been able to locate my launchers.xml file and here is what it contain:
Code:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<advanced_launcher version="1.0">
<categories>
<category>
<id>default</id>
<name>Default</name>
<thumb></thumb>
<fanart></fanart>
<genre></genre>
<description></description>
<finished>false</finished>
</category>
</categories>
<launchers>
<launcher>
<id>d7ca314f87186bcabb37a3aa7b649d28</id>
<name>N64</name>
<category>default</category>
<application>/sdcard/Android/data/com.retroarch/files/retroarch.cfg</application>
<args>"%rom%"</args>
<rompath>/storage/extUsb/Retro Gaming/Roms/N64/</rompath>
<thumbpath>/storage/extUsb/Retro Gaming/Roms/N64/</thumbpath>
<fanartpath>/storage/extUsb/Retro Gaming/Roms/N64/</fanartpath>
<trailerpath></trailerpath>
<custompath></custompath>
<romext>N64</romext>
<platform>Nintendo 64</platform>
<thumb></thumb>
<fanart></fanart>
<genre></genre>
<release></release>
<publisher></publisher>
<launcherplot></launcherplot>
<finished>false</finished>
<minimize>false</minimize>
<lnk></lnk>
<roms>
</roms>
</launcher>
</launchers>
</advanced_launcher>
On kodi forums I have been told that maybe I do not have permissions to create/update launchers.xml file with Advanced launcher. I have tried to change permissions through adb shell in chmod but it seems that because I am not rooted, I cannot do that either !
Any Ideas ?
Thanks a lot

Here is the only error I get in my kodi log:
Code:
11:01:50 T:1074216536 ERROR: Control 50 in window 10001 has been asked to focus, but it can't
11:01:50 T:1745679520 DEBUG: LocalizeStrings: no strings.po file exist at /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.program.advanced.launcher-master/resources/language/English, fallback to strings.xml
11:01:50 T:1745679520 NOTICE: AdvancedLauncher: Load launchers.xml file
11:01:50 T:1745679520 NOTICE: AdvancedLauncher: Initialisation
11:01:50 T:1745679520 NOTICE: AdvancedLauncher: 1e7b8f5c6ff492497f785c40753d4827 category folder > Launcher list
11:01:50 T:1074216536 DEBUG: bool XFILE::CPluginDirectory::WaitOnScriptResult(const string&, int, const string&, bool)- plugin returned successfully
11:01:50 T:1745679520 INFO: CPythonInvoker(40, /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/plugin.program.advanced.launcher-master/addon.py): script successfully run
11:01:50 T:1738250528 NOTICE: Thread BackgroundLoader start, auto delete: false
11:01:50 T:1074216536 ERROR: static bool XFILE::CDirectory::GetDirectory(const CURL&, CFileItemList&, const XFILE::CDirectory::CHints&, bool) - Error getting plugin://plugin.program.advanced.launcher/?1e7b8f5c6ff492497f785c40753d4827
11:01:50 T:1074216536 ERROR: CGUIMediaWindow::GetDirectory(plugin://plugin.program.advanced.launcher/?1e7b8f5c6ff492497f785c40753d4827) failed
11:01:50 T:1738250528 DEBUG: Thread BackgroundLoader 1738250528 terminating
11:01:50 T:1074216536 DEBUG: CGUIMediaWindow::GetDirectory (plugin://plugin.program.advanced.launcher/?1e7b8f5c6ff492497f785c40753d4827)
11:01:50 T:1074216536 DEBUG: ParentPath = [plugin://plugin.program.advanced.launcher/]
11:01:50 T:1531006792 DEBUG: bool XFILE::CPluginDirectory::StartScript(const string&, bool) - calling plugin Advanced Launcher('plugin://plugin.program.advanced.launcher/','21','?1e7b8f5c6ff492497f785c40753d4827')
11:01:50 T:1531006792 DEBUG: bool XFILE::CPluginDirectory::WaitOnScriptResult(const string&, int, const string&, bool) - waiting on the Advanced Launcher (id=41) plugin...
11:01:50 T:1733488360 NOTICE: Thread LanguageInvoker sta
11:02:12 T:1536950664 DEBUG: Thread LanguageInvoker 1536950664 terminating
11:02:12 T:1074216536 DEBUG: Keyboard: scancode: 0x04, sym: 0x0008, unicode: 0x0000, modifier: 0x0
11:02:12 T:1074216536 DEBUG: bool CInputManager::eek:nKey(const CKey&): backspace (0xf008) pressed, action is Back
11:02:12 T:1074216536 DEBUG: CGUIMediaWindow::GetDirectory (plugin://)
11:02:12 T:1074216536 DEBUG: ParentPath = []
11:02:12 T:1531006792 ERROR: Unable to find plugin
11:02:12 T:1074216536 ERROR: static bool XFILE::CDirectory::GetDirectory(const CURL&, CFileItemList&, const XFILE::CDirectory::CHints&, bool) - Error getting plugin://
11:02:12 T:1074216536 ERROR: CGUIMediaWindow::GetDirectory(plugin://) failed
11:02:12 T:1074216536 DEBUG: CGUIMediaWindow::GetDirectory ()
11:02:12 T:1074216536 DEBUG: ParentPath = []
Might help !

fireHose

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.

Help explain Miflash error log

Tried with Miflash Pro with the lastest update v5.3.714.36 I can sign in in the authorized tab with my 2016 account.
[23:48:23]:5 COM5 6.4132248s cannot receive hello packet
[23:50:56]:5 COM5 6.4076536s cannot receive hello packet
[23:52:01]:5 COM5 7.5992028s resdump:<?xml version="1.0" encoding="UTF-8" ?><data><log value="Read back verify failed at sector 230,num sectors 506" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 506" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>

Hi, I have the same problem, did it work out?
thanks

Phone bricked, QFIL shows firehose fail / "The target rejected your <configure>"

Hi there, hope for your help on a bricked Mi 9 SE grus. Situation is as following:
-phone got bricked by failed downgrade from xiaomi.eu-ROM downgrade to the official Xiaomi Global ROM
-phone shows nearly no signs of life (no response on any single button/button combination, no vibration, no heating up while battery charge)
-only sign f life is when phone ist set to EDL mode by testpint method -> then phone is recognized on PC as "Qualcomm HS-USB QDLoader 9008 Com 5"
So I tried to revive the phone by using Qualcomm QFIL (v2.0.3.5, build type flat build). Firehose configuration is set to:
-download protocol: 0 - Sahara
-device type: UFS
-validation mode: 0 - no validation
-no other checkbox is set
I tried different unzipped fastboot ROMs (last China [grus_images_V12.0.2.0.QFBCNXM_20200804.0000.00_10.0_cn], several global ROMs). By all of them QFIL fails, it shows:
Download Fail:Firehose Fail:FHLoader Failrocess Fail
The (shortened, due to char limitation in this post) detailed log shows as following:
Spoiler: detailed log
11:22:36: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM5 --sendxml=rawprogram0.xml --search_path=C:\_GRUS_CN_V12_0_2_Normal\images --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=ufs
************************************************
11:22:36: DEBUG: XML FILE (117 bytes): CharsInBuffer=1961-117=1844
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Jul 3 2020 @ 22:57:39" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: Binary build date: Jul 3 2020 @ 22:57:39'
11:22:36: DEBUG: XML FILE (118 bytes): CharsInBuffer=1844-118=1726
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Jul 3 2020 @ 22:57:39
" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: Binary build date: Jul 3 2020 @ 22:57:39
'
11:22:36: DEBUG: XML FILE (116 bytes): CharsInBuffer=1726-116=1610
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Chip serial num: 4135639522 (0xf680d9e2)" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: Chip serial num: 4135639522 (0xf680d9e2)'
11:22:36: DEBUG: XML FILE (101 bytes): CharsInBuffer=1610-101=1509
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Supported Functions (14):" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: Supported Functions (14):'
11:22:36: DEBUG: XML FILE (83 bytes): CharsInBuffer=1509-83=1426
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: program" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: program'
11:22:36: DEBUG: XML FILE (80 bytes): CharsInBuffer=1426-80=1346
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: read" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: read'
11:22:36: DEBUG: XML FILE (79 bytes): CharsInBuffer=1346-79=1267
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: nop" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: nop'
11:22:36: DEBUG: XML FILE (81 bytes): CharsInBuffer=1267-81=1186
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: patch" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: patch'
11:22:36: DEBUG: XML FILE (85 bytes): CharsInBuffer=1186-85=1101
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: configure" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: configure'
11:22:36: DEBUG: XML FILE (99 bytes): CharsInBuffer=1101-99=1002
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: setbootablestoragedrive" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
11:22:36: DEBUG: XML FILE (81 bytes): CharsInBuffer=1002-81=921
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: erase" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: erase'
11:22:36: DEBUG: XML FILE (81 bytes): CharsInBuffer=921-81=840
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: power" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: power'
11:22:36: DEBUG: XML FILE (89 bytes): CharsInBuffer=840-89=751
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: firmwarewrite" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: firmwarewrite'
11:22:36: DEBUG: XML FILE (90 bytes): CharsInBuffer=751-90=661
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: getstorageinfo" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: getstorageinfo'
11:22:36: DEBUG: XML FILE (85 bytes): CharsInBuffer=661-85=576
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: benchmark" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: benchmark'
11:22:36: DEBUG: XML FILE (80 bytes): CharsInBuffer=576-80=496
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: emmc" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: emmc'
11:22:36: DEBUG: XML FILE (79 bytes): CharsInBuffer=496-79=417
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: ufs" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: ufs'
11:22:36: DEBUG: XML FILE (82 bytes): CharsInBuffer=417-82=335
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: fixgpt" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: fixgpt'
11:22:36: DEBUG: XML FILE (105 bytes): CharsInBuffer=335-105=230
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: End of supported functions 14" /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'INFO: End of supported functions 14'
11:22:36: DEBUG: XML FILE (136 bytes): CharsInBuffer=230-136=94
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Only nop and sig tag can be recevied before authentication." /></data>
-------------------------------------------------------------------------------------------
11:22:36: INFO: TARGET SAID: 'ERROR: Only nop and sig tag can be recevied before authentication.'
11:22:36: DEBUG: XML FILE (94 bytes): CharsInBuffer=94-94=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
-------------------------------------------------------------------------------------------
11:22:36: DEBUG: Response was 'NAK'
11:22:36: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
11:22:36: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
11:22:36: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Any suggestions what this error causes, resp. how to avoid this/what the solution is? Any kind of help is highly appreciated, thx in advance!

@Theo_Rehtisch have you found any solution because i also have same problem....

hard bricked willow (redmi note 8t) no fastboot / no recovery

I managed to flash the wrong firmware (ginkgo fw => willow) and now the thing is bricked. the only sign of life is a COM30 device under MiFlash / QFIL.
Is there any chance I can unbrick the device myself? I do not want to open it though....

I just found this: https://forum.xda-developers.com/t/...ight-turns-on-for-a-second-using-edl.4228641/
I followed the instructions, but I also get the sahara fail. QFIL says QDLoader 9008 (COM30) - is this EDL mode?

lueromat said:
....
I followed the instructions, but I also get the sahara fail. QFIL says QDLoader 9008 (COM30) - is this EDL mode?
Click to expand...
Click to collapse
Yes, this looks like EDL on com port 30.
You only get QDloader 9008 if you have installed the drivers before, so maybe these are old versions.

Elinx said:
Yes, this looks like EDL on com port 30.
You only get QDloader 9008 if you have installed the drivers before, so maybe these are old versions.
Click to expand...
Click to collapse
sorry, confused - are you sayin this is EDL mode? this is what I see in my device manager:
Qualcomm HS-USB QDLoader 9008 (COM30)

lueromat said:
sorry, confused - are you sayin this is EDL mode? this is what I see in my device manager:
Qualcomm HS-USB QDLoader 9008 (COM30)
Click to expand...
Click to collapse
Yes, if fastboot and recovery aren't possible anymore, you can with testpoint to EDL. But it looks that your device already is in EDL mode

ok - so I don't have to open it up?
does anyone have any idea why I get the error in GFIL?
or any other comments or suggestions?
sucks to have a brick

lueromat said:
...
does anyone have any idea why I get the error in GFIL?
...
Click to expand...
Click to collapse
Try first to update the drivers

Download willow fastboot ROM and extract. Download the programmer(need decompress) and replace the original one which is in "images" folder. Run Xiaomi Flash and select the fastboot ROM folder and it gets ready.
Long press your power button more than 10s so the device could do a power cycle. Then, connect the device to the computer and start flashing immediately.
The programmer posted here is for ginkgo. But ginkgo and willow have same chipset so you can try again.
Good luck.

lueromat said:
...
or any other comments or suggestions?
...
Click to expand...
Click to collapse
Yuki1001 said:
Download willow fastboot ROM and extract. ......
Click to expand...
Click to collapse
Ofcourse, as Yuki1001 said.
Don't use the mentioned Ginkgo rom of the guide, but a fastboot Willow rom. The same as your Willow was delivered from factory or newer. The patched firehose file is the same. Maybe then the flashing will run without error.

Yuki1001 said:
Download willow fastboot ROM and extract. Download the programmer(need decompress) and replace the original one which is in "images" folder. Run Xiaomi Flash and select the fastboot ROM folder and it gets ready.
Long press your power button more than 10s so the device could do a power cycle. Then, connect the device to the computer and start flashing immediately.
Click to expand...
Click to collapse
so this worked! the xiaomi flash tool did something, and it said "flashing success" afterwards. but now nothing happens. shouldn't it be able to boot now that the correct image has been flashed? or do I now have to use QFIL?

After "flashing succes", the image should be flashed. Try to boot with long press power

Elinx said:
After "flashing succes", the image should be flashed. Try to boot with long press power
Click to expand...
Click to collapse
hmm doesn't work unfortunately. I even tried the procedure again: soo it appears that something has been flashed, but afterwards I cannot get it to boot and it still says Qualcomm HS-USB QDLoader 9008 (COM30). maybe it doesn't work with xiaomi flash tool?

lueromat said:
so this worked! the xiaomi flash tool did something, and it said "flashing success" afterwards. but now nothing happens. shouldn't it be able to boot now that the correct image has been flashed? or do I now have to use QFIL?
Click to expand...
Click to collapse
Are you sure the fastboot ROM you flashed is the correct WILLOW fastboot ROM?
Download latest willow fastboot ROM here.
As I said above, extract fastboot ROM and replace the programmer in "images" folder. Then flash again. Please give a screenshot of XiaomiFlash so I could understand your problem better.
You can also try to flash using QFIL.

lueromat said:
hmm doesn't work unfortunately. I even tried the procedure again: soo it appears that something has been flashed, but afterwards I cannot get it to boot and it still says Qualcomm HS-USB QDLoader 9008 (COM30). maybe it doesn't work with xiaomi flash tool?
Click to expand...
Click to collapse
chiming in with my experience here: try to open & disconnect the battery for about 15 seconds after flashing success.
happened with my old Mi 5s Plus, it was stuck in FORCED EDL mode, no way to recover except by battery disconnection after successful flash.

Crescendo Xenomorph said:
... try to open & disconnect the battery for about 15 seconds after flashing success.
..
Click to expand...
Click to collapse
You could be right with this, because I only had a succesfull flash/startup with disconnected battery.
I'm not sure, but it could be that this was the same behaviour with my phone. Phone didn't start after EDL flash.
I hadn't noticed it because I immediately flashed (succesfull) again, with disconnected battery.
Problem is, lueromat hasn't opened his phone for EDL and tries to prevent this.
Maybe full batterydrain will work too.
Question....... is it possible to start fastboot now?
In that case you can try to flash a fastboot rom the normal way again with flashall.bat.

Elinx said:
You could be right with this, because I only had a succesfull flash/startup with disconnected battery.
I'm not sure, but it could be that this was the same behaviour with my phone. Phone didn't start after EDL flash.
I hadn't noticed it because I immediately flashed (succesfull) again, with disconnected battery.
Problem is, lueromat hasn't opened his phone for EDL and tries to prevent this.
Maybe full batterydrain will work too.
Question....... is it possible to start fastboot now?
In that case you can try to flash a fastboot rom the normal way again with flashall.bat.
Click to expand...
Click to collapse
I own a RN8(ginkgo) and it's not easy to open the back cover. I manually went to EDL with a fastboot command and do an experiment to confirm it could flash without errors.. The result is that the phone reboot and boot up with no problems.
Maybe he could try to force reboot by sending reboot command if lueromat did a correct flashing?

@lueromat Try to send reboot command manually.
XML:
<?xml version="1.0"?>
<data>
<power value="reset" />
</data>
(The power tag could let the device reboot to system/to edl with correct value)
Create a xml file and send it to the phone manually after flashing.
Rename the xml to "reboot.xml". I wondering what will happen after you send this command(xml).
Code:
fh_loader.exe --port=\\.\COM30 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc

Elinx said:
Problem is, lueromat hasn't opened his phone for EDL and tries to prevent this.
Maybe full batterydrain will work too.
Click to expand...
Click to collapse
Yuki1001 said:
Maybe he could try to force reboot by sending reboot command if lueromat did a correct flashing?
Click to expand...
Click to collapse
I think you guys may be on to something. I was also thinking that I somehow have to get out of EDL mode, either through waiting, or forcing. Opening the device is a PITA and I'd rather wait until the battery dies (which I guess may take weeks with the screen and all off - good I ordered the poco m3 as replacement ).
So I tried the xml command via fh_loader, but it didn't quite work - see log below. either the xml syntax is wrong, or my phone is still in "sahara-mode" - whatever that is. I tried to play around with QFIL before, maybe it's because of that.
Code:
16:34:07: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
16:34:07: DEBUG: Binary build date: Jun 25 2019 @ 03:16:10
16:34:07: DEBUG: Build Version: 19.06.25.03.16.10
16:34:07: INFO: Current working dir (cwd): C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: INFO: Showing network mappings to allow debugging
16:34:07: DEBUG: New connections will be remembered.
16:34:07: DEBUG:
16:34:07: DEBUG: There are no entries in the list.
16:34:07: DEBUG:
16:34:07: INFO:
16:34:07: INFO: Trying to store 'reboot.xml' in string table
16:34:07: DEBUG: ==================================================================================
16:34:07: DEBUG: ==================================================================================
16:34:07: INFO: Looking for file 'reboot.xml'
16:34:07: DEBUG: 2. Calling stat(reboot.xml)
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='rb'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: Found 'reboot.xml' (65 bytes) in local directory 'C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='r'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: User set ZLPAWAREHOST to 1
16:34:07: INFO: User wants to talk to port '\\.\COM40'
16:34:07: DEBUG: port_fd=0xE0
16:34:07: INFO: Took 0.00000000 seconds to open port
16:34:07: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
16:34:07: INFO: Sending <configure>
16:34:07: DEBUG: CHANNEL DATA (P0000) (H00202) ( 228 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="emmc" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>
============================================================================================================
16:34:07: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
16:34:07: DEBUG: CHANNEL DATA (64 bytes) <-- TARGET to HOST
16:34:07: DEBUG: CharsInBuffer = 64
16:34:07: DEBUG: printBuffer:6017 PRETTYPRINT Buffer is 64 bytes
16:34:07: DEBUG: printBuffer:6094 01 00 00 00 30 00 00 00 02 00 00 00 01 00 00 00 ....0...........
16:34:07: DEBUG: printBuffer:6094 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
16:34:07: DEBUG: printBuffer:6107
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: DetermineTag:6861 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7935 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7945
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work

lueromat said:
I think you guys may be on to something. I was also thinking that I somehow have to get out of EDL mode, either through waiting, or forcing. Opening the device is a PITA and I'd rather wait until the battery dies (which I guess may take weeks with the screen and all off - good I ordered the poco m3 as replacement ).
So I tried the xml command via fh_loader, but it didn't quite work - see log below. either the xml syntax is wrong, or my phone is still in "sahara-mode" - whatever that is. I tried to play around with QFIL before, maybe it's because of that.
Code:
16:34:07: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
16:34:07: DEBUG: Binary build date: Jun 25 2019 @ 03:16:10
16:34:07: DEBUG: Build Version: 19.06.25.03.16.10
16:34:07: INFO: Current working dir (cwd): C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: INFO: Showing network mappings to allow debugging
16:34:07: DEBUG: New connections will be remembered.
16:34:07: DEBUG:
16:34:07: DEBUG: There are no entries in the list.
16:34:07: DEBUG:
16:34:07: INFO:
16:34:07: INFO: Trying to store 'reboot.xml' in string table
16:34:07: DEBUG: ==================================================================================
16:34:07: DEBUG: ==================================================================================
16:34:07: INFO: Looking for file 'reboot.xml'
16:34:07: DEBUG: 2. Calling stat(reboot.xml)
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='rb'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: Found 'reboot.xml' (65 bytes) in local directory 'C:\Program Files (x86)\Qualcomm\QPST\bin\
16:34:07: DEBUG: 2. Calling fopen('reboot.xml') with AccessMode='r'
16:34:07: DEBUG: Trying get filesize, calling fseek()
16:34:07: DEBUG: User set ZLPAWAREHOST to 1
16:34:07: INFO: User wants to talk to port '\\.\COM40'
16:34:07: DEBUG: port_fd=0xE0
16:34:07: INFO: Took 0.00000000 seconds to open port
16:34:07: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
16:34:07: INFO: Sending <configure>
16:34:07: DEBUG: CHANNEL DATA (P0000) (H00202) ( 228 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="emmc" Verbose="0" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="1048576" ZlpAwareHost="1" SkipStorageInit="0" />
</data>
============================================================================================================
16:34:07: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
16:34:07: DEBUG: CHANNEL DATA (64 bytes) <-- TARGET to HOST
16:34:07: DEBUG: CharsInBuffer = 64
16:34:07: DEBUG: printBuffer:6017 PRETTYPRINT Buffer is 64 bytes
16:34:07: DEBUG: printBuffer:6094 01 00 00 00 30 00 00 00 02 00 00 00 01 00 00 00 ....0...........
16:34:07: DEBUG: printBuffer:6094 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
16:34:07: DEBUG: printBuffer:6094 04 00 00 00 10 00 00 00 0D 00 00 00 01 00 00 00 ................
16:34:07: DEBUG: printBuffer:6107
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: DetermineTag:6861 XML not formed correctly. Expected a < character at loc 0
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7935 3. TAG not found or recognized
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
16:34:07: {ERROR: GetNextPacket:7945
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13:prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target
Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
Click to expand...
Click to collapse
Did you send the firehose programmer before you send the reboot xml?
As the log said, may be you forgot to send programmer manually?
{
"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"
}
Do a power cycle and send "prog_emmc_firehose_Sm6125_ddr.elf" using QSaharaServer.exe first:
Code:
QSaharaServer.exe -u 40 -s 13:"prog_emmc_firehose_Sm6125_ddr.elf"
The parameter "-u" is your port number(example COM40 is -u 40).
Then send xml.
Code:
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
You need to send the programmer first to switch the communication protocol to firehose then use fh_loader send reboot xml command. Sorry forgetting to tell you that you need to send programmer first. In fact, before your any operation in EDL mode, your flashtool(miflash/qifl etc..) send the programmer automatically before sending rawprogram0.xml. You can check the flash log for this.
If device reboot but still in EDL mode, may be you need to wait until the battery runs out because I don't know more usage of power command to force reboot to system.
Hope your phone could reboot and back to life.

those commands completed without problem, and after the fh command the phone is disconnected in my device manager for a second, so it appears the xml command worked. however, when it reappears in device manager it's still on com40, and I cannot boot into bootloader. maybe a different command will do it? at least it's listening. here is the log:
Code:
C:\Program Files (x86)\Qualcomm\QPST\bin>QSaharaServer.exe -u 40 -s 13:"prog_emmc_firehose_Sm6125_ddr.elf"
Binary build date: Jun 25 2019 @ 03:16:15
QSAHARASERVER CALLED LIKE THIS: 'QSaharaServer.ex'Current working dir: C:\Program Files (x86)\Qualcomm\QPST\bin
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: prog_emmc_firehose_Sm6125_ddr.elf
18:15:01: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_Sm6125_ddr.elf"
18:15:01: 591740 bytes transferred in 0.125000 seconds (4.5146MBps)
18:15:01: File transferred successfully
18:15:01: Sahara protocol completed
C:\Program Files (x86)\Qualcomm\QPST\bin>fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
Base Version: 19.06.10.18.44
Binary build date: Jun 25 2019 @ 03:16:10
Incremental Build version: 19.06.25.03.16.10
18:15:07: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
fh_loader.exe --port=\\.\COM40 --sendxml=reboot.xml --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
18:15:07: INFO: Current working dir (cwd): C:\Program Files (x86)\Qualcomm\QPST\bin\
18:15:07: INFO: Showing network mappings to allow debugging
18:15:07: INFO:
18:15:07: INFO: Trying to store 'reboot.xml' in string table
18:15:07: INFO: Looking for file 'reboot.xml'
18:15:07: INFO: User wants to talk to port '\\.\COM40'
18:15:07: INFO: Took 0.00000000 seconds to open port
18:15:07: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
18:15:07: INFO: Sending <configure>
18:15:07: INFO: TARGET SAID: 'INFO: Binary build date: Jul 3 2019 @ 22:23:56'
18:15:07: INFO: TARGET SAID: 'INFO: Binary build date: Jul 3 2019 @ 22:23:56
'
18:15:07: INFO: TARGET SAID: 'INFO: Chip serial num: 570422912 (0x21fff680)'
18:15:07: INFO: TARGET SAID: 'INFO: Supported Functions (14):'
18:15:07: INFO: TARGET SAID: 'INFO: program'
18:15:07: INFO: TARGET SAID: 'INFO: read'
18:15:07: INFO: TARGET SAID: 'INFO: nop'
18:15:07: INFO: TARGET SAID: 'INFO: patch'
18:15:07: INFO: TARGET SAID: 'INFO: configure'
18:15:07: INFO: TARGET SAID: 'INFO: setbootablestoragedrive'
18:15:07: INFO: TARGET SAID: 'INFO: erase'
18:15:07: INFO: TARGET SAID: 'INFO: power'
18:15:07: INFO: TARGET SAID: 'INFO: firmwarewrite'
18:15:07: INFO: TARGET SAID: 'INFO: getstorageinfo'
18:15:07: INFO: TARGET SAID: 'INFO: benchmark'
18:15:07: INFO: TARGET SAID: 'INFO: emmc'
18:15:07: INFO: TARGET SAID: 'INFO: ufs'
18:15:07: INFO: TARGET SAID: 'INFO: fixgpt'
18:15:07: INFO: TARGET SAID: 'INFO: End of supported functions 14'
18:15:07: INFO: TARGET SAID: 'INFO: Calling handler for configure'
18:15:07: INFO: TARGET SAID: 'INFO: Storage type set to value eMMC'
18:15:07: INFO: TARGET SAID: 'WARN: NAK: MaxPayloadSizeToTargetInBytes sent by host 1048576 larger than supported 16384'
18:15:07: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 16384
18:15:07: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 16384
18:15:07: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
Send RESET to target with DelayInSeconds="2" ? (y|n):y
18:15:10: INFO: Sending <power>
18:15:10: INFO: TARGET SAID: 'INFO: Calling handler for power'
18:15:10: INFO: ==============================================================
18:15:10: INFO: Files used and their paths
18:15:10: INFO: 1 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt'
18:15:10: INFO: 2 'C:\Program Files (x86)\Qualcomm\QPST\bin\reboot.xml'
18:15:10: INFO: _ (done)
18:15:10: INFO: | |
18:15:10: INFO: __| | ___ _ __ ___
18:15:10: INFO: / _` |/ _ \| '_ \ / _ \
18:15:10: INFO: | (_| | (_) | | | | __/
18:15:10: INFO: \__,_|\___/|_| |_|\___|
18:15:10: INFO: {All Finished Successfully}
18:15:10: INFO: Overall to target 2.922 seconds (0.00 Bps)
Writing log to 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt', might take a minute
Log is 'C:\Program Files (x86)\Qualcomm\QPST\bin\port_trace.txt'