Database Users

[FIX] Unbrick LG G3 stuck in Qualcomm HS-USB QDLoader 9008 mode

[FIX] Unbrick LG G3 stuck in Qualcomm HS-USB QDLoader 9008 mode
NOTE I HAVE NOT TRIED THIS ON MY LG G3 , But have tried it on the G2. So please understand that I am sharing the method to help any one who is stuck and this tool has the necessary files for the G3 to fix. The difference between the two being , select chipset as B2 (MSM8974AC), rather than the G2 as seen in the screen shots. And also ensure you use the G3 TOT files for your model no. Please DO NOT USE TOT files of any other model number other than what you own
Please ensure you read these instructions a couple of times and ask questions if you have any. I myself paid for some of the tools and got it for the benefit of the community.
If all goes well and I have helped you Donate to me!
If you are stuck in the Super Brick mode of Qualcomm HS-USB QDLoader 9008 mode , this tutorial is for you.
Please NOTE. DO NOT TRY this unlesss you are 100% sure you are in Qualcomm HS-USB QDLoader 9008 mode ,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download BoardDiag3.99c.zip
Extract BoardDiag3.99c.zip , please ensure your antivirus is off during this duration, some antivirus will detect b2b.exe as a virus. Also run b2b in administrator mode
Steps 1 : (Must be done even if you have previously extracted TOT files. This will extract the files with an mbn extension as well as, more importantly it will create a partition.txt which is crucial for this fix to work)
1. Open b2b.exe
2. At the bottom of the application "Image Extraction" Select the path to the TOT file for your Phone model.
3. Select the Dir to any Dir where you would like to extract the files to. (DIR : Selects a folder to save the images extracted from the Tot file.)
4. Click on Extract and wait, this Starts extraction.
5. On completion, “Complete” pop-up appears.
Extracted files :
Step 2: Get ready to flash.
1. On The Top of the tool , select chipset as B2 (MSM8974AC)
2. Select port and set it to the com port where your phone shows up as QDLoader 9008 mode in Device manager, in my case com 10.
3. Set Target Dir to the same path where you just extracted the TOT files from STEP 1 part 3 above.
Step 3: Test AP & EMMC
1. On the Top left of the Tool , select the AP check box and the EMMC check box.
2. Click on Start. This will test your AP and EMMC to ensure your phone can be fixed and there are no other HW issues.
3. Once done it should say pass under test results for AP and EMMC , circled in blue refer below.
Step 4: Test AP , EMMC & SDRAM
1. On the Top left of the Tool , select the AP check box , EMMC check box & SDRAM TEST
2. Click on Start. This will test your AP, EMMC & SDRAM to ensure your phone can be fixed and there are no other HW issues.
3. Once done it should say pass under test results for AP,EMMC & SDRAM circled in blue refer below.
Thats it , if all went well and I have helped you Donate to me! :good:

I had this problem with my lg g3. Wish i had known about this software sooner though as i already sent it to lg for service. However if anyone has any luck with the tmobile variant D851 i am curious if anyone confirms working.

if not ok contact me i unbrick in teamveiwer

AP CHECK Failed
D855 32g sea
View attachment 3008175

appletext01 said:
D855 32g sea
View attachment 3008175
Click to expand...
Click to collapse
Did you execute the exe with Run as Administrator ?

@Kriptonite, it's crazy man, seems like you came just in the exact time I needed this.... I am stuck with a beta Lollipop rom flashed, but I cannot boot to download mode because my current IAF partition is not compatible with my new bootloader...
So , when I boot in download mode, my computer recognises as HS-USB QDLoader 9008..
I want to try this desperately, and be sure I'm gonna donate you very generously after that
But could you drop me a hand here? Any ideas on when /how can I get TOT file from LG 8555 firmware? I only have several KDZ files, but no TOTs...
Thanks!
EDIT: it didn't work
Device was not found in dload trying to flash programmer
TEST aborted!
Tried thousands of times, triple checked everything

tryed
kryptonite said:
Did you execute the exe with Run as Administrator ?
Click to expand...
Click to collapse
Yes , I did but it still not working .

rodrigofd said:
@Kriptonite, it's crazy man, seems like you came just in the exact time I needed this.... I am stuck with a beta Lollipop rom flashed, but I cannot boot to download mode because my current IAF partition is not compatible with my new bootloader...
So , when I boot in download mode, my computer recognises as HS-USB QDLoader 9008..
I want to try this desperately, and be sure I'm gonna donate you very generously after that
But could you drop me a hand here? Any ideas on when /how can I get TOT file from LG 8555 firmware? I only have several KDZ files, but no TOTs...
Thanks!
EDIT: it didn't work
Device was not found in dload trying to flash programmer
TEST aborted!
Tried thousands of times, triple checked everything
Click to expand...
Click to collapse
did you check the com port number?

