Develop Bugs

Bricked LG G3 - Need help!

Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.

Walshinho said:
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Click to expand...
Click to collapse
can you post
the guide that you used to root
your phone variant
and whether it boots into download mode
what firmware version you were running

the guide i followed was this (exactly) http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
i have a UK D855
I can get it to download mode (but cant get to recovery with the power and down buttons)
unsure exactly which firmware, i hadn't played around with the phone until this happened.
when i let the phone get stuck on the lg page the windows pc seems to recognise the device, if i put it in download mode it comes up with the device error that it is there but cannot be run.
Thanks.

You probably have either
1) A bad usb cable
2) Or your drivers arent properly installed
You are plugging it into a USB2.0 port right?

I installed the drivers from the universal LG driver tool from their site, it worked find with the phone (or so it showed) before this issue, i've also tried a different cable and a different machine for it to come up with that same driver problem (10). Ive also tried uninstalling the driver software and reinstalling, is there a way to get rid of all traces of the bad drivers? thanks again for replying

Error Image
{
"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"
}

Working Fine
This is when the device isn't put into download mode and instead is left to try and boot (where it is stuck on the LG 'life's good' page).

Any idea guys? Im having no luck with any info im getting online at the moment and i'm really in need of this phone to work.
Thanks in advance.

Can you expand the "android device" section.
See if it's android adb

sorry, i think i quite understand. Which part should i expand on?
Thanks

In
device manager, look up Android device.

Update
The phone will now only go straight to firmware update and will never go or show the download mode as it has before. This is causing my LG Flash Tool to come up with 'cant change to download mode' and im not sure why or how this has happened.

The phone is now appearing fine on the device list. Its just the last of download mode. Is there a way to force it in cmd?

Please some screenshot again. The one I linked would be fine for adb

I see you can boot on download mode, so you can restore your G3 by applying a kdz firmware with flashtool2014: http://forum.xda-developers.com/showthread.php?t=2785089
On download mode the G3 is recognized only in ports (com&lpt)

I bricked my G4 H812. No download mode, nothing on screen, only QHSUSB__BULK.

So I messed up flashing the rooted system.img:
Code:
dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
I used skip instead of seek
{
"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"
}
so I've wiped out the partition table and pretty much everything.
The good news is I have a backup of the entire /dev/block/mmcblk0 that I made before attempting to modify anything, so hopefully it's possible to recover, if I knew how...
When plugging the cable in, the phone appears as QHSUSB__BULK device in Windows, and "qcserial ttyUSB0: Qualcomm USB modem converter" in Linux. Otherwise, nothing happens. Whether I have battery/SD card inserted or not, holding volume up or any other buttons, there's no response at all. Blank screen, no LED, no vibrate, it does absolutely nothing. The only thing it will do is reconnect if I hold the power button for several seconds. fastboot.exe doesn't detect any devices. Windows device manager doesn't list any disks except the computer's actual hard drive.
I'm sure there must be some way to recover it using this QHSUSB__BULK mode, but I haven't found anything.

I'm in the same boat as you, but with H815. With proper drivers your device will be recognized as a Qualcomm 9008, I think. I have very heavily researched this, and unfortunately, there is no available way to recover. For G2 and G3, there was a tool called BoardDiag. Perhaps this will at some point be made compatible with G4.

I've heard about these drivers and BoardDiag but haven't found them. Maybe tomorrow I'll look for them more... otherwise I can probably take it to the shop under warranty, but I worry they'll give me back a new one with a new firmware and I'll have to wait for another root exploit... :|

Silly question that won't help you fix your problem but... Why did you type out that? Why not just copy paste?
Sent from my Nexus 7 using Tapatalk

Try this no promises
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142

tobesedated said:
I did the same thing with my G2 and followed this guide to restoring it.. It may work for the G4 as well if you have or can get the image files for your device...
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!

RenaKunisaki said:
No good. I don't get any /dev/sd* when I plug it in. Only /dev/ttyUSB0. Unless that serial port somehow is actually a storage device, but that seems unlikely...
Copy/paste would have been a good idea!
Click to expand...
Click to collapse
Stupid question but you are using linux to try this right? I don't know that it will work in Windows

Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...

RenaKunisaki said:
Yes, I'm using Linux, and I also have a Win7 box to play with.
Anyway I took it in for repair under warranty, so just have to hope there's no problem...
Click to expand...
Click to collapse
lemme know how that goes, im sitting on a brick too. i just figured id wait a few weeks see if any fixes pop up before i send back to lg. i meant to zero out laf.img to access fastboot mode to try oem unlock on ls991, but im a dummy and got way in over my head and deleted aboot by accident. my windows xp netbook doesn't even see a qualcomm device. i havent tried on the raspberry pi yet. the only response i can get from the phone is a battery symbol with a ? , and onlyif i plug in usb from pc with no battery in the phone

