H811 completely dead - T-Mobile LG G4

Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?

I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.

ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.

Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.

partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.

wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....

I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.

http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick

mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk

mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.

My phone lives!

partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!

Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk

partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.

WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk

WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.

partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.

WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.

wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,

WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.

Related

[Resolved] Moto X randomly bricked itself

So, I imported and gifted this device to my GF and will describe what happened as she did. She was downloading a torrent and suddenly the screen just went black. After holding the power button for awhile, the phone came back on but, would get stuck on the boot logo(welcome message) screen and in a boot loop. I know that it is a SIM unlocked Moto X(XT 1053?)
So far, I've tried getting into the bootloader and am able to. The only problem is when I get to the recovery, I don't see the little dead Android dude. The phone ends up dying. Now I have it charging and I'm on the bootloader screen, but I still can't get into recovery. I just get a blank screen when I try.
It will be hard, time consuming and maybe a little expensive RMAing the device, as I'd probably have to send it back to the US for the warranty.
I'm thinking maybe I just try and unlock the bootloader and see if the subsequent factory reset helps. But I don't know if this will work.
I have tried fastboot erase cache but it didn't help.
I think somehow my recovery is gone. I've tried flashing a recovery.img but it errors out. (failed to hab check for recovery)
Any ideas?
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
KidJoe said:
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
Click to expand...
Click to collapse
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
deejaylobo said:
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
Click to expand...
Click to collapse
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
KidJoe said:
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
Click to expand...
Click to collapse
I only found one person with a similar issue, and you're right, he did end up getting a replacement. That's just not an option for me. It's too much of a pain sending it back to the US.
Yeah, I think I will reflash a ROM. Can you point me towards figuring out which is the correct ROM? My System Version is 212.44.21.ghost_row.Retail.en.US. So, I just grab the corresponding SBF, yeah? I flashed the logo with mfastboot, so I'm okay with that. EDIT: No worries. Foudn the right file. Sorted. Everything seems to be working fine. Thanks!
The face thing, is just to prank her. I previously had a custom message set up for her through the Moto Maker. I think she'll be rebooting her phone more often now.

Randomly gets stuck on boot

