Good morning.....
At&T Samsung S7 G-930A(verified - bought from AT&T and checked on settings / internal)
Anyone else having issues recently? Latest update seems to brick the phone.
I tried many different firmware versions, but only TB1 seems to allow it to load and proceed through installation. Tough to find, but here is link.
https://mega.nz/file/xt4l3AgK#cfzcMT...LN8QqN7tqrp0Ew
from Ryzir
Even after updating to latest firmware, clean install, caches wiped, and minimal use......phone still runs hot and seems to restart.
I recently changed battery and was able to get further than before (actual loading and use of android on phone), but phone still restarts intermittently (about every 10 minutes).
Is the phone just broken? or is there a potential software fix?
Related
i just got my note pro 12.2 wifi version (international) a few days ago and already experiencing problems, firstly the wifi was so slow so i updated it OTA to the latest stock firmware i can't remember what it is but it's the latest official 4.4.2 they have and that improved the wifi but now i'm encountering issues of rebooting randomly after using facebook app. it's always after i lock the screen it suddenly reboots after 2 mins or something especially if i have say been using a lot of memory for it.. ie if i scroll down 4000 friends that's when it always reboots once i lock the screen. is this liekly to be hardware or software issue or an app issue?
i have only had it a few days so haven't managed to play with it enough to test it to the max.
just now it rebooted and i played one youtube HD video and used multi window to use the facebook app (old version 7.0 - i like this version).. but i hadn't used the facebook app that much while on, the only thing i did different was i plugged in my samsung s3 charger into the note pro to test how long it would take to charge using a usb 2.0 connection instead. it's official charger official cable, is that likely to cause reboot issues?
previously it was just after using facebook for a long time for a ram intensive amount, i also tested it after reboot and using facebook a bit and locking screen and it didn't reboot so it made me think ok it's just when facebook is being used a lot and all the ram and memory is exhausted caching 4000 friends viewing so i didn't think anything of it.
is this likely to be hardware or software issue? are hardware issues ever the main problem with rebooting?
I know the usual tests, having to use odin to flash official firmware, trying a different facebook version, removing and not using facebook at all and see if it still reboots and lastly factory reset.
ideally i'd like to avoid all of those things as it is a major hassle and i can live with the reboot issue provided it isn't a hardware problem. is there anyway to test it to know for certain it is hardware and not software and the app?
edit: it keeps rebooting even if i dont use the app
seems to happen when i lock the screen sometimes it just reboots randomly.
anyone else have this?
You could try to remove that facebook app and see if that fixes the problem.
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
pete101 said:
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
Click to expand...
Click to collapse
Could it be a bad sector on the SD card? I'd long format it using a pc to be sure.
Sent from my SM-P900 using Tapatalk
it's not the faceboook k app i've realised now it just coincidentally seemed to be that as it is ram intensive.
i factory reseted and then put the app back on but didn't log in. 3 times it has rebooted by itself over different scenarios.. 1 plugging in a samsung usb 2.0 charger from a samsung s3, 2 when unmounting sd card, 3 when closing the screen when any ram intensive app is in the background (there's still like 500mb of ram left!! i dont know why it's rebooting like this.
i can't figure it out. is anyone else having these issues? im not sure if it's a kitkat 4.4.2 issue.. reading forums from other users with different devices i'm seeing the reboot issue coming up alot especially on the s4.
http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046/page22
but i dont know for certain if it's a hardware issue.
my next steps which i really want to avoid is to factory reset AGAIN and not load any apps (the problem with this is it requires a certain amount of ram intensity to be used before it randomly happens.. if i dont add any apps like instagram or facebook or tumblr i can't get it back to the state where it reboots randomly)
i've also enabled all apps (i usually disable all the bloatware i can without being rooted) but it does bring up errors of android.core.process has stopped etc and some gapps errors (im hoping this is the cause of the reboot) and see if it reboots. it's difficult recreating the scenario consistently.
i udnerstand it might reboot if you've overused the memory but it clearly shows lots is free so i can't figure out what is causing it?
my next step after all this is to flash the latest version of stock so i can't put it down to the OTA updates that is causing it. if that fails i revert to odin to flash the original 4.4.2 it came with.. and failing that i'll have to return it
does anyone have any ideas whether it is hardware (maybe the power button is slightly off so when you press down it in a certain angle it triggers a restart?)
or is the motherboard or corrupted sector of the memory which when it writes over it causes the reboot?
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
If it were me I would yank the microsd card out, factory reset, set up just my gmail without allowing auto backup/restore and apply all updates. I'd then let the tablet run for a full day and use it just for web browsing and Youtube to see if the problem is still there. I would not install anything for at least a day, including the microsd card. This would be as stock as one could get and rule out the possibility of it being any software that I installed or the microsd that I was using.
I suspect it's software but the only way to know is to be patient and test it out for sure.
Sent from my SM-P900 using Tapatalk
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
orobin said:
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
Click to expand...
Click to collapse
Assuming you have custom recovery installed as well; have you tried wiping dalvic? It will force applications to recompile and possibly fix a corrupted application or its associated files.
Hi,
I just checke.…
I was thinking that the root method was not setting the knox flag, so i was thinking there is no recovery in the file flashed… .
I was wrong.
My waranty is void, knox is set. I still have no custom recovery : in the file provided by chainfire, there is a recovery which is probably coming from samsunG…
So i will install a new recovery and try to wipe all caches dalvik.etc.
Hi,
since my knox is set now :
I tried to install TWRP recovery, which allow me to do a wipe of the cache AND dalvik Cache.
it did not resolved anything. the tablet still reboots randomly.
then, I decided to restart from scratch :
I flashed the same firmware I had, using ODIN, and do not root it.
this is this firmware : http://www.sammobile.com/firmwares/database/SM-P900/XEF/
I will keep you updated if it solve the reboot issue or not.
thanks
Olivier
pete101 said:
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
Click to expand...
Click to collapse
Hi
I had the same problem and also thought it was the power button that was faulty but then I flashed the previous firmware then tried to use it a bit and no reboots since so I guess samsung released a new firmware that solved the slow wifi problem but then boosted it a little too much or so it seems judging by the reboots whenever there's too much overload.
So I guess for now I will stick with an older firmware
oops... it rebooted while I was surfing the play store so I guess I spoke too soon
Hi, everyone, sorry to bother you, but I'm in a bit of a pinch.
My unrooted stock Nexus 5 was running smoothly with then latest OTA update 5.0.1 until I got No SIM card error. I eliminated SIM card as problem source, removed SIM, discharged it completely and after few days turned it on and it was working. But problem returned soon and same method didn't show result. So things I already did:
- check my card in other phone: works
- check other cards in my phone: doesn't work either
- left it off without SIM for a few days
- erase cache
- upgrade to OTA 5.1.0
- factory reset
- unplug battery from motherboard for some time
- flash stock 4.4.4 from developers google com
- put some tape on card to make contact better
in this order. My next move would be to check if SIM card case pins are broken. Warranty expired month ago so there's that. Do you have any advice to give me? Is there any part of the phone that could've stayed not wiped during 4.4.4 stock flash and that's the reason problem remained?
You have a weather widget, clock, GPS location app that is causing the issue. Try uninstalling one at a time until you find the culprit. For me it was transparent weather clock widget that was causing this. Something about the way the app polls the GPS location causes problems.
I flashed stock 4.4.4 and only stock apps are present. I can either uninstall upgrades or root and delete gapps for good. What say you? I think phone somehow got "stupid" hard and I have to reset certain part that wasn't affected during flashing because it haven't once worked throughout process.
My nexus 5 is doing the exact same thing, exactly as you described, since the update. I'm losing my mind
Seeing as we both have the issue I don't think its a problem with your phone in specific. If anyone knows please help! I've tried uninstalling every app, going on safe mode, swapping sims etc
ag1000 said:
My nexus 5 is doing the exact same thing, exactly as you described, since the update. I'm losing my mind
Seeing as we both have the issue I don't think its a problem with your phone in specific. If anyone knows please help! I've tried uninstalling every app, going on safe mode, swapping sims etc
Click to expand...
Click to collapse
If it happened immediately or just after update try flashing stock KitKat.
Got the same trouble
The problems begun 1 week ago with interruptions with the radio, i have to restart the phone with Stockrom 5.1 self flashed and uber-kernel to get any connection. Switch the airplane mode often to get any radio signals. I ask my provider o2-germany for some trouble in their radio stations - and there was, just a few hours it worked. In a few days ago I traveled across germany, from the south to the north and back, got while traveling no good receptions, only gprs and edge. And now I switched from stock-rom 5.1 to OptiPop 5.1 the trouble begins with no-simcard ...
I will try xTraSmooth 5, when this ist not working i try an older image...
Edit:
OptiPop working now without flashing UBER Kernel. Now Issues so far!
Mine is absolutely stock on 5.1, not seen it once in 18 months and now it has done it twice in 12 hours.
I've always been completely stock and my phone started doing this every time I reboot it. Any more word on this? It also does seem my GPS looses lock on a lot too. This seems to have started since the last OTA update a few weeks back or so.
after i flash latest factory image mmb29v I got No SIM card error. There is an error in Safe Mode and SIM card not detected .pleas help me
I've got some very strange issues happening since the latest T-Mobile update to baseband G930TUVU2APC8.
The phone is a T-Mobile Galaxy S7 with a Sandisk 200GB micro SD card installed
Whenever I'm on a phone call through a my Jawbone Era (and charging; I haven't tried it unplugged) the phone will behave as if it did a reboot, without actually rebooting, every few minutes. The phone will stop responding for about 20 seconds, then show just the wallpaper for about 5 seconds, then go back to the lock screen. At this lock screen it requires me to enter my password instead of using fingerprint as if it had just powered up. The phone call does not drop through all of this.
The next issue is that some pictures taken from the quick launch are sometimes not saved. I'm not 100% sure that this only happens after the reboot issue above, but I think it does. I have secure startup disabled .
I tried a factory reset which did not fix the issue, contacted t-mobile and was sent a replacement device that still has the problem. None of this was happening prior to the latest update.
Has anyone else experienced these issues? Also, is it possible to downgrade the firmware version?
Thank you,
Matthew
techy101 said:
I've got some very strange issues happening since the latest T-Mobile update to baseband G930TUVU2APC8.
The phone is a T-Mobile Galaxy S7 with a Sandisk 200GB micro SD card installed
Whenever I'm on a phone call through a my Jawbone Era (and charging; I haven't tried it unplugged) the phone will behave as if it did a reboot, without actually rebooting, every few minutes. The phone will stop responding for about 20 seconds, then show just the wallpaper for about 5 seconds, then go back to the lock screen. At this lock screen it requires me to enter my password instead of using fingerprint as if it had just powered up. The phone call does not drop through all of this.
The next issue is that some pictures taken from the quick launch are sometimes not saved. I'm not 100% sure that this only happens after the reboot issue above, but I think it does. I have secure startup disabled .
I tried a factory reset which did not fix the issue, contacted t-mobile and was sent a replacement device that still has the problem. None of this was happening prior to the latest update.
Has anyone else experienced these issues? Also, is it possible to downgrade the firmware version?
Thank you,
Matthew
Click to expand...
Click to collapse
The problem started in PB8 firmware, PC8 firmware has constant wifi dropout issues, you might find even that at 3G connection performing better than fiber optic wifi internet.
Easiest is to update facebook to latest version and see how many "can not connect right now" errors.
Random reboots is normal never mind how many times your factory reset or do a full firmware PB8 flash.
T Mo is not the brightest tools in the shed, it takes 5 visits to their T Mo offices to get the accounts and products purchased + refunds for items payed in cash or freebies refunded etc etc etc.....
Folks,
During a recent power outage my battery completely drained for the first time. Powering on after a full charge, started getting screen msgs (yellow text) info on some system internals. tried rebooting, and got "failure to load efs". and the phone comes back up in Factory test mode. I had never attempted any modification on this phone and everything looked stock to me. I had bought used from B&H, so cannot swear to its complete history. Samsung recommended a "smart Recovery from Best Buy that after two swap-outs i am still getting all the above msg's. I have no experience in rooting or anything else, but have a background in software. Info found through searches seems to indicate Verizon Samsung sg3's may be the most difficult to add mods. I found a stock rom, and loaded it successfully via odin. Best Buy guy said he loaded an original stock as well, and still no luck. Even though this happened after a hardware issue, and i know its firmware, at a loss as to what is causing this. it generally degrades performance of the phone in everything, including linking to playstore to download apps. I have everything backed up, with nothing to lose if anyone has a path to a working phone....I'm game. running 4.4.2
The situation is following: For two months the device worked flawlessly. Some time ago, my phone started to randomly hang and reboot. I was unable to find any pattern with these reboots - it could work through an hour of stability test and fail when I was reading a book. Lately, the situation got much worse - the phone may reboot many times right after OS boot up. I thought the problem is with my sd card, but when I removed it, nothing changed. I also tried to update the ROM I use(It was fulmics 2.0, so I flashed 3.0). And I noticed, that reboots may happen even in TWRP(luckily, none happened during the installation of ROM).
The questions are:
1) Is it possible to properly diagnose the cause of the problem? If not, what may be the cause?
2) What to do now? I believe the only possible ways are to replace motherboard or take phone to service(and they essentially will do the same thing - just replace the motherboard)