Even before I had issues it would stay relatively warm when just charging it at 5W (it still does that when it's turned off) so I started suspecting liquid damage (prior experience) or the battery starting to show its age even though it's only been charged about 300 times. This all started after I flashed LOS on it where hwc was disabled. The phone had pretty much stayed unused until late 2021 and was meant as a dev/backup phone.
After a second hard crash it stopped trying to boot and will now only enter Download mode and nothing else. Prior to this I only had to reflash it, but this time it's not looking so good.
I'm too facing the same, tryin to revive my cousin's s8, which is not even rooted once. Tried flashing stock fw using odin. It just doesn't show samsung logo but still goes to download mode. Any help devs?
Related
Hello,
my Galaxy S4 got soft bricked recently and I am looking for a solution for 5 days now and now I decided to ask you guys for help since I can't find anyone with the same problem.
I had Albe95 LolliROM 9.0 (15/05/16) [HPA1] flashed on my phone for about 3 weeks and everything was perfect.
I was using my phone when it suddenly restarted itself and it got stuck in a bootloop (SAMSUNG animation). After many attempts I could boot into recovery (TWRP) but it would freeze there and I had to remove the battery...
I could also boot into Download Mode so I decided to flash a stock rom (I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_HOME.tar) which I downloaded from Sammobile. Odin would always stuck at system.img.ext4 but again after many attempts it workted and I had success. When it was booting my phone froze at "optimizing apps". So I had to turn it off and restart again, but this time the phone was always freezing at the first samsung logo and wouldn't go further.
I can still go into Download mode but can't flash anything because eather Odin fails (complete(write) operation failed) or my phone freezes. Sometimes when I boot my phone into Download Mode the screen would do strange things like flickering and weird colors would show in DL Mode.
So my problem:
- booting into Download mode after works though it freezes sometimes
- can't flash roms because phone is freezing all the time
The model # in download mode is 9505? Was the phone ever dropped? You're using the original Samsung USB cable to flash?
audit13 said:
The model # in download mode is 9505? Was the phone ever dropped? You're using the original Samsung USB cable to flash?
Click to expand...
Click to collapse
Thanks for the reply.
-yes modelnr is 9505.
-i have not dropped my phone recently. I mean its over 3 years old so of course I've dropped it but never really bad and it has no scratches or anything.
-I've tried different cables and samsung cable was one of them.
I also tried all ports of my laptop even tried another pc
Maybe flash the stock rom with a pit file?
audit13 said:
Maybe flash the stock rom with a pit file?
Click to expand...
Click to collapse
I didn't try this pit file thing because I don't understand the meaning of it exactly..
But after many many Odin flash attempts I got a success with a stock rom 5.0.1.
I think I figured out what the problem is but I can't really tell why it's happening (Hardware broken maybe, but which one?)
So after the flashing the stock rom successfully the phone restarted and started the first boot but it froze during the samsung animation again...
I thought maybe if I try a lot of times eventually it will work, so I tried and tried and it always got stuck at samsung animation. (before every boot I had to remove the battery and wait ca 10 sec because otherwise the phone would not start booting at all)
I did not come further than the samsung animation so I removed the battery and placed the phone (I almost gave up).
But after one hour I tried again and this time it passed the samsung animation and got to the Optimization part of the apps. aaaaand it froze there again.
I thought maybe if I wait again for 1 hour I can pass the optimization part. So I did and it really worked. I got to the startscreen.
So the current problem is:
- The phone boots and makes it to the homescreen and freezes after ca 10 seconds. And also I have to wait for about half an hour or one hour to get that far. If I try again right after the freezing I can't get passed the Samsung logo.
What could cause this freezing? Maybe the cpu has to "cool down" in the one hour of waiting and freezes because it gets to hot? I really don't know what it could be.
Something on the motherboard, likely either CPU, EMMC chip, or GPU, is failing. Why or how I don't know, but I'd have a tech look at it.
Hi All,
I've done a fair bit of Googling about this problem and I'm fairly certain my phones (hard) bricked, but I said I'd post just to make sure.
I have a Galaxy Note 4 N910F running a custom rom ( I cant remember which ROM, I think it was like Kyros Final Edition Note 5 Port or something) , I've been running it for a few months with no problem, last night I was uninstalling various apps from my phone, games etc... when my phone froze and turned off, when I turned it back on it was stuck in a bootloop, showing the galaxy note 4 screen vibrating twice and turning off and repeating.
I tried to boot into TWRP but it just froze on the Note 4 logo with "Warranty Bit Recover Set" or something along those lines at the top, when I took the battery out and put it back in, the phone would no longer turn on, nor will it charge, its completely dead.
I somehow managed to get it turned on again after a while, went into download mode and using Odin installed a stock rom, the install went fine however when the phone restarted after the install it said "booting to recovery" and ended up with a dead Android dude and a "no command message" , I got into recovery mode then and cleared the cache. Then I restarted the phone again and the same thing happened.
Now the phone wont turn on again, I've soft reset it, left it plugged in charging for a while and still nothing. Has anyone experienced something similar to my problem before? Any advice/help is much appreciated.
Thanks
Alan
My phone has been operating perfectly fine up until a video meeting I had today, where the phone went from 100% to 0% by the end. This Axon 7 has had a lot of wear and tear on the battery so that is normal. Today the phone was very very hot during shutdown.
Upon trying to reboot, I am stuck in a bootloop. I have Lineage installed, and tried Stock but that wouldnt even get to the booting animation. I uninstalled Magisk before these tests. Now I am back on Magisk, in LineageOS (latest build) and managed to get back to the booting animation.
Does anyone know any kind of damage that could occur with a hot phone during normal operation (not boot or shutdown) shutting down? A bootloop seems like a strange result.
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
otaconremo said:
If you can still boot to twrp, just stay there and let it charge a bit, maybe 20% + battery level. I experienced this situation twice already.
The first one I experienced this, it won't even boot or even charge while it's off. I even opened up the phone to reconnect the battery. The second time, I was able to boot to twrp. So I let it charge while in twrp. HTH
Click to expand...
Click to collapse
This was the solution, however, along with something else.
The phone only charged correctly in TWRP, so I advise that. Definitely uninstall magisk so it doesnt patch other installs (I've noticed its installer gets called every time I flash a rom). I still had bootloop so I assume all my hard-resetting didnt help. I got it to fully boot on Bliss, but since I kinda miss Lineage I may return to it later today. (I love my "0% brightness" and blue light filter among other lineage features).
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...
Please help! My S5 Neo was in a drawer for a few months after the LCD got smashed. I recently bought a new LCD assembly and connected it to make sure it worked before fitting and it was fine. However, the phone immediately started doing a software update but was interrupted after a few seconds as the battery was dead. Now the phone won't power up or boot into download mode or recovery. When I plug the phone in to its charger, the LED flashes red but nothing is displayed on the screen. I had a new battery for it and charged it in another device but still no joy. I've been messing around with old galaxy phones for a couple of years now, flashing custom ROM's etc, so I wanted to just re-flash a stock ROM into it but there's no way I know of performing this without getting the device into recovery or download mode. Does anyone have any ideas? The device is totally stock and hadn't even been rooted. I'm currently using an S4 Active running Lineage OS 17.1 so I'm not desperate for a phone, but I loved my S5 and really would like to get it up and running again. It never once had any problems.