So my phone will randomly not boot fully, just get stuck on the animation. I'm running Rapture 2.3. It just keeps playing the animation over (not a full bootloop, just freezes) and I have to pull the case off, carefully remove the back cover, and take the battery out (as holding the power button does nothing). I've tried clearing my cache and even another ROM (FireKat did the same thing), but this problem pops up so arbitrarily it seems. Whether I'm doing a full reboot, a 'hotboot' or 'fast reboot', or even turning the device on from dead off after charging, sometimes it works just fine, sometimes I have to pull the phone apart and try again.
Anybody else have this problem?
I'm having the same issue and I can't figure it out for the life of me. I just live with it the way it is. Let us know if you figure out something.
---------- Post added at 05:46 AM ---------- Previous post was at 05:44 AM ----------
falsepr0phet said:
So my phone will randomly not boot fully, just get stuck on the animation. I'm running Rapture 2.3. It just keeps playing the animation over (not a full bootloop, just freezes) and I have to pull the case off, carefully remove the back cover, and take the battery out (as holding the power button does nothing). I've tried clearing my cache and even another ROM (FireKat did the same thing), but this problem pops up so arbitrarily it seems. Whether I'm doing a full reboot, a 'hotboot' or 'fast reboot', or even turning the device on from dead off after charging, sometimes it works just fine, sometimes I have to pull the phone apart and try again.
Anybody else have this problem?
Click to expand...
Click to collapse
I'm having the issue and I can't figure it out for the life of me. I just live with the way it is. Let us know if you figure out something.
I'd do a factory reset, Odin back to stock, and start the rooting process over.
Android_Monsters said:
I'd do a factory reset, Odin back to stock, and start the rooting process over.
Click to expand...
Click to collapse
Okay you win, I'll give it a try. Just did the reset, Odin-ing back to stock now. Will update.
UPDATE: On stock, rooted and recovery. Installed xposed and gravity box to give me advanced reboot options. Did several fast reboots, regular reboots, and full power down and back ups. No freezes. Going to clean install Rapture now.
chrispyutec said:
I'm having the same issue and I can't figure it out for the life of me. I just live with it the way it is. Let us know if you figure out something.
Click to expand...
Click to collapse
What (if any) Xposed modules do you have installed? After a few hundred reboots after installing things one by one and doing several reboots between each install, I'm pretty sure I've narrowed it down slightly.
I can tell you that Wanam and Xposed Torch are not looking like the causes.
Currently I'm not running xposed or wanam and it still does the same. I'm pretty much used to living with it. Luckily I go naked and not rock a case that's tough to remove which helps for battery pulls.
chrispyutec said:
Currently I'm not running xposed or wanam and it still does the same. I'm pretty much used to living with it. Luckily I go naked and not rock a case that's tough to remove which helps for battery pulls.
Click to expand...
Click to collapse
Interesting. I think I've figured it out. It did it as soon as I restored Gravitybox. So I uninstalled it, did several reboots and had no freezes. I did a fresh install, and did not restore the data but rather set all the settings manually, and so far have had no freezes. I wonder if it has something to do with restoring data using Titanium Backup from a completely different device (individually restored a lot of data from my Galaxy S4).
EDIT: Nevermind, it just froze again :/
falsepr0phet said:
Interesting. I think I've figured it out. It did it as soon as I restored Gravitybox. So I uninstalled it, did several reboots and had no freezes. I did a fresh install, and did not restore the data but rather set all the settings manually, and so far have had no freezes. I wonder if it has something to do with restoring data using Titanium Backup from a completely different device (individually restored a lot of data from my Galaxy S4).
EDIT: Nevermind, it just froze again :/
Click to expand...
Click to collapse
Dang it! Was hoping you were on to something.
chrispyutec said:
Dang it! Was hoping you were on to something.
Click to expand...
Click to collapse
Do you use a custom ROM or are you rooted at all? This is so frustrating. Sometimes I feel like I get it, then it happens again.
falsepr0phet said:
Do you use a custom ROM or are you rooted at all? This is so frustrating. Sometimes I feel like I get it, then it happens again.
Click to expand...
Click to collapse
I'm running a clean install of Rapture with no other mods except for what's already baked into the ROM.
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
chrispyutec said:
I'm running a clean install of Rapture with no other mods except for what's already baked into the ROM.
Click to expand...
Click to collapse
I only get stuck on reboot when I either restart or shutdown. I never have random reboots and what's weird is my stuck on reboot issue doesn't happen every time I restart or shutdown......it's totally a flip of the coin if it will get stuck or not.
Have you tried a different rom? Of course, with a factory reset + Odin to stock first.
chrispyutec said:
I'm running a clean install of Rapture with no other mods except for what's already baked into the ROM.
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
I only get stuck on reboot when I either restart or shutdown. I never have random reboots and what's weird is my stuck on reboot issue doesn't happen every time I restart or shutdown......it's totally a flip of the coin if it will get stuck or not.
Click to expand...
Click to collapse
I'm also having this issue on occasion. I am thinking I may not have flashed the proper baseband and firmware to match the rom I was using. Is this possible with anyone else?
chrispyutec said:
I only get stuck on reboot when I either restart or shutdown. I never have random reboots and what's weird is my stuck on reboot issue doesn't happen every time I restart or shutdown......it's totally a flip of the coin if it will get stuck or not.
Click to expand...
Click to collapse
After 3 days, 5 ROM installs, and what seemed like well over 1000 reboots, I've finally.. given up. I tried flashing the "Baseband" and "Bootloader" from the Rapture post, still freezes. I'm at the point where I can actually tell when it's going to do it because the boot animation isn't as bright as normal. It always get's darker right before it shows the lockscreen, but if it's going to freeze, the boot animation starts dark.

