Related
We received our Samsung Galaxy II phones a few days ago.
My wife had a Swiftkey and Swiftkey X keyboard apps in her Amazon appstore account. She installed Swiftkey X, and she was presented with an "update" that showed Swiftkey (not the X; apparently this is an issue with Amazon appstore based on Swiftkey site). Thinking that it was an update to the Swiftkey X, she apparently applied it, and immediately there were number of FC notices (she remembers seeing TWLauncher among them) and a spontaneous reboot of the phone. Then, she couldn't get online either through WiFi or 4G. At that point she gave the phone to me to fix it
Comparing her phone side by side with mine it is very clear that there's an issue with network connectivity. While mine flies through the pages, market downloads, etc. either on WiFi or 4G, hers get stock for 3-5 seconds before opening pages or sometimes just displays a "webpage cannot be found" or "connection error".
I went ahead and did a factory restore, but that seems to only delete user account, personal files, etc. if I understand it correctly. Moreover, the issue is still there after the restore. So, is there a way to restore the system files to stock as well? Can it be done without rooting, or does it require loading a fresh ROM?
Sorry for the lengthy message and thanks in advance!
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
tenderidol said:
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
Click to expand...
Click to collapse
if you look at the sticky threads at the top of this forum there is one called index by AllGamer. Its at the bottom of the first post. Make sure you grab the Tmobile one and not the telus one
Sent from my SGH-T989 using Tapatalk
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
513263337 said:
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
Click to expand...
Click to collapse
Dude. That's a half ass way, it doesn't take you to stock. First of all its deodexed.. Just a sec
This is the only proper way to go back to stock THIS IS IT RIGHT HERE
Sent from my SGH-T989 using Tapatalk
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
you dont have to root it to run the odin package
mikeyinid said:
you dont have to root it to run the odin package
Click to expand...
Click to collapse
Oh, sorry about that. I'm a newbie for the SII rooting/modding (did quite a bit with Nook Color), and I need to do some reading first.
Smart man!
Sent from my SGH-T989 using Tapatalk
voidthedroid said:
Smart man!
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Alright, I'm halfway through. The rooting process for the SII is little different than NC, but the principles are the same.
By the way, is it safe to assume that some conflict between SwiftKey and SwiftKey X caused the problem on her phone? The reason I ask is because I'd like to put SwiftKey X on my SII (it has multi-language support) and I dont want to deal with the same issue if it was the culprit.
I believe I did enough reading at this point
Since this doesn't involve rooting (now I understand it), I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
mikeyinid said:
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot!
Just finished flashing the stock image and everything worked as expected. This was also a good practice to learn how to restore it to stock in case something goes bad.
513263337 said:
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
Click to expand...
Click to collapse
The issue was created after installing a 3rd party keyboard and -by accident- applying an update that was supposed to be for a slightly different version, which resulted in numerous force closes and random reboots immediately. I might be wrong here, but that indicates that more than just the user files were affected, since deleting just user files via factory reset didn't help the network problem. However, flashing the stock image -without rooting- took care of the problem.
[Stock Odin Rom]{How To Use ODIN} attached. N900TMI7& NB4 (4.4.2) (How to use ODIN)
*****regarding the 4.4 update if u flash in Odin your boot loader will be updated .... Meaning no going back to 4.3***
Here's the stock odin tar downloaded from samfirmware. Mediafire dl link much faster than hotfile http://bit.ly/18Ll149. 4.4 nb4 link
http://www.mediafire.com/download/esadia6synn8s6j/TMB-N900TUVUCNB4-20140305155920.zip
Fyi.. Odin will not factory reset. If you want to start fresh factory reset in recovery before the Odin flash.
1.. Download .tar and Odin to pc (move to desktop)
2.. Extract .zip N900TUVUBMI7_N900TTMBBMI7_TMB-1.zip
3..Run odin as administrator (left click on odin.exe)
4. Put phone into download mode..With phone off press Volume down + home and power (press power button last) ..now press..volume up to enter dl mode..
5.. Connect phone to pc... Wait till drivers install. when completed youll see a yellow ID:COM box light up...
6.. Click on pda and open N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5. ( If you did like i said it will be on you desktop. )
7 Patience.........
When finished it will reboot. on odin a green box should come up saying "passed"
People that havent used Odin before i would suggest using the odin i linked here. Its kinda dumbed down. .. No re-partition options .. If not ***** MAKE SURE TO NOT CHECK ANYTHING ELSE EXCEPT AUTO REBOOT*****....
Link to odin 1.85 https://www.dropbox.com/s/s7t92nmy95kh3d9/Odin3-v1.85-1.zip
***I will keep this post updated with stock firmware's as they become available***
Sent from my SGH-T889 using Tapatalk 4
I need to know how can I just remove /system/csc/languages.xml and repack and flash.
does this change your warranty from 0x0 to 0x1 ?
any brave souls ?
This is the exact rom that you get on your phone. No need to flash unless you need to fix it or go back to stock
Sent from my SGH-T889 using Tapatalk 4
Fyi I talked to. Mr Robinson. Hes going to look into making a root injected stock rom
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Fyi I talked to. Mr Robinson. Hes going to look into making a root injected stock rom
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
If he does not do it I will look into it. Here is a ROM I made for the Sprint Note II http://forum.xda-developers.com/showthread.php?t=1990681. I stopped updating it because my wife was always on me about spending all my time on the computer but since my divorce was final on Monday I have a little more free time.
bp328i said:
If he does not do it I will look into it. Here is a ROM I made for the Sprint Note II http://forum.xda-developers.com/showthread.php?t=1990681. I stopped updating it because my wife was always on me about spending all my time on the computer but since my divorce was final on Monday I have a little more free time.
Click to expand...
Click to collapse
Cool... You don't have to tell me about your wife. I look at my phone or computer and she turns into the devil?. Horns and all . :sly:
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Cool... You don't have to tell me about your wife. I look at my phone or computer and she turns into the devil. Horns and all . :sly:
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
My wife says I touch my phone more than I touch her - but when I explained that most of the time I was touching my girl friend and that she shouldn't worry about my phone, things got really ugly.
mocsab said:
My wife says I touch my phone more than I touch her - but when I explained that most of the time I was touching my girl friend and that she shouldn't worry about my phone, things got really ugly.
Click to expand...
Click to collapse
Lolz... I think you wife and my wife might be sisters
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Lolz... I think you wife and my wife might be sisters
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
LOL
thanks for this, im getting RPC:S-5:AEC-0 errors. Hopefully this will revert everything back to normal.
transitoyspace said:
thanks for this, im getting RPC:S-5:AEC-0 errors. Hopefully this will revert everything back to normal.
Click to expand...
Click to collapse
So am i i asked deez troy about it
deeznutz1977 said:
So am i i asked deez troy about it
Click to expand...
Click to collapse
I just flashed this, Didnt help.....ugh...i knew i should have just waited on the root.
transitoyspace said:
thanks for this, im getting RPC:S-5:AEC-0 errors. Hopefully this will revert everything back to normal.
Click to expand...
Click to collapse
Ditto, also having the same issue. One of the solution was to install the latest Play Store apk, but obviously we have the latest. Then I found another thread here on xda where it apparently went away the following morning.
Seems like it ain't working on my S4 either even though I was able to install an app couple hours ago.
DKYang said:
Ditto, also having the same issue. One of the solution was to install the latest Play Store apk, but obviously we have the latest. Then I found another thread here on xda where it apparently went away the following morning.
Click to expand...
Click to collapse
I Just pmd chainfire ill let youi guys know
deeznutz1977 said:
I Just pmd chainfire ill let youi guys know
Click to expand...
Click to collapse
Seems like you quoted me before my edit. lol. It's also not working on my S4, so it might be on Google's side from what I'm experiencing, but I'll wait and see the response you get from him.
DKYang said:
Seems like you quoted me before my edit. lol. It's also not working on my S4, so it might be on Google's side from what I'm experiencing, but I'll wait and see the response you get from him.
Click to expand...
Click to collapse
Well i have my SG3 on Sprint, works fine there (older version of playstore) and root wasnt by Chainfire(dont think at least)
So I dont think its googles side....hopefully this gets resolved quick.
transitoyspace said:
Well i have my SG3 on Sprint, works fine there (older version of playstore) and root wasnt by Chainfire(dont think at least)
So I dont think its googles side....hopefully this gets resolved quick.
Click to expand...
Click to collapse
Seems like a reboot fixed it on my S4. I'm able to update apps on that one now.
Also just tested with the Note 3, I rebooted and was able to download an app. I still think it was on Google's side, but that's only an assumption or it could be because these two devices are using my primary gmail account.
DKYang said:
Seems like a reboot fixed it on my S4. I'm able to update apps on that one now.
Also just tested with the Note 3, I rebooted and was able to download an app. I still think it was on Google's side, but that's only an assumption or it could be because these two devices are using my primary gmail account.
Click to expand...
Click to collapse
I didnt reboot, it just started auto updating stock apps. Looks like it might have been Google.
Either way this Odin works. thanks OP for hosting it on mediafire, hotfile always takes forever for me. :good:
As this is the first Odin firmware tar I will move this to development
Future releases would need to go in General.
I successfully rooted and installed twrp on my 10.1> I think I just made a big mistake tho and bricked my device. So i tried to used odin to install the factory firmware but when I load it odin freezes, only does this with the factory .md5 not recover.tar . I tried to format everything but nothing works I still have the twrp interface on my tab but when i turn it on its stuck at the galaxy tab 3 screen
Reinstall twrp with odin to see if that clears in?
cduced said:
Reinstall twrp with odin to see if that clears in?
Click to expand...
Click to collapse
Device doesnt show in com slot
fix
The exact same thing happened to me, the stock firmware file is almost 2 gig, odin isnt freezing, its verifying the file so load it then wait
Zidkijah posted on another thread a copy that I was able to use to un-brick mine. Note that the only problem is that it's a little bit different from the stock version. But so far so good, just need some tweaking.
I uploaded it to a dropbox account so if one doesn't work, you can try the other.
His Link
My Link
I plan on re-installing clockwork mod, backing it up to my SD card and trying out the Deodexed version that came with the P5210.
Here is the thread
andrugs said:
I successfully rooted and installed twrp on my 10.1> I think I just made a big mistake tho and bricked my device. So i tried to used odin to install the factory firmware but when I load it odin freezes, only does this with the factory .md5 not recover.tar . I tried to format everything but nothing works I still have the twrp interface on my tab but when i turn it on its stuck at the galaxy tab 3 screen
Click to expand...
Click to collapse
has happened to me too just yesterday you have to download your firmaware right from this site: http://samsung-updates.com/device/?id=GT-P5210
ps. very slow, you have to have patience, but at least they work
Simix93 said:
has happened to me too just yesterday you have to download your firmaware right from this site: http://samsung-updates.com/device/?id=GT-P5210
ps. very slow, you have to have patience, but at least they work
Click to expand...
Click to collapse
One thing though, I don't see one listed for the USA.
I'm sure it's because it was only released in June of 2013 and no official updates available.
gjimene2 said:
One thing though, I don't see one listed for the USA.
I'm sure it's because it was only released in June of 2013 and no official updates available.
Click to expand...
Click to collapse
this is for the USA but I do not know if it works, try: http://www.androidfilehost.com/?fid=23060877490002437
and anyway I do not think it is so important to the firmware for which the region is but just look at your tablet alive, right?
Simix93 said:
this is for the USA but I do not know if it works, try: http://www.androidfilehost.com/?fid=23060877490002437
and anyway I do not think it is so important to the firmware for which the region is but just look at your tablet alive, right?
Click to expand...
Click to collapse
So true, hopefully I didn't come off as to complain lol.
I have that file archived too. It has a good feel to it. The keyboard is bigger but looks just like the one of my Note 2, but with the numeric keys on top of the qwerty.
gjimene2 said:
So true, hopefully I didn't come off as to complain lol.
I have that file archived too. It has a good feel to it. The keyboard is bigger but looks just like the one of my Note 2, but with the numeric keys on top of the qwerty.
Click to expand...
Click to collapse
I did not understand what you wrote, but I hope functions, if that's okay with prizes that I do not miss one
Am I just being stupid or is there a way to root the new note 10.1 2014 edition on t-mobile's network? The model is SM-P607T & I don't see that listed anywhere on odin/s list or anything. Or is it just too soon from release?
Extra info: Baseband P607TUVUANE2, Android 4.4.2, Kernal 3.4.0-1433887
riffy504 said:
Am I just being stupid or is there a way to root the new note 10.1 2014 edition on t-mobile's network? The model is SM-P607T & I don't see that listed anywhere on odin/s list or anything. Or is it just too soon from release?
Extra info: Baseband P607TUVUANE2, Android 4.4.2, Kernal 3.4.0-1433887
Click to expand...
Click to collapse
I am looking for this as well since i got one today. It looks like it is the same thing as the P605 which is LTE. The non LTE ones do not use the Qualcomm chip. It also looks like 4.4.2 just came out for the P605 not to long ago and there really isn't anything out for it yet. Bigbuff is talking about updating TWRP to 4.4.2 for the P605. At that time I am sure we will get a recovery and be able to flash SuperSU. If it is out already I have not found it and would like to know as well.
OK so it's not just me then. Usually by the time I get a device all this stuff is out all ready.
I wonder if you can use the international version P605. That's got the qualcomm chip with LTE. I have the 605v and there's been no development for it. Verizon has locked the bootloader, as they tend to do, so we are stuck. If you understand Knox and how that works I would try the P605 method. I tried it on mine and it failed and it didn't cause any damage.
Sent from my SM-N900P using Tapatalk
Have you guys tried to put your tablets into download mode. My underdstanding you need to hold down volume down plus the power button for three seconds, but when I try this mine boots into regular mode and not the download mode. Can someone else try this and see if you get a different outcome?
Sent from my SM-P607T using XDA Premium 4 mobile app
Haven't tried it but you have to add home to that as well I thought. Yeah, Google search:
Boot your phone into Download Mode by Pressing and Holding the Volume Down + Home + Power buttons at the same time till you see a warning message on your screen. You’ll be asked to hit the Volume Up to continue into download mode.
draigons said:
Have you guys tried to put your tablets into download mode. My underdstanding you need to hold down volume down plus the power button for three seconds, but when I try this mine boots into regular mode and not the download mode. Can someone else try this and see if you get a different outcome?
Sent from my SM-P607T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
its Power + Vol-D + Home gets you to a screen that says vol up to get to download mode or vol down to reboot. I can get to Download mode by doing that. I am going to try doing the P605 root they have out and see how that goes in asec. Make sure you down the Full Odin Firmware.
http://www.sammobile.com/firmwares/3/?download=29807
So you can use this if you need to.
Good luck! I'm not adventurous enough to try it.
WARNING: By doing this your Spen will not work anymore
Ok here is how to root the P607T right now. It is the same way as Root for the P605 right now. After reading http://forum.xda-developers.com/showthread.php?t=2766394&page=9
on post 88. Someone with the P605 used the P905 CF-Auto root to root their 605.
here are the steps
1. Download to your PC http://download.chainfire.eu/385/CF-Root/CF-Auto-Root/CF-Auto-Root-viennalte-viennaltexx-smp905.zip
2. Reboot your P607T into Download Mode. You can do this by turning off the tablet. then hold Home + Vol-D + Power you will get a screen that says Press Vol D to get into Download mode.
3. Plug your P607T into your PC.
4. Open Odin 3.07 which is included with the down you already did. You should see a Blue tab that says something like Com1.
5. Make sure the only thing that is checked is Auto-reboot.
6. Click PDA and file the CF-Auto-Root-viennalte-viennaltexx-smp905.tar that was in the Zip file you just unziped.
7. Click start and wait.
Your tablet will now reboot into a P905 recovery and flash SuperSU. It can take awhile for the reboot into recovery to happen so just wait. After this is all done your tablet will boot back into Android. Go into the play store and update SuperSU. SuperSU will keep FCing until you update it in the Playstore.
Now here is the problem we run into if you do all this. After CF-Auto Root is done it is going to put a P905 recovery on your Tablet not a P607T recovery. If you want to get your P607T recovery back for future OTAs you need to Odin the full Firmware for the P607T which you can find here. http://www.sammobile.com/firmwares/3/?download=29807 Once they get a working TWRP for KitKat and the P605 we should be able to get everything else we need to get back our old recovery.
Now another problem That I have found as well is that the Spen does not work after doing this. I do not really care because I do not really use the Spen. I know there is a fix in this thread http://forum.xda-developers.com/showthread.php?t=2766394&page=9 but I have yet to get it to work because I do not know how to type the *#2663# in phone app and then update wacom firmware from kernel to get the Spen to work. We do not have a Phone app to do that. So you are warned that your Spen will not work after doing this.
Other Wise enjoy root until a better way is out.
LTE still work?
riffy504 said:
LTE still work?
Click to expand...
Click to collapse
No clue I don't use LTE I just opened a 200mb line to get the Tablet on EIP. I will pop in my sim when i get home from work and check it for u.
Edit: yes lte still works I am still trying to fix the spen however that still doesn't work.
Also looks like TWRP has a working recovery now for the P607T. here is a link to a odin file for it. http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776 I would use that and just flash SuperSU with it. should give you root and hopefully a working Spen.
May be possible to use mobile odin pro and inject root to the stock firmware, without tripping the knox flag?
This works on the note 3, upgrading to 4.3.
Edit: mobile odin requires to have already root, I used it when upgrading to 4.3
to not lose root.
Thanks.
To late... I already tripped stupid knox. hehe I love the samsung note lines but I really REALLY hate knox! Just a reason for them to deny warranty, or else it'd be optional.
That odin file worked great. Now to wait for some custom roms.....
Just jumping in on the got-this-yesterday train and glad to see some folks have jumped on ahead of me. Thanks for the information you've all provided thus far. I'm hopeful that development on this thing will be strong, I'm liking the device so far.
I'm interested in rooting ASAP but I've been out of the Android loop for a little while, so this KNOX thing freaks me out a bit (I'm just getting familiar with what it is). Seems like it is a simple warantee related thing. Is it irreversible? How common is flashing a custom ROM without triggering it? Does it affect usability at all to have it triggered?
I'm interested if flashing this this evening but not really sure what I'm in for as far as KNOX.
amirite said:
Just jumping in on the got-this-yesterday train and glad to see some folks have jumped on ahead of me. Thanks for the information you've all provided thus far. I'm hopeful that development on this thing will be strong, I'm liking the device so far.
I'm interested in rooting ASAP but I've been out of the Android loop for a little while, so this KNOX thing freaks me out a bit (I'm just getting familiar with what it is). Seems like it is a simple warantee related thing. Is it irreversible? How common is flashing a custom ROM without triggering it? Does it affect usability at all to have it triggered?
I'm interested if flashing this this evening but not really sure what I'm in for as far as KNOX.
Click to expand...
Click to collapse
Edit: Originally used root de la vega method for the note3. Mobile odin requires root.
The procedure to inject root with mobile odin pro is on the international note 3 forum.
Worked for my tmo note 3 upgrading to 4.3 and not lose root, but only flashing the original firmware.
Any custom rom, custom recovery or custom kernel will trip knox.
This is not tested yet on the note 10.1 2014.
Will check on the mobile odin thread or Chainfire's blog.
Tripping knox for now is irreversible and voids the warranty.
Normal device operation is not affected. What is lost is the security feature.
Only a concern if your company uses knox, and you use your device for work.
I am going to wait a few weeks, hoping for a no knox tripping root method,
to keep the warranty. But I know that eventually will not care on tripping knox.
Well fudge! I never thought to test the s pen before I rooted. Guess what, it doesn't work.
riffy504 said:
Well fudge! I never thought to test the s pen before I rooted. Guess what, it doesn't work.
Click to expand...
Click to collapse
I posted a big huge warning sign saying that the s pen would not work if you rooted
Sent from my HTC One_M8 using Tapatalk
No I mean it didn't work hardware wise. I thought the touch screen was off by 1/4th an inch but never thought to try the s pen before last night. I even flashed back to stock and it was the same way. Where ever you touched with the s pen it'd either do nothing or it'd randomly draw in a tiny little square up near a corner. The touch screen was really noticeable trying to click on links in chrome cuz I'd always missing, but I thought it was me till I realized the s pen didn't work either. Then I figured it was just the hardware was messed up. Messing around in the drawing app proved that the touch screen was off to a corner by 1/4th an inch. Even if I turned the device around it always was off to that same physical corner.
Oh! Also, I used the new Odin file btw. I assume the s pen works on that one. Never did use the one for the P905, that you posted with that warning.
Hey everyone.
Been a LONG time since I have been on XDA. Got the new Note 5 and decided to customize my Note 4. I downloaded TWRP (Latest from their site) for my Sprint Note 4 and something strange has happened.
After flashing through Odin, my screen touches are off by 3/4" on part of the screen... Meaning, On the top 1/3 of the screen, my touches act normal but on the bottom 2/3, they are "off" as in, when I touch, the input registers about 3/4 of an inch lower than where I am touching.
I have tried redownloading and reflashing TWRP and also tried the latest CWM Recovery. I was able to get Hybrid 3.0 Rom to flash and after booting up, during initial setup, it's still the same way. Meaning when I touch the "2" on the keyboard, it registers the letter "z".
UPDATE*** (Video https://youtu.be/MtU9qoIZooM )
After fidling and getting the ROM to launch, I notice I can use my SPen just fine. Going to take video and post what is happening. Here are a few pics of the screen touch turned on in Developer mode. As you can see in the images below, with my finger, the touches are further off the lower I get on the screen but fine with the SPen.
Video
https://youtu.be/MtU9qoIZooM
thermus said:
Hey everyone.
Been a LONG time since I have been on XDA. Got the new Note 5 and decided to customize my Note 4. I downloaded TWRP (Latest from their site) for my Sprint Note 4 and something strange has happened.
After flashing through Odin, my screen touches are off by 3/4" on part of the screen... Meaning, On the top 1/3 of the screen, my touches act normal but on the bottom 2/3, they are "off" as in, when I touch, the input registers about 3/4 of an inch lower than where I am touching.
I have tried redownloading and reflashing TWRP and also tried the latest CWM Recovery. I was able to get Hybrid 3.0 Rom to flash and after booting up, during initial setup, it's still the same way. Meaning when I touch the "2" on the keyboard, it registers the letter "z".
UPDATE*** (Video https://youtu.be/MtU9qoIZooM )
After fidling and getting the ROM to launch, I notice I can use my SPen just fine. Going to take video and post what is happening. Here are a few pics of the screen touch turned on in Developer mode. As you can see in the images below, with my finger, the touches are further off the lower I get on the screen but fine with the SPen.
Click to expand...
Click to collapse
Heard of this before and it was due to flashing wrong recovery for your device. Maybe try going back to complete stock unrooted with official tar.
Will give that a try. That's the one thing I didn't try.
it happened to me, dial *#2663# and update the tsp fw update (general), it eventually fixed the issue for me although i had to do it frequently for at least a month until the phone forgot about it
sr.bond said:
it happened to me, dial *#2663# and update the tsp fw update (general), it eventually fixed the issue for me although i had to do it frequently for at least a month until the phone forgot about it
Click to expand...
Click to collapse
HELL YES!!!!!!! I was just coming back to report that the flashing to stock do NOT fix it. Your recommendation work beautifully! THANK YOU!!!!:laugh:
Anyone have ideas? I have the US Cellular variant and this exact problem after flashing TWRP except that *#2663# doesn't do anything... I've seen someone do it in a video and nothing happens when I hit the last pound. Is it different for USC?
For anyone wondering I had to root, enable hidden menu via editing the file at efs/carrier/hiddenmenu, once I did that the *#2663# worked and I was able to perform the update. Touchscreen works fine now.
I am having the same Issue
I am not a noob been doing this for awhile but the other day I had grabbed the wrong TWRP recovery for my Note 4 I grabbed the Note 4 edge and now my screen is out of whack and I cant used the *#2663# code to bring up the TSP FW so.... any help would be appreciated
I have tried flashing different ROMS, Kernels to get back to stock that didnt work, I have tried Galaxy tools but I cant find how to bring up the TSP menu I have tried flipping the recoveries and wiping and formatting to no avail, so Need some help if possible
SysEng1967 said:
I am not a noob been doing this for awhile but the other day I had grabbed the wrong TWRP recovery for my Note 4 I grabbed the Note 4 edge and now my screen is out of whack and I cant used the *#2663# code to bring up the TSP FW so.... any help would be appreciated
I have tried flashing different ROMS, Kernels to get back to stock that didnt work, I have tried Galaxy tools but I cant find how to bring up the TSP menu I have tried flipping the recoveries and wiping and formatting to no avail, so Need some help if possible
Click to expand...
Click to collapse
Sometimes the first step is restore full stock tar and then try the dialer code.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Stock Tar
samep said:
Sometimes the first step is restore full stock tar and then try the dialer code.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have been trying the stock Tar but anything "stock" seems to boot loop tried wiping everything then tried wiping davlik and cache after ROM flash
I have been also trying to get the *#2663# menu to come up edited build.props and created /efs/carrier/HiddenMenu but I can never get the tsp menu it works great on my Note II and thats jellybomb ROM version 21 and if I dial *#2663# bam instant TSP menu
SysEng1967 said:
I have been trying the stock Tar but anything "stock" seems to boot loop tried wiping everything then tried wiping davlik and cache after ROM flash
I have been also trying to get the *#2663# menu to come up edited build.props and created /efs/carrier/HiddenMenu but I can never get the tsp menu it works great on my Note II and thats jellybomb ROM version 21 and if I dial *#2663# bam instant TSP menu
Click to expand...
Click to collapse
When you goto download mode, does your phone's display show reactivation lock enabled or disabled?
Even if it is enabled, you should be able to successfully flash the stock tar that matches your bootloader (should be the last full update your phone completed- I wouldn't say bootloops count as successful upgrade or downgrade of bootloader). You would then need to let it auto reboot and sign in with original Google account password during the setup wizard.
If your reactivation lock is disabled, pay close attention to what you're flashing and watch Odin log for issues. If you can boot to stock recovery, factory reset and try Odin again.
Edit: what stock tar are you trying you flash? Most likely, you still won't succeed in downgrading the bootloader to lower security bootloader once you update to OE1 or higher.
Sent from my SM-N910P using Tapatalk
Thanks that ROM worked
samep said:
When you goto download mode, does your phone's display show reactivation lock enabled or disabled?
Even if it is enabled, you should be able to successfully flash the stock tar that matches your bootloader (should be the last full update your phone completed- I wouldn't say bootloops count as successful upgrade or downgrade of bootloader). You would then need to let it auto reboot and sign in with original Google account password during the setup wizard.
If your reactivation lock is disabled, pay close attention to what you're flashing and watch Odin log for issues. If you can boot to stock recovery, factory reset and try Odin again.
Edit: what stock tar are you trying you flash? Most likely, you still won't succeed in downgrading the bootloader to lower security bootloader once you update to OE1 or higher.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you the ROM helped me fix my issue and now I am back to good
sr.bond said:
it happened to me, dial *#2663# and update the tsp fw update (general), it eventually fixed the issue for me although i had to do it frequently for at least a month until the phone forgot about it
Click to expand...
Click to collapse
:good:
Total awesomeness!!! This worked perfectly. Thank you for sharing with the community!
The *#2663# is like sugar......Thank you veeeeeeeeryyyyyyy much
Thanks a lot for *#2663# !!! Even after 8 years I need the Gallaxy Note 4, because its one of the last Phones with easy changeable batteries.