Samsung S5 reboots casually, and then does not boot for a certain period of time - Galaxy S 5 Q&A, Help & Troubleshooting

Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!

hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838

eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.

I will follow up on the battery swap when mine arrives.

hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.

eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!

hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart

Related

[Q] Focus Bricked During Mango Update

Hey guys,
I was updating my Focus earlier today. It went through the process fine until the last restart step of the last update(there were 2 or 3 in total), when it seemed to just hang on the Samsung loading screen. I left it for about 10-15 minutes, but I had to go catch a bus so I had to unplug the phone and go.
Bad choice on my part. Reading online after the fact informed me the Focus could hang for a while on the Samsung loading screen at that step of the update. And now, since I interrupted the update process, its been bricked for me. Whenever I turn it on, it just stays on the Samsung loading screen. It will not be recognized by Zune, or my computer at all. I can get it to go to the hard reset screen, but nothing seems to come of that (I let it go for intervals of 15 minutes, as a few sites advised, to 45, with nothing occuring).
I'm trying leaving it on the Samsung focus screen for a few hours. If that fails, I'll leave it on overnight in the hard reset download mode. I dont have much hope though, and I'm wondering if any of you guys know anything I could try to fix it.
Thanks a bunch.
I'm pretty sure you can get to download mode and flash one of the original focus roms. Just head over to the Focus development section and reflash the rom. Make sure you flash the right one in regard to rev version. The thread will give you all the directions you need.
Figured i'd include the link just to make it a little easier. I hate bricking phones haha. Good Luck
http://forum.xda-developers.com/showthread.php?t=1131022
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
neibl said:
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
Click to expand...
Click to collapse
The low storage issue from adding a mSD card would have been resolved with a simple HARD RESET.
Right now you need a backup of your phone, made before the flashing with Omnia bits. Someone else had this issue, read here. This is also for the specific thread you opened here.
*noob*
My phone froze during the update for 7.5... Zune gave me an error code but wasn't able to write it down. The phone froze on the left arrow and the red "do not remove" symbol for about 30 mins before i unplugged it and turned it off. When i turned on the phone it stayed on the samsung logo and did nothing. i did a hard reset i still got the same thing. Then i took out the memory card and reset, still the same stuck on samsung. Then i called samsung and the walked me through a reset/reformat By pulling out the sim card then Holding down the camera/volume/power at the same time until it vibrates then after just hold down the camera and volume down, click the windows icon to reformat, still stuck on the Samsung logo!!!!
I'm going to try this flash thing... We will see how it goes i'm a noob
Interesting Samsung gave you that advice.
First thing you should have done is connect it with Zune started and it should have continued the process as long as there wasn't a fatal error.
Flashing UCJK2 should work in your case (assuming you have 1.3 hardware).
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
neibl said:
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
Click to expand...
Click to collapse
As I said and the per the info in the thread above, you need to restore from backup. Most likely flashing any rom is not working.
If you tinkered by flashing unknown bits and without taking precautionary measures, don't blame others.
I was not blaming anyone, the only reason i started flashing was because a microsd card ruined the phone down to 15 mb and no matter what method i used to reset the phone it would not leave that state, i tried for month before resorting to drastic flashes.
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
neibl said:
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
Click to expand...
Click to collapse
Zune creates backups of stages before the last update. If you're on Mango, you should have a NoDo backup in Zune. There is no way you can restore without Zune. You can check by going in Zune (when phone connected), Phone (near Marketplace/Social - top left), then "Settings", then "Update". Now Zune should tell you you have a Restore. Good luck!

