I'm currently on vacation in Thailand and my nonrooted VZW LGG4 on the latest OTA randomly fell into a boot loop today in the middle of snapping a photo. Pulling the battery did not help. I can access stock recovery but neither safe mode or factory reset solved anything.
Any other ideas or am I screwed until I return to the states and go through a VZW RMA?
usefulidiot127 said:
I'm currently on vacation in Thailand and my nonrooted VZW LGG4 on the latest OTA randomly fell into a boot loop today in the middle of snapping a photo. Pulling the battery did not help. I can access stock recovery but neither safe mode or factory reset solved anything.
Any other ideas or am I screwed until I return to the states and go through a VZW RMA?
Click to expand...
Click to collapse
Well sounds like either a corrupted partition or hardware failure. Don't know if this is possible with VZW version - but if you got access to a PC you could flash last version of the firmware through LG-Bridge.
Greetings
Medizinmann
Related
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Fearborn said:
So, at the risk of posting too much info (instead of not enough) I'm going to start at the beginning:
I rooted my wife's S3 and loaded TWRP and Paranoid Android. It ran fine, but there was a camera issue, so she wanted me to restore it to the stock ROM. I did this (to 4.1, I believe, whatever was out in August). Again, it ran fine and I was planning to restore the root access, but did not.
Later, it was dropped in Hibachi sauce (not sure this is relevant, but in case) and we put it immediately in rice. It worked fine, other than the touch screen intermittently ceasing to receive touch commands.
When the updated ROM came from Samsung, my wife installed the update and the phone continued to work fine, other than the screen issue.
She was tired of the issue and decided to sell it to buy an iPhone (shudder) so she did a factory reset. This is where the issues began (I included the previous steps as I'm not sure which may have caused the current issue).
Upon the factory reset, the phone would only boot to the beginning of the AT&T logo loading. I thought it may be something she could fix through Kies and suggested she try that, so she did. The phone would then boot to a screen in Odin mode that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." We did this and there was no help.
I can get it to boot into recovery (the default one now) and have tried to reflash that and the stock ROM that I did previously and only can get two actions: either the freeze at the AT&T logo (if I use Odin to flash the ROM) or the above message in Odin mode (after trying to fix from Kies).
I'm not sure what to do at this point and would appreciate any and all help you guys can provide. I've lurked around and learned quite a bit to flash my ROM and my wife's from you guys, so I'm really hoping I can learn more from this.
Thanks in advance!
Click to expand...
Click to collapse
So is it stuck on the AT&T Logo? Or Samsung Logo?
UnknownTroll1 said:
So is it stuck on the AT&T Logo? Or Samsung Logo?
Click to expand...
Click to collapse
It was the AT&T logo, it's currently the Odin. If I flash it again with the stock ROM, it'll be the AT&T logo again, but it doesn't completely load the AT&T logo. The Samsung one loads and then the AT&T starts to load, but doesn't finish playing.
Anyone?
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jblparisi said:
Yes, Odin to stock unrooted, then go ahead and factory reset by holding volume up + home button on first boot. Done.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
If this works (I'll try it when I get home) I will be so grateful! BTW, do you happen to have a decent link to a stock ROM? If not, I'll Google it tonight.
I rooted my phone with GALAXY NOTE 2 Toolkit. It was working fine for few months. Recently I noticed a problem when I tried to reboot it, but I pulled the battery out and after reinserting all went OK. then Next day or two another time when I tried to reboot, I got to the point where I cannot boo the phone anymore. I get to the initial T-MOBILE screen and that's where it gets stuck.
I tried to upload a recent ROM through Odin. It worked fine, no errors, no problems, but when I try to boo the same thing happens.
I also tried to get to the other menu ( Power+Home+VolumeUp). It shows the menu with some options but I'm not sure how can I use those. I treid few things but it does not work.
I need to use the phone for work every day so I am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
SAME HERE!!!
aklisiewicz said:
i rooted my phone with galaxy note 2 toolkit. It was working fine for few months. Recently i noticed a problem when i tried to reboot it, but i pulled the battery out and after reinserting all went ok. Then next day or two another time when i tried to reboot, i got to the point where i cannot boo the phone anymore. I get to the initial t-mobile screen and that's where it gets stuck.
I tried to upload a recent rom through odin. It worked fine, no errors, no problems, but when i try to boo the same thing happens.
I also tried to get to the other menu ( power+home+volumeup). It shows the menu with some options but i'm not sure how can i use those. I treid few things but it does not work.
I need to use the phone for work every day so i am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
Click to expand...
Click to collapse
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
go to recovery mode if you can
kim621973 said:
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
Click to expand...
Click to collapse
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
kim621973 said:
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
Click to expand...
Click to collapse
While Knox is a problem, the bootloader is the booger that won't allow return to 4.1.2. Sammy hosed us on that little bit of trickery.
If my wife didn't have a GS3 that I maintain I might have OTA'd. I have been watching their "upgrade" process for a while and knew that there was trouble in the OTA.
It will be painful for a while as people migrate in with problems that have been covered several times. We'll get through it.
Hastily spouted for your befuddlement
I got my LG G4 from Verizon about a year ago. In January, my phone shut itself off and got stuck in a bootloop, just showing the LG screen then resetting. My boyfriend was able to get it to turn back on using the USB debug mode but he's now in Asia until June. I came back from a long trip to find that that no longer works. I downloaded SDK and tried doing a reboot again and it still just reloops the LG screen. The phone is running stock firmware, bootloader hasn't been tampered with, and no attempts to unlock or root the phone have ever been made. Is there anything else I can do before resorting to the factory reset? If I can't fix it, is there a way to get the data onto a drive before resetting it?
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Coddeh said:
Hi Guys,
As the title says my S20 Ultra has managed to get itself stuck in a boot loop as of last night. I can boot into recovery mode, download mode and safe mode. When booted into safe mode it will stay on the home screen fine. However if i try to unlock the phone to use it, it crashes and reboots into a bootloop.
If I just plug in a usb to access the files via usb in safe mode before the phone is unlocked the phone is not detected (device manager detects a samsung device but nothing in file explorer most likely because the usb services haven't started up yet and won't until the phone is unlocked).
Im sure a factory reset will solve the bootloop issue but I don't want to lose the date on the phone until it's backed up (recently renovated our house and I have pictures on there of before and afters I would like to keep).
Is there a method I could use to get the data back other then sending the phone off to a recovery service? Maybe something that doesn't void the warranty of the phone but if there is no other choice I would consider voiding the warranty. I used to install custom roms on all my old android phones but never felt the need to on this one. I'm fairly tech savvy so am Just looking for ideas.
Cheers
Click to expand...
Click to collapse
Try flashing the same firmware you're currently running using Odin and HOME_CSC to keep your data, possible it will replace and fix the corrupted files causing the bootloop
So last night I tried what you have mentioned. It didn't change anything unfortunately.
I then thought it might be worth trying an older firmware. I tried rolling back to the previous firmware and then to android 10. Both of these ended up making things worse and it would boot loop at the android startup screen.
Luckily I managed to get back into Odin mode and put the current firmware back on and I'm now back to square one.
OK so I have had a thought. I've seen that some people have managed to establish a USB connection to thier device through TWRP and managed to backup their data through that. I've also seen that on older phones you can use odin to only flash TWRP and then boot into it. I'm not sure if things have changed drastically and you are unable to do that on the S20 ultra now. After my data (pictures and videos) was backed up I could then reflash the recovery back to stock and do a factory reset to fix the bootloop.
Does this seem plausible?
Hi everyone, so long story short. my galaxy A50(SM-A505GN) was suddenly in a bootloop.
long story, the phone is doing just fine, everything works well. I was in a middle of a call when it suddenly froze then restarted itself an then voila it's stuck on the "Samsung Galaxy A50 secured by Knox powered by android" Logo WHICH never shows up on startup before. it only shows the samsung logo on startup before, there is a pending update on the notification bar but I have not installed it yet so I don't think that is the culprit. no apps installed before the boot loop. if you need any more info about the phone that I might have missed just mention it. I'll try to answer it the best that I can.
Things I have tried:
wipe cache
wipe data and cache
flash latest stock rom (dumb thing won't let me downgrade)
things the phone can do:
go into recovery mode ONLY if the USB is plugged to a PC/laptop
go into download mode from recovery mode
force restart with volume down + power button
it is still on boot loop even after flashing the stock rom. Is there anything I can do to this phone WITHOUT returning it to Samsung, because we all know why that idea sucks. btw, I live in the Southeast Asia region where the warranty for mobile phone is sooo bad.
more than willing to flash custom ROM into it just so it could return to being usable but unfortunately I can't unlock the bootloader without the doing the OEM unlocking thing on dev options. any suggestion on how I could fix this damn phone would be so much appreciated. I really can't afford a new one right now. Thank you.
This happened with me too. Did you update the security patch which came in as OTA update ?
I think this happened because of the security patch.
youhavereachedsahilkalra said:
This happened with me too. Did you update the security patch which came in as OTA update ?
I think this happened because of the security patch.
Click to expand...
Click to collapse
there is a pending update but I have not downloaded nor install it. looks like I will have to wait next month and try flashing the latest patch.
Bro, install recovery 3.4 and the rom fresh. i had some problem. i fix it intro to recovery with download mode, and go to recovery