hello!
some time ago i talked with my s4 (for 1+ hour)and charged the same time and phone started reboot randomly.
i have tried flashing other FW, bootloader and recovery - no help. tried to update to lollipop.
after that i broke screen (you may understand why).
changed it
Now i tried flashing stock 4.4.2 FW, recovery and csc, but cant get even into recovery, i always get blue screen.
Is there any way to revive my phone? can't find any information about bluescreen at all. is my hardware dead?
Download mode works (only it).
update: twrp recovery works now, i am able to mount usb storage to pc with no problem, tried to copy backup to phone memory-blue screen again. something wrong is with memory. what is possible to do with this?
update2: phone is working. installed stock lollipop, random reboots and sometimes blue screen again. don't know what to do more. please help anybody
update3: internal storage lost. twrp show internal storage 0B. unable to flash kernel or anything else.
never mind. mainboard is probably dead
Related
This problem started when I moved back to Arya from a 5.1.1 port few days ago. I didn't bother much, cause I keep my phone on always, but whenever I wanted to go to Recovery or reboot the phone it would not boot, would stuck at the Note 3 N9005 logo and I had to do a battery pull to solve the problem, so yesterday I thought about flashing a stock ROM via Odin, and now the phone won't boot at all regardless of the battery pull method!
I can't enter recovery either, it stays at the Entering recovery (SELinux status screen) for a few seconds and then just a black screen with nothing at all. I did flash the TWRP tar image via Odin after flashing stock ROM yesterday, so that I can do a complete wipe, but nah, can't enter TWRP. Download mode however works after a battery pull.
Here is a video, probably the worst quality video you have seen lately, but it still does show the problem :laugh: So kindly tell me what to do! I have a non working phone for over 12 hours now, and I am realising how much I depend on a phone now, that feeling is inexpressible.
how did you solve it ?
Hello, for abou two months I have installed the JDC AOSP firmware on my phone. I encountered many faults and bugs on this rom, and the best of all was the sd corrupt and the last days wasn't even opening. When i touched the screen it was rebooting, so i decided to go back on officiak firmware. I installed two different official firmwares but still the problem remains. On the first touch it reboots. What could possibly go wrong? thank you
Maybe a power button issue?
Does the phone reboot by itself in download or recovery mode?
audit13 said:
Maybe a power button issue?
Does the phone reboot by itself in download or recovery mode?
Click to expand...
Click to collapse
no it was by the little papers i have placed on sim card due to common problem on galaxy s4 "sim card removed". But now there is more important isue. The phone yesterday suddenly turned off and since then it doesn t boot on. It is stuck on galaxy logo and also it is not booting in rocovery mode. I have tried and installed via odin official firmware again it says pass, also today i have installed CWM but still none of these problems solved. Is there anything we can do?
What did you do after installing cwm? Factory reset?
I would use twrp as a custom recovery because cwm has not been updated for a long time.
Hello,
I suddenly started to have big problems with my Note4.
Everything went fine for about a half year (I bought the device from ebay).
Then, suddenly without reason, the phone rebooted.
Each day I got more and more reboots (it starts with freezings and then turns off), and eventually the device rebooted every 5-10 minutes.
From time to time, I got the message "kernel panic!" with "emmc read fail".
So I tried my best with google, nearly everyone said that the emmc flash is corrupted and has to be fixed by Samsung - but because my decive has knox 0x1 triggered, this is no option for me.
I already flashed the Stock Rom again with Odin, after a full wipe of everything.
This didnt change the problem.
So I've read about PIT files and repartitioning, and flashed the PIT file for my SM 910F DBT. The reboots cycles changed from every 5-10 minutes to every 30-60 minutes, sometimes everything was fine for some hours, but there still were these suddenly reboots, and everytime I had to remove the battery to got android booting up again.
I cant remove the battery so many times a day, I thought, so I searched for another solution again - thinking of something like checkdisk, to find the corrupted flash cells and maybe exclude them from use, so they couldnt crash the phone.
I found a description with android adb and "fsck" and thought that this may fix my problem - I tried and it failed, because I needed to root my phone again (maybe).
This is why i flashed twrp again. My phone booted in the new, custom recovery automatically. I wanted to put the zip file for superSU and the file for the custom Kernel (think I need that for root?) on my internal SD, so I wanted to shut down and boot normally - TWRP said "heey you dont have root, should we root your phone now? swipe for yes!" or something like that, so I did as they said.
From now on, I werent able to boot into normal android again. Neither into the recovery mode, the screen just stays black.
I can still boot into download mode - but everytime when I try to flash something with odin, odin starts and after a few minutes, he gives a red line : "flash write failure".
I'm totally upset and dont know what to do anymore. Is my note4 dead now, forever?
If you have any suggestions, please write something. I will be very thankfull, I need my phone very badly :/
Edit:
If I try to boot normalley, I got the message "Firmware upgrade encountered an issue. Please select recovery mode in Keis & try again."
Kies troubleshooting says that it doesnt support my device..
Chocsy
no idea, everyone? still stuck
Look at http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821 , installing wake lock worked for me
Update 2018: emmc chip died later.... Needing wakelock is an indication emmc is going south appearantly
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...
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?