Related
I realize this has probably been posted and resolved but I cannot find any solutions yet. So here's the deal:
My fiancee dropped ger G1 into the toilet abot 2 months back or so. I was cleaning and stumbled across it and figured I would check and see if it had dried out okay or not. It is a non rooted black G1 running android 1.6. I tried a coupke of things and figured out I can turn it on now but it goes directly to the bootloader screen. I have ran the DREAIMG.nbh for rc29 and it will update it okay no problems. The issue is that after a soft boot(? Is that the right phrase?) By pushing menu power and call that it boots up...and goes right back into bootloader and tried to run the rc29 update again.
Has anyone else stumbled across this problem and if so how did you solve it? It boots into the factory recovery fine also and will run update.zip files but then once again boots directly to bootloader.
I am trying different things and tweaking here and there because I have a pretty strong feeling this isn't impossible. I'm just overlooking something I'm sure. If this issue has been resolved can someone post the link to the thread or even pm me and give me ideas here. I'm trying to root it since it seems the operating system is shot as is.
-------------------------------------
Sent via the XDA Tapatalk App
Water-Logged
Geoi1006 said:
I realize this has probably been posted and resolved but I cannot find any solutions yet. So here's the deal:
My fiancee dropped ger G1 into the toilet abot 2 months back or so. I was cleaning and stumbled across it and figured I would check and see if it had dried out okay or not. It is a non rooted black G1 running android 1.6. I tried a coupke of things and figured out I can turn it on now but it goes directly to the bootloader screen. I have ran the DREAIMG.nbh for rc29 and it will update it okay no problems. The issue is that after a soft boot(? Is that the right phrase?) By pushing menu power and call that it boots up...and goes right back into bootloader and tried to run the rc29 update again.
Has anyone else stumbled across this problem and if so how did you solve it? It boots into the factory recovery fine also and will run update.zip files but then once again boots directly to bootloader.
I am trying different things and tweaking here and there because I have a pretty strong feeling this isn't impossible. I'm just overlooking something I'm sure. If this issue has been resolved can someone post the link to the thread or even pm me and give me ideas here. I'm trying to root it since it seems the operating system is shot as is.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
the reason it goes into the bootloader is most likely that there is still moisture under the keys .. my friend had the same situation .. the keys were constantly making contact and thus went wherever the keys led .. for instance: a stuck home key would get you into recovery .. a stuck back key gets into bootloader .. it takes quite a lot of effort and patience but if you can completely dry out the insides you should get it functioning again
Also, im pretty sure the G1 goes into the bootloader if there is a hardware failure(like the radio is not responding).
And how the hell did your fiance drop her G1 into the toilet? She better be hot because she sure as hell doesnt seem smart.
kingkurry said:
Also, im pretty sure the G1 goes into the bootloader if there is a hardware failure(like the radio is not responding).
And how the hell did your fiance drop her G1 into the toilet? She better be hot because she sure as hell doesnt seem smart.
Click to expand...
Click to collapse
Happens to a lot of people...Kind of a rude statement for you to make about his fiance. On another note, OP, did you try burying the G1 in a bowl of rice (uncooked of course) and leaving it for a few days and then trying again. That has never failed me.
G1ForFun said:
Happens to a lot of people...Kind of a rude statement for you to make about his fiance. On another note, OP, did you try burying the G1 in a bowl of rice (uncooked of course) and leaving it for a few days and then trying again. That has never failed me.
Click to expand...
Click to collapse
+1.... the rice trick usually works as long as you haven't messed around with it too much while it is wet.
make sure you remove the battery, sdcard and sim card so the rice can absorb more water too
Jeffro64 said:
+1.... the rice trick usually works as long as you haven't messed around with it too much while it is wet.
Click to expand...
Click to collapse
Yup, I had a friend that dropped a G1 into a toilet months ago. He took everything apart you can take apart ie battery cover, battery, sim, SD card etc.. and he put it in a bowl of rice for 3 days. It's worked fine ever since..
you could get isopropanol ;D thats pure alcohol, then put the lower side of the g1 into a cup of that and let it dry for ~1 day. if that doesnt work i dont know how to go further ;D
Wrong section.
Jeffro64 said:
+1.... the rice trick usually works as long as you haven't messed around with it too much while it is wet.
Click to expand...
Click to collapse
Double ditto on the rice. Instead of a bowl, though, I recommend a ziplock plastic bag. That way no additional moisture is getting the attention from the rice.
We did this with my wife's old phone, worked like a goddamn charm. I was amazed.
+5 on the rice idea. did that a long time ago with my brothers G1. He jumped into a lake after a discgolf disc. more worried about losing a $20 disc than a $300 phone. (We both pre-ordered the phone and i think thats how much it was.)
To be honest, there really is no point. The fact that its been like 2 months means most of them moisture should be gone. The reason the phone is going into the bootloader is because of a hardware failure. When the phone boots(the G1 screen) it runs hardware diagnostics. If there is a failure(which there is probably due to toilet water corrosion) it will go into the bootloader.
Anyway, forget the g1. She is your fiance ffs. Buy her something nice, like a MT Slide, or a Nexus
Let this be a lesson to all of you that get your phones wet. immediately after they get wet, remove the batteries, and submerge the phone in alcohol. Then put the phone in a ziploc bag with LOTS of silica gel packets. Leave in bag for 2 days.
Another story related on a french G1 forum :
A guy helped his sister to move. Exhausted, he went to the balcony to smoke and take a deep breath. While he was taking his cigarettes out of his pants, he realized he had also hung his G1, which fell from the 4th floor.
Sick of what occured, he went down to get his G1 back. Hopefully and even supernaturally, the screen was intact. Even more, when he tried to turn it on, he saw the G1 screen. It booted normally, and everything was working perfectly !!
Surprising, isn't it ?
That's why the HTC Dream (G1) is Magic (MT3G) !!
Lol I am getting her the mt slide next week lol. And in regards to "she doesn't sound very smart"... My fiancee works in assisted living and doesn't have much downtime. If you really need details(and why would you?) It fell out of her scrub pocket where you'd think it'd be safe at. S*** happens lol no need to say what was said.
My friend who has helped me rescue my phone a couple of times in my early rooting days recommended the rice bowl idea. Furthermore the phone doesn't boot into the G1 screen then to bootloader. Its going straight to bootloader. If its a radio problem is it possible to go thru and rename the current G1 radio to update.zip and flash it in recovery? Then the danger spl(which I have all saved on my pc from my rooting my G1). Thoughts? Ideas?
And thanks for the help guys btw
-------------------------------------
Sent via the XDA Tapatalk App
The rice trick won't help you anymore as there should be no moisture left after all that time. If you can disassemble it, clean it's guts with alcohol to get rid of shorts and it should probably be fine
Geoi1006 said:
Lol I am getting her the mt slide next week lol. And in regards to "she doesn't sound very smart"... My fiancee works in assisted living and doesn't have much downtime. If you really need details(and why would you?) It fell out of her scrub pocket where you'd think it'd be safe at. S*** happens lol no need to say what was said.
My friend who has helped me rescue my phone a couple of times in my early rooting days recommended the rice bowl idea. Furthermore the phone doesn't boot into the G1 screen then to bootloader. Its going straight to bootloader. If its a radio problem is it possible to go thru and rename the current G1 radio to update.zip and flash it in recovery? Then the danger spl(which I have all saved on my pc from my rooting my G1). Thoughts? Ideas?
And thanks for the help guys btw
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Hey dude, sorry about the "she doesn't sound very smart." I was just trying to make a joke but I now realize that it was pretty rude. No need to explain. Also, when i said that, I didn't consider the fact that girls need to sit down to pee.
Now if a dude did that, that would be stupid.
kingkurry said:
Now if a dude did that, that would be stupid.
Click to expand...
Click to collapse
LOL. Now you trying to say that girls are stupid?
It is better for you to just say sorry and don't reply again.
kingkurry said:
Also, im pretty sure the G1 goes into the bootloader if there is a hardware failure(like the radio is not responding).
And how the hell did your fiance drop her G1 into the toilet? She better be hot because she sure as hell doesnt seem smart.
Click to expand...
Click to collapse
heh i know this smoking hot blonde that dropped her blackberry in the toilet your logic is true cause she is not that smart.
She ended up getting a droid so there must be something ticking up there.
ionic7 said:
heh i know this smoking hot blonde that dropped her blackberry in the toilet your logic is true cause she is not that smart.
She ended up getting a droid so there must be something ticking up there.
Click to expand...
Click to collapse
Either that or she buys everything advertisements tell her to
I know an amazing looking girl whos boyfriend dropped her iPhone in the bath after he left it sitting on the side.
Don't always assume that men are smarter than women.
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Creepazoid said:
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Click to expand...
Click to collapse
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Creepazoid said:
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Click to expand...
Click to collapse
I wasn't being sarcastic, however this is me now saying you're probably screwed.
Sent from my DROID BIONIC using xda premium
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Haha, alright, well thanks again for the heads up on the one-click, definitely going to come in handy in the future.
Sent from my MB860 using XDA App
beidave said:
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Click to expand...
Click to collapse
He said he's tried a few different batteries.
Sent from my DROID BIONIC using xda premium
So what was the verdict? Mine just did the same thing. However, I Have followed all of the directions everytime i've flashed and never had an issue til right now.
If you can't get the phone on at all, no fastboot or anything. No hardware buttons do anything, nothing comes up on the screen with anything you try....
That's a hard brick.
= requires a new phone
No way to fix it.
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
When I messed up my flash and my phone was stuck at the dual-core logo, I followed the steps below.
Pull your battery.
When you put it back in, hold down the power and volume down to access fastboot mode.
From there you can do a one-click restore method.
That is how I solved my problem. I hope it helps you.
Sent from my DROID BIONIC using xda premium
nickbeisher said:
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
Click to expand...
Click to collapse
have you triedf pulling the battery and putting it back in. the hold volume key down and power at the same time? if that works then just restore using fxz. if it does not work your phone is bricked
Brick!!
This is my third droid, I had The D1, the X, and now the bionic. By far I like this one much better than the the others. I have rooted all of them, and done the basic app freezing, overclocking, and other basic mods. This is my first go round with the custom rom flashing. I Flashed R3blurr3d, and every new update ( each update a new flash ). I also flashed D3blurr3d, and Liberty, just to check them out. I personally like Reblurr3d. When I flashed I always followed every direction to the letter, and if I was unclear on something rather than ask a stupid question, or ask something that had already been covered. I read and search until I find the answer I need and it is clear to me, sometimes that means searching for hours on end. I do this for the fear of ending up with a "Brick".
Now with everything I have read about any of these phones to "Brick" It is an error on the user's end while flashing or something of that sort, ( not following directions ).
So with everything operating butter smooth, and flashing dozens of times before this. What would cause a "Brick" during everyday use?
My guess is....he didn't know what he was doing. You rooted it for him and left it rooted for a user that knows nothing about root access. He probably did something using root access to fck something up.
When someone asks you to root their phone for them, the answer is always no.
Unless they know what they're doing, never give someone root access.
my first bionic did same thing. it was not rooted yet. just started rebooting it self. got more frequint then just quit the way you talked about. hardware problem.
Yes. That is what it is. It is a hardware issue, after talking to tech support it is a capacitor or something like along those lines, it stores battery power for times when more power is needed, like turning on the phone for instance. And when it randomly boots it is because it runs short on power due to the faulty hardware.
But apparently it is a known issue with Verizon, so if it happens to anyone else they should not have any trouble getting a new phone. I talked to a very nice tech support agent, and I will have a new phone by noon on Saturday.
And also I didn't have anyone root my phone, I do all of it on myself, Im no computer genius, but like I said I take my time and follow directions. And until now I have had no issues, and this had nothing to do with root access, flashing custom rims, or any other tweaking just a bad part Anthe phone. The thread was started by someone else. When I searched the threads, I found this and it was the same exact problem as I had, so that's why I asked what the end result was.
So with all that being said maybe this will be informative to someone else.
Hi everybody,
I was (am?) running CM 10.1 for a couple days just to see how it was, and it was nice. I was going to make it my daily driver until I got a call while the phone was in my pocket and suddenly, the ringing stopped. I took the phone out of my pocket and tried to unlock it. No cigar. It must have powered off. Pressed and held. Nothing. Bootloader? Nope. Try under the halogen work lamp. Nope. No charging light, no splash screen, nothing. Just a brick.
How is it possible for the phone to just brick itself like that? I remember setting the max clocking speed at 1.5ghz and the governor to "conservative" but that's really it. Plus I had rebooted a couple of times between then and now. I ddon't have many apps, let alone many that have root access. So what's up?
Please help me. I give my battery 15 maybe 24 hours before it dies and I can't boot.
Oh yeah. I don't have S-off, I got my version of CM from get.cm, no custom kernel, or any mod of any sort. The phone was not actively doing anything, except for sitting in my pocket. I held the power button and the power + volume for a good 20-30 seconds.
EDIT: Is my only option to play dumb and ask for warranty? D': I don't want to do that because the rep who traded in my GS2 noticed that it was rooted. I'll probably get denied.
Seriously, anybody? What are my options? What caused this? Is it my fault?
I wish I had some insight on why that happened to you or how to fix it. What I can say is that I was thinking about flashing my first AOSP rom in the near future but was iffy on it. Now I'm super iffy.
I suppose there is a possibility that it was not software related. Maybe the phone is just a clunker? Hopefully someone more knowledgeable than myself can comment.
try posting this in the CM 10.1 forums and you will get a result. sorry.
Sent from my SGH-I747 using xda premium
SantinoInc said:
I suppose there is a possibility that it was not software related. Maybe the phone is just a clunker?
Click to expand...
Click to collapse
That's a possibility, and what I'm thinking too. Surely someone would have noticed if their phones blew up when they received a call right? The phone wasn't doing anything I hadn't done before (i.e. receiving calls).
You think Sprint will replace it? It's pretty much mint other than the software.
And there is no HTC One Cyanogenmod forum yet.
EDIT: So is it safe for me to go to the store and tell them it crapped out on me? Will they be able to tell that I rooted it?
Have you tried using the HTC charger that came with the phone and letting it charge for for an hour? If the phone got completely discharged it may take up to 10 minutes just to lite up/
RJR
rrusek said:
Have you tried using the HTC charger that came with the phone and letting it charge for for an hour? If the phone got completely discharged it may take up to 10 minutes just to lite up/
RJR
Click to expand...
Click to collapse
First off, Lithium ion batteries do not completely discharge, ever. If they do, they are ruined. Your phone will turn off before it lets the battery drain.
Second, I had at least 80% charge left when it bricked this morning. But what the heck, might as well.
EDIT: Wow. I googled hard bricks and pretty much every case is some kind of update or flash gone wrong. Nobody was just walking around when their phone bricked. This is weird. Considering how rare hard bricks are and the fact that the only apps with root access I had were Ti, File Manager, Spirit and Nova, I'm inclined to believe this is a hardware issue. But I can't be sure.
Bumping. I only have a little while before my charge runs out.
Hmmm, do you know, or have an idea what the battery life was when the incident occurred?
==
EDIT: Oh I see...
I unplugged it about 3 maybe 4 hours before it bricked. It had maybe an hour of screen time then. I'm assuming I had around 80% when it bricked. I have no idea how much power the device is currently consuming. But if it's truly bricked, prolly not much, so it'll last for a while.
If it isn't truly bricked, then probably not that long...
Guys, I'm desperate. I'll try absolutely anything.
All right, it seems like I'm done. This device is toast. Even though it seems like I didn't make any mistakes. I know that almost for sure because my phone was ringing when it bricked at 12:36 P.M. today.
Based on what I've said, does anybody think I am COMPLETELY to blame for this? I don't want my conscience to eat me alive when I take this is for warranty and play dumb. I truly believe this has nothing to do with rooting/custom ROM. I really believe this is a defective phone. Am I wrong?
Did u try the bright light trick
Sent from my HTCONE using Tapatalk 4 Beta
Try the bright light trick...
You can't even get into the boatloader? Or does anything show up when you plug it into the computer?
Sent from my HTCONE using xda app-developers app
sauprankul said:
Hi everybody,
I was (am?) running CM 10.1 for a couple days just to see how it was, and it was nice. I was going to make it my daily driver until I got a call while the phone was in my pocket and suddenly, the ringing stopped. I took the phone out of my pocket and tried to unlock it. No cigar. It must have powered off. Pressed and held. Nothing. Bootloader? Nope. Try under the halogen work lamp. Nope. No charging light, no splash screen, nothing. Just a brick.
How is it possible for the phone to just brick itself like that? I remember setting the max clocking speed at 1.5ghz and the governor to "conservative" but that's really it. Plus I had rebooted a couple of times between then and now. I ddon't have many apps, let alone many that have root access. So what's up?
Please help me. I give my battery 15 maybe 24 hours before it dies and I can't boot.
Click to expand...
Click to collapse
i knew there was something going on here, between cm10.1 and the sprint htc one ? sure makes me wonder, i've been on my replacement for nearly 2 weeks now running stock rooted with s-off. http://forum.xda-developers.com/showthread.php?t=2310750
Ok I just read your thread and was wondering. did you get your 150 back?
Either you and I are incredibly unlucky or the m7spr cm 10.1 is suicidal.
Just a question. in general, what setting were you using? Anything similar to mine? I had also set notification light to "long". how about you?
sauprankul said:
Ok I just read your thread and was wondering. did you get your 150 back?
Either you and I are incredibly unlucky or the m7spr cm 10.1 is suicidal.
Just a question. in general, what setting were you using? Anything similar to mine? I had also set notification light to "long". how about you?
Click to expand...
Click to collapse
I was told I would be refunded on my next bill so i'm waiting it out to see before I send back the bricked one. no i was stock-cm and what I mean by that is i installed cm10.1 added my apps, set up my home screens and used it like that until it died. i changed nor tweaked any of the settings from cm defaults
The same thing happened to my room mates HTC One yesteray. I first installed CM, and it was getting extremely hot, so I decided to try rootbox, similar issue, and the device was discharging far too fast. He turned the phone off to wait for me to get home so I could try to fix it. I got home, and there was no sign of life, it was charged fully before he turned it off. It wouldn't turn on at all. I had him take it to sprint and do warranty, they said they needed to open it(LAWL). He went back an hour later, they couldn't open it of course. They handed him a new phone.
Have you tried plugging it into a pc to see if it recognizes anything in device manager? Checked adb devices and fastboot devices?
I have. And nothing. No charge no power no recognizing
Sent from my HTCONE using Tapatalk 4 Beta
For some odd reason my Droid turbo lags from time to time. It takes forever to open apps, scrolling is not smooth. When Typing messages my phone is like three words behind
Also charging my phone takes forever. It will quick charge to about 35%.. But after that it takes hours to reach 100%. I plug my device in at 6AM.. Woke up at 11 and the device was only at 77%!
This can't be normal.. Should I get a replacement or is their a simple fix?
Mine went from 63 to 100 in about an hour, something isn't right, take it back
I agree with mikera67. Something is definitely wrong. Have had my turbo for a week and have not had any lag or issues with charging. I would take it back and exchange it.
Can I call Verizon and have them send me a replacement? Or do it has to be done in store?
Sent from my XT1254 using Tapatalk
YoungAceAtlanta said:
Can I call Verizon and have them send me a replacement? Or do it has to be done in store?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You should be able to call them. Personally, I would just take it in to a store if possible, would make the process a lot quicker and easier. Every time I call Verizon with an issue I get stuck with some tier 1 tech that assumes I am an idiot. So then I have to spend 30 minutes on the phone until I can convince them I am not an idiot and there is actually a problem.
Last time I had to warranty replace a phone I tried to just call them and have them send me a replacement only to spend an hour on the phone and have the tech tell me it must be user error (the lower volume button was stuck in a permanently on state so the phone would never load past the bootloader). I then went into a store and they had a new phone on the way in 10 minutes.
You was right Manjews lol.. The rep I was on the phone with couldn't do it so he said he left notes on my account so when I go into the store they exchange it with no hassle
Sent from my XT1254 using Tapatalk
Hi.
I have the weirdest issue: My screen flashes when I try to turn it on, but refuses to give me any picture. Here's the weird part: It only happens when the phone is cold (approx under 22c, 72f). Now to be clear, the screen works at any temperature I've attempted to use it in. It just won't START in those "low" temperatures. When it's running it'll keep running with zero problems.
The touch works when I attempt to turn on the screen, regardless of if it actually turns on or not.
I've tried complete factory wipe, and even downgraded the OS via the huawei program on PC. Only difference was that sometimes when it would have flashed it gets stuck on a green glitchy pattern.
I'm fairly proficient in electronics, but I can't think of any reason why it would act this way.
It's clear I'll have to send the phone for repairs, but I'm out of warranty so I'd rather find a fix I can do myself (even if it's complicated, I've got access to microscope and fine soldering equipment), and MOST IMPORTANTLY I want to figure out WHY this is happening.
Tell me if any specific information could help figuring out what is wrong.
Send to service... replace screen in warranty...
my p20 pro also did it... i walk to service, replace screen in warranty within 3hours...
I'm sorry..... 22 Celsius.... Cold? Damn not jealous at all. Still 5 degrees here [emoji23]
Sent from my CLT-L09 using Tapatalk
blufreak said:
I'm sorry..... 22 Celsius.... Cold? Damn not jealous at all. Still 5 degrees here [emoji23]
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
Well I should have used quote make around cold.
Here it's around freezing atm.
Update
So, interesting update:
I dropped my phone, and it slammed into the floor quite hard. It seemed to have fixed the problem. Now I REALLY want to figure out what was the cause of the problem to start with!
VanDerGroot said:
I REALLY want to figure out what was the cause of the problem to start with!
Click to expand...
Click to collapse
Looks very much like an unstable contact that was "slapped" back by the fall. If you really want to know what was the issue you should open up your phone and tell us all.
arty_a said:
Looks very much like an unstable contact that was "slapped" back by the fall. If you really want to know what was the issue you should open up your phone and tell us all.
Click to expand...
Click to collapse
How would temperature effect an unstable contact?
I would open my phone but I don't have a heat gun.
Thermal expansion, maybe?
I think mine does the same thing. Only ever notice it outside, where I have to keep trying to open my screen, while it keeps flashing, and when I wake up in the morning and usually have to fully restart my phone to use it.