Hello XDA forum! I am new here but I have enjoyed reading through many of the great posts you have available. I have a problem and I'm hoping you can help me. I'm learning quite a bit about the android OS and dabble in some minor tablet repairs but I still consider myself a noob, especially after reading some of the more technical posts! I have a couple of tablets here that are locked up after too many pattern attempts and I'd like to do a factory reset, but I just can't seem to get them into recovery mode. All the normal keystrokes yield no results. For example:
Tablet 1 is a 7" Noria by Chromo that identifies by my computer MID-X15. It's recognized in device manager as being installed with correct drivers. To the best of my knowledge USB debugging is not activated as I have tried both Multi Tools and platform-tools adb, while the device is not shown on either program. I have also tried numerous different key combinations from a powered-down state (vol - & vol + with power, just vol + and power, just vol - and power, and repeatedly pressing different combinations both at and before the manufacturer splash screen). The internet has proven to be less than helpful as I'm on my 3rd hour of forum surfing. I have never flashed a tablet before and I'm not precisely sure if can be done without USB debugging on or without being able to access the system. I am perfectly willing to purchase a TF card and attempt the process but there's not a ton of information about this relatively obscure little tablet.
Tablet 2 is a Klu by Kurtis. It is also a 7" tablet and I have the same problems with the USB debugging being off. On this device I can get into the screen with the android on his back with the red exclamation mark, but the recovery console never starts. Numerous hours of surfing and countless attempts at alternate keystrokes have also yielded no results.
If someone would be so kind as to offer a few suggestions or point me in the correct direction I would seriously appreciate it. Thank you so much!
(close to) 24 hour bump. Hopefully someone may have a suggestion for me. Thanks in advance!
One more bump. Anyone?
Unfortunately, after researching both tabs, I have found that neither tablet is very good quality.
Chromo Noria - This is a very well-known tablet to be problematic for no reason at all, and once this problem occurs, nobody has discovered how to retrieve the system.
Curtis KLU - This also is not the greatest tablet ever. Fortunately, I've found this thread for you to take a look at - it contains instructions on how to boot ClockworkMod.
Hope this helps.
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
[email protected] said:
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
Click to expand...
Click to collapse
I can see that. It's always fun to be aggressive every once in a while.
Don't we all wish that there was a hardware method to factory restore our devices? :laugh:
Am I right?
I too have been tinkering with a chromo noria 7" tablet in my spare time, as my son got one of these last christmas and its been stuck in a boot loop for no reason for almost six months now. Today I decided to play and discovered that adb could see it while it was boot looping and tried adb reboot recovery command and to my surprise it booted the recovery menu. That being said, does anyone know what I can flash from there cuz a wipe/factory reset does not fix the loop. Any advice would be happily welcome and im sorry if I'm posting wrong in any way. Hope at least my findings are helpful.
Sent from my Moto G using XDA Free mobile app
Related
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
Hi people,
I'm just looking for a bit of friendly advice really. I know there are similar threads about both of my separate issues but I just want a bit of help weighing up my options.
I've been enjoying my used TF300T ('unwanted gift') for about 6 months and had CM10 running on it. I have had (very) intermittent problems with the touch screen of the type I've seen described on the forum, where it will lose touch input completely but will come back on if you reboot it or turn the screen off/on etc. This has probably happened about 10 times in 6 months, and never persisted beyond a reboot.
Last week, whilst I was away from home and perhaps less inclined to do the proper forum-trawling, I had the problem reoccur but it was persistent. No touch input at all. Perfectly functional within the dock though. I figured the first thing I would try was a factory reset. I booted recovery only to realise that I had the lovely TWRP touch recovery installed and couldn't use it. At this point, I decided that this was very probably a hardware issue if touch didn't work in the recovery or the main OS (though there may be things I don't know that still muddy the water here??).
I opened it up to have a look if there were any cables needed securing etc. At this point, I realised I was definitely on my own because the 'Warranty void...' sticker had already been broken ('Unwanted gift', eh?). I played with the cable a bit and could get it to behave differently but only succeeded in getting 'ghost' input allover the place. I figured that at least it was receiving some input now and crossed my fingers that a factory reset would 'recalibrate' it in some way.
In desperation and not wanting to pay too much in roaming data on my phone, I didn't come here and do the reading I should have done. I just installed CWM recovery and used that to do a factory reset (It's not compatible, it hung, I powered it off and now I've killed my bootloader. No recovery, no fastboot, only APX. I've now read this scenario a number of times on the forum :crying. So, with my excuses made and story told, my questions are as follows:
1) Am I correct in saying this brick is unrecoverable at the minute? (I didn't create the blob.bin I need to use wheelie and get nvflash access. This blob.bin is device specific and I can't unpack it from a cm10 or ASUS download? I think I probably only need to reflash the bootloader, so might not need bricksafe.img??)
2) If I were to have ASUS reflash this, I believe it comes in somewhere below $100 and could be worthwhile if the touch problem is a software one.. Do you think the touch problem is hardware or software?
3) If the screen is a hardware problem, can anyone tell me which part I might need to replace?
4) If it needs reflashing and a part replaced (either by me or an ASUS engineer), should I really be looking at selling this for parts and getting a new one economically speaking? Are any of the parts I have actually useful to anyone?!
Many thanks for reading a long and complicated post. If it cheers you up, the garage also told me my car isn't worth repairing this week!
I believe that you have a hard brick.
Asus can fix it but they normally just replace the motherboard and charge in the region of $250 for this service.
Your device will come back locked and you a lot of people have found the unlock tool no longer works. Probably due to serial not matching MB.
Best option is sell individual working parts on eBay whilst they have some value and you might get $200+ back. Or sell the unit as faulty for $100+
Sorry for the bad news.
Thanks for the input, sbdags. In terms of selling the parts individually, is it just really the screen and digitizer that have any value? ..and the dock, I guess.
asus service have tools to unlock force recovery mode and reflash it but it is easy to said us motherboard replacement to get to much money lol
Been a watcher on the forums for awhile, now I actually had to sign up and get some help, LOL.
Anyway, dropped my s2 skyrocket, noticed that it kept trying to reboot every now and then when I used it the same day. The next day, I plugged it in in the evening, and shut off, rebooted, but the screen would go black and the phone would vibrate with 2 seconds in between vibrations. It gets to the "Samsung" word, then the screen goes black in the style of an old tube TV (with the thin white line at the end). Then the vibrations start. So far a useless phone. Took it apart and checked connections carefully (I'm used to working with processor boards quite a bit).
What do you guys suggest? Damaged memory? Should I attempt to reflash? Stuck power button (seemed ok, though)? Bad screen?
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
creepyncrawly said:
Well, probably some kind of physical damage, but hard to say. Anyway, you posted in the forum for SGH-I777 but you have the SGH-I727, so I would suggest that you look in the correct forum.
Click to expand...
Click to collapse
Oh, thanks for the heads up. Yeah I just figured out that the i727 isn't in "Top Devices" or "Legacy," so you have to go to all forums. Ugg. Already moved. Thanks to whoever notified mod.
Anyway, yeah, any help would be AWESOME. What physical damage would prevent booting past the "Samsung" screen and default to a black screen that intermittently vibrates?
I'll be honest, if ur asking that question probably something u don't have the current skill set to fix. Try to Odin back stock, but if it started post-drop you may be SOL and in need of a new phone.
Got it into download mode after multiple failed attempts. Each time I would get it into download mode, the screen would shut off after about 5 seconds of being on. I tried several combinations of plugging it in first, then installing the battery, or holding down the button while I plugged it in with no battery, etc. I had just given up after getting it into download mode briefly for the 20th time, when I gave it one more go while rocking the on and off button. Technically that is recovery mode, but I let off right before plugging the phone in and it hit download mode and stuck.
So what I am thinking is the power button got jammed internally. I have heard of it happening on other forums. Even though it looks good and clicks upon external examination, the pressure circuit on the inside might be in contact. Anyway, just one theory.
For future though, I did discover that you don't HAVE to have the USB unplugged prior to getting into download mode. On the contrary, a power source must be present in order to register that the keys are pressed PRIOR to initiating USB input. Thus, you can actually remove the battery, plug in the USB (power source), then hold the volume keys while replacing the battery. Goes into download mode that way, too.
Will keep you guys updated. Might need a bit more help if the phone starts acting up again.
At this point, if the Download mode still holds ok, should I consider CyanogenMod, or is it easier to get back a good ROM from stock?
icenight:
Thanks for the reply. I don't understand much about smart phones or how they work, but trust me when I say I have had AMPLE experience with electronics, circuit boards, hardware, etc., particularly in the computer/laptop world. I code quite a bit of websites, and understand almost all things networking and OS. Just never really got into it with the phones.
Getting super excited to see the sheer amount of modding you can do though. Would love to break into a hardware modding world if it ever comes available. That's where it's at with electronics for me.
Well glad u got it sorted, lucky guy you are lol.
As for boards and the like, if it didn't work I would've suggested replacing the motherboard and/or power daughter board. But for a skyrocket may not be worth the money.
Since you're a hardware guy, maybe mess around with the phone and JTAG? Finding a way to unbrick without it would be very helpful
Since the problems started after a physical damage (fall) , I wonder how would Odin or wipe and flash might work !
Definitely a hardware damage...
Yeah, it kinda puzzled me, too. I believe the power button might have been internally stuck, but that's just one idea. Could have been a loose connection, too.
Can you lose some solid state memory with firmware on it, but the SS memory still be OK to right another copy on?
More than likely it was your power button
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
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....