Related
I think I just figured out how to fix it!!!!!!! I was tinkering around and got my red light brick to turn on!!!! I'm not sure exactly what fixed it so here's everything I did-
1. Removed the storage & sim cards.
2. Took off the backplate.
3. Removed the battery.
4. Bent these 2 pins up a little bit:
5. Put the battery in at an angle, so that the power leads were connected, but the metal shielding plate on the back of the battery was not touching:
6. Hit the power button (with the battery still "halfway" installed) Bam, green light of life.
Somebody please confirm this. Meanwhile I'll be copywriting this process so anyone who performs it owes me 10 bucks
So my replacement Tilt isn't working either, so they're overnighting me a third one. In the meantime, I haven't sent back my original (RLoDed) Tilt, so I thought I'd play around with some of your theories.
skuzz said:
Another thought I had. After the tilt goes into red brick death mode, has anyone tried plugging it into power, battery installed, and then holding down power+camera(all the way) and then pushing in the reset button on the bottom? This may trigger it to go into flash mode - although I kinda doubt it'll work. Worth a shot! Might be able to reflash it back to life! Holding down power and camera while it boots is how you manually force it to get in the Red/Green/Blue firmware flash mode. If it let us do that much when the device bricked we might have a snowball's chance in hell of getting them working. I didn't think of trying it before I returned mine tho. D'oh!
Click to expand...
Click to collapse
I didn't know what to try besides installing the battery and SIM card and trying to push down the power, camera, and stylus buttons (I knew I was doing it correctly, because I had to use this to return my second Tilt to factory specs). No response whatsoever! This thing is deader than a doornail. Except for the red LED, of course... that works REALLY well whenever it's plugged in.
sWuRv said:
I think I just figured out how to fix it!!!!!!! I was tinkering around and got my red light brick to turn on!!!! I'm not sure exactly what fixed it so here's everything I did-
1. Removed the storage & sim cards.
2. Took off the backplate.
3. Removed the battery.
4. Bent these 2 pins up a little bit:
5. Put the battery in at an angle, so that the power leads were connected, but the metal shielding plate on the back of the battery was not touching:
6. Hit the power button (with the battery still "halfway" installed) Bam, green light of life.
Somebody please confirm this. Meanwhile I'll be copywriting this process so anyone who performs it owes me 10 bucks
Click to expand...
Click to collapse
I appreciate your enthusiasm, but the only thing I can confirm is that this did NOT work on my RLoDed Tilt. Tried it several times in various ways. I think you just seriously lucked out!
As such, I'd also have to vote against stickying this... for now.
Best of luck, all... if not actually in fixing your RLoDed Tilts, then definitely in avoiding the $500 service fee if AT&T discovers we voided our warranties.
alright i will confirm this too....my phone was truely RLOD..... i did the same thing that these guys did just jammin the battery in and out and it "jump started the phone"
exact process used
Moto Razr charger
hold down power button
"bounce" battery on and off the contacts for the battery a good 100 times or so
green light apeared after the red light started to flicker a little bit..... tis as if you were giving the phone CPR or something
im not going to call this a fix all i know is that the phone was RLOD and now it is working....battery is at 54% right now and i will post back in a bit to see if it has risen at all....
no smell arising from device
running origional rom but have had other roms on there (alex's)
hard SPL still installed on device
SPB phone suite is the last software that was installed on the device
reg tweaks installed as well, the usual ones no sms, hsdpa enabled blah blah blah
that is about all i can provide....the unit was on the computer overnight charging....when i woke up it was RLOD....and i was sad....i did have the ATT store replace the battery for me as well dunno if that had anything to do with the issue...
in the time that it has taken me to write this the battery is now at 55% so it is charging.....on wall charger with MOTO razr charger
ok lets take a little closer look at what happened within the past little bit....
after gettin the device all up and running it was behaving very oddly.... it would go through multiple attempts to connect to the data network for various reasons....after showing that it was at 55% on the charger it went back down to 54%... i pulled it off the charger and took it into the other room to do something......within 10 min it was down to 46%....now having a data connection my blackberry connect should have a valid network connection....but it did not... not sure why...
the best that i can conclude is that it was trying to connect to so many things all at the same time that it exhausted its self that fast....
so the question is how many people out there that have RLOD are running the BB connect software on there devices and have made REG edits to the data connection time outs and the HSDPA mod availability
editing those settings together may confuse the device and make it think that it has to connect to too many things at one time....
just another thought process that i thought that i would throw out there...
here are some things on the my device that would use the DATA connection and automatically initiate the connection on the device rather than you opening a program forcing it to connect such as Internet explorer
GPS update
HTC home weather tab
SPB weather tab
Blackberry connect
SPB insight....RSS Reader
text messages going in and out....my phone sees quite a few of those
Edit/Delete Message
There have been a few other people who have now fixed their RLOD's. Confirmed it was done by messing about with the battery. If you have revived yours, please post your method in here so we can compare them and eventually pinpoint the fix. Thanks.
i had the same prob..took out the batterly wiped the four contact points on the phone (might of pushed them down or up) and put battery back in and worked..
I believe sWuRv was onto something. My Tilt had the RLOD today. I tried everything, even what he suggested above to no avail. So I called warranty and got my replacement on it's way, express shipping waved and all. So I decided to everything I could think of to try and get the thing back on so I might be able to back up my data again.
I started fooling with the battery, like sWuRv suggested but I moved it all around at 45 degrees or so pushing the power on button. I noticed while it was plugged to the USB with red light on that every now and then the red light would flash when I moved the battery so the contacts moved (while holding the battery at that 45 degrees). I started getting the light to go yellow but it would not stay. So I unplugged from the USB and kept trying it while pushing the power button. It eventually started and I was able to back up to my SD card. One thing I can tell you is that this process caused the phone to get hot and smell like electronics burning a little. There is definitely a power problem inside.
I have no idea how or why this worked but it did. I think I will still take the replacement even though I have to figure out how to swap my fancy invisible armor clear protector skin.
I'll try and update on whether this phone dies again or what until I get the new one.
rlod
I tried messing with the battery in a variety of ways for 30 minutes with no sucess. RLOD stayed solid.
RLOD
Holy shoot............After bouncing my battery up and down about 40 times my phone came to life!!!!!!!!!!!!!!!
Reseating the battery and/or sim/storage cards is hardly a revolutionary procedure. Its Cellphone 101.
you guys are LIFE SAVERS. I have been on this forum for about a month now and I finally found a reason to post. I haven't posted because I always find my answers. I just wanted to thank everyone, as I have been on the phone with Amazon.com (where i got my tilt), went into an AT&T store and was on the phone with HTC tech support ALL day trying to resolve my red light issue. Unbelievable that all I needed to do was give it some "battery CPR":
UGHHHH. Well i found reason to make post #2. The fix lasted less than 5 minutes.
this did not work for me
These stories remind me off all the bad batteries/no powerup of my Motorola Q and those of others. My mother is on her 4th Q and I know its the battery, but the store just swaps out the whole phone. I've seen batteries last as little at 2 weeks, especially if let run down to empty at any point.
My questions are, is this just a bad battery problem? Does anyone with RLoD have a spare battery to try? If these batteries fail in the shorted condition, will they over draw power from the phone and mess up the charging circuit?
Roto
"Not the Mama", OR, NOT THE BATTERY
rotohammer said:
These stories remind me off all the bad batteries/no powerup of my Motorola Q and those of others. My mother is on her 4th Q and I know its the battery, but the store just swaps out the whole phone. I've seen batteries last as little at 2 weeks, especially if let run down to empty at any point.
My questions are, is this just a bad battery problem? Does anyone with RLoD have a spare battery to try? If these batteries fail in the shorted condition, will they over draw power from the phone and mess up the charging circuit?
Roto
Click to expand...
Click to collapse
I certainly don't believe it's a bad battery problem. I had 2 spare batteries, fully charged with separate docking charger - none of the 3 batteries made any difference once I got the RLOD.
cushcalc said:
I certainly don't believe it's a bad battery problem. I had 2 spare batteries, fully charged with separate docking charger - none of the 3 batteries made any difference once I got the RLOD.
Click to expand...
Click to collapse
Very good, thanks for the insight!
I finished a call yesterday and then dropped my phone on to the pavement cos I was a bit drunk... Anyway this caused my phone to go from working fine (all be it with pants battery life) to just flashing the red light. Fixed it today. I tried the methods prescribed in this thread without success although I did not persevere for very long. I then put a spare battery in to the phonea and bingo the orange light comes on, phone boots up and it's now happilly charging. Note that I charged the old battery for several hours before trying the fix. Pity nobody seems to know what the problem actually is. I wish HTC would let us know....
sWuRv said:
There have been a few other people who have now fixed their RLOD's. Confirmed it was done by messing about with the battery. If you have revived yours, please post your method in here so we can compare them and eventually pinpoint the fix. Thanks.
Click to expand...
Click to collapse
I had a similar problem with my old iPAQ hw6515, and a Motorola V3. The contacts on the battery don't spring forward as well on an older phone as they do when it was new. I shimmed the battery. I did this by taking a business card and holding it against the opposite side of the battery from the contacts I traced the battery's profile and cut it out. I scotch taped my new shim to that side of the battery, then re-inserted it. This forces the battery up against the contacts better and in many times resolves inoperable phones, failure to charge, and spontaneous rebooting issues.
-Jay
My replacement tilt (first one had a bad USB connector) died Sunday.
Had it on the charger, looked down, red LED. Back of phone was pretty
warm. Pulled the battery, SIM, memory card, slammed the battery onto the
battery contacts rapidly 5-6 times, put the SIM, memory, battery back into
it, and it charged up. Did a hard reset. Battery was 100% charged, I turned
it completely OFF when I went to bed. Got up, battery was 0% drained!
Red LED again. Did the rapid thingy with the battery again, orange charge
light came on.
Called at&t warranty replacement. When I told her I had a red LED, she didn't
even ask me to do anything else. She just asked for the IMIE number and shipped me another one.
Maybe the 3rd one will be the charm LOL.......
I'm beginning to think that HTC doesn't stand for "high tech computes" but
"high tech CRAP"....
Maybe you guys got the margin of error productions? I know its really unlikely that you could get them again after a replacement but it is possible, and it maybe your computer. What do you think could be making this things go crazy? Overly protective anti-virus, I know, I know but it could do things secretly and screw around like mine does and wont let me into sites I have been on before on the same app no changes . . . Well I hope you luck.
ok I just tried everything you guys said, but it didn't work for me
so as some of you have stated it must be the battery, so what I did is put it between my hands for about 1 minute and put it in and it worked again!
really weird... must be the heat?
well hope that helps the research
Cheers
Jay
Hey guys, I need some help with my G1. I regularly do conditioning for my phone and for some reason, even if my phone has a full charge, it just turns off and I can't turn it back on until I put it on a charger or wait about two hours. Also the phone doesn't give me a notification that it's shutting down. Not sure if this is the right topic to put it in but thanks for the help!
EDIT: I have been using Cyanogen v4.2.13 and I've checked my battery status on my phone and it says that it's in good condition
Ive been having the same problem. Hopefully someone can help us!
me too!
I have this exact problem. I have the latest CyanogenMod - v4.2.13 ROM on my phone. I read somewhere that the auto wallpaper switching apps caused this. But even after uninstalling the app my phone randomly shuts down.
i guess you can try going back to a earlier cyanogen rom or any rom and see if that changes the problem, if not, i guess you can try to wipe, and to the htc recovery and all that and go back to 4.2.13, im still new at this whole thing so its just a thought
Same here
I'm not sure what the deal is. I think that I have dirt in my SD connector or something because mine runs out of memory and reboots sometimes. Other times it works for days. Still other times, it goes into a reboot loop until I take the sd card out and re-seat it.
Perhaps the weak sd connection is the culprit. Are other people keeping the phone in a pocket that generates lint and dust?
Does a battery pull / replace seem to fix the problem?
i keep mine in my front pocket all day everyday lol
I say take a sledgehammer to it, that way it'll die reliably rather than randomly
I reflashed radio, spl, rom, partitioned, wiped, everything! Still shut itself off today. I had to turn it back on with the charger connected to get it back again.
Hey guys, I found the problem. My battery couldn't hold a charge so I would suggest getting a new battery if you had the same problem as I did. Be sure to condition/calibrate it so it'll last longer.
EDIT: Also only put your phone on a charger if the battery is extremely low.
Change Battery
I tried at least 4 different ROMs(with wipe/reset) and it did the same thing. So it's not the software. As a finally test I swapped batteries with my wife (also has a G1). No random shut down on my phone but her phone did. So it's definitely a battery issue. Also, I noticed my battery has swollen quit a bit. New battery on it's way.
I recently received a replacement Nexus One from HTC and within three weeks it has already developed another problem.
Here's what usually happens:
Night to 6AM: Charging the phone
6AM: Pull the phone from the charger
6-8AM: The phone drains battery normally
~8AM+: The phone will automatically shut off for no reason at all, and then I try to turn it back on. After boot up it immediately begins the shut down procedure, with the battery reading ~0% life (sometimes I can't even turn the phone back on after a battery pull, it takes multiple pulls).
I originally thought that the problem was the Nexus was reading an incorrect charge on the battery, so I tried wiping the battery stats. There was no change in behavior, the phone continued to shut off. The only way to fix the problem temporarily is to charge the phone to use it, but the problem persists once the phone is taken off the charger.
I even tried doing a full factory reset, but the device exhibited the same problems after a certain period of time, which leads me to conclude that this is most likely a hardware problem, either with the battery or something with the N1 itself.
Has anyone else experienced similar problems, or does anyone know how to fix the issue? Please offer some insight, as this is getting quite frustrating and I can't use my phone normally until I get another replacement, or I fix the problem.
Can ANYONE help me? I hate only being able to use my phone for like two hours a day if even that.
I will have to start using my RAZR as a back up everywhere I go until I figure this out
answer
CHECK YOUR PM--i had same issue---IT WAS THE BATTERY!!!!! They sent me a new replacement batt and it hasnt cutoff in 2mos!!---KNOCKS ON WOOD DAMMIT!!LMAO!
There a multiple cases where Z3 Compact suddenly off, and then cannot be boot at all (with any mean available). It randomly can be boot, in my case i charged it a long time (approximately one night), then i saw the LED lights lit hence the successful boot. But 5 minutes later, poof, it die again and cannot be boot. I plugged back to the charger, no LED light or respond whatsoever.
The second time i able to boot it, i reflash the stock rom using the PC Companion repair section. But the problem persist, which hint me that this is maybe a hardware problem. I found in the sony forum that the motherboard or the battery could be fail, OR the battery was too low to lit the LED light during charging (which seem illogical for my case which the phone dead with 100% battery).
In the end i sent it to the service center and the phone not currently held up in a ward for god know how long. The friendly assistant at the service center suggested the board or the battery were failed since the phone didn't respond with charging and reset charging.
Any comment from you guys about the possibility of board and battery failure will be appreciated
There a thread in the sony forum,
https:// talk.sonymobile.com/ t5 / Xperia-Z3-Compact/ Sudden-Death-of-Sony-xperia-Z3-Compact/ td-p/877345/page/5
and based on the thread there is a lot of case happen in Malaysia. So for future owner, watch out!
well, this is a similar case [i suppose] http://forum.xda-developers.com/z3-compact/help/bricked-z3c-help-t2952415
Well my Z3C used to be softbricked like you. Meaniez had post my thread about it right above.
The reason for this was the unrespond battery. In my case, I charged it for about 3->4hrs, started at 17%. Then it suddenly softbricked, plugged it to PC, the logo Xperia appeared, but it still remained the same. I took it to the store, their technicians found out that the battery wasn't gone at all, it was hibernate. So they charged it with high-voltage electric for hours, then it came back to life, just like we do the electric shock to save people.
I think my case will help you with a solution to safe your phone.
leonjun said:
Well my Z3C used to be softbricked like you. Meaniez had post my thread about it right above.
The reason for this was the unrespond battery. In my case, I charged it for about 3->4hrs, started at 17%. Then it suddenly softbricked, plugged it to PC, the logo Xperia appeared, but it still remained the same. I took it to the store, their technicians found out that the battery wasn't gone at all, it was hibernate. So they charged it with high-voltage electric for hours, then it came back to life, just like we do the electric shock to save people.
I think my case will help you with a solution to safe your phone.
Click to expand...
Click to collapse
Well, in your case, the phone responded when connected to PC. Mine didn't respond at all. Thanks though for your information.
You meant the logo Xperia didn't appear on the phone when you plugged it ?
fzl.abdulaziz said:
There a multiple cases where Z3 Compact suddenly off, and then cannot be boot at all (with any mean available). It randomly can be boot, in my case i charged it a long time (approximately one night), then i saw the LED lights lit hence the successful boot. But 5 minutes later, poof, it die again and cannot be boot. I plugged back to the charger, no LED light or respond whatsoever.
The second time i able to boot it, i reflash the stock rom using the PC Companion repair section. But the problem persist, which hint me that this is maybe a hardware problem. I found in the sony forum that the motherboard or the battery could be fail, OR the battery was too low to lit the LED light during charging (which seem illogical for my case which the phone dead with 100% battery).
In the end i sent it to the service center and the phone not currently held up in a ward for god know how long. The friendly assistant at the service center suggested the board or the battery were failed since the phone didn't respond with charging and reset charging.
Any comment from you guys about the possibility of board and battery failure will be appreciated
There a thread in the sony forum,
https:// talk.sonymobile.com/ t5 / Xperia-Z3-Compact/ Sudden-Death-of-Sony-xperia-Z3-Compact/ td-p/877345/page/5
and based on the thread there is a lot of case happen in Malaysia. So for future owner, watch out!
Click to expand...
Click to collapse
I am French, exact same thing happened to me last night (didnt boot, plugged it, pressed power/vol+, booted with red light blinking and when on lockscreen restarted automatically and did the same thing again in a loop, then stopped responding at all. Plugged it for the night, green light this morning. Unplugged, didnt boot. Waited, plugged it again, this time it booted up, and it's still working fine. Did a factory reset and erased my data in case I have to send it to repair. It's such a shame, I love this little phone.
I think I'm done. Sick with having to go to the centre, sick with their crappy excuses and most importantly sick with all the 'bad batch' problems - Glass cracked, Flap covers, and worst of all, sudden death? Gosh that's crazy. Btw I am from Malaysia and my phone last night have just officially been infected with the sudden death problem for no reason. I am pretty confident that even if they swap my phone with a new one, that would also be from the bad batch.
But again, this is just me. I hope yours would be much better because overall the phone is actually quite good given the size. Cheers
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
bilboa1 said:
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
Click to expand...
Click to collapse
I know I'm a bit late to the party, but a colleague of mine just contacted me about the same issue - phone rebooted and remains dead.
I have not yet had a chance to look into the phone itself, but according to him the internal storage would be full up to a few MB, which would explain the issue based on your investigation.
Will look into it further...
Dude,
I feel your pain, read what happened to me : http://forum.xda-developers.com/showthread.php?t=3037336
The phone went back in warranty, I just had to pay the postal service, nothing else.
They didn't told me what was the problem, but I think they replaced the motherboard.
Sent from my D5803 using XDA Free mobile app
FYI: Here's the report I received from them.
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
This just happened to me. For my exp, we have this problem when we charge with the magnetic cable. Correct me if I am wrong.
So happy to see this topic, hoping that there is the fix guide in this, however ...
can anybody helps me ?
laufersteppenwolf said:
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
Click to expand...
Click to collapse
Hi,
please do inform us when u find any solution cause i'm facing similar issue after using it for 6-7 months
shardul.phatak said:
Hi,
please do inform us when u find any solution cause i'm facing similar issue after using it for 6-7 months
Click to expand...
Click to collapse
Have you tried upgrading to 5.1.1 (23.4.A.0.546)? I had the same problem, where my z3c would only last an hour or so until the next sudden death and I'd have to wait a few days before being able to turn it on again (and will die after another hour).
Since I upgraded, it has only happened a couple times, and even then I could immediately turn it back on. While it's not a complete solution for me, at least my phone is usable now.
laufersteppenwolf said:
Well, bad news I guess... I tried whatever I could possibly think of, but the best I get is a steady red LED for some time, after that the LED turns off again and still no reaction at all (also while the LED is lit).
From what I can tell, it's most likely a battery issue, because when the red LED first lights up, it's kind of a flickering, which is why I assume the voltage is just too low to do anything.
We'll see what Sony's gonna tell us after they got the device for repair
Click to expand...
Click to collapse
Well, This sudden death phenomenon happened to me as well this weekend, without any prior warning, since the phone is just 5 weeks old. I tried every possible fix suggested on the web, no response at all.
Now the phone has been shipped to a service centre in Athens, Greece, 350 km from where I live. Ought to have an update on phone;s status in approx. 10 days I was told. I keep my fingers crossed... From what I've read searching this matter during these past days, it seems more like a hardware issue (i.e. defective motherboard). If that's true, and since this phenomenon tends to grow steadily like an epidemic all around the globe (first SE Asia, now Europe) than it is a disgrace for SONY not to organize a recall...
Same issue here. Started few times and then hard brick. No flash mode, no fast boot, no charging... The girl from Sony support, after I've told her that i have an issue reported by many user on their support forums told me not to believe everything I see on the internet . I've been a Sony fan for many years but this denial of a manufacturing fault will make me reconsider...
This has been happening to me regularly now. The only way to get it to boot is to leave it on a charger for an hour or two. After an hour it will say it's charging again. Once it shows that it's charging, you can power it on. Pretty annoying, especially because when this happens to me, the battery will usually be over 90% full.
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
bilboa1 said:
So I got the black screen of death issue and I think I solved it.
My internal nand was pretty full (got the warning several time). Eventually, the screen turned black one day and the phone wouldnt turn back on, even with
- reboot power/volume combo
- reset button behind the flap (30s+)
- charger connected/disconnected with same buttons
Leaving the phone there for a day or two (trying to boot it every now and then with the power button...), eventually it works/boots for some magical reason. Then it goes black again for a day or two, sometimes quickly, sometimes not. I did that a few times over several days...
Eventually when I got it to boot again I directly did a factory reset. This does not clean the internal sdcard. Things worked for a week straight (ie longer than usual) and bang, black screen again, and again and again...
So when I got it to boot once again (yes, that's PAINFUL to test all this) I did a factory reset + wipe of the internal sdcard.
Since that day, no more black screen of death.
I therefore suspect there's a bug with the nand controller when its nearly full or is full, or there's a bug plus bad nand hardware that causes it. I'm a little clueless on why it can eventually reboot.
I tested this 20, 30 times just to be certain, and it really seems related. So now I'm curious, any of you with the problem had the internal nand nearly full ? (or above 75% full at least). If so, try to boot the phone again a bit later and remove files from the sdcard just to see.
Click to expand...
Click to collapse
My internal and external storage are both only half full and the sudden death bug continues to happen. Not sure it's related to storage. I've noticed that it only happens to me when the phone is sleeping with the screen off. I know sony did a lot of work to get the phone to use very little power when idle. Maybe it's related to the phone not being able to wake up? Does anyone know if this happens with non-stock ROMS as well?
penske said:
This has been happening to me regularly now. The only way to get it to boot is to leave it on a charger for an hour or two. After an hour it will say it's charging again. Once it shows that it's charging, you can power it on. Pretty annoying, especially because when this happens to me, the battery will usually be over 90% full.
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
My internal and external storage are both only half full and the sudden death bug continues to happen. Not sure it's related to storage. I've noticed that it only happens to me when the phone is sleeping with the screen off. I know sony did a lot of work to get the phone to use very little power when idle. Maybe it's related to the phone not being able to wake up? Does anyone know if this happens with non-stock ROMS as well?
Click to expand...
Click to collapse
Started happening to me a couple of weeks ago. Currently on SlimRom 4.4 and have been using this ROM for about a year now.
I was actually about to reflash a stock ROM until I saw this thread and now I don't know. Might have to call Sony.
Hi
I have a OnePlus 3T stuck on 50% battery it doesn't go up or down, I tried letting the battery drain and then restarting, but it still displays 50% even after factory reset.
Is this a problem that can be resolved? I am not sure what else to try, I tried battery re-calibration apps and charging the phone a few times etc. but it did not work.
Hope you can help.
Thanks
Infinite Battery life? COOL!
Or did you mean the Indicator is stuck on 50% even when the Battery itself runs out and dies? If that, i can see it being an issue. We should start with the basics. What ROM? Bootloader state? Recovery? Kernel? Firmware? Mods? Length of time since last clean install. etc.
A Factory Reset seems like a good first step for now.
Haha, yes the indicator is stuck on 50%.
If I let it run out then recharge fully as they say to do to recalibrate, then even doing this overnight, it is still (apparently) charging in the morning - so I turn it on and it is still the same thing stuck on 50% and not recalibrated (if calibration is indeed the problem).
I moved to Lineage OS 15.1 (OFFICIAL) using latest TWRP recovery. Bootloader is unlocked.
It is now back on stock (latest build downloaded from oneplus) after full wipe of data/cache/dalvik, with stock recovery (bootloader still unlocked). The problem remains.
So as you can see a factory reset did not work I am afraid.
sumade said:
So as you can see a factory reset did not work I am afraid.
Click to expand...
Click to collapse
When it's been on charge long enough that it should have fully charged, it's still showing 50%, right? If you use it long enough to discharge completely, are you getting half the Battery life? (This is the difference between the indicator being faulty and the Battery being faulty).
If the indicator is correct and the Battery is refusing to charge beyond 50%, that's your Battery about to die. Send it to Oneplus for a replacement.
Thanks, yes if I leave it on overnight or otherwise more than enough for a full charge, it shows 50%. It is difficult for me to say if it lasts a full charge as I only just purchased the phone, so I have nothing to compare to.
However, the indicator does not slowly increase to 50%. I can fully discharge the phone until it turns off, and whilst doing so the indicator stays at 50%. I then go to charge the phone whilst turned off, and it doesn't matter how long I charge it for, almost always I turn it on and it is stuck at 50% (very rarely it looks like it's working, it starts lower and the level even seems to increase a few percentage points, going to say 15%, then it stops and I wait a while until it is clear it is not going to change, and eventually restart the phone, turn it back on and it's the same old deal, stuck at 50% no matter what).
I am not sure if this is very helpful, it's difficult to describe, I guess the bottom line is, no matter how long or little I charge it, almost always I turn it on and it is stuck at 50%, which made me think it was some sort of indicator problem, but I am not sure. I guess I should try and send it back as there's clearly a problem and I have tried reasonable steps to resolve.
Probably battery is fried
Damn, that's a shame, if that's the case I guess I should send it back then (although I can see the seller disputing it, I've barely used the device and it doesn't seem to be resolvable so I don't have a choice really).
I suppose I will rebuy OnePlus 3T unless there is an alternative, wasn't happy with recording quality which is a shame as I like to record guitar/singing, but everything else seemed great - I guess a new Xiaomi is another option as no trouble with battery, but I hear recording quality not so good.
sumade said:
Damn, that's a shame, if that's the case I guess I should send it back then (although I can see the seller disputing it, I've barely used the device and it doesn't seem to be resolvable so I don't have a choice really).
I suppose I will rebuy OnePlus 3T unless there is an alternative, wasn't happy with recording quality which is a shame as I like to record guitar/singing, but everything else seemed great - I guess a new Xiaomi is another option as no trouble with battery, but I hear recording quality not so good.
Click to expand...
Click to collapse
I'm sure the seller was perfectly aware of this defect when they sold it. If the phone is in good condition otherwise, and if you got a good deal on it, you might consider getting Oneplus to service it. It's a gamble but it's still a great phone and a new Battery would give you at least two more good years with it. I'm sure we'll still be getting custom ROM support that long too.
Any other 3T you buy used now could face a similar issue any time soon and then you'd be in the same boat.
If it still has a warranty, then it's easily solved through official service.
If not, then if u bought it from a private seller, than good luck with convincing him about the problem
Sent from my ONEPLUS A3003 using Tapatalk
You need to have it serviced. I had that issue shortly after I purchased my 3T. I had tried all sorts of apps to see if it was charging and they all said it was, just not dash charging. Everything showed 50%, every app, any ROM, recovery, everything. Also, if I remember right, the battery wasn't exactly charging while plugged up, it just wasn't drawing juice from the battery. I know they replaced the motherboard but I can't tell you how much that would cost as it was under warranty.
if you are on OOS try *#808* check battery charging .if you get -40C its a problem with the motherboard
kopap said:
if you are on OOS try *#808* check battery charging .if you get -40C its a problem with the motherboard
Click to expand...
Click to collapse
You mean *#808#
Sent from my OnePlus3T using XDA Labs
I had this issue just recently. See if the message "battery temperature is too low" appears when you try to charge when the phone is off. If yes you either have a broke battery or motherboard.
I had to get a replacement motherboard and battery to get my issue fixed.
BillGoss said:
You mean *#808#
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
yea sorry *#808# and check under charger
FIX
Did you fix it?
I had the same problem and fixed it by flashing a new KERNEL, is not battery issue nor mother board just flash a diferent KERNEL bro, hope it helps
vseehua said:
I had this issue just recently. See if the message "battery temperature is too low" appears when you try to charge when the phone is off. If yes you either have a broke battery or motherboard.
I had to get a replacement motherboard and battery to get my issue fixed.
Click to expand...
Click to collapse
Same problem facing by me to
Gigiomd said:
Did you fix it?
I had the same problem and fixed it by flashing a new KERNEL, is not battery issue nor mother board just flash a diferent KERNEL bro, hope it helps
Click to expand...
Click to collapse
For oxy? On custom roms used holy kernel
There are 3 possible solutions for this issue.
1: replace battery.
2: change the ROM for one that changes the Kernel for a version without this temperature protection.
3: fix or replace the main board.
To fix the main board you need to check 2 things on it.
On the left side of the battery connector (under a double sided glue tape foam), there are some SMD. The lowest two are related with this problem. I fix my board resoldering the one on the right (nearest to the connector). Be aware that the SMD is small and when are desoldered, it gets sticked on the double sided glue tape foam. I took a picture of it, but i don't know how to insert here.
If someone is reading this thread today and wants to know the solution,
This problem occurs when battery wire is connected loosely to motherboard or that connector has gone bad.
It has nothing to do with ROMs, kernel etc non-sense.
It's true, had the same problem after switching the battery of my OnePlus3T.
After reopening the device and reattaching the cable by CAREFULLY using more pressure and using a bit duct tape to fixate everything, it worked just fine.
Charging now works as it's supposed to and I'm again able to see the actual charge level.
Thanks lockhrt999!