Database Users

How I un-bricked my bricked phone.

A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....

Very nice..

wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?

Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse

mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.

thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.

goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.

goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.

this might be a fix for the haykuro spl bricked users..

Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback

goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.

Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.

imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.

Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?

goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"

A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)

bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!

Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl

wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz

marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info

[Q] Nexus one modem seems busted, bricked?

Hi all,
I've bought a Nexus One from a friend that went to US a while ago (I live in Brazil). My N1 was exhibiting an overheating & reboot issue whenever I used the 3g connection.
2 weeks ago, just after a phone call, it rebooted and did not come back. I took the battery out for the night, but still did not come back.
The bootloader is unlocked, but I was using stock gingerbread. I can get into fastboot, but not recovery. I tried the PASSIMG method a couple of times, and tough the flashing did succeed, the phone keeps stuck at the X logo.
The last radio flash was 5.08, when ginger came. Does this means my device is bricked? To make matters worse, it seems I'm out of warranty...any of you guys have any clue to help me? Or is it all lost and I should get a new phone??
Thanks!

If you're booting - you're not bricked. Brick = NOTHING on the phone, no reaction whatsoever to anything, won't turn on.
Anyway, since you have your bootloader unlocked - fastboot flash recovery recovery.img, and then try to boot into recovery, see if it works. Read the Wiki to help yourself.

Hi Jack, thx for the reply!
I already tried that; the flash succeeds, but I cannot get into recovery. If I try to reboot into recovery, it still gets stuck at the X logo.
I understand that brick == nothing at all; but I suspecting that the GSM modem is history. I was already having rebooting problems with it, and now it seems that it's dead and the phone will not boot because of it. Does this makes sense?

Have you tried "fastboot boot recovery.img"?

danger-rat said:
Have you tried "fastboot boot recovery.img"?
Click to expand...
Click to collapse
Just tried it, the phone reboots, but vibrates 7 times and does not boot, still in the X logo...

7 vibrations - means you have some HW problem, and the phone won't boot. Yes, I guess that even though you're not bricked, the phone isn't usable and needs to be fixed/replaced. Sorry.

That was what I was afraid....I had this "7 vibration" stuff happen before, but I was able to get it back on track...
Thx all for the help, time to get a new gadget

MY LG G2 for verizon is bricked HELLLPPPPP PLEASE

sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains

Im in the same boat
xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.

xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
BAYOUREBEL said:
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
Click to expand...
Click to collapse
DId you not try and go back to stock?...
http://forum.xda-developers.com/showthread.php?t=2432476

xdavelope said:
sorry to bother you all. i bricked my device and it's only a few hours old. I rooted it using the io root method. that was painless.
anyway, it didn't brick then. i got a notification from verizon for the 4.4.2 update so I clicked download update it never installed and that's when the bricking started. Anytime I connect it to the computer it opens up like 40 disks and it says cannot be used unless it's formatted so I have to spend a while canceling those out. when I restart the phone it says the lg logo then the screen goes black . im stuck. i've been trying for hours. if i get the phone back i won't root it or do anything. ill deal with the bloatware, whatever. i've tried a lot of different things but to no avail. any help is appreciated. thank you for your time...and wont go into download mode....help please anyone....
i have no recovery installed....every time i try to cut the phone off it vibrates screen goes off and on showing the lg logo very quickly then goes black but remains on until battery drains
Click to expand...
Click to collapse
If you can't boot into stock recovery (vol down + power key) and can't get into download mode (this is where they detect root once FW update shows up and the bottom left corner says Bootloader: ROOTED) then you can rest assure as long as you are under warranty, send it in to LG directly.
Do not send it to Verizon as you may incur charges for replacement. There's insurance from Verizon, but the real "replace with no charge" warranty is sending it to LG directly. Make an account on their website, register your G2, and make a Repair request by online chat or phone.
I just got my T-mobile G2 back after 2 weeks with the same issues and while it took a while to get repaired, I didn't pay a penny and it works without T-Mobile ever knowing its different hardware (all they replace is the flash memory that is corrupted in the phone).
Only downside is that it came back with KitKat and unrooted which means I have to wait for a working root procedure for it unlike with JB (I'm not afraid to root it again since I know what messed it up before was custom recovery TWRP version 2.6.3.2 that doesn't support KitKat lol).
hyelton said:
DId you not try and go back to stock?...
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
He can't get into download mode which means no KDZ flashing.

