How To Guide Unbrick / Flash Stock Rom (1.1.7 global) QDLoader 9008 fix | EDL Mode fix

[hemanth.k]

You have to update the drivers to QDLoader 9008, if your device is listed like, then you did boot correctly to EDL mode. Now, it could be an issue with the tool, with the cable, or even, with your device, a device seriously bricked, although, always boot to EDL, in a "dead" brick, it´s unresponsive, and images can´t be loaded to it. For the next show some SS.

here you go

 

[TheNewHEROBRINE]

View attachment 5868443here you go

Did you trying using an EDL cable?

 

[hemanth.k]

Did you trying using an EDL cable?

i dont have one or couldnt prepare one. so i gave the phone at nearby servicecenter

 

[SubwayChamp]

View attachment 5868443here you go

What is it? This way your device is recognized as QDLoader 9008? well, unfortunately it´s hard to help this way, good luck.

 

[hemanth.k]

What is it? This way your device is recognized as QDLoader 9008? well, unfortunately it´s hard to help this way, good luck.

sorry i thought you asked for what is being shown on the phone's screen. on the unbrick tool only that which i showed a couple messages above is being shown. I ddidnt go for mod cable or thedevice didnt get recognised in debug 9008 mode, so i gave the phone at SC.

 

[ot_inc]

Where is button in this diy cable ?

This cable is recognized by the EDL simply by plugging it in.

 

[SubwayChamp]

sorry i thought you asked for what is being shown on the phone's screen. on the unbrick tool only that which i showed a couple messages above is being shown. I ddidnt go for mod cable or thedevice didnt get recognised in debug 9008 mode, so i gave the phone at SC.

I think your device only went to ReadDump mode, it happens when the RAM is exceeded, and can´t process correctly the tasks, a simple reboot sometimes fix it. Of course, in the SC probably they tell you, it´s an issue with the motherboard. Just out of curiosity, kindly, let us know the end of the story.

 

[hemanth.k]

I think your device only went to ReadDump mode, it happens when the RAM is exceeded, and can´t process correctly the tasks, a simple reboot sometimes fix it. Of course, in the SC probably they tell you, it´s an issue with the motherboard. Just out of curiosity, kindly, let us know the end of the story.

I always feared this. That the sc guys say its a MB issue.

If they say so, i am going to bring it back and not going to do any with it, unless somebody from the community helps figure out the issue. And yeah i ll keep it posted.

Also this is how it happened.

I was on 1.5.2 (BL Locked) BL Unlocked. Flashed PA. PA started behaving strange after a month's usage. Went back to 1.1.3(BL Locked) All was fine until those bugs annoyed me System Update kept failing with error 20. I remembered something about having the same firmware in both slots (current: b) so Unlocked BL again. Flashed 1.1.3 on b swithced to slot a, and kaboom!

Debug:

1. Tried EDL mode recovery.
2. AFter installing Qualcomm drivers, device got recognised in 900E mode but not the 9008 debug mode.
3. Couldnt go for Mod Cable, so i felt like giving it at SC where they would have access to these.

Update from SC:
Checked for liquid Damage, none found. (Opened back and peeled off hte black sheets)
THeir network was **** so couldnt download QFIL package is the last response.

 

[SubwayChamp]

I always feared this. That the sc guys say its a MB issue.

If they say so, i am going to bring it back and not going to do any with it, unless somebody from the community helps figure out the issue. And yeah i ll keep it posted.

Also this is how it happened.

I was on 1.5.2 (BL Locked) BL Unlocked. Flashed PA. PA started behaving strange after a month's usage. Went back to 1.1.3(BL Locked) All was fine until those bugs annoyed me System Update kept failing with error 20. I remembered something about having the same firmware in both slots (current: b) so Unlocked BL again. Flashed 1.1.3 on b swithced to slot a, and kaboom!

Debug:

1. Tried EDL mode recovery.
2. AFter installing Qualcomm drivers, device got recognised in 900E mode but not the 9008 debug mode.
3. Couldnt go for Mod Cable, so i felt like giving it at SC where they would have access to these.