file hex is bad
hehe tool have file hex is bad .B2 (MSM8974AC) G2 (MSM8974) G2MLTE (MSM8926) 100% dead file hex

kryptonite said:
Did you execute the exe with Run as Administrator ?
Click to expand...
Click to collapse
Ran with admin rights, got the same dload error. willing to try anything to fix my G3 D855.

rodrigofd said:
@Kriptonite, it's crazy man, seems like you came just in the exact time I needed this.... I am stuck with a beta Lollipop rom flashed, but I cannot boot to download mode because my current IAF partition is not compatible with my new bootloader...
So , when I boot in download mode, my computer recognises as HS-USB QDLoader 9008..
I want to try this desperately, and be sure I'm gonna donate you very generously after that
But could you drop me a hand here? Any ideas on when /how can I get TOT file from LG 8555 firmware? I only have several KDZ files, but no TOTs...
Thanks!
EDIT: it didn't work
Device was not found in dload trying to flash programmer
TEST aborted!
Tried thousands of times, triple checked everything
Click to expand...
Click to collapse
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
http://forum.xda-developers.com/showthread.php?t=2785089
Ther you hawe TOT files.

muhamet said:
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
http://forum.xda-developers.com/showthread.php?t=2785089
Ther you hawe TOT files.
Click to expand...
Click to collapse
Thanks very much for your trouble, @muhamet. I've already found the TOT files.
However, it still didn't work .
In the end, I managed, today, to return the phone in warranty, and get a brand new one.. so happy ending at last!

Nice i am hapy for you.Good luck my frend whit new device

AP Check is failing for me too, how to get around it? please help me, I have a brick for the last 2 days and its driving me crazy!!

ngocdiemmobile said:
hehe tool have file hex is bad .B2 (MSM8974AC) G2 (MSM8974) G2MLTE (MSM8926) 100% dead file hex
Click to expand...
Click to collapse
xlnzee said:
Ran with admin rights, got the same dload error. willing to try anything to fix my G3 D855.
Click to expand...
Click to collapse
Skin1980 said:
did you check the com port number?
Click to expand...
Click to collapse
Could you try with the updated version ? Download here

rodrigofd said:
Thanks very much for your trouble, @muhamet. I've already found the TOT files.
However, it still didn't work .
In the end, I managed, today, to return the phone in warranty, and get a brand new one.. so happy ending at last!
Click to expand...
Click to collapse
so happy for you... i tried to solve your problem in the last days but didn't find out anything

kryptonite said:
Did you execute the exe with Run as Administrator ?
Click to expand...
Click to collapse
kryptonite said:
Could you try with the updated version ? Download here
Click to expand...
Click to collapse
when i press volume up and plug in the device it shows under Other devices as "QHSUSB_BULK" in device manager. If I install the qualcomm driver then it shows under Ports (COM & LPT) as "Qualcomm HS-USB QDLoader 9008"
Edit: Tried it with the new version, same error, attached screenshot.

xlnzee said:
when i press volume up and plug in the device it shows under Other devices as "QHSUSB_BULK" in device manager. If I install the qualcomm driver then it shows under Ports (COM & LPT) as "Qualcomm HS-USB QDLoader 9008"
Edit: Tried it with the new version, same error, attached screenshot.
Click to expand...
Click to collapse
any help?

Since you 're going to bring the pieces of rice to share .
So I'm forced to stop services for tool unbrick it , All your efforts are useless.
Do not try to unbrick when I do not allow my friend .
I have stopped all of the data point unbrick tool. You can not unbrick was ,
Tool will report did not find DL Download
. Remember to celebrate : I'm not going to bring the share tool .

tungkick said:
Since you 're going to bring the pieces of rice to share .
So I'm forced to stop services for tool unbrick it , All your efforts are useless.
Do not try to unbrick when I do not allow my friend .
I have stopped all of the data point unbrick tool. You can not unbrick was ,
Tool will report did not find DL Download
. Remember to celebrate : I'm not going to bring the share tool .
Click to expand...
Click to collapse
@tungkick why don't you share the solution for all to fix , and trust me if they fix it they will donate. Don't sit there asking for money first, its against the rule on XDA.
Take a leap of faith with the community, provide solutions and then happy users will donate if they can and that will be worth far more than when you demand a payment and ridicule the efforts of users who are trying hard to fix their phone.

Fastboot mode not detected by PC

So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?

potemkinbuster said:
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
Click to expand...
Click to collapse
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?

the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.

wulsic said:
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
Click to expand...
Click to collapse
I've tried this, but it takes forever and when it comes back with a response it only says (ERROR TOO MANY LINKS), which makes the use of fastboot commands useless
albatron34 said:
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
Click to expand...
Click to collapse
I wishi I could make it get into download mode xP

Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!