MDA400 said:
If you can't boot into stock recovery (vol down + power key) and can't get into download mode (this is where they detect root once FW update shows up and the bottom left corner says Bootloader: ROOTED) then you can rest assure as long as you are under warranty, send it in to LG directly.
Do not send it to Verizon as you may incur charges for replacement. There's insurance from Verizon, but the real "replace with no charge" warranty is sending it to LG directly. Make an account on their website, register your G2, and make a Repair request by online chat or phone.
I just got my T-mobile G2 back after 2 weeks with the same issues and while it took a while to get repaired, I didn't pay a penny and it works without T-Mobile ever knowing its different hardware (all they replace is the flash memory that is corrupted in the phone).
Only downside is that it came back with KitKat and unrooted which means I have to wait for a working root procedure for it unlike with JB (I'm not afraid to root it again since I know what messed it up before was custom recovery TWRP version 2.6.3.2 that doesn't support KitKat lol).
He can't get into download mode which means no KDZ flashing.
Click to expand...
Click to collapse
Not getting into download mode is odd especially for just accepting a OTA update. Remember since they accepted the OTA its gonna take a special way of getting into download mode as the phone will be constantly on in boot loop. not all of the time but most of the time when people say they cant get into bootloader they have to keep trying due to the phone has to be "Turned off" OR rebooted at the same time of holding down the key combo.

hyelton said:
Not getting into download mode is odd especially for just accepting a OTA update. Remember since they accepted the OTA its gonna take a special way of getting into download mode as the phone will be constantly on in boot loop. not all of the time but most of the time when people say they cant get into bootloader they have to keep trying due to the phone has to be "Turned off" OR rebooted at the same time of holding down the key combo.
Click to expand...
Click to collapse
To get the phone to turn off, one has to reboot the phone (power key for 10 seconds) while holding volume up WITHOUT having the USB cable plugged in.
Recovery mode is a bit trickier by having to hold the power key for 10 seconds, then just as the phone reboots, hold PWR + VOL DWN and while holding VOL DWN, release PWR and press it again (gets to that factory reset screen where you press PWR 3 times).
Not trying to teach you this if you already know how, just stating it if the OP looks at this then he can try again with the above.
Also, Download mode is essentially the "bootloader" and it is locked meaning unless you have certified software (KDZ FW updater), you can't adb anything just in download mode unlike some LG phones that have emergency mode which is unlocked bootloader.

MDA400 said:
To get the phone to turn off, one has to reboot the phone (power key for 10 seconds) while holding volume up WITHOUT having the USB cable plugged in.
Recovery mode is a bit trickier by having to hold the power key for 10 seconds, then just as the phone reboots, hold PWR + VOL DWN and while holding VOL DWN, release PWR and press it again (gets to that factory reset screen where you press PWR 3 times).
Not trying to teach you this if you already know how, just stating it if the OP looks at this then he can try again with the above.
Also, Download mode is essentially the "bootloader" and it is locked meaning unless you have certified software (KDZ FW updater), you can't adb anything just in download mode unlike some LG phones that have emergency mode which is unlocked bootloader.
Click to expand...
Click to collapse
Yea I know the commands, The guide for going back to stock was created by me for the G2 haha, Hopefully the OP will see your post and try that

ive tried
ive tried factory reset "vol down & power"...its just goes black and stays the same