When your device is detected in this mode, this means that you (only) have to update the drivers, to get QDLoader 9008, a brief explanation, Qualcomm drivers contains a huge variety of modes, when your device is detected under a Port COM, this means that also it´ll support the huge variety of modes that Qualcomm drivers contains, suppose that Qualcomm contained 50 modes, you shouldn´t expect that your device have 50 ways to boot to those modes, no, under Port COM, your device can detect those 50 modes that Qualcomm drivers contains, it´s only that the drivers have to be updated (on the go), to run properly, in this specific mode you need; QHUSB-9008.

Update from SC:
Checked for liquid Damage, none found. (Opened back and peeled off hte black sheets)
THeir network was **** so couldnt download QFIL package is the last response.

 

[hemanth.k]

When your device is detected in this mode, this means that you (only) have to update the drivers, to get QDLoader 9008, a brief explanation, Qualcomm drivers contains a huge variety of modes, when your device is detected under a Port COM, this means that also it´ll support the huge variety of modes that Qualcomm drivers contains, suppose that Qualcomm contained 50 modes, you shouldn´t expect that your device have 50 ways to boot to those modes, no, under Port COM, your device can detect those 50 modes that Qualcomm drivers contains, it´s only that the drivers have to be updated (on the go), to run properly, in this specific mode you need; QHUSB-9008.

Sorry for my innocence or ignorance in these matters, but may i know what you mean by updating the drivers on the go to debug 9008 mode?

Because i tried something similar on my windows system. I have manually updated the driver to Debug 9008 mode. And the flash tool didnt work. Someone said it should be with a mod USB C - A cable.

 

[TheNewHEROBRINE]

Someone said it should be with a mod USB C - A cable.

I said so because, OP said so.
Also, I have never seen someone reporting that the driver change procedure actually work.

 

[SubwayChamp]

Sorry for my innocence or ignorance in these matters, but may i know what you mean by updating the drivers on the go to debug 9008 mode?

Because i tried something similar on my windows system. I have manually updated the driver to Debug 9008 mode. And the flash tool didnt work. Someone said it should be with a mod USB C - A cable.

Fortunately I kept the procedure from my last session flashing on a Qualcomm device, it´s in Spanish, but the pictures are self explanatory.

 

[hemanth.k]

Fortunately I kept the procedure from my last session flashing on a Qualcomm device, it´s in Spanish, but the pictures are self explanatory.
View attachment 5871557View attachment 5871559View attachment 5871561View attachment 5871563View attachment 5871565View attachment 5871567View attachment 5871569View attachment 5871571View attachment 5871573

I have done exactly this. Then used this QFIL package here (1.1.7) , but then it failed. What did you do beyond this?

 

[SubwayChamp]

I have done exactly this. Then used this QFIL package here (1.1.7) , but then it failed. What did you do beyond this?

Now I´m very confused, if you said in your previous post to that last; "...but may i know what you mean by updating the drivers on the go to debug 9008 mode?" why you now are saying "...I have done exactly this"
And just a clarification, it´s not debug mode, this is a different thing.

If you are absolutely sure (I would ask for pictures( that your device was in 9008 QDLoader, then the issue is from QFIL., if this was the case, then you should need a patched firehose file.

 

[hemanth.k]

Now I´m very confused, if you said in your previous post to that last; "...but may i know what you mean by updating the drivers on the go to debug 9008 mode?" why you now are saying "...I have done exactly this"
And just a clarification, it´s not debug mode, this is a different thing.

If you are absolutely sure (I would ask for pictures( that your device was in 9008 QDLoader, then the issue is from QFIL., if this was the case, then you should need a patched firehose file.

Sorry to break it to you again, but apologies for the miscommunication.

I have already givne in the phone at SC, and i have received a call last night from the SC saying they fixed the phone. I cant give you anymore pictures than the one i alreayd put.

 

[hemanth.k]

... the end of the story.

I got the device back flashed with nos1.1.8

 

[SubwayChamp]

I got the device back flashed with nos1.1.8

Good to know.