Hi all. I recently fixed up my old G900F that had been sitting in my closet for years in need of a screen replacement. All went well with the repair but after booting up the phone, it goes through the android optimizing apps screen, but then the device reboots and just sits on the Samsung boot animation. Occasionally the device will vibrate and the recents and back button light up, almost as if the device booted successfully, but it ends up staying in this loop. I let the device keep looping for over an hour but it still never booted successfully. I have also tried to install other stock Roms using Odin, which flash successfully, but do the same loop.
Any help would be appreciated. Thanks!
Did you replace the battery?
It may not have enough available watts to boot up. The current draw on boot up may be heavy...
Also clear the system cache.
If all that fails the firmware image may have been corrupted, factory reset or reflash if that fails, but replace the battery first.
If that fails the mobo may have been damaged by what broke the display. Any impact sufficient to damage the display or bend the frame can take out the mobo as well.
Related
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
PIT files
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
Is the battery original? If so, it's possible the battery could be reaching its end.
Reddog090 said:
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
Click to expand...
Click to collapse
New phone. Opened the box and this is what's been happening.
The phone stays in a bootloop (first screen, followed the the blinking Samsung logo, back to first screen - repeat).
After a while, sometimes, it actually boots into Android. I see the Welcome screen that is seen at first boot on new Samsung devices. At this point, I can tell the phone is really hot right above the SIM slot (no SIM in phone, nor memory card). It stops responding to touch and gets stuck. I have to pull out battery to restart.
Once it restarts, it's back to the bootloop. Then again after some time it might randomly go into Android, get hot, reboot.
Is this a hardware issue? Or is this fixable?
I've already:
Flashed stock MM
Reset
Wiped cache
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
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...