Database Users

[Q] qhsusb_dload Hard Brick

Looks like I have a hard brick with the device manager reporting qhsusb_dload. This appears to be related to corrupt partitioning, the last thing I flashed was a zip package in CWM and rebooted the phone and it didn't reboot by vibrating and showing the Samsung logo, it just was black.
I pulled the battery and attempted to power it on again and I was getting no response from the device, I plugged it into my pc and that's when I saw the qhsusb_dload missing driver which I found drivers for, but it doesn't help me.
My question is, is this something JTAG can fix? I don't want to take a chance on warranty replacement and getting a MF3 factory phone since I wont be able to Loki. Any info would be appreciated.

ChaosMinionX said:
Looks like I have a hard brick with the device manager reporting qhsusb_dload. This appears to be related to corrupt partitioning, the last thing I flashed was a zip package in CWM and rebooted the phone and it didn't reboot by vibrating and showing the Samsung logo, it just was black.
I pulled the battery and attempted to power it on again and I was getting no response from the device, I plugged it into my pc and that's when I saw the qhsusb_dload missing driver which I found drivers for, but it doesn't help me.
My question is, is this something JTAG can fix? I don't want to take a chance on warranty replacement and getting a MF3 factory phone since I wont be able to Loki. Any info would be appreciated.
Click to expand...
Click to collapse
Yes, unfortunately it's down to JTAG with a RIFF box or similar equipment.

GiantBallSack said:
Yes, unfortunately it's down to JTAG with a RIFF box or similar equipment.
Click to expand...
Click to collapse
Figures... now I gotta find someone that can do the JTAG/RIFF repair.

ChaosMinionX said:
Figures... now I gotta find someone that can do the JTAG/RIFF repair.
Click to expand...
Click to collapse
I found this on GSM-Hosting, and was reported to be a Samsung driver. If the driver installs successfully, QPST will probably see the phone, but I doubt that ODIN would. I still think you are down to JTAG, but here's the driver if you want to mess around with the phone some more

GiantBallSack said:
I found this on GSM-Hosting, and was reported to be a Samsung driver. If the driver installs successfully, QPST will probably see the phone, but I doubt that ODIN would. I still think you are down to JTAG, but here's the driver if you want to mess around with the phone some more
Click to expand...
Click to collapse
Thanks, I had the drivers after looking on google so now it shows up as Qualcomm HS-USB QDLoader 9008 (COM6). ODIN so far doesnt appear to be able to see the phone any longer. Will QPST be able to do anything?

ChaosMinionX said:
Thanks, I had the drivers after looking on google so now it shows up as Qualcomm HS-USB QDLoader 9008 (COM6). ODIN so far doesnt appear to be able to see the phone any longer. Will QPST be able to do anything?
Click to expand...
Click to collapse
If you had a full flash file, you could flash it with QPST and unbrick it. Those files are extremely hard to come by, only the service centers seem to have them. It may be possible to backup a different S4 and flash it but you may end up with an identical copy of the other person's phone. My only experience with QPST is changing the service programming for CDMA phones. Hard-bricks I had equipment for. I have it installed, I'll see if I can pull a dump of my phone that can be flashed, but I still wonder about the EFS partitions.

GiantBallSack said:
If you had a full flash file, you could flash it with QPST and unbrick it. Those files are extremely hard to come by, only the service centers seem to have them. It may be possible to backup a different S4 and flash it but you may end up with an identical copy of the other person's phone. My only experience with QPST is changing the service programming for CDMA phones. Hard-bricks I had equipment for. I have it installed, I'll see if I can pull a dump of my phone that can be flashed, but I still wonder about the EFS partitions.
Click to expand...
Click to collapse
Alright thanks, yeah I can get the phone in QPST its listed in Download mode. Wonder if a dump from a working phone could fix it?

ChaosMinionX said:
Alright thanks, yeah I can get the phone in QPST its listed in Download mode. Wonder if a dump from a working phone could fix it?
Click to expand...
Click to collapse
It's possible. Check your PM.