potemkinbuster said:
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
Click to expand...
Click to collapse
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb

I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.

wulsic said:
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
Click to expand...
Click to collapse
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either

Godra said:
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
Click to expand...
Click to collapse
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...

potemkinbuster said:
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Click to expand...
Click to collapse
so it partly like works, perhaps you can still get it to work but else you must do the hardbrick fix method from general. I can't say much other things how you could fix it if fastboot mode doesn't work recovery not then you must use that.

potemkinbuster said:
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
Click to expand...
Click to collapse
Yeah, its a bit tricky when doing it first time but its not that hard. I used this tutorial to open phone and short those capacitors. You just have to remove almost all conectors (but camera one) and remove everything to get to SoC.

I did try to shorten capacitors and removes all connectors but i suppose to shorten them when i put back connectors exept the battery , the probleme whene i reattach them i can no longer see the capacitors @@

There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.

Godra said:
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Click to expand...
Click to collapse
that small metal piece is the volume boutton , and it seemd that they are not removable

No, there is one bellow it but it might be different in your phone. What version of G2 do you have?

Godra said:
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Click to expand...
Click to collapse
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"

kakashi_senpai said:
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
Click to expand...
Click to collapse
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.

Godra said:
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Click to expand...
Click to collapse
this is a pic from my phone can u please show where to put the wire please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kakashi_senpai said:
this is a pic from my phone can u please show where to put the wire please
Click to expand...
Click to collapse
Well first you need to remove the buttons plate as it's located underneath that. See the images if you don't know what I mean:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
The only video perhaps available I searched through the thread was this:
https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be
It isn't very clear with the unbricking situation but I unbricked my phone using the images too, Just try to read and see the images and you should be able to unbrick it only you need a thin wire kinda not too large. I couldn't find a smaller wire so it took me like 15 minutes to get it unbricked as I also had some fail attempts.

Yes sir thats my probleme , I tryd to remove the buttons plates but they are stuck with both side , in the video u gave , they are separated
---------- Post added at 10:59 PM ---------- Previous post was at 10:04 PM ----------
well i succeeded to remove button plate , and my device was read as bulk mode. and now i reattached battery and unplug usb connector, now i put back buttons ? and plug it again or what i do exactly ?

hard bricked a6000..

Okay , i dont know what really happened but.. I was running CM12 with custom kernel.. it were fine *for2days* , then there were some annoying bugs with the video and audio playbacks and also wifi.. Before i flashed cm12 i did twrp backup, so i restored it and when i rebooted to system.. the phone didnt seem to turn on. just a black screen and vibrating every 2 seconds. PC doesnt recognize it , i cant get to the boot logo , just vibrating.. I cant go in recovery neither download nor fastboot or anything else.. just vibrating every 2 seconds or less.

edit.. it stopped vibrating when i pulled out the battery for 10mins. now its doing nothing, just black screen. ill charge it for several hours and try again

smirnofz951 said:
edit.. it stopped vibrating when i pulled out the battery for 10mins. now its doing nothing, just black screen. ill charge it for several hours and try again
Click to expand...
Click to collapse
I think its not possible to revive your Lenovo A6000.
I too had a similar experience. The Motherboard of the phone may have have fried .
So I suggest you to visit the Lenovo Service Center & say that the phone doesn't turn ON after you updated to the new update version.
Say nothing about rooting or your custom ROM.
I hope you are still under warranty & they will probably repair it for Free. Also Enquire abt the charges if any.

Qualcomm Hs USB Qdloader 9008 (or 9006) mode
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you

kartixda said:
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
I tried everything. But when i connect my phone to PC its just vibrating , its not recognized by pc.. Vibrating in different intervals, sometimes stops for a 5 - 10 seconds. I dont know what really happened to that phone. I just restored my twrp backup, rebooted and thats it... It cant be hardware issue.

averagegeek said:
I think its not possible to revive your Lenovo A6000.
I too had a similar experience. The Motherboard of the phone may have have fried .
So I suggest you to visit the Lenovo Service Center & say that the phone doesn't turn ON after you updated to the new update version.
Say nothing about rooting or your custom ROM.
I hope you are still under warranty & they will probably repair it for Free. Also Enquire abt the charges if any.
Click to expand...
Click to collapse
Yea i'm under warranty , ill go tomorrow and see what they will do.

Are u able to go into fastboot mode by pressing power + volume down .If yes then it is very easy to recover!

smirnofz951 said:
Yea i'm under warranty , ill go tomorrow and see what they will do.
Click to expand...
Click to collapse
Let me know what they said
Sent from my Lenovo A6000/Plus using Tapatalk

