This happens only when I install any custom rom...the phone works fine with x720 5.8.018s version...anything apart from that device will shut down every 2-3 minutes ...very strange behaviour ...any one has any idea ?
any custom rom , android 6 or 7 , AOSP or stock based, it will boot fine and after initial setup , it will work for 3-4 minutes and then suddenly device shuts down. .. when i boot it up again , same thing happens, in one minute shuts down.
if i flash 5.8.018s stock rom , everything works fine....and it doesnt shut down...
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
marik1 said:
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
Click to expand...
Click to collapse
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Manan79 said:
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Click to expand...
Click to collapse
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Manan79 said:
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Click to expand...
Click to collapse
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
Click to expand...
Click to collapse
On my equipment too !!
Andresdsr said:
On my equipment too !!
Click to expand...
Click to collapse
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
mchlbenner said:
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Andresdsr said:
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Click to expand...
Click to collapse
Does anyone completely solved the shutting down issue on x720? I remember the same issue with the stock rom when i was getting the phone (5.8.018). but this rom could have been a shop rom, cant remember.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Click to expand...
Click to collapse
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
sk8223 said:
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
Click to expand...
Click to collapse
Thanks for the information.
Could be possible... If I'm shaking the phone like a cocktail-mixer, it feels something loose inside it and this could be the battery of course which could be not fixed correctly. But I am sure, that this issue has also something to do what is happening on the phone currently. Sometimes I am going to bed and the phone does not move for 8hrs, it simply lays on the table. In the morning, it is shutted down. Need to hold the power button for about 10sec to restart the phone (usually hold 2sec to power on). Sometimes (not really often) it warm-starts automatically.
I think this could be also a memory issue or internal storage. Yesterday I was playing a game (Bowling by Jason Belmonte) and after 3min, the phone hung up, display remains on, no reaction on pressing the hardware buttons, waiting 5min... nothing happens. So I pressed the power button 10sec, phone seems to reboot normally, but it take a bit more time in my oppinion. Now after entering the pin, some phone configurations were resetted to default, but not all. Playing this came, it sometimes happened, that the phone switches off (with one vibration). Rebooting with a 10sec press and it runs again normally. This time phone hung up and some configurations were resetted to default. WTF?
Today I have played Hmmsim 2. Phone hung up again, pressing the power button 10sec, phone begins to reboot, but rebooting never finished (waiting for about 1-2hrs). Long Press power button (10sec) to try to reboot again - same behaviour, never ending ROM loading screen. Wiped to factory via TWRP and the phone reboots again, but all configurations lost, like freshly installed rom. OK, whatever, using the google backup for apps and so on... when installing the apps in the background, the phone reboots about 3-4 times, app installations not finished. Cancelled and shutting the phone down to TWRP, where I am now...
What I will try to say is, that whenever the storage or memory is used to much or something like that, the phone begins with that behaviour.
And now I am thining about what to try next. I think I will try to flash the stock recovery via TOOL ALL IN ONE then flashing a stock rom like 5.9.023S.
I am still not sure of a hardware issue...
peed_neslo said:
I am still not sure of a hardware issue...
Click to expand...
Click to collapse
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
sk8223 said:
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
Click to expand...
Click to collapse
Thank you very much!
I am sure that the phone was doing the same on stock rom, but maybe fewer times. I have flashed a stock based rom now (Turbos mini 5.9.023s) and the issue still exists, but now the phone reboots normally more often than going into edl mode (emergency mode). I have found an old thread here on XDA and the issues described there sounds nearly the same. Finally the user in this thread also had hardware issue.
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
peed_neslo said:
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
Click to expand...
Click to collapse
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
Click to expand...
Click to collapse
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Admittedly I'm not sure at all if this issue was already present after starting the phone for the first time. One of the first things I have done during the initial setup wizard was using the integrated data transfer app by LeEco (scanning a QR code with the old Xperia Z, downloading app to transfer data to the x720). This app establishes a Wifi direct connection between both phones to transfer the data like apps and other stuff. This transfer process takes at least 6-7 hours and during that process I am sure that the phone was not rebooting a single time. Maybe a specific app or background process of an app causes this irregular rebootings. I have not testet this. I have installed the most common of my apps also using different custom ROMs later.
On the current ROM (Turbos mini 5.19.023s) I have now looked into the last_kmsg.log file severel times after the phone was hard-rebooting (not to emergency mode - the phone is switching down to emergence mode really rarely since I have flashed the stock based ROM) to debug for a kernel problem and the power off reason seems to be ""Triggered from PS_HOLD (PS_HOLD/MSM controlled shutdown)". In the log file I could also find some "kernel panic" entries. So I have a little gleam of hope that the issue is not a hardware problem. I have to test a bit more with the stock recovery/ROMto gain a better knowledge of the issue. I think I will post this into the ROM topic to ask a developer.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Finally - I got it working without any problems now!
Happily it seems to be not a hardware issue. I have flashed the Grossoshop ROM and Recovery via a provided .bat file. This .bat file has flashed the recovery first via fastboot, then the ROM via fastboot. This Grossoshop ROM was based on 5.8.018s I think. Then I have updated TWRP Recovery to the latest version via TWRP itself (flashed the new image). Then I have flashed Mauro's 2.2 (which is based on 5.9.023s) and it is running great! Super performance, no extrem battery drain, no reboots, all is working (except the chinese design downloads as I cannot create a Leeco account from Germany). But now I'm satisfied. :good::laugh:
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
Thanks!
Click to expand...
Click to collapse
My x720 has done the same to me a couple of times now, Vibrates once and turns off and I have to hold the power button for a few seconds longer to turn it back on again which is odd.
The battery was charged over 50% % 70% at the times it happened and I wasn't even using the phone, It was just sat on the table in front of me.
I didn't have any problems at all until a few days ago when it first shut down.
I'm using Oreo - AICP 13.1 from here - https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
The problem now is I don't know where to start troubleshooting When I get time I am planning on a clean wipe and fresh install of AICP again to see if that solves the problem
When using this ROM does your phone heat up a lot.
Sent from my LEX727 using xda premium
Did you manage to fix the problem somehow?
Related
Hey all.
Been having problems with a Nexus One that crashes at seemingly random times.
I have been unable to pin it on anything, and am asking your help.
It appears to be independent of the Rom installed, whether there is an SD card present, or whether its connected to a USB cable or phone charger.
Any help would be greatly appreciated.
Phone Info:
Nexus One (AT&T model)
Radio: 4.06.00.12_7
Current Rom: Enomther's TheOfficial Nexus1 - v2.12.2
Provider: Rogers (BC, Canada)
Logcat output attached as screen capture image.
This has been reported by a few users. I sent mine in for repair and got it back not repaired - they couldn't replicate the problem.
My case has been escalated which means a HTC guy called and asked me a few questions and then told me to wait for an email (a few days ago).
I believe my problem started when I seriously overheated it ... driving with navigation on, 3g downloading maps and traffic data, car charger plugged in all on a very hot day on a very hot dashboard. This was the first reboot and they got more and more often after that. Now I can't run anything for more than 5 minutes if 3G or wireless is on (in 'Airplane' mode I can run for quite a while without a reboot).
mine was doing the same thing.
getting progressively worse until the phone was basically unusable earlier this week.
I was running CM6 at first when it started happening.
installed the newest nightly and it worked better for a bit then got even worse.
uninstalled the stand alone version of gmail from the market and it worked for a couple hours and then kept rebooting on me.
finally i did a factory data/cache wipe and installed a rooted stock rom and things have been working PERFECT for over half a week.
I had the same issue. first reboot happen when i had nav running plunged in then after a few months utube , browser etc would restart my phone. it didn't matter which rom i used or stock. I sent it in and they fixed it. i had issues with htc but it got fixed.
Yup, same here, strange thing is it isn't a complete reboot. Hard to explain but what happens is i'll touch the phone and then it will immediatly go to the CM6 boot logo, then immediatly to the lock screen, (which I have disabled) then to my normal desktop. Total time elapsed maybe 5/6 seconds, wierd.
A normal reboot usually takes about say a minute or so. just started happening 3/4 days ago, and happens maybe twice a day at most, some days not at all. Probably wait until Cyanogen includes 2.2.1 into 6.0.0 stable then reflash.
Ive been having the same problem for about a week now, but I'm still using stock, not rooted. Its weird, because its a really fast reboot. It goes to the Booting X, for about 6 seconds, then it boot up just fine. I cant understand it.
this really sucks
I am keeping my ATT nexus one around for gingerbread but these random reboots are really killing me....I use the phone for five minutes and it just reboots by itself....The phone runs really well for those five minutes...Ive done five factory resets but it is still just doing these phantom reboots.... Anybody find out anything more about this...or know a fix....the phone is not rooted and it is clean stock froyo...so please help or keep talking about it so htc will address this issue lol which i doubt since this phone is starting to become ancient....(cant wait till nexus S) =P
With regards to the original problem posted, I believe I've managed to diagnose it correctly.
The problem lies with faulty heat distribution. The phone would crash and reboot more often in times of great stress:
charging the phone (heats up the battery)
running many applications at once (heavy system load)
navigation (heavy dataand gps traffic, image processing)
This coupled with the fact that changing the OS did nothing to remedy the problem solidified the notion that the problem was hardware based.
Given this, I contacted HTC Nexus One support and had the phone repaired.
Note: HTC will honor the warranty and fix hardware issues for an unlocked Nexus One. With software issues, you're on your own (for obvious reasons).
This is exactly what my phone is off to warranty for. I experienced this with every rom tried. I wipe my phone completely and put stock froyo on only to see the exact same behaviour...so at least I'm not crazy
The tech told me it was a hardware problem so that is a bit of a mind ease.
It seems Nexus One and Desire are really similar: HTC Desire rebooting on its own.
P.S. It's a problem with faulty motherboard, if you're within warranty, it should be replaced.
I also have been pleasantly experiencing this issue with the nexus one, so i sent it for repair at HTC and they have said it is an issue with the motherboard and it has been replaced, it is now in the post so I will update this post when I receive it to whether the problem is resolved. Hope so was driving me crazy!
The log did not capture the error. In most cases its a software issue, not hardware. (has happened to me too, not recently though)
Well an update as promised.
I received my N1 back after UPS had finished not dispatching it due to "Adverse weather conditions" and the issue is GONE!!! I know a week isn't really a long time to trial the device but this was happening several times a day.
HTC replaced the motherboard.
My advice to anyone having this problem, is to send it to HTC for repair (dont be worried about it being rooted/custom ROM etc mine was and because its a known hardware issue they really aren't bothered about it.)
It took two trips to HTC for them to finally address the issue. They did fix something (they didn't say what) and the problem is gone.
I believe it was the motherboard because Swype Beta decided that it was a new phone and not the one I registered (so it would not install).
Hi there,
I bought my Galaxy Note one month ago and in the first weeks I never had any problems with it, but recently it crashes more and more often. A week ago, while I was still on stock rom (unrooted), it crashed 5 times at one day. I did nothing that could be a problem for it, I was sketching (Autodesk SketchbookMobile), browsing, playing games etc.
I thought it may be the best to try a custom Rom, so I rooted my Note and flashed RocketRom v20. But soon after that the same problem appeared, and besides that, I needed after every crash more than 10 trys to successfully start the phone, somestimes it stuck at the "Samsung Galaxy Note" logo, sometimes it even accomplished it to get to the PIN-input, but crashed at it.
Yesterday I flashed RocketRom v21, but nothing changed.
The only thread about crashes I found in this forum says it may be because of S-Memo, but I barely use it, and never had problems while using it.
Right now I'm holding my Note in my Hand and try to start it, it's attempt 30 or so. I really love the Galaxy Note, but this makes it hard to use for me.
I appreciate every attempt to help me.
seems like manufacturing defect. If you are able to enter download mode, then flash Stock ROM which is latest for your region. then go for a replacement.
A few minutes ago I wasn't even able to get to downloadmode or to charge the phone, but after I plugged it in and out a few times I somehow managed it to get to download mode. I flashed the stock Rom, but the phone again stucked at the "Galaxy Note"-Logo the first two attempts to start it, now, again, it shows no reaction.
It seems like I have no other choice then to send it back
Sounds like a hardware defect with the internal NAND that might be accounting for the random freeze/reboots. Bad RAM can also do this.
Bad/ Corrupted sectors can do that. Lawl.
Also, list all apps that you've installde from the market. There might be some conflicting processes that's causing the phone to hang.
And first to be sur take your sdcard out, and test sometime bad/defective sdcard can also have dramatic effect.
It's already on it's way to Amazon.
I tried starting it without the sd-card, but that didn't help.
I hope it doesn't take too long, because i can't handle the tiny screen of my Samsung Wave anymore.
You are not the only one with this problem. Mine also started crashing/turning off randomly after approx 1 month of buying. Again on stock rom unrooted and very few apps installed.
Starting to think that just maybe samsung have tried to push the boat out too far by releasing this device. Don't get me wrong I love it (when it works) but it just seems too buggy atm. And I don't think ICS will cure all these problems we are all having. I know every device has a small percentage of faulty products but it seems that the note has a high percentage of those.
Sorry to be so negative but when you spend 600 euros on a phone you expect it to work for more than a month.
Hey guys..
I've owned all the Samsung Galaxy phones from the S+ right up to the S4 and I've flashed firmwares over all of them with generally no problems at all.
But lately I have a constant issue that has been plaguing my Galaxy S 4 (i9505) phone since I flashed the 4.3 i9505G (GE Edition) ROM over my phone.. (have since moved to OMEGA v12)
The phone just randomly reboots whenever it seems to feel like it.
It could be whilst taking a picture, it could be whilst using google maps, it could be whilst installing an app from the app store or just scrolling across the screen. It's basically rebooted through anything and everything and I've tried pinning it down to something but every time I think that I've got it sorted out. It crashes again whilst doing something else.
1 thing however has got me stumped. The phone has NEVER crashed whilst plugged in. If I keep the phone plugged in, it's never ever just rebooted on its own for me. Which got me thinking that it could be a faulty battery or some sort of voltage issue.
Coming from the 4.3 GE Edition ROM there are other people experiencing random reboots. But now I've just flashed over OMEGA v12 and right after flashing (I did a full wipe of course first) the phone rebooted whilst typing in my Wifi access key. After the reboot I was able to set my phone up and I did a reboot myself, then I went to the app store to add an account and the phone crashed AGAIN.
I'm totally over this issue with my phone. I paid a small fortune for it and I cannot rely on it at all. So I absolutely need it to work. I've had issues on 4.3 GE getting Mobile Data to work. I've had issues with it crashing and I'm just done with all of this.
Do you think that my phone is already broken? (It's barely 3 months old) Do I need to get it replaced under warranty? Can I even get it replaced under warranty, is there a way to even get my warranty back or reset the flash counter etc?
I'm just so confused guys I thought maybe it was my battery, and that my battery was faulty because I had battery percentages dropping and jumping around like mad. For example 15% battery left would actually have the phone turn off... and reboot at 0%. Then the light wouldn't go green for 'Fully charged' and the phone would sit on 99% or 100% but still not say 'charged'. In addition I could swear I had lost more than 10% of my charge in the blink of an eye etc.
I just bought 2 new batteries but they will take a week to get here.. and if the phone is still rebooting (and it isn't a voltage/cut out issue with the battery) then should I assume it's a hardware issue and that the phone needs replacing? Or could it just be a bad flash or something? The phone has at least a 2 year warranty. I don't want to replace it after just 3 months when I haven't even so much as dropped it once.
My recovery is PhilZ 5 Touch 6.0.4.0
I always check MD5 sums before flashing and do a full wipe:
- Wipe Data/Factory Reset
- Clean to Install a New ROM
- Yes
- Then Flash the new .zip file etc.
What on earth could be wrong with my phone?
I'll happily provide any more information, as I honestly cannot handle this happening and I have no idea what my problem is...
Thanks incredibly much for any help at all, what-so-ever.
leijonasisu said:
Hey guys..
I've owned all the Samsung Galaxy phones from the S+ right up to the S4 and I've flashed firmwares over all of them with generally no problems at all.
But lately I have a constant issue that has been plaguing my Galaxy S 4 (i9505) phone since I flashed the 4.3 i9505G (GE Edition) ROM over my phone.. (have since moved to OMEGA v12)
The phone just randomly reboots whenever it seems to feel like it.
It could be whilst taking a picture, it could be whilst using google maps, it could be whilst installing an app from the app store or just scrolling across the screen. It's basically rebooted through anything and everything and I've tried pinning it down to something but every time I think that I've got it sorted out. It crashes again whilst doing something else.
1 thing however has got me stumped. The phone has NEVER crashed whilst plugged in. If I keep the phone plugged in, it's never ever just rebooted on its own for me. Which got me thinking that it could be a faulty battery or some sort of voltage issue.
Coming from the 4.3 GE Edition ROM there are other people experiencing random reboots. But now I've just flashed over OMEGA v12 and right after flashing (I did a full wipe of course first) the phone rebooted whilst typing in my Wifi access key. After the reboot I was able to set my phone up and I did a reboot myself, then I went to the app store to add an account and the phone crashed AGAIN.
I'm totally over this issue with my phone. I paid a small fortune for it and I cannot rely on it at all. So I absolutely need it to work. I've had issues on 4.3 GE getting Mobile Data to work. I've had issues with it crashing and I'm just done with all of this.
Do you think that my phone is already broken? (It's barely 3 months old) Do I need to get it replaced under warranty? Can I even get it replaced under warranty, is there a way to even get my warranty back or reset the flash counter etc?
I'm just so confused guys I thought maybe it was my battery, and that my battery was faulty because I had battery percentages dropping and jumping around like mad. For example 15% battery left would actually have the phone turn off... and reboot at 0%. Then the light wouldn't go green for 'Fully charged' and the phone would sit on 99% or 100% but still not say 'charged'. In addition I could swear I had lost more than 10% of my charge in the blink of an eye etc.
I just bought 2 new batteries but they will take a week to get here.. and if the phone is still rebooting (and it isn't a voltage/cut out issue with the battery) then should I assume it's a hardware issue and that the phone needs replacing? Or could it just be a bad flash or something? The phone has at least a 2 year warranty. I don't want to replace it after just 3 months when I haven't even so much as dropped it once.
My recovery is PhilZ 5 Touch 6.0.4.0
I always check MD5 sums before flashing and do a full wipe:
- Wipe Data/Factory Reset
- Clean to Install a New ROM
- Yes
- Then Flash the new .zip file etc.
What on earth could be wrong with my phone?
I'll happily provide any more information, as I honestly cannot handle this happening and I have no idea what my problem is...
Thanks incredibly much for any help at all, what-so-ever.
Click to expand...
Click to collapse
I can only give you advice on some of the smaller issues that you mentioned. I haven't had a problem with reboots at all (i've flashed all manners of ROMs too, including the GE), so I'm guessing it is hardware related. You should get it replaced (if it still is messing up with the new batteries).
As for warranty, yes you can claim it back on warranty. To be doubly safe, restore it to stock: http://forum.xda-developers.com/showthread.php?t=2265477
Use Triangle Away: http://forum.xda-developers.com/showthread.php?t=1494114
Also FYI, rooting does not void warranty: http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu (assuming you are in the EU, not sure about other countries) (gosh i've posted this a lot today).
Thanks a lot buddy I am in the EU definitely and the phone is purchased from the EU. I am actually about to flash it right back to stock now to see if it stops the rebooting issue. I will just have to live without custom roms for awhile and such. If it still keeps crashing I will wait for the new batteries. If it still keeps crashing again after I get those. I guess all that is left to do is render myself without a phone for a week or two and have it repaired...
I wouldn't worry mate it sounds to me like a definite battery issue
Sent from my GT-I9505
similar problem
leijonasisu said:
Thanks a lot buddy I am in the EU definitely and the phone is purchased from the EU. I am actually about to flash it right back to stock now to see if it stops the rebooting issue. I will just have to live without custom roms for awhile and such. If it still keeps crashing I will wait for the new batteries. If it still keeps crashing again after I get those. I guess all that is left to do is render myself without a phone for a week or two and have it repaired...
Click to expand...
Click to collapse
Hi leijonasisu,
I've stumbled across your post after having experienced more or less the same issues as you. After trying many custom ROMs in the last few weeks, the phone has barely been useable for more than a few minutes until it randomly reboots. At which time, I must start over with the whole flashing process. My question is, did getting a new battery resolve your issue? Or did you just trade the device back in?
many thanks
kingzain900 said:
I can only give you advice on some of the smaller issues that you mentioned. I haven't had a problem with reboots at all (i've flashed all manners of ROMs too, including the GE), so I'm guessing it is hardware related. You should get it replaced (if it still is messing up with the new batteries).
As for warranty, yes you can claim it back on warranty. To be doubly safe, restore it to stock: http://forum.xda-developers.com/showthread.php?t=2265477
Use Triangle Away: http://forum.xda-developers.com/showthread.php?t=1494114
Also FYI, rooting does not void warranty: http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu (assuming you are in the EU, not sure about other countries) (gosh i've posted this a lot today).
Click to expand...
Click to collapse
Looks like it's better to restore to Samsung stock firmware first then start again from there,
But this will upgrade the the Knox bootloader also.
Stock firmware can be downloaded here, www.sammobile.com/firmwares
I fixed this ages ago. It was a battery issue, I'd bit my bottom dollar that it would be a battery issue for anyone else too, I've read a lot of stuff online about people who have gotten bad batteries with theirs. Swapped to 2 third-party and apparently larger batteries and never had an issue and never looked back.
Sorry for not replying back much sooner but I forgot about the thread.
Try another battery and if within a day or two you get no reboots then toss the bad battery and enjoy your phone! The thing is the battery (due to voltage issues) can make it look like it's the OSes fault when in actual fact it's just a faulty battery and voltage issues.
same problem here.. s4 randomly reboot..
I got the same problem.
The phone reboots every few minutes on me when i want to take it out of standby.
Sometimes it works for a few hours and sometimes it just reboots itself every few minutes or it reboots when i want to do something.
So ur all saying that a new battery could solve my problems ??
Opuske said:
I got the same problem.
The phone reboots every few minutes on me when i want to take it out of standby.
Sometimes it works for a few hours and sometimes it just reboots itself every few minutes or it reboots when i want to do something.
So ur all saying that a new battery could solve my problems ??
Click to expand...
Click to collapse
Hi, the OLD problem WAS caused by the faulty batteries batch (easy to recognize - the battery serial no was beginning with BD code).
Now, more frequently it is resulting from KNOX related issues.
spamtrash said:
Hi, the OLD problem WAS caused by the faulty batteries batch (easy to recognize - the battery serial no was beginning with BD code).
Now, more frequently it is resulting from KNOX related issues.
Click to expand...
Click to collapse
hi thx for the answer.
Could infact be knox issue as i am now back on stock rom without root or anything and im not having any issues now.
But i would like to have a custom rom and root again .
So how would i go from here to there without having random crashes / reboots on custom rom ?
Opuske said:
So how would i go from here to there without having random crashes / reboots on custom rom ?
Click to expand...
Click to collapse
Only one option then: read the ROM-specific threads, loo for feedback posts. If ROM would cause random reboots, you can be certain that it will be written there.
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
adilabdi110 said:
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
Click to expand...
Click to collapse
Have you disabled everything related to knox and deknoxified your phone?
Do press thanks if my posts are helpful
Sent from my Stock Deodexed i9500 :')
adilabdi110 said:
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
Click to expand...
Click to collapse
Uninstall everything realiting to Knox with Titanium backup and be Happy
Sent from my Galaxy S4 using Tapatalk
i9505 S4 sussed out the randomsoft rebooting
i9505 Kitkat random rebooting with UGNG8
UK - BTU
2014 November
I9505XXUGNG8
I9505YXYGNH2
I9505XXUGNG8
4.4.2
For me kitkat UGNG8 with random soft rebooting, tried everything with that firmware I could, reset to default and it was still randomly rebooting when ever it liked. Usually after swiping the screen out of wake lock most of the time. I even re-odin GNG8 3 times.
Cured by Odin with this one, below, which I thought I couldn't, because of the backward compatibility of the dates, but it went in ok. No reboots for weeks. Cured my i9505 S4
2014 July UK - BTU
I9505XXUFNB9
I9505BTUFNE1
I9505XXUFNB9
4.4.2
Link http://www.sammobile.com/firmwares/download/31852/I9505XXUFNB9_I9505BTUFNE1_BTU.zip/
So if you pulling you`re hair out with the S4, or trying to get rid, Odin this firmware first.
satelliteone said:
i9505 Kitkat random rebooting with UGNG8
UK - BTU
2014 November
I9505XXUGNG8
I9505YXYGNH2
I9505XXUGNG8
4.4.2
For me kitkat UGNG8 with random soft rebooting, tried everything with that firmware I could, reset to default and it was still randomly rebooting when ever it liked. Usually after swiping the screen out of wake lock most of the time. I even re-odin GNG8 3 times.
Cured by Odin with this one, below, which I thought I couldn't, because of the backward compatibility of the dates, but it went in ok. No reboots for weeks. Cured my i9505 S4
2014 July UK - BTU
I9505XXUFNB9
I9505BTUFNE1
I9505XXUFNB9
4.4.2
Link http://www.sammobile.com/firmwares/download/31852/I9505XXUFNB9_I9505BTUFNE1_BTU.zip/
So if you pulling you`re hair out with the S4, or trying to get rid, Odin this firmware first.
Click to expand...
Click to collapse
Interesting will have to give this a go, also the battery option.
For months I was running on Lollipop custom ROM, the developer did an upgrade and then the SIM card removed error started. I went back to the old version was keep getting the SIM Card removed error. A few days ago went back to Original ROM for NZ 4.4.2 and I still get the SIM Card error and now the phone just reboots randomly.
Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.
If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...
This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely
Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk
Same issues, I downloaded the wake lock and so far so good.
I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.
have anybody tried going back to Lollipop?
golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.
Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.
I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk
If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.
Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.
Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.
If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?
I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds
Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.
That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.
Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.
Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.