JTAG service only. Period
Sent from my GT-I9505 using xda premium

TheAxman said:
JTAG service only. Period
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Anyone on the forum do JTAG service? I dont want to take chance of ATT warranty sending me a MF3 phone.

GiantBallSack said:
It's possible. Check your PM.
Click to expand...
Click to collapse
I've done a lot of research and experimenting in this area, because I'm currently stuck in a similar situation with my phone stuck in QPST mode. If you have any knowledge about a working .hex file for this device, please let me know (PM me if needed?).
TheAxman said:
JTAG service only. Period
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Pretty much. Unfortunately in my case, JTAG appears not even a viable option. Might be different for the OP, however. Probably has a different "style" of hard-brick.
ChaosMinionX said:
Anyone on the forum do JTAG service? I dont want to take chance of ATT warranty sending me a MF3 phone.
Click to expand...
Click to collapse
There's a few people on the forums with JTAG boxes offering service. Perhaps the most reputable would be @connexion2005 - his website is mobiletechvideos.com. Costs $60 for an S4, plus extras (rush shipping, rush processing, data recovery, etc.), last I looked.
Only problem is, if you're hard-bricked because of the MF3 update somehow, you might be SOL. Last I heard, mobiletechvideos.com sent back a phone to another XDA member, unfixed for this reason. Still waiting to hear the whole story on this, so I wouldn't discredit mobiletechvideos.com yet. They're very good at what they do, and they've repaired thousands of hard-bricks on many different models of phones.

Aou said:
I've done a lot of research and experimenting in this area, because I'm currently stuck in a similar situation with my phone stuck in QPST mode. If you have any knowledge about a working .hex file for this device, please let me know (PM me if needed?).
Click to expand...
Click to collapse
We worked on a good bit today, and QPST just wouldn't cooperate with the phone in anyway. It wouldn't write aboot.mbn like the phone needs. A full flash in .mbn format is needed.

GiantBallSack said:
We worked on a good bit today, and QPST just wouldn't cooperate with the phone in anyway. It wouldn't write aboot.mbn like the phone needs. A full flash in .mbn format is needed.
Click to expand...
Click to collapse
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.

Aou said:
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Click to expand...
Click to collapse
I didnt have MF3 official on there, the only files from MF3 I used were the Modem, and Tasks's latest AOKP had MF3 RIL. I wonder if I am in the same boat as you?
I do however have a replacement device on its way tomorrow, I wonder if ATT has officially gone to MF3 for replacement warranty devices yet?

ChaosMinionX said:
I didnt have MF3 official on there, the only files from MF3 I used were the Modem, and Tasks's latest AOKP had MF3 RIL. I wonder if I am in the same boat as you?
I do however have a replacement device on its way tomorrow, I wonder if ATT has officially gone to MF3 for replacement warranty devices yet?
Click to expand...
Click to collapse
I certainly hope they haven't. If they have, I'd rather pay the $199 deductible on a new device through insurance instead!

Aou said:
I certainly hope they haven't. If they have, I'd rather pay the $199 deductible on a new device through insurance instead!
Click to expand...
Click to collapse
You and me both! I would just assume sell the warrantied device and pay difference to get a Google Edition, I am not real keen on HTC phones. Guess we will see what they ship me when it arrives tomorrow!

Aou said:
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Click to expand...
Click to collapse
nevermind, sorry

Well good news! My replacement from warranty came today and its still running MDL, so guess I will be returning the bricked device. Sigh of relief seeing MDL and not MF3 thats for sure :good::good:

ChaosMinionX said:
Well good news! My replacement from warranty came today and its still running MDL, so guess I will be returning the bricked device. Sigh of relief seeing MDL and not MF3 thats for sure :good::good:
Click to expand...
Click to collapse
man you sure lucked out there