I'm having about the exact same problem. I rooted my phone a while back, I left it stock and just used some modules (xposed). When I noticed the update I of course was stupid enough to hit the update... My phone is doing the same as his. I can get to the factory reset screen but even if I go through there I get the same black screen (though backlit). I can't boot into download. I'm downloading the .tot needed for stock, but I'm not sure if that'll be a lot of good without download mode. I have everything on my phone backed up from when I rooted it (I'm missing a few pictures but nothing major.) Any and all help would be appreciated. I've got a bunch of precalc homework and Prom in a couple days so I'm willing to sacrifice sleep tonight. Thanks! (Made this account just for this, though I've used the site a bit before.)

xdavelope said:
ive tried factory reset "vol down & power"...its just goes black and stays the same
Click to expand...
Click to collapse
It's cuz you're not doing it correctly.
Yes, you're supposed to depress "vol down & power" but once you see LG logo, let go of both buttons and then immediately hold down only the "power" button.
After a few secs, a white factory reset screen will appear. Ignore the warning and press power button. I know, its kinda scary at first, but then phone will load into recovery.

I can get to the factory data reset screen but when i choose yes it just gives me the secure boot error. I am able to put my phone into download mode by pressing up volume and power when plugging to pc, but cant get pc to recognize it. I am sure I am missing something.

i am also bricked. i cant get into download mode or recovery. i have twrp installed, cant get to that either. i have tried every button combination and all i get is a black screen and vibrations, no lg logo. need help.

Dont
BAYOUREBEL said:
Did just like you with OTA today and now bricked. Guess I will have to call Verizon and see what they can do.
Click to expand...
Click to collapse
Call LG verizon will void your warranty

Has anyone made any progress or did all just send back to LG?
I am in similar shape, can get to the white factory reset screen - which does nothing once I accept.
I can also get into download mode, but the phone isn't recognized.
Wanted to confirm before I try to send it back that I can't fix myself.
Thanks!

Also, did anyone who was able to get back to the hard reset screen have luck sending to LG? Or did it have to be completely bricked?

Im also bricked. And there is no recovery mode. download mode is usable. but when i in twrp before brick i deleted efs because i have a back up after that recovery had corrupted and driver in the rom memory to talk to pc had also deleted with efs(i think). I have an idea to fix but im not sure
If I can change rom from mainboard and replace it other rom from other lg g2? Will it solve my and our problem??????
thanks to reply.

[Q] AT&T LG G2 won't boot

I've been messing around with my phone, trying to flash CWM and CyanogenMod (to no avail), and yesterday something happened. I woke up, my phone was dead so I started charging it. It booted into the Stock OS (the one that ships with the G2--build D20010o I think). Shortly after, a message appeared on the screen about an update the phone was going to install (I'm assuming one that AT&T was pushing to my phone), and shortly after it powered down on its own. I have not been able to get it to boot into the OS since.
Before all of this happened, I rooted the phone with IORoot, tried to flash CWM (I think successfully), but was not able to install CyanogenMod, so I flashed an earlier build of the stock OS (D20010o), rooted it again (I'm not sure that I had to--I think it stated that my phone was already rooted), tried to flash CWM again (unsuccessfully this time), and I gave up. Then this problem occurred.
Every time I try to power on the phone, the LG logo flashes, and the screen stays on, but it's black. If I try to do a factory reset via the hardware buttons, I am able to see that screen, but as soon as I follow the instructions of pressing the power button twice, it says that it's initializing the reset, but then the phone's screen goes black again--not sure if the screen is on or off, though. The LED light is also not on during any of this.
I'm unsure what to do. I've had the phone for about 6 months, but I had not owned an Android before that--iPhone user for 3 years. I obviously did not do enough research or ask enough questions, but I would like my phone to be in a usable state. I would greatly appreciate any help that anyone can give me!

NEVER take an OTA with a recovery.
Use the lg flash tool to go back to stock
http://forum.xda-developers.com/showthread.php?t=2432476

Sorry, should have also mentioned that I can't boot into Download Mode. I'm assuming there's no .kdz file for AT&T, and the other method in that link requires Download Mode. :/

LG G2 Might be bricked, not sure.

Hello, cutting to the chase
Model: LG G2 D802
Story time: I tried to install ressurection remix rom through the sideload, after fully wiping my phone ( Wiped system, data, yada yada ) it showed some kind of an error about SU not installing properly, I thought well if I'll reboot TWRP will automaticly install SU for me, so when I tried to reboot it showed that No OS is installed, I thought it's a simple bug so I'll reboot to recovery again to check and bam. Nothing works.
+ Can't boot into recovery ( Tried volume down + power button ) LG Logo shows up and goes blank again ( Note that the screen doesn't turn off, just stays black, after holding it for a couple of seconds I can see screen going off completely but can't turn it on)
+ Can't turn it on normally.
+ Can't boot into download mode.
+After plugging it into an USB it mounts a D lettered drive with 63MB stuff in a folder called image with *.mdt files, modem files( I can screen it if it's important )
I'm clueless, never happened to me even though I flashed a lot of roms, I think I bricked it. Help?

UPDATE: I managed to quickly release Volume Down And Power buttons when LG appeared for half a second and hold it again, succesfully booted into TWRP. I haven't bricked it I think. Will tell how it goes <3

Hey man, how'd it go?
I'm in exactly the same situation as yours, can boot into twrp but nothing else works, i fear of the qhsusb_bulk brick but these people don't even seem to have recovery.
Any suggestions? Go back to stock? How?

Argus137 said:
UPDATE: I managed to quickly release Volume Down And Power buttons when LG appeared for half a second and hold it again, succesfully booted into TWRP. I haven't bricked it I think. Will tell how it goes <3
Click to expand...
Click to collapse
How did it go!? I'm in a similar situation (but can boot into download-mode). Would love to get back to twrp, since I want to give it a try to flash another cm (stable). Thanks for sharing your experience...

If its picking up bulk mode normally its hard bricked there is a guide for restore nearly all g2s from hard brick having done it myself included 1st time took me a week to get back up but. Now i prob take about 45 min just cause i aint had one in a while

TheMadScientist420 said:
If its picking up bulk mode normally its hard bricked there is a guide for restore nearly all g2s from hard brick having done it myself included 1st time took me a week to get back up but. Now i prob take about 45 min just cause i aint had one in a while
Click to expand...
Click to collapse
Hey there, can you specify what you did exactly or where to find!? Do you mean something like this? (can't post outside links, in XDA-forum, title is "LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]") Thanks for help...

Yes thats it. Lol i still got the files on my pc for my g2 i keep the whe setup cause im on the g3 now i just check in the g2 forums cause i had mine for 2 years and modded the crap outa it but yea i keep all the files on hand so if anything ever happens i can fix it almost on the fly now

Well so what happened to me that I managed to get inside the TWRP. When it lighed it up for a second I quickly released and held again that got me inside magically. So then I just transfered new rom and tried to install again. Sadly I didin't see that the ROM Im trying to install requires bump TWRP and I bricked my phone again. Though I entered download mode and flashed the stock rom through LG G2 flasher.

heres a video i made, how to go into recovery. for those that cant get in to twrp.
https://www.youtube.com/watch?v=jPUTImVEHqc