Touchscreen software issues - Galaxy S III Q&A, Help & Troubleshooting

Hi all.
i am a n00b so please forgive me if i am doing this incorrectly..
i flashed CWM recovery touch to my GT-I9300 and the touchscreen stopped working.
i have read numerous posts about how if the touchscreen stops working, the digitizer is broken and needs replacing.. i am 90 percent sure that the software is somehow out of whack..
so, my question is...
Is it possible to reflash the drivers or software that the digitizer/touchscreen needs to work with ODIN or another way? If so, how would i do it?
i am currently using a USB adapter and a USB mouse to navigate my phone.

What phone what firmware what cwm details are missing

JJEgan said:
What phone what firmware what cwm details are missing
Click to expand...
Click to collapse
Recently flashed note2 kernel and the digitizer chip was burned (broken).
If you do a reinstall, stock or whatever and still find the touchscreen isn't working then you probably did the same.

JJEgan said:
What phone what firmware what cwm details are missing
Click to expand...
Click to collapse
galaxy s3.
not sure on the firmware as i was flashing all kinds of stock roms as i was trying to fix another issue (EFS / IMEI wiped).
and i cant remember the version of CWM.

If the digitser doesn't work in recovery AND android, its hardware not software because recovery and Android do not share "software" and by that I mean kernel and drivers.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

bender_007 said:
Recently flashed note2 kernel and the digitizer chip was burned (broken).
If you do a reinstall, stock or whatever and still find the touchscreen isn't working then you probably did the same.
Click to expand...
Click to collapse
but you wouldnt think that flashing CWMR would "Burn" the digitizer. which makes me think its a software issue

rootSU said:
If the digitser doesn't work in recovery AND android, its hardware not software because recovery and Android do not share "software" and by that I mean kernel and drivers.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
so if i wanted to check to see if it is a software issue, where would i get drivers from?

If you flashed say, the note 2 cwm like many people do by mistake then its definitely hardware.
If you have cwm touch / philz touch for the s3 and touch doesn't work and also touch doesn't work in android then its also 100% hardware.
Any drivers recovery uses are not used in the android ROM itself. You have 2 sets of drivers. If you flashed cwm and touchscreen was broken by driver / software issue, touchscreen will still work in android.
Simple and easy Test to do
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Are the "menu" and "back" buttons part of the touchscreen? Because they still work

BallaratBloke81 said:
Are the "menu" and "back" buttons part of the touchscreen?
Click to expand...
Click to collapse
Nope. Completely separate and not indicative of anything.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Related

S3 Won't start, no-led or start-up screen

