Related
Unbrick Zenfone 2 ze550ml/ze551ml​Tutorial how unbrick (save) a cable suspended Zenfone 2 (lost bootloader) absolutely can not use or connect ADB recovery, fastboot to perform the operating system reload. Have to say this is the measure of last resort that you can perform with the Zenfone his second before the machine is required to submit to ASUS support.
How to know that your Zenfone 2 is bricked ?
>> Device can not start, only logo ASUS quite awhile now off. If you use keyboard shortcuts to access cluster bootloader (droidboot), display the cable connection icon which is usually called "the hanging cable."
Device can not connect to your computer regardless of whether in any mode (including ADB, fastboot), this leads to not be able to use ADB fastboot.
Cause: Loss bootloader
Damaged in a bootable partition.
-Most Of the cases are droidboot.img can flash the wrong file by other files as boot.img, recovery.img or get confused by any other machine on the line.
-Case Rare than natural bootable partition defective (not by you impact) or in some cases droidboot.img flash file into the machine suddenly collapsed sources can also occur.
The issue of "hanging cable screen" on Zenfone 2:
-Not Like Zenfone front lines, as his son Zenfone 6 was holding here, he was not sure the cable hanging screens you skipped bootloader, I can still access the bootloader, normal recovery. While on Zenfone 2, once encountered this phenomenon, make sure the machine's bootloader has been lost, this time ADB and fastboot recovery is meaningless.
How to unbrick?
This section explains how unbrick, you do not need sports references may skip and go to parts made right. You are using the Zen series (fone / pad) platform using Intel chips may also refer to similar application for its line, of course, will not be quite the same.
-When Your units with brick Zenfone 2, meaning lost bootloader (in this case), you can not lead to any use fastboot mode to flash the ROM file anymore. Typically, in this case, then one would have to use some special tools to be able to load directly into memory (memory) of the lower level as the bootloader using box, the second in the testpoint or the second machine sprung straight into memory ... However, for the mobile Intel chips sales are done with relatively simple parts, they provide a driver called IntelSocUSB available, when necessary Equipment using bootloader, you could still lose the connection with your computer via lower IntelSoc mode for use in emergencies.
IntelSoc edge-side connection, you also need to use additional software xFSTK Downloader, the tool support is simply loaded bootloader instead of using complex command lines. Unlike the methods used img file, which is when you already have a bootloader, as available "basis" can thus use only 1 img file. In contrast when used xFSTK Downloader you must have 2 file dnx_fwr.bin and ifwi.bin firmware, bootloader file same file simultaneously in the form of a new bin can be loaded into the device.
-Once You have successfully loaded bootloader can easily use tools like ADB fastboot nap ROM or ASUS FlashTool to bring "life" to return to the their Zen2 then.
Perform:
You must perform sequential follow the steps indicated below, a process steps will include many small, you also need to do before the next turn. Since there are many different levels and its brick is just so normal users can not list them all the way, I will try to extend to all cases that may occur, you just follow the sequence guidance, if encountered other problems please cmt for further discussion.
Step 1: Install the driver and connect mode IntelSocUSB IntelSoc
-This Is the driver help with a computer connected to your Zen2 IntelSoc mode as mentioned above. Because of this special driver, on some machines running windows 8 / 8.1 / 10 you can not install the normal way is that to add a little more tricks, not too hard, I'll complete list Under.
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
drive.google.com/file/d/0B2oMRhweQ4CHbURUNk1ZTHI2Mjg/view?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
If you're using Windows 8 / 8.1:
-On Keyboard press Windows + I to show charm bar bar in the right corner, click on the item setting.
Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This force will reboot windows and allows you access to the advanced mode, in turn selected the following items: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
-Continue Press 7 on the keypad to access the installation mode allows drivers.
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
If you're using Windows 10:
-On Keyboard press Windows + I or click Start, select Settings.
-In The Settings window, select the Update & security.
-Continue Choose recovery and click "Restart now".
-When The computer has access to the Advanced screen, how similar startup with Windows 8 above.
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
1.2 Connect with computer IntelSoc Zenfone 2:
After driver installation step above 1.1 as successful you are in a window like this, do not click Next yet. Now you must complete step IntelSoc connection before installing xfstk downloader.
-The Device manager: right-click the Computer icon, select Manager, find the device manager.
-In Device manager, to IntelSOC, click the down side, you only see the present only one item is Intel SoC driver.
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables.
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
-This Is a required step to complete before performing next.
Ash back window IntelSOC earlier installation, click Next and Finish.
1.3 Installing xfstk-downloader:
Download xFSTK Downloader v1.7 here:
drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view?usp=sharing
-Download And install with a setup similar to IntelSoc Driver guided above is, simple installation process does deserve to be noted.
-That's It step 1.
Step 2: Use the Downloader to reload the bootloader xFSTK
This is a tool to support the new bootloader loaded into memory chip straight soc IntelSoc mode.
XFSTK load Downloader v1.7:
drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view?usp=sharing
-The Necessary files:
ZE551ML: drive.google.com/file/d/0B2oMRhweQ4CHR21YaDdXdUNlOGs/view? Usp = sharing
ZE550ML: drive.google.com/file/d/0B2oMRhweQ4CHcHg4WXJQckFGOTA/view? Usp = sharing
After downloading the necessary files extract to a separate folder 3 file dnx_fwr.bin, ifwi.bin, bootloader.
-Open XFSTK Downloader, first passed MRD tab A0 / B0 + A0 + CRC as shown Moor.
-Then Go to Options to change the value in the Value section Override Flag GP 0x80000807. Click OK is complete initial preparation.
This force remains connected to the phone cable.
Begin the process of loading the bootloader:
+ First in turn selected item Firmware FW 2 cells and IFWI DNX 2 dnx_fwr.bin and ifwi.bin file.
+ Section IFWI: skip the first box, in the box looking to file droidboot_dnx.img.POS_sign.bin Image OS, here is our bootloader files.
Now let's go to the Device Status section below, this section shows the number of connected IntelSoc, you need at least one device is connected. If in step 1 you do succeed, make sure xFSTK Downloader also get equipment, if not retry the connection cable.
Just click on the download button to start Begin implementation.
-Here You may see error faild continuity however kept calm to software performance. Until now informed SUCCESS as shown below, then congratulate you, our problem is almost solved.
The process is loaded bootloader successful restart when you will not see another familiar ASUS screen but instead is a 4 color, just like some TV stations stop broadcasting on TV.
Shortcuts in bootloader test can not yet see. Now you can load the ROM via fastboot mode / droidboot and know.
-If Not know how to do this, see step 4. If the flash ROM or flash via fastboot not finished still not on the operating system, your computer would be heavier than normal, continue to step 3.
-Note: Hanging cable phenomenon will appear again if you are not successful flash ROM. Each drawing shows the cable hanging out, you need to perform this step 2.
Step 3 (if applicable): Using ASUS FlashTool reloaded raw files.
Here's how to load ROM via fastboot mode is considered as the most supportive.
Download ASUS FlashTool 1.0.0.14: the previous version can not support Zenfone 2.
https://drive.google.com/open?id=0B4uMV7GwfDAEYm5RWTFydXZWOTQ
Download firmware for ZE551ML 2.20.40.194 raw format here:
https://drive.google.com/file/d/0B0v_vGzEh1G5WU1QTzlTOExIekU/view
Version for ZE550ML 2.20.40.155 raw format here: https://yadi.sk/d/XAUyR8eRtuKdA
Installing ASUS FlashTool resembles IntelSoc describes how to install the above, you also need to fully implement the steps before the installation on your Windows 7.8.10 will not repeat again.
-To Phone droidboot mode / fastboot, connected computer, enable ASUS FlashTool.
ASUS FlashTool -On screen, in the model of your selected device (ZE551ML / ZE550ML). Part wipe data option. Click the button next to wipe data section to find raw files downloaded above.
Below current frame connected devices, if not try to wait for a few minutes, plug in the cord, if not you are required to reinstall the driver IntelUSB (this does not lead his popularity and link again).
-Click Select your device and press the Start button to begin implementation.
Firmware loading process long-range 5 to 10 minutes. Then the machine will automatically boot into the operating system, if successful, congratulations to you.
Note: It is possible at this stage you will not succeed with the process of loading raw files, the software itself runs completely without any notice. If this process occurs too 30p then your job is forced to withdraw cable.
-Mark Whether the file import process may not succeed but at least Flash Tool ASUS sent commands resize partitions, if the command is successful, then the partition on the device has been fixed and you was able to load the ROM type fastboot okay, do the next step 4 preview successful offline.
Step 4: Use a rechargeable Fastboot img file.
The last pitch to bring life back to the two of you here Zenfone.
-There Bootloader means you can use fastboot to flash ROM img format already.
Img -Download the latest ROM for Zenfone 2 here:
-Choose The appropriate ROM version (ZE551ML / ZE550ML) and download all the files in that directory, links to download: mega.nz/#F! K4MHiAgL! DVuOKeH3eokcwPSNI79ffw! Xwc0BJrY
-Use Manager winrar or any unzip the archive file will be system.img system.zip
-Copy Boot.img, droidboot.img, recovery.img, system.img in the folder C: \ adb adb install directory or your.
-file SplashImage here:
fshare.vn/file/2KIL3GQ1NZN2
General similarity copied to the folder with the other files.
Open ADB made the following statement:
Code:
fastboot flash splashimage splashimage.img
fastboot fastboot flash droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Added to index, thanks for your work!
cmendonc2 said:
Added to index, thanks for your work!
Click to expand...
Click to collapse
My another Guide to Recover Fastboot of bricked Zenfone 2 ze551ml
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
Thank u very much for this tutorial
Z008
Raw firmware link added for ze550ml users
is it normal for my "MOOREFIELD" to appear temporarily?
Should i continue despite my detect = 0 since it appear temporarily?
I have a few corrections that I have to figure out myself in order to get through, I hope these are a translation problems and can be solved easily.
First of all, the links for Z008 (raw image) is misspelled and contains bad characters (the "*"s). And the Fastboot image link is misspelled too or broken, either of them, therefore, I had to look in the index for those.
Then, The Asus Flash Tool AFT the version provided is 1.0.0.7 which is very old and doesn't support our phones, then I had to look up for the newest one (or even compatible) which is 1.0.0.14. Then the flashing instructions in xFSTK are confusing because there are 3 files to flash (explained better on the other post) FW DnX is the Dnx, IFWI is IFWI, OS DnX is blank and OS Image is the droidboot. That is much simpler.
The part of the explanation of how to use the AFT is almost unredeable. It's just simple as choosing the model, choose to Wipe Data (yes), look for the raw image, selecting the phone with its serial number (btw, the installation of the drivers was a little messy since the AFT Install couldn't install them).
Don't misunderstand this reply, this guide was very useful to me, but I correct this for the ones that encounters this problem. I succeed unbricking my zenfone after it went to the USB Logo by itself (I still don't know why would this happens since I didn't touch the fastboot, but it clearly shows that this cases could happen to anyone).
nanofives said:
I have a few corrections that I have to figure out myself in order to get through, I hope these are a translation problems and can be solved easily.
First of all, the links for Z008 (raw image) is misspelled and contains bad characters (the "*"s). And the Fastboot image link is misspelled too or broken, either of them, therefore, I had to look in the index for those.
Then, The Asus Flash Tool AFT the version provided is 1.0.0.7 which is very old and doesn't support our phones, then I had to look up for the newest one (or even compatible) which is 1.0.0.14. Then the flashing instructions in xFSTK are confusing because there are 3 files to flash (explained better on the other post) FW DnX is the Dnx, IFWI is IFWI, OS DnX is blank and OS Image is the droidboot. That is much simpler.
The part of the explanation of how to use the AFT is almost unredeable. It's just simple as choosing the model, choose to Wipe Data (yes), look for the raw image, selecting the phone with its serial number (btw, the installation of the drivers was a little messy since the AFT Install couldn't install them).
Don't misunderstand this reply, this guide was very useful to me, but I correct this for the ones that encounters this problem. I succeed unbricking my zenfone after it went to the USB Logo by itself (I still don't know why would this happens since I didn't touch the fastboot, but it clearly shows that this cases could happen to anyone).
Click to expand...
Click to collapse
I will try to update all the links and make my post more clear as soon as possible .
Thanks for doing corrections in my post .
Unfortunately, I've encountered some other issues after I succesfully unrbricked my Zenfone. I must say that I quite step away from some of the steps since after I flashed the RAW Image file on the AFT I successfully boot into system. That means I skipped the flashing of the other img droidboot, boot, recovery and system images provided. Then, when I tried to flash TWRP back again, I noticed that even though the flash was succeed, trying to boot in recovery mode lead me back to fastboot mode, pointing out that recovery partition is still damaged. Maybe I need to flash the RAW again to repartition, but since the phone works now I don't want to touch anything again. I can still flash things through fastboot though, the Xposed, the root image, etc. But it seems like I don't have a recovery functional.
The sources for this are still very poor and we need to bring it all the things that the Russian, Vietnam and Chinese forums were posting all this time about the ubrick thing, maybe there's something that I've missed.
Did anyone try to download the system images from that Mega page? I found the link somewhere but the compressed files seems to be corrupted (for the Z008), I would appreciate if anyone else can confirm this.
issue with serial no.
AFT fail to flash coz of serial don't match with actual serial no. of phone
any solution
aniruddha007 said:
issue with serial no.
AFT fail to flash coz of serial don't match with actual serial no. of phone
any solution
Click to expand...
Click to collapse
Which version of AFT are you using?
Explain what do you mean with "doesn't match" I didn't have to check the serial number at any point.
http://mega.nz/#F! K4MHiAgL! DVuOKeH3eokcwPSNI79ffw! Xwc0BJrY
Link dead, new link pls
nanofives said:
Which version of AFT are you using?
Explain what do you mean with "doesn't match" I didn't have to check the serial number at any point.
Click to expand...
Click to collapse
it checks for serial no. of device n fails
so i tried to flash twrp.img using fastboot but got an error "flash_cmds error!"
plz help me guys
As this is an error that was not reported when I was reading through all the foreign forums, I have to state the obvious since I don't have a particular answer.
I assume at this point that you have all the proper drivers, therefore the AFT shouldn't recognise the device. So... what I think is, is your phone in fastboot mode? (I mean the fastboot mode with the 4 colours instead of the ASUS Logo). Maybe there could be a failure in the process of unbricking with the xFSTK downloader.
Add source
please add source bro, this's my tut
amtech. vn/threads/un-hard-brick-zenfone-2-giai-phap-cuu-may-cuoi-cung-truoc-khi-den-trung-tam.370362/
remove blank after "."
---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------
And thanks for translating :angel:
---------- Post added at 07:58 PM ---------- Previous post was at 07:48 PM ----------
aniruddha007 said:
it checks for serial no. of device n fails
so i tried to flash twrp.img using fastboot but got an error "flash_cmds error!"
plz help me guys
Click to expand...
Click to collapse
you can't use fastboot to flash img file because some partitions still have error.
You must use AFT, try check your cable and run AFT as Admin.
---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------
@nanofives
it show the 4 colours because it have no splashimage
yes its in fastboot mode
nanofives said:
As this is an error that was not reported when I was reading through all the foreign forums, I have to state the obvious since I don't have a particular answer.
I assume at this point that you have all the proper drivers, therefore the AFT shouldn't recognise the device. So... what I think is, is your phone in fastboot mode? (I mean the fastboot mode with the 4 colours instead of the ASUS Logo). Maybe there could be a failure in the process of unbricking with the xFSTK downloader.
Click to expand...
Click to collapse
oh yes its in fastboot with 4 colour
I have problems in 4-color screen.
Everything I do ok.
I need help from you ...
Thank you very much
What are you trying to do? The process is stuck somewhere?
Enviado desde mi ASUS_Z008 mediante Tapatalk
@salsav3i
Bro i didn't knew that this is your guide , i got this guide in Vietnamese language from my friend who lives in Vietnam
Hi, does this lock my bootloader?
I have created a set of Windows scripts (.cmd files) to backup/restore selected partitions via emmcdl utility (a part of android-host-knife project).
Tested on RN3P but may be used with other Qualcomm-based devices.
emmcdl uses "firehose" module to interact with device's eMMC in 9008/EDL mode. With prog_emmc_firehose_8976_ddr.mbn from the "fastboot" firmware, can read/write partition table and any partition (including non-volatile ones, like modemst1/2, fsg etc.).
With this selected partition list, successfully restored phone's IMEI, MAC addresses and bootloader unlock status after accidental damaging the memory.
Can be used to create rawprogram0.xml file to flash images via MiFlash (recommended) or another Qualcomm utility.
!!! Not for beginners! If you don't know what is a "partition", "image" etc., please don't use this toolset until learning about that.
Do create a basic guide.
Will help a lot of em
Sent from my Redmi Note 3 using Tapatalk
Navi44 said:
Do create a basic guide.
Click to expand...
Click to collapse
Don't want to create a guide for beginners, like "click here and have fun". Since this process is dangerous, a user should have some knowledge, experience, and be careful.
emuzychenko said:
Don't want to create a guide for beginners, like "click here and have fun". Since this process is dangerous, a user should have some knowledge, experience, and be careful.
Click to expand...
Click to collapse
Some are ready to learn and take risks.
Anyways, it's all your choice.
Sent from my Redmi Note 3 using Tapatalk
I'm just trying to restore all partitions on my kate variant, i wiped every partition described in this thread:
https://forum.xda-developers.com/redmi-note-3/how-to/partition-layout-snapdragon-t3530412
It was an atempt to solve a weird bug after tons of flashes, i wiped them again and tried to flash the firmware using miflash in edl mode and nothing happens, it says flash successful but the phone is stuck booting in the MI logo part with the 3 dots.
My phone has locked bootloader, also i wiped those partitions performing an unofficial unlock.
I have the qcn file for the IMEIs.
The question... how to use the file from the OP's post?
If anybody can help me it will be appreciated.
Thank you for your time.
avercros said:
I'm just trying to restore all partitions on my kate variant, i wiped every partition described in this thread:
https://forum.xda-developers.com/redmi-note-3/how-to/partition-layout-snapdragon-t3530412
It was an atempt to solve a weird bug after tons of flashes, i wiped them again and tried to flash the firmware using miflash in edl mode and nothing happens, it says flash successful but the phone is stuck booting in the MI logo part with the 3 dots.
My phone has locked bootloader, also i wiped those partitions performing an unofficial unlock.
I have the qcn file for the IMEIs.
The question... how to use the file from the OP's post?
If anybody can help me it will be appreciated.
Thank you for your time.
Click to expand...
Click to collapse
It can take 10-15 minutes on first boot from miflash. if the dots are animated just go make some food and wait.
also make sure you do it like this : flash global stable FASTBOOT rom in edl mode with miflash, make sure you replace bootloader before you flash with unlocked one (emmc_appsboot.mbn) then reboot to fastboot when you see "successful" msg(hold vol down and power until you see fastboot), then "fastboot flash recovery recovery_zcx.img" then "fastboot boot recovery_zcx.img" i recommend zcx because it will automatically patch dm-verity... when zcx recovery boots, reboot to system. after you boot once into miui you can flash whatever recovery you want through twrp
the names are generic make sure to name your recovery image properly...
fastboot-edl to enter edl from fastboot mode - https://drive.google.com/open?id=0B2w-p-CP_G3FM1pCcG1JT0lfRUk
fastboot rom list - http://en.miui.com/a-234.html
zcx 917 - https://drive.google.com/file/d/0B2w-p-CP_G3FcHJRVTZHSjlNU3M/view?usp=drivesdk
unlocked emmc_appsboot.mbn - https://drive.google.com/file/d/0B2w-p-CP_G3FaXVFdWp1ODJOQm8/view?usp=drivesdk
miflash 64 bit with miphone drivers - https://drive.google.com/open?id=0B2w-p-CP_G3FRHR5UEp5TUMwemM
pabloa2 said:
It can take 10-15 minutes on first boot from miflash. if the dots are animated just go make some food and wait.
also make sure you do it like this : flash global stable FASTBOOT rom in edl mode with miflash, make sure you replace bootloader before you flash with unlocked one (emmc_appsboot.mbn) then reboot to fastboot when you see "successful" msg(hold vol down and power until you see fastboot), then "fastboot flash recovery recovery_zcx.img" then "fastboot boot recovery_zcx.img" i recommend zcx because it will automatically patch dm-verity... when zcx recovery boots, reboot to system. after you boot once into miui you can flash whatever recovery you want through twrp
fastboot rom list - http://en.miui.com/a-234.html
zcx 917 - https://drive.google.com/file/d/0B2w-p-CP_G3FcHJRVTZHSjlNU3M/view?usp=drivesdk
unlocked emmc_appsboot.mbn - https://drive.google.com/file/d/0B2w-p-CP_G3FaXVFdWp1ODJOQm8/view?usp=drivesdk
Click to expand...
Click to collapse
I tried this and the phone keeps stuck in booting.
I think that the last hope for this is a full partition repair or sell it for spare parts :/
avercros said:
I tried this and the phone keeps stuck in booting.
I think that the last hope for this is a full partition repair or sell it for spare parts :/
Click to expand...
Click to collapse
one final thing even though i mentioned it already, you must make sure your phone has dm-verity patched before you boot if you plan on using custom recovery. if you don't use zcx to automatically patch it then you need to install something like lazy patcher before you boot miui the first time. make sure you follow directions carefully. if your phone still isnt booting after 15 minutes (yes it can take that long) then you're out of luck, but i have a strong suspicion that your phone is not bricked.... a hard bricked phone will show no signs of life whatsoever, no leds, no screen, nothing. you must use testpoint method to enter qdloader mode at that point but your phone is not hard-bricked.
pabloa2 said:
one final thing even though i mentioned it already, you must make sure your phone has dm-verity patched before you boot if you plan on using custom recovery. if you don't use zcx to automatically patch it then you need to install something like lazy patcher before you boot miui the first time. make sure you follow directions carefully. if your phone still isnt booting after 15 minutes (yes it can take that long) then you're out of luck, but i have a strong suspicion that your phone is not bricked.... a hard bricked phone will show no signs of life whatsoever, no leds, no screen, nothing. you must use testpoint method to enter qdloader mode at that point but your phone is not hard-bricked.
Click to expand...
Click to collapse
Not working, i've done everything following your post, my phone only shows the MI logo and now it's blinking, it does not boot.
This is in the wrong section.
emuzychenko said:
I have created a set of Windows scripts (.cmd files) to backup/restore selected partitions via emmcdl utility (a part of android-host-knife project).
Tested on RN3P but may be used with other Qualcomm-based devices.
emmcdl uses "firehose" module to interact with device's eMMC in 9008/EDL mode. With prog_emmc_firehose_8976_ddr.mbn from the "fastboot" firmware, can read/write partition table and any partition (including non-volatile ones, like modemst1/2, fsg etc.).
With this selected partition list, successfully restored phone's IMEI, MAC addresses and bootloader unlock status after accidental damaging the memory.
Can be used to create rawprogram0.xml file to flash images via MiFlash (recommended) or another Qualcomm utility.
!!! Not for beginners! If you don't know what is a "partition", "image" etc., please don't use this toolset until learning about that.
Click to expand...
Click to collapse
Thanks for the thread..
Is there some insight to create "rawprogram0.xml" from this tool? I've try to execute it to see if there's any command list but only have "parttable.txt not found" message.
emuzychenko said:
I have created a set of Windows scripts (.cmd files) to backup/restore selected partitions via emmcdl utility (a part of android-host-knife project).
Tested on RN3P but may be used with other Qualcomm-based devices.
emmcdl uses "firehose" module to interact with device's eMMC in 9008/EDL mode. With prog_emmc_firehose_8976_ddr.mbn from the "fastboot" firmware, can read/write partition table and any partition (including non-volatile ones, like modemst1/2, fsg etc.).
With this selected partition list, successfully restored phone's IMEI, MAC addresses and bootloader unlock status after accidental damaging the memory.
Can be used to create rawprogram0.xml file to flash images via MiFlash (recommended) or another Qualcomm utility.
!!! Not for beginners! If you don't know what is a "partition", "image" etc., please don't use this toolset until learning about that.
Click to expand...
Click to collapse
Thanks man !
This tool was a big help for my other device (LYF) based on qualcomm.
it's one of a kind..couldn't find anything similar & easy on internet.
don't know why this thread is not popular given that lot of people want the things this tool can easily do, may be they are reluctant to go over edge and try on own.
Anyway thanks a lot again & Keep good work
Qullcomm device
Hello sir I have erased perist on my device accidentally and my device is Redmi 4x I have tried to restore my persist partion on my device via emmcdl utility when I enter first command emmcdl -1
It's show my device port com 5 and when I entered second command
emmcdl -p COM5 -f prog_emmc_firehose_8937_ddr.mbn -e persist -o persist.img it's showing error failed to write hello response back to device and didn't receive Sahara hello packet from the device and some thing like that. the error also show when I disconnected my device from pc. Please anyone help me.thankyou
Dbdbsss said:
Hello sir I have erased perist on my device accidentally and my device is Redmi 4x I have tried to restore my persist partion on my device via emmcdl utility when I enter first command emmcdl -1
It's show my device port com 5 and when I entered second command
emmcdl -p COM5 -f prog_emmc_firehose_8937_ddr.mbn -e persist -o persist.img it's showing error failed to write hello response back to device and didn't receive Sahara hello packet from the device and some thing like that. the error also show when I disconnected my device from pc. Please anyone help me.thankyou
Click to expand...
Click to collapse
Have u unlocked ur bootloader.
If yes then
Put phone in fastboot mode.
Flash persist img using fastboot command
fastboot flash persist persist.img
Or use advance twrp and flash persist.img in persist partition.
rawprogram0.xml
how to create a rawprogram0.xml which contains all partitions?
i am much willing to learn more about this,
feel free to message me in fb
facebook.com/samuel.tajuda
When I tried to Restore a Backup Userdata.img to my Zenfone, It requires me a Startup Password that I've not currently set on. (I only used Lockscreen and Google's Default Password but nothing happens)
Does somebody know the Encrypted Password made by QCPart or How to Unpack the Disk Image File that only shows Unallocated on Linux Reader for Windows?
I have some important files that I need to retrieve from the Bricked Phone that I backup with it before I Flashed the Android ROM with Clean Firmware
First of all, thanks for all the people here provide very useful message.
Acutally I encouter a lot of similar issues across the posts.
Please refer to the posts here:
Unbrick guide Z00l Ze550kl
Need QCN file for ZE550KL/Z00L (2GB Ram) Please.
[Solved]Stuck on logo when booting into custom ROM( Zenfone 2 laser ZE550KL Z00LD)
My model is ZE550KL 2GB/16GB version.
What need to be prepared (please look around from google)
1. CSCImage for recovery
2. QPST 2.7
3. Workable QCN, if you have no backup please make one from the other post. (you will need imei coverter and HxD)
4. Retail image WW_ZE550KL_1.17.40.1234-rel-user-20160304185904-secured-releaseAFT_QC
5. Offical latest image
6. TWRP
7. Minitool Partition Manager (I tried diskpart but not working, so please use this one)
8. Qualcomm Driver
Here are the procedures for reference (I do this for over 10 times and 3 nights)
Please make sure you have working QCN...otherwise you cannot recover the calling feature.
1. Erase aboot
fastboot_8916 erase aboot
use above command to erase the partition
you can unplug the battery and cable and replug them.
or simply use fastboot reboot command.
Result: Device enter into 9006 mode
2. Open Minitool Partition manager
Right click and Delete all partition.
Create one single partition using ext4 format
Once done, remove the battery and cable, replug them.
Result: Device enter into 9008 mode
3. If you installed QPST, you should have a program called QFIL
Please use it and extract the firmware from CSCImage, it should have all the items except emmc MBN, just copy it from the root folder.
If you do this correct (follow other post for more detail)
Replug the device will give you a fastboot screen
Result: Device with workable fastboot
4. Now you have a clean bootloader, but no other thing
Go to CSCImage and click flashall
Once it is done, all the partitions will be ok (sometimes I got /factory not mount, let's fix this later)
Result: you will have a engineering OS and bootloader unlocked, diag mode natively enabled.
5. Open Software Downloader from QPST, and recover the QCN, it will reboot the phone.
If you are not doing this correctly (and many issues here), you will get bootloop.
And you have to start over again.
My suggestion is do not touch any of the bootloader setting. (so do not try to use unofficial bootloader unlock guide)
Even you give a command like "fastboot oem adb_enable" it will cause a bootloop and have to start over.
So my suggestion is not touch any bootloader setting
Result: The phone calling and data should be recovered. You can test by making some call.
6. If you want to keep your bootloader unlocked, the retail image flashall you can search there is a "oem lock"
change to unlock and run it in fastboot mode.
Result: You will have a bootloader unlocked phone, with WW firmware.
You can start from here to do TWRP.
to fix /factory partition. you can install busybox and in adb shell, use mkfs.vfat for the partition.
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
christian.arvin said:
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
Click to expand...
Click to collapse
This means you didn't unlock your bootloader.
bootloader needs to be unlocked to flash the partition file, and then the partition will be recovered without data.
My bootloader was unlock.
I digged deeper in your method. And this is what i understand and let it be an information for those who will try.
Back up all partition before you delete all partitions. (Your serial and other sensitive data are stored in some of this partition)
Your method only restore 5 partition table that is inside the main0 gpt mbn.
Note: the whole partition table is listed in the both0 gpt mbn.
In my stupidity I renamed the both0 gpt to main0 gpt thinking that it would work. Instead I run into an unstoppable bootloader bootloop.
In an ending note my ZF2 Laser's only hope is a full eMMC reflash that requires external methods. Or let the official professionals handle it.
Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.
sbelcovski said:
Hello everybody. Im asking for help and im pretty desperate for my issue.
I have LG G4 h815 20p which was rooted few years back. Then the phone died and got re-balled recently and it works now. But i can not access twrp by using Volume Down and Power buttons combination. I can go to Download mode where i can updated firmware using LG UP and it will be processed to the end and after the required reboot phone stays black and recognized only as qualcom device in device manager.
I can not use ADB as it will never show any devices under adb device neither fastboot devices. Drivers are installed. Tried bunch of different versions on both win10 and win7 but no luck. I also tried installing those on ubuntu, where the phone is seen as a device under lsusb but not under fastboot or adb.
I just want to get the phone up and running. NO matter if i unroot or keep it rooted. It wont be used as daily phone but im eager to fix it.
The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
Tried LG UP, LG flash tool neither helped. LG Flash tool wont even end as LG UP finishes but wont boot after the reboot when process is completed.
Any help please will be extremely highly appreciated. I am also willing to arrange team viewer if necessary for easiness.
Click to expand...
Click to collapse
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs
steadfasterX said:
Boot to fastboot and exec
fastboot format userdata
(will obviously erase the whole device including photos etc)
If that does not help you can use SALT to flash TWRP to the BOOT (!) partition. For that you must start SALT from the cli with --experimental argument. If you plan to use SALT I recommend using the latest mAid njghtly which has all already installed.
For flashing with SALT you also must do a custom backup of the sbl1 partition and place the twrp image in the same dir where the sbl1 backup is.
Sent from my OnePlus 7T Pro using XDA Labs
Click to expand...
Click to collapse
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?
sbelcovski said:
Hey, Thank you.
I found your stuff uploaded, but i really cant figure it out. Whenever i press Volume UP and Power button to keep them 6-7sec then plug usb cable, the phone misses the chance to go into download mode. So i have no opportunity to go into fastboot. But i can go in download mode but neither fastboot or salt finds the device.
Could you please provide some more info?
Click to expand...
Click to collapse
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-
steadfasterX said:
fastboot and download mode are complete different things. you cannot use fastboot commands in download mode.
you have to provide more info:
how do you run mAid? VirtualBox or from an USB stick (recommended)
share the debug log of SALT when your device is in download mode (Advanced menu -> debug log -> upload button -> share just the link)
boot your device in download mode and THEN start mAid first could also help
.-
Click to expand...
Click to collapse
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.
sbelcovski said:
Hello again.
I figured mAid out. I run from live usb, and i can connect to phone and get the device information through Salt..
What i did:
- i use experimental flag with root privileges and device is read and comes info that my Laf fw does not support direct flashing. (i cant figure it out how this works),
- i made backup of sbl1 partition, downloaded twrp image twrp-3.3.1-PREVIEW-196_g4_MM.img, placed the twrp image in same folder where the backup of sbl1 is.
- Now i dont know how to flash the the twrp to the boot partition. I tried to find some guides but no luck. Yesterday for some reason i had Flash button in salt on the bottom, today it is not there. The way i start salt is by browsing inside /home/android/Desktop/LG directory and use sudo ./SALT.desktop --experimental command. I use the latest mAid from your file server 4.19.126-1-MANJARO - mAid_v2020-07-14_23-43_x86_64_forgetful.iso.
3 attachments are uploaded bellow. The debug log from salt was unable to upload and gave bunch of package errors, so it is attached bellow in a txt file as well.
The phone keeps stable connection in download mode.
Please advice. I am very grateful.
Click to expand...
Click to collapse
you start SALT in experimental mode as this in a terminal:
Code:
~/programs/SALT/salt --experimental
anyways the problem is that your LAF version is 100004 so flashing will likely not be possible.. You can try it anyways by using the above cmd which will bring up the flash buttons.
before doing that rename the twrp image to recovery.img to ease up things.
then you select flash (folder) and ensure that anything else then the recovery image is selected (e.g. do not flash sbl1 etc).
also ensure that the target partition is named "recovery" then choose flash.
as said it will likely not work though as your download mode (LAF) is too new though. you could downgrade with LGup to Lollipop which will allow flashing with SALT for sure.
but back to the initial description, you mentioned that:
[...] after the required reboot phone stays black and recognized only as qualcom device in device manager.
[...]The phone lists bootloader unlocked on the top of the screen together with LG logo and then comes the android robot animation for 3-4 seconds then loops the same 2-3 times then goes black screen (shows as qualcom device in device manager).
These indicates very very likely the beginning of the ILAPO. you can check my signature for some workarounds though there is no proper way to fix it other then by replacing the mainboard.
.-
STYLO 6 MTKCLIENT INSTRUCTIONS FOR FLASHING, BACKING UP, UNLOCKING THE BOOTLOADER, AND ROOTING ON WINDOWS 10/11:
!!!WARNING!!! ATTEMPT THIS AT YOUR OWN RISK, READ THE FULL TUTORIAL BEFORE YOU START!!! I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES! THIS PROCESS IS NOT FOR THE INEXPERIENCED PLEASE HAVE ADB COMMANDS KNOWLEDGE BEFORE TRYING TO ATTEMPT!!
THIS PROCESS WILL WIPE ALL YOUR DATA SO BE PREPARED FOR THE FACTORY RESET TO BE FORCED BEFORE YOU CAN BOOT THE PHONE!!!
DOWNLOADS:
1. Download Python from here "https://www.python.org/downloads/"
2. Download USBDK here "https://github.com/daynix/UsbDk/releases/download/v1.00-22/UsbDk_1.0.22_x64.msi"
3. Download mtkclient here "https://github.com/bkerler/mtkclient"
4. Download SP Flash Tool here "https://www.mediafire.com/file/kyoksq6kncpg8sg/SP_Flash_Tool_v5.2124_Win.zip/file"
5. Download Magisk APK here "https://github.com/topjohnwu/Magisk/releases"
INSTALLATION:
1. Install Python (select "Add Python X.X to PATH")
2. Install USBDK
3. Install Mtkclient- While in the mtkclient folder hold shift and right click and select "Open PowerShell window here" Run this command in that window "python setup.py install" and then run command "pip3 install -r requirements.txt" Mtkclient is now installed correctly.
4. Install SP Flash Tool and use the Scatter file I provided and the preloader file I provided.
5. MTK VCOM Drivers need to be installed.
NEED TO KNOW:
***For the Stylo 6 to connect you must remove some of the loaders from the mtkclient-main\mtkclient\Loader file leaving MTK_AllInOne_DA_5.2136.bin as the only loader needed. Just highlight the unneeded ones and cut and paste them into the parent folder so you will have them for other devices.
***To run a command you will need to hold shift and right click to open a PowerShell window to use the tool.
***With Mtkclient waiting for the phone to be connected by hitting enter with your command entered, you will also need to click "Download" in SP Flash Tool to cause it to be waiting for the phones connection.
Now that both tools are awaiting the phones connection make sure the phone is completely shut off and plug it in WITHOUT ANY BUTTONS PUSHED! You should now be connected to Mtkclient and the tool will be running the command you entered. If you do not get connected with a couple attempts close out mtkclient powershell window and reopen it.
!!!!!DO NOT UNLOCK OR ROOT THE PHONE BEFORE A PROPER BACK UP OF THE DEVICE IS TAKEN!!!!!
!!!!!DO NOT SKIP THIS STEP!!!!!
I recommend taking a full flash back up of the phone right off the bat, this will take a couple hours, but for more experienced users there is a backup of each partition separated into each file separately that will work too.
"python mtk rf flash.bin" Is the command to make 1 single full flash file to restore the phone. To restore the phone with that file the command is "python mtk wf flash.bin"
"python mtk rl out" Is the command that separates each partition into its each individual file and places the files in the out folder, to restore the whole out folder the command is "python mtk wl out" I recommend this backup after unlocking your bootloader so you will have your boot images to use for rooting.
UNLOCKING YOUR BOOTLOADER:
To unlock your bootloader you will first need a full backup to ensure you can recover a bricked device, you will then run these two commands in this order...
"python mtk e metadata,userdata,md_udc"
"python mtk da seccfg unlock"
CONGRATULATIONS YOUR BOOTLOADER IS UNLOCKED!!!
ROOTING YOUR PHONE:
Now to root your phone you will need that single partition back up, or at least your boot_a.img or boot_b.img or both. "python mtk r boot_a,boot_b boot_a.img,boot_b.img" this will pull both your boot.img files only 1 is necessary, but both can be used.
!!ATTENTION!! DO NOT, I REPEAT DO NOT MIX UP YOUR BOOT_A AND BOOT_B FILES YOU WILL LOOSE WIFI OR BLUETOOTH IF YOU FLASH THEM TO THE WRONG SLOT!!!
You install the Magisk APK to your phone and you patch your boot.img with the app, change their names to patched_a.img and patched_b.img if you do both of them, you then copy them to your computer in the same folder that the mtkclient tool is located. If you have fastboot access you can flash patched_a.img to your phone with these commands... "adb reboot fastboot" then "fastboot flash boot_a patched_a.img" and you can ensure your phone boots to that slot with this command... "fastboot --set-active=a"
On models without fastboot access, you will need to flash both your patched_a and patched_b.img with mtkclient.
AGAIN DO NOT MIX THEM UP!!!
"python mtk w boot_a,boot_b patched_a.img,patched_b.img"
CONGRATULATIONS YOUR PHONE IS NOW ROOTED!!!
NOW MAKE ANOTHER BACKUP!!!
Many who are not experienced with root can easily brick or send their device into a bootloop. So once you get it successfully rooted I recommend you do another backup, run this command to do that
"python mtk rf rootedflash.bin"
that will give your new backup a different name so you can keep them organized. You will be able to restore it right back to where you have a freshly rooted phone.
Tips and Tricks:
If you have the 2021 December update you may need to flash an older firmware because LG made a patch to mess up the connection with mtkclient!
To reboot the phone from Brom hold power and volume down buttons until it reboots.
To boot the phone into recovery hold power and volume down until the phone says booting recovery, from recovery you can shut the phone down to try to connect to mtkclient on failed attempts and to boot into fastboot.
On other devices the SP Flash Tool is not needed, like for instance the K51 doesn't need that step.
Special thanks to Bjoern Kerler for his work on his mtkclient tool that makes this all possible.
And to the team at Hovatek for working with me.
I am hoping that a twrp is created for this device soon so that all of this will be a safer easier process, but for now you just have to tread lightly with modifications to the phone as many things aren't tested and may cause a bootloop or a bricked device.
Here is the scatter and preloader file for SP Flash Tool for the Stylo 6
I got the metropcs version of the stylo 6 does it have a snap ot mediatek processor,and i have a chrome book pc will python run on that new to all this kinda of stuff just wanna run a gsi rom since there isnt a twrp for our device any help would be appreciated
I don't know about using a chrome book, but once unlocked you can install a gsi through fastboot, I've had 11 and 12 installed on the stylo 6 and k51
how hard is it too do once everything is setup
im nervous to try scared im.gonna brick the phone is there away to pay to do it online to unlock the bootloader
how did 11 and 12 run on the phone once u installed it
You will lose all data. It forces a factory reset, my tutorial tells it all, the hard part is setting it up, once it's set up correctly it's just running all the commands, sometimes it takes a few attempts to get the phone to connect properly but other than that it's pretty straightforward, you don't gotta worry about bricking it if you make a proper backup first and follow the steps exactly as I've laid them out
Applies to a cricket stylo 6 also ? I have a tester before my boost.
It works on all stylo 6 models, and K51 K61 and any other LG phones that are mediatek. And also almost any mediatek device all around, except so far not on Samsung mediatek phones, but I'm currently working on that.
Most phones don't need the extra step of running sp flash tool, only the stylo 6
Has anyone unlocked their bootloader and rooted with my instructions yet?
Warlockguitarman said:
Has anyone unlocked their bootloader and rooted with my instructions yet?
Click to expand...
Click to collapse
I've tried but so far only been able to connect and make a full back up. It is hard to connect the phone and takes several attempts. That's why I couldn't keep going. Back up took too long and I've got to go to work. I work with my phone so I don't have time for a factory reset.
But I have a question. What is the first command to unlock the bootloader??? I was able to do that one (python mtk e metadata,userdata,md_udc) but when I tried the second command it had disconnected and I couldn't get it to connect fast enough. But it did something to my phone. Things are out of order and some things missing. What does it do??
Haven't tested anything yet** and maybe thus this is still a bit confusing...
Like why is SPFT needed. What it does exactly when one clicks Download? Writes the preloader? Hope not. Could readback be used instead?
And how come Mtkclient is also waiting for device. I suppose one has to start it as well? Like how?
( **and I cannot as having different device)
I haven't tried read back, but sp flash fails to write to the phone, it just holds the phones preloader long enough for the mtkclient to make a successful handshake, I've not found any other way for mtkclient to make a successful connection to the stylo 6, yea it takes multiple attempts and it does force a factory reset when unlocking the bootloader
Warlockguitarman said:
I haven't tried read back, but sp flash fails to write to the phone, it just holds the phones preloader long enough for the mtkclient to make a successful handshake, I've not found any other way for mtkclient to make a successful connection to the stylo 6, yea it takes multiple attempts and it does force a factory reset when unlocking the bootloader
Click to expand...
Click to collapse
Ok and whats this? python mtk e metadata,userdata,md_udc. Changed my phone. Just wanna know what's its purpose. It left my homescreen as if it did a factory reset. But all my files, and many apps I still have. Screenshots below. My homescreen was like the Mario screenshot. Today it turned into the Ghostrider one. And my appdraw changed completely. So I ask again. What does it do? What is it's purpose. Why did that happen? I'll wait for your response before attempting the next command.
All I know is its the first step to unlock the bootloader, which is going to factory reset your phone before you can reboot, so your gonna lose all data, but you can flash back the userdata if you made a backup into the out folder or if you just backup the userdata by itself.
Warlockguitarman said:
I haven't tried read back, but sp flash fails to write to the phone, it just holds the phones preloader long enough for the mtkclient to make a successful handshake, I've not found any other way for mtkclient to make a successful connection to the stylo 6, yea it takes multiple attempts and it does force a factory reset when unlocking the bootloader
Click to expand...
Click to collapse
So, I assume it's the UsbDk drivers that catches the connection...
Mtkclient probably doesn't do a thing at that point, as it isn't running...
That SPFT might slow the process somehow, IDK. I mean that some times these devices are so little time in certain mode that Windows fails to install the drivers, or maybe even use them in time...
It would help that the drivers could be somehow be in installed state already. That is right keys in the registry and all...
Other devices don't need the sp flash tool to connect but for some reason I could never get the stylo 6 to connect unless i had both mtkclient and sp flash waiting for the phone connection
Still I don't understand as your guide doesn't have any command for mtkclient for it to wait for the phone connection... is it missing something?