Phone was working perfect until this evening .
I flashed "Googy-Max2 Kernel 2.0.8 (Linux 3.0.101 / Linaro GCC 4.8.2)" kernel on "temasek's UNOFFICIAL Build - V21"
On reboot the touchscreen went unresponsive and yet the hardware keys and the softkeys were working! :crying:
I flashed various other kernels and roms as well as tried a hard factory reset installing the official firmware for India (4.1.2), yet the problem is there unresolved. :crying:
Any help would be highly grateful. :angel:
Touch screen problems after a flash are usually due to flashing the wrong file, probably a Note file, blowing the controller. You'll need a new digitizer.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Touch screen problems after a flash are usually due to flashing the wrong file, probably a Note file, blowing the controller. You'll need a new digitizer.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
So it could be wrong kernel or ROM ?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Either, as the rom would also contain a kernel.
Sent from my GT-I9300 using Tapatalk
Same thing happened to me, no way I flashed a Note file, used the 1.8 Googly Max kernel on PA 3.99RC2, trying lots of things but nothings working. I really hope the digitizer isn't gone, I replaced the whole screen unit just on Monday.
boomboomer said:
Either, as the rom would also contain a kernel.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
If there isn't something completely wrong with either the rom or the kernel, it's impossible to flash a note kernel to a s3, because of different partitions used.
The only possibility would be an also wrong updater script inside the zip, which flashes the wrong kernel to the "right" partition (like it happened to psndna once).
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Did you flash 4.1.2stock rom maybe ur touch screen are broken I saw this issue some s3s to and phones touch screens was broken
GT-I9300 cihazımdan gönderildi
boomboomer said:
Either, as the rom would also contain a kernel.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
S1N1ST3R said:
Same thing happened to me, no way I flashed a Note file, used the 1.8 Googly Max kernel on PA 3.99RC2, trying lots of things but nothings working. I really hope the digitizer isn't gone, I replaced the whole screen unit just on Monday.
Click to expand...
Click to collapse
Abo3mood said:
So it could be wrong kernel or ROM ?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
boomboomer said:
Touch screen problems after a flash are usually due to flashing the wrong file, probably a Note file, blowing the controller. You'll need a new digitizer.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I didn't flash a wrong kernel. i had my "temasek's UNOFFICIAL Build - V21" Rom installed on my phone with "201113-1224-cm11-i9300-r3p2-linux30101-WOLFSON-temasek" as the current flashed kernel. Due to experiencing lag I decided to try a new kernel which was "Googy-Max2 Kernel 2.0.8 (Linux 3.0.101 / Linaro GCC 4.8.2)".
I wiped the dalvik cache after flashing the kernel, and rebooted my phone. the android updated apps and started with an unresponsive screen.
I just hop that the digitiser isn't screwed up.
P.S:- I've tried the following things.
1. flashing stock rom via odin after a mega/factory wipe technique mentioned in http://forum.xda-developers.com/showthread.php?t=1832326
2. flashing various different roms and kernels with apt procedures.
3. re-rooting the phone and flashing "CWM touch 6.0.4.5" via odin and repeating the process of flashing roms (both stock and custom).
None of the techniques have given me a positive response.
mskomek said:
Did you flash 4.1.2stock rom maybe ur touch screen are broken I saw this issue some s3s to and phones touch screens was broken
GT-I9300 cihazımdan gönderildi
Click to expand...
Click to collapse
Yes i did flash 4.1.2 stock rom after a complete wipe.
I had broken my screen by dropping it quite a while ago which i very recently (2 days ago) got replaced from Samsung carecenter.
Don't know what went wrong.
haseeb2009 said:
Yes i did flash 4.1.2 stock rom after a complete wipe.
I had broken my screen by dropping it quite a while ago which i very recently (2 days ago) got replaced from Samsung carecenter.
Don't know what went wrong.
Click to expand...
Click to collapse
if touchscreen doesnt response in recovery there is bad news for you bro your touchscreen is broken again
i dont think so its a software problem becase nothink work in recovery right!?
DerTeufel1980 said:
If there isn't something completely wrong with either the rom or the kernel, it's impossible to flash a note kernel to a s3, because of different partitions used.
The only possibility would be an also wrong updater script inside the zip, which flashes the wrong kernel to the "right" partition (like it happened to psndna once).
Gesendet von meinem SAMSUNG-SGH-I317 mit Tapatalk 2
Click to expand...
Click to collapse
And I'm sure that he never will make that mistake again:silly:
But sadly a few ppl where affected by his unfortunate mistake..
But humans are no way near perfect and sh.. happens
Related
I have been trying to flash NX-Kernel_v1.1.0 to my phone which is running Rootbox-JB-i9300-v3.9.1.
I have noticed that the file I am trying to flash is not a .tar, which is what I am use to, but a .zip.
When i use TWRP to attempt to flash it boots into download mode and does nothing.
I have also tried using odin and mobile odin but i think because its a .zip odin cannot even see it.
The thread is linked below. I have searched it and people seem to be saying that it is possible to flash with a recovery and odin/mobile odin, all of these i have tried.
Can someone please tell me what i am doing wrong!?!?
http://forum.xda-developers.com/showthread.php?t=2192893
just flash it from recovery like a rom
is the rom based on CM10.1?
Tried
Glebun said:
just flash it from recovery like a rom
is the rom based on CM10.1?
Click to expand...
Click to collapse
I have tried flashing from tw recovery it does not boot into system from there.
The rom is a AOKP base.
guspop said:
I have tried flashing from tw recovery it does not boot into system from there.
The rom is a AOKP base.
Click to expand...
Click to collapse
Why would a kernel made for galaxy note or note 2 work on a galaxy s3?
There are sure to be differences which will make it not boot.
Sent from my GT-I9300 using xda premium
oops, didn't see that. Of course it won't boot, you're lucky if you didn't kill it
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
ficti0n851 said:
Why would a kernel made for galaxy note or note 2 work on a galaxy s3?
There are sure to be differences which will make it not boot.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
b-eock said:
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
Click to expand...
Click to collapse
Wow thank you I cannot believe I didn't realise it was for the note.
b-eock said:
First off, kernels cannot kill phones. Only corrupted or mismatched or blank boot loaders can.
Click to expand...
Click to collapse
Hate to tell you it can. I bricked an S3 by accidently flashing an S2 kernel to it which bricked the device to the point that a jig would not even revive it.
That makes no sense if you think of the booting process... I mean crazy things happen. But a kernel should never fully brick a device...
guspop said:
I have been trying to flash NX-Kernel_v1.1.0 to my phone which is running Rootbox-JB-i9300-v3.9.1.
I have noticed that the file I am trying to flash is not a .tar, which is what I am use to, but a .zip.
When i use TWRP to attempt to flash it boots into download mode and does nothing.
I have also tried using odin and mobile odin but i think because its a .zip odin cannot even see it.
The thread is linked below. I have searched it and people seem to be saying that it is possible to flash with a recovery and odin/mobile odin, all of these i have tried.
Can someone please tell me what i am doing wrong!?!?
http://forum.xda-developers.com/showthread.php?t=2192893
Click to expand...
Click to collapse
Flash it w CWM. Should work
Sent from my SPH-L710 using xda app-developers app
b-eock said:
That makes no sense if you think of the booting process... I mean crazy things happen. But a kernel should never fully brick a device...
Click to expand...
Click to collapse
It does if the kernel is not for the proper chip set. Like a kernel for a qualcom chip flashed on an eyxnos chip.
jorv976 said:
Flash it w CWM. Should work
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
the issue has already been found. The kernel is for a different device.
It should only result in a soft brick... Bootloaders are the first to come (primary then secondary. Secondary passing the booting process off to the kernel. Recovery is in the kernel while DL mode is in the boot loaders.) Oh well. I make sure I don't do stuff like that. I'm really OCD and paranoid about stuff being just right.
b-eock said:
It should only result in a soft brick... Bootloaders are the first to come (primary then secondary. Secondary passing the booting process off to the kernel. Recovery is in the kernel while DL mode is in the boot loaders.) Oh well. I make sure I don't do stuff like that. I'm really OCD and paranoid about stuff being just right.
Click to expand...
Click to collapse
\Yeah thats what I thought as well. I was just rushing far more then I normally do and downloaded the same rom for both the S2 for my brother and my S3 and flashed the wrong one to mine. Boy was I not happy. Spent 3 days with some of the most talented developers here and we all agreed that jtag was the only hope.
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes
i tried wanam XXEMD3 and stock deoxded XXEMD3 with Googy-Max 1.4.6 kernel
i don't think its problem of kernel because i used it on XXEMD2 which is all fine.
today i flashed wanam XXEMD3 and when i running setup and connecting WIFI it keeps reports "Authentication error" or something , i think that's translation.
i thought it could be problem of ROM , and then tried stock deoxded XXEMD3, same , i figure maybe WIFI password i typed wrong ? although it's highly unlikely
and then i restored back to XXEMD2 with recovery , WI-FI works all fine ...
any idea ?
You should look for a wifi fix for your kernel or your ROM. This should to it. If there isn't any you should go to support of kernel or ROM. They should be able to fix this if no wifi Dix patch exists
Gesendet via Tapatalk von meinem S3 mit Imperium ROM
qtwrk said:
i tried wanam XXEMD3 and stock deoxded XXEMD3 with Googy-Max 1.4.6 kernel
i don't think its problem of kernel because i used it on XXEMD2 which is all fine.
today i flashed wanam XXEMD3 and when i running setup and connecting WIFI it keeps reports "Authentication error" or something , i think that's translation.
i thought it could be problem of ROM , and then tried stock deoxded XXEMD3, same , i figure maybe WIFI password i typed wrong ? although it's highly unlikely
and then i restored back to XXEMD2 with recovery , WI-FI works all fine ...
any idea ?
Click to expand...
Click to collapse
Please try flashing ROM with full wipe and supplied kernel.
rootSU said:
Please try flashing ROM with full wipe and supplied kernel.
Click to expand...
Click to collapse
It's OK now
I don't know what and where the problem was, but I figure reflash ROM several times solves problem, it's kinda pain in ass as sometimes I have to reflash it dozens times to have Wi-Fi work...
Sent from my GT-I9300 using xda premium
qtwrk said:
It's OK now
I don't know what and where the problem was, but I figure reflash ROM several times solves problem, it's kinda pain in ass as sometimes I have to reflash it dozens times to have Wi-Fi work...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
How peculiar?!
rootSU said:
How peculiar?!
Click to expand...
Click to collapse
indeed it was ,
i don't know what was going on , but however i managed ...
again , really really really really really annoying as i have to flash something like kernel , Jkay and some other MOD.
first of all i thought it might be some MOD or kernel causing the problem so i only flashed ROM but problem remains ...
even same ROM , this time i flash it might be fine but next it could go wrong ...
It's an intriguing one. I assume you've tried full format of /system etc so I can't think what else it would be. Please update us if you work it out
rootSU said:
It's an intriguing one. I assume you've tried full format of /system etc so I can't think what else it would be. Please update us if you work it out
Click to expand...
Click to collapse
I don't think the word "intriguing" is that I will choose to describe it...
Yes, sure, the wiping is like standard procedure , data, cache and system were always formatted before flash...
Sent from my GT-I9300 using xda premium
Hey guys... this is a tough one...
I have a i9300, and it is rooted, and I use Carbon Rom (a AOSP ROM).
My brother bought one i9300 this week. He asked me to root it, and install Carbon Rom too.
Ok, so I rooted the phone, using CF-Root-SGS3-v6.4, via odin. After that, i flashed philz_touch_5.07.1-i9300 recovery, and used it to flash a zip with the AOSP ROM and Gapps. Well, after i flashed the ROM, the phone boots into Carbon, but reboots EVERY 30 SECONDS. I thought it could be a problem with the download, so i flashed the same file that i flashed on mine, but problem still persisted. Then, i tried to Restore on HIS phone, a Nandroid from MY phone. Same thing.... boots normal, and reboots after 30 seconds. At this point, i realized that his Baseband version was different from mine. (it was the only difference i could find). Mine is BUEMA1 and his was UBELL1.
So, i downloaded, from sammobile.com the latest firmware/radio for his carrier. After flashing it, the phone boots Normal into Stock ROM, but it freezes ALL the time. It freezes on normal uses, such as email, whatsapp, etc...
Could something be corrupt? What would it be? IMEI seems to be fine.
I cant think of anything that could cause reboot every 30 seconds on AOSP, and freeze on Stock
Read the Freezing thread .
jje
JJEgan said:
Read the Freezing thread .
jje
Click to expand...
Click to collapse
where is this? couldn't find it
1. Root it again.
2. Install CWM Revovery
3. Copy a Custom ROM & the rightful Gapps to your SD Card.
4. Boot into Recovery and Select the Option "Format System" or use this tweak: http://forum.xda-developers.com/showthread.php?t=1832326 (install it like you would with a ROM) It will Wipe Everything from your phones Internal Memory.
5. Install the Custom Rom first, then Gapps. Then boot up your phone.
I would suggest using CM10.1 for starters.
yurividal said:
where is this? couldn't find it
Click to expand...
Click to collapse
General
Sent from my GT-I9300 using Tapatalk 2
yurividal said:
Hey guys... this is a tough one...
I have a i9300, and it is rooted, and I use Carbon Rom (a AOSP ROM).
My brother bought one i9300 this week. He asked me to root it, and install Carbon Rom too.
Ok, so I rooted the phone, using CF-Root-SGS3-v6.4, via odin. After that, i flashed philz_touch_5.07.1-i9300 recovery, and used it to flash a zip with the AOSP ROM and Gapps. Well, after i flashed the ROM, the phone boots into Carbon, but reboots EVERY 30 SECONDS. I thought it could be a problem with the download, so i flashed the same file that i flashed on mine, but problem still persisted. Then, i tried to Restore on HIS phone, a Nandroid from MY phone. Same thing.... boots normal, and reboots after 30 seconds. At this point, i realized that his Baseband version was different from mine. (it was the only difference i could find). Mine is BUEMA1 and his was UBELL1.
So, i downloaded, from sammobile.com the latest firmware/radio for his carrier. After flashing it, the phone boots Normal into Stock ROM, but it freezes ALL the time. It freezes on normal uses, such as email, whatsapp, etc...
Could something be corrupt? What would it be? IMEI seems to be fine.
I cant think of anything that could cause reboot every 30 seconds on AOSP, and freeze on Stock
Click to expand...
Click to collapse
hi man , I was having this problem before , try to mega wipe then flash a stock rom via odin
Geaquzzil said:
hi man , I was having this problem before , try to mega wipe then flash a stock rom via odin
Click to expand...
Click to collapse
Mega Wipe... what would that be?
I guess it is this: http://forum.xda-developers.com/showthread.php?t=1983489
right?
Anyways, i have flashed a TouchWizz ROM called WanamLite... the phone is SUPER FAST, and freezing is gone.
Too bad he cant use a AOSP (I LOVE Carbon ROM)... but i will let it stick to WanamLite since it is working and rooted. I kind of gave up
yurividal said:
Mega Wipe... what would that be?
I guess it is this: http://forum.xda-developers.com/showthread.php?t=1983489
right?
Anyways, i have flashed a TouchWizz ROM called WanamLite... the phone is SUPER FAST, and freezing is gone.
Too bad he cant use a AOSP (I LOVE Carbon ROM)... but i will let it stick to WanamLite since it is working and rooted. I kind of gave up
Click to expand...
Click to collapse
Did you at least read my post?
DiDA™ said:
Did you at least read my post?
Click to expand...
Click to collapse
I did. Thank you very much.
The thing is, the phone is running so smooth with this WanamLite Rom, that i am afraid of touchung it and it start freezing again. Not even stock ROM was so smooth. It hasnt frozen in 2 days. But I will for sure try your suggestion if i start to see issues with this Rom too.
I would love to be able to run CarbonRom on his device, but i dont want to take the risk of "touching what is working", specially because it is not my device.
Anyways, i appreciate the help i have received on this forum. Seriously, thank you very much, to each one of you.
yurividal said:
I did. Thank you very much.
The thing is, the phone is running so smooth with this WanamLite Rom, that i am afraid of touchung it and it start freezing again. Not even stock ROM was so smooth. It hasnt frozen in 2 days. But I will for sure try your suggestion if i start to see issues with this Rom too.
I would love to be able to run CarbonRom on his device, but i dont want to take the risk of "touching what is working", specially because it is not my device.
Anyways, i appreciate the help i have received on this forum. Seriously, thank you very much, to each one of you.
Click to expand...
Click to collapse
With a wipe it will work too. If u have PhilZ u can select in reset menu "Clean to install a new ROM".
Gesendet von meinem GT-I9300 mit Tapatalk 2
TheRealFelix0212 said:
With a wipe it will work too. If u have PhilZ u can select in reset menu "Clean to install a new ROM".
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
I did this... Several times
yurividal said:
I did this... Several times
Click to expand...
Click to collapse
Strange.. On my device it works fine.
Gesendet von meinem GT-I9300 mit Tapatalk 2
TheRealFelix0212 said:
Strange.. On my device it works fine.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
I know, on mine too. The problem is with my brother's.
Are you certain they are both i9300s
Sent from my GT-I9300 using xda app-developers app
ads2996 said:
Are you certain they are both i9300s
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
100% positive
You need to check its not a fake / clone first .
Settings about phone details .
jje
JJEgan said:
You need to check its not a fake / clone first .
Settings about phone details .
jje
Click to expand...
Click to collapse
It is deffinetely a Genuine Samsung device...
Hello all,
I tried to put omnirom on my galaxy s3 i9305, but I got status 7.
So I removed the lines (getprop...), but still didn't work.
Than I flashed Perseus kernel on it, because I thought that this will be necessary. I'm not sure if this is the fault, but now the touchscreen doesn't work anymore.
I installed Samsung stock rom but touchscreen still doesn't work.
In stock rom, isn't there also the kernel integrated?
Must I search now for Samsung original kernel?
And why I am not able to install omnirom, although one time it worked.
What version of TWRP do I need to install omnirom with android 4.4.2 and where do I get it from?
Thank you very much for your answers.
Matthias
Sent from my Nexus 5 using xda app-developers app
the problem I've seen the recovery or flash a kernel that is not the model of mobile. are you sure the kernel or the recovery was for your model?
Well,
I was wondering, too, why I get status 7 which means wrong model.
But in the back of the phone it says i9305, and I downloaded kernel and omnirom for the i9305.
Do I need a new kernel anyway?
Sent from my Nexus 5 using xda app-developers app
You are in the wrong forum this is not I9305 q&A
Does that mean you have flashed firmware for I9300???
Any way you now need a paid for service repair .
No, I flashed for i9305.
But there are stock kernels in Internet available, can't I use one of them?
Sorry for the wrong forum.
Sent from my Nexus 5 using xda app-developers app
i've read a couple of days ago that a guy flashed a galaxy note 2 kernel on his i9300 and the same thing happened to him too. his touchscreen wasn't working although he flashed an original rom via odin. only the physical buttons were working. the note 2 kernel he flashed fried something on the mobo so he had to change his touchscreen.
you can download and flash an original rom (they have stock kernels built into them).
good luck
Yes usual is fried digitizer .
See multiple posts .
See recovery by ADB and mouse see stickys .