I have been reading on some of these forums regarding the Note 4 possibly having hardware or software failure in January and February of 2016.
I was using my note 4 last week with stock firmware, never been rooted or changed in any way and suddenly it started randomly rebooting until it finally wouldn't turn back on.
I tried all various groupings of button combinations which did nothing. I tried pulling out the battery and holding down the power button for a minute and then put the battery back in which got me to Odin mode (downloading do not turn off target). I had a MMC read failure and it would not boot up.
I tried to use odin to re-install new firmware but kept getting the error no Pit to partition (i do not know if it was my lack of ability or software/hardware problem). At this point i have given up but then read something about cooling down the phone so i stuck it in the fridge for 5 minutes. I took it out and it actually booted up normally.
Now i notice it is slow and laggy sometimes and still randomly shuts off (it was only using about 1.2G of 1.8G of ram it usually was previously).
Has anyone else had similar issues or found fixes to the problems described above?
I am having similar issues with a note 4 Verizon phone.
I bought it from a friend fairly cheep because it had been dropped but only cracked the camera lense cover.
At first it would boot up and allow me to activate then all the freezing started and random shutdowns. So I figured it was a software issue.
I put it in USB mode flashed with Odin and continually fail.
I tried flashing the recovery firmware and it passed.
Then tried flashing stock fw
With fail again.
Now the phone won't do anything. No recovery mode or USB mode just black screen.
Although while holding the power and volume buttons and plug into USB my pc will pick it up.
But phone does nothing
Sent from my SM-G900V using Tapatalk
If you pc picks it up, can you use adb to interact with it?
Related
So here's the story.
I have a Note 3 I acquired that was in pretty rough shape. According to the person that gave it to me, they had tried to flash a rom that was unstable and crashed the device causing a boot loop he couldn't recover from. So he reported it lost and got a new one.
The first thing I tried was installing stock firmware using odin. This at least allowed the phone to fully boot up. But, it would still restart after about 10 mins of usage. The next thing I tried was flashing TWRP on to the phone and doing a complete wipe of the phone. Then I flashed the stock firmware using odin.
This has brought the phone more or less back to a usable state. However, there are new problems.
The phone reboots at random. Usually after being on for an hour or longer. Also, the phone won't power down. When I long press the power button and select power off, the screen shows that it's powering down. The phone stays on the power down screen for about 2 mins then the phone reboots.
I've tried a factory reset and reflashing the stock firmware.
Alright, so my dad purchased a new AT&T Galaxy S5 (Unlocked) from NewEgg.com and received it yesterday morning.
At 9am he powered it up, setup his Google account and get to the home screen, no issues.
at 10am he went to Cricket Wireless and received his SIM card, however, the phone was not activated because the "expert" wasn't in until 2pm.
He had the phone charging while on a bike ride and upon returning the phone started doing the boot loop where it shows the Samsung logo for several seconds, goes back, vibrates once, pause, vibrates a second time and repeat.
He went to Cricket after 2pm and the phone was still doing the boot loop and then somehow it stopped. The "expert" took the phone, said it was activated, took the battery off, wrote some numbers down, and from that point on, it has been doing boot loop since.
I've tried getting into the Recovery Mode (Vol Up + Home + Power) and the blue letters recovery booting.... display and I let go and it just goes back to the boot loop process. I've done this numerous times on many devices. The power button is fine as is the volume button.
I've also tried Odin with several Stock AT&T Rom's and each one errors out at system.im.ext4 each time. I've tried this on two Windows 7 machines and one Windows 8 machines with numerous USB ports.
I have also tried doing the firmware upgrade via Samsung Kies 3 and that also fails.
I've been looking up an down for similar problems like this, but can't seem to find anyone else with the same symptoms.
Can't seem to get into recovery mode.
Can't seem to flash a Stock ROM to it.
Can't seem to get Kies to flash Stock ROM either.
Any ideas what I'm failing to try? I've added some screenshots to assist.
Zero2Cool said:
Alright, so my dad purchased a new AT&T Galaxy S5 (Unlocked) from NewEgg.com and received it yesterday morning.
At 9am he powered it up, setup his Google account and get to the home screen, no issues.
at 10am he went to Cricket Wireless and received his SIM card, however, the phone was not activated because the "expert" wasn't in until 2pm.
He had the phone charging while on a bike ride and upon returning the phone started doing the boot loop where it shows the Samsung logo for several seconds, goes back, vibrates once, pause, vibrates a second time and repeat.
He went to Cricket after 2pm and the phone was still doing the boot loop and then somehow it stopped. The "expert" took the phone, said it was activated, took the battery off, wrote some numbers down, and from that point on, it has been doing boot loop since.
I've tried getting into the Recovery Mode (Vol Up + Home + Power) and the blue letters recovery booting.... display and I let go and it just goes back to the boot loop process. I've done this numerous times on many devices. The power button is fine as is the volume button.
I've also tried Odin with several Stock AT&T Rom's and each one errors out at system.im.ext4 each time. I've tried this on two Windows 7 machines and one Windows 8 machines with numerous USB ports.
I have also tried doing the firmware upgrade via Samsung Kies 3 and that also fails.
I've been looking up an down for similar problems like this, but can't seem to find anyone else with the same symptoms.
Can't seem to get into recovery mode.
Can't seem to flash a Stock ROM to it.
Can't seem to get Kies to flash Stock ROM either.
Any ideas what I'm failing to try? I've added some screenshots to assist.
Click to expand...
Click to collapse
You probably have a locked bootloader, i don't have any personal experience but i've heard these american companies are infamous for locked bootloaders - locked meaning that you can't flash anything without using an unlocked BL.
You can look around see if there are any unlocked bls for at&t.
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....?!
Im so lost with this, im all stock but one day my phone just freezes then bootloop, I would be able to get it work by just leaving it and let it drain itself since it will be boot looping and lock me out completely, like the power button + low volume button would not work even after 10 minutes of holding it, would not boot to download or recovery mode, just the soft touch keys light on and the blue LED.
I reflashed my ROM from sammobile yesterday but did it half-effort, just dirty flashed it but it seemed to reformatted my phone anyway, after reflashing it, everything seemed to work properly for 20 hours and then now im back to this piece of ********* boot looping...
S7 Edge
running the Australia unbranded XSA-G935FXXS1DQG4 from the branded G935FXXS1DQG5,
would flashing de-branded affect this? or this is hardware?, one thing I did that I think was a mistake is that I chose to restore from old device, can apps cause this?
the very first time this happened, I plugged it in to charge then crash and bootloop.
UPDATE:
Things I've tried,
-Booting with NO sim card and SD Card
-Wiping cache and partition then reflashing stock XSA and OPS firmwares
im convinced that this is a hardware issue and will go to Samsung.
mine does this too. crashes then gets into a bootloop at the Samsung logo. I usually try holding the lock and volume down button. I factory reset the phone once but it still keeps happening, this started happening around 4 weeks ago
Guys your Main/Mother-boards are broken.. u need to replace it, or send back to Samsung..
Damn! Crash reboot samsung logo
Damn you say broken mother board...
did this. Press vol down, power button and home key...hmmm... i think...pressed so many combos hard to tell themapart
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...