I have a Note 4 and I was very satisfied with the performance until a few weeks ago, an upgrade to Android 6.0.1 was downloaded and applied.
It seems the update failed and despite I'm now in Android 6.0.1, the phone is working very erratic. Sometimes it freezes for a while (10 seconds, 30, 1 minute, 2 minutes) and then just continues as normal (when it freezes for more than a minute, it goes directly to lock screen ). Sometimes it says some app or system process (touchwiz and the like) has failed and sometimes it simply reboots without any reason. I have restarted it in secure mode but there is no difference.
I have uninstalled all downloaded apps but there is no difference. I have reset it to factory defaults but keeps failing.
I have downloaded latest 6.0.1 Firmware from Sammobile and flashed it with Odin but the fail is still there.
One thing I have noticed is when I start in recovery mode (power+home+vol up), instead of the recovery menu, the android robot appears and the text installing update. It goes for a while, then crashes (robot with red triangle) and then the recovery menu appears. This happens every time I start in recovery mode so it looks like there is some update that was applied (since I have 6.0.1 instead of 5.x) but only partially.
Any help?
is there a way to revert it back to Lollipop?
Hi!
Same thing happened to me. Connect to a computer and use Samsung Smart Switch to do an emergency recovery.
But the phone will be erased.
After that, my Note 4 got even better than before!
Good luck!
Tried Emergency Recovery but phone doesn't show up in the list, so I tried Update Firmware. It told me the firmware I have would be replaced by current version (The SAME version) but I went ahead anyway. Firmware was downloaded from internet, phone booted in Download mode and Smart Switch copied the firmware to the phone, then restarted, installing... Error Message: "No Command", nothing else.
I removed battery, rebooted and error message appeared telling there was a problem with firmware update and I would need to use emergency recovery from Kies (I understand I have to use Smart Switch, no Kies). So I connected it again to Kies and opened Emergency Recovery but once again, it doesn't appear in the list. So trying again with Firmware update. If this doesn't work, I'm afraid I have a very expensive paperweight
Failed again. At 25% update, Download screen showed:
ODIN: flash write failure
A window in Smart Switch tells me something went wrong and offers me Emergency Recovery. It also tells me I have to write a recovery code if using another PC. The recovery code is blank. not a good signal.
Again, Emergency Recovery is showing nothing in the list of devices
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
jedikalimero said:
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
Click to expand...
Click to collapse
please keep posting your observations, i am on the verge of trying flashing 5.1.1 myself.
would be great to know if this resolves our issues.
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
I went to the repair service. The guy there didn't know how to fix it an told me to send it to Madrid for repair. But I haven't sent it yet for two reasons. The phone is still under warranty (as ANY OTHER Note 4 bought in the EU), but first, he told me it would take 25 days to repair (this is Spain, you know. In UK it would take 3 days) and second, my front glass cracked so I had to take it to a repair shop to replace just the glass for 30 euros instead of the 200 euros it would have costed to replace the whole (and totally functional) screen officially. So I'm afraid they would find out the glass was replaced and take this as an excuse to void my warranty. In older models you could replace the glass and nobody would notice it, but in the Note 4 you have to break a copper heat dissipation foil that lies between the back of the screen and the metal frame in order to disassemble the phone.
jedikalimero said:
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
Click to expand...
Click to collapse
so sad!
Related
I have this galaxy s7 edge from sprint, from day 1 i was using it ok but there was an update available so i went for it OTA. the phone completed the process correctly, everything was fine. Then i powered off the phone (i had not done that since i got, kept it on and plugged during the night) that's when it started to bootloop into the logo.
I tried to flash the stock firmware, as the phone is able to go into download mode. Unfortunately as soon as the phone restarts, it wants to install an update, then the process stops at 25% or 32%, it changes every time.
Any luck ? I got same problem with my s7 edge
Do you all have disabled apps? Did you root? If you install an update with certain apps disable that's known to cause a bootloop but that's just my guess. If you say you don't have disabled apps I don't know then.
Sent from my SM-G935P using XDA-Developers mobile app
ivn260 said:
I have this galaxy s7 edge from sprint, from day 1 i was using it ok but there was an update available so i went for it OTA. the phone completed the process correctly, everything was fine. Then i powered off the phone (i had not done that since i got, kept it on and plugged during the night) that's when it started to bootloop into the logo.
I tried to flash the stock firmware, as the phone is able to go into download mode. Unfortunately as soon as the phone restarts, it wants to install an update, then the process stops at 25% or 32%, it changes every time.
Click to expand...
Click to collapse
Before flashing the stock firmware, try this: Boot into stock recovery & perform a factory reset. Then boot into Download Mode & flash a firmware again.
Sent from my SM-G935U using Tapatalk
Same issue. Factory reset from revovery. Downloaded lastest firmware for the model from SamFirm. Flashed with ODIN. Rebooted phone then stuck at 32% system update then erasing, now stuck on SAMSUNG logo. Cannot get into recovery mode by pressing Vol Up and Home button. Phone will just not respond. Will only respond once battery dies. all Lights are still on including blue light on top of phone. Any help?
ivn260 said:
I have this galaxy s7 edge from sprint, from day 1 i was using it ok but there was an update available so i went for it OTA. the phone completed the process correctly, everything was fine. Then i powered off the phone (i had not done that since i got, kept it on and plugged during the night) that's when it started to bootloop into the logo.
I tried to flash the stock firmware, as the phone is able to go into download mode. Unfortunately as soon as the phone restarts, it wants to install an update, then the process stops at 25% or 32%, it changes every time.
Click to expand...
Click to collapse
hello i had this problem while i was trying to root and unlock the phone
this is what i did hopefully it works for you too
1* download the latest firmware according to your android version
use odin3 v3.13 patched version
2* boot into boot loader
chose Bl on odin and the pit file , uncheck re-partition
and press start , that will get your phone unbrick then flash the ap file and then cp and csc that shoud do the job :good:
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
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....?!
My S7 edge had been acting weirdly for a few weeks, things like random restarts once a few days so I didn't pay much attention and over excessively heating up to 50/55 degrees (I usually checked the temperature through CPU_Z), and just a few hours ago I ran into problems like the phone restarting on its own, never getting past the samsung logo on boot, so I did the normal thing everyone else would do and just factory reset the device through recovery mode, a point to add here the device took an absolute age to load into recovery mode, this wasn't a case of bad key combination or anything like that, the device would load this the dmverity tree hash verification thing and sit there for a good 2-3 mins which is unusual, same thing happens with factory reset takes an absolute age and comes back with the following text-:
"E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done...
Data wipe failed."
booting up the device in this state would show up with an error "Device storage corrupt" with a " reset device" button in the bottom of the screen which didn't respond to any touches which was weird as well because holding the power button and then selecting the power off option worked with no issues so it wasn't an issue with the touchscreen.
searching for a solution on google led me to flash a official firmware that I downloaded from updato, just a heads up my device has never been tampered with or had any kind of software modifications this includes flashing any roms or even official firmwares before, so I download the firmware and flashed it as usual this is the firmware that I flashed through odin 3.12.3 firmware version was G935FOJV1DQAV also my device model is SM-G935FD while the firmware I flashed was for SM-G935F but this shouldn't be an issue because when I usually got updates over the air on the device they would be for SM-G935F so if there were any issues with this they should have popped up a long time ago, so everything went smoothly and the phone booted up again as usual, did the initial setup and adding accounts, recovery everything, hooked up the charger and left the phone to download all the necessary stuff through samsung and google cloud recovery, comeback after a few minutes to find that the device just wouldn't respond to the power button or the home button to wake the device up but the led on the phone was flashing in blue color which means I did receive some notifications, so I hard reset the phone by holding down power+volume down key, same issues pop up like before the firmware I flashed getting stuck on the boot samsung logo, went back to recovery to do another factory reset again it keeps freezing on the dm-verity tree hash thing, but this time the factory reset happens properly with no errors, but the device doesn't boot up at all, gets stuck on the samsung logo and the led on top starts flashing in several different colors, just like when you boot up a brand new S7 edge.
As a last ditch effort I try initializing the device through smart switch, everything goes normally but when the flashing process starts it gets stuck on 7% indefinitely, tried everything else but to no avail, tried flashing through odin again but it gets stuck on the same point as smart switch, tried installing the firmware in parts through odin again gets stuck on the same point when flashing AP but other parts get installed without any problems, download mode boots up fine, recovery mode now boots up very slowly with a dm-verity error "E:failed to mount / system (invalid argument).
I have 1 month warranty left on my S7 edge from where I purchased it, I want to send it back for a refund or a replacement but the only thing thats kind of worrying me is that in download mode the knox switch hasn't been tripped still shows 0 (0*000), but shows system status as custom, will this effect my warranty claim if they check my device?
TreekoX said:
My S7 edge had been acting weirdly for a few weeks, things like random restarts once a few days so I didn't pay much attention and over excessively heating up to 50/55 degrees (I usually checked the temperature through CPU_Z), and just a few hours ago I ran into problems like the phone restarting on its own, never getting past the samsung logo on boot, so I did the normal thing everyone else would do and just factory reset the device through recovery mode, a point to add here the device took an absolute age to load into recovery mode, this wasn't a case of bad key combination or anything like that, the device would load this the dmverity tree hash verification thing and sit there for a good 2-3 mins which is unusual, same thing happens with factory reset takes an absolute age and comes back with the following text-:
"E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done...
Data wipe failed."
booting up the device in this state would show up with an error "Device storage corrupt" with a " reset device" button in the bottom of the screen which didn't respond to any touches which was weird as well because holding the power button and then selecting the power off option worked with no issues so it wasn't an issue with the touchscreen.
searching for a solution on google led me to flash a official firmware that I downloaded from updato, just a heads up my device has never been tampered with or had any kind of software modifications this includes flashing any roms or even official firmwares before, so I download the firmware and flashed it as usual this is the firmware that I flashed through odin 3.12.3 firmware version was G935FOJV1DQAV also my device model is SM-G935FD while the firmware I flashed was for SM-G935F but this shouldn't be an issue because when I usually got updates over the air on the device they would be for SM-G935F so if there were any issues with this they should have popped up a long time ago, so everything went smoothly and the phone booted up again as usual, did the initial setup and adding accounts, recovery everything, hooked up the charger and left the phone to download all the necessary stuff through samsung and google cloud recovery, comeback after a few minutes to find that the device just wouldn't respond to the power button or the home button to wake the device up but the led on the phone was flashing in blue color which means I did receive some notifications, so I hard reset the phone by holding down power+volume down key, same issues pop up like before the firmware I flashed getting stuck on the boot samsung logo, went back to recovery to do another factory reset again it keeps freezing on the dm-verity tree hash thing, but this time the factory reset happens properly with no errors, but the device doesn't boot up at all, gets stuck on the samsung logo and the led on top starts flashing in several different colors, just like when you boot up a brand new S7 edge.
As a last ditch effort I try initializing the device through smart switch, everything goes normally but when the flashing process starts it gets stuck on 7% indefinitely, tried everything else but to no avail, tried flashing through odin again but it gets stuck on the same point as smart switch, tried installing the firmware in parts through odin again gets stuck on the same point when flashing AP but other parts get installed without any problems, download mode boots up fine, recovery mode now boots up very slowly with a dm-verity error "E:failed to mount / system (invalid argument).
I have 1 month warranty left on my S7 edge from where I purchased it, I want to send it back for a refund or a replacement but the only thing thats kind of worrying me is that in download mode the knox switch hasn't been tripped still shows 0 (0*000), but shows system status as custom, will this effect my warranty claim if they check my device?
Click to expand...
Click to collapse
Having the same issue. anyone help? did you manage to solve this issue?
Hi,
My galaxy S4 decided to poop itself yesterday. I was browsing my emails and the phone restarted by itself. . but then it kept restarting over and over again (Boot loop). The phone felt hot, so i took the battery out and left the phone for a while.
Once i put the battery back in, the phone kept boot looping. I managed to get it into safe mode and make sure all my photos were safe – I've just returned from a holiday in Hawaii, so this was very important to me.
After i was able to make sure photos were backed up on the computer, i cleared the cache partition and even did a hard reset. The phone kept boot looping. My phone now gets stuck on the "Samsung Galaxy S4 GT I9505" start up page. I read about issues with the power button, so even atempted to open the phone up and wiggle the power button around a bit by squeezing it with some tweezers. This made no difference. I've even swapped batteries and tried charging it.. this also doesn't work. Currently my phone has the "Samsung Galaxy S4 GT-I9505".
I have been on whirlpool forums and it was suggested that i reinstall the firmware through odin.. i did, but with great difficulty and many attempts. My phone was able to boot up and i was able to send one message and make one phone call before it went into bootloop again or just switches off and doesn't want to be switched back on again. When the phone was on, no sound was apparent when a phone call/text message came through for testing. I've retried dowloading the software on odin, but when i try to switch my phone on it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
I've also tried putting the phone on the charger and no sound or green battery coloured animation comes up on the screen now.
Please somebody help
It was the latest stock firmware from sammobile.com that was flashed to the phone? Was the phone factory reset from stock recovery before booting the phone after fllashing with Odin?
As far as I know it was the latest unbranded firmware from sammobile.com.
A factory reset was one of the first things I did after starting the phone up in safe mode and trying to recover files.
The phone has never previously been tampered with. I've only ever upgraded the software through WiFi or Samsung kies. Using Odin was a learning experience for me.
Maybe the factory reset needs to be done from the recovery screen rather than from the ROM settings?
The factory reset was originally performed from the recovery screen. I can no longer get into recovery mode though. It only seems the phone wants to get into download mode
Have you tried flashing a ROM designed for a particular carrier in your country?
This is going to sound silly.. But I thought that's what I was doing when I went through Odin and got the firmware from sammobile.com
Which version of Odin and firmware was flashed?
What errors occurred during the flash process according to the Odin log?
Tried flashing with a pit file?