LG G4 bricked - cannot get into recovery or download mode. - G4 Q&A, Help & Troubleshooting

Hello everyone, I hope you can help me. My husband tried to downgrade his LG G4 UK model from Marshmallow to Lollipop, using LGUP. The process failed and the phone is now bricked. I switch it on, and the "LG powered by Android" screen comes on, followed by the other LG screen. The phone just sits like that. I have tried to boot to recovery, and boot to download mode; but can do neither. I have also tried connecting to LGUP, LG Bridge, and the LG Mobile Support Tool. None of these can find the phone, as it needs to be switched on to be located by the programs. When I connect the phone to my laptop, I get the "thump" sound that shows the phone is connected to the computer. That is all I can get though. Is there a way out of this, and back to getting the phone working again? I would be grateful for any advice you can offer me to resolve this issue.

I think it's hard bricked. In that case, you can't recover it.

SirDarknight said:
I think it's hard bricked. In that case, you can't recover it.
Click to expand...
Click to collapse
I have now been able to get the phone into download mode. I was hoping that getting into download mode might help LGUP to see the phone, but I can't find a way of doing that.

We're on the same boat.

Did It - Fixed It!
drumbeater79 said:
We're on the same boat.
Click to expand...
Click to collapse
I took a punt, and the punt worked. I disconnected the phone from the computer, and pulled the battery. Then I re-inserted the battery. Next, I tried to get the phone to boot into download mode, by pressing power and volume down; with the phone disconnected from the computer. The phone then brought up a screen, asking if I wanted to do a factory reset. I chose "yes" and it asked me again (presumably in case I had pressed "yes" in error. The phone then powered down, before powering up, and optimising apps. Then it went to the welcome/sign in screen. All the previous apps are lost, but at least the phone is working now. Hubby is chuffed to bits with his "new" phone.
@SirDarknight @drumbeater79

Glad to hear that!

ursulavasey said:
I took a punt, and the punt worked. I disconnected the phone from the computer, and pulled the battery. Then I re-inserted the battery. Next, I tried to get the phone to boot into download mode, by pressing power and volume down; with the phone disconnected from the computer. The phone then brought up a screen, asking if I wanted to do a factory reset. I chose "yes" and it asked me again (presumably in case I had pressed "yes" in error. The phone then powered down, before powering up, and optimising apps. Then it went to the welcome/sign in screen. All the previous apps are lost, but at least the phone is working now. Hubby is chuffed to bits with his "new" phone.
@SirDarknight @drumbeater79
Click to expand...
Click to collapse
It's a hard reset, not download mode. Glad that it worked for you I already tried it several times but I can't get past the screen saying Android starting apps.

Related

Please help - My Excalibur won't boot up.

Dash Bricked Need Help!!!
I tried using a the google mail java app on my tmobile dash. It froze up on me, and when i turned it back on it just stays at the "tmobile" splash screen. I have tried using the soft key and power button reset but it doesnt work. What's weird is that it wont power down unless I take the battery out. It powers on, shows the tmobile splash screen, then freezes. Is there any other way to reset it or is it totally bricked? I bought it new off craiglslist so tmobile wont replace it for me cause I'm using it unlocked on cingular.
The power key reset should work. Could you be doing it wrong?
I was facing the same problem but after doing hard reset (Power Off, Press 2 soft key, Press Power On Key for 2 seconds then release soft key) worked fine. Seems timing is very important, try and try.
Help, i think i bricked my phone!
I was installing the WM6 Update released on this website, everything was going fine when i saw that my lil' cousin' disconnected my phone while i moved away from the PC (he pulled the phone altogether).
Now my phone is stuck in the bootloader mode screen (tricolor, blue green/red i think). It detects USB (it says USB on the bottom of the screen whenever i connect it). Is there a fix for it for the DASH? I read the wiki about a fix for a similar problem for the Hermes, but that didnt work for mine.
Can anybody help me please?!
Mine's a T-Mobile Dash with the stock rom from T-Mobile.
remove and reinsert the battery
if that does not work paperweight thats how i ruined my cingular 2125
Oh god, all this brickage makes me too scared to update. Can anyone direct me to where I can find how to backup my current setup so that I could reload it if something went wrong or I didnt like the Beta WM6?
MrLuna said:
I was installing the WM6 Update released on this website, everything was going fine when i saw that my lil' cousin' disconnected my phone while i moved away from the PC (he pulled the phone altogether).
Now my phone is stuck in the bootloader mode screen (tricolor, blue green/red i think). It detects USB (it says USB on the bottom of the screen whenever i connect it). Is there a fix for it for the DASH? I read the wiki about a fix for a similar problem for the Hermes, but that didnt work for mine.
Can anybody help me please?!
Mine's a T-Mobile Dash with the stock rom from T-Mobile.
Click to expand...
Click to collapse
Just try the flash again and it should start working. I had my computer bluescreen while I was flashing an SDA and got to the tricolor screen. It flashed fine after trying again. If its not detecting right. Pop out the battery on the phone and restart your computer and attempt the flash again. Shouldn't be a problem. Definitely scary though. I don't think you can brick these unless you mess up the bootloader perhaps...
ANyone know How do I manually put my Dash in Bootloader mode?
deemota said:
ANyone know How do I manually put my Dash in Bootloader mode?
Click to expand...
Click to collapse
power off, hold the camera key beside Space Tab for about 3 sec, and then press power key while still pressing the cam key.
You are a GOD. Thanks.
you have no idea why it gives you warnings not to run any programs or disconnect while the ruu is updating you think they just give you warning messages because the htc techs have nothing better to do????????
Blackforge said:
Just try the flash again and it should start working. I had my computer bluescreen while I was flashing an SDA and got to the tricolor screen. It flashed fine after trying again. If its not detecting right. Pop out the battery on the phone and restart your computer and attempt the flash again. Shouldn't be a problem. Definitely scary though. I don't think you can brick these unless you mess up the bootloader perhaps...
Click to expand...
Click to collapse
Well, tried that, but the computer doesnt detect the phone, meaning it wont connect to ActiveSync. Since it won't connect to activesync the program wont install it on the phone since it can't find it.
Good thing i have insurance. Bad thing i'm trying again as soon as i get the replacement
Are there any alternatives though? Maybe i can fix it before i send this one back.
restart your computer again..
This is from HTC Q&A
Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter CE OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It's normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.
1. Disconnect your Mobile Device from the USB cradle/cable.
2. Reset your Mobile Device.
3. Reconnect your Mobile Device to the USB cradle/cable.
4. Check that the communication cradle/cable is connected properly.
5. Return to the ROM Update Utility.
Note: You should ignore the ActiveSync connection.
WM6: Endless Bootup Loop
A few days before the official TMobile WM6 update came out I download the widely posted leaked version. The Dash started acting up during bootup one day, so I reflashed with the TMobile WM6. Now the same thing just started, and the device can't be used.
When powered on it does the quick vibrate, TMobile screen, Windows Mobile Screen, TMobile screen again, with power up 'jingle', then it just shuts off and starts the bootup sequence again. Endlessly.
Have tried removing the battery, etc. Has anyone else run into this? Any ideas of a keypress combo or something I can press during bootup that might jump-start it??? Thanks!
Take out the microSD card and the unit should boot properly. Mine was fixed with a new SIM card, but a new device may also be needed.
Wound up doing a hard reset. I had tried taking out the microSD card, then it would just hang on the TMobile screen. I also tried rebooting without the SIM card in, then it would do the loop thing. I'm thinking it must be related to software loading during the boot, and the only program I have on the microSD card that loads during bootup is FizzWeather.
rabilancia said:
Take out the microSD card and the unit should boot properly. Mine was fixed with a new SIM card, but a new device may also be needed.
Click to expand...
Click to collapse
I think this may at times be related to an auto-install file being present.
If you hold down the "end" key during boot-up it seems to prevent the cycling.
Thanks, will keep that in mind if it happens again. By 'end' key, do you mean the red phone icon key that you hang up on a call with?
robertgbl said:
I think this may at times be related to an auto-install file being present.
If you hold down the "end" key during boot-up it seems to prevent the cycling.
Click to expand...
Click to collapse

From download mode to dead ?

Hi,
yesterday i got my sgs and first i wanted to update it to JM5.
Because 3 of my friends have the same phone i know what to do.
First i tried to get into download mode but it doesn´t work.
I found here in the forum (thread 749470) "Australia Optus Galaxy S no download mode!" that i´m not the only one with this problem.
Someone told me to use "adb reboot download" to enter download mode - and this worked fine. The working android appeared on the screen.
Odin now found the phone and i tried to flash but it always ended with "file analysis....". So I found help in this forum - restart pc, start odin as admin, use another firmware, try other usb port - nothing happened - last thing: remove the battery for 30sec and try again.
NOW: SGS alway shows the same pic: a phone + ! + PC - but PC can´t find phone, phone can´t be switched off - nothing!
What can I do now except taking the phone back to my dealer?
I appended a pic from my display.
Thanks for your help!
HolyFreak
if you can not get into download mode, then there is no way to fix it
you'll have to send it back to the store, to have it repaired
hmm, you can press at least the power button for 7-10 seconds, then the phone reboots, mybe you are able to go into download or recovery mode, with those button combinations.
but isn't that icon his screen shows, meant to connect the phone to pc and start kies so kies can fix it? (at least i read sth like that on forum) but if this all doesn'T work i don't know
You can always switch the phone off, pull the battery out. ( Avoid doing so when flashing though. )
http://forum.xda-developers.com/showthread.php?t=725858
saldawop said:
http://forum.xda-developers.com/showthread.php?t=725858
Click to expand...
Click to collapse
This guide is really not all that useful.
Take out the battery, and reboot by first pressing voldown+home and then power and wait until you see the yellow download screen.
I'd recommend not doing anything with a phone that you can't get into download mode from a cold start with. Too much can go wrong. Leave it on stock.
I remember seeing that screen when I thought I had bricked my phone, I think I managed to pull back by removing the battery and trying again.
waspbr said:
I remember seeing that screen when I thought I had bricked my phone, I think I managed to pull back by removing the battery and trying again.
Click to expand...
Click to collapse
that is only because your 3 button combination was working
in his case, his 3 buttons are not working
there is a batch of samsung phones that came from factory with the 3 button combo disabled
Having the same issue. Think the stores will replace it under warranty like this?

[Q] T-Mobile Note 3 stuck in a auto-restarting, recovery bootloop

Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks

Phone won't turn on after root

I rooted my Verizon LG G4. Afterwards it wouldn't boot completely. It gave a Verizon message and wouldn't completely turn on. I tried to go back to the factory firmware and now I can't get it to boot up at all. No Verizon logo, nothing. Hard bricked? Is it completely shot or can it be fixed? I found a link to unbrick Qualcomm phones but it won't let me post the link here. It is very complicated!
Thanks!
kada598 said:
I rooted my Verizon LG G4. Afterwards it wouldn't boot completely. It gave a Verizon message and wouldn't completely turn on. I tried to go back to the factory firmware and now I can't get it to boot up at all. No Verizon logo, nothing. Hard bricked? Is it completely shot or can it be fixed? I found a link to unbrick Qualcomm phones but it won't let me post the link here. It is very complicated!
Thanks!
Click to expand...
Click to collapse
Can you get into download mode? If so, try to KDZ back to stock or push the backup image you should have made.
Sent from my Xposed VS98613B using XDA Free mobile app
KADA528 - Did you find a fix?
I have the same exact problem. Phone won't turn on after rooting. Cannot get to download screen either.
Hey guys i have the same problem phone wont turn on after root i did everything and it did nothing. I try to turn it on now and it does nothing not even download mode. I connect it to the computer and i hear Windows give me the sound when you plug in a phone.
Unable to revert to stock on vs986
I rooted my Verizon LG G4 using low effort root on version 11A. I am new to this rooting and didn't know how to disable system update. When I got the system update notification, instead of tapping install later, I tapped install now. Of course, the system update failed but since then I am not able to enter download mode to revert to stock. I tried to factory reset but it gives me secure boot error 1003 and just restarts the phone. Is there anything I can do to enter download mode? Thanks in advance.
sunny2015 said:
I rooted my Verizon LG G4 using low effort root on version 11A. I am new to this rooting and didn't know how to disable system update. When I got the system update notification, instead of tapping install later, I tapped install now. Of course, the system update failed but since then I am not able to enter download mode to revert to stock. I tried to factory reset but it gives me secure boot error 1003 and just restarts the phone. Is there anything I can do to enter download mode? Thanks in advance.
Click to expand...
Click to collapse
Turn off the phone, hold volume up, then plug in the USB.
I didn't root my wife's G4, but I have a feeling something is going on. At first, the phone would show the LG splash screen, then go black. Went in and did a factory reset, still the same thing. I took it into a VZW store on December 23rd and they tried doing the same things... as they were doing that another guy walked in with the same issue, same exact model. Anyone know if some sort of push was done recently?
After they processed the warranty repair, I brought it home and tried to re-flash the OG firmware. Now the phone will not power on at all, no bootloader, download mode, etc.
Silver lining is that my wife wanted a phone for the holiday, so I purchased a LG V10 with the intention of returning it within 14 days... she loves the phone, I get $100 back from LG, and I sold her replacement G4 for over $250, so I actually MADE money on the deal, LOL.
sushi-gee said:
Turn off the phone, hold volume up, then plug in the USB.
Click to expand...
Click to collapse
Thanks for your reply. I tried as you described several times but it just starts the phone without going to download mode. I am not able to do a factory reset either. I also tried to boot into recovery using quickboot app but the phone just restarts.
If the phone won't turn on, hold down down volume and power buttons at the same time. Assuming it turns on, turn it off and hold the same buttons again while it's off and then choose clear cache. Had both the unable to turn on and it stuck on the Verizon screen the past few days and this fixed it.
Almighty1 said:
If the phone won't turn on, hold down down volume and power buttons at the same time. Assuming it turns on, turn it off and hold the same buttons again while it's off and then choose clear cache. Had both the unable to turn on and it stuck on the Verizon screen the past few days and this fixed it.
Click to expand...
Click to collapse
Tried this method. Was able to get to recovery. After I tapped wipe cache, the phone restarted, gave the same "secure boot error! Error code 1003, Verizon logo appeared and phone restarted. I have root access. Is there a way to uproot without going into download mode?
---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------
Edit: I meant unroot.
sunny2015 said:
Tried this method. Was able to get to recovery. After I tapped wipe cache, the phone restarted, gave the same "secure boot error! Error code 1003, Verizon logo appeared and phone restarted. I have root access. Is there a way to uproot without going into download mode?
---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------
Edit: I meant unroot.
Click to expand...
Click to collapse
You may want to try KDZ/TOT... http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Just a warning, that's what I tried to do and then my wife's G4 no longer powered on. I was OK because I had a warranty replacement already in progress.
WorldOfJohnboy said:
You may want to try KDZ/TOT... http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Just a warning, that's what I tried to do and then my wife's G4 no longer powered on. I was OK because I had a warranty replacement already in progress.
Click to expand...
Click to collapse
Flashing KDZ/TOT needs to be in download mode. I am unable to enter the download mode or factory reset the phone. When I try to plug the usb cable with the volume up button pressed, it gives me a secure boot error 1003 and boots to system.
sunny2015 said:
Tried this method. Was able to get to recovery. After I tapped wipe cache, the phone restarted, gave the same "secure boot error! Error code 1003, Verizon logo appeared and phone restarted. I have root access. Is there a way to uproot without going into download mode?
---------- Post added at 03:58 PM ---------- Previous post was at 03:54 PM ----------
Edit: I meant unroot.
Click to expand...
Click to collapse
Interesting because on the same day I responded, I uninstalled something and rebooted and the phone rebooted and I got to see both the LG logo and the Verizon Wireless boot screen but then when I wasn't looking, it turned black as if the phone was off. Nothing would turn it on until I did the force reboot and then clear cache and the phone was back to normal again.
sunny2015 said:
Flashing KDZ/TOT needs to be in download mode. I am unable to enter the download mode or factory reset the phone. When I try to plug the usb cable with the volume up button pressed, it gives me a secure boot error 1003 and boots to system.
Click to expand...
Click to collapse
So you can't get into Download mode, but can boot into the OS and the "recovery" menu (sorry, I'm coming from HTC phones, so I'm on a different set of terms/boot options)? I don't know of a method that will work to fix Download mode.
I was able to factory reset the phone. First, I unrooted using the su app. Then, I downloaded the Verizon Upgrade assistant that also had a repair assistant. After clicking repair, the repair assistant took about 15 to 20 minutes and said that the phone has been repaired. I went into recovery mode and wiped cache. After that, I used the recovery menu to factory reset the phone and this time, I was successful with the factory reset. Then, I took the system update to update the software to 13b. I don't plan on rooting the phone till a custom recovery such as TWRP becomes available for this phone.
xxjrsmith3xx said:
Hey guys i have the same problem phone wont turn on after root i did everything and it did nothing. I try to turn it on now and it does nothing not even download mode. I connect it to the computer and i hear Windows give me the sound when you plug in a phone.
Click to expand...
Click to collapse
Did you ever figure out how to get it back on?

NOOB: hard bricked op3, volume up button hasn't been working

First off, I did do a search, but as far as I can tell no one has had this problem so far.
This is all after modding using a tool kit: (i can't include the url but it is the toolkit by neisor on the oneplus forums)
tldr: phone stuck in bootloop, computer wont recognize the phone, maybe because it keeps shutting off and then booting to the 1+ logo, then shutting off again, would drivers help? what can I do about the volume up button?
So for a while my volume up button hasn't been working, and the mega unbrick post shows that I need to hold the volume up button for at least 25 seconds and while holding, plug my phone in. I have also seen some posts that say the volume up button could be a software issue, and the button itself could be working, and it is just not registering, as well as someone saying that you could take the back off and manually press the button, instead of using the bar on the outside of the phone (would this work?). I have gotten the button to work in the past by pressing the volume up button to the side instead of straight in, but I haven't been able to get it to work since my phone got bricked.
Another issue: my phone is stuck in a boot loop, I can't access fastboot, and I'm unsure of recovery because my volume up button is not working. would it be worth it to deal with the constant vibrating to try to get it to recovery?
I have been able to shut the phone off by holding the power button for something like a minute and a half, though.
This is my first post, and if I have broken any rules I am very sorry, but I need help and am tired of not having a phone.
Thank you everyone,
Mark
Edit: this is what I did to root the phone:
1. download the toolkit
2. unlock bootloader (when fastbooting the phone said unlocked at the bottom, and a message about not being secure showed every time I rebooted the phone)
3. flashed twrp (no issues, still booted, recovery went to twrp. for some reason I had to flash multiple times as every now and then recovery would revert to stock op, although I did make a backup through twrp)
4. send supersu zip file to phone, install using twrp (phone would not boot, op logo stayed on phone for 2 hrs + until I rebooted to fastboot and tried to reinstall the backup I made, still nothing)
5. Try magisk (still stuck on op logo)
6. try to go back to stock, accidentally lock bootloader (now the phone is stuck in bootloop, don't know what to do from here as I cant get to fastboot and am unsure of recovery's accessibility.)
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Thanks
150208 said:
If you are sure you have a broken volume button, you need to replace it first in order to get the phone fix.
Correction:
Fastboot/bootloader = Power+Vol Up
Recovery = Power+Vol Down
Click to expand...
Click to collapse
thanks for the correction, I will keep trying the volume buttons, if it doesn't work by the end of today I will search for a new volume button.
Thanks again,
mark
Ouch
badabdba said:
This happened to me except I didn't even get anything appear on the screen -- the phone just periodically vibrated with the screen not even light up. I tried the reset toolkit which is meant to flash your phone back to normal using Qualcomm drivers or something, but that didn't work either. Eventually I had to send it to OnePlus who fixed it for free in under a week! They said the motherboard had failed.
I hope you get this fixed!
Click to expand...
Click to collapse
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
MarkTheFur said:
Damn, that sucks, and besides being unfixable (doubt it), this is my biggest fear. I'm in the US and really don't want to have to ship my phone to china to have it fixed. If you are in the US as well do you know if there is a OnePlus branch I can send it to in the US?
Thank you,
Mark
Click to expand...
Click to collapse
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
MarkTheFur said:
... what can I do about the volume up button?
Click to expand...
Click to collapse
Can you boot into recovery by pressing power+volume down buttons?
Update: Got phone to show on computer as qualcomm under coms and ports
So last night I went ahead and held volume up for about 20 seconds, then plugged the phone in, keeping the volume up button pressed the entire time. my phone stopped bootlooping and showed up as a qualcom device! So I have downloaded the new driver the stock os, and am going to proceed to try to unbrick my phone.
Wish me luck,
Mark
Yes, I did, and its working so far
tnsmani said:
There seems to be one in Texas. Anyway, contact OnePlus and they may try to solve it over the air.
Apart from that, did you install the Qualcom drivers properly? Even with your faulty power button, try to hold it down for 40+ seconds (for the phone to switch off) and then immediately hold down the volume up button for 10 seconds and then plug in the phone to the PC. I know I am merely repeating the instructions of Naman Bhalla in his Mega Unbrick Guide but it is crucial to do them correctly especially the installation of the drivers. Try these steps repeatedly because for some people, the phone gets recognised after repeated attempts. Or else replace the power button and then try these steps.
I had to use the Guide last month and successfully resurrected my dead phone.
Click to expand...
Click to collapse
I still need to turn off the signed drivers features ( a huge bi*ch, I have to use another computer to contact microsoft or something to get my computer to load when I turn off safe boot or whatever its called), but once I do that I can install the driver and attempt to reinstall the stock os. Hopefully everything will go well.
Thank you,
Mark
Not as far as I know
rk2612 said:
Can you boot into recovery by pressing power+volume down buttons?
Click to expand...
Click to collapse
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
MarkTheFur said:
So far recovery has not been loading, just the bootloop, but I have gotten the phone to power off by pressing the power button for 40 seconds, and the volume up button plus plugging in does make the phone register as qualcom 9008 or something like that. Basically everything is going well so far, and the faulty vol button seems to have been a software bug, as it does work when plugging it in. I will try to get to fast boot, but it did not work last time.
Thank you,
Mark
Click to expand...
Click to collapse
Glad to hear that there is some progress. Best of luck and keep us informed.

Categories

Resources