Galaxy S III 19300 has developed a problem where every time i try to use the phone i.e press power button and then swipe, the screen sleeps, Sometimes it sleeps after 10 seconds sometimes before i even swipe. Factory reset done, have now rooted it, but need to ascertain if it is a hardware failure or bug. I managed to set time out for the longest setting and obviously usb debug mode but wonder if its a power issue or gpu or driver issue etc.... please can anyone help?
Hopefully you're still on a stock rom.. Theres a ussd code to bring up a test app. You'll be able to test the proxy sensor etc from there.
If everything seems OK or if you have a custom rom then you'll have to download the firmware and odin on a pc and flash the phone back to stock. You'll need to flash the firmware, factory reset and flash again. That way you know there isn't any remnants left over from the last time it was used/flashed/rooted. This is the only way to find out if it's a hardware or software issue without all the faff.
Beyond not having the phone in my hand that is the only advice worth giving. If you keep chasing shadows you won't find the problem. Best to nip it in the bud.
ussd code
shivadow said:
Hopefully you're still on a stock rom.. Theres a ussd code to bring up a test app. You'll be able to test the proxy sensor etc from there.
If everything seems OK or if you have a custom rom then you'll have to download the firmware and odin on a pc and flash the phone back to stock. You'll need to flash the firmware, factory reset and flash again. That way you know there isn't any remnants left over from the last time it was used/flashed/rooted. This is the only way to find out if it's a hardware or software issue without all the faff.
Beyond not having the phone in my hand that is the only advice worth giving. If you keep chasing shadows you won't find the problem. Best to nip it in the bud.
Click to expand...
Click to collapse
Hi, thanks for your response. Yes i'm still on still on the stock rom and do not believe it was ever flashed/rooted. I will take your advice and try your suggestion. Where would i find the USSD code for the test app?
Dial *#0*# for the diagnostic screen.
Related
I recently flashed CWM onto my uncles GS3 and rooted his current rom. I made a backup and then tried out a new AOSP rom, which we decided not to keep because my uncle did not like it. But now, returning to the old rooted stock rom, every time the phone disconnects from wifi, it completely freezes up on the lock screen. Pressing the lock button does not shut off the screen and instead just locks it. You are unable to unlock it as the phone completely freezes up. The only way to get into the phone is to double tap home to get into the voice commands, and then go to home from there.
But even after that the phone continues to freeze. I tried another ROM on his phone today, but the problem still persisted a while later. It all happens when the phone is connected to wifi, and you walk out of range. After which the phone starts to freeze up.
I'm totally unsure whats going on. I just flashed the rom again, and we are trying a clean slate with no restoring of any data. It may have started to happen after we installed root browser (just as a guess), but we could be completely wrong.
If this continues again on this rom as well (which is Revolution HD) Im going to go back to completely stock (rom & recovery), and hope it still doesn't persist there. If not then I am out of options, and I have no clue what to do.
Any help would be GREATLY appreciated. We spent so many hours today trying to resolve this.
Thanks!
Usualy WiFi problems are kernel related. Have you tried Siyah or another custom kernel?
If this will not help than returning to stock with all wipes is the best idea, this should resolve your problem. If not, than you can try to reset router or set static IP for s3. Also try to remove WiFi setting for your home network in the phone and set it again manualy or via WPS mode.
i9.0.1.3k galaxy imperator
SirKunon said:
Usualy WiFi problems are kernel related. Have you tried Siyah or another custom kernel?
If this will not help than returning to stock with all wipes is the best idea, this should resolve your problem. If not, than you can try to reset router or set static IP for s3. Also try to remove WiFi setting for your home network in the phone and set it again manualy or via WPS mode.
i9.0.1.3k galaxy imperator
Click to expand...
Click to collapse
Thanks for the reply. This issue has been occurring between two different roms, so can the kernal still be an issue? Its happened with the absolute stock rom (w/ root) and Android HD Revolution.
My uncle said he would play around with the phone and let me know if it freezes again by tomorrow. If it does im going to wipe and stock.
Can anyone show me where to get the stock roms for the i9300?
I've downloaded and tried 3 different ones, but the phone never manages to boot up!
JitinDhillon said:
Can anyone show me where to get the stock roms for the i9300?
I've downloaded and tried 3 different ones, but the phone never manages to boot up!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671969
Sent from my GT-I9300 using xda app-developers app
JitinDhillon said:
Can anyone show me where to get the stock roms for the i9300?
I've downloaded and tried 3 different ones, but the phone never manages to boot up!
Click to expand...
Click to collapse
Same problem on Galaxy Note N7000, did your problem resolve by reverting back to stock because I've tried every possible option, to no avail?
juliobahar said:
Same problem on Galaxy Note N7000, did your problem resolve by reverting back to stock because I've tried every possible option, to no avail?
Click to expand...
Click to collapse
Go into recovery and wipe the cache, I believe that was my problem.
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?
Hey Guys,
I use a stable 10.1.3 CM since a year on my S2. Lately the camera started to quit qorking: "can't connect to camera".
About this time the torch (LED app) app did the same thing: "unfortunately torch has stopped".
What I did: do a full data/cache/dalvik cache erase: factory reset.
The camera/torch still malfunctioning.
Then flashed the last nightly CM: cm11-20140429, but still no luck.
Then reflashed the old stable version, maybe if it'll work, but noooo.
Do you have any suggestion to resolve this issue? My phone is 2 years old, never had a problem with it. Until now.
Shall I flash something via Odin?
Is there a "deeper" way to rewrite the camera/LED firmware/code/whatever?
(I was wondering if flashing these 2 CM versions the appropiate firmware's aren't rewritten)
Thanks in advance for the replies!
you can try more ROMs. However, there is a possibility that its a hardware issue.
The camera stopped working on my galaxy S1 after a factory reset.
I never did get it working again, and I tried about 4 different camera firmwares, flashing back to stock, and replaced the camera module too. Nothing worked.
knuckles1978 said:
The camera stopped working on my galaxy S1 after a factory reset.
I never did get it working again, and I tried about 4 different camera firmwares, flashing back to stock, and replaced the camera module too. Nothing worked.
Click to expand...
Click to collapse
Sorry to hear that.
I'm wondering now to replace the camera module as well.
I quickly tried this 3 ROM: aosb_kk_1.3.6_i9100, omni-4.4.4-20140728-i9100-NIGHTLY, Slim-i9100-4.4.2.build.5-OFFICIAL-4068, but with the same disappointig result: no camera, no LED.
If I first start LED/torch isntead of camera, the LED sometimes flashes:
I switch on, but nothing happens. Then switch it off: after a few sec delay the button will show the "off" state, and during this process the LED flashes for 1 sec.
I will try to revert to stock with odin, maybe...
The camera module is very easy to change. All you have to do is unplug it and plug a new one in.
You might be luckier than me.
knuckles1978 said:
The camera module is very easy to change. All you have to do is unplug it and plug a new one in.
You might be luckier than me.
Click to expand...
Click to collapse
Yes, but what if the same thing will appear? Ie. I'll change the camera module, but won't work.
Isn't there an easier way to check if surely the camera moduled is dead?
Btw I downgraded it to stock ROM via Odin, but camera still dead, so it is probably not a software error. :crying:
There's no way of telling if your camera module is broken without putting a new one in.
It didn't fix it for me though. And believe me when I say I spent a lot of time trying to figure it out.
Ok then.
Thank you very much for the support!
Hi guys, this morning my father's Le Max 2 (snap820, 4/64) stopped receiving calls, and both the home and recent apps virtual buttons decided not to function, too. Strange enough, I'm able to long press them and get the action I'm supposed. Any ideas/fix? I've already checked the phone for malicious apps and misconfigurations
Hi, I have exactly the same issue, plus I cant download any more applications from play store. Can anyone help?
If you have a backup taken when the phone was working well, I'd suggest you to restore it. If not, try another ROM, or at least a different ROM flavor (if it had an EUI based ROM, use LineageOS and viceversa). If that doesn't work, you may need to get into Qualcomm recovery mode and flash the developers ROM to get the phone to a real factory state.
But first, try to revert to factory settings from the current ROM, and see if that solves the issue.
There are several threads here with info on how to apply the above solutions.
If none of these solutions works, and you still have warranty time left, you may want to contact the seller for a repair or replacement.
Good luck.
Do the notifications work?
I was on holiday, so no PC I could use for flashing or else. A reset from the settings worked, still don't know what caused the issue sadly
I couldn't find the fix for this in any other threads, can someone help a not-terribly-tech-savvy person with a fix for this
Today I also had a same problem. So just I backed up all important data's and done factory reset. Now everything works fine.
Everyone have same problem at the same time means the ROM has virus or Trojan.
What is the ROM everyone is using?
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.