yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ollie2012:
hi I am stuck at qfil and it doesnt detect the port; help please!!

Also this doesnt wipe the phone does it?

---------- Post added at 02:38 AM ---------- Previous post was at 02:17 AM ----------

I am getting this error

2020-09-27 11:34:38.638 11:34:38: ERROR: function: port_connect:100 Failed to open com port handle

2020-09-27 11:34:38.643

2020-09-27 11:34:38.647 11:34:38: ERROR: function: main:297 Could not connect to \\.\COM8

2020-09-27 11:34:38.652 Download Fail:Sahara Fail:QSaharaServer Fail:Process fail

2020-09-27 11:34:38.681 Finish Get GPT
[Android Software Development] alexenferman:
Your phone will not be wiped. Looks like you took too long before doing something in EDL mode. You need to reboot to EDL again.
[Android Software Development] TheDeveloperDude95:
Hey guys, keep getting this error everytime i try to enter partition manager, i get the error.

2020-10-10 02:49:17.606 Start Download

2020-10-10 02:49:17.606 Program Path:C:\Users\Bud36\Desktop\zte\zte-master\Z959\prog_emmc_firehose_8909.mbn

2020-10-10 02:49:17.606 ***** Working Folder:C:\Users\Bud36\AppData\Roaming\Qualcomm\QFIL\COMPORT_3

2020-10-10 02:49:17.873 Binary build date: Jun 25 2019 @ 03:16:15

2020-10-10 02:49:17.873 QSAHARASERVER CALLED LIKE THIS: 'C:\Users\Bud36\Desktop\zte\Qualcomm_Flash_Image_Loader_v2.0.3.5\QSaharaServer.ex'Current working dir: C:\Users\Bud36\AppData\Roaming\Qualcomm\QFIL\COMPORT_3

2020-10-10 02:49:17.873 Sahara mappings:

2020-10-10 02:49:17.873 2: amss.mbn

2020-10-10 02:49:17.889 6: apps.mbn

2020-10-10 02:49:17.889 8: dsp1.mbn

2020-10-10 02:49:17.889 10: dbl.mbn

2020-10-10 02:49:17.889 11: osbl.mbn

2020-10-10 02:49:17.889 12: dsp2.mbn

2020-10-10 02:49:17.889 16: efs1.mbn

2020-10-10 02:49:17.889 17: efs2.mbn

2020-10-10 02:49:17.889 20: efs3.mbn

2020-10-10 02:49:17.889 21: sbl1.mbn

2020-10-10 02:49:17.904 22: sbl2.mbn

2020-10-10 02:49:17.904 23: rpm.mbn

2020-10-10 02:49:17.904 25: tz.mbn

2020-10-10 02:49:17.904 28: dsp3.mbn

2020-10-10 02:49:17.904 29: acdb.mbn

2020-10-10 02:49:17.904 30: wdt.mbn

2020-10-10 02:49:17.904 31: mba.mbn

2020-10-10 02:49:17.904 13: C:\Users\Bud36\Desktop\zte\zte-master\Z959\prog_emmc_firehose_8909.mbn

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904 02:49:17: Requested ID 13, file: "C:\Users\Bud36\Desktop\zte\zte-master\Z959\prog_emmc_firehose_8909.mbn"

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904 02:49:17: 284396 bytes transferred in 0.187000 seconds (1.4504MBps)

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904 02:49:17: File transferred successfully

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904

2020-10-10 02:49:17.904 NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!

2020-10-10 02:49:17.920

2020-10-10 02:49:17.920

2020-10-10 02:49:17.920 02:49:17: Sahara protocol completed

2020-10-10 02:49:17.920 Sending Programmer Finished

2020-10-10 02:49:17.920 Switch To FireHose

2020-10-10 02:49:17.920 Wait for 3 seconds...

2020-10-10 02:49:20.936 Max Payload Size to Target:49152 Bytes

2020-10-10 02:49:20.936 Active Boot Partition:0

2020-10-10 02:49:20.936 Device Type:emmc

