Hi,
After a LineageOS update, my Samsung S5 (G900F) was working and suddenly shouted down. I tried to restart it but it was booting in loop (always without passing through the first Samsung Galaxy S5 logo). As I wasn't being able to restart it I tried to fix it by installing the stock rom through Odin. It installed successfully and the phone rebooted with images in the screen. If I touch the phone I can hear the touch working and volume also works but I don't have image, not even while booting the phone.
Now, the only way I have to see image (in the download mode only) is to take off the battery for a few minutes and then restart the phone while pressing the download mode buttons.
I tried several times to install the stock rom through odin but the same thing happens everytime so I am still without image.
Any suggestions?
Thank you. :good:
Related
I have a Note 3 (SM-N9005) running Lollipop 5.0 I tried to root (n900-cwm-recovery-6.0.5.0-kk(0812) via Odin. It PASSED) but couldn't get to custom recovery. It would only go to download mode with a message at the top of the screen saying "could not do normal boot". Tried re-flashing 3 times but still same result
So i re-flashed stock ROM with the idea to start again. Got a PASS according to Odin.
But now the phone mostly freezes at the Samsung boot screen and then shuts down. Occasionally it makes it all the way to starting but then shuts down again. Any ideas please??
Thanks
PS. I can get to stock recovery and download mode
Hi Guys,
I am facing a peculiar kind of problem in my phone (G900F) since yesterday.
What happens is that, if I tried
i) To restart my phone from the phone (reboot menu), the phone stuc in boot screen and then vibrate twice then after 5-10 sec the phone start rebooting all along once again with 2 vibration and this process keeps repeating until I pull out the battery.
ii) To access recovery (both hard- key combination or from reboot to recovery option in phone), the phone reboots and it stays in the initial screen for about 45 seconds and then the screen went black and freezes there until I pull out the battery.
iii) To access download mode ( both hard- key combination and reboot to download mode option in phone), there seem no problem.
The weirdest part is that, if I remove the battery for 5-10 min and re-insert the battery and do any of the above options; the phone reboots and i get the home screen loaded successfully with no problem . I can also get into my recovery after this 5 mins switch off just like the above. I also found the phone lags a bit in this home screen.
I almost did all the combination to get off this problem (stated below) but I keep getting this problem again and again.
I was in Sixperience v 3.1 with Pheonix Kernel v 10 and Philz CWM recovery and tried the below to try to fix the issue
1. Re-flashed Kernel from Recovery (Also, tried to re-flash kernel after uninstalling Xposed but no use)
2. Re-flashed Modem and Bootloader from ODIN once again (G900FXXU1CPF7_BL_G900FXXU1CPB8_MODEM_LTE.tar)
3. Reflashed ROM once again as a fresh install through Philz recovery.
4. Restore the cwm backup from recovery (which was backed up a week before.)
5. Flashed Samsung Stock MM ROM (G900FXXU1CPFH_G900FPHN1CPFD_PHN.tar.md5) as a fresh install.
After this stock ROM installation is done, the phone struck at SAMSUNG flashing logo and the blue LED keeps glowing for more than 30 mins)
Nothing works. ? Any idea on what is to be done to fix this issue? I am not sure, what i did but this problem keeps coming even after trying of all of the options since yesterday.
Please help to with your expertise.
Device was working fine until OTA update to 6.0.1 (MMB29M.G900FXXU1CQDA). It wouldn't boot past the Samsung logo.
I downloaded that same firmware (and the one before) and flashed it via Odin 3.12.7, however situation remained the same.
Flashed TWRP 2.8.7.0 and then PhoenixROM 15.0 and device booted fine. However it would always reboot after display stays off for 3 seconds.
Flashed TWRP 3.1.0-1 and then LineageOS 14.1-20170802 and device booted fine again. The reboot problem remained the same.
The reboot problem is NOT present while device is connected to a PC, however it is present while connected to an AC wall socket.
Each time the display goes off the device stays off for 15 seconds before booting again.
Anyone got similar experience, any advice?
eqagunn said:
Device was working fine until OTA update to 6.0.1 (MMB29M.G900FXXU1CQDA). It wouldn't boot past the Samsung logo.
I downloaded that same firmware (and the one before) and flashed it via Odin 3.12.7, however situation remained the same.
Flashed TWRP 2.8.7.0 and then PhoenixROM 15.0 and device booted fine. However it would always reboot after display stays off for 3 seconds.
Flashed TWRP 3.1.0-1 and then LineageOS 14.1-20170802 and device booted fine again. The reboot problem remained the same.
The reboot problem is NOT present while device is connected to a PC, however it is present while connected to an AC wall socket.
Each time the display goes off the device stays off for 15 seconds before booting again.
Anyone got similar experience, any advice?
Click to expand...
Click to collapse
Flash stock lollipop and report back.
godkingofcanada said:
Flash stock lollipop and report back.
Click to expand...
Click to collapse
Did. Same case as with Marshmallow.
However there has been further issues, seems the phone can't be saved.
After flashing Lolipop the phone wouldn't boot via power button, but instead I need to boot it to Download mode and hit cancel.
This however makes it go to Recovery mode. Trying to boot the system from Recovery makes it power off.
Tried flashing TWRP back and when I enter it, the device keeps choosing random options rapidly, as if it's constantly detecting touch across the screen.
Therefore I'm no longer able to flash LineageOS back.
Gave up on the device in the end, seems to be defective.
eqagunn said:
Did. Same case as with Marshmallow.
However there has been further issues, seems the phone can't be saved.
After flashing Lolipop the phone wouldn't boot via power button, but instead I need to boot it to Download mode and hit cancel.
This however makes it go to Recovery mode. Trying to boot the system from Recovery makes it power off.
Tried flashing TWRP back and when I enter it, the device keeps choosing random options rapidly, as if it's constantly detecting touch across the screen.
Therefore I'm no longer able to flash LineageOS back.
Gave up on the device in the end, seems to be defective.
Click to expand...
Click to collapse
It sounds like the touch screen is going wonky. Or the mobo has an issue. You could get it diagnosed at a shop reasonably cheap
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.
My Galaxy S4 VE (GT-I9515) crashed. (the screen went black) It was not rooted and ran the latest Andoid 5.0.1 ROM.
When I turned it on, it went into a bootloop, randomly crashed during booting, or turned on normally. I removed sd and sim card and tried a different battery. Furthermore I tried to boot into recovery mode and wiped the system data and the cache. It did not help.
Sometimes it was not possible to get into recovery mode because the phone's screen went black and it rebooted.
Then I tried flashing multiple stock ROM files using Odin, but it did not solve the problem.
After that i tried rooting the device and installed a custom recovery (TWRP), but i still got random crashes during booting and sometimes it got stuck showing the samsung boot animation. The only things that work reliably are the Download Mode and the charging animation.
Now, what can I do to fix my phone?
I read a bit about flashing a .pit file but I don't think that will help?
Is this a hardware or a software issue?
How can I find out, what caused the problem?