Need Help with APX Mode Brick.

Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app
I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app
I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986
You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!
I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.

Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"

Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"
Its a Note 4 SM-N910F, Android 6.0.1, BB N910FXXU1DPE2, kernel 3.10.40-7733605 [email protected] #1
i feel I have tried everything... History:
Phone has been working fine for a year, upgraded to 6.0.1 no problems about 2 or 3 months ago. no new apps installed. Last week it started getting very laggy, keyboard strokes took for ever to register. I thought, ok, time to to a factory reset to blow out any old cobwebs. Did it via the menu. However the phone froze midway thought. I left it for an hour and then pulled out the battery. I popped it back in and it performed the reset without me having to press anything. Cool, thats good I thought.
Now I was going to change the battery, so I powered off as normal and put my other 2 week old original samsung battery in, and it would not power on. After a few reinsertions it powered back on. I though i have to do another reset. So I tried, and it would not reset. It just died. I cant restart the phone, it dies. If I shut it down normally. it wont turn on back on, I have to take out and reinsert the battery multiple times, holding down the powerbutton between to discharge. this can take up to 10 tries now. Sometimes it will go th the unable to bot in normal mode and "downloading , do not turn of target, but it will stay there for ever, more than an hour.
Every 15-20 tries it would turn on, let me get in via pin, only to start freezing up within a min, and then die again. Somewhere I read that a guy hada similar problem, and he used wakelock and that worked, on level 4. I managed to download that and used it, and hey presto, it works!
Now I had to power down the phone for a reason, and it took me about 30 min of battery and powerbuttonholding before it managed to boot up, and I was quick enough to start wakelock on level 4.
It wont boot in to safe mode, it wont boot in to recovery mode, it wont boot in to the factory reset mode. Its the same with either battery, and different cables.
Any ideas what i can do here, or what could be wrong? I havent gotten it wet or banged it.
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
armstrongracer said:
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
Click to expand...
Click to collapse
are you still under warranty? i sent mine to a samsung center, the guy recognized the problem as the motherboard, said I wasnt the first. That was 3 weeks ago, they are STILL waiting for the parts. They say the Samsung factory are way behind with repair parts, etc etc. I am hoping it will go under warranty. Ill update when I know!
I've been having the same problem that started yesterday morning. I've tried a few different solutions but nothings worked, I get the feeling that my phone is dead and I'm not in warranty either. I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
neils0911 said:
I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
Click to expand...
Click to collapse
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
bonfilet said:
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
Click to expand...
Click to collapse
Definitely...surely it couldn't have been that hard to make a device with a battery that was still removable on the newer phones. It's frightening how many forum posts I've found with people having their phones just brick out of nowhere (and that's just the note 4). I've given up trying to fix mine, I've tried every method I could find and nothings worked. I can only assume that this problem is simply the motherboard of the phone not working anymore. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
neils0911 said:
. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
Click to expand...
Click to collapse
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
mymigi said:
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Click to expand...
Click to collapse
If you are able to boot it into Download Mode then you should Download Stock Rom file for Galaxy Note 4 from Sammobile and Flash it through Odin..
Everything will be OK... ?
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can find here firmware for N910A , 5.1.1 and 6.0.1 : https://simunlockremote.com/firmware-support/
bonfilet said:
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
Click to expand...
Click to collapse
I think the camera on the note 4 is absolutley terrible. I might even go so far as to say the pictures are unusable. the applied noise reduction renders everything splotchy, colors are off and its not sharp at all. and Im not talking dark conditions here.
Anyway, my phone was repaired under warranty and is back to working as it should. It was indeed the motherboard, so if you have the same troubles I had, those are your best bets.
I don't think replacement via warranty will be available. I will attempt to power into download mode and verify if I can get it back up and running. If not, a good ole paperweight.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here ..
https://www.androidfilehost.com/?fid=24459283995298017
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here. .
https://www.androidfilehost.com/?fid=24459283995298017
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
onno72 said:
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
Click to expand...
Click to collapse
My phone is also random Rebooting
It also shuts down at 25% of battery remaining, Have you also faced similar issue?
Download the app "Wake Lock" and run the Partial Wake Lock option. Apparently the updated software impacts the CPU. For the restarting issue, put it in the freezer for a couple minutes. You may have to take the battery out once, but it has worked for me every time.
This looks very much like the issue reported here:
https://forum.xda-developers.com/no...-error-fix-t3434335/post72944466#post72944466
There are temporary fixes (wakelock), but ultimately this is a harware issue, and the fix is a new motherboard.
I think that underlying it is a problem with heat affecting the eMMC chip or its connection to the motherboard.
See also:
https://us.community.samsung.com/t5...ePhones/thread-id/12183/highlight/true/page/1
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/
Hey can u pls get me the stock firmware for n910gddu1dpb4
You might find this interesting. Since I couldn't get mine to power up at all, I called Samsung tech and they quoted me $75 to fix it and they would pay for shipping. I figured it was better then getting another phone off Swappa. 2-3 weeks later i get an email that they are repairing it under warranty at no cost to me. I got a refurbished phone since i know my IEMI number was different. they didn't explain why. Anyway, I got lucky i guess.

6P completely dead 2 days after Android O