GiantBallSack said:
It's possible. Check your PM.
Click to expand...
Click to collapse
Hey, could you tell me how it is possible ?
i have a I9505 in QPST DL mode and i don't know how to get a dump from a working model !
thx !

[HELP!] I think I messed up my EFS partition and I don't have a backup....

I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.

ethanscooter said:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
Click to expand...
Click to collapse
Where did you find the fastboot file?
________
v7
XDA Assist

v7 said:
Where did you find the fastboot file?
________
v7
XDA Assist
Click to expand...
Click to collapse
I forgot where I found it from... do you know where he correct one is?

ethanscooter said:
I forgot where I found it from... do you know where he correct one is?
Click to expand...
Click to collapse
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?
__
v7
XDA Assist

v7 said:
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?
__
v7
XDA Assist
Click to expand...
Click to collapse
I forgot, honestly this happened a few weeks ago I tried looking through my history but I couldn't find it. How can I fix it?
EDIT: It wasn't from XDA for sure.

ethanscooter said:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
Click to expand...
Click to collapse
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.

_MetalHead_ said:
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.
Click to expand...
Click to collapse
I tried it and still nothing...

http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
first try this.
then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)
(Try this first!!!)
EDIT: if that doesn't reset, try this.
http://forum.xda-developers.com/one...over-oneplus-2-to-t3269543/page2#post64303240
Official O2OS files.

krishna442 said:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
first try this.
then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)
(Try this first!!!)
EDIT: if that doesn't reset, try this.
http://forum.xda-developers.com/one...over-oneplus-2-to-t3269543/page2#post64303240
Official O2OS files.
Click to expand...
Click to collapse
I cannot use that because my device is not hard bricked and it will not install the driver since I can enter the bootloader normally.

Not sure if you've seen this post its based on the post above but I think it just uses fastboot. Don't know if it will work for you, but figured it would be worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2

I tried using the tool and it did not work, I purposely hard bricked the device to try it and still no signal or imei. Another problem is WiFi takes about 4 minutes just to turn on but I can live with that I just want service.

Basically flashing back the stock should bring back the efs. Let's see if someone has a solution. Sorry!

EFS files are unique to each phone. If the EFS is corrupt or damaged, and there is no backup, I don't know of any way to fix it ;_; You can try OnePlus support but they aren't as dumb as carrier warranty or other phone manufacturers. They'll be more likely to know what you did.

It is possible to restore your imei number, I did it on my brothers lg g2. It requires some software for PC (I can't remember the name, you'll have to google it) and the box your phone came in with the imei number. It is possible, so don't lose hope!

EddyH1993 said:
It is possible to restore your imei number, I did it on my brothers lg g2. It requires some software for PC (I can't remember the name, you'll have to google it) and the box your phone came in with the imei number. It is possible, so don't lose hope!
Click to expand...
Click to collapse
Is it called QPST configuration? If so all I need help with is getting the phone to be recognized by the tool. Don't you need it to be on some COM port or something?

ethanscooter said:
Is it called QPST configuration? If so all I need help with is getting the phone to be recognized by the tool. Don't you need it to be on some COM port or something?
Click to expand...
Click to collapse
Yeh that software rings a bell and yeh I believe it's something like com port 47 maybe. It was a while ago when I did it and I can't remember the process of doing it :/

EddyH1993 said:
Yeh that software rings a bell and yeh I believe it's something like com port 47 maybe. It was a while ago when I did it and I can't remember the process of doing it :/
Click to expand...
Click to collapse
Don't I need a special driver? Also, do I need to put the phone into diag mode and how would I do that?

ethanscooter said:
Don't I need a special driver? Also, do I need to put the phone into diag mode and how would I do that?
Click to expand...
Click to collapse
Have a look at this link http://droidmodderx.com/galaxys3/?page_id=79 I really can't remember how I did it and without researching again I won't know. It's a rough idea to maybe help you, I think the device just needs to be in USB debugging mode. I can't help anymore sorry and good luck.

any fix for this yet?

Same problem also with my op2 . No imei no baseband