2020-10-10 02:49:20.936 Platform:8x26

2020-10-10 02:49:20.936 Disable Ack Raw Data Every N Packets

2020-10-10 02:49:20.936 Skip Write:False

2020-10-10 02:49:20.936 Always Validate:False

2020-10-10 02:49:20.936 Use Verbose:False

2020-10-10 02:49:20.936 ***** Working Folder:C:\Users\Bud36\AppData\Roaming\Qualcomm\QFIL\COMPORT_3

2020-10-10 02:49:20.936 Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified

2020-10-10 02:49:20.951 Finish Get GPT

Any fix would be helpful, my device is an ZTE Z959 (abby)
[Android Software Development] alexenferman:
Do you have the portable QFIL or did you install QFIL on your PC? Make sure you have the installer version!
[Android Software Development] TheDeveloperDude95:
I currently have the portable version, where can i get the installer version
[Android Software Development] javaboy1123:
getting an error, is Z983 supported?

[MENTION=10365003]alexenferman[/MENTION]

Z983 is on the list, I grabbed the correct firehose (at least for the correct proc prog_emmc_firehose_8940.mbn), used the installed version of QFIL and the driver provided, rebooted the phone into FTM, and then adb reboot edl several times and still get the following:

ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:924 Sahara protocol error
ERROR: function: main:303 Uploading Image using Sahara protocol failed

Z983 is in the list of supported phones. Is it actually supported?
[Android Software Development] ibrickedakindlefire1stgen:
Again, I still have no clue what went wrong in my case. I provided the hex dump of my devinfo partition after modifying it and booting in my last reply, and I still have no working method for my device, as it doesn't seem to work. I'm sure there is some way of going about it for my device, but I haven't had any help and I can't think of anything else to do.
[Android Software Development] 99p:
TWRP

How do you get twrp on the phone?

---------- Post added at 05:08 PM ---------- Previous post was at 04:59 PM ----------

How do you flash magisks?
[Android Software Development] darkherman:
[MENTION=10365003]alexenferman[/MENTION]

I don't see the line 007FFE00 on the devinfo partition to unlock bootloader, is there another way to unlock bootloader on another line?

check the file
[Android Software Development] ibrickedakindlefire1stgen:
[MENTION=10279629]darkherman[/MENTION] We have the same issue. I've made a few replies showing the differences between the thread and what's on our devices, but I haven't gotten a single response.
[Android Software Development] alexenferman:
If you don't see the second line, simply change the first one only, and try it, then see if it works.
[Android Software Development] ibrickedakindlefire1stgen:
[MENTION=10365003]alexenferman[/MENTION] As I've mentioned in my previous replies, there is already a 0x01 at offsets 0x10 and 0x18. Another user with the username of "RedneckTechVet" had a similar situation. I've documented my failed attempt at following the steps outlined in his reply before. What he did worked for him, but not for me. I also documented the hex dump after rebooting with the modified partition. I just don't really know how to debug this. I'm not sure if the Magisk patcher isn't working, or if the bootloader actually isn't being unlocked, or anything, just whatever I have done puts it into DFU mode, and I'm not sure where to go from here.

If you have any ideas, let me know.
[Android Software Development] melvin11:
how can i rooted my device oppo a5 2020 (Q) version 10 oreo
[Android Software Development] darkherman:
Which line can you indicate?
[Android Software Development] throw1235:
anything for the VFD 710?
[Android Software Development] damprobot:
Can anyone explain how they succeeded with the max xl (bolton)? I can access everything in qfil but devinfo doesn't have the lines android boot. It's different.
[Android Software Development] Natsuki Subaru:
I have a ZTE z983. I'm stuck on QFIL, I kept getting the error bellow:

Spoiler content hidden.

Here is a step by step of what I did:

-I downloaded QFIL v2.0.1.9 from qfiltool.com

-I downloaded ADB

-I downloaded the QFIL firehose (prog_emmc_firehose_8940.mbn)

-I downloaded the driver provided in QFIL

-I downloaded the driver for z983 (ZTE handset usb driver)