Good morning all,
my 6p looks completely dead. I've installed the latest Android O factory image from the Google Developer site, flashed it and was running withot issues until today.
I was about to write a comment on Facebook, and then the phone freezed. After seeing how the phone was not recoverying, I tried a hard reset by long-pressing the power and both the volume keys. Then, the phone got a black screen, didn't vibrate, and now looks totally dead.
It's not charging or responding in any way, no matter how I press it. I'm quite confident the phone was over 50% when this issue occurred.
I don't really know what coul've caused this, but on my side, the preview was flashed cleanly with a complete factory reset, and I've only restored media files, without rooting.
Any ideas as to what should I do?
Do you get anything showing up on a computer when you plug it in?
jmaclean62 said:
Do you get anything showing up on a computer when you plug it in?
Click to expand...
Click to collapse
Hi jmaclean, nothing, not even in Windows Device Manager...
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Zwitterion said:
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Click to expand...
Click to collapse
Yes a bad choice I would say - as an owner of a Nexus 6P device currently awaiting repair (thank god I'm in warranty) - I can tell you this device is plagued with issues that only become apparent as soon as your warranty is approaching expiry.
I love the phone, the design and build quality aesthetically speaking but would never be buying from Huawei again. The device is plagued with poor design that people believe leads to the CPU failing for some odd reason causing the dreaded bootloop issue.
My phone died literally in front of me and never worked again. I've contacted Huawei to get some clarification if this is an inherent fault as thousands are complaining about it and they just plain deny it and maintain if the warranty expires your out of luck. Apparently fixing the bootloop requires a motherboard change which in itself costs over $200 apparently. May as well get another phone for that as even the replacement component will eventually fail!
Sounds like a power issue. Maybe there's an open at the power switch or bad battery connector or battery. It most likely is nothing to do with Android oh it's just a coincidence. If you would have not even flashed Android O it would have still done this
seems like you will need to open up your nexus and unplug the battery, and then put everything together and try
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
paracha3 said:
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
Click to expand...
Click to collapse
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
murphyjasonc said:
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
Click to expand...
Click to collapse
Yes I was able to apply that and got it to work. Thanks

V20 VS995 Bootloop (no root, 1CA update)

Today on my way to work I was playing music through my bluetooth and the music stopped. I went to reset bluetooth and it took almost 3 mintues to turn off. When I went to turn it back on, it wouldn't. I powered off and reset the phone. After, it got stuck in a bootloop. LG logo for about 7-8 secs and restarts.
Before the bootloop, I was noticing a few weird things: A notification of USB Options was always up, was saying I was using my phone as a USB Power Supply. If I changed the options it would revert back to USB PwrSply. I noticed the battery life was getting a lot worse. Also, when plugged into Quick Charge it would not say "Quick Charging" anymore.
I can get into the Recovery menu, but all options revert to the bootloop.
I can get to the Download menu. After about a few seconds of sitting on the Download menu, it starts the LG logo bootloop.
I have not tried to flash another stock ROM. I have downloaded the LGUp program, Uppercut, LG Mobile Support Tool, and LG Mobile Driver. I also downloaded the previous 1BA firmware kdz file.
I believe I have the knowledge to reflash properly, but I do not want to make the phone worse or lose my data. Plus, I don't want to void the warranty.
TL;DR I have bootloop and want to save my data!
Any suggestions would be very much appreciated! Thank you!
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
runningnak3d said:
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
Click to expand...
Click to collapse
I was hoping that this wasn't the issue. I was hoping that it was from the 1CA update, because the other random problems seemed to have started when it updated. Should I at least try to reflash? Would reflashing to a stock/OEM ROM (the one i mentioned above) void the warranty?
Also, when I restarted the phone today, that was the first restart that I have done since the update. Not sure if that means anything, but maybe??? lol
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
runningnak3d said:
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
Click to expand...
Click to collapse
Awesome! That's definitely good to know. Thanks.
I'm going to attempt to downgrade flash it. If it doesn't work, I'll contact LG. I dont really care about buying a new phone. My data on it is worth WAY more to me than the phone. (Guess I really should start backing up my stuff XD )
If you have any suggestions as to recovering my data, even if it kills the phone, I'm all ears!
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I'm not sure to be honest, your situation seems strange
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
lakingslayer said:
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
Click to expand...
Click to collapse
It wasn't hot at all, I had the A/C in my car on and it sets on a car mount that mounts to the air vent. It gets direct A/C. I didn't have it charging either.
All I did was connect my phone to Bluetooth, play a mix, and drive 15mins to work at 6am in the morning. It was still dark and cool out. The music stopped and I tried to reset bluetooth. It took forever to turn off and wouldnt turn back on. I reset phone and BOOTLOOP. ???
There is no damage to the phone physically. I don't think I've ever dropped it ever. It's gotten hot a couple times, but that was months and months ago.
I've never had a problem with this phone since I got it almost 2 years ago, since the 1CA update, I had a couple bugs, now this bootloop.
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I hope you got your data off before you started messing with it.. your phone is dead.. Runningnak3d gave you a clear warning
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Click to expand...
Click to collapse

Categories

Resources