Hello,
After rooting my phone I wanted to go to the recovery menu to delete all data on the phone.
So I shut down the phone and used the buttons to go the the recovery menu, when the screen appears it was there for 0,5 seconds and then I saw some text (Don't know what it was). I was not able to do anything so I decided to pull out the battery.
After waiting a while I wanted to turn the phone back on but it didn't do anything.
No led, no screen nothing, no communication with the computer.
Battery was 100% loaded.
How can this happend?
Is there something that I can do?
Thankss
No details posted crystal ball cannot see what model phone what firmware or what root method .Do you know ???
Usual is user error failing to read the instructions .
jje
JJEgan said:
No details posted crystal ball cannot see what model phone what firmware or what root method .Do you know ???
Usual is user error failing to read the instructions .
jje
Click to expand...
Click to collapse
Hi,
I used gs3.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-and-flash-stock-roms-using-odin-for-windows-0142713/
Model I9300.
Thats all I know..
Put your battery in. Plug the usb cable in. If no led comes on at this stage, you need a new motherboard
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Nicasius said:
Hi,
I used gs3.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-and-flash-stock-roms-using-odin-for-windows-0142713/
Model I9300.
Thats all I know..
Click to expand...
Click to collapse
Nothing to do with this forum why don't you ask the forum that gave you this method that has bricked your phone .
Suggest you flash with Philz recovery from Android Original Development .
That fails then flash your stock rom via Odin and try again .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
rootSU said:
Put your battery in. Plug the usb cable in. If no led comes on at this stage, you need a new motherboard
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Nope,
No Led, nothing.
JJEgan said:
Nothing to do with this forum why don't you ask the forum that gave you this method that has bricked your phone .
Suggest you flash with Philz recovery from Android Original Development .
That fails then flash your stock rom via Odin and try again .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Click to expand...
Click to collapse
Thanks for the information, i'm going to read the threads.
They're not really going to help you now. Your phone exhibits the symptoms of full sds.
Send it for repair if you still have warranty.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
They're not really going to help you now. Your phone exhibits the symptoms of full sds.
Send it for repair if you still have warranty.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Yeah I know but in the future.
Is it by my fault that the phone is broken ?
That I do something wrong or is the software corrupted?
Nicasius said:
Yeah I know but in the future.
Is it by my fault that the phone is broken ?
That I do something wrong or is the software corrupted?
Click to expand...
Click to collapse
Ultimately its samsungs fault for having faulty firmware on the emmc, but it certainly could have been partially your fault for taking a patched device and flashing it with an unpatched component. Without knowing exactly what you flashed/ recovery version etc its hard to say
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Nicasius said:
Yeah I know but in the future.
Is it by my fault that the phone is broken ?
That I do something wrong or is the software corrupted?
Click to expand...
Click to collapse
When you flash stuff from a forum that has just copied bits and pieces its hard to know what went wrong .
However best response is to tell Samsung that it failed to boot one morning and you have read on the web about the emmc problem .
I have my phone back so now i'm going to try to root it again.
It's kernelversion 3.0.31 - 1314436
I'm going to use the XDA manual and rom: http://forum.xda-developers.com/showthread.php?t=2407407
Is this a good kernelversion? Not that my phone will fail again.
Thanks!
// EDIT:
Succesfully rooted / flashed my Phone .

Just wanting to be sure about binary flash counter and warranty

Hello, I know that this question might be stupid but if I have custom binary flash counter more than zero (0), and rooted one as well may warranty service could refuse to fix my phone because of that I have custom binary flasher more than zero? Did somebody try sending rooted phone with flash binary counter more than zero to warranty without having problems?
They usually reject. That's why triangle away exists.
If you want warranty, it must be reset and its your responsibility to do this before the phone fails and cannot boot fully
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
They usually reject. That's why triangle away exists.
If you want warranty, it must be reset and its your responsibility to do this before the phone fails and cannot boot fully
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Thank you for the answer, and they can see it even if it's hardware failure and can't boot up into download mode too?
Nope. If its Completely dead / download doesn't boot, they wont reject
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
If i'm not mistaken they also have a flashable zip package that you can flash through recovery to reset download counter. If your phone isn't fully bricked and you can access your recovery do this. If you aren't able to do this for some reasin ir cannot find the package, try to brick the cell on your own (delete stuff....efs and system. Just delete...)
Sent from my GT-I9300 using xda app-developers app
killbubble said:
If i'm not mistaken they also have a flashable zip package that you can flash through recovery to reset download counter
Click to expand...
Click to collapse
I've never seen or heard of that...
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
killbubble said:
If i'm not mistaken they also have a flashable zip package that you can flash through recovery to reset download counter. If your phone isn't fully bricked and you can access your recovery do this. If you aren't able to do this for some reasin ir cannot find the package, try to brick the cell on your own (delete stuff....efs and system. Just delete...)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Really? What zip package do you mean? Could you give me a link to that?
And what's the point to brick my phone on my own? ;D
rootSU said:
I've never seen or heard of that...
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
I can't be sure about it now and i might be mistaken, but tomorrow i will surely search it for you. To op: the point to bricking your own phone is so that samsung cannot recognize or read its internal software and therefore check if it has been compromised (rooted or flashed roms...) and will have to fix it.
It works for many people...
i did this a couple of years ago on my dad's jailbroken iphone 4: he got a new one even
Sent from my GT-I9300 using xda app-developers app

Reset flash counter to 0 when status is normal

OK something is wrong with my Samsung Galaxy S III SIM and it's not the SIM itself. So I have to return the phone.
I unrooted the device and the status is showing: NORMAL. But... flash counter says: 4 and I'm afraid they won't accept it like this.
Question:
Do I have to root the device again to be able to use Triangle Away OR
is there any way I can reset the flash counter to 0 when unrooted as it now?
Thanks a bunch!
Alex
Yes. You need to re-root.
Read the full fix thread in general > sticky roll-up thread to see how you should reset with triangle away
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Xaninha said:
OK something is wrong with my Samsung Galaxy S III SIM and it's not the SIM itself. So I have to return the phone.
I unrooted the device and the status is showing: NORMAL. But... flash counter says: 4 and I'm afraid they won't accept it like this.
Question:
Do I have to root the device again to be able to use Triangle Away OR
is there any way I can reset the flash counter to 0 when unrooted as it now?
Thanks a bunch!
Alex
Click to expand...
Click to collapse
Yup u do have to root your phone and remember it only works on the stock kernel so dont try flashing one
Rooted again what now?
Hmm... I have just rooted the phone again following these instructions.
reviews.cnet.co.uk/mobile-phones/how-to-root-your-samsung-galaxy-s3-50008588/
Phone is now rooted and went back to Status: Modified.
Now... the Triangle Aways, right?
I may brick my phone, it says... GLUP!!!
Alex
Its just a disclaimer...
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
SUCCESS!
SUCCESS! NOW BACK TO UNROOT PROCESS...!
Flash Counter doesn't even show up!
May I unroot with Super SU (full unroot option) or should I go back to Odin and install Samsung Rom?
Thanks!
rootSU said:
Its just a disclaimer...
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Depends if you have stock recovery or not... I'd reflash with Odin
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Didn't work... =(
I reflashed it but to no avail. Status is Modified. But no Super Su installed which I find weird.
Any ideas?
Thanks!
QUOTE=rootSU;46023063]Depends if you have stock recovery or not... I'd reflash with Odin
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit[/QUOTE]
You have to factory reset after the flash
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Eureka!
It worked! It worked!
You're very efficient, smart and generous.
Thank you very much!
Alex
rootSU said:
You have to factory reset after the flash
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Warranty went poof
Well... after my tiny adventure of turning my phone into a virgin and immaculate device... I went to Vodafone for a repair. They have samsung tech people there. And after two days, they said they would repair the phone for 264 USD because the garanty was voided. Then they handed me a print-screen with the IMEI in the physical device and another with a window saying IMEI: null/null.
I didn't make a fuss about it and left. Later I typed *#06# and to my surprise I saw my complete IMEI. I rooted the phone again.
I have no idea where they saw the null/null but I have the feeling that due to flash roms or some software installation I screwed the original IMEI.
This guy here www.sammobile.com/forum/showthread.php?t=13140 seems to have solved the issue... problem is I have no EFS backup, and in the EFS folder I have no " .nv_data" file. Only ".nv_data.bak". I copied this file to ",nv_data." and rebooted but to no avail.
So to sum it up... I no longer suspect that it's physical problem related to the sim socket but it's a firmware issue due to software installation, which one I don't have a clue. I only run CF-Root to root and I only applied the ROMs presented in samMobile.
I must have the EFS corrupted in some way. Gah.
Thank you for your atention.

[Q] bootloader and mobile odin

I installed the official 4.3 firmware via mobile odin pro. afaik mobile odin does not flash or update the bootloader. everything seems fine . my question is, is there any reason to install the new bootloader? using pc odin perhaps from the leak files? im thinking as long as the bootloader i have works it is best to leave it alone. also is there a utility that can identify which bootloader i have?
Afaik the bootloader is irrelevant to the rom or recovery, some people still have the ICS bootloader to avoid the flash counter increasing (even with the danger of SDS it brings).
I read that the newest 4.3 has a 'warranty bit' register, but if that is any different to the normal JB bootloader I don't know.
For the moment I'd wait, it won't do any harm.
I've got ics bootloader still
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
I've got ics bootloader still
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
I'm also using the old ICS bootloader here @rootSU just got a question... can it still be used on the 4.3 official firmware?
I've not used official firmware but I can't think of a reason why not
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

galaxy s3 touch stopped working after using wrong root file

using file-philz_touch_5.15.0 n7100.tar.md5(Galaxy Note 2) installed via Odin and my S3 stopped working the touch screen
sorry if the topic is in the wrong place, just please do not remove without at least help me(sorry for the bad english I'm using google translator)
alifizee said:
using file-philz_touch_5.15.0 n7100.tar.md5(Galaxy Note 2) installed via Odin and my S3 stopped working the touch screen
sorry if the topic is in the wrong place, just please do not remove without at least help me(sorry for the bad english I'm using google translator)
Click to expand...
Click to collapse
Note2 kernel will destroy the touch screen of an SG3, sorry but you need a repair to fit a new screen.
boomboomer said:
Note2 kernel will destroy the touch screen of an SG3, sorry but you need a repair to fit a new screen.
Click to expand...
Click to collapse
sorry to hear..been there, done that.
I hope you've got warranty.
Technically its not covered by warranty
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Technically its not covered by warranty
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Technically not. Mine was , just restored efs manually, put back original software etc.
Got whole new screen
the only solution will be to replace the touch?
alifizee said:
the only solution will be to replace the touch?
Click to expand...
Click to collapse
As said just hand it to service say screen stopped and hope they accept as warranty if not you pay .
JJEgan said:
As said just hand it to service say screen stopped and hope they accept as warranty if not you pay .
Click to expand...
Click to collapse
First get an usb otg cable, connect the mouse to it, put everything back to stock, so everything in download mode says : samsung official and counter = 0.
alifizee said:
using file-philz_touch_5.15.0 n7100.tar.md5(Galaxy Note 2) installed via Odin and my S3 stopped working the touch screen
sorry if the topic is in the wrong place, just please do not remove without at least help me(sorry for the bad english I'm using google translator)
Click to expand...
Click to collapse
I may be wrong, but if you made a nandroid backup of your device, you might be able to restore it using that. Ive never messed up my device before so, like i said, i may be wrong.
tomosh22 said:
I may be wrong
Click to expand...
Click to collapse
Yes. Nandroid backups cannot restore fried hardware.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
s3 touch stopped working
alifizee said:
using file-philz_touch_5.15.0 n7100.tar.md5(Galaxy Note 2) installed via Odin and my S3 stopped working the touch screen
sorry if the topic is in the wrong place, just please do not remove without at least help me(sorry for the bad english I'm using google translator)
Click to expand...
Click to collapse
The same problem happened to my galxy s3 as well... some body help please...
Xaver Tooth said:
The same problem happened to my galxy s3 as well... some body help please...
Click to expand...
Click to collapse
If you read the whole thread instead of just quoting the first one you will get your answer. Honestly its only about 8 post and will take you all of 5 minutes.
Darke5tShad0w said:
If you read the whole thread instead of just quoting the first one you will get your answer. Honestly its only about 8 post and will take you all of 5 minutes.
Click to expand...
Click to collapse
Thank u but i did read the post many times. but though some one might as well know some thing abt the problem.
i've read more then needed. since it was not a hardware damage, i wwas expecting a genuine response rather then just a mock over the post i made.
The response was genuine, giving you the correct answer -you won't find a different one. If you flashed a Note kernel then your hardware is damaged and needs a new screen assembly.
100% solution
after root i9300 with wrong cft auto root.. touch doest work.. and i replace this chipset.. and my problem solve.. find this chipset from broken lcd.. good luck

Categories

Resources