Develop Bugs

[Q] Rom Question

I'm having issues flashing multiple roms of the 4.x.x Roms. The only rom so far I have been able to install and actually run on my phone is TweakWiz V2. I have tried many other roms and they just stay in a boot loop screen. Examples are with the Avatar rom it just stays on the mask an keeps going and going. I have tried CyanogenMod/Cyan Kang an it just stays on the Circle with the bar going around on the inside.
I am running the TWRP Touch Recovery. I also have the latest Radio update and everything else is updated on my phone.
I also let the install itself run for 10+ minutes everytime. But all the roms I try they keep doing the exact same thing and staying in a boot loop.
Can anyone give me any tips or suggestions to maybe something I could do to use another rom or maybe even a suggestion to something I may have overlooked.. Any help is appreciated. Thank you.
An if you need me to give any other information let me know an I will provide.

1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash

krazierokz said:
1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash
Click to expand...
Click to collapse
1.Im using the latest TWRP.
2. Wiping System, Cache, Dvalik or whatever. I wipe everything in the usual instructions. And I make a backup of previous ROM. Flash the ROM then the G-Apps.
3. After I flash I let the ROM run its course an I wait from 15-45 mins for the ROM to load if it doesnt I switch back to TweakWiz or try another.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

try using this recovery since the recovery you are using is the latest one and technically for 4.3 ROMs, give this a shot http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.5.0.0-hercules.tar its the same recovery but lower . the steps you clarified seem very proper but your recovery may be at fault crossing fingers try flashing that recovery through odin or download the zip from the same website and report back after trying to flash again

Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.

idtheftvictim said:
Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.
Click to expand...
Click to collapse
Is there a option I'm not deleting ?
Because I've been flashing ROMS on different phones an I have never had any issues before. I was using ICS an GB etc before an just recently decided to upgrade an use the JB (I think that's the name.) on my phone.

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

HELP Baseband Unknown and Deleted IMEI

Hello guys I just wanna inform you that there is something happening with the CM 11 4.4+ based ROMS
they deleted my Baseband and IMEI
I restored through KIES and got my Baseband and IMEI back but this thing keeps happening and I cannot figure out why?
It's painful procedure because I did this more then 10 times
First I had to Reflash everything through KIES which makes my phone as DEFAULT
then I had to ROOT and install the ROOTED Original 4.3 then I had to install Clockwork Mod with MOBILE ODIN in order for me to install different ROMS
after that I do FULL WIPE ALWAYS
Cache / Dalvik / Data / System even Internal Storage
I installed CM11 whatever ROM u choose:
http://forum.xda-developers.com/showthread.php?t=2453586 (tried this one no success)
Tried this one:
http://forum.xda-developers.com/showthread.php?t=2565259 again the same thing Bad baseband
Also this one:
http://forum.xda-developers.com/showthread.php?t=2493905 OMNI Rom (first installed older version everything was fine but when It updated to the latest OMNI I got the same Unknown Baseband and no DATA whatsoever)
so what the heck is going on? Please help me?

recovery might be the issue
I just had this problem yesterday. You wouldn't happen to be using TWRP recovery would you? I found that if I was using TWRP and Kit Kat AOKP I would have no service and my APN list would be empty. If I used Philz Custom recovery or CWM it would work fine.
I tried going downloading the newest 2.6.3.1 version of TWRP and it made my phone unable to boot. I had to flash another recovery via Odin in order to get back into my phone.
Just a thought.

I've had this issue as well and for some reason the latest nightlies don't play nice with my phone and recovery I'm using the latest official twrp for t0lte. Not t0ltetmo. I recently tried fishing the last multi window and I lost my microphone use. I have since reverted to a homemade build from January.. It seems to be the only thing that works.
Sent from my SGH-T889

Guys I used both CWM and TWRP both the latest versions... and this thing happen during both tries... I don't think it's the Recovery!

[Q] Soft Bricked my phone, have no idea what to try next.

Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes

Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?

audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.

Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes

You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?

Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors

audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?

At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.

You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?

The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.

IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes

I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.

audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?

You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.

audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?

Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.

audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes

I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.

I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?

Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.

Samsung Galaxy Note 4 Inaccurate Touchscreen, Can't Flash ROMs

touch screen bugging out
Ok so my phone for some reason can't click on the exact location i seem to want to press
idk i was trying to flash the silly roms you guys have around here. for stock galaxy note 4 spr
i've been flashing for a while
and it seems none of them work anymore
i use the latest TWRP even used the other one CWM or something like that
i used odin even up to .10 from 1.85 even lower and still can't
even when i install (seems to be the only rom i can cm12)
the locations i press on my screen are buged out. so i have to press higher than i should to even get a click and its hard to text or anything.
i did factory resets, cashe wipes. deleted partitions.. what am i doing wrong ??
why can't this annoying this go away what am i missing guys ???
and why is it only 1 rom can flash on my phone ?? and i can't go back to any lollipop or anything ??
(i also tried flashing a superSU from the tWRP .. when i used CM 12 and it all successed but still
i have this thing where i can't click anywhere im on my phone directly i have to try and feel it out.. please help

1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom

Not long ago, it was discovered flashing the wrong recovery will mess up the lock-screen.
Some were solved with KIES firmware restore; no root, straight to dialer type *#2663# and then TSP FW update. If KIES won't update it, power down, pull battery 30 seconds, Odin stock tar and boot then the dialer code and update.
Do that after you determine which stock tar or KIES update is recommended from Your response above.
Sent from my SM-N910P using Tapatalk

schlepprock said:
1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom
Click to expand...
Click to collapse
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD

it seems this has been a common issue the word we are looking for is calibration issues
it seems it happens to this person exactly how it is happening to me
there was a solution at the bottom but those buttons do not work for galaxy note 4 spr
does anyone know the codes for doing so ?
source:
http://forum.xda-developers.com/note-4-tmobile/help/touch-screen-issues-root-t2986883

Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk

NatsarYAhu said:
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD
Click to expand...
Click to collapse
I recommend you flash this rom. Mostly stock but very stable,and the developer is working on some goodies.
http://forum.xda-developers.com/showthread.php?p=62336588
I recommend that you back up everything you want to keep because you need to wipe everything EXCEPT external SD card. Wipe cache, dalvik , system, and data three times. Then factory reset three times and then flash this rom.
Note4 Rocking a Hybrid Rom

samep said:
Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Ok so this stock actually went through will get with you shortly to let you know if sync is fixed,
edit: still not synced correctly but phone does finally work how i want just the main problem is bugged trying the link with *#2663# now
Edit: IT WORKED !!! big UPS BRO thank you !!!

i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks

imeicodes said:
i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks
Click to expand...
Click to collapse
Odin stock tar and try again.
There's also an update to CFAR (Chainfire auto root) for Note 4. After you fix your touchscreen, root with it and make a TWRP backup once that is installed. A TWRP restore plus full un-root in SuperSU may make OTA possible; CFAR backs up stock recovery.
You can use Flashify to install custom recovery. You may have installed the wrong recovery to have the touch screen out of cal like it is.
Sent from my SM-N910P using Tapatalk