-I rebooted my phone to EDL using ADB

-I opened QFIL and it showed Qualcomm HS-USB QD-Loader 9008 (COM7) and in driver manager

-I selected the QFIL firehose

-I tried to open the partition manager

I'm not really good at stuff like this but I really need that root so sorry if I missed something very obvious.
[Android Software Development] Natsuki Subaru:
I tried using the installer version of QFIL and moving the location of the QFIL firehose from desktop to C:\PROG and rebooting my phone to EDL mode several times, still didn't work. I might have the wrong driver but I'm not sure. Please help
[Android Software Development] Natsuki Subaru:
I have tried reinstalling the drivers

I tried using QFIL v2.0.1.9, v2.0.3.5 and QPST v2.7.474

It still didn't work :cry:

As to why, I'm not sure.

It might be because there's no firehose specifically for z983

But A0620 has the same SoC as z983 so I used that instead.

Or maybe because I'm missing some drivers but I'm pretty sure I have it all.

Can anyone help
[Android Software Development] HunterAnderson:
I got all the way to the part with the hex editor but after that my ZTE Z839 was not the same as the guide. The first boot line was there but the second line already had 01's in the right place. Additionally there was no second android boot part and also near the top of the file was a bunch of FF's.

Does that mean by bootloader is unlocked?

Here is the .bin file.
[Android Software Development] PrivyetCyka:
im having the exact same thing happen but i dont know if the bootloader is unlocked or not because im not sure where to flash the magisk_patched boot img i renamed it boot.img but dont know whether to flash it to boot or aboot if anyone knows just let me know and ill try it out

*edit* tried both and they just bootloop "your device failed to start correctly" and thats with and without preserving verity and signing
[Android Software Development] PrivyetCyka:
you have to immediately...and i mean quick like lightning... the instant that phone goes into edl and the top thing says qualcomm hsusb 9008 or whatever , click whatever button you need( partition flash etc) if it doesnt work the first time you need to reboot the phone or pop the battery and do it again you gotta be quick quick like less than one second
[Android Software Development] ilya980:
I tried this on a 32 bit Windows 7 laptop. It seems that I've got a little further, but I am still getting an error about some file missing. Please help.

Here is the log from 32-bit Win 7 system:

2021-02-28 18:26:16.381 Start Download

2021-02-28 18:26:16.397 Program Path:C:\prog_emmc_firehose_8916.mbn

2021-02-28 18:26:16.397 ***** Working Folder:C:\Users\Ira&Ilya\AppData\Roaming\Qualcomm\QFIL\COMPORT_17

2021-02-28 18:26:16.724 Binary build date: Jun 25 2019 @ 03:16:15

2021-02-28 18:26:16.724 QSAHARASERVER CALLED LIKE THIS: 'C:\Programs\ZTE Z812\Qualcomm_Flash_Image_Loader_v2.0.3.5\QSaharaServer.ex'Current working dir: C:\Users\Ira&Ilya\AppData\Roaming\Qualcomm\QFIL\COMPORT_17

2021-02-28 18:26:16.740 Sahara mappings:

2021-02-28 18:26:16.740 2: amss.mbn

2021-02-28 18:26:16.756 6: apps.mbn

2021-02-28 18:26:16.756 8: dsp1.mbn

2021-02-28 18:26:16.756 10: dbl.mbn

2021-02-28 18:26:16.771 11: osbl.mbn

2021-02-28 18:26:16.771 12: dsp2.mbn

2021-02-28 18:26:16.771 16: efs1.mbn

2021-02-28 18:26:16.771 17: efs2.mbn

2021-02-28 18:26:16.771 20: efs3.mbn

2021-02-28 18:26:16.787 21: sbl1.mbn

2021-02-28 18:26:16.787 22: sbl2.mbn

2021-02-28 18:26:16.787 23: rpm.mbn

2021-02-28 18:26:16.787 25: tz.mbn

2021-02-28 18:26:16.802 28: dsp3.mbn

2021-02-28 18:26:16.802 29: acdb.mbn

