Ok hello i'm pretty new to this, but I have looked around quite a bit and nothing seems to help. So my friend gave me this Galaxy S6 edge(more specifically the SM-G925I - TCE Mexico (Telcel)). The issue with this phone is that it freezes then restarts randomly and it also doesn't recognize the carrier. It recognizes that theres a sim but the carrier is not recognized and I don't have access to mobile data. The bigger issue at the moment is the crashes though. I already tried resetting to factory defaults, booting in safe mode, wiping the cache and wiping all the data/ factory reset from the recovery menu. I thought it was the OS or something so I installed twrp wiped EVERYTHING(pretty sure I did since when I rebooted twrp told me if I was sure since I had no os installed) and installed the official 7.0 firmware update from sammobile. It was previously 6.0.1 and I thought having a different version might fix the issue. Yet the issue remains, within a few minutes of me using it it freezes, turns off, and reboots. At this stage I might you might think its a hardware issue but when i'm in recovery or download mode it doesn't turn off. Also I decided to leave it charging when I left for work and when I came back it hadn't turned off at all. I checked the uptime and it was at 7 hours and yet within a few minutes of me checking the settings it froze and turned off. I'm not really sure what to do anymore i'll probably take it to a service center to see whats up but I wanted your opinions first. Thanks.
Sochez said:
Ok hello i'm pretty new to this, but I have looked around quite a bit and nothing seems to help. So my friend gave me this Galaxy S6 edge(more specifically the SM-G925I - TCE Mexico (Telcel)). The issue with this phone is that it freezes then restarts randomly and it also doesn't recognize the carrier. It recognizes that theres a sim but the carrier is not recognized and I don't have access to mobile data. The bigger issue at the moment is the crashes though. I already tried resetting to factory defaults, booting in safe mode, wiping the cache and wiping all the data/ factory reset from the recovery menu. I thought it was the OS or something so I installed twrp wiped EVERYTHING(pretty sure I did since when I rebooted twrp told me if I was sure since I had no os installed) and installed the official 7.0 firmware update from sammobile. It was previously 6.0.1 and I thought having a different version might fix the issue. Yet the issue remains, within a few minutes of me using it it freezes, turns off, and reboots. At this stage I might you might think its a hardware issue but when i'm in recovery or download mode it doesn't turn off. Also I decided to leave it charging when I left for work and when I came back it hadn't turned off at all. I checked the uptime and it was at 7 hours and yet within a few minutes of me checking the settings it froze and turned off. I'm not really sure what to do anymore i'll probably take it to a service center to see whats up but I wanted your opinions first. Thanks.
Click to expand...
Click to collapse
*#0*# test if all sensors,cameras,speakers,etc are working.Test wifi,gps,bluetooth.Try to see if charging port is clean inside...
Related
Hi, I'm having a curious problem with my S3 and I've been unable to solve it. I watched the "noob" video and tried searching these forums as well as a google search with various combinations of the wording for my problem. Nothing matching my issue turned up, I hope I didn't miss anything.
I recently bought a S3 second hand (yes, i know, i should have known better). It was rooted and running some kind of custom ROM when I first turned it on, but I was willing to deal with it until I double checked the procedure for getting it back to stock and starting again myself (nothing against the original rooting and flashing, just like to know exactly what I'm running).
When I purchased the phone I obviously checked that all of the main things worked - calling, texts, mobile data, wi-fi etc. I get home and connect to my home wi-fi and start checking things out and setting stuff up. The phone randomly rebooted. I carry on after the reboot and about 10 mins later, another restart.
To cut a long story short, there is something wrong with the wi-fi. If I turn off wi-fi in the settings menu and reboot, everything works great. No crashes, no reboots. If however I enable the wi-fi about 50% of the time it will crash while wi-fi is activating. The other 50% of the time, it will crash as it goes into the screen lock (either via timeout or pressing the button).
I've re-flashed to it's stock version of Android (using the 'Samsung GS3 Toolkit and Odin), same problem. Anyone got any ideas?
Thanks in advance
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
boomboomer said:
You can try updating the modem and RIL to the right version for your country, search in general forum. If it still reboots then try with another wifi source - I've seen some routers cause problems on client machines.
If you do a factory reset when you flash the modem, plus you have the latest stock ROM on board, then any remaining problems are probably hardware.
Test it fully after the factory reset, before you add any apps etc.
Click to expand...
Click to collapse
After much experimentation and flashing of various files to my phone I have further narrowed the problem. I've still not solved it, but getting closer I feel.
After a clean ROM flash it works like a charm regardless of how much i use the wifi etc. It's only after the first reboot that the trouble starts. It will begin randomly restarting. If I perform a factory reset from recovery mode, it works again, but starts resetting again after a reboot.
Any ideas?
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
go in e3 recovery and perform factory reset
DrushNL said:
First off all, I'm not sure if this question is answered else where.
I have my S2 almost since the day it came out in NL.
Today a problem occurred. After I boot my phone it keeps rebooting the launcher (not sure if that's the correct name). The phone it self stay's on, I don't go back to the Samsung logo or what else - just Android it self keeps rebooting.
I run Go Launcher Ex for a long time, never had problems with it.
I assume it's a memory problem.
Had a similar problem about a year ago, where my internal memory was stuffed. After removing some apps etc. my phone was just fine again. Problem today is I cant do anything. Connection with pc fails, because of the rebooting software. I'm not even fast enough to get to the Android settings.
Edit: I tried booting in Safe Mode. Which works, till it reboots into normal mode.. and keeps rebooting. And of course there's no time to get something done in safe mode.
- Phone get's really hot when this all happens. An other indication for a stuffed memory(card) I think?
- Removed the SD + SIM, no changes.
Edit:
I was quick enough to change the launcher to something else (i believe Nova, via Home Switcher). Then reboot my phone in Safe Mode with Nova on, then the reboot of the software starts again.. and it forces itself into Go Launcher Ex without Safe Mode.
Thanks in advance,
Click to expand...
Click to collapse
Go to recovery and wipe cache and wipe dalvik Cache. If still not working then do Factory Reset. If the problem is still there than flash the rom again.
Sent from my GT-I9100 using Tapatalk
As my main goal was to get my data from the phone I suprised myself a lot and I'm copying as we speak the whole /emmc/ via SDK tools.
It's gonna take a while - I assume it's copying the whole 16GB.
After that I'll try factory reset's etc. and check if I can use my phone again.
Sup guys, so i just had a really strange problem that popped out randomly, i was watching a youtube video and i had to help a person quickly and when i came back just a minute later i saw my phone showing encryption unsuccessfull when i pressed the power button to turn my screen on. Well it said to factory reset my phone, i don't store any important data on my phone anyways so i just went for it, and it restarted went to my TWRP recovery and tried factory reseting it, to no success. It basically failed to access /data/ and other directories and i can't see any files in them through recovery. And so i can't even factory reset it, i can't install a ROM cause the partition is corrupt i assume. How can i "unbrick" this? I was running the good old Temaseks CM 12.1 ROM, has been working fine for a looong time. My PC recognizes the phone but i can't access any data, it just shows that it's connected, odin doesn't recognize it.
Can somebody help me please ? I use my phone alot and it's really important.
Hello, so I changed my screen few weeks ago, and I started to notice that it won't work propelry, in menu or setting it's okay, but when I try to use apps, some of them wont work as it should. For example, i can't take photo in messenger, i can't send good game in Clash Royale. Screen seller sent my some files to update my phone, but I noticed that i can't get into recovery mode, only in factory mode, I tried to do factory reset, OTA update because mine is still 2016-06-08, but it won't update, I also tried flash those files without recovery mode(when you start downloading ant then turning off your phone), but it didn't work. Have any ideas, what it could be?
SliFaZ said:
Hello, so I changed my screen few weeks ago, and I started to notice that it won't work propelry, in menu or setting it's okay, but when I try to use apps, some of them wont work as it should. For example, i can't take photo in messenger, i can't send good game in Clash Royale. Screen seller sent my some files to update my phone, but I noticed that i can't get into recovery mode, only in factory mode, I tried to do factory reset, OTA update because mine is still 2016-06-08, but it won't update, I also tried flash those files without recovery mode(when you start downloading ant then turning off your phone), but it didn't work. Have any ideas, what it could be?
Click to expand...
Click to collapse
Did you replace the screen yourself or was it a kind of Elephone repair ? .. obviously changing a screen is a major kind of thing and (I would assume) it could cause issues if not done properly.
Have you tried to flash the 2016-06-08 Rom in Splash Tools (or a custom ROM) and checking to see if the issue still exists - Im sure if its your screen it would occur on whatever ROM you were using, as its a hardware fault. Thing is if its just a sioftware "glitch"... I would first flash TWRP in flashtools, then flash a ROM from within TWRP and check if the issue still persists.
Obvioulsy if the issue continues once youve tried this I guess your screen is faulty unfortunately
I would recommend using this TWRP version 3.0.2.8. here: https://www.androidfilehost.com/?fid=24727369092696060
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.