Sourav_8434 said:
Are u able to go into fastboot mode by pressing power + volume down .If yes then it is very easy to recover!
Click to expand...
Click to collapse
Its not going into fastboot mode. Just vibrating in intervals.

averagegeek said:
Let me know what they said
Sent from my Lenovo A6000/Plus using Tapatalk
Click to expand...
Click to collapse
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?

smirnofz951 said:
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?
Click to expand...
Click to collapse
I think they dont

Sourav_8434 said:
I think they dont
Click to expand...
Click to collapse
Thanks for supporting, ill let you guys know if something happen.

smirnofz951 said:
So , i went to Lenovo's service center and as u said i told them that it happened after an OTA update. They told me that its software issue and will fix it soon. Can they understand that it have been rooted and flashed with custom ROM ? Before it died I flashed back the stock kitkat rom but the recovery is still twrp. And if so, will they charge me for that?
Click to expand...
Click to collapse
I hope they don't. Probably they will replace the Motherboard .
I also had the same issue as yours. I told the same as you did & they haven't charged for me.
I expect that even if they found out ,they will probably ignore it

its recognizd what i should donow

Okay , the phone came back. For first 3 days it was in Sofia,Bulgaria and they didn't found out why its not booting. Then, they texted me that the phone is shipped to India ( i dont really know why ). 10 days later the phone arrived here with changed motherboard. They did not charged me and my warranty is still alive. I'm fully sure that its software issue , really don't know whats the point of changing mobo. Anyway , thanks for supporting.
Lol lol lol just booted in recovery and its still twrp .. how its possible when they said its changed mobo

Help ME!! Bricked my Lenovo A6000 plus
kartixda said:
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
I too have the same problem.The device is completely gone black but responds to power button.My PC detects Qualcomm Usb drivers 9008 .I tried flashing the stock rom but it is taking sooo long and does not finish flashing.{I even kept it overnight to flash}.Please help me recover my phone.