2021-02-28 18:26:16.802 30: wdt.mbn

2021-02-28 18:26:16.802 31: mba.mbn

2021-02-28 18:26:16.802 13: C:\prog_emmc_firehose_8916.mbn

2021-02-28 18:26:16.818

2021-02-28 18:26:16.818 18:26:16: Requested ID 13, file: "C:\prog_emmc_firehose_8916.mbn"

2021-02-28 18:26:16.818

2021-02-28 18:26:16.818 18:26:16: 223504 bytes transferred in 0.172000 seconds (1.2392MBps)

2021-02-28 18:26:16.818

2021-02-28 18:26:16.834

2021-02-28 18:26:16.834

2021-02-28 18:26:16.834 18:26:16: File transferred successfully

2021-02-28 18:26:16.849

2021-02-28 18:26:16.849

2021-02-28 18:26:16.849 NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!

2021-02-28 18:26:16.865

2021-02-28 18:26:16.865

2021-02-28 18:26:16.865 18:26:16: Sahara protocol completed

2021-02-28 18:26:16.865 Sending Programmer Finished

2021-02-28 18:26:16.865 Switch To FireHose

2021-02-28 18:26:16.880 Wait for 3 seconds...

2021-02-28 18:26:19.891 Max Payload Size to Target:49152 Bytes

2021-02-28 18:26:19.891 Active Boot Partition:0

2021-02-28 18:26:19.907 Device Type:emmc

2021-02-28 18:26:19.907 Platform:8x26

2021-02-28 18:26:19.907 Disable Ack Raw Data Every N Packets

2021-02-28 18:26:19.907 Skip Write:False

2021-02-28 18:26:19.922 Always Validate:False

2021-02-28 18:26:19.922 Use Verbose:False

2021-02-28 18:26:19.938 ***** Working Folder:C:\Users\Ira&Ilya\AppData\Roaming\Qualcomm\QFIL\COMPORT_17

2021-02-28 18:26:19.954 Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified

2021-02-28 18:26:19.969 Finish Get GPT
[Android Software Development] ilya980:
I installed QPST 2.7.496 and was able to get a step further. I generated port_trace.txt, but I still get an error. Now it is "Download Fail:FireHose Fail:FHLoader Fail:Flash Information is not filled". The log file suggests that PC is talking to the phone just fine. Does anyone know what is still wrong? Thanks.
[Android Software Development] ilya980:
It worked with QPST 2.7.460 and QFIL that comes with it.

But now I am getting no /devinfo partition. I see the same partitions as ninegua Bootloader Unlocking on older Qualcomm ZTE Devices, /Devinfo partition modification | XDA Developers Forums (xda-developers.com)

Is there a way to unlock it? Thanks.
[Android Software Development] xompax:
Howdy! 🤠 I have an old ZTE Z855 from a relative’s LifeLine plan. I tried the procedure with windows 7 x64 and windows 10 x64 but in both cases windows can’t find drivers for QSHUSB_BULK. Anyone else encounter this problem or find a way around it? Thx
[Android Software Development] ilya980:
I was only able to make it work with Win7 x32. For the Z812 I used Qualcomm HS-USB QDloader 9008 driver 2.1.3.5 dated 12/17/2018, QPST 2.7.460 (latest QPST did not work!), the QFIL that comes with it, and the latest ADB driver. The phone is recognized as QSHUSB_BULK under Win10 x64, and is recognized by QFIL on a COM port, but I was never able to get past the sahara error on Win10 x64 ("ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.").

