Hi guys.
I have a problem wih my phone. When I bought it the operating system was android 5.0.1 and the phone constantly reboots so I changed it to android 4.4 (original version) with Odin and nothing changed. There are periods when is working fine but just few days,in rest the phone keeps restarting especially when battery level is below 50%.
I'm thinking to change the system to cyogen or something else but I don't know if this will work .
What can I do in this case? Thanks!
Related
Hello to everybody,
I am new user of a galaxy s2 which I byied used, .
During the last days, I've noticed that the screen sometimes turns on without any obvious reason to me. After 2 or 3 seconds it turns off and so on.
During these same days, after some calls, I get a notification fot "vingo" to have access to some of my phones hardware, which I decline.
My phone has the ics 4.03 version of android, and specifically the polish one (I live in Greece)
my kernel version is 3.0.15-Ι9100XXLPS-CL294511 [email protected] #3 .
any advice ?
since my phone runs a polish firmware, it has already been rooted ?
and if yes,could/should I return it somehow to the previous version of android GingerBread ?
or is there a way apart from reset to default values,to eliminate this problem ?
thanks in advance for any answer.
this is probebly due to some backgrond data /apps,
factory reset is the sysmplest way,
backup with Titanium and reset
restore apps only one by one monitoring the issue....
Hello everyone,
I'd be grateful if anyone can help me out with a problem I'm currently experiencing with my Galaxy S3.
The phone basically won't boot. It powers on fine, goes through the custom logo (for my network provider, Three) and then goes into the Samsung logo. There it stays, unable to boot.
What I think has caused this is that Three notified me of an over-the-air update to Android 4.3 from Android 4.1.2. I downloaded the update, and ran it, but I don't think it completed successfully and so the phone's firmware is probably now corrupt.
I sadly didn't take a backup and would really like to get the phone working again without losing text messages, apps, app data and so on.
I've looked at various options. I have the correct stock ROM/firmware for the phone (H3G version of 4.1.2). I could use Odin, or I could probably install Clockwork Recovery and use that. But I don't know exactly what I'm doing and in particular, how to keep my app data.
Any advice greatly appreciated.
pmattingly said:
Hello everyone,
I'd be grateful if anyone can help me out with a problem I'm currently experiencing with my Galaxy S3.
The phone basically won't boot. It powers on fine, goes through the custom logo (for my network provider, Three) and then goes into the Samsung logo. There it stays, unable to boot.
What I think has caused this is that Three notified me of an over-the-air update to Android 4.3 from Android 4.1.2. I downloaded the update, and ran it, but I don't think it completed successfully and so the phone's firmware is probably now corrupt.
I sadly didn't take a backup and would really like to get the phone working again without losing text messages, apps, app data and so on.
I've looked at various options. I have the correct stock ROM/firmware for the phone (H3G version of 4.1.2). I could use Odin, or I could probably install Clockwork Recovery and use that. But I don't know exactly what I'm doing and in particular, how to keep my app data.
Any advice greatly appreciated.
Click to expand...
Click to collapse
What does the device name and all show In the download mode
Sent from my GT-I9300 using XDA Premium 4 mobile app
Hello,
I have an MTK6589 phone GFive G9 phone with 4.2.1 Android version firmware custom added on the phone (not part of the settings coming with the phone). More information about the version is in the attached screenshot.
Generally, the phone is working fine but I have been experiencing issues with random restarts when using the phone. This happens approximately once a day, the phone freezes for around 10s and then restarts and continues working normally. I believe that this is relate do some of the apps I have installed on the phone, but I am uncertain which ones or if this assumption is correct.
I would like to get to the root of the problem, could you help me determine what is causing this issue?
Is there any log files that could help me with this or is the only way to go and start uninstalling random apps until I discover which is causing issues?
Is there any way to determine that the issue is not in the ROM itself?
Thank you,
Hello!
A few days ago, I used CM12 Unofficial with Android 5.0 and ArchiKernel, and it worked fine. While I was using it, the phone turns off and reboots. Showed the "Samsung Galaxy SIII" logo and rebooted, in a bootloop.
I flashed the rom back, wiped all, and nothing, the bootloop still happened. I flashed it with Odin, to Android 4.1.2. The phone works, but when I use it some minutes turns off and goes into a bootloop. When I run an Antutu Benchmark also turns off.
Researching and playing with kernels, adb, and roms, I discovered that turns off when the processor runs at over 1200MHz. This happens with every kernel, also stock.
What happens and how can I make it work normally again? Thanks
Click to expand...
Click to collapse
The problem was the battery. After changing the battery the phone worked fine again.
It's obviously a hardware fault, you can't fix it.
So I had this SGP321 for over a year now.Bought it brand new from this guy on the internet for a suspicious low price.Not a real shop or anything so no waranty. It worked very well for a few months then I noticed it started rebooting every now and then.After a OS update that was rolling out at that time (can't remember the version) the reboots were more often.After the KitKat update arrived and I downloaded it,after the process was over and the phone had to reboot,it entered a reboot loop that could not be stoppped (apart from forced shut down,but with same thing when trying to turn back on). I repaired the OS with the PC tool,no changes.I flashed older versions of stock OS with flashtool,reboots every couple of minutes. Then I installed Cyanogenmod 11.That worked very well,no reboots,but had many bugs and battery draining fast in stand by (about 1% per hour no matter what I deactivated,or with various apps to induce deep sleep). The new CM12.1 does not work,keeps rebooting.
Now,yesterday I tried again and again to get the tablet to work with a stock ROM. I only intend to use it for reading comic books,so all I want is a stable ROM with good battery life.So I would like to have a stock one. But why does a custom one run fine on it and a stock one keeps rebooting? I tried Sony forum but they were at a complete loss and sent me here for help.Any ideas?
rammstein_08 said:
So I had this SGP321 for over a year now.Bought it brand new from this guy on the internet for a suspicious low price.Not a real shop or anything so no waranty. It worked very well for a few months then I noticed it started rebooting every now and then.After a OS update that was rolling out at that time (can't remember the version) the reboots were more often.After the KitKat update arrived and I downloaded it,after the process was over and the phone had to reboot,it entered a reboot loop that could not be stoppped (apart from forced shut down,but with same thing when trying to turn back on). I repaired the OS with the PC tool,no changes.I flashed older versions of stock OS with flashtool,reboots every couple of minutes. Then I installed Cyanogenmod 11.That worked very well,no reboots,but had many bugs and battery draining fast in stand by (about 1% per hour no matter what I deactivated,or with various apps to induce deep sleep). The new CM12.1 does not work,keeps rebooting.
Now,yesterday I tried again and again to get the tablet to work with a stock ROM. I only intend to use it for reading comic books,so all I want is a stable ROM with good battery life.So I would like to have a stock one. But why does a custom one run fine on it and a stock one keeps rebooting? I tried Sony forum but they were at a complete loss and sent me here for help.Any ideas?
Click to expand...
Click to collapse
Seems that it has hardware problem like corrupting internal Flash memory or smth else, that is very difficult or imposible to fix by reflashing.