After updating to the OTA 4.3 my S3 now has a glitch causing the screen to occasionally black out, mostly during phone calls but also after screen timeouts when i hit the power button to turn the screen back on it'll stay black for awhile, the menu and back buttons light up and the touch sensor still works even when black. it work flawlessly before the update. I tried to root and was successful at it using the saferoot method but because of the know being lock I can not install a custom rom or recovery and the problem was still there because I was still using the 4.3 rom. So I used odin3 vs3.07 and put the stock rom back on and unrooted and the problem is still there. does anyone know how to fix this glitch or does anyone know how i can go back to the 4.2.1 rom or install the 4.4.2 rom because 4.3 has been nothing but a headache for me.
johnwilliams-84 said:
After updating to the OTA 4.3 my S3 now has a glitch causing the screen to occasionally black out, mostly during phone calls but also after screen timeouts when i hit the power button to turn the screen back on it'll stay black for awhile, the menu and back buttons light up and the touch sensor still works even when black. it work flawlessly before the update. I tried to root and was successful at it using the saferoot method but because of the know being lock I can not install a custom rom or recovery and the problem was still there because I was still using the 4.3 rom. So I used odin3 vs3.07 and put the stock rom back on and unrooted and the problem is still there. does anyone know how to fix this glitch or does anyone know how i can go back to the 4.2.1 rom or install the 4.4.2 rom because 4.3 has been nothing but a headache for me.
Click to expand...
Click to collapse
Wrong forum my friend >> http://forum.xda-developers.com/galaxy-s3-verizon <<
Related
I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
any solution yet to this my 4 soft keys wont work i dont know wat to do
No resolution for soft key fail
monac66 said:
I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
Click to expand...
Click to collapse
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
For the record
Charcaroth said:
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
Click to expand...
Click to collapse
In case anyone else has this issue, I tried flashing a stock Froyo ROM, a stock Gingerbread ROM, CM 7.2 again, and even stock GB with the latest Verizon Wireless update for GB and the softkey functions never returned. I've managed to put Paranoid Android 2+ back on the Fascinate, a Jellybean ROM, so I can mimic the buttons with onscreen controls, but it eats up a lot of screen real estate. It's a workaround, not a solution by a long shot.
Hi
I have a 4.0.3 france firmware installed samsung I9100G.But lately the no lockscreen problem (holding the power button will not bring the options and just shuts the phone off),ringtone and a few other problems started to annoy me really bad.
I'm thinking to install the 4.0.4 german firmware from samfirmware but how stable is it? is there any problem with the 4.0.4 or anything special i should know about it?
i have reflashed the 4.0.3 but those problems didnt go away.
thanks for any helps.
Go back to GB.For me that is more stable than ICS or JB.
Sent from my GT-I9100 using xda premium
If the firmware is official, it should be stable. So, your choice: or GB, or ICS.
burning_afd said:
Hi
I have a 4.0.3 france firmware installed samsung I9100G.But lately the no lockscreen problem (holding the power button will not bring the options and just shuts the phone off),ringtone and a few other problems started to annoy me really bad.
I'm thinking to install the 4.0.4 german firmware from samfirmware but how stable is it? is there any problem with the 4.0.4 or anything special i should know about it?
i have reflashed the 4.0.3 but those problems didnt go away.
thanks for any helps.
Click to expand...
Click to collapse
May be I can help you fix all your 4.0.3 problems instead of messing with your phone.
Post all the problems you are facing, and we'll get started
Swyped from my Galaxy SII
Jokesy said:
May be I can help you fix all your 4.0.3 problems instead of messing with your phone.
Post all the problems you are facing, and we'll get started
Swyped from my Galaxy SII
Click to expand...
Click to collapse
updated to 4.0.4 but nothing changed.
ok here are the problems:
- The power button options are not showing up. if i hold the power button it just closes the phone directly.
- The screen lock doesnt work. Wont lock the screen with any option there.
- The sim lock doesnt work. If i put the sim lock on (put a lock on the sim) the phone starts normally but wont let me call or text. So i have to disable the lock on the sim to make it work normal.
Now these are the problems i have seen so far. When i got the phone it was GB and there was absolutely no prob until updating to ICS. So whats the suggestion, should i give a try on custom firmware ICS or go back to official GB? if you say custom firmware then which one?
burning_afd said:
updated to 4.0.4 but nothing changed.
ok here are the problems:
- The power button options are not showing up. if i hold the power button it just closes the phone directly.
- The screen lock doesnt work. Wont lock the screen with any option there.
- The sim lock doesnt work. If i put the sim lock on (put a lock on the sim) the phone starts normally but wont let me call or text. So i have to disable the lock on the sim to make it work normal.
Now these are the problems i have seen so far. When i got the phone it was GB and there was absolutely no prob until updating to ICS. So whats the suggestion, should i give a try on custom firmware ICS or go back to official GB? if you say custom firmware then which one?
Click to expand...
Click to collapse
It's always recommended to perform a factory reset after upgrading your phone software
Swyped from my Galaxy SII
For me the samsung stock roms are like windows o/s.
GB=xp
Ics=vista
Jb=w7
A crude comparison......but vista was a pile of crap.....
Sent from my GT-I9100 using xda premium
burning_afd said:
updated to 4.0.4 but nothing changed.
ok here are the problems:
- The power button options are not showing up. if i hold the power button it just closes the phone directly.
- The screen lock doesnt work. Wont lock the screen with any option there.
- The sim lock doesnt work. If i put the sim lock on (put a lock on the sim) the phone starts normally but wont let me call or text. So i have to disable the lock on the sim to make it work normal.
Now these are the problems i have seen so far. When i got the phone it was GB and there was absolutely no prob until updating to ICS. So whats the suggestion, should i give a try on custom firmware ICS or go back to official GB? if you say custom firmware then which one?
Click to expand...
Click to collapse
1. If your phone is not rooted, root.
2. Create file /efs/imei/keystr, containing the word ON.
3. Make sure the file has rw-r--r--, or 644 permissions.
4. ...
5. Profit!
ctomgee said:
1. If your phone is not rooted, root.
2. Create file /efs/imei/keystr, containing the word ON.
3. Make sure the file has rw-r--r--, or 644 permissions.
4. ...
5. Profit!
Click to expand...
Click to collapse
ok thank you very much bro. that did it
i first rooted the phone from here: http://forum.xda-developers.com/showthread.php?t=1679778 with the option 2.
then used this little guide:
- Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
Go to home, force close your terminal app, shut your screen off, and when your turn it back on your lock screen should? be there.
Obviously you must be rooted the "su" command
And for Signal Problem Simply do not put any pin on your sim ,,,
I just installed Galaxy Task 14 slim coming from CM10 Upgraded cwm to newest through Odin Flashed made a backup and installed Worked great for a few minutes Tried front and back cam out then out of nowhere the screen turned scribbled I cant see nothing not even power off or reboot buttons what do I do?
Galaxy Tab 10.1 p7510wifi
JavaKid said:
I just installed Galaxy Task 14 slim coming from CM10 Upgraded cwm to newest through Odin Flashed made a backup and installed Worked great for a few minutes Tried front and back cam out then out of nowhere the screen turned scribbled I cant see nothing not even power off or reboot buttons what do I do?
Galaxy Tab 10.1 p7510wifi
Click to expand...
Click to collapse
I rebooted and it seems to come up right will someone with more experience please elaborate on what may have been the cause so I can fix whatever happened.
EDIT: Keeps coming back eventualls flashing another kernal now. Any info would be great thanks.
Also tried installing CM10.1 newest out.... Same issue distorts screen with horizontal lines then just kept doing it....Had to restore twice from recovery only one rom works what up? Am I alone in this?
The only stable kernal is 2.6.36.4 but when I flash it doesnt take for newer builds...... Does anyone have the answer? If I dont put the tablet to sleep it works fine once awaken from sleep its scrambled again???
FIXXXED!!!!!!!!!!!
JavaKid said:
I rebooted and it seems to come up right will someone with more experience please elaborate on what may have been the cause so I can fix whatever happened.
EDIT: Keeps coming back eventualls flashing another kernal now. Any info would be great thanks.
Also tried installing CM10.1 newest out.... Same issue distorts screen with horizontal lines then just kept doing it....Had to restore twice from recovery only one rom works what up? Am I alone in this?
The only stable kernal is 2.6.36.4 but when I flash it doesnt take for newer builds...... Does anyone have the answer? If I dont put the tablet to sleep it works fine once awaken from sleep its scrambled again???
Click to expand...
Click to collapse
Did not realize this help section was so dead...... Anyways a few hourse later I discovered this thread pertaining to the issue... Should have a sticky or something its rather important so you don't think your tab is junk. For anyone having this issue go to http://forum.xda-developers.com/showthread.php?t=1975407
Cleared the issue right up I am on the latest cm build and running great no more sleep scribble display crap.
Hello guys, firstly, I wanna say this issue I encountered is pretty anodyne, but anyway, I wanna solve it cause it's annoying.
So, I was using a S2 with CM10.2 installed and I wanted to replace it with the [ZERO]BUG ROM v5.0+Premium Suite to, basically, improve its battery life and other minor issues. So I executed an "unclean" install, cause I directly entered CWM and installed the ROM, without installing the stock 4.1.2 via Odin and then again root the phone and install CWM. So it went ok apparently, but everytime I try to lock the screen, it surely locks, but no lock screen appears when I turn it on. Plus, the phone shuts down when I keep the power button pressed 2 seconds, and no power menu appears on the screen before that.
I thought it was a bad "coordination" between the two ROMs, because of the unclean installation, so I installed stock 4.1.2 via Odin to keep in that ROM cause it's pretty good, but still no lock screen or power menu.
So I wanna know how to solve this, cause I'd like to sell the phone and it has to be perfect for that. I don't care to stay in stock, go for CM or another custom CM/stock-based, I just wanna solve it.
So thanks in advance to all of you who are trying to help me.
Hello, Hopefully some one is still checking this forum that can help me. I got a DNA with CM 11 on it, while I wait for the first Verizon snapdragon 820 with SD card, as my LG G2 started failing miserably (dead spots in screen and no loger connects to Wi-Fi or Bluetooth)
I wanted to clear it out and to go to a 5.x.x ROM. so I made my backups and went to the 5.1 google play edition ROM and fastboot-ed the latest firmware as instructed in the post. at first the capacitive navigation buttons seem to work, but in about half a day they become flaky and sometimes work and sometimes don't. whatever app I am in at the time seems to work fine, just can't exit without the nav keys unless I reboot or force another app to open from the lock screen. I have also tried a 5.0.1 and and now on a stock ODEX debloat 4.4.2 all with the exact same issue. I use TWRP and do a factory reset in TWRP before each flash. How is this issue following the flashing of each ROM? Any one have any ideas for me to try?
Thank you