HardBrick By Flashing Recovery Only !!! Showed QHSUSB_Bulk Help Please

hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?

Google probably won't do anything for you as you installed it at your own risk

mustafa alzubaidy said:
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Click to expand...
Click to collapse
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.

Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.

Heisenberg said:
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Click to expand...
Click to collapse
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.

anmar21 said:
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Click to expand...
Click to collapse
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)

mustafa alzubaidy said:
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
Click to expand...
Click to collapse
Yeah, wrong recovery, big mistake.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.

Heisenberg said:
Yeah, wrong recovery, big mistake.
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Click to expand...
Click to collapse
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help

mustafa alzubaidy said:
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
Click to expand...
Click to collapse
It's impossible to say if or when it might become available.

@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
It corrupts the partition table which affects the other partitions.

mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .

sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc

If he really sends the device in and Google finds out HOW exactly the phone died, he might face severe consequences. It´s dishonest after all.
If you flash the wrong recovery for a different device, it´s your own bad luck. Now here´s the deal, you can still repair the device if a) Huawei would fix it or b) find a phone shop which could replace the motherboard. Once the Bootloader is bricked, there´s barely anything a regular user could do except for some complicated methods which require the knowledge and the special tools which most people don´t have.
anmar21 said:
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
Click to expand...
Click to collapse

mustafa alzubaidy said:
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
Click to expand...
Click to collapse
Flashing the wrong recovery can and does cause such a brick, this is what you're experiencing. I've seen it happen on many devices, it borks the partition table.

mustafa alzubaidy said:
but flashing wrong recovery i dont think it will cause such brick
Click to expand...
Click to collapse
You can tell yourself this all day long, but the phone that is in your hands that is now a doorstop, is proof otherwise.
Very crappy situation, but this is why toolkits stink, and why you need to be VERY careful when you mess w the device.

no imei no network no finger print sensor working...xt1643

i flashed stock rom https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
and now i have no network and my finger print sensor is not working...
then i flashed the 23.1 build
https://drive.google.com/file/d/0B6R99CgoFhmKQUVMVWE4ckEyRms/view
still its not working.
someone please help me.

jayeshaupe90 said:
i flashed stock rom https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
and now i have no network and my finger print sensor is not working...
then i flashed the 23.1 build
https://drive.google.com/file/d/0B6R99CgoFhmKQUVMVWE4ckEyRms/view
still its not working.
someone please help me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Try this

blackbeats said:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
try this
Click to expand...
Click to collapse
u had the same problem?

jayeshaupe90 said:
u had the same problem?
Click to expand...
Click to collapse
nope but i have read threads most suggested to updat to nougat modem and device specific framework

jayeshaupe90 said:
u had the same problem?
Click to expand...
Click to collapse
i am not able to flash .
I does not detect my phone
model: Usb imei not showing
and when i click on start it says failed gpt.bin something

jayeshaupe90 said:
i am not able to flash .
I does not detect my phone
model: Usb imei not showing
and when i click on start it says failed gpt.bin something
Click to expand...
Click to collapse
“Failed gpt.bin” something doesn't help us, or you.
Tell us the exact errors shown. We'll be then able to help you out to the best of our ability.
From my knowledge, you cannot flash a gpt partition file of an older ROM. You should, as Blackbeats mentioned, flash only the modem partition from the correct ROM for your device.

@jayeshaupe90
I think your phone became G4 (not plus !! )...
This happened because of flashing wrong firmware.. and this has no solution till now...
Check this [ https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912 ]
If this happened (your phone became G4) then we cannot do anything to help you, otherwise correct me...
PS. Anyhow someone found solution for network.. read on second page of that thread..

zeomal said:
“Failed gpt.bin” something doesn't help us, or you.
Tell us the exact errors shown. We'll be then able to help you out to the best of our ability.
From my knowledge, you cannot flash a gpt partition file of an older ROM. You should, as Blackbeats mentioned, flash only the modem partition from the correct ROM for your device.
Click to expand...
Click to collapse
as an experimental idea flash twrp then a custom rom then the modem file and see if it detects
PS then jtaging is the last option