PLease Help
Hello,
I tried flashing the stock rom of a6000+ using twrp but after that my phone got bricked.
i am not able to boot in recovery mode. My device is not getting recognized in adb.
in the device manager section it show TP-Link Android Device->Android Bootloader Interface.
Please Help Me Unbrick My Phone.
the phone just restarts itself even if it is connected to computer.
email:[email protected]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kartixda said:
Qualcomm Hs USB Qdloader 9008 (or 9006) mode
Hello friend your phone can be recovered. First, try doing this step by step:
I hope you are using Windows Os on PC
1. remove battery from your device (wait for atleast 5 seconds)
2. download Qualcomm Hs Usb drivers, install and resart your PC ( if you want help fetching drivers let me know I'm not allowed to post links here)
3. Open device manager form control panel
3. insert battery and connect the phone to your pc via USB ( I recommend USB 2.0 port) without pressing any buttons.
4. check if your device is detected and listed as qualcomm Hs USB qdloader 9008 (or 9006) in device manager under Ports
5. if showing your phone has life and it is recoverable for sure
6 if not showing repeat step 1 and 3 but, this time press and hold volume up + power button while connecting the phone to your computer
reply here and let me know if your device is showing as qdloader 9008 (or 9006) mode or not
Happy to help you
Click to expand...
Click to collapse
hello, I have a bricked A6000, maybe you can help...
now it is shown as qualcomm Hs USB qdloader 9008 in device manager. what should i do next?

Lg g3 auto-rec "hard brick" fix

Hello everyone, first let me give major props to my man @bender_007 for creating the amazing LG G Series Autorec Apps which make installing TWRP on LG G Devices a simple process and for also helping me and others who ignorantly misused his app, thanks B!
Anyway recently I bought a LG G3 on Verizon that was on 35b 5.1.1 Lollipop and I rooted. Boy was I eager to get some TWRP poppin on this beast, however flashing TWRP thru Flashify and TWRP Manager left me unsuccessful giving me Secure Booting Error. So desperate I seen Autorec on the Play Store, installed immediately. From there I went through the app's proccesses and from there attempted to boot into recovery hoping for some success.... I did not realize this was went for 24b 5.0.1 until it was late, I mean hey he says it in the description. The phone was dead it wouldn't show anything on the display when I held the power button and it only vibrated, I was f***ed.... At least that is what I thought. I used the method below that me and @bender_007 were collaborating upon as he tried to help me. So please give him credit. I cannot guarantee this will work for you but it worked for me and you don't have to worry about opening up your phone and shorting pins, that nonsense if this works for you.
MATERIALS
A FUNCTIONAL COMPUTER (PREFERABLY WINDOWS, I USED WINDOWS 7)
LG FLASH TOOL 2014: http://www.mediafire.com/?fwrcd3pdj0svjtb
LG DRIVERS-
UNIVERSAL: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
VERIZON:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427
THE LATEST KDZ FOR YOUR PHONE MODEL (GOOGLE IT)
Your Dead but Still Amazing LG G3 and a USB Cable
Note: IF DONE PROPERLY YOU WILL STILL HAVE ALL YOUR EXSISTING DATA PRE-BRICK
PROCEDURE
1. Gather all materials, and know the locations of all your downloaded files.
2. Install the drivers for your phone.
3. Unzip LGFlashTool_2014.zip
4. Move the .KDZ you should've downloaded to the LGFLASHTOOL_2014 folder.
5. Open Device Manager (press start, type in Device Manager into search bar, hit enter)
6. Click View, "Show Hidden Devices"
7. PLUG in USB CABLE TO COMPUTER ONLY!
8. THIS STEP IS VERY VERY VERY IMPORTANT! TAKE THE BATTERY OUT OF YOUR LG G3. PUT IT BACK IN. CLOSE THE BACK. HOLD VOLUME UP ONLY, WHILE HOLDING POWER UP DO NOT LET GO PLUG IN OTHER HALF OF USB CABLE INTO PHONE. KEEP HOLDING VOLUME UP FOR 20 SECONDS. YOURE PHONES SCREEN WILL STILL BE BLACK AND IT SHOULDVE VIBRATED ABOUT 2 SECONDS AFTER YOU PLUGGED IN WIRE (You'll know when you do it right when COMPUTER says installing drivers in bottom right corner.)
9. In Device Manager under Modems there should be something like LGandroidNET I DONT REMEMBER EXACTLY THIS IS ALL OFF THE TOP OF MY HEAD. Anyway, if it says that then you are good, believe it or not your in download mode. (IF YOU DO NOT SEE THIS REPEAT STEP 8)
10. Go to LGFlashTool_2014 folder and run the LGFlashTool2014.exe application.
11. Change PhoneMode to Emergency
12. For "SELECT KDZ FILE" open the folder of the the FlashTool, it should be on it by default and pick the KDZ file.
13. Click "Normal Flash"
14. On the next SCREEN click "START" at the bottom
15. Now there should be a pop-up that says "Select Country & Language" Do not mess with this, just click "OK"
16. There should be a SCREEN now that has a % or whatever... From HERE TO THE END OF IT DO NOT UNPLUG YOUR PHONE!!!
17. When you hit like 85% your phone will boot up do not UNPLUG still and once it hits 100% your done! Safe to UNPLUG and YOU FIXED YOUR PHONE!!!!!!
If you have any questions please ask I have pure empathy for anyone who goes through this hell.

The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?

wombatthing said:
The first time I attempted to connect the phone I successfully had the phone under the modem tab. After being unable to find a .KDZ file (after a minute of searching) I stupidly tried another approach. Now after that not cooperating, I came back to attempt this again after finding a .KDZ file and am unable to set up the device properly to show under the modem tab. I'm following your instructions exactly and gave no luck. Any idea why this would be happening?
Click to expand...
Click to collapse
Okay I'm here to provide my best assistance and for that you'll have to answer a few questions?
1. What is your device model? ex. VS985 Verizon
2. What KDZ did you attempt to flash? ex. VS98547a_01.kdz
Looking forward to your reply.
Sent from my VS985 4G using Tapatalk

@wombatthing I would go to device manager go to view "Show Hidden devices" then disconnect your phone take out battery put it back in close back then hold volume up for 20 SECONDS while doing that connect to computer. It probably won't say installing drivers because you said it worked the First time, from there see if it's under Modems. Good luck my friend in here for any questions
Sent from my VS985 4G using Tapatalk

Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks

Ray1000 said:
Will this method keep all my files that were stored in the internal memory? I'm not worried about the device, i just want my files! Camera pictures etc.
Edit. I tried it but in DIAG mode because i'm afraid emergency can delete my files? I can see the "LGandroidNET " but no vibration and seems like the driivers never install properly. My phone is completely dead.
@bender_007 @OneShotGoGetter
Thanks
Click to expand...
Click to collapse
My friend all is good. First of all as long as it says LGandroidnet you are good you should be in download mode, in lg flash took for mode click emergency and not diag then click normal flash THIS WILL KEEP YOURE DATA IF YOU SEE CRS FLASH OR SOMETHING LIKE THAT THEN ITLL RESET YOURE PHONE just do Emergency and Normal Flash and it should work. Hope I help if you have questions please ask.

@Ray1000 "Emergency" Mode is just Download Mode flashing. Diag is not that's why you were unsuccessful.

Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00

For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64

mackleroar said:
Thanks for this! I'm getting stuck at the end (step 16) when the flash tool says:
"Problem with communication between cell phone and PC.
Please disconnect the cable from your cell phone in order and remove and connect the battery. Power on your cell phone and press the Restart button to resume update. If LG Support Tool is stopped abnormally, try with [Options]-[Upgrade Recovery] in tool menu."
I've tried just clicking the retry button, and also unplugging the phone and putting it in recovery mode again before clicking retry. Neither has worked so far. Any thoughts?
Phone is D855, kdz version is D855V20b_00
Click to expand...
Click to collapse
Sorry for the late response. First of all you are welcome. I don't know if you fixed the problem yet but I'll help anyway. First remove youre battery for at least 10 seconds then put battery in, hold up and connect charger for 20 seconds. Of you are unsuccessful try reinstalling drivers. Best of luck my friend.
Sent from my VS985 4G using Tapatalk

Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!

Perezvon said:
Hi, I have tried your method but get stuck on "Problem with communication..." Is this a problem specific to windows 10?
I have attempted to update the Qualcomm HS-USB QDloader 9008 but cannot see it in device manager.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Im having the same problem!!!!!! I've tried everything. I will let you know if I fix it and please let me know if you get your's running?

Does anyone know if this method will work for the Sprint LS990 variant? I too had my phone broke by autorec and I lost download bit have access to TWRP and can flash roms but can't do a factory reset with the LG Flash Tool.
Sent from my LG-ls990 using Tapatalk

Failed to flash
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!

i also cannot find the Qualcomm's driver on windows 10 & phone looses communication with flash tool..

vajee555 said:
Hi,
Thank you for this post. But unfortunately I can not get back my device. What happened was I bricked my phone while flashing TWRP. It's a G3 D855 and does not power on at all. Screen is blank, no LED or vibrate. I tried volume up/down combinations with power button but nothing happens. However when I connect it to PC, device manager shows it under Modem and COM ports.
I tried to flash a stock ROM using your method. But I got following error during process.
The only problem was phone did not vibrate when I connect it as you mentioned.
Do you think my phone is gone forever? Is there any other way? Appreciate a reply.
Thanks!
Click to expand...
Click to collapse
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me

ayarihime said:
the same thing happened to me, just dont close the error notification and move it to the side, so you can see the cellphone is upgrading, dont close the error message until your cellphone boots, this worked for me
Click to expand...
Click to collapse
Hello. I managed to get my device to work. Flashed a stock MM rom and now stucked with damn Mcfee kill switch. Can not go to download mode either . Any idea how to fix this? Thanks!

Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC

mjmaxint said:
Hi how did you manage to fix it @vagee555? I am receiving the same error message: Problem with communication between cell phone and PC
Click to expand...
Click to collapse
Hello, I had to short some other two pins to get it identified by my PC. The pins mentioned it this post did not work for me. Follow the link given below and it will work for you. Thank me later.
http://forum.gsmhosting.com/vbb/f494/how-hard-unbricked-lg-g3-all-variants-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/

He guys thank you very much. My LG3 was already down for months after many failed attempts and I was about to bin it. Decided to give it one last try, found your instructions and it works, I now have Marshmallow!! (However I downloaded the KDZ file from "downloadmirror.de" and I am not sure if that was a good idea.

Pixel 4 EDL

Most of the EDL related posts I've found are in relation to the Pixel 3. Since I've now encountered the EDL issue with my Pixel 4, and there doesn't seem to be a place for it yet, figured I'd get one started here.
There's nothing I can point to that could have caused the issue. Phone was working fine when I went to bed, and when I woke up, it had become a brick overnight. Restarting didn't help at all. Phone remains in EDL, confirmed by connecting to my PC. I was running the Android 12 Beta, though I don't believe it to be a contributing factor.
I'm assuming a catastrophic hardware failure at this point.

Have you already tried using the Pixel Repair Tool? It was specifically designed to work with Rescue Mode which is similar to EDL. Maybe a reflash is necessary.

V0latyle said:
Have you already tried using the Pixel Repair Tool? It was specifically designed to work with Rescue Mode which is similar to EDL. Maybe a reflash is necessary.
Click to expand...
Click to collapse
You need to have access to the Recovery Menu to be able to use the Pixel Repair Tool, specifically entering the Recovery mode. EDL is not the same.

@Amon Darthir are you able to get into bootloader? Hold volume down, then hold power button until phone restarts.
Is your bootloader unlocked? I'd try using the Android Flash tool and reflash all partitions.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

V0latyle said:
@Amon Darthir are you able to get into bootloader? Hold volume down, then hold power button until phone restarts.
Is your bootloader unlocked? I'd try using the Android Flash tool and reflash all partitions.
Click to expand...
Click to collapse
Like Jojo said, EDL is not the same. The EDL is a layer BELOW the what we know as the bootloader. This is the bootloaders bootloader. If you are booting to the EDL, it's because the bootloader is likely corrupted. You can't boot to Fastboot, or what you'd think of as the normal Bootloader.
Essentially, without being Qualcomm, there's nothing you can do. (Unless you want to replace your main board for ~$450).
The issue is being tracked here, but support from Google is nearly non-existent.

Amon Darthir said:
Like Jojo said, EDL is not the same. The EDL is a layer BELOW the what we know as the bootloader. This is the bootloaders bootloader. If you are booting to the EDL, it's because the bootloader is likely corrupted. You can't boot to Fastboot, or what you'd think of as the normal Bootloader.
Essentially, without being Qualcomm, there's nothing you can do. (Unless you want to replace your main board for ~$450).
The issue is being tracked here, but support from Google is nearly non-existent.
Click to expand...
Click to collapse
I see, thanks

Hey!
I am glad I came up to this as I believe I may have a solution for you guys!!!!
V0latyle said:
I see, thanks
Click to expand...
Click to collapse

*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode(like QFIL).
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.

So these are some of my posts for some folks which had same problem, phone stuck at 9008 mode.
I have a lot of interest on this because I am working on a way to unlock any Google Pixel form it's career(which I already did), including the boot loader(which I am currently working on).
I am posting all of that on the Pixel 4 XL forums though.
The situation is this:
EDL mode is like a recovery mode which is available on any Qualcomm device, and it's the primary bootloader.
When the phone boots, it triggers the secondary bootloader(which is the one carriers lock, and it's this one you usually unlock when you want to flash stuff to your phone, like TWRP).
The idea behind this mode is to allow devs to use this to force flash firmware to get the device back and running in case Fastboot and ADB weren't available(basically, to solve the problem you guys are having).
In my case this is useful because I can use it to flash the unlocked firmware from Google and them unlock my phone (my phone is working perfectly on Android 12), and them flash stuff to it.
So if any of you guys try this, let me know how it went!

#mcl said:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode(like QFIL).
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
Click to expand...
Click to collapse
I no longer have my device, as I was able to wallop Google Support enough over the issue that they agreed to RMA the device, however, I'm curious how this would actually work.
The device only boots to EDL, so ADB isn't an option, neither is Fastboot. From what I've seen and understand, without a proper Firehose file, and an image from Qualcomm or Google themselves, there's basically no way to flash the device back to a working state (assuming it even can be).
Are there actual FULL Pixel images available, with bootloader and Android? (They sound to be packaged together). This would seem to be a very serious set of files to have out in the wild... (Which is part of the problem. No one has been able to find those images, otherwise, many would have tried using QPST already)

Amon Darthir said:
I no longer have my device, as I was able to wallop Google Support enough over the issue that they agreed to RMA the device, however, I'm curious how this would actually work.
The device only boots to EDL, so ADB isn't an option, neither is Fastboot. From what I've seen and understand, without a proper Firehose file, and an image from Qualcomm or Google themselves, there's basically no way to flash the device back to a working state (assuming it even can be).
Are there actual FULL Pixel images available, with bootloader and Android? (They sound to be packaged together). This would seem to be a very serious set of files to have out in the wild... (Which is part of the problem. No one has been able to find those images, otherwise, many would have tried using QPST already)
Click to expand...
Click to collapse
So let me explain.
From what I know you can download the firmware directly from Google from here.
For the firehose file, it's the one I send on 2 message. If you open Qualcomm QPST tool, and go to the download menu you will find a place to insert the phone image, though you can only put an image with an specific file system, the same as the files I shared. From what I saw on the web, you just need to flash that file.
If you use QFIL however, you will need and XML file as well.
I believe they are the firmware/Firehose files but I am not sure.

The IssueTracker updated today, with what appears to be an official response from Google:
"This issue occurred due to the natural lifecycle of a memory component. Memory components have a predefined lifecycle based on consumer use cases over time. The recommended solution is an out of warranty repair or replacement..."
Click to expand...
Click to collapse
So we now know that the issue is indeed a hardware fault, and that it is a fault in one of the memory components as suspected.
What's curious still is that these devices are encountering this issue, while much older devices continue to work. Wonder what the difference is.

Amon Darthir said:
The IssueTracker updated today, with what appears to be an official response from Google:
So we now know that the issue is indeed a hardware fault, and that it is a fault in one of the memory components as suspected.
What's curious still is that these devices are encountering this issue, while much older devices continue to work. Wonder what the difference is.
Click to expand...
Click to collapse
Hey!
That's a possible case, though I don't believe that for a few reasons:
1) Even though some components are consumable(like battery and SSD), RAM isn't one of them.
2) For a RAM to fail there is usually a cause, like working on extremely high frequencies, high temperatures and so on which obviously doesn't happen on a phone unless you leave it burning under the sun.
3) How many cases of faulty RAM modules did you see on the web, I didn't see any yet(at least not on phones)
So unless the user overheated its phone or drop it from an airplane XD, it seems to be a hard excuse for the problem.
I don't believe that there is a hardware failure, but I am not a phone engineer so I can't guarantee.
Anyway, if someone finds the cause please let me know

#mcl said:
Hey!
That's a possible case, though I don't believe that for a few reasons:
1) Even though some components are consumable(like battery and SSD), RAM isn't one of them.
2) For a RAM to fail there is usually a cause, like working on extremely high frequencies, high temperatures and so on which obviously doesn't happen on a phone unless you leave it burning under the sun.
3) How many cases of faulty RAM modules did you see on the web, I didn't see any yet(at least not on phones)
So unless the user overheated its phone or drop it from an airplane XD, it seems to be a hard excuse for the problem.
I don't believe that there is a hardware failure, but I am not a phone engineer so I can't guarantee.
Anyway, if someone finds the cause please let me know
Click to expand...
Click to collapse
Never said it was the RAM. It's likely the memory component that the bootloader is on, which is part of what has been speculated. I doubt my "memory component" the only thing they were referring to was RAM.

