Database Info

Touchscreen not working after root, but S-Pen works fine

I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu

Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets

I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2

to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?

This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...

jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?

kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.

I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.

reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.

reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.

Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.

Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?

Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions

anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding

WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck

erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir

popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .

erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen

any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help

reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse

[Q] PLEASE HELP. Soft Bricked My Verizon Galaxy S4.

Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.

muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped

[Q] Kernal flashing gone wrong...need help :(

Hey everyone, I'm new to android and tried something just to install a custom ROM. I flashed the kernel and tried to install a new one and I thought it was going well when I heard the woman talking through the phone, but apparently not... Now when the logo shows as it starts but it never makes it pass there.
It shows something like TV static and then reboots again and again.
It hasnt stopped since... I really feel bad cause i feel like a failure and thats the only good phone i have ever gotten...
Ive also tried the recovery mode, that doesnt work. The logo at startup gets brighter then reboots agaain ans again... Please help me.. Please asap so i can use it finally... Thanks alot
Oh sorry i forgot to state the phone specs , im new here...
Samsung Galaxy S 4G
2.2
Couldnt get it updated to 2.3
Thanks again guys.

StrugglaREP said:
It shows something like TV static and then reboots again and again.
Click to expand...
Click to collapse
As the cobwebs clear, that sounds like problems with bootloaders going from Froyo to Gingerbread. I vaguely remember something about "rainbow" screens if you didn't follow the right steps in the transition.
I think your best bet is getting the Heimdall "one-click" approach to work for you. If you don't have a custom recovery running, there aren't a lot of choices.
@lumin30 wrote up a great set of instructions that I would follow carefully.
It's pretty hard to hard-brick an SGS4G, so breath easier...

I'll give it a try, thanks!
jeffsf said:
As the cobwebs clear, that sounds like problems with bootloaders going from Froyo to Gingerbread. I vaguely remember something about "rainbow" screens if you didn't follow the right steps in the transition.
I think your best bet is getting the Heimdall "one-click" approach to work for you. If you don't have a custom recovery running, there aren't a lot of choices.
@lumin30 wrote up a great set of instructions that I would follow carefully.
It's pretty hard to hard-brick an SGS4G, so breath easier...
Click to expand...
Click to collapse
Thanks for answering so quickly, I'll be sure to go and try it out right now and see what happens. I really hope th phone connects to the computer atleast cause it keeps restarting itself... as I said I'm really new to Android I was just trying to update the kernel toget the ROM able to update so I can put on a custom one and get the apps that I really need that wouldn't work on 2.2
But Thank you very much , I'll get right on it and see what happens and say whether it worked or not

[Completed] [Q] Installing Android Lollipop on a unknown tablet.

Hello! This is my first post on this forum, but I'll try to be helpful.
Well, I got my hands on a tablet. Which tablet? I have no idea. The "About page" on the settings only says that the Model number is M1706. And nothing else. (Besides that it's running on Android 4.2.2)
Since Android Lollipop is out, I've been dying to try it. Unfortunately, I don't have a device that supports it, so I though I'd try to install it on this random tablet that I have.
And here's where the problems start.
I tried flashing a AOSP Lollipop build to the tablet, but it always aborted. (From this thread)
Then I tried to install a custom recovery to see if that would help.
Managed to find the TWRP apk and install it. Unfortunately the app crashes when I open it.
So I tried downloading it from the App Store. The thing is that my tablet doesn't have the App Store app.
I tried many different versions, but none of them were able to be opened. It's like a process was killing the app, I think. I have no idea, though.
I then installed Clockworkmod ROM Manager to see if that would work.
It installed and opened, but it can't flash ROMS unless my tabled is rooted.
Since this is a mistery tablet, I don't think there are any root methods for it.
That's my situation right now.
Any suggestions on what I can do to achieve my goal of installing Android Lollipop on my tablet?

Hi,
I have to say, you're swimming in dangerous waters here.... And so far you've been extremely lucky. You can't flash anything to just about any device, unless it's made specifically for your device. Many times trying to do so can brick (destroy) your device.
So you'd be best to stop trying to install things made for other devices.
As far as your device getting Lollipop, that seems doubtful. I say that because it's on Jelly Bean.... Not even kit Kat. Of course that's an educated guess though. And until you find out what actual device you have, There's not much we can do for you. Also, you won't know if there's anything out there for your device... Cause you don't know what device you have.
I'd work on solving that mystery... And go from there. ?
Good luck.

Darth said:
Hi,
I have to say, you're swimming in dangerous waters here.... And so far you've been extremely lucky. You can't flash anything to just about any device, unless it's made specifically for your device. Many times trying to do so can brick (destroy) your device.
So you'd be best to stop trying to install things made for other devices.
As far as your device getting Lollipop, that seems doubtful. I say that because it's on Jelly Bean.... Not even kit Kat. Of course that's an educated guess though. And until you find out what actual device you have, There's not much we can do for you. Also, you won't know if there's anything out there for your device... Cause you don't know what device you have.
I'd work on solving that mystery... And go from there. ?
Good luck.
Click to expand...
Click to collapse
Eyyup. I know what I'm doing is very dangerous, but this tablet is basically useless without any form of Google apps. Besides, I think it's a prototype tablet, so even if I brick it, I won't be sad. I got it for free, after all.
I'm trying my best to figure out which device it is. Usually when you have Google apps in a device, Google Play store shows its type when you install an app using Google Play Store on a desktop. Since I can't get Google Play Store in it, though, it may be a lot harder. I still need to try installing Google+ to see if it works. Will come back with the results in a bit.

Hi,
If you want to post about this further, please post here...
[Ask Any Question][Newbie Friendly]
XDA Assist is here to help members navigate the site, not for support.... So this is not the place to discuss your progress unfortunately.
Good luck! Thread closed.

[Completed] How do I unbrick my phone?

First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.

I have some good news. I managed to flash the firmware again and now I can access the phone again. However, the WiFi problem persists. I've tried looking on the internet for a solution, but I can't find one. I've tried flashing the modem and all that stuff, but it still doesn't work.
Oh, and by the way, I no longer have TWRP and I don't think I have root access anymore either (I had to do a data partition wipe as well).

I'd really appreciate a reply from someone. I've tried everything, but to no avail.

einwaliser said:
First of all, I'd like to say that I know very little about how Android, electronics or mobile phones work in general, so everything I've done has been from internet tutorials. Please don't use any jargon as I probably won't know what you mean. ELI5.
A few days ago, I tried to root my phone and it didn't work. As a result the phone went into a boot loop and I didn't know how to fix it. The long and short of it was that I ended up flashing the stock firmware onto my phone and basically doing a complete factory reset. After some time trying this I managed to get the phone to start up and I was able to access the interface and all that. Unfortunately, my WiFi wasn't working (the button would simply turn off whenever I turned it on) so I had no way to download the most recent updates or apps or anything like that. After following several tutorials on how to fix this, such as flashing the modems and bootloader, I still wasn't having any luck. So I tried something that proved to cause even more problems - I tried to install a new kernel. Now my phone won't even boot past the logo. I probably didn't install the right one, but what can I say, it's not very clear which one I need.
Now I'd like to point out that as a layman who just wants his phone to work again, half of the time I don't understand what I'm doing or whether or not I'm doing it right. In other words, I realise that I've probably messed up my phone, but what can I do? I can't take it to a technician because I don't have the money for that, I can't buy a new phone for the same reason and I can't phone up and ask for a replacement because the warranty expired ages ago and I don't have the original documents here.
I've installed the Team Win Recovery Project on my phone and I have Odin installed on my PC as well.
TLDR; yes, I know I'm an idiot and I don't appreciate you telling me. I'd like to reset my phone to how it was before - the normal firmware, the normal kernel and all that, but I'd still like to have root access and keep the TWRP recovery mode too.
Model: Samsung Galaxy S4 GT-I9505
Model name: GALAXY S4 LTE
Country: UK
Version: Android 5.0.1
You'll probably need more information, so if you do just let me know and, if possible, where I can find it.
Click to expand...
Click to collapse
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.

engloa said:
Hi
We have a dedicated help section for the S4, you'll need to start a new thread and ask there, providing as much info as you can:
http://forum.xda-developers.com/galaxy-s4/help
A [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly thread is also available for you if you dont want to start a new thread.
Good luck.
Click to expand...
Click to collapse
Hi engloa,
It's OK, I've fixed the problem now; I installed a different ROM and now it works fine. Thanks anyway though.