Dear Team,
A brief history
I have a LG G2 D802 with Cyanogenmod 13 installed, It was working fine for a month or so. I used to flash CM13 nightlies and use comfortably. I use the TWRP recovery. Every now and then, there used to be the "error updating from zip" while flashing, but have managed to reflash and make things work somehow. Worst case scenario, I used to put the phone in download mode and flash stock Lollipop rom and then root and flash CM 13.
Current Situation-Problem
Last week while flashing the latest CM 13 nightly, the "error updating from zip" came and then whatever I tried couldn't make the phone boot normally. Finally decided to go into download mode and flash stock Lollipop rom. Unfortunately, half way through the process, the flash tool showed an error and I made the dumbest decision of pulling the usb cable from the laptop. Post that, the phone is always booting to LG boot logo and staying put. I tried rebooting to recovery and putting it in download mode, so many times. Every time I am greeted by the stubborn LG logo mocking me at my frustration
Please let me know your thoughts. If I can manage to put it into download mode somehow, I am confident of bringing my G2 back to life. Kindly assist me with your inputs.
This is my first post on XDA, kindly bear with me in case I have made any mistakes.
Thanks in advance,
TekGru
About 2 months ago I couldn't access Download Mode and I realized that it was probably because I couldn't really turn off the phone, like we can do to any phones with removable battery. So I've searched YouTube and found some videos teaching how to remove back cover and unplug the battery pin. After doind that I've waited about 30 seconds, replugged it and tried to access Download Mode and... violà, success
Note that you don't have to remove the battery, just unplug the pin, so the phone turns off completely.
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!
Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
Hello!
It's my first time here on XDA-Developers, so I hope I can solve my problem here. So, I flashed with ODIN my SM-G530FZ with the Stock ROM, since I had some issues with the phone. I wiped Data, Cache, System and Dalvik Cache via TWRP before doing this. After the flash, I couldn't start the phone anymore. Only when it's connected to my Samsung charger. Then, it started on its own and got stuck at the boot logo. I had to remove the battery to stop the process. But the same thing happened when I put the battery back in. Phone boots up when it's being charged. I tried to go to recovery mode, but nothing happened. Also tried to do the same thing with download mode, but this didn't work as well. I assume that I have bricked my phone pretty bad, so I hope that I can find some help here
Thanks for reading!
I've hard brick my 1H like this before, so I had to make a USB JIGG, made it with 1 dollar in materials.
You can buy these on the internet for about 3 bucks if you don't know how to build one or look up some tutorials.
What they do is force the phone to go into download mode.
Now, the commands for recovery and download mode could have been damaged so this should work unless.. you actually damaged them both from ever working.
ok guys i know there are loads of threads about thois but ive got a slightly differen situation.
my daughter had this phone and then it suddenly tured off and wouldn't turn back on, i managed to get it to boot by disconnecting the battery and plugging it while holding the power down and reconnecting the battery which put me into fastboot then the boot to edl script made the phone boot. i have since unlocked the bootloader and flashed twrp and the reflashed the stock firmware which worked for a few hours but i tried to reboot it and now it wont boot, i can get to twrp but even if i flash the stock firmware it refuses to boot any idea on what i should do to try to get this phone to boot up?
Try to flash a custom rom, as far as i know this problem is caused by a MIUI update.
Joaoovn said:
Try to flash a custom rom, as far as i know this problem is caused by a MIUI update.
Click to expand...
Click to collapse
i have tried to flash a couple but every time i try it fails with error 7 and tried the normal fix but it doesnt help. then anything i do in twrp makes the system unmount and then it cant mount again. the only eay to get to get it to boot again is to take the back off and disconnect the battery and hold the power button down when i reconnect it but ive got no idea why it does this.