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.
Related
Hi guys,
Tried searching for my problem, but though I found some similar stuff, noone had quite my problem.
I was checking my Nexus S after a trip and it was with the 'emergency only' message. This sometimes happens to me, not sure if it's due to the roaming activation or caused by a bug where the radio subsystem crashes after a long period without network.
Anyway, I proceeded to my common solution: Turn off and reboot.
Except that after the phone was off, it would not turn on.
It doesn't even vibrate. It doesn't show anything when connected to the wall socket or to the computer. It's just completely dead.
Now, I'm not even sure if this is a hardware or software problem. Any idea on how I can debug this?
Here's what I've tried:
1. Take the battery out: no changes (even tried leaving it out overnight).
2. Charge the phone overnight: no change.
Next step: I'll go to a store and try a different battery... meanwhile I'm without my primary phone which sucks... Can anyone help?
Thanks in advance!
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
If it is not the battery, i can see what else you can do, a "dont turn on" phone is a dead end...
Sent from my Nexus S using XDA App
Guess I'm screwed... I had some pics and other data there... anyway I can get it back? i.e. is there a way to remove the internal sd card?
saranyan said:
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
Click to expand...
Click to collapse
Was this tried? Cause if that works there's hope for you yet.
BlackHawkA4 said:
Was this tried? Cause if that works there's hope for you yet.
Click to expand...
Click to collapse
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
nunocordeiro said:
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
Click to expand...
Click to collapse
Sounds like something is wrong with the hardware then. Have you brought it the store? Might need to get a new one on warranty.
I have the same issue with my old Blackberry 9000. It worked fine up until I stopped using it. Left it in a drawer for a few months. Went to sell it to Sprint. Wouldn't turn on. No LED, no nothing. Worked fine months before when I was still using it. To this day I have no idea what's wrong with it and it doesn't turn on.
Why not get an external battery charger and charge the battery up and then test it?
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
If you can get to download mode nothing is lost. Just flash new image via Odin.
Sent from my GT-I9000 using Tapatalk
nunocordeiro said:
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
Click to expand...
Click to collapse
Never heard of that happening, but it's a possibility... Still, I would first attribute it to a bad battery and try that first
Sent from my Nexus S 4G
With a new battery (that works on another nexus S) still no luck. =(
I still can't find anyone with this problem. I feel like the unluckiest idiot on Earth.
I assume I can't get to download mode since I can't even get the phone to report it is charging (it used to do that even if off). Do you want me to try anything, though? I'm open to suggestions until Monday. Then I'm taking it to Samsung. Hope they can recover my pictures.
BTW, my receipt doesn't have the IMEI and a customer service rep told me I need it on the receipt or they won't give me free support. How can I get it with the phone off?
Regards and thanks to all who responded,
Nuno
nuno, if you cant power on even with a new charged battery, then it's a harware fault and nothing can me done... =o\
but thanks for the advice, i never thought about the data in sd card, i guess i should make some backups! =o)
nun
BTW said:
Look under your battery. IMEI should be printed on the sticker beneath. Good luck!
Click to expand...
Click to collapse
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
odd things can happen ... it sucks
igorgatis said:
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
Click to expand...
Click to collapse
Did you try flashing a different rom? Or radio/
I haven't experienced this myself but I'm very interested on what happened. Did you guys flash any custom ROMS? or Radios for that matter?
This looks very similar to what i have. I just got my nexus s GT-i9023, it doesn't boot into fast boot, recovery, download mode or normal. The most activity i have got so fare is when i take the battery out, put it back it, and try turn the phone on it will sometimes flash then do nothing. I have looked every ware. When i use "./platform-tools/adb get-state" it returns "unknown". Any help would be great.
What i think i did was this:
- Unlocked bootloader, this worked
- restart
- installed clockwork mod with fast boot, this worked
- wiped data
- wiped cache (correct me if i spelt that wrong, or anything else)
- flashed cyanogenmod, this got an error but i didn't notice it the first time and i can't remember what it was.
- flashed gapps, this didn't work, when i restarted the phone it said that the installer for gaps had quit.
- restarted
- flashed cyanogenmod again, this is when i noticed the error
- restarted, didn't change anything
- wiped data
- wiped cache
- flashed i9020t recovery, this http://forum.xda-developers.com/showthread.php?t=1061855 i think this is what stuffed it up because my phone is i9023
- wiped data after flashing, thats what it said to do, i thought it was strange but i went along with it.
- wiped cache
- reboot
- now doesnt work.
Take it to the store where you purchased and claim ignorance!
Good morning all,
my 6p looks completely dead. I've installed the latest Android O factory image from the Google Developer site, flashed it and was running withot issues until today.
I was about to write a comment on Facebook, and then the phone freezed. After seeing how the phone was not recoverying, I tried a hard reset by long-pressing the power and both the volume keys. Then, the phone got a black screen, didn't vibrate, and now looks totally dead.
It's not charging or responding in any way, no matter how I press it. I'm quite confident the phone was over 50% when this issue occurred.
I don't really know what coul've caused this, but on my side, the preview was flashed cleanly with a complete factory reset, and I've only restored media files, without rooting.
Any ideas as to what should I do?
Do you get anything showing up on a computer when you plug it in?
jmaclean62 said:
Do you get anything showing up on a computer when you plug it in?
Click to expand...
Click to collapse
Hi jmaclean, nothing, not even in Windows Device Manager...
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Zwitterion said:
I thought the Galaxy Nexus was a disaster but it appears that the 6P isn't far behind. Just bought a 6P (thankfully, a mint refurb) and am wondering if I made a bad mistake?
Click to expand...
Click to collapse
Yes a bad choice I would say - as an owner of a Nexus 6P device currently awaiting repair (thank god I'm in warranty) - I can tell you this device is plagued with issues that only become apparent as soon as your warranty is approaching expiry.
I love the phone, the design and build quality aesthetically speaking but would never be buying from Huawei again. The device is plagued with poor design that people believe leads to the CPU failing for some odd reason causing the dreaded bootloop issue.
My phone died literally in front of me and never worked again. I've contacted Huawei to get some clarification if this is an inherent fault as thousands are complaining about it and they just plain deny it and maintain if the warranty expires your out of luck. Apparently fixing the bootloop requires a motherboard change which in itself costs over $200 apparently. May as well get another phone for that as even the replacement component will eventually fail!
Sounds like a power issue. Maybe there's an open at the power switch or bad battery connector or battery. It most likely is nothing to do with Android oh it's just a coincidence. If you would have not even flashed Android O it would have still done this
seems like you will need to open up your nexus and unplug the battery, and then put everything together and try
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
paracha3 said:
I have owned this 6p for over 18+ months now. Never had any bootloop issues since day 1. A week ago i loaded factory image of Android O to this phone everything was working fine with great battery life.
I do not know if this is a coincidence with OP but i was also on facebook (chrome webapp) when during freshing of the page, the phone rebooted and since then it is stuck in bootloop.
I have connected to PC and reloaded the oreo stock image again and it completes successfully but again goes into bootloop. Any idea what should i do??
Click to expand...
Click to collapse
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
murphyjasonc said:
Follow the bootloop fix guide. I believe it's in the general or q and a section. It shuts down the big cpu cores but will get your phone going again. It worked for me. I was able to boot up and get some files off that hadn't been backed up yet. I was also able to use my phone until my RMA arrived.
Click to expand...
Click to collapse
Yes I was able to apply that and got it to work. Thanks
Yesterday, after a few hitches, I installed twrp 311 and then RR and immediately switched to AOSPE. Now in having the issues described in the title. It might be relevant that the handset got a little wet, but it's gotten wet before and nothing's happened. Could it be a software issue? A hardware issue? A coincidentally timed buildup of dust? Other people have similar issues, but as far as I've seen nobody has had a phone that seems to have a broken USB port except when the phone turns off. Also, the charging connection breaks when I jiggle the cable in the port, which might be relevant.
Halp
Try charging with another USB cable and report. Avoid charging through power banks, they can cause such issues.
william.johhn7! said:
Try charging with another USB cable and report. Avoid charging through power banks, they can cause such issues.
Click to expand...
Click to collapse
I guess I should have added that I tried all the usual stuff. Multiple wall chargers, multiple cables, including a power-only cable, and I've never had any issues with this or other power banks, but it's possible. I'm still leaning towards/hoping that it's a software issue brought on by my flashings.
westinator said:
I guess I should have added that I tried all the usual stuff. Multiple wall chargers, multiple cables, including a power-only cable, and I've never had any issues with this or other power banks, but it's possible. I'm still leaning towards/hoping that it's a software issue brought on by my flashings.
Click to expand...
Click to collapse
Well, power banks has affected my device resulting to what you're facing now. So I don't use them anymore. Try fastboot back to miui. See if the issue persists. If it does, approach the service center. If the port's damaged, then they'll probably replace the sub-board which can cost you around 30% the cost of the device. And if you're under warranty period, you'll be lucky to get it replaced for free.
william.johhn7! said:
Well, power banks has affected my device resulting to what you're facing now. So I don't use them anymore. Try fastboot back to miui. See if the issue persists. If it does, approach the service center. If the port's damaged, then they'll probably replace the sub-board which can cost you around 30% the cost of the device. And if you're under warranty period, you'll be lucky to get it replaced for free.
Click to expand...
Click to collapse
Alright thanks for the advice, I'll try a different ROM... Will switching back to miui relock my bootloader?
westinator said:
Alright thanks for the advice, I'll try a different ROM... Will switching back to miui relock my bootloader?
Click to expand...
Click to collapse
Offficial stable?(I hate it) I don't know. Forked version(Better than official miui)(Xiaomi.eu, multirom, miuipro) won't.
william.johhn7! said:
Offficial stable?(I hate it) I don't know. Forked version(Better than official miui)(Xiaomi.eu, multirom, miuipro) won't.
Click to expand...
Click to collapse
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
westinator said:
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
Click to expand...
Click to collapse
Flashlight doesn't work in miui roms but works for custom ROMs?! very odd. Try wiping battery stats through twrp. And the last hope to get it working is by fastboot flashing. If that doesn't help, the device needs to be serviced. There must be some local centers that services Xiaomi products.
Anyways forwarding your matter to others(A telegram group consisting of other users and developers). Lets see if they can help.
westinator said:
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
Click to expand...
Click to collapse
Flash global stable ROM in edl mode, for me thats the only way to be sure that it's not software
It wont lock the bootloader
bekcicandrej said:
Flash global stable ROM in edl mode, for me thats the only way to be sure that it's not software
It wont lock the bootloader
Click to expand...
Click to collapse
It fixed it!
Some things happened between my last post and the problem fixing itself:
I think I put my phone into edl mode, but rebooted it because I had to go and didn't have time to flash miui
My corrupted samsung sdxc, that I should have mentioned before, was somehow fixed by xiaomi.eu when aospe and rr couldn't fix it
My phone restarted in my pocket when I didn't tell it to - I discovered this when I was prompted to decrypt it at boot
I tried to allow adb in dev settings, but it failed with the error message "your device is temporarily restricted" or something like that
With hopeful/wishful heart, I plugged it in after getting back from a meeting, and everything seemed to work connection-wise (???? don't question, just be grateful I guess). I reflashed AOSPE because I like it better than any other ROM I've tried, and not only did the usb port continue to function normally, but the flashlight started working again!
I guess I'll make monthly sacrifices to the deity of smartphones, or maybe to that xiaomi bunny.
Problem Solved, and thanks for all of your effort. Maybe the suggestions helped! Who knows...
westinator said:
It fixed it!
Some things happened between my last post and the problem fixing itself:
I think I put my phone into edl mode, but rebooted it because I had to go and didn't have time to flash miui
My corrupted samsung sdxc, that I should have mentioned before, was somehow fixed by xiaomi.eu when aospe and rr couldn't fix it
My phone restarted in my pocket when I didn't tell it to - I discovered this when I was prompted to decrypt it at boot
I tried to allow adb in dev settings, but it failed with the error message "your device is temporarily restricted" or something like that
With hopeful/wishful heart, I plugged it in after getting back from a meeting, and everything seemed to work connection-wise (???? don't question, just be grateful I guess). I reflashed AOSPE because I like it better than any other ROM I've tried, and not only did the usb port continue to function normally, but the flashlight started working again!
I guess I'll make monthly sacrifices to the deity of smartphones, or maybe to that xiaomi bunny.
Problem Solved, and thanks for all of your effort. Maybe the suggestions helped! Who knows...
Click to expand...
Click to collapse
Glad to hear the good news.
FYI I flash miui in edl on a bi-monthly basis, just to refresh the partitions
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.
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.