I got a S7 active from eBay and some apps (not a specific one) sometimes freeze and then the phone reboots to recovery (see photo attached). What could be the cause for this and can it be fixed? I figure maybe a new ROM would help but S7 active so far doesn't have any custom ROM yet. Thanks
PS: Apparently the baseband version was 1APN1. I just went to Software update and update to 2API2, not sure if that helps.
cppc said:
I got a S7 active from eBay and some apps (not a specific one) sometimes freeze and then the phone reboots to recovery (see photo attached). What could be the cause for this and can it be fixed? I figure maybe a new ROM would help but S7 active so far doesn't have any custom ROM yet. Thanks
PS: Apparently the baseband version was 1APN1. I just went to Software update and update to 2API2, not sure if that helps.
Click to expand...
Click to collapse
Ok now the phone doesn't seem to reboot to recovery anymore, but still occasionally restart itself. I haven't observed myself the restarting yet, most of the time it happened while charging or I was away, but I know it restarted because the first time after the phone restart, fingerprint won't work and I have to enter PIN.
Anyone experience the restarting issue and can it be fixed? Thanks
cppc said:
Ok now the phone doesn't seem to reboot to recovery anymore, but still occasionally restart itself. I haven't observed myself the restarting yet, most of the time it happened while charging or I was away, but I know it restarted because the first time after the phone restart, fingerprint won't work and I have to enter PIN.
Anyone experience the restarting issue and can it be fixed? Thanks
Click to expand...
Click to collapse
Ok I think because this device is quite new and there might not be many people using it, there's less chance that someone has experienced the same issue. I will try to ask in the S7 forum, so mod if possible please close this thread. Thanks
So the tablet sometimes loses touchscreen function. The physical buttons work fine when it freezes, it's just the screen that gets completely unresponsive.
The physical buttons work fine when it freezes, its just the screen.
I don't remember facing this issue in Lollipop, only in Marshmallow. Reseting didn't help.
This issue is similar to this one: https://forum.xda-developers.com/galaxy-tab-s/help/tab-s-vzw-loses-touchscreen-t3037140
Same problem with my 807R4. Will be in the middle of something and the capacitive buttons and screen stop responding. Tried restoring all available firmwares thru Odin and problem persists. I'm wondering if it's a memory issue? This tablet is a pig with RAM! I would like to flash an AOSP rom to see if it's a memory issue unfortunately my model is snap dragon based and there is only 1 working recovery and 0 custom roms.
Visionikz03 said:
Same problem with my 807R4. Will be in the middle of something and the capacitive buttons and screen stop responding. Tried restoring all available firmwares thru Odin and problem persists. I'm wondering if it's a memory issue? This tablet is a pig with RAM! I would like to flash an AOSP rom to see if it's a memory issue unfortunately my model is snap dragon based and there is only 1 working recovery and 0 custom roms.
Click to expand...
Click to collapse
Haha across this and my starting doing this as well. I was even thinking of looking for a broken SM-T800 model and swapping the motherboard so I can use ASOP.. but idk.. might not be worth it...
Use the shortcode to access the firmware TSP settings for the touch screen and ensure that all parts have the same build number. If not tap the general update button and it should fix the mismatch.
ashyx said:
Use the shortcode to access the firmware TSP settings for the touch screen and ensure that all parts have the same build number. If not tap the general update button and it should fix the mismatch.
Click to expand...
Click to collapse
What is the process for this?
Apparently very common. Have the same issue with my wife's SM-T807R4, the US Cellular version. Also seemed to get worse after MM update. Rooted it a couple days ago and started disabling or deleting the Samsung bloatware but so far it hasn't done anything. One thing that did work, though only temporarily, was clearing the cache with Titanium Backup. After doing this (and it took several minutes), I was able to surf the web (with Chrome) for over 30 minutes without it freezing. However, it started freezing again after a while and now is back to freezing every 2 or 3 minutes. It will however play an entire 2 hour movie without locking up so it definitely appears to be related to the touchscreen.
Update:. I think this may be a hardware issue. I booted into TWRP recovery and had the screen freeze. When booting to recovery, there's not much if any of Android loaded. If it was software related, I don't think the screen would freeze in TWRP.
Udate? Samsung nor Verizon offer update!
ashyx said:
Use the shortcode to access the firmware TSP settings for the touch screen and ensure that all parts have the same build number. If not tap the general update button and it should fix the mismatch.
Click to expand...
Click to collapse
Seems like a lot of people have the same problem no one has solution is what I hear?
same problem
among other problems im having with my Tab, this is annoying me so much. i need to flash the stock 4.4.2 firmware and they delete all versions of firmware for this specific tablet from sammobile, the Verizon model. wtf is there any way i can get a stock kitkat rom for my SM-t807V? where? o if anybody can send me a backup o something.
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
time_lord2004 said:
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
Click to expand...
Click to collapse
Simply installing a custom ROM will not affect the radio partition.
Why not try a RUU to return to full stock. Find one for your phone and run that. If it still doesn't work then it's a hardware problem.
Ok, so I replaced the current 2.41.401.41 (August) ROM with the earlier 2.41.401.4 (January) in the hope that a ROM change might reset the cellular radio. It didn't. 'Turn on radio' still does not respond either.
I did this with the bootloader onlocked, but S-ON. I think my very last attempt to fix this could be to set S-OFF, in the hope that some tool might be able to access the radio partition and re-write it or reset it or something. (This is still in the slim chance that this fault really is in software and not hardware!)
Are there any xda tools that write to or reset the radio partition (when S-OFF is set)?
What the...?!!?? So I thought as one last go at this (unless someone had comments re the S-OFF/radio partition idea), I'd let the phone get the OTA update back to the latest OS. So first I executed 'fastboot oem lock'. That of course erased device and reset it again. Radio still not working, no surprise.
After that, restarted in bootloader mode to confirm it says 'relocked', then rebooted normally... and I've started receiving missed txts! WTF.
So with enough restarts/resets, it's fixed itself? Faulty hardware, yeah right. Unless it is on the turn and happens again. [Edit: Yes it has, damn.]
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
I got this disease a week ago, tried to restart, didn't help. Been tapping airplane mode like million times, nothing. Found this thread, followed your instructions guys.
time_lord2004 said:
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
Click to expand...
Click to collapse
Didn't work for me :/ moved on to zachariah's solution...
zachariah109 said:
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
Click to expand...
Click to collapse
Yes, IT WORKED.
Don't get me wrong, this is not the end.
Today. Radio doesn't work again. 5min off doesn't help anymore, unlocking-relocking bootloader ain't do **** too.
If you find any other action sequence which "fixes" radio, please share.
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
lightweaponx said:
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
Click to expand...
Click to collapse
Today I ran RUU. It didn't fix radio. Problem must be somewhere out of radio/system partitions range.
Well, I thought I'd do one final(?) post regarding this issue. I'm starting to concede that I might have a hardware fault, but it's taken a while to accept this.
About 2 weeks ago I started having problems with the 'swipe-down' at the top of the screen to look at notifications and settings (and it started responding badly in the camera app). Then it stopped responding completely... work-around was to use an 'open notifications' app.
However, I tried out 'Apex Launcher' as an alternative to the Sense interface, and swipe-down worked perfectly ok, so isn't the hardware ok? Isn't it a software issue? However, swipe-down had completely stopped working in the camera app by then (using a different camera app is acceptable work-around).
Roll forward to a couple of nights ago, I got notification and updated to android 8/Oreo, what have I got to lose! After the update completed, I can now swipe-down ok again on the home screen! But still not in the default camera app! So have I got a hardware problem or not...
But the big thing, and the biggest headache... once again after the big update (to Oreo) and reboot - once again the cellular radio was not working. I tried all my tricks of the past, nothing would make it go. A factory reset (to Oreo, not an old RUU), unlock and relock (which does a factory reset), nothing worked. Brought up phone info via *#*#4636#*#* and this seems to have had a make-over. There is now a button for 'mobile radio power' (must be a replacement for the 'turn on radio' option) which was showing as off. Turning it on seemed to do nothing (leaving it for a while and then waiting for screen refresh, this button would display as off again).
I'd probably rebooted, shutdown/gone into bootloader at least 2 dozen times, tried all combinations of everything I could think of and could not get it to wake up. At lunchtime today I was leaving the office, booting up my phone one last time and said to a workmate 'going to a shop to look at new phones'. 30 seconds later I look down at my screen... what the *(&$%*&!! I have a signal! Missed txts are coming in!
I know that now that the cellular radio is on, it'll keep running. It always has through this whole ordeal. It's just a matter of getting it to turn on in the first place, or starting after a reboot.
The fact that after installing Oreo the swipe-down works nicely (except for the default camera), and the cellular stuff works fine, once it is on, it really is difficult to conclude whether these are all software or hardware issues. But the reluctance of the system to turn on the cellular radio might be the biggest damning factor to point to it being dodgy hardware.
So the key is not to have to reboot ever again, or at least until the next flagship is out! I still have faith in the HTC stuff, but this has been frustrating...
Hope this helps someone out there!
So i've opened mine up - was due for a screen replacement anyway - tada bad contacts to the radio module (dry solder joint) physically pressed the radio module and it turned straight on. *i've added some paper layers underneath to keep *merckanikal* pressure on it (easier fix than reflowing) and now i know where it chip is i can press on the screen to add a little more if it doesn't work
It really ****ed me today however(seemed to cause phone to bsod, then reboot without radio) and the reason i've spent the last 3 hours replacing the screen and ****ing with the radio.
(whole day of work lost thanks to it. won't see that time back)
In other news i went and tested the note 8's spen - and i think i'm retiring the 10 this week. althought i've just fixed it shes' let me down for the last time.
The only negative i've gotten from the mechanical pressure is the lcd is showing a slight tinge of red now that the glue has hardened. and theirs pressure on the back of the screen. i used 4 layers of 80gsm paper (folded) to pack it out. i'm hoping as the phone heats and moves the paper will compact slightly more and the red blub on the screen will dissipate entirely -
- restarted over a dozen times to confirm the fix is atleast working for me. bootloader'd recoveried etc.. hasn't disabled the radio since..
Hope this helps for any of you still hanging onto the htc10.. (the pixel2's daddy, seriously just feels like the exact same phone*thats what she said?*)
time_lord2004 said:
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
Click to expand...
Click to collapse
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Dissmeister said:
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Click to expand...
Click to collapse
Did It Really Works
Adeel Ali said:
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Did It Really Works
Click to expand...
Click to collapse
Yes it works.
yldlj said:
Yes it works.
Click to expand...
Click to collapse
Brother Did U Tried It U Also Have HTC 10
Adeel Ali said:
Brother Did U Tried It U Also Have HTC 10
Click to expand...
Click to collapse
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
yldlj said:
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
Click to expand...
Click to collapse
Yes I Went From Oreo To Nougat Once
Adeel Ali said:
Yes I Went From Oreo To Nougat Once
Click to expand...
Click to collapse
Then erase persist. Or get back on oreo
RUU worked for me
Hello! I am going to describe my issue with 2 years old nexus 5x which is restarting randomly.
It all started a couple of days ago when my phone started to ask me to enter PIN code. That happened randomly. After entering the code my phone worked completely ok.
But yesterday it started restarting on its own. The restart happened once, than I suddenly got a message before loading screen saying: "Your device is corrupt. It can not be trusted and may not work properly".
Today my Nexus restarted around 10 times. These restarts do not depand on phone usage, since it is restarting randomly (when charging, when not charging, when using it, when screen is off).
I decided to clear cache partition factory reset it and update apps. Unfortunately that did not help, since my phone is restarting even more frequently. Normally it freezes for 5 seconds and than restarts. Sometimes I still get the message: "Your device is corrupt...", but not always.
My Nexus has not been modified (it is not rooted and it is running android 8.1 with november security patch). Also apps have been installed only from play store and not from unknown sources.
I would really need your help. Has anybody experienced any similar issues or does anybody know what could cause the restarting?
Thank you in advance.
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
rp158 said:
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
Click to expand...
Click to collapse
Thank you for your response. Is installing a custom rom the only possible soultion?
No. It's no solution. It's a vague trial.
tic_tac7 said:
Thank you for your response. Is installing a custom rom the only possible soultion?
Click to expand...
Click to collapse
If you are original owner of phone for up to 30 months, go here and let LG fix (or attempt to) the phone. Mine required two repairs. If you are not in the US, check with LG support in your country.
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Renos_Z said:
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Click to expand...
Click to collapse
I already use Nova Launcher, so I dont think this will fix my problem. Now its taking more time between rebooting cycles buts its still there.
I guess my last attempt will be to flash a stock ROM and see if it works.
CaioBomani said:
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
Click to expand...
Click to collapse
reflash firmware via Odin. gert FW(firmware) from sammobile.com/firmware and use SamFirm to download, as it downloads 4x faster than from thr site directly. When flashing, use the HOME_CSC vs just the CSC file, as the csc factory resets whereas home_csc keeps your files and settings etc etc. If that doesnt fix it, you have a hardware issue(IMO, at least, and ive been rooting samsungs for a decade). If you have a hardware issue, id get it as good as i could and use the trade-in specials sammy has going