Related
Hope any of you guys can help me on this. Last night my Leo's screen went totally unresponsive.
Could not get past the screen lock. Removed the battery, rebboted ... could not get the PIN code in.
I had seen this already two nights ago, but it got away once I moved in an area where I could get a reasonable signal (ultra-crappy where I am now on vacation).
Now Im'm beginning to think the signal thing was just a coincidence and that the problem is way more serious.
In total despair, I even tried a hard reset. To no avail.
Phone boots up fine. I can even sync to it (so yes, I can get to the registry). But since the only control is the screen ... not really a lot I can do with it.
I need to be in touch for work and I badly need the voice and internet connectivity (right now I'm using the wife's phone ...).
Any ideas besides getting an RMA from HTC?
Thanks a lot in advance.
Update: spoke with HTC support.
It looks like the issue is somehow triggered by the lock screen.
As suggested by HTC, I flashed again the 1.66 ROM upgrade and everything ran smoothly until the phone went in standby the first time.
Then, I was (and still am) unable to unlock the screen. And if I soft reset screen is unresposnsive again.
Right now I can just receive calls (I removed the PIN code from the SIM temporarily).
HTC told me to send it in for repair, but everything in Italy is closed until Aug 23rd and the only option I have is to ship it at my own expense to the UK and back (HTC will collect and deliver free of charge only within the same country).
Total bill some 100+ Euro plus driving 100 KM or so to the nearest courier collection point. A nightmare.
What really troubles me is that the problem surfaces only once the screen locks.
On one hand I follow HTC's support that if flashing 1.66 did not cure the issue, it cannot be software.
On the other hand, if it is indeed hardware, how come it freezes only after the first lock screen? Lock/unlock is a software thing. Screen should behave exactly the same way before or after the lock - shouldn't it?
Anyone here seen/heard of anything like this?
wow, gotta love those "closed for the summer" euro vacations.
If you reinstall the ROM, then why not disable the lockscreen until you can get it fixed?
You can install BSB tweaks and that has an option to disable autolock.
i had the same exact problem; it started freezing only on the lock screen then got worse and started freezing at random times while in use. I finally broke down and sent it in to HTC to check it out. I'm waiting to hear back with there diagnosis and I will pass along whatever they tell me.
Good to know the problem has come up somewhere else (if you're the only one you are most likely to hear it's your fault before they replace the most expensive component in the phone). Where are you located slimster?
How long have you been waiting for? HTC policy should be 7-10 working days from when they receive the phone at the lab (so they told me and I remember reading it somewehere here in xda too).
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Is cinema mode on?
annik1s said:
Is cinema mode on?
Click to expand...
Click to collapse
Thanks, no, cinema mode isn't on.
It's really curious, the screen fades slightly in brightness after five seconds, then goes to the dim version of the watch face, then goes completely black a second later. One tap brings it back so I'm it's like the regular off screen mode.
TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.
Chewie01 said:
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.
Click to expand...
Click to collapse
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.
TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Just got my Zenwatch and I am having the same problem... Resetting the watch helped. But, I am still not getting the watch to vibrate on notifications. It vibrates when I set an alarm (on the watch) to it's not the vibrating device itself...
TheGreatWaldopepper said:
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.
Click to expand...
Click to collapse
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.
Chewie01 said:
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.
Click to expand...
Click to collapse
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.
TheGreatWaldopepper said:
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.
Click to expand...
Click to collapse
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.
Chewie01 said:
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.
Click to expand...
Click to collapse
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.
TheGreatWaldopepper said:
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.
Click to expand...
Click to collapse
Well the good news is I now have the replacement watch and it works as advertised. I did have to complain a lot to get the difference in price resolved. I ended up complaining so much that the store manager gave me the money out of his own pocket just to get rid of me .
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
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.
Good morning!
I bought this phone off of a friend for dirt cheap because they changed it because of this problem. I Tried everything in my power, like reflashing the firmware, but nothing seems to work really. I'm pretty positive it's a hardware failure of some sort. I was trying to get it fixed but I get mostly a "Change the motherboard". Before going with that route, and possibly adding to more e-waste, I would like to try and pin-point the source of the problem. I have a log of the last few seconds before the phone freezes and reboots by itself.
Hope this could be able to at least see where the problem is, if not i'll just buy a random motherboard off of aliexpress praying to not get scammed, or just sell it back for parts since the display works completely
Here is the txt file