Database Users

TOUCH HD keeps turning itself off

Hi Guys, i have a strange Problem since a couple of days.
The touch HD turns itself off after some minutes. I have to take out the battery and put it back in, otherwise it will not turn on...
i have:
- deactivated automatic shut down in power settings
- deactivated today timeout
- tried hardreset
- tried another rom (currently dutties final)
no success :-(
i have absolutlely no clue what could cause this and how i can fix it...
help is highly appreciated.

hello there , actually maby its a virus or there is problem in SPL
Try to install again the SPL modified and tell me
best regards
ms4cah

unlikely it has anything to do with SPL. it was fine for months, i had not flashed or installed anything.
it seams dead now by the way. i cannot turn it on again.
i also tried a new battery. it doesnt even charge, no light at the power button. nothing.

Surrido said:
unlikely it has anything to do with SPL. it was fine for months, i had not flashed or installed anything.
it seams dead now by the way. i cannot turn it on again.
i also tried a new battery. it doesnt even charge, no light at the power button. nothing.
Click to expand...
Click to collapse
Sounds like a warranty claim

I am getting the same problem!! is there anything i can do to fix this? anyone figured out the reason?

I had this sort of problem.
The HD would hang, then switch off, then to get back on I had to remove the battery for a while. Sometimes it worked after a minute, other times I had to leave the battery disconnected for longer.
So I performed a hard reset and it switched itself off during boot (after successfully resetting).
Battery out for a while.
H/R once more. Again crashed during boot but not at the same point as previous.
Tried a different battery with a full charge - same result.
Tried to re-flash a "very popular" custom ROM with USPL. Got to 1% and error. This was because the HD had crashed..
Tried to flash the official HTC ROM and it got to 15% and error. HD crash.
So I have contacted HTC and they are sending a courier to collect it so they can take a look with a view to repairing it.
The last ROM I successfully loaded about 2 weeks prior to the start of my problems was a custom win mo 6.5 rom. As I couldn’t get it to a stable state - I couldn’t flash the official HTC ROM.
I’ve convinced myself it’s a hardware fault rather than any software damage..
Although I fear I’ll be in for some bad news.

mine too
Hi,
I have the same problem.
Mine was doing hard reset and after a day or two the same problem.
Now I cannot turn it on.
I will send it to htc...
Crossing my fingers.

I had the same problem with mine...
While turned on, it automaticly tryed to turn of, as if something was pressing the on/off buttom. Everytime that message for turning it off poped up and I just couldn't control the on/off button anymore.
I tryed everything and nothing worked. It really seemed a hardware and warranty claim issue. However, since I bought it abroad and it does not have warranty here in Brazil, I just decided to sell it (obviously warning the buyer about the issue) and to buy another one (which is working as a charm).
It is a hardware issue, for sure...

So my HD has been away at HTC for nearly a week, and im currently tracking its return journey, due to land back here at some point this morning.
I have had no contact from HTC so its going to be a suprise as to whether anything has been repaired.
My hope was they couldn't turn it on at all - thus replacing the bits n bobs inside, replacing the main board containing my 6.5 ROM.
So for now im hoping "no news will be good news", but I will update this when I have it back.

... I've the same problem...
Hi, I've the same problem. Do you have any solutions?

Nasher79 said:
So my HD has been away at HTC for nearly a week, and im currently tracking its return journey, due to land back here at some point this morning.
I have had no contact from HTC so its going to be a suprise as to whether anything has been repaired.
My hope was they couldn't turn it on at all - thus replacing the bits n bobs inside, replacing the main board containing my 6.5 ROM.
So for now im hoping "no news will be good news", but I will update this when I have it back.
Click to expand...
Click to collapse
Just recieved delivery. The service report states:
1. Diagnosis
2. Replace Main Board
3. Function Test
Result
Confirms it was a H/W fault and my "flashing" did not effect the warranty status. That may have been because they couldnt get far enough to confirm so.

Mega75 said:
Hi, I've the same problem. Do you have any solutions?
Click to expand...
Click to collapse
Other than a Warranty repair, im afraid not. Try your best to get it back to HTC official software, then report it as no power / cant boot.

Nasher79 said:
Just recieved delivery. The service report states:
1. Diagnosis
2. Replace Main Board
3. Function Test
Result
Confirms it was a H/W fault and my "flashing" did not effect the warranty status. That may have been because they couldnt get far enough to confirm so.
Click to expand...
Click to collapse
Good to know, confirmed h/w issue

i simply deactivated automatic shut down in power settings as mentioned in the first post and unistalled a couple of new programs i had recently installed!!
Not quite sure which of the above worked.. but atleast for now it seems to be working fine!! the screen has not turned off by itself and i have not had to remove battery etc to get it to work again!
I'm not quite sure if the problem is properly fixed but it has been a few days since anything occurred!! so fingers crossed!!

mine was doing this last tuesday, each time i went into my pocket for it, it was turned off, then i hard to do the reset pin or remove the battery, it has been ok since, i just thought, maybe it was me, pushing it in my jeans i might be turning it off.
also using duttys popular 6.5 latest rom, i dont think its fair to blame his rom, as mines ok now, maybe i should reflash it again?? im still waiting for a new version to be released.... JESUS!!! just looked it up to r12, im on r9 .
oh no... no it not..... says to go here, and it will be released here and not on dutty throy???
http://htcpedia.com/forum/forumdisplay.php?f=79

iamdarren said:
mine was doing this last tuesday, each time i went into my pocket for it, it was turned off, then i hard to do the reset pin or remove the battery, it has been ok since, i just thought, maybe it was me, pushing it in my jeans i might be turning it off.
also using duttys popular 6.5 latest rom, i dont think its fair to blame his rom, as mines ok now, maybe i should reflash it again?? im still waiting for a new version to be released.... JESUS!!! just looked it up to r12, im on r9 .
oh no... no it not..... says to go here, and it will be released here and not on dutty throy???
http://htcpedia.com/forum/forumdisplay.php?f=79
Click to expand...
Click to collapse
FYI, Throy is releasing roms exclusively to HTCPedia now, so no future roms will be released on either XDA or www.duttythroy.com

wow!!! i never knew!!!! thats crazy as his own site duttythroy wont be used.
im getting it now, but only 11 when it says 12 is out, either way, i will still flash i love the roms, i will be sure to be on all the site, incase theres another change of heart??
anyway guys i will report if i noticed the shutdown thing happening again with the version. 4mins till downloaded.....

I think theres a couple of different issues here. My own problem was due to faulty parts in the hardware itself. Absolutley nothing to do with any ROM, only reason I mentioned them was because of the invalid warranty possibility.
If your problem was ROM related, Im sure in the relevant ROM thread, there would be many people (everyone) with the same issue. Thats not to say that its not some sort of conflicting software you may have installed after the ROM flash.
Some simple troubleshooting steps:
1. Hard reset - If it still has a problem...
2. Flash Official HTC ROM - If still a problem...
Phone HTC.
All the best, hope you manage to get something to work for you. I know how lost I felt without mine!

Nasher79 said:
I think theres a couple of different issues here. My own problem was due to faulty parts in the hardware itself. Absolutley nothing to do with any ROM, only reason I mentioned them was because of the invalid warranty possibility.
If your problem was ROM related, Im sure in the relevant ROM thread, there would be many people (everyone) with the same issue. Thats not to say that its not some sort of conflicting software you may have installed after the ROM flash.
Some simple troubleshooting steps:
1. Hard reset - If it still has a problem...
2. Flash Official HTC ROM - If still a problem...
Phone HTC.
All the best, hope you manage to get something to work for you. I know how lost I felt without mine!
Click to expand...
Click to collapse
Your exactly right. Some people experience similar symptoms which are rom related others have same problem which is hardware related. One can only be fixed by HTC as motherboard problem, other can be rectified by different means without having to send device back for repairs

Hi again,
Today I have received an sms from HTC service informing me that my HD has a circuit problem and they will fix it without any charge.
I have to wait.

Nexus 6p Won't Start (Suspected Hardware Failure)

My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.

someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?

v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken

someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.

someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.

No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation

someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.

v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|

If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?

someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.

I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...

BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?

I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget

someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.

I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?

someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.

I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?

someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty

I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..

NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.

Bricked beyond repair?

So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.

Just to rule out the obvious, have you tried different cable and computer?

gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.

godraistlin said:
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
Click to expand...
Click to collapse
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.

How did you brick your OP in the first place? Does it still charge?

Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.

gabriwinter said:
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.

The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.

godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.

Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.

Did you try holding power button for >40 seconds?

godraistlin said:
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.

After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.

dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

GAMIT PRUTHVI said:
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

gabriwinter said:
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

jhs39 said:
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.

No sound after upgrade to Andriod 11

So I have a china mode IN2020 that was working great.
I am in the US.
After One Plus sent down an upgrade to Andriod 11 I started had issues with the phone.
The text messages took forever to load and trying to send them was a waste of time. I changed the text message program and solved that issue.
Then the phone starts doing weird things, I would go to dial and it would just right back to the phone screen, programs crashed, etc.
The last problem was the phone now is useless the speaker (does not matter if I use the speakerphone, earpiece or Bluetooth) Is DEAD during a call. the person on the other end of the call hears me fine but, I hear nothing.
One plus says it is because of the motherboard not working with the US upgrade.
They want to charge me $350 to replace it with a US version.
I have since flashed it back to Andriod 10 and again it works perfectly.
I have also tried TWRP to flash to a custom ROM but the phone will NOT flash.
I get errors like wrong Andriod version or a check sum error occured.
Any help or suggestions...
thanks!!

If / when you upgrade to 11 I would highly recommend a factory wipe afterwards..
Jumping between bases causes issues and a wipe fixes them, at least in my case.
It's like jumping between ROMs, always best to have a fresh start.. 10-11 isn't any different, it's possible a mod may have caused it.
So if you had viper running on 10 then you updated to 11 and didn't disable it it could have borked it, or there could have been left over remnants of it left behind..
Again a wipe would help here

I was/am running stock ROM.
and thanks but I did do a factory reset.
dladz said:
If / when you upgrade to 11 I would highly recommend a factory wipe afterwards..
Jumping between bases causes issues and a wipe fixes them, at least in my case.
It's like jumping between ROMs, always best to have a fresh start.. 10-11 isn't any different, it's possible a mod may have caused it.
So if you had viper running on 10 then you updated to 11 and didn't disable it it could have borked it, or there could have been left over remnants of it left behind..
Again a wipe would help here
Click to expand...
Click to collapse

Sirtronicsskg said:
I was/am running stock ROM.
and thanks but I did do a factory reset.
Click to expand...
Click to collapse
How did you update the phone? Via system?
Grab oxygen updater and get it from there.
No reason why it shouldn't work

the phone updated automatically (via One Plus)
but after that did not work i downgraded it to 10 and then tried it again with the same result.
My understanding is the phone has a different motherboard, it is an IN2020.
They say it runs a different os...
dladz said:
How did you update the phone? Via system?
Grab oxygen updater and get it from there.
No reason why it shouldn't work
Click to expand...
Click to collapse

Sirtronicsskg said:
the phone updated automatically (via One Plus)
but after that did not work i downgraded it to 10 and then tried it again with the same result.
My understanding is the phone has a different motherboard, it is an IN2020.
They say it runs a different os...
Click to expand...
Click to collapse
The board strictly speaking shouldn't mean you don't get audio? That's just wrong..
Personally I haven't used the Chinese version of the 1+8pro but if an update is available then it should accept it correctly.

I agree, BUT they told me to send it it for a repair and if they replace the motherboard it will cost me $350.When i said the update should work no matter where i am the answer i received was if you are in the US and get that update it can cause issues.
dladz said:
The board strictly speaking shouldn't mean you don't get audio? That's just wrong..
Personally I haven't used the Chinese version of the 1+8pro but if an update is available then it should accept it correctly.
Click to expand...
Click to collapse

I don't think there's anything wrong with the update itself, I highly doubt it, but you can try downloading the update from Oxygen Updater and install it again, make sure you factory reset right after finishing.
If it doesn't work, then I think it might be something with your hardware, couldn't be something else I suppose

Ys I did that also and same result.
It this phone goes to Andriod 11 it has the speaker issue, No matter how it gets there..
TickedBid said:
I don't think there's anything wrong with the update itself, I highly doubt it, but you can try downloading the update from Oxygen Updater and install it again, make sure you factory reset right after finishing.
If it doesn't work, then I think it might be something with your hardware, couldn't be something else I suppose
Click to expand...
Click to collapse

Sirtronicsskg said:
I agree, BUT they told me to send it it for a repair and if they replace the motherboard it will cost me $350.When i said the update should work no matter where i am the answer i received was if you are in the US and get that update it can cause issues.
Click to expand...
Click to collapse
They're wrong, just putting that out there.
So what are you meant to do?
Are they suggesting if you were in the devices homeland then it would work?
If so just use a VPN, install it and prove them wrong because they're chatting bubbles.
They ought to just fix it.

I already had this "fight with them"
got this today
Greeting from OnePlus.
This email is regarding your repair request RMA# OP202012290204583075 for OnePlus 8 Pro.
I see that you have created a repair request for the OnePlus 8 Pro device due to the earphone malfunction. We certainly understand the need and importance of having the device working in an optimal condition. We are here to assist you.
We would like to keep you informed that we will be able to repair all components apart from the motherboard. After inspection, if we find it to be an issue with the motherboard we will be unable to proceed further with the repair as it is a Chinese version and due to region difference and unavailability of the motherboard, the device will be sent back without repair.
Also, we are glad to inform you that we have approved your repair request. If you would like to continue with the above repair options you can follow the shipping instructions and send the device for repair. If not, you can revert us so that we can get the repair request canceled.
this is BS!!!
dladz said:
They're wrong, just putting that out there.
So what are you meant to do?
Are they suggesting if you were in the devices homeland then it would work?
If so just use a VPN, install it and prove them wrong because they're chatting bubbles.
They ought to just fix it.
Click to expand...
Click to collapse

Sirtronicsskg said:
I already had this "fight with them"
got this today
Greeting from OnePlus.
This email is regarding your repair request RMA# OP202012290204583075 for OnePlus 8 Pro.
I see that you have created a repair request for the OnePlus 8 Pro device due to the earphone malfunction. We certainly understand the need and importance of having the device working in an optimal condition. We are here to assist you.
We would like to keep you informed that we will be able to repair all components apart from the motherboard. After inspection, if we find it to be an issue with the motherboard we will be unable to proceed further with the repair as it is a Chinese version and due to region difference and unavailability of the motherboard, the device will be sent back without repair.
Also, we are glad to inform you that we have approved your repair request. If you would like to continue with the above repair options you can follow the shipping instructions and send the device for repair. If not, you can revert us so that we can get the repair request canceled.
this is BS!!!
Click to expand...
Click to collapse
Tbh pal they wouldn't have Chinese boards there.
I honestly cannot see them doing any ad-hoc soldering, so if taking it apart and putting it back together doesn't fix it or changing the earpiece and speaker modules then they'll send it back.
Give it a shot there not much you can do.
How come you bought a Chinese version? Cost?

I'm not going to send it in because it is a motherboard component issue that happened only with Andriod 11, so why waste my time and be without a phone.
I honestly got it as a gift and did not know it was the in2020.
dladz said:
Tbh pal they wouldn't have Chinese boards there.
I honestly cannot see them doing any ad-hoc soldering, so if taking it apart and putting it back together doesn't fix it or changing the earpiece and speaker modules then they'll send it back.
Give it a shot there not much you can do.
How come you bought a Chinese version? Cost?
Click to expand...
Click to collapse

Sirtronicsskg said:
So I have a china mode IN2020 that was working great.
I am in the US.
After One Plus sent down an upgrade to Andriod 11 I started had issues with the phone.
The text messages took forever to load and trying to send them was a waste of time. I changed the text message program and solved that issue.
Then the phone starts doing weird things, I would go to dial and it would just right back to the phone screen, programs crashed, etc.
The last problem was the phone now is useless the speaker (does not matter if I use the speakerphone, earpiece or Bluetooth) Is DEAD during a call. the person on the other end of the call hears me fine but, I hear nothing.
One plus says it is because of the motherboard not working with the US upgrade.
They want to charge me $350 to replace it with a US version.
I have since flashed it back to Andriod 10 and again it works perfectly.
I have also tried TWRP to flash to a custom ROM but the phone will NOT flash.
I get errors like wrong Andriod version or a check sum error occured.
Any help or suggestions...
thanks!!
Click to expand...
Click to collapse
I am having this same issue with the IN2020 version.
What files are you using to go back to Android 10?

Screen dead + Front camera keeps trying to open

Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.

Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.

XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.

Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.

XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?

angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/

XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha

angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.