I accidentaly flashed the edge version of twrp to my regular s6, 920r4. Now my touchscreen is reversed along the xaxis. When I dial *#2663#, nothing happens, only a dialtone goes on. Any suggestions?
Reflash regular S6 5.1.1 stock ROM via odin.
I did that, still no fix. Then I did a full reset, no fix.
Bring your S6 back to Samsung for repair.
roydok said:
Bring your S6 back to Samsung for repair.
Click to expand...
Click to collapse
Obviously my knox is tripped after flashing TWRP, would samsung be able to fix this anyway?
I hope so...
In other related threads, members were able to use the "secret codes" to update the TSP firmware. Could I perhaps install say the firmware for the 920F, then access the secret codes on that firmware, and in that process update the TSP firmware?
Flash this S6 regular S920R4 5.1.1 stock ROM instead of G920F:
http://www.sammobile.com/firmwares/download/48614/G920R4TYU2BOF7_G920R4USC2BOF7_USC/
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
This did not do anything for me. Could i just use the right one instead and all should go well? or there be another solution?
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse
I finally got this issue fixed after almost half a year. I updated the firmware to a newer version, using the software update on the phone. My issue is finally fixed. I think that perhaps the several months new software update was different enough to require a complete changing of the recovery software.
Or at least something like that!
No longer will I be using my old s4, running liquidsmooth, that restarts 3-4 times a day. With a shattered screen at that!
Resurrecting the Thread
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse
wolkowicz said:
Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Click to expand...
Click to collapse
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.
After rebooting my phone couple of times it works. Thanks!!!
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse
Ishmael89 said:
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.
Click to expand...
Click to collapse
wolkowicz said:
After rebooting my phone couple of times it works. Thanks!!!
Click to expand...
Click to collapse
No problem, glad it worked out and you can use your phone regularly now!
As I have found multiple threads for the same issue, I figured I would post the info in a few of them so if anyone else come looking for the issue and fix - they can get right to the howto instead of digging through multiple threads like I did. More info about the issue was found on the following link/s - https://1024kb.co.nz/galaxy-s6-reversed-touchscreen/ & https://forum.xda-developers.com/showpost.php?p=62289392&postcount=9
You DO not have to flash any stock roms or other versions of twrp to fix this, as it will NOT fix the issue, as near as I can tell something corrupted or changed the setting somewhere on the hidden section of the phone's firmware. All you need to do is access a hidden engineers menu, click on a button and your done.
The hidden adjustment setting is accessible through keypad *#2336# (reverse-entered as #*2114*) (you have to do this as the touchscreen is still reversed so you are unable to enter *#2336# normally). Once the task completed I then was able to press the back key and have it function as normal which confirmed the fix.
Related
Hi , I don't have an access to the hidden menu from the dialer on my galaxy S6 , so the command susch as *#06# and any other keys they don't work , so please I need a fix for that .
My Rom: XtreStoLite v1.1
thanks in advance
I don't have any hidden menus or service menus working either. Since I updated past the AODG firmware they stopped working. I'm on AOE4 now, still not working. Last one it worked with was AOCV for me. Not on a custom rom, on stock firmware.
mupet0000 said:
I don't have any hidden menus or service menus working either. Since I updated past the AODG firmware they stopped working. I'm on AOE4 now, still not working. Last one it worked with was AOCV for me. Not on a custom rom, on stock firmware.
Click to expand...
Click to collapse
if you find any solution to this , please let me know .
machhho said:
if you find any solution to this , please let me know .
Click to expand...
Click to collapse
I honestly don't think there is one. I even rooted the phone on the AODG fw and I couldn't launch the service menus at all even with root, kept getting this error (picture attached). I tried all sorts of ways, it just seems to be disabled.
mupet0000 said:
I honestly don't think there is one. I even rooted the phone on the AODG fw and I couldn't launch the service menus at all even with root, kept getting this error (picture attached). I tried all sorts of ways, it just seems to be disabled.
Click to expand...
Click to collapse
thanks for replying , but it should be a solution to this . hopefully a dev will look into this issue and solve it very soon .
mupet0000 said:
I don't have any hidden menus or service menus working either. Since I updated past the AODG firmware they stopped working. I'm on AOE4 now, still not working. Last one it worked with was AOCV for me. Not on a custom rom, on stock firmware.
Click to expand...
Click to collapse
can you tell me what Country of AODG firmware did you install because on mine it failed at the hidden.img so I had to odin the recovery to get phone booting . because to avoid the hidden.img fail you have to install an unbranded firmware so that's why I'm asking you this .
thanks in advance
Hello
I am having a hard time with my n920p since a few days.
All sensors are down. *#2663# gives a FAIL, updating the hub fails. MCU name: NG.
Flashing different roms nothing. Deleting cache data anything deletable.
21 sensors detected through cpuX. Though no data received.
Opened the bugger nothing visible. All Cables in place.
Read somewhere that reballing the MCU was the key. Though i don't want to mess with the electronics yet, because i still hope it's a software issue.
Any Thoughts?any ideas?
belkacemi_sa said:
Hello
I am having a hard time with my n920p since a few days.
All sensors are down. *#2663# gives a FAIL, updating the hub fails. MCU name: NG.
Flashing different roms nothing. Deleting cache data anything deletable.
21 sensors detected through cpuX. Though no data received.
Opened the bugger nothing visible. All Cables in place.
Read somewhere that reballing the MCU was the key. Though i don't want to mess with the electronics yet, because i still hope it's a software issue.
Any Thoughts?any ideas?
Click to expand...
Click to collapse
I am also having the same Issue and am almost certain that it was due to a ROM that I installed on the device that wrote over a key component of Samsung firmware. I have unrooted and gone back to my original stock 5.11 to no avail, I then upgraded to Marshmallow OTA with my fresh, unrooted factory firmware to no avail. I even went as far as installing multiple different versions of factory sprint firmware (closely following double install instructions) and I'm still stuck with an issue that I'm sure is only software related.
I am more than willing to do whatever it takes to get this problem fixed so if there is -anyone out there who has some insight please contact me back!!!!!!
So, I rooted my S7. It worked fine. One day, randomly out of no where it bootlooped (Google play services crashed. I restarted phone and it bootlooped. )
I have not made a single system modification other then rooting it. Didn't mod anything or mess with system files, and I had barely even been using the phone when it happened.
So I unrooted it (The phone still gave me the "Custom" symbol though) and Just now-- It randomly restarted. I didn't restart it. it just did it by itself. And it came into a bootloop. I don't understand why. What can I do to fix this?
MORE SPECIFICALLY: By Bootloop, I mean it stays on the T-Mobile screen and vibrates every minute or so and does not do anything (I even left it alone for ~ 30minutes and it never got past this screen)
Factory resetting the phone fix's it, but I don't want to factory reset my $400 phone every week! I don't understand how I could fix this either.
What method did you use to unroot? Did you flash stock firmware with odin?
sparky2029 said:
What method did you use to unroot? Did you flash stock firmware with odin?
Click to expand...
Click to collapse
All I did pretty much was flash stock s7 firmware. (More specifically boot.img)
Originally couldn't find a stock s7 image then I just used one I already had and it worked fine
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Just now noticed wat your problem is sorry for being late so yes to fix the bootloop refladh stock firm and when you go through all the root steps install xposed (yes it's possible it's insane on how they got it to work but it's possible I've done with my self)after getting xposed installed through flash fire go to xposed and get xtouchwiz something it's a blue gear install that And it will set your system status as official
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Here's a quick explanations of wat i think it is it's becuz you've ether heavenly been modding the phone or if your phone status is custom then that's the problem I had with mine after asking around someone gave me the fix i put it in the other comment hope this fixes your issue it worked for me 2 months of no bootloop I switched to 7.0 vzw beta so I lost root
Hello everyone, I am no expert but have installed Rom's for at least a year now. Mainly on my Note 3 but I just switched to my wife's SM-G920T — Galaxy S6. Late last night I was playing around with Kernels on DAMUZ+v4+EPH2 rom. Well one of the kernels has switched everything to be reversed and I can't find a cure. What I mean is in TWRP in order to install I have to hit the wipe button. If I hit wipe it will choose install, if I hit backup it chooses restore and visa versa. I have usually cured any problems in the pass by flashing Odin firmware to start over but it's not fixing the problem. Everything has to be opposite side of the screen to choose the correct choice. After flashing firmware G920TUVU5EPK5_TMB5EPK5_TMB_T-Mobile_USA_6.0.1 odin passes, it reboots and everything looks fine until the phone boots up. On setup of Wifi once again everything is reversed. I don't know what else to do, please any suggestion's are welcomed?
I found the solution by Google search, and someone else had the same issue. The fix for me was the exact same,
Update: Resolved by flashing the stock Marshmallow using Odin, then using *#2663# to reload the TSP firmware. This resolved the issue.
Hi, I have a bricked phone (Samsung Grand 2 SM-G710) it gets stuck in firmware update encountered an issue, I tried to flash it but when it finished, the booting logo appears with blue letters saying recovery booting, a few seconds pass and it returns to the firmware update screen .... I have tried different firmwares but same happens.
SABN said:
Hi, I have a bricked phone (Samsung Grand 2 SM-G710) it gets stuck in firmware update encountered an issue, I tried to flash it but when it finished, the booting logo appears with blue letters saying recovery booting, a few seconds pass and it returns to the firmware update screen .... I have tried different firmwares but same happens.
Click to expand...
Click to collapse
It's so called soft brick. Not as terrible as hard one. I suppose the problem is with dm-verify but I can't go deeper with it as I have no much experience with disabling it.
Also you say you were flashing the firmware but I'd suppose you rather talk about ROM. Because they are basically two different things. Firmware is like drivers in Windows, and ROM is the very operating system.
For now, I would advise you to flash Samsung stock ROM. Hopefully, you'll be able to use your phone while searching how to solve the issue with alternative ROMs.
LlamaQ said:
It's so called soft brick. Not as terrible as hard one. I suppose the problem is with dm-verify but I can't go deeper with it as I have no much experience with disabling it.
Also you say you were flashing the firmware but I'd suppose you rather talk about ROM. Because they are basically two different things. Firmware is like drivers in Windows, and ROM is the very operating system.
For now, I would advise you to flash Samsung stock ROM. Hopefully, you'll be able to use your phone while searching how to solve the issue with alternative ROMs.
Click to expand...
Click to collapse
well yeah, by firmware i mean the stock rom of the device, i tried with the two different versions that my baseband comes with, but nothing.
SABN said:
well yeah, by firmware i mean the stock rom of the device, i tried with the two different versions that my baseband comes with, but nothing.
Click to expand...
Click to collapse
i have tried different versions of odin, different basebands but i keep getting the same results
Per phone exactly ONE Stock ROM version exists, the version that was pre-installed by manufacturer.
jwoegerbauer said:
Per phone exactly ONE Stock ROM version exists, the version that was pre-installed by manufacturer.
Click to expand...
Click to collapse
been there done that, originally it comes with a rom released in 2014 and the other one that is newer released in 2015 try with both just in case but I'm still stuck , reading about it I'm starting to believe it's a hardware problem