Yeah, I heard some people wouldn't get the Qualcomm device popup, but would get the question mark battery icon. For me it was the opposite; the device shows up (as QHSUSB__BULK in Windows and ttyUSB0 in Linux) but absolutely nothing on the screen no matter what I do.
My guess is because some people only wiped out laf or aboot or a couple other things that are used later in the boot process (so it will boot, but fail quickly when it can't find them), whereas I wiped out the entire partition table, so the very first step fails; probably the hardware itself (the modem, CPU, or who knows), upon not finding a bootable partition, goes into some backup mode where it can be flashed over USB. (Just nobody seems to know how to flash it from there...) Or the very first sectors of the MMC contain the actual stage 1 bootloader (I noticed partition 1 starts at sector 32768, so some 16MB at the beginning is unaccounted for), and that code is responsible for disabling the QHSUSB__BULK mode, but having wiped out even that, it stays enabled. (Possibly another way for root/unlock if someone examined it closer...)

Yeah no easy way you need a direct flashing eMMC tool

I'm guessing no one managed to fix their brick? Same thing happened to me after attempting to revert to an earlier version bootstack.zip.
From my reading of G3 unbricking, the attempted-downgrade flag got tripped and so it's in the same 9008 state. Without access to the LG supplied .mbn files, there's no way to do any sort of fix. i.e. this problem could be easily fixable, just not by anyone without LG tech tools.

Contact @vn_mobile

Has a system image been posted? I'm kinda in the same boat...

dd if=/data/media/0/system.rooted.img bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
mean 3955228672 byte (~ 3.9GB) of eMMC (mmblk0) is CLEAR
If can go to my country i can recovery for you or

Hi,
Read this web pages.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
http://www.androidbrick.com/lg-g3-hs-usb-qdloader-9008-unbrick/
http://www.androidbrick.com/unbrick...oader-9008-if-you-have-the-right-kind-of-rom/

Looking at some of the other posts on here, I think the only thing to do at this point is hope you still have warranty.
(Not really sure how I'll fare though, I just got this one as a replacement for a bootlooping G4 yesterday)

I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay

xxxwalo said:
I did the same thing to my g4... I still can't find any solutions to unbrick it. Luckily I found another one on craigslist for cheap so I went ahead and bought it... Not ****ing around with it though I learned my lesson the hard way ... At the mean time I'll probably end up selling my bricked one for parts on ebay
Click to expand...
Click to collapse
This phone isnt even a year old yet... why would you buy another instead of sending it off to LG for Warranty repair. There are a lot of these that have bricked from OTA update.

If someone simply post the AP Chipset driver for BoardDiag.exe to start, it will be solved....
I solve my G3 with BoardDiag.exe and flashing all original image partition extracted from TOT file.... But I can't find any AP CHipset that support G4 yet.

G4 H815 UK version - sudden death

Hi guys,
You helped a lot recently, but now I am totally puzzled by behaviour of my LG G4. All was good, till I had to put another sim card in it (it was Lyca UK with 2x mobile numbers assigned). Most of them time it was not recognising the car. Suddenly yesterday night in hotel it rebooted and stopped on LG logo. After a while I pulled out battery and since, I have all sorts of random problems
1) It will boot only to first Lg logo then hang on it, or
2) It will boot to second LG logo and will flash LED in left top corner or
3) Most of the time (8 out of 10) will not start at all
4) Once it went back to system then froze when I unlocked screen
5) Power + volume down doesnt work (too early in bootloop to enter TWRP?)
6) LG UP won't start - laptop doesn't see it
I can freeze it or bake it but I'm driving long distance and I need satnav which I have in that phone.
Do you have any ideas please ? adb, or fastboot? of LGUP or anything else ?

birkopf said:
Do you have any ideas please ? adb, or fastboot? of LGUP or anything else ?
Click to expand...
Click to collapse
A (very hopeful) fix that sometimes works for me is to remove the battery and hold the power button for a few seconds. Then re-insert the battery and turn it on as normal and then be patient. If you get to the second LG bootscreen, does the auto brightness dim the screen when you're in the dark?
If you've lost hope and are ready to spend a few hours trying to re-flash (with no promise of success). Try the following:
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGMobileDriver_WHQL_Ver_4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product-help/CT10000025-1438110404543-preinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
Failing that, try this method: https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848

Hey hrt5!
Thank you so much for detailed explanation. I was moving apartment and had no chance to come around to it, but I did yesterday.
My G4 is very temperamental. Once it will enter download mode... once it won't. Countless battery pulls. I never managed to fully follow your guide because it will always reboot or go blank after I click software update. However in download mode I started LGUP and 50% of procedure went fine, then it rebooted showing error which I attached. Now I will try to start LGUP again and use second option (I believe refurbish) while obviously still trying your method.
https://s23.postimg.org/anw0ynsaz/lg_up.png
{
"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"
}
adb and fasboot still wont show device - it hangs or reboots before it will be detected.
What could cause such damage or software issue ? Phone was dry, was in hotel room, no shock, nothing. I just changed sim card.

