I'm new to this forum and this is my 2nd attempt to get help to solve my problem. I have read ALL the rules posted in the XDA New User Guide - Getting Started On XDA, as well as all of the linked pages that are suggested to read before posting. It was very informative but I'm more confused then ever about the right place to seek help. This is all very overwhelming and I'm afraid I'm going to say something to offend someone or post in the wrong place and get in trouble, or worse, ignored. I suspect I did just that in my last post because I never got a response. I apologize in advance if I have done something wrong.
Ok, I'll do my best to explain my problem. I have an LG K20 Plus (I'll refer to this as my original phone) that I bought, brand new, from T-Mobile in May. In August I cracked the screen but continued to use it because besides the crack, it worked fine. By September the crack had worsened significantly and I decided to replace the outer glass as I had successfully done that with my older LG G3.
In that process, while trying to get that dreadful glue off, I scraped off some of the black stuff under the glue on the LCD which caused a white spot, about the size of a 1/2 dollar, on my screen. Although it was bothersome, the phone itself still worked fine. I continued to use it while I searched for the easiest way to fix it within my budget. After reading posts here and realizing it would work, I bought a used LG K20 Plus (I'll refer to this as my used phone) with a bad esn. The plan was to put my original logic board into the used phone and be on my way. That didn't happen.
When the used phone arrived, I turned it on to verify everything worked. I then put my original logic board into the used phone and turned it on. I saw my orignal wallpaper and was so happy I had my phone back. Then I tried to swipe to unlock and nothing happened. I booted it up a couple more times and still nothing. I connected a mouse via an OTG cable and verified that there were no more obvious issues with the phone except the digitizer. To confirm the dispaly wasn't faulty on the used phone, I put the used logic board back into the used phone it came with and booted it up. The digitizer was back to working again. I ran through as much as I could on a locked phone and the digitizer worked like new.
I, carefully, put my original logic board back into the used phone and, again, no touch capability. Again, I researched this problem to no avail. I realized I was way over my head and I decided to ask for help instead of making things worse by trying to fix it without knowing what I was doing. So, I put the phone in a drawer and asked for help here. That was a month ago. I know you are all very busy and, like I said earlier, I'm sure it's my fault and I messed up somewhere because my post didn't receive any replies.
I can't use my original phone because I have no touch ability and I can't use the used phone because it has an esn lock. At this point I decided to try and (I'm sure I'm using the wrong terminology here) flash the used phone and root it to bypass the bad esn lock. After researching that and seeing the word "illegal" A LOT, I decided I just didn't know if it was legal or not, so I decided to not take the risk of doing something that may get me into trouble.
At this point I decided I didn't have much to lose so I backed up my original phone and, with only the display of the used phone attached, I started the process of flashing it with TWRP and rooting it via this guide https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248 So, it is now successfully rooted but it still has no touch ability. The really weird thing is, while I was in TWRP Recovery mode, the touch ability worked again. But as soon as I rebooted the phone into regular mode, the digitizer stopped working again. I'm so confused and I don't even no where to start looking because I can't define the problem or the exact thing that is failing. I don't even know if it's hardware or software related.
So, I guess my question is, does anybody have any experience with this kind of problem you could share with me. I'd settle for someone being patient enough to explain to me exactly what is going on so I could research it better myself. Asking for help was not my first step. I have been looking and looking for 6 weeks now. I'm way out of my league with this stuff. It's really difficult to find a solution to a problem you don't quite understand. It's a little bit like being told to look up a word in the dictionary to find the spelling.
*LG K20 Plus
*LG-TP260
*T-Mobile
*Rooted
Baseband: MPSS.JO.
2.0c1.2-00012-8937_GENNS_PACK-1.85468.1
I think it's my original ROM
Kernel Version 3.18.31
I flashed TWRP
USB debugging enabled
OEM Lock Off
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
HelpNeededPlz said:
I'm so sorry but I have run into a few problems .. firstly, on my phone I have to use a mouse connected via OTG cable because I have no touch ability and my usb connection is set to "charge only". Apparently you can't change that until the phone is plugged in and obviously I need the mouse so I can't connect to computer. I downloaded an app called LogCatX and made a log file but I don't know how to attach a file and when I copy/paste it into the reply it says it is too long and reduce by 30000 characters. Any advice?
Click to expand...
Click to collapse
I think the new touch screen will need a calibration.
PS: i liked how you explained your problem
Sorry for my confusion but I'm not sure if you were telling me what I should do to figure out where the incompatibility issue may be or if you were asking me to upload the catlog so you could look at it and help me. I don't know what a catlog is, nor how to interpret it. At any rate, 6 hours later, I have, finally, figured out how to upload a file. :victory: I've been looking at how to fix a kernel incompatibility issue and I've read you can flash a custom kernel. If I did something like that, would that resolve my problem. Are they specific to the version of operating system your phone has (ie nougat, marshmallow etc) or do you need to use one for your specific phone model? Would flashing a custom ROM do the same thing? And is that model specific or OS specific? Where would I go to find something like that?
NOTE... In looking for differences in my phone to try and figure out where this kernel compatibility issue might be, I noticed that there are two different numbers on the midframe of my phones. I don't know if this means anything. I'm just trying to help someone help me.
zelendel said:
Here is what you do. Hook it up to a pc. Take a logcat and that will tell you what is failing. It sounds like a kernel compatibility issue.
Click to expand...
Click to collapse
Hello? Was this the extent of your help? I'm not sure if you were asking me to run a catlog to upload so you could help me figure out what was wrong or if you were just telling me what to do and then moving on. Because if it was the later, all you've done is piled more stuff on my steadily growing mound of confusion. To make matters worse, my posts is showing as getting a response, so, I fear, nobody else will look at it and I will be left in the same place as before. If someone happens upon this post, could you give me advice that will actually help me solve my problem, along with instructions on how to do whatever I need to do. Thank you in advance. Until then, I'll be anxiously awaiting your reply....
Related
So I tried everything in all the other threads and it's still a no go for me. This is extremely disappointing, I was really loving this thing.
I'm scared to even attempt going through Asus's terrible customer service, especially with my TF being rooted and all...
any advice on what I may be able to do?
what happens when you plug it in? Does charger get hot? Try leaving plugged into powered usb overnight.
I had an issue where I left my transformer a week ago plugged into the electricity, and when I came back home - it was out of battery and refused to turn on. I tried plugging into the computer directly but that didn't help either.
Today I went to best buy and plugged it into an adapter on display, and it started working..
When I came back home, I tried my cable again and it suddenly worked!
The moral of the story is it seems the power adaptors are quite flaky. Try to disconnect and connect again..
Also see this thread with some tips on fixing the power adaptor:
http://www.transformerforums.com/fo...er-no-longer-charges-wall-wart-adapter-4.html
I highly doubt the charger is the problem in my particular case because the dock seems to charge fine. Also, my TF died on my when it still had around 80% battery life.
Another thing is that my alarm clock that I have set up on my TF still goes off every morning and the only way for me to turn it off is by repeatedly pressing the power button (this is extremely annoying).
I'm assuming that the screen may have just completely died or something of that sort.
Do you guys have any other advice, or should I just go ahead and attempt to rma it?
thanks it advance
I had this same thing happen to my TF a few weeks ago. The solution for me was to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1185104
I used v6.3 for my US 8.6.5.9 rom version. This basic steps I took were to install the APX driver (steps in the thread above), then run the batch file and do 4, 5, & 6. I didn't see anything on my TF screen until the above was completed and then turning it on.
Hope this helps you.
starplaya93 said:
So I tried everything in all the other threads and it's still a no go for me. This is extremely disappointing, I was really loving this thing.
Click to expand...
Click to collapse
Have you tried buying it a few drinks and whispering complements about how beautiful and smart it is into it's microphone?
jmolhava said:
I had this same thing happen to my TF a few weeks ago. The solution for me was to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1185104
I used v6.3 for my US 8.6.5.9 rom version. This basic steps I took were to install the APX driver (steps in the thread above), then run the batch file and do 4, 5, & 6. I didn't see anything on my TF screen until the above was completed and then turning it on.
Hope this helps you.
Click to expand...
Click to collapse
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
Bump /:
10char
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
I am very interrested in this thread as I have the very same problem.
Asus proposed to RMA it but I fear that they might find some trace of the previous root as I unrooted "blindly"
blabox said:
I am very interrested in this thread as I have the very same problem.
Asus proposed to RMA it but I fear that they might find some trace of the previous root as I unrooted "blindly"
Click to expand...
Click to collapse
yeah, that is what i'm worried about as well.
What number did you contact for the RMA?
Well apparently my only option is to RMA the device.
I went ahead and un-rooted it with the BRK toolkit, however after un-rooting it said that I have to load a stock rom and recovery image onto it. How do I go about doing this without turning it on and flashing the zip in recovery?
Do you all think ASUS will even notice it is rooted and if so what steps should I take to ensure that there is no proof of root?
Please help me a bit on this one guys.
I had the same issue with mine last week. Appeare dead but would connect to PC APX mode and could view SD card contents.
When looking at the screen with a flashlight, the text was visible. The unit was actually working but the backlight had died.
Had to get it replaced with new one from place I bought it from on their product replacement scheme. great except its a new one that can't be rooted yet.
Sitting patiently for that to be released so I can go back to playing....
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
Yes, my TF was rooted and running a custom ROM. When running the batch file that is in the package in the other thread I referenced, I did steps 4, 5, and 6. Then rebooted and it was fine. If you can get the APX driver installed and your computer will recognize it, then try those steps using the tool. Once I rebooted, it just loaded my same ROM as if nothing had happened.
Of course a hardware failure would cause the same thing (backlight or LCD not working, etc...) but in my case it was a software or booting issue and the above fixed it. If you try what I did and still nothing then RMA is probably your only option.
i had this problem too, in my case it was a defective power button. had to push it real hard to get the pad turned on ... rma fixed it ....
i have the same problem also and it turned out to be the power button my solution was just to keep pressing it haha and then it worked strangely enough. ive read somewhere that it it gets misalligned somehow. i guess i have 2 options either send it back or fix it myself at the moment im just living with it.
it works somedays then otherdays it takes a few pushes lol
My case seems to be none of the above.
I tried checking if it was an issue with the back light and put a flashlight up to it in a pitch black dark room but I can't see anything on the screen whats so ever, regardless of the angle I put it in.
I also don't think it is the power button because like I said, i'm able to put he tablet in APX mode and take it out of APX mode as well at will by pressing the power and volume up button.
Thirdly, I tried the root kit several times (version 7) and while it's doing it's job of rooting and un-rooting my TF, there still is no change in the functionality of the screen.
so i'm pretty much sol. I already placed in an RMA to asus, now I just have to ship it off (asus has by far the worst customer service that I have ever seen).
My final question would be is there anyway to load a stock rom and recovery image without being able to turn the tablet on? I'm able to unroot it with the rootkit, but it says that I still need to load a stock rom and whatnot.
If somebody can point me towards directions as to how I go about doing this, that would be great.
Thanks for all the help guys.
Hi everyone,
I'm experiencing really wierd behaviour with my HTC Desire S. I'll try to tell the story as it happened, so you may have the best grasp on what's happening to me. Here's the thing: yesterday, I charged my HTC on the wall plug as almost every night (y'all know how it is with smartphones, always needing to be charged ). When I unplugged it on the morining, the green LED stayed on. Not cool. I can't really remember if it was turned on and stuck or already turned off at that time, but I had to reboot the phone. Okay, that can happen, phones have to reboot sometimes.
And then, it did not boot. Instead, it was stuck on the bootscreen. I looked around on the internets, but people seemed to have boot loops or devices stuck after the "quietly briliant" part. Actually, mine was stuck before that part. It didn't even play the funny sound and show the fancy animation: it was stuck on the blank screen with only the HTC logo.
I tried many things, like praying pagan gods and removing the battery, let it cool for a while, boot and wait to see what happens for more than 30 minutes, boot it while plugged on the wall plug... I think I was about to get to the "I'll have to make a factory reset, then" line when I tried to see what dmesg would tell me if I plugged the phone on my computer. Note to self: always try to plug to computer. It did boot completely. The victory dance was almost completed when I was invited to enter my PIN code. My touchscreen did not respond. Damn.
So I had to reboot. Again had to remove the battery (I don't like that, but what choice do I have?). Now it always boots completely (that's a good start), but my touch screen seems completely unresponsive. I can't access anything, can't enter my PIN code or unlock the phone when there's no SIM.
That's where this forum comes in: I've not given up. You see, my phone has USB debugging activated (yeah I know, the thread's title spoiled all the story). I'm pretty sure this means adb can help me in some way to troubleshoot my device. adb shell gives a nice UNIX-like shell, yay, that is relevant to my interests.
My phone has never been rooted. I've looked into it (that's why USB debuging was activated), but I wasn't 100% confident it would work, so I gave up before ending up bricking my phone (duh, too late, haha). It's running the last Gingerbread version distributed by HTC in Belgium (2.3.5, I think, without any certainty), with the last Sense version related (could it be 3.0.3?).
tl;dr: Unrooted phone with unresponsive touch screen, debugging mode enabled, trying to find what's wrong.
So here's what I'd like to know: is there any way to try to force start my touch screen with the help of adb? Where's the related log, the one that should display the error(s) that occur(s)? Should Bill Murray play in the next Batman? If root is needed, do I have a way to use a temproot exploit in order to fix my phone once and for all?
Any attempt to help will be greatly appreciated. This is my first post here, I hope it's clear enough, and not too nooby for you guys. Also, that I didn't break any rule (I watched/lauged at that video about noobs to xda). Btw, I'm quite confortable with UNIX shells, so don't avoid cli-related answers if that may happen to be helpful. Also, I'm not at home right now, but I'll follow this thread with a lot of interest anyways. I'm back on a regular connection next sunday.
Have a nice day! And sorry for the long post (but believe me, I'm even more sorry to admit I can't investigate further on my own, now that is frustrating).
Okay, I'm back.
It makes no sense. I let my phone on for a few days, then suddenly, probably out of boredom removed the battery, put it back and rebooted. I distractingly tried to unlock it… and it worked.
I have absolutely no single clue on what happened. And I'm still quite concerned, because this means it can happen again without any warning.
I'm gonna give a shot at HTC's support in order to ask them what I can do to locate the problem if there are traces. I'd really, really like to read all the logs (and logcat didn't show anything interesting).
If anyone has a suggestion, feel free to shoot it. I'll try to keep this thread updated in case someone has the same problem.
Duh, just got an anwser from HTC's support. Totally useless, they told me to try to reboot in Safe Mode in order to see if the problem happens again. Well, even in normal mode it has not failed for two days. GJ, guys.
I'm really willing to meddle in my system in order to see what could have gone wrong. I'd especially like to see if there is any way to see whether there are HW faults or not, since I'm suspecting a temporary TS chip failure, which can happen again at any moment. I'll be reading some documentation about Android's system and its logs.
Yeah, I know I'm talking a lot alone, but if someone ever has the same problem, he might be able to see what I've gone through, so I'm documenting as much as possible. =)
adb bugreport
I'm fixing an infuse for a friend who needed the screen replaced simple enough job so I thought as I repair phones and electronics as kind of a hobby. However the replacement screen isn't responding to any kind of touch at all. It displays the puzzle piece lock screen and everything else even shows there's been some missed calls ect. yet will not respond to any kind of touch. I think it's a calibration issue but I can't get passed the lock screen so there's no way to change the setting. Honestly I'm most worried about all the media on the phone most (pics, videos, contacts, ect )
If there is a way I can retrieve that off the internal storage I'll feel better about taking drastic measures. Other things I've noticed is an unusualy long boot up time hanging at the white Samsung letters but this is the first time I've dealt with an infuse so I'm not to sure on that.
Any advice is appreciated.
Thanks,
s1im
There are different versions of screens or maybe it was revisions. At least for the LCD +digitizer assembly. Rev.6.1 and 6.2 and 6.3 if I remember correctly.
Edit....here is a link for reference, also two of the screens were interchangeable but not all three. Sorry I don't remember which ones.
http://item.mobileweb.ebay.com/viewitem?itemId=180914982430&siteId=0&isClassified=false
Edit....my statement regarding interchangeability may not be true. The screen I bought could be used as a replacement for two of the rev numbers. That could mean that it is backward compatible but the other one isn't forward compatible.
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
s1imch4anc3 said:
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
Click to expand...
Click to collapse
Correct mine had a sticker on it.
Bummer I have no idea what kind of screen she had I threw it away as a jumbled mess is there any other way to find out what screen it was... either way thanks for the replies
Wish I could answer that, but here is another screenshot. It shows one for 6.0/6.1 and another for 6.2 so my original numbers were off. Did the new one say what it is?
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
s1imch4anc3 said:
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
Click to expand...
Click to collapse
Just guessing but maybe adb. You could try to edit the title of your thread or start a new one about this question.
Edit..I have an idea but first a few questions , is this phone stock, and would you be comfortable flashing a kernel if it is? This will give you CWM recovery which has mount USB storage as an option in it. All this can be done with the physical buttons, power and volumes.
I found something that may work without having to make software modifications so I'm going to try that first and if not I'll get back to you...
To answer your questions tho the phone is stock and I've rooted /flashed a couple phones with no problems before so I'm OK with giving it a try
Again I'd like to thank you for your continuous help
You should be able to pull everything you need with adb...but the problem is, is adv enabled? And can you pull a whole directory? I doubt you know individual file names for each media file, not to mention that would be a long tedious process as there are likely well over a 100 if not in the 1000s of music/pics/vids
Well..looks like you can pull a whole.directory (sdcard)
this thread may help http://forum.xda-developers.com/showthread.php?t=744454
Btw...you don't have to be rooted to adv pull
Sent from my HTC PH39100 using Tapatalk 2
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
s1imch4anc3 said:
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
Click to expand...
Click to collapse
ADB was the first thing I thought of, but flashing a kernel with custom recovery in Odin should allow you to get into USB storage. I am not familiar with the stock recovery but you could see what options are there. I believe it would be from device powered off hold volume up+volume down+ power buttons then release power at Samsung screen.
Were you able to resolve the screen issue with the different version? I am having the same problem.
Hi guys, I'm sincerely apologizing if this is the wrong place to open a thread about something like that, I couldn't figure out where else to write down my issue. I've been told here are people that know the most about devices and that someone might be able to solve an issue I got with my Samsung s6 Edge. The samsung support has been not helpful at all and it's either sending it to them to repair it and loose all my files or at least before doing that at least trying to save some of my personal files. The problem yet is that I can't even get into my phone. I was charging it at night and suddenly I saw a flashing Samsung Logo on screen with a blue LED that flashes as well. So the device had to be turned itself off and then it was restarting but it couldn't get pass the 2nd SAMSUNG loading Screen and got stuck. That's all. From then on I wasn't able to do anything with it. First I thought it may be making some updates, but then again I turned off my wifi before going to sleep. So that can't be the case. I waited hours, because I was hoping it might get pass it at some point but it didn't. While waiting I looked up tutorial to fix it but nothing seemed to work out and then I called the samsung support which basically just told me to turn it on and off without any real solving advice. So here I am. desperate to just save up the last photos and that's it. Does anyone know a solution that won't mess with my guarantee.
Again, I'm really sorry if this isn't the right place to ask.
Thanks for reading if you made it up to here,
Erika
EriBerry said:
Hi guys, I'm sincerely apologizing if this is the wrong place to open a thread about something like that, I couldn't figure out where else to write down my issue. I've been told here are people that know the most about devices and that someone might be able to solve an issue I got with my Samsung s6 Edge. The samsung support has been not helpful at all and it's either sending it to them to repair it and loose all my files or at least before doing that at least trying to save some of my personal files. The problem yet is that I can't even get into my phone. I was charging it at night and suddenly I saw a flashing Samsung Logo on screen with a blue LED that flashes as well. So the device had to be turned itself off and then it was restarting but it couldn't get pass the 2nd SAMSUNG loading Screen and got stuck. That's all. From then on I wasn't able to do anything with it. First I thought it may be making some updates, but then again I turned off my wifi before going to sleep. So that can't be the case. I waited hours, because I was hoping it might get pass it at some point but it didn't. While waiting I looked up tutorial to fix it but nothing seemed to work out and then I called the samsung support which basically just told me to turn it on and off without any real solving advice. So here I am. desperate to just save up the last photos and that's it. Does anyone know a solution that won't mess with my guarantee.
Again, I'm really sorry if this isn't the right place to ask.
Thanks for reading if you made it up to here,
Erika
Click to expand...
Click to collapse
You may get more help by getting the thread moved to Galaxy S6 Edge Q&A, Help & Troubleshooting.
To do so, simply click the "report button" and select "thread/post moving".
Now, on with the issue. What you're having seems to be a bootloop.
One thing you could try is booting into recovery and wiping the cache.
I'm not exactly sure how booting to recovery works on the S6, but it generally is: turn the phone off, then hold the power button + volume up button until the phone vibrates. If that doesn't work, try adding the home button to that combo, or just Google how to boot into recovery.
Anyway, if that doesn't work, then I'm afraid there won't be any other solution than reinstalling the firmware yourself or sending it to warranty (where they will probably reinstall the firmware).
Your photos shouldn't be affected in the process, as they are saved on the internal memory and, unless somebody wipes it, you shouldn't lose your files.
But you will definitely lose your apps and app data in the process.
Flashing the firmware yourself should not void the warranty.
The process can be done with Odin (a software also used by Samsung). I'm not sure how familiar you are with flashing, but you may want to do some reading or watch video guides on the subject of using Odin. Since the S6 is pretty much a new device, I'm sure you will find lots of video tutorials for the S6 specifically.
And, as I said, your internal storage stuff should be safe too.
This is now my 3rd attempt to find a solution to my problem. My first attempt went unanswered, and although my last attempt got a response, it didn't help me one bit. Unfortunately, I didn't gt a response to my folow up questions either. So, this is going to be a much shorter explanation of my issue. (Previous post has a detailed explanation).
I bought a LG K20 Plus brand new in May. I broke the screen and decided to just buy the same phone and put my logic board into. The problem is, when I did that, the digitizer fails to recognize any touches. Strangely, the digitizer, again, works while booted into TWRP recovery but fails again after normal reboot. I'm so frustrated. I got really excited when my previous post got a response. It was such a huge disappointment to realize that I wasn't going to get the help that would lead to fixing my phone. After over a month and, at this point, my hope was non existent, I decided to just seperate the glass from the lcd and then put the glass on my broken phone. But in looking at it again, I don't see what difference the display makes. I really dont want to risk breaking another didplay. I don't know, it's apparent that I just don't get it. So, here i am again, asking for help. Will someone please tell me what I'm missing. Also, if you have advice please list more then a one sentence solution. I'll need some direction.
NOTE: I'm currently using a mouse via OTG cable and cannot change USB connection from "charge only" to mtp. So connecting to a PC isn't possible for more then charging.
Boot into fastboot and unlock the bootloader. Probably won't help, but why the hell not, right?
Sent from my [device_name] using XDA-Developers Legacy app