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 .
Related
hi guys
I had CM10 and all worked fine.
I wanted to change to a different ROM and wiped EVERYTHING and installed MIUI ROM. I didnt liked it at all and switched to Pardus HD RoM
™ FINAL 4.1.2 ReMastered (12.09.13) - I noticed it did something with my modem during installation.
I didnt liked it too - and installed Omega v48.1 (4.2.2) which I think I do like.
BUT....
I noticed I dont have signal.
I do have WIFI. I checked my IMEI and it is OK but serial number is 000000000
I tried ARIZA patch but it didnt worked.
I tried to install a different modem - no help.
i tried to Install stock rom - I cant. installation fail.
going back to CM10 is ok but no signal, IMEI is 0049 and serial is unknown.
Please help me gain a signal again.
PLEASE I BEG YOU, read the sticky threads. Read general > sticky roll-up > imei /efs.
This has all been asked before. This has all been answered before. Same post 15 times a day. Its getting ridiculous
-----------------------
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
I did read a lot but couldnt find a solution. trust me im with this at least 10 hours.
can you help me please? link to the thread?
if i had a solution i wouldnt post - right?
btw - i dont have efs saved.
rootSU said:
PLEASE I BEG YOU, read the sticky threads. Read general > sticky roll-up > imei /efs.
This has all been asked before. This has all been answered before. Same post 15 times a day. Its getting ridiculous
-----------------------
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
Well the answer is in there. Clue - read the ariza section at the end of post 1... after reading the rest of post 1
Answer is there. Cannot spoon feed you what is already there. Just read it please!!!
-----------------------
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
can you link me to the thread? there is so many posts i dont know what to look for and what to do.
rootSU said:
Well the answer is in there. Clue - read the ariza section at the end of post 1... after reading the rest of post 1
Answer is there. Cannot spoon feed you what is already there. Just read it please!!!
-----------------------
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
Its in general > sticky roll-up thread. Link is in my signature. Its a thread stuck at the top of the general section
-----------------------
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
ok
i read it - but nothing new....
i tried his patch - NOT WORKING for me...
marik9581 said:
can you link me to the thread? there is so many posts i dont know what to look for and what to do.
Click to expand...
Click to collapse
Are you even on the right baseband? Mg4? Did you try the pre-patched baseband by zuluman linked in the ariza thread? If so, send your device for repair. All covered in the thread!
-----------------------
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
baseband is: I9300UBEMH1
im looking now for the zuluman patch but cant find it.
rootSU said:
Are you even on the right baseband? Mg4? Did you try the pre-patched baseband by zuluman linked in the ariza thread? If so, send your device for repair. All covered in the thread!
-----------------------
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
Try using the "search this thread" function on the ariza thread. I shouldn't have to tell you this
-----------------------
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
ok forget this
i cant find anything... im tired of this ******** and i dont know why this happened.
I will get it to fix in the lab tomorrow and that all.
my phone worked great before the roms - but i will ask them to install the rom i want and make sure all working ok and thats it.
thanks anyway for trying (or not) to help...
marik9581 said:
baseband is: I9300UBEMH1
im looking now for the zuluman patch but cant find it.
Click to expand...
Click to collapse
Its all documented. If you're not willing to put the effort to find the fix, even when I told you exactly where it was, then no one is going to spoon feed you. Want to be spoon fed? Join an android help forum. This is a developers forum and everyone here who wants help is expected to want to learn and be able to follow instructions. If this isn't you, you're in the wrong forum.
The problem with sone people is they expect "flash this" as an answer and are in too much of a rush to read. They skim things or don't bother reading properly.
Fact is, if you'd have read my thread before flashing roms, your phone would still work. If you had followed my thread now, you would understand and if you'd followed my directions properly, you'd have a working phone. But this is too much for the impatient.
Basically, don't flash your phone if you can't be bothered to understand why it broke or how to fix it
-----------------------
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
and last thing
i know you tired from answering the same thing over and over again.
but if so many people asking it again and again - it means something.
maybe the info is confusing, maybe it is not clear enough
and maybe you can just take a deep breath and just help instead of behaving like this.
im a manager of a forum too... i know what you mean... but when i see a person really in a trouble and confused - i help him.
and yes.... i know the search in this thread... try you to search zuluman in this thread and find an answer.
rootSU said:
Try using the "search this thread" function on the ariza thread. I shouldn't have to tell you this
-----------------------
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
this is the only forum i know and trust.
million of times before this place helped me and i found my answers alone with no need to ask and open threads.
dont feed me... im all ok.
thanks
rootSU said:
Its all documented. If you're not willing to put the effort to find the fix, even when I told you exactly where it was, then no one is going to spoon feed you. Want to be spoon fed? Join an android help forum. This is a developers forum and everyone here who wants help is expected to want to learn and be able to follow instructions. If this isn't you, you're in the wrong forum.
-----------------------
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
Ariza thread > search this thread > by author "zuluman" - really difficult to do? No
-----------------------
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
---------- Post added at 05:13 PM ---------- Previous post was at 05:09 PM ----------
marik9581 said:
try you to search zuluman in this thread and find an answer.
Click to expand...
Click to collapse
I just asked my cat to do this and he found the answer straight away
http://forum.xda-developers.com/showthread.php?p=45038238#post45038238
ok
i found this: patched_modem_XXEMA2.zip
what my baseband tell you? i9300ubemh1
how should i install that file? ( patched_modem_XXEMA2.zip) goto recovery and install it from there with no wipe and no nothing?
just install it from there and thats it?
rootSU said:
Ariza thread > search this thread > by author "zuluman" - really difficult to do? No
-----------------------
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
---------- Post added at 05:13 PM ---------- Previous post was at 05:09 PM ----------
I just asked my cat to do this and he found the answer straight away
http://forum.xda-developers.com/showthread.php?p=45038238#post45038238
Click to expand...
Click to collapse
Yep cwm recovery flash. You cant have MA anything thogh. The link I gave is MG4. You cannot go older than MG2....
There is also another post in that thread where someone else claims to have patched an MH1 baseband. Its later than the post I gave you the link to.... I forget his name. Only a few pages after
ok... thanks...
its good i saw your link to the MG...
so i installed it in recovery mode. after installing it - rebooted... and now -
imei: unknown
serial number is long number - i guess it is ok.
no signal - before that i had a signal bar but no registered to a carrier.
now i have a circle and when going to mobile networks - i get message: insert sim card. (my sim is inserted)
rootSU said:
Yep cwm recovery flash. You cant have MA anything thogh. The link I gave is MG4. You cannot go older than MG2....
There is also another post in that thread where someone else claims to have patched an MH1 baseband. Its later than the post I gave you the link to.... I forget his name. Only a few pages after
Click to expand...
Click to collapse
Do you have any EFS backup (from preferably before flashing Pardus)? or at least before flashing Ariza patch initially?
If not, best bet is to flash latest stock official MG4 ROM (or newer) completely unroot (resetting flash counter etc) and take to a mobile repair shop. Any will do. They will be able to re-write your EFS partition for v ery little money (£20 UK price) and then you can start again and have no serial / IMEI issues.
I think in your case this is the easiest thing to do.
Although, try maybe flash standard MG4 modem from my imei therad (without patch) to see if serial stays and IMEI comes back. Or the MH1 linked later in ariza thread.
i have a friend that have a cell lab.
i will go to him tomorrow and fix this.
i dont want patches and stuff... he rooted my phone before and he will fix it for me...
thanks anyway...
rootSU said:
Do you have any EFS backup (from preferably before flashing Pardus)? or at least before flashing Ariza patch initially?
If not, best bet is to flash latest stock official MG4 ROM (or newer) completely unroot (resetting flash counter etc) and take to a mobile repair shop. Any will do. They will be able to re-write your EFS partition for v ery little money (£20 UK price) and then you can start again and have no serial / IMEI issues.
I think in your case this is the easiest thing to do.
Although, try maybe flash standard MG4 modem from my imei therad (without patch) to see if serial stays and IMEI comes back. Or the MH1 linked later in ariza thread.
Click to expand...
Click to collapse
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.
Hy first sry about bad eng.
Yesturday my phone died with no reason. Cannot boot. Tryed everything. From old roms,moded/stock(like 15), pit files,bootlanders etc...
Every time no pit partition, i searched on internet,and tryed changing computer,changing usb hubs,and everything. Can some 1 pls help me ?
sam galaxy s3 i9300 16 gb
Unfortunately .pit was your last resort. If that failed, you have a NAND issue (internal memory) which usually means a motherboard replacement is required
-----------------------
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:
Unfortunately .pit was your last resort. If that failed, you have a NAND issue (internal memory) which usually means a motherboard replacement is required
-----------------------
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
Im sry for comming up like monkey,but i realy dont know what should i do, i have contract for that cell for another 12 mounths i need to pay with no meather of what. Should i take it to warnity? I understand some things about roms and s**t , and i was changing roms before. I realy tryed everything,only dont know how and can i install new pit partition in cell?
Yep, if you have warranty - use it. Definitely
-----------------------
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:
Yep, if you have warranty - use it. Definitely
-----------------------
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
atleast i know what i should to do now. ty anyway :good:
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
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