Welcome to the bootlooped LG G4 family. However sad that would be it looks like the way to have it repaired is to send to LG if it is still under warranty to have motherboard replaced. SBA is the company that is registered as LG repair center. I would suggest to be very patient if you go through official repair as it might take weeks or even months to have yours fixed (you can read all the horror stories online). If you have phone insurance try going through insurance as that would be quicker or go through the supplier that you bought from.
Please read numerous threads on bootloop of LG G4. Also if you have nothing to lose then you can try freezing or heat gun methods to at least run your phone temporarily to recover data if you haven't backed it up.

On a more positive note mine was repaired under warranty by SBE via LG in under Week.

I don't think I have warranty, I bought from eBay. Also - I just moved abroad. Today I managed to go to 86% of reflash but if motherboard is bugged, it probably won't do much difference even if I succeed... Could you be so mind and add to this post or PM me contact details to SBE/SBA? This is amazing - Exactly when I needed it most because I moved to new country, new city when I'm looking for apartment and I'm not familiar with streets, underground, etc. perfect timing for this LG.

Can someone give me contact details to this authorized service ?

birkopf said:
Can someone give me contact details to this authorized service ?
Click to expand...
Click to collapse
go via lg sbe are awful crooks lg dont say but they do have there own service centre even out of warranty they should do it for a cost

Hi guys,
Where I can buy motherboard for G4 H815 ? I have found few of those on ebay for about GBP135 or more.
Authorised Service took my phone, repaired it (placed new motherboard) and then they called me to tell me that phone works fine but it was rooted so I either pay GBP157 for motherboard or they remove the new motherboard and return to me unrepaired... this is super annoying.
Ideally I would want to buy motherboard and replace myself. Sadly I cannot find anything below GBP100 and I'm sure someone has already found some good source

LG-H815T S/N 512xxx won't boot (but not in bootloop) - all stock, no modifications

I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...

Its a hardware issue. They all are.
Every one is its own story but in the end she just wont boot

zeroid said:
I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...
Click to expand...
Click to collapse
If you like give this test a try. I don't know if it works with a defective mainboard but testing costs nothing..
Download FWUL and boot it (https://tinyurl.com/FWULatXDA).
Then go into the download mode on your g4.
Then open the folder LG in FWUL and open a LGlaf shell.
If you see the prompt in a black terminal ok. If not use the other shortcut with auth in its name. You may have to start the LG laf shell 2 or 3 times sometimes...
If you see the black terminal prompt type in the command:
ls
It should give you a list of files and folders. If not there's something wrong.
If you have luck you can then backup your data.
You need an external SD card to store your data.
I have no access to download mode atm but if you want to test this let me know and I can prepare the rest in a day or 2.
.
Sent from my LG-H815 using XDA Labs

Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...

zeroid said:
Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...
Click to expand...
Click to collapse
You can't fix the mainboard issue by your own. The only chance is getting a replacement by LG.
The freezer method is good for a last backup of your files but don't do it often it is not good for your phone.
.
Sent from my LG-H815 using XDA Labs

Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....

zeroid said:
Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....
Click to expand...
Click to collapse
Well then try it with FWUL.
I just need to test the right commands first..
.
Sent from my LG-H815 using XDA Labs

So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.

zeroid said:
So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.
Click to expand...
Click to collapse
Do you have downloaded the latest version? Directly on the desktop?!
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Do you have downloaded the latest version? Directly on the desktop?!
Click to expand...
Click to collapse
I downloaded from the main Androidfilehost link.
Here's the desktop when I boot:
{
"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"
}

Sorry but you haven't downloaded the latest version.
Tbh the sort order by AFH is really misleading and irritating.. so I have just re-ordered the androidfilehost structure so you may find the latest release better now.
The latest one is v1.3 btw.
Go to: https://www.androidfilehost.com/?w=files&flid=142115
Find the folder LATEST
Download FWUL from there
.

OK tried that version, no luck getting the LG LAF terminal window up for the short time the phone stayed in download mode. Even download mode is not stable any more, and just after that it wasn't switching on at all so kind of lost all hope of recovering anything from it now.
Thanks for the link to FWUL - could prove useful in the future.

Possible Brick - Flashing Unlock Not Allowed

I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!

So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?

Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).

I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?

ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.

That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk

ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.

I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"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"
}
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?

Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.

ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.

Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk

I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk

ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?

Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.

ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:

0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk

Aiit.tnx

@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.

SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.