I really messed my new phone up.

Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Highway 55 said:
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree. I need some one with skype to walk me though it. I literally followed step by step guides on youtube without knowing what I was doing, it was my fault.
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
I hope everything turns out okay and you get your phone working again. I would Skype with you but I'm on dad duty with my kids tonight. Good luck!
Sent from my Nexus 6 using Tapatalk
Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
That was your mistake. If never messed with Android worst thing you could do is jump right on a Beta build.
---------- Post added at 08:14 PM ---------- Previous post was at 08:08 PM ----------
Easy to fix if unlocked and have TWRP. Recommend going to stable build first and work your way up. At least will have a working phone. Make a backup up stable build and then play all you want. Could have made backup of stock before even flashed M and would have been golden.
What did you do when you got the corrupt message? I'm asking because many people get this message but if you ignore it, it should boot up anyway.
slosrtnick said:
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
Click to expand...
Click to collapse
yeah I got it! i watched a video on re-flashing M? I think? It works now, I'm still not sure how to back up my stuff properly but I have a working phone! Thanks for the reply!
Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
It sounds like all you need to do is: when you get to that "phone is corrupt" screen, press volume down and then the power button to continue.

Hard bricked??

I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
waylo said:
I was on 10N, rooted, and was planning on bring it in to the store to have them look at something. I was attempting to revert back to 10H, stock, in case they checked for mods.
Using TWRP, I flashed the 10H bootstack. Then, I flashed the 10H-RETURN-2-STOCK.zip. These were all made by @MicroMod777. The 10H-return-2-stock is supposed to restore stock recovery + system.
When I selected reboot into system in TWRP, the screen blacked out. And that's it.
Unable to get any screen to turn on again. No powering up at all.
Any suggestions? If I can't get into download mode, or get the screen on, it's done.
Click to expand...
Click to collapse
Did u pull battery?
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Did u pull battery?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
waylo said:
Yes, multiple times. Pressed the power button with battery out. Screen is dead black =(
I think the rationale behind my flash zips makes sense, right? Revert the bootstack, then the system+recovery...
Click to expand...
Click to collapse
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
Not sure what happened. I pulled 10H just in case. Did ur md5 match?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
waylo said:
Yes it did, checked it right after the transfer, both the bootstack and the recover-to-stock.
I'm guessing it might have been the bootstack, as recover-to-stock.zip wouldn't have affected ability to get into download mode.
I hooked it up to the USB and windows tried to install a qhsusb_bulk driver. But now nothing.
With no download mode, this one is toast I think. Just dropped by the store, a replacement will be shipping out soon.
Crap, I really liked this one's camera, with minimal pinkish tinge.
Kudos for pulling the 10H file, just in case.
Click to expand...
Click to collapse
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
MicroMod777 said:
If it was a bad flash then that would of for sure bricked it. A bad Aboot partition= brick for sure.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yeah, next time I will go the KDZ route to return to stock. Bummer!
Look up G2 unbrick.
Sent from my LG-H811 using Tapatalk
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
MrSteelX said:
I am sorry to say but your g4 is hard bricked. You attempted to downgrade on the g4 and that is a BIG NONO. AutoPrime warned us that every update, they change a bit that pervents a downgrade. Once you upgrade to 10n, You are stuck on 10n. If you had tryed the kdz back to 10h, It would have failed.
Click to expand...
Click to collapse
Thank you all for the education.
10N hadn't been out for a day, so I was concerned this would raise some red flags at the store. Otherwise would have kept it on--a vast improvement over 10H.
I haven't been on LG at all previously, so all this info would have been nice to know beforehand. =/
Oh well, live and learn.
Of course it's similar with most phones (i.e. Samsung won't let you downgrade bootloaders/modem), but typically it will just not take, rather than brick. As I recall, what happened to me is an inherent danger with TWRP zip flashing.
Yeah, the KDZ failed 10h flash would have been a nicer way to let me know I am trying to do something very very bad.
I looked at some LG2 unbrick notes. Most of them talk about the connected computer showing several hard drives when connected. At this point, I can't even get the computer to show the qhsusb_bulk driver install attempt again. Any tips on how to get the phone to power on the right way to allow for this?
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Biker1 said:
Thank you all for the edumacation. I am on 10n and will delete my 10h 'revert to stock' zip and anything else 10h. I didn't realize you cannot downgrade.
I will also delete my 10h Nandroid I made a few days before flashing 10n, and will make a 10n Nandroid.
Click to expand...
Click to collapse
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
waylo said:
I don't know for sure that the 10H system + kernel + recovery files will cause trouble. It's probably the bootstack file only that affects the ability to boot successfully. Provided you can get into download mode, you can salvage pretty much anything.
Your nandroid .data partition would probably be fine.
Click to expand...
Click to collapse
I hear ya.
I needed to make an updated 10h Nandroid anyway.
Don't hold me to it but from what i can tell we aren't being locked out of downgrading in future updates, just in 10n as it's main purpose was to patch stage fright which was a massive security flaw and they felt it unsafe to allow downgrade to an insecure state
so uh huge question here...i got my phone from tmobile aand it was 10h....so i flashed twrp and it worked...but now no matter what rom i run i get a hang until i reboot..then when i reboot the phone spazzes the **** out...help anyone thanks
Your problem is unrelated to this thread. Your phone is buggy but not bricked.
Last night I tried to root my phone. I pushed a rooted image. It completed and rebooted. Then I got a security error 11. I then pushed a factory image using the KDZ method. Now it's completely dead. Pulled battery a few times. Nothing. Held down power and volume down a few times. Nothing. Plugged it in to charge. No LED light, no battery charging animation, no security error. No nothing. I also connected it to my PC with a usb cable while holding in volume up. Nothing. A whole lot of nothing. I contacted LG and they sent me a fedex label. It's now in the mail.
Question: I have the naughty image on there, but as far as I know it never actually took so I never had root. Also, presumably the factory image is what is currently loaded. So will they be able to detect that the phone is rooted? If they find the naughty file will they consider that in the same way as if I had succeeded in rooting it?
I knew at the time that I was doing something that would void the warranty so I can't complain too much. So then in the process of finding that I was naughty will they unbrick it at least to the point where I can pray for a future fix? I can say "gosh darn just send it back as is" and hope that they helped me out while detecting my naughtiness. Or if I say, "ok you got me, what's it gonna cost for you to unbrick my phone?" will they fix it at a reasonable price? If not, can I run it over with my car and pay the $150 deductible on my insurance? Basically, where am I at?
this is lg we are talking about. They will do 1 of 2 things to fix it, 1. reflash the whole emmc chip call it done. 2. swap out the mother board and call it done.
So sorry, it was not a bad flash I did this exact thing tried to revert. You are hard bricked I just turned my phone in though because I did it on day 2 I had it and got a new one. Just warning people you upgrade and try to go back you will get a hard brick.
I did the same thing as smkyle, but I haven't turned mine in yet. Is there any hope for fixing it.
Edit: In device manager it showed "QHSUSB_BULK" and then stopped. I have a spare battery and charger so after swapping out the battery the computer read the phone again, but this time installed drives and now shows "Qualcomm HS-USB QDLoader 9008 (COM7)".

Possible bricked LG G4

I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Same here..
Why are you both flashing MM? Is there an official image to flash?
EmSeeMAC said:
Why are you both flashing MM? Is there an official image to flash?
Click to expand...
Click to collapse
That's why I'm an idiot. It's not an official .TOT.
ironbesterer said:
That's why I'm an idiot. It's not an official .TOT.
Click to expand...
Click to collapse
I fixed mines using LG UP
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
This should help you fix the dreaded 2
If you can boot into download mode, flash the ROM for your phone on sammobile
Just say you installed an update and it bricked your phone if it's still under warranty. I dunno how many times I botched my G Flex 2 and LG replaced it (ATT model).
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
He fixed it
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
mswlogo said:
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
Click to expand...
Click to collapse
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
agentfusion said:
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
Click to expand...
Click to collapse
It would be close to a thousand to pay off my current device (around $300 owed on it) and then go out and buy a new one. But, with autoprime and awesomeslayerg's help, I got my phone back to normal.
I'm glad I seen this before I tried that

Categories

Resources