I recently installed LineageOS on my S7 Edge because it has a problem with a recent samsung update (the device wasn't able to read the sim card, problem solved by installing Lineage).
It was fine for a couple hours of intensive use, then it freezed. When I rebooted the device it started and was fine but only for a couple of minutes.
After various attemping of simply rebooting the problem persisted, so i decided to reinstall LineageOS, but the device also freezes after 2 minutes of use in Recovery (TWRP).
I then tried to reinstall stock rom in Download mode and the process via Odin was fine (so the smartphone is able to stay on for more than 5 minutes) but when it reboot and start the blue screen with the android robot saying installing system/wiping ecc.. it last two minutes and then freeze.
In TWRP I'm also able to Advanced Wipe and repair System/Data/Cache partitions, and they are correctly mounted.
But every time the device boot (by now only in recovery mode because it doesn't have any rom installed on) it lasts only 2 minutes so I don't have enough time to install any ROM. What can I do?
- Temperature is between 24° C and 33° C
- TWRP 3.2.3-0
- First time installed LineageOS 15.1
- Installed MindTheGapps instead of OpenGapps because during the installation of OpenGapps the device freezed
This looks like a hardware issue to me. My S7 edge recently died just like that.
Related
Hi.
I am using a N910W8 from wind mobile.
I got this phone not too long ago.
My last rom used was cm12.1. Nightly 2016 04 26
A few days ago, it started to hang, I did a system format via recovery and swiped fix permissions (huge mistake)
It booted up and I was installing my apps by play store when the phone hanged.
And now, my phone would only turn on if I pulled the battery out for a couple of minutes. My phone would keep freezing if I tried to install or rom, any rom.
It is unable to boot. Not even to the logo.
It would freeze if I basically turned it on for more than 30 seconds, in recovery or download mode.
Is my device bricked?
I am open to all suggestions and recommendations.
If I am missing any detail, just ask.
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.
Hi
I am stuck with Pulsing blue LED and the "Powered by Android" screen,
have access to both the recovery and the download Mode,
I also have Odin (version 3.13) on my computer along with TWRP (3.1.1 trlte and 3.2.1 version)
My device is a Samsung Galaxy Note 4 N910F bought in shop, no special carrier. It was bought in the Netherlands.
I have tried everything that I have read. The furthest that I can go is the Second Samsung Logo with the Flashing Light
Whenever I try to Flash the stock Firmware for my N910F, everything goes well in Odin but then when the phone reboots, it (sometimes) install the system update until 30% then shows erasing then either crashes right there and then or load the system update bar, completes it then shuts down.
I have tried multiple firmwares, even recovery firmwares. All the same problem. I can see the firmware is flashed, because when I enter recovery mode after I flashed a different ROM, it shows the version I flashed.
I cannot seem to install TWRP because it was never rooted.
Whatever I do, at some point, my phone either gets stuck in a bootloop, freezes with the LED light or shuts down.
And I have also proceeded to use different batteries.
Do you have any options?
Thank you
Heat????
I'm far from an expert here, but I've just experienced a similar problem where my N910F started boot looping / freezing within 15s to 2 min after unlocking. Unfortunately my micro Sd (SanDisk 256GB) was corrupted a week ago, so before doing anything else I did some research (XDA/YouTube) and probably found pretty much what you've found. I frequently change batteries so I could discount that as an issue. Someone suggested using the Samsung Smart switch here https://www.samsung.com/uk/getting-started/smart-switch/, but I haven't used it (yet) so I can't tell. I presume you had the latest firmware from Sams https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/.
My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1.
Good luck and hope this may be of some help.
I've got this problem, too, when using the unofficial Lineage 15.1 rom. SIM death and boot loop. After flashing the latest stock rom through odin, it passed but the screen was black and no system was installed. The blue notification light was constantly stuttering, though. And I couldn't even go to recovery!
When flashing, a 910F can get hot - use a cool temperature room and/or a fan blowing onto the device.
If it's not too late...
Hello,
I'm currently experiencing a bootloop on my phone, it gets to the resurrection remix logo screen during boot then restarts. I've tried booting into recovery and download mode. When I try to boot into recovery it loads the factory reset screen as usual but when I say yes to the reset in order to launch TWRP it just goes to the LG logo, then remix and restarts all over. I got into download mode one time since this started but since then I've made countless attempts to boot into it again and can't.
What I was doing right before this happened is, I recently completely wiped my phone, flashed stock firmware, wiped, then installed resurrection remix. Everything was going perfect, it started no problem, I went through and cleaned up some apps I didn't want etc normal setup steps then I used the power menu to boot into recovery instead of just using the hardware keys and the bootloop started.
Besides the not booting, the other major issue here is that it never stays connected to the pc via adb long enough to do any actions or flash a single file. By the time the pc sees it and adb sees it, I have roughly 2 seconds before it restarts again.
I really really really need any help I can get please ASAP as this is my mom's phone and she needs it for work in 4 hours. This issue started about four hours ago and I've been trying to fix it ever since. I feel like I have looked everywhere on here and through google but probably missed the solution. Before you ask, I'm 28 not a teenager and work in IT as a career for the last 12 years so don't get the wrong impression. She asked me to work on it because I had set it up a few months back with a lollipop version of resurrection remix and magisk, but in the last month or so she was having really poor performance and issues with settings crashing and a few other apps.
I hope you don't need any more info from me, if you do however I'll be here trying to fix it until she goes to work at least. I really could use the help and would greatly appreciate it.
Thank You
So, my G4 Plus got itself bricked out of thin air. I got it last year , unlocked it ages ago, tried some ROMs but decided to go back to stock+ because of pesky camera problems.
Earlier today i was using it normally when it froze and a long vibration started. With no other options I made a hard reboot and it started up again, only it didn't... The boot animation came out all choppy before rebooting itself again. Sometimes it lasted longer, sometimes a bit shorter but it never fully booted up again. Back home I booted into TWRP, flashed cache/dalvik, nothing. It DID get to a full "G" logo, then rebooted itself again. Got a ROM into the SD card, started flashing, froze, reboot again. Tried formatting everything, same thing, froze, reboot.
Just about the only things I can do with it are boot to TWRP and do anything that doesn't involve storage (so pretty much useless) and bootloader.
I also tried just about everything in my power to flash it on ADB/fastboot, but windows itself won't recognize the thing. All sorts of drivers, command lines, windows test mode (for driver certificate shenanigans), nothing worked. I even tried the same on a netbook with win7 since my desktop doesn't have a single USB 2.0 and I heard ADB has trouble with 3.0, nothing again. It doesn't recognize the device at all. They do recognize my girlfriend's G5 by the way, but seem to want nothing to do with my crippled-down-to-bootloader G4+.
I need some help guys, any clues?
Remember:
-Not your everyday bootloop
-Stuck with bootloader and limited usage of TWRP (i can copy files from SD to Internal with no problems)
-Neither Win10 with USB3.0s nor Win7 with USB2.0s recognize the phone at all, at least in this state (every driver out there already installed in every order)