jayeshaupe90 said:
i am not able to flash .
I does not detect my phone
model: Usb imei not showing
and when i click on start it says failed gpt.bin something
Click to expand...
Click to collapse
one more casualty, sorry I'm out of tears over my own dead set!
others are also trying, maybe different path to hell, but same result: https://forum.xda-developers.com/moto-g4-plus/help/diag-mode-g4-qpsd-t3591683/page3

BlackBeats said:
as an experimental idea flash twrp then a custom rom then the modem file and see if it detects
PS then jtaging is the last option
Click to expand...
Click to collapse
no success

jayeshaupe90 said:
no success
Click to expand...
Click to collapse
Then jtag it go to the nearest repair shop and get the software restored

BlackBeats said:
Then jtag it go to the nearest repair shop and get the software restored
Click to expand...
Click to collapse
if jtag is what i understand it to be is handing it over to Moto-the-BI*** repair shop, he can't.
his bootloader is unlocked so they are basically going to replace the board which is 80% of phone price.

MK+2017 said:
if jtag is what i understand it to be is handing it over to Moto-the-BI*** repair shop, he can't.
his bootloader is unlocked so they are basically going to replace the board which is 80% of phone price.
Click to expand...
Click to collapse
Try some unauthorized shop local shop

There seems to be a lot of lost IMEIs in the G4 Plus Community, I and a few others have narrowed it down to NV Data corruption, which needs a flash box or a new logic board AFAIK. Good luck mate!

Help unbricking my phone!

I have the T-mobile OnePlus 7t Pro 5G Mclaren edition. I was trying to root it and ended up bricking it. I'm trying to restore it using MSM download tools but I can't seem to get the device detected. I've watched countless YouTube videos, XDA forms, and google and still can't seem to get it to work. I downloaded the drivers, switched it to 9008, tried different OOS downloads, been careful to get the button timing right. None of these things seem to work! Please help!

so your phone was never detected as Qualcomm HS-USB QDLoader 9008?

someone5 said:
I have the T-mobile OnePlus 7t Pro 5G Mclaren edition. I was trying to root it and ended up bricking it. I'm trying to restore it using MSM download tools but I can't seem to get the device detected. I've watched countless YouTube videos, XDA forms, and google and still can't seem to get it to work. I downloaded the drivers, switched it to 9008, tried different OOS downloads, been careful to get the button timing right. None of these things seem to work! Please help!
Click to expand...
Click to collapse
Did you get the bootloader unlocked? Check in the guide section and it has everything there. I'm not doubting your efforts but there's a detailed thread there. If you were able to unlock the bootloader you might be able to flash a rom.

Does adb recognize your device in fastboot?
It's usually driver issue, try downloading your driver from here then reinstall it.
Try changing the cables, a faulty cable can cause this too.

XDHx86 said:
Does adb recognize your device in fastboot?
It's usually driver issue, try downloading your driver from here then reinstall it.
Try changing the cables, a faulty cable can cause this too.
Click to expand...
Click to collapse
I figured it out! Ended up being the dumbest thing lol

someone5 said:
I figured it out! Ended up being the dumbest thing lol
Click to expand...
Click to collapse
I'm assuming it was the cable, glad it worked out then mate.

someone5 said:
I figured it out! Ended up being the dumbest thing lol
Click to expand...
Click to collapse
Hi, do you mind sharing how you solved your issue with msm tool.... i am currently having same issue. please check attachment.

xixtech said:
Hi, do you mind sharing how you solved your issue with msm tool.... i am currently having same issue. please check attachment.
Click to expand...
Click to collapse
First you have to make sure you have the original boot image.
Second when you go to upload it to the phone you have to unplug your PC from the internet and put the calendar date back to December 2018 and then try to upload.
Hope this helps