Hi everyone!
I've got a question for you all about my Samsung Galaxy + (GT19001) is acting rather weirdly. I'm no native speaker of English and I'm not familiar with the terminology (since I'm a noob and don't really understand computer thingeys) so I'd like the answer of a few experts before I lose my temper and buy a new phone all together.
Here's the thing. A few weeks ago, I got this phone from my father. He's too old for this technology, he didn't understand it. Hence, I took it from him. But... A few hours ago, I dropped it.
yes... I dropped it. The phone looked fine, I booted the system again, I received a connection to the internet and I got a connection with my sim card, so all seemed fine. BUT; later this evening I wanted to find something on the internet and I noticed this rather strange behaviour. I wouldn't say that my phone is in a loop, but this is what happened:
- the touch screen became really anxious and in the half of the time just touching the screen may result in making pictures. (....?)
- If that isn't annoying enough, the phone works just fine, as long as you touch the screen. So, what happens is that the phone makes a lot of pictures and when you let go, the phone returns to the start screen. That doesn't mean that the phone is rebooting, but it means that it returns to the first screen (on the same wall you'd also place your widgets and maps and stuff). This doesn't make any sense. I reasoned that it was due to a bug and I decided to reboot the whole system. Didn't work. Nextly, I can't get any access to Samsung Kies or Samsung Odin because "the server is unavailable 4100".
It's a real nuisance because currently we don't have any internet connection (because the connection from the provider broke down during a storm >>>>), but as you see, I'm still able to connect my laptop via USB to my phone and I can still access the internet. I don't get it.
So, there are two things I'd like to know. What's going on? Is this failure the result of me dropping the phone? And if this isn't the case, how on earth do I fix it?
Thanks for your answers
Well I don't think it's related to dropping your phone because if it were then why all of this is happening now, it should have been happened earlier. Could be because of a malware. A soft reset will do the work.
It seems to be slightly damaged by dropping.
Send it to Samsung service and they will fix it for you.
truicentrum said:
- the touch screen became really anxious and in the half of the time just touching the screen may result in making pictures. (....?)
So, there are two things I'd like to know. What's going on? Is this failure the result of me dropping the phone? And if this isn't the case, how on earth do I fix it?
Thanks for your answers
Click to expand...
Click to collapse
Basically this should have been posted in the i9001 Q&A here, as there was a BUG in some Roms in i9001 that caused such behavior for which there is a patch, to resolve
sorry my memory is running out: due to age. try asking there for correct response.
Check this out! Links to useful Guides and " Banned " Documentaries
Related
I just got my Diamond back from repairs and wanted to compare experiences:
1)
I first bought a Diamond two months ago. It came with 1.37 ROM series on it, the screen wasn't too yellowish, but touch function wasn't responsive and the GPS was a MESS!
(of course, I tried many ROMs official and unofficial, almost every Radio ROM and various Hard-SPL. None of that fixed the problems.)
I could cope with with the other flaws, but I just couldn't bear my GPS wasn't getting a fix, no matter how much sattelits were in view...
It worked at first, but soon started to display '66666' instead of the location and finally, it would never display any location again.
I tried every tips and tricks and softs, it helped giving me more and more satellits in view and apparently active, but at the end my crappy GPS could never turn the datas received into a proper location...
2)
I sent my device back to warranty (after flashing back to official ROM and SPL) and had to wait for about a month.
(the technician at first tought I was just a noob unable to set his phone properly, but after two days of attempts, he had to admit that there was something wrong with my phone and sent it to the the headquarter for replacement of motherboard and so on.
3)
The new phone I got came directly with 1.93 ROM and a little bit more yellowish screen, though, there is no spot or stain on it. So the coulour doesnt bother me.
But from the beginning I noticed the new phone was much more responsive even at the slightest touch.
From the first try, the GPS got a fix in about 1 mn time, with only 3-4 satelits in view.
I installed Hard-SPL and the latest Australian Official ROM, and though the screen seems now a little less responsive than before, the GPS is still working, fine.
I'm a VERY happy user of Diamond now, but I'm still wondering one thing:
it looks like once the warranty technicians understood that I was very demanding about quality and complete functions, they took time but gave me a phone totally different in terms of behaviour and quality of the components sensitivity of screen, GPS etc.
Is there some bad production series that they never tells publicly about, and much more better series that they give you as a replacement once they understand you will bother them until the end of time if you are not satsified?
Plz tell your experience about having received two new diamonds with totally different behaviour and quality of the components.
I guess you are totally right!!!
My first device was pealing paint in the aluminium frame on the second day, work very good by the way.
Now i´m on the second device and i my hardware keys, especially the call button is sometimes irresponsive and i have to push it several times to enter the dial.
Tried cooked rooms as well, and the call button issue still remains, so i´m a little unhappy with my diamond experience.
I've noticed that whenever i turn on my display after having left the diamond unused for sometime the lcd doesn't switch on smoothly, what i mean is that it first displays a grey pattern(only for a ms or so) and then the desktop( lcd off>>grey flash>>desktop). Usually the transition from off to desktop is quite smooth, but in my case its not!
Is this a s/w issue or h/w ?
I've never experienced that particular problem myself, but sounds like H/W problem to me...
just been through a couple of other threads related to the grey screen of death...i've had it once...it happened while i ended a call, had to soft reset to resolve it.
take a look at the grey screen of death i'm talking about
Pretty scary indeed!
It might not be a coincidence that you experienced both: grey transition when switching on the screen and once, the grey screen of death after a call...
Two different effects of the same defective part in your H/W?
a solution!, almost
untill now i've had auto brightness control switched off and the brightness was set to minimum to save battery life, but now i just tried switching on auto adjust backlight and the problem seems to have vanished.....coming out of standby is smooth as ever!
although i've to say that i don't quite understand the logic behind it.
*EDIT*
it doesn't help for long
blufade said:
a solution!, almost
*EDIT*
it doesn't help for long
Click to expand...
Click to collapse
This is what I was worrying about...
Your method sounded like a work around to avoid the display failure. But as a matter of fact, there must be a reason for the display to fail. (bad screen, power supply or something...)
By the way, I'm more and more convinced about my assumption that there are bad production series and better ones:
Today I had my device connected to my PC through USB for a couple of hours. In the meantime, I was downloading and deleting messages, watching google video on opera, after that I used wifi etc.
In this situation, my first Diamond would have got hot like hell and my hand could barely stand the pain...
Since many people were complaining about over-heat problems, I thought that was a common problem with Diamond.
But the new one did not get that hot. Just a little over-warmed, but definitely not too hot. From that phenomenon, I can see what I felt about a better touch-flow behaviour, a better GPS and so on is a part of a whole:
I was first sold a ****ty phone, and now I finally got a proper Diamond!
People with bad series, you don't have to cope with all those troubles, ask for a replacement phone!
my diamond gets heated up quite a bit at times....but i dont fully uderstand what exactly is the cause.....i've had experiences with the diamond getting pretty hot while using wifi & or gps and on another occasion i was watching a DVDRIP via wifi(@ full power) using core player and also with gps cycle running in the backgroud, still the diamond stayed well within reasonable limits.
i think it has to be a software problem, possibly the radio s/w
would you mind sharing the radio version of your diamond?
As written in my signature, I'm using the 1.00.25 which is included in all latest official ROMs.
By the way, I hope you did not cast a spell on me! (just kidding)
Today I experienced my first grey screen!!!
My Diamond was connected to the PC through USB cable, downloading e-mails, and I got a phone call. When I hung the phone, It suddainly happened, for the first time in my Diamond user carreer!
Just for one second, looking like an old black and white TV screen trying to tune on channels.
Hope that was the first and last time. In ordinary calls, (without being synchronized to the PC at the same time, it never happened so far...
sorry to hear that my friend
My Diamond was connected to the PC through USB cable, downloading e-mails, and I got a phone call. When I hung the phone, It suddainly happened, for the first time in my Diamond user carreer!
Click to expand...
Click to collapse
I'd the same experience except for the fact that my diamond wasn't connected to a PC.
I hard reseted my diamond yesterday, but the grey splash while i turn on the display from standby(post 3) still exists ( ......i don't suppose its a software problem anymore.
blufade said:
i don't suppose its a software problem anymore.
Click to expand...
Click to collapse
Why not trying to send it back to the seller and get a new one?
This problem is easy to demonstrate to the technicians, and I don't think they will be cheeky enough to say that's a normal phenomenon!
This problem is easy to demonstrate to the technicians, and I don't think they will be cheeky enough to say that's a normal phenomenon!
Click to expand...
Click to collapse
not that easy.....the thing is that if we turn on & off the lcd without a gap of atleast 4-5 min(dono exactly) i dont see that grey splash
i think im going to wait another 3-4 months before i approach for warranty.
I had that "gray splash" problem with my Kaiser and Diamond.
Hard reset also didn't work like above. For both devices the fix was simply flashing to a different (cooked) ROM.
As mentioned in another thread, the grey screen problem was fixed (as least for me when I flashed to dutty's rom)
blufade said:
not that easy.....the thing is that if we turn on & off the lcd without a gap of atleast 4-5 min(dono exactly) i dont see that grey splash
i think im going to wait another 3-4 months before i approach for warranty.
Click to expand...
Click to collapse
You can stay there and wait for 5 more minutes in the shop while they are attending other customers, just to proove your point.
If they are honest, they will not deny the fact!
foxium said:
I had that "gray splash" problem with my Kaiser and Diamond.
Hard reset also didn't work like above. For both devices the fix was simply flashing to a different (cooked) ROM.
Click to expand...
Click to collapse
knave said:
As mentioned in another thread, the grey screen problem was fixed (as least for me when I flashed to dutty's rom)
Click to expand...
Click to collapse
There might be some tweaks in the cooked ROMs that avoid the problem, or it might be due to some bad flashing or defective hardware.
If not, how do you explain that I've never experienced this with my previous HTC phones (wizard, Trinity...) nor I experienced it with my Diamonds (the first one and the new one) with stock or cooked ROMs.
except for that very special time, when I received a call while downloading messages through Active Sync.
Basically about 2 months ago I rooted the phone and put in cyangen mod, everything was fine until the touch screen stopped working. Most of the time it was brief but sometimes the touch screen just wouldn't work for a whole day and then start working again. Thinking I had done the root wrong I unrooted the phone back to it's orginal. However the problem still showed up despite that. I recently updated it to the donut update, and that's when the problem got worse. Now the touch screen won't work and when I go to the contacts using the trackball I get an error. And anytime i recieve a phone call I get the same error. Thinking it was a software problem and factory reset the phone and scaled it back to rc29. But still the touch screen doesn't work, and now because of that I am stuck on the setup screen at the beginning which ask you to touch the android to continue (which I can't). I have wiped and factory reset the g1 many times, and usually that has made the touch screen work again, but now it seems to not work at all. I deducted over the last couple of days that it must be the power adapter causing all of this. Since I got the touch screen working yesterday and had no problems the entire day. Then a hour after I put it on the charger the touch screen stopped working again and hasn't worked since. Is there anything that can be done at this point to fix it? I read somewhere about a script that makes the g1 touch screen work again but haven't been able to find it.
Same problem
I'm having a near identical problem. Most all of the symptoms are the same - except my touchscreen has only worked for a few seconds on one occasion after the initial failure. I've tried wiping, and about 3 different mods (JaCx, Cyan, Enomther). None have helped, and currently I'm stuck at the same point where it's asking me to touch the Android to begin, and I can't. The only difference is that I didn't unroot. So I'm going to try a few more roms, but I doubt I'll have any luck. My phone was also put on a charger that wasn't made for the g1. I began to notice the problem thereafter. Not sure why, but that certainly seems like the only reasonable variable which could be causing this.
Anyone out there have any ideas? It'd be much appreciated.
Have you guys dropped your phone recently? I'd like to share my story as well. Two weeks ago, I dropped the phone on hard tile while it was still in its leather/suade case. I picked it up and instantly found the touch capabilities were gone (with screen open or closed). After many soft resets and not knowing how else to fix it, I also decided to revert back to rc29 from cyanogenmod. Still no go, after being stuck at the setup screen. I disassembled the phone, using the G1 service manual, to make sure none of the ribbons were knocked loose and examined the lcd and digitizer for any cracks. No problems that I could see. Disassembled, and reassembled the phone a few more times and still with no avail.
If you were one of the first to receive a g1, such as myself, oct 22nd is the last day of your 1 yr warranty. So give t-mobile a call, and submit a claim before then if you want to take advantage of it. Make sure you reflash to stock image, and that there are no signs of visible damage on the phone or else the warranty will be void. Good luck.
Edit: If your phone's touch screen is working at random times, I'm suspecting its a hardware problem, most likely a damaged or worn out flex cable from opening and closing the screen. Try slowly opening the screen and touching the screen at the same time to see if anything happens.
When I was waiting for my G1 I came on this forum (Had a Diamond before so knew about it anyway) and found a topic discussing problems like this... If you have an Early G1 then I'm guessing this is the problem...
There is some sort of design flaw with the ribbon cable connecting the Touch Screen to the Mainboard catching onto the sliding mechanism. This eventually destroys the cable and causes the touchscreen to stop working. On Later models they've fixed it by taping the ribbon cable down instead of letting it hang loose.
In short... you need to unroot your phone and take it back to T-Mobile.
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
gat0rjay said:
Interesting thoughts, thanks for the input. My G1 has never been dropped, and is actually relatively new, only a couple months old. But it's not on T-Mobile. I flashed MLIGN 2.5.7 (Hero). I did this b/c I know it bypasses the typical "touch here" activation BS. So I can boot, and get into the OS just fine. Which is where I'm at now.
Here's what I've done. I completely wiped my Fat32, Ext2, and Linux_Swamp partitions using Gparted. I completely wiped the phone using Cyan 1.4 Recovery. Yet no matter which Mod I use my touch screen doesn't cooperate, AND (no matter which mod I'm using) when I try to launch basic apps (dialer/phone, some settings menus, etc) I am notified that, "android.process.acore" has stopped. Without fail. It ALWAYS does this when attempting to access the dialer/phone. I would be more than happy to take some time troubleshooting the touch screen IF my damn dailer/phone would work. But it does not.
I read on some other forums about there being 2 compcache files for someone who had a similar issue. That's slightly above my head, though, and I'm not quite sure how to go about checking that and/or deleting one. Really, I just want to be able to access my dialer/phone app for the time being. Then I can take some time to trouble shoot the touch screen.
Anyone have any ideas about the process failing, or the compcache affect?
Also, I'm using 1.33.2005 SPL.
Thanks
Click to expand...
Click to collapse
I realize this is an old thread but did you ever get the issue figured out? My phone did this just last night
Alright as suggested earlier in the thread it was a hardware issue. I found that my touchscreen had become unplugged and was causing the errors.
Sorry to bring this guy back from the dead but I figured I would educate a few people one a common touch-screen problem.
Yeah, 90% of the time it's the adapter you're using. Being a G1 owner with lots of mini-USB chargers i found the same problem. Also being a tech rep at t-mobile, i've had lots of calls revolving around this and fixing it.
The G1 uses a 1000mA charger (1A). For me, the touch-screen going haywire/unresponsive seemed to get more severe as the the chargers specs went lower. An old Motorola charger at 500mA was ridiculous. Talking to customers with the exact symptoms and hardware, eventually lost all functionality of the touch screen.
On a side note, it's not just the G1 that has problems with the wrong charger. A linksys router I have has a standard power port connection type in the back but requires a bigger amp adapter. hooking the wrong one up will cause complete failure. In many situations, not enough energy is just as detrimental as too much energy. One last example: Take a big 10" sub driver, hook it up to a crappy 300W amp, you get an overheated coil and eventually a busted driver.
So, lesson is, just because it fits doesn't mean it's safe to use. I never mix and match adapters with any device ever because of the risk of damage.
Hello lovely people of XDA.
Both my wife and me have the Z1, i for my part have experienced screen self cracking and now she is experiencing touch malfunction.
It acts out from time to time, making typing a pain in the a** and playing games even more dificult.
F.ex. if she presses the F key, it registers the D etc.
Ive made a video of this availible here:
http://youtu.be/McGnrGfVpq8 (Sorry about the music, but there was too mutch background noise).
This happens on the home screen, during Candy Crush(yeah i know) and during texting.
Ive repaired the phone twice(previous and newest firmware) via Sony PC Software and still its no good.
It even acted out on the first boot.
Has anyone ever seen anything like this?
Can't seem too find any solution.
CreeVal said:
Hello lovely people of XDA.
Both my wife and me have the Z1, i for my part have experienced screen self cracking and now she is experiencing touch malfunction.
It acts out from time to time, making typing a pain in the a** and playing games even more dificult.
F.ex. if she presses the F key, it registers the D etc.
Ive made a video of this availible here:
http://youtu.be/McGnrGfVpq8 (Sorry about the music, but there was too mutch background noise).
This happens on the home screen, during Candy Crush(yeah i know) and during texting.
Ive repaired the phone twice(previous and newest firmware) via Sony PC Software and still its no good.
It even acted out on the first boot.
Has anyone ever seen anything like this?
Can't seem too find any solution.
Click to expand...
Click to collapse
Theres a well documented thread about touchscreen issues, I myself was one of the people it affected, your problem sounds slightly different.
The method to test was put the phone on a flat surface and make contact with the screen, move around and if you notice a break in contact then you more than likely have the bug.
Holding the metal frame of the phone in your hand eradicated the issue for some (me included) but it was certainly a pain.
My problem went away on it's own but some weren't so lucky.
Have a search for the thread in here, it's more than likely still active.
If nothing helps from that thread then it's more than likely a case of doing a warranty repair. (if it's the same issue)
Hello there and thank you for your reply.
As it seems to me there has been no solution to the problem, ive tried holding the phone without a case and the problem persist.
People are talking about the new update fixing it, but ive tried both updating and reseting the phone so that did not do anything.
It seems like the only thing to do is to send it in for a warranty repair.
With my self cracking the workshop told me that some of the frames where faulty placed in the factory and therefore might crack the screen after a long time under pressure.
Perhaps this is related somehow, though it feels and looks like a software bug.
Thank you for your reply, i'll be sure to keep a look out on that thread. (i found it now, but i could not find it before i posted this :S)
Thanks again
The kitkat update was rumored to remedy these touch screen issues. Have you updated? My C6906 was giving me occasional touch screen issues but they are non-existent after updating.
Sent from my C6906 using XDA Premium 4 mobile app
Yes i have installed Kit Kat, seemed to help at first but started acting out again the same day.
I even did a factory reset with newest firmware downloaded through PC Companion.
I'll keep looking around and post my findings.(If any)
Update:
So we both sent our phones to the service center and sold them right afterwards. Could not find a solution for the problem and the service center ended up replacing my handset and my wifes screen.
I now have a Nexus 6(it's so fantastic!) and she has an iPhone6 plus(Blaaarh...)...
Hello,
I bought a used Z1 almost a year ago. Everything was working perfectly, I was very content with my purchase but I broke the display shortly after. I got it changed at a local repairman but ever since then, my screen acts weirdly.
1. When I use the phone for 10-15minutes, it gets a little warm and so do my fingers and then the touchscreen starts acting weird and pressing stuff on its own. If I lock/unlock it, the problem is solved.
2. Same thing happens when the phone is turned sideways for a few minutes and when I flip it vertically, the touchscreen starts acting weird. Lock/unlock fixes the issue again.
The fact that lock/unlock fixes it leads me to believe that it's not a hardware problem. I started a research and found this topic - https://forum.xda-developers.com/showthread.php?t=2691849 , however it's a bit outdated and is already edited saying not to try the fix. I'm not proficient enough at this so I cannot really grasp the idea behind the topic mentioned earlier and can't get myself to try it cause it might brick my phone or something.
Any suggestions would be helpful.
Regards:good:
sorry to say you friend but it's a hardware problem it's something related whut the screen contrast I've tried everything the only thing left it's to get an original screen replacement and I haven't been able to get one in my country
Generic Screen, that's the problem, i would never recommend to buy a "new" screen, always buy an used one or a phone with broken motherboard and swap them imo
tbh, your problem is weird to, may be a bad installation, i had the same problem in a z1 that i use for games, disassembly all the phone and now I'm using the screen without gluing to the base and the problem was "solved"
Hi,
First of all, Sorry for Bad English, Bear with me.
Long Story, Short!
It keeps happening!
It would turn off, won't reboot
Won't take charging
I will leave it for a while
If I leave it off after when I am tired trying to turn it on, a few hours later It will be WARM like it was being used, Then I would plugin again and THIS TIME IT WOULD TAKE CHARGE and EVEN REBOOT!!
After when I am using it for a while (10-12min) GOES BACK TO POINT 1
I ERASE EVERYTHING, FACTORY RESET IT, and This time.. IT would work for more than 10-12min,
I will install apps, login into the account, and then again... The same thing would start to happen! !
What Really Happen? Day ZERO!
I bought this Red Magic 3 phone 3 months ago and it was working super awesome and everything was great until last week after a 30-40 min gaming session on this phone, I went back to sleep and kept the phone on the table.
The next morning I noticed that the mobile is turned off, I thought Maybe battery drained so I plugged in to charge and continued with my morning routine.
After an hour I noticed that mobile is still not charging I tried plugging in and out multiple times and it didn't start charging, I checked the Data Cable on my MI MAX 2 (that also supports Type C) and Cable and Adapter were working fine.
I immediately realized that SOMETHING IS WRONG!!!
I saw some youtube video and I tried that Vol Key + Power Key thing and that Bios look alike menu opened up, I can see all the reboot, recovery boot, etc option but nothing worked.
So I picked the WIPE DATA option and It worked, Formatted the Phone and IT REBOOTED.
I figured maybe some software issue was causing it.
BUT SINCE THAT DAY it keeps happening!
It would turn off, won't reboot
Won't take charge when I plugin
I will leave it for a while
a few hours later It will be WARM like it was being used, Then I would plug in again and THIS TIME IT WOULD TAKE CHARGE and EVEN REBOOT!!
After when I am using it for a while (10-12min) GOES BACK TO POINT 1
Service Center
They are no help! They don't know what is wrong with it, Even they formatted it in front of me they did the Factory RESET it, I tried using it in Front of them for a while and the SAME THING HAPPENED!
then they installed some updates using some official package.
But still,
IT would work for more than 10-12min,
I will install apps, login in the account
suddenly... The same thing would start happening again!
Their Resolution is :
Motherboard issue and I will have to get the motherboard replaced.
This simply means EVEN THEY DON'T KNOW WHAT IS WRONG WITH IT and CHANGING EVERYTHING is their SOLUTION!
and they said it won't be covered on the warranty! Because the warranty has been voided BECAUSE THERE IS A SMALL CHIP on the phone! -_- which happens to be 40-50 days old.
I know is their Excuse to get money from me! Now I don't know what to do with it.
For me it was my first expensive mobile. I never bought a mobile for more than 200$.
Same thing for me.
Germany, Europe.
Download Ampere.
What's your battery health at, voltage, and how many ma draw when just sitting in that app.
I've learned my lesson with this company. A couple of extra capacitative buttons and a large battery are not a reason to buy a phone. The build quality is ok, the software abysmal (I still get random **** getting pressed when I unlock the phone), and support horrendous. Do yourself a favor, threaten to speak with the governing authority in your country regarding warranties. Tell them a small crack on the screen is not indicative of internal damage. Tell them you will post a youtube review of the company and phone if they do not abide by their warranty and fix your phone.
Once you fix your phone, sell it and cut your losses.
When will people learn YouTube won't do anything. You need subscribers to have any kind of weight. I'm at 2.4m lol.
I don't know the warranty laws in your country. I know here they have to prove that what you did was the cause. Nubia is really shady and not only scams but will flat out lie all the time. I seen people had bad battery's and they say they need a replacement board.
Just let me know what I asked and we can start going in a little deeper. Start off with the basics then move into some other stuff. Could be a simple easy fix.
Some off topic posts are removed. Please remember our rules and post constructive content. Thank you.
Any update?
I'm curious to see if this is a battery issue or something else
Mineapple said:
Same thing for me.
Germany, Europe.
Click to expand...
Click to collapse
So What did You do....!
Ok I attempted to help you trouble shoot this issue and get it fixed but it's pretty clear this is an uphill battle and a waste of my time.
bignazpwns said:
Ok I attempted to help you troubleshoot this issue and get it fixed but it's pretty clear this is an uphill battle and a waste of my time.
Click to expand...
Click to collapse
Thanks for your time.
I got the Battery Replaced thinking it was the issue but right after the installation. I turned it on to use it and it didn't work... I am still facing the same issue.. Meaning Battery was fine.. there is something else that causing it to turn off like this..!
Still, it acts like in COMA, then it heats up, I will charge it, It will boot.. If I will try using it ..it will turn off and won't turn back on!
bignazpwns said:
Any update?
I'm curious to see if this is a battery issue or something else
Click to expand...
Click to collapse
Well.. I got the battery replaced and it was a waste of another 2,000INR. Still Facing the same issue. This means this Turning Off issue is not caused by the Battery.. It is due to something else..! :crying: