Related
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this (PLEASE NOTE THIS IS Version 2 and please use this version to revert successfully previous version had some flaws in it): http://www.mediafire.com/?d4n1fx3cj446k1l)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
5pace said:
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this: http://www.mediafire.com/?muiza8fbwidq69d)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you
Click to expand...
Click to collapse
orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
yuryvrn said:
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
Click to expand...
Click to collapse
orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I have the stock JOP40D, yakju, the phone is rooted. My sensors.tuna.so is attached. I am new to android, did I understand you correctly all I have to do is to replace the original sensors.tuna.so by the modified file you will send back? Or I need to apply your patch as described in the 1st post (since my ROM is stock)?
THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.
I have this issue too. I am on CM 10.1 EuroSkank on stock kernel. Is there a zip file I can flash? Thanks for the fix!!!
Sent from my Galaxy Nexus using xda premium
PaXGeN said:
THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.
Click to expand...
Click to collapse
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium
LKNim said:
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You can try the Fix, if it doesn't work properly you can restore the backup with the Un-Fix :good:
Proximity Sensor Blues!
5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I'm new to this forum, so bear with me. I've been having the Proximity Sensor Blues lately and am in need of a cure. I've got a Verizon GNex (rooted and unlocked) running JB Sourcery 4.0 (soon to be 4.1 unless you tell me different) with their most recent "stock" kernel. I've attached the two files you requested, but have not tried the fix yet.
Considering the ROM I'm running and the attached files, is it OK for me to try the fix? Should I try a different kernel? Does it matter if I have TWRP instead of CWM? Please help!
Everything its ok
Sent from my Galaxy Nexus using xda premium
Sorry guys, I didn't have much time to reply this topic I had exams plus real life hassles to deal with, again I am sorry for the delay.
I've attached flashable zips files and appended your appropriate usernames with them, you can download and flash these files as per your usernames. If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
On a side note I knew about the app (even before making this mod), but I wanted my proximity sensor to be disabled without depending upon an app so I eventually came up with disabling it through lib file which was far more efficient. And these files aren't supposed to disable all the other sensors, using other ROM libs on another ROM will stop the functioning of other sensors, it's just because every ROM is unique in it's own way so these files require to be modded according to their respective ROMs source files. And yeah, again I do not guarantee this mod would work because after applying it to my Nexus, it still rebooted but the reboots were less occurring as compared to when the proximity was enabled.
P.S. I re-purchased Galaxy Nexus, the old one was a C8 (White color), and luckily the new one was a C2 (Black color) and it can do wonders in overclocking and undervolting.
On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?
bacekoko said:
On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?
Click to expand...
Click to collapse
You may want to try this:
5pace said:
If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
Click to expand...
Click to collapse
If it doesn't help in your case, then I am sorry as I am out of ideas.
So far, so good. Got fed up with the PS on my phone and tried this today. The sensor is disabled as far as I can tell. THANKS!
It worked for me, thanks.
All sensors are Off
Thakyou for this fix.
Not even a single call drop since i installed but none of the sensors are working.
I don't want any sensors but just the Camera so please if u can make it work I'll be very thankful.
Currently I'm on 4.1.1 JRO03C
I tried it on JDQ39 (4.2.2) it disabled only the proximity but calls were still dropping.
If possible then please make a fix to disable all sensors on 4.2.2 except camera and sound.
Thanx again.
I've a gnex with installed custom rom( minco v5 4.1.2 )
I've tried your mod for proximity sensor fix and it worked but it disabled light sensor too. I've tried app on playstore but it does the same.
I really need to disable proximity sensor to get my phone working good, but i won't to disable light sensor. Can you help me?
thank's,
Daniele.
My sensor PLS
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4
ryza666 said:
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4
Click to expand...
Click to collapse
I've use PaXGeN's sensors modified by you 5pace and there are working on my CM 10.1 M3 ( on every kernel ). I think PaXGeN pack sensors will work on every single custom rom based on jb 4.2.2. My proximity sensor is disabled but everything else is working smooth. I've checked efficiency by Android Sensor Box. Thanks for this thread.
Hello guys,
in first - sorry for my bad english
I´ve got a Problem with my Note P-600 (WIFI Edition).
Last week ive rooted the Note with odin 3.09 and cf-Autoroot. (KNOX Warranty is now 0x1) and Ive installed Nova-Launcher and latest firmware.
I try to activate Multi-Window feature but no Sidebar is available. Same with the S-Pen Winow. I can draw the lines, but i dont get a new windows to choose an application.
I thought, if i deinstall the Nova-launcher, i will get back the feature. But nothing happend.
My next step was to make a full-wipe and flash the firmware new withoud odin.
Now ive got a "unrooted" system but the features Multi-Window and S-Pen Window ist also missing.
Does someone know how to fix it?
DaGreek said:
Hello guys,
in first - sorry for my bad english
I´ve got a Problem with my Note P-600 (WIFI Edition).
Last week ive rooted the Note with odin 3.09 and cf-Autoroot. (KNOX Warranty is now 0x1) and Ive installed Nova-Launcher and latest firmware.
I try to activate Multi-Window feature but no Sidebar is available. Same with the S-Pen Winow. I can draw the lines, but i dont get a new windows to choose an application.
I thought, if i deinstall the Nova-launcher, i will get back the feature. But nothing happend.
My next step was to make a full-wipe and flash the firmware new withoud odin.
Now ive got a "unrooted" system but the features Multi-Window and S-Pen Window ist also missing.
Does someone know how to fix it?
Click to expand...
Click to collapse
Press and hold the back button to get the Multi-window side bar. As for S Pen you have to hold it over the screen and press the button on the pen to get the air command to display so you can choose the pen window to activate an app by drawing a box.
nrage23 said:
Press and hold the back button to get the Multi-window side bar. As for S Pen you have to hold it over the screen and press the button on the pen to get the air command to display so you can choose the pen window to activate an app by drawing a box.
Click to expand...
Click to collapse
Sorry I've forget to wrote that I have try these commands. When I push the back-button for few seconds it happend nothing -,-
The air-command start every app but only the spen window does not...
Any other idea?
DaGreek said:
Sorry I've forget to wrote that I have try these commands. When I push the back-button for few seconds it happend nothing -,-
The air-command start every app but only the spen window does not...
Any other idea?
Click to expand...
Click to collapse
Sorry No idea then.
DaGreek said:
Does someone know how to fix it?
Click to expand...
Click to collapse
Not really because you already flash the stock firmware back.
But you can also disable the Multi Window:
Multi window: Settings : Devices : Multi window -> Switch
(Here you can also select the "Open in multi window view" option and try it by select a picture or music file within the "My files" app. Normally this should split the screen and open the image in the second window.
SPen window: Settings : Controls : S Pen (Not really something to disable or test it)
EDIT: You can also check in the Application Manager (via Settings) if you not disable something which is here important. Maybe enable everything to check it. And also you can try here to clean the cache and the default values for the corresponding apps (didn't know now which).
but i want do enable cause without multiwinod or spen-window i can work with 2 application at same time
i search for similar apps but dont find at yet a good once
Fixing Note 2014 resolved^_^
For note 2014 edition p600
First off Reinstall same software with Odin MEANING FLASH BACK TO 4.3 FACTORY SAMMY SITE + after flashing back reinstall CleanRom 1.2 its stable enough to re_pull the spen window commands plus muiti screen back after flashing new rom from the factory software. im assuming you know how to flash back right?
miyalovee said:
For note 2014 edition p600
First off Reinstall same software with Odin MEANING FLASH BACK TO 4.3 FACTORY SAMMY SITE + after flashing back reinstall CleanRom 1.2 its stable enough to re_pull the spen window commands plus muiti screen back after flashing new rom from the factory software. im assuming you know how to flash back right?
Click to expand...
Click to collapse
Thank u for solving my problem you've right this fixed the problem thumbs up!!
To XDA members ill be working on helping out for note 2014 , note 2 , in debricking galaxy s3s. inboxs problems in ill try to get your problems fixed:thumbup:
Sent from my SM-P600 using xda app-developers app
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.
Recently i've done a firmware change, after that, my phone began to behave weird, it seems like the touchscreen is uncalibrated or something like that, when i press somewhere my phone choose another:crying:
Elielnew said:
Recently i've done a firmware change, after that, my phone began to behave weird, it seems like the touchscreen is uncalibrated or something like that, when i press somewhere my phone choose another:crying:
Click to expand...
Click to collapse
Verify the firmware you installed is for your phone and verify md5.
If not, get the right stock tar, verify md5, flash in Odin and goto dialer and enter and select this with S-Pen for accuracy: *#2663# and then tap TSP FW update (General).
If unsure what happened, I'd suggest you redo all the steps anyway.
Sent from my SM-N910P using Tapatalk
You updated twrp. With the note edge recovery. Touch screens off by like a 1/4 inch right..... Flash right recovery and do above update firmware. It will fix it.
Sent from my 0x1 Note 4...... I love tep
kaos420 said:
You updated twrp. With the note edge recovery. Touch screens off by like a 1/4 inch right..... Flash right recovery and do above update firmware. It will fix it.
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
Please describe for action.
Kronk442190344 said:
Please describe for action.
Click to expand...
Click to collapse
Read the thread
Sent from my 0x1 Note 4...... I love tep
Last time this happened I had to dial a code to get into some settings. Can someone give me the directions again to realign the display for note 4 sprint?
floykoe said:
Last time this happened I had to dial a code to get into some settings. Can someone give me the directions again to realign the display for note 4 sprint?
Click to expand...
Click to collapse
Open dialer and use SPen to dial *#2663# Then tap the TSP FW update
(General) tab.
You may have flashed the wrong recovery to have that happen.
Might also have to flash stock tar in Odin and try again, if unsuccessful.
Sent from my SM-N920P using Tapatalk