So, I was able to obtain 2 dumps using QFIL. One dump of partitions from the EDL mode (Vol down+Power into FTM mode, then "adb reboot EDL), and another dump from "download mode" (Vol down+Vol up+Power), but I don't know what to do with these dumps. I've tried looking at /aboot with IDA, found references to strings indicating unlocked device, but I don't have skills to figure out what is disabled and whether there is a way to patch the /aboot or the flags it checks.

Anyone can help me understand /aboot? Thanks.
[Android Software Development] nyhat:
Hi,

Looks like it doesn't work on my Z971. adb reboot EDL gives "no devices found" error.
[Android Software Development] ilya980:
Have you installed the adb driver? It is not the same as Qualcomm HS-USB QDloader 9008 driver. Just having adb.exe is not enough. Also, the adb installer I used has some GUI, which I could not click through unless the phone was in the FTM mode. Try putting the phone in the FTM mode, then install that adb driver, then do adb reboot EDL (you might need to reboot after installing adb driver). I recall that some versions of adb worked for me and others did not.
[Android Software Development] PrivyetCyka:
Am I missing something? I followed the directions without any issues to a T and when I got to editing the hex , it was already the way it was supposed to be edited so I reflashed it anyway and nothing.. ? Z839 Blade Vantage
[Android Software Development] ikasemota:
please i have a zte n9131 device(Sprint) that was sent to me as a gift. i have tried all method to unlock it to use all network but not working. will this method to unlock the bootloader work?
[Android Software Development] xompax:
Same here- hex was already properly modified - using the Z855 - was also not sure now to continue. Any thoughts? Happy to provide more details and field questions if needed to help diagnose.
[Android Software Development] ebrahimwaleed:
i have a

TracFone ZTE Jasper LTE Z718TL​

Qualcomm Snapdragon 210 MSM8909

i tried booting to ftm the phone just boots the os i only have access to phone stuck recovery and os

any help will be nice
[Android Software Development] Jnrach2017:
I have no idea, can you guys help me to get this done
[Android Software Development] theqwertman:
I confirmed as well that QFIL is perfectly capable of writing to the boot partition. There is no secureboot (at least, not on the N9835), so if you grab an untouched-from-the-factory phone and do absolutely nothing other than overwrite the boot partition with custom code, the blissfully ignorant bootloader will run your custom code.

I guess ZTE assumed that nobody would ever leak the Qualcomm tools that are capable of leveraging EDL. If the bootloader is the front door, it doesn't matter that it's locked, because there's a back door that's unlocked. It's just that the back door is in an obscure location - people had no idea how to get to it for a while, and even now it's difficult to find the right directions to get to it.

So, what's the reason for bothering to unlock the bootloader? Well, going through the front door is easier, even after you've figured out how to get to the back door. The point is being able to run the familiar fastboot commands, instead of having to fiddle with the Windows-only Qualcomm GUI. And, beyond convenience, an unlocked bootloader has additional capabilities that EDL doesn't, like booting an image without having to flash it first.

But if all you want is to load a custom recovery, kernel, and/or system, then as long as you can get QFIL to work, then there's no need to unlock the bootloader.
[Android Software Development] luridphantom:
does this mean you can flash magisk without unlocking the bootloader?
[Android Software Development] GreenCanMan:
Is there anyway to use this on Linux (Without installing Windows or a Virtual machine)?

I have a z957 btw
[Android Software Development] theqwertman:
Yes, I did that last week. You don't even need to get temp root beforehand.

Use the Qualcomm tool as documented in the first post of this thread, but retrieve boot instead of devinfo

Use adb push to send your boot partition image to your sd card

Install Magisk APK

Patch the boot image with Magisk app

Use adb pull to copy the patched boot image back to your PC

Use the Qualcomm tool again - right-click on boot partition, choose "Load Image", and choose the Magisk-patched boot image

Unfortunately, not until/unless somebody reverse-engineers the binary protocols used in the Qualcomm app and builds a clone of it for Linux. You can try WINE, otherwise you'll need Windows. You can always do Windows in a VM, as long as the VM supports USB.
[Android Software Development] GreenCanMan:
But everytime i use a Windows 7 32 bit VM QFIL just crashes and in a Windows XP 32 bit VM It wont even launch I can try a Windows 7 64 Bit VM or a Windows 8.1 32 Bit VM If That Would Help
[Android Software Development] ilya980:
Does this allow to remove all the AT&T bloatware from the phone? My phone is Z812. There is no devinfo and fasboot oem bootloader is disabled. Wouldn't patching a boot.img this way cause a brick since patched boot.img is not signed? Also is there a TWRP or any custom ROM for this phone? Thanks.
[Android Software Development] theqwertman:
@GreenCanMan all of those are ancient. I recommend using the latest Windows 10, which is what worked for me.
[Android Software Development] GreenCanMan:
So I flashed the wrong firmware on my phone... Does anyone have a stock rom for the ZTE Z957?
[Android Software Development] nirwin:
I'm running this process on a ZTE Blade Vantage (Z839). I'm currently failing at the partition manager step. When I click Tool > Partition Manager > "Ok" in QFIL, the new window that's supposed to allow me to choose the /devinfo partition never appears. I have the firehose downloaded and selected, and the correct port is listed at the top of the QFIL window. I will say that that the phone in EDL is entirely unresponsive, despite that port showing up.

Has anyone else experienced this problem in QFIL? It this just an indication that something is going wrong with the phone connection?
[Android Software Development] luridphantom:
i tried it with a z839 and the firehose supplied in the github doesn't seem to work for me. fyi i'm using the verizon version so not sure if its supposed to be signed differently, kinda like how the zte sonata 3 has a different firehose from the zte maven2
[Android Software Development] luridphantom:
that's interesting, wonder if i can use it to root my axon 7 and axon 7 mini w/o bootloader unlocking since i have social media stuff on them i cant easily pull off without root

what device did you test this on btw?
[Android Software Development] nirwin:
I'm also using the verizon carrier-locked version. Were you able use another method to unlock the bootloader, or is this a project I should quit?
[Android Software Development] luridphantom:
nope, the firehose provided in the github repo doesn't work for the z839. not sure which firehose someone used to get theirs working because the verizon phone seems to require a differently signed firehose from other phones like the zte maven 2/3, etc
[Android Software Development] luridphantom:
just an update that i bricked my zte blade pro v8 on marshmallow 6.0.1 trying this method...if anyone knows where i can download firmware files for this phone or get it back into edl from it's bootlooping state that would be great
[Android Software Development] ilya980:
Hi, does anyone have a firmware PV_ZTE_P816A06V1.0.0B07.zip for a ZTE Z812 phone? I believe, this is one of the early builds. There are a few places on the internet that mention the existence of this build, but they all look shady and want money for the download. There are also MFG_DRV_PKG_QCV1.0.0B04.zip , PV_ZTE_ P816A06_CKETV1.0.0B06.zip , and P816A06_CIQV1.0.0B15_DL.zip mentioned for this phone. Does anyone have any of these files? Thanks.
[Android Software Development] ilya980:
Is there a way to update ZTE Z812 beyond Android 5.1? Is there any custom ROM available?
[Android Software Development] luridphantom:
i wouldnt try it, have one myself and always running out of space. its a terrible phone

i also tried to do the devinfo trick to my z812 but couldnt find that partition
[Android Software Development] ilya980:
It is not the phone that is terrible. It is the bloatware pre-installed by AT&T and "partners". Also SD card works great if you move your apps there. But some apps cannot be moved, because of all AT&T, Google, etc. crap. This phone would be a great phone with some barebones Android 7.0 or something.

You can go to "Storage"->"Used space"->"Apps" and then select bloatware apps one by one and then Clear cache, clear data, uninstall, disable, and force stop. Really helps a lot, but you have to be careful not to disable something you need. I went through like 10 or 15 apps like this right after factory reset.

There is no devinfo partition, but theqwertman says it is possible to root by reading boot image with QFIL, patching with Magisk, and then writing back with QFIL without bricking. I haven't tried because I can't find any custom recovery or custom ROM for this phone. Maybe someone could build a TWRP (or another recovery) and some custom ROM for this phone?
[Android Software Development] luridphantom:
you don't need twrp to flash magisk if you already have qfil access. read back the boot img from qfil, change the dumped binary to something like boot-original.img then copy it to your phone and pass it through the magisk app. take the patched boot img off your phone and qfil that to the boot partition

one thing to watch for is dm-verity, always be ready to flash your original boot img through qfil if something goes wrong