Amon Darthir said:
Never said it was the RAM. It's likely the memory component that the bootloader is on, which is part of what has been speculated. I doubt my "memory component" the only thing they were referring to was RAM.
Click to expand...
Click to collapse
The bootloader is on the SSD of the phone I think, and it doesn't fail as well, at least no so often...

#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
Sorry for bumping this old thread.
Like quite a few other reports I could find on the Internet, my Pixel 4 XL bricked itself overnight as well...Happy to come across your posts and interested in trying these files out.
Right now I can confirm that my phone is stuck in the EDL mode as I can see "QUALCOMM HS-USB QDLOADER 9008 COMx" in Device Manager when connected to a Windows computer, and I do see the phone in QPST Configuration, that says something like "QCP-XXX Sahara download".
However, unlike most QPST tutorials I found online (including the one you posted), the port status in QPST Configuration does not say "Enabled", but rather showing a half-way green progress bar all the time. I've tried to wait for about one hour just in case, and reinstalling the Qualcomm driver, restarting the computer etc. but nothing changed.
And if I just ignored that and go straight to flashing anyway, I couldn't get it to work with the MDN files you posted. QFIL would need a .xml file which is not included. Software Download reports an error message of "could not open the programmer file" (by this I was using the EU/.../pixel_free one).
Not sure what does it mean by "could not open" - is it the .mdn file is invalid, or it's just not the right file for this particular phone?

I suppose nobody has been able to use what @#mcl has posted back in 2021 to work? And the natural lifecycle of a memory component is only 3 years? That sucks.

Hi!
Yeah unfortunately there is close to nothing about this, probably because it's very low-level programming, and for security and economical reason Qualcomm won't share this kind of information. Only someone that work inside Qualcomm may have access to the needed files and documentation.
ObsidianTheRed said:
I wanted to confirm that removing com.google.android.apps.work.oobconfig as detailed in mcl's original post worked on a Verizon carrier-locked Pixel 5. Awesome!
Click to expand...
Click to collapse
bodayw said:
Sorry for bumping this old thread.
Like quite a few other reports I could find on the Internet, my Pixel 4 XL bricked itself overnight as well...Happy to come across your posts and interested in trying these files out.
Right now I can confirm that my phone is stuck in the EDL mode as I can see "QUALCOMM HS-USB QDLOADER 9008 COMx" in Device Manager when connected to a Windows computer, and I do see the phone in QPST Configuration, that says something like "QCP-XXX Sahara download".
However, unlike most QPST tutorials I found online (including the one you posted), the port status in QPST Configuration does not say "Enabled", but rather showing a half-way green progress bar all the time. I've tried to wait for about one hour just in case, and reinstalling the Qualcomm driver, restarting the computer etc. but nothing changed.
And if I just ignored that and go straight to flashing anyway, I couldn't get it to work with the MDN files you posted. QFIL would need a .xml file which is not included. Software Download reports an error message of "could not open the programmer file" (by this I was using the EU/.../pixel_free one).
Not sure what does it mean by "could not open" - is it the .mdn file is invalid, or it's just not the right file for this particular phone?
Click to expand...
Click to collapse
I still didn't gave up on any of the projects (the EDL thing and the unlock SIM & Booloader), but due to high complexity of those projects, the fact that I have a quite busy life which leaves me with very little time to bring live to these projects and that I am basically alone, means they will probably take some time.
Maybe try searching using different search engines, and try being very specific like "MBN file pixel 4".
Hope you find a solution to your problem!