I decided to start a thread because I noticed there were multiples about this issue. So 3 days ago I was on Facebook when my phone randomly froze. I pushed the power button, and that's when it began bootlooping. I instantly tried booting into recovery with no success. I was hopeful, however, because I could still access the bootloader. I got on my computer and began researching the issue and steps I could take to fix it. I tried every method out there and was unsuccessful. I ended up buying a Pixel today off Craigslist and am loving it so far. So anyway since my Pixel came with the OEM charger, and I had been using a non-oem ever since I had my 6P, I decided to plug in the OEM and see what happens. Within the first hour my 6P began to get very hot, almost to the point where I couldn't even hold it in my hand. Keep in mind the phone was still consistently boot looping the whole time. So I decided to unplug it. Well I left it sitting and went about my business and when I came back to my bed I noticed it was doing the Google boot animation!!!! I started freaking out! After it booted up I finished the tutorial stuff and just let it sit on the home screen for a second. I noticed the battery was low so I figured I would plug the charger back up and let it charge. Well in the time it has taken me to write this post, it just started boot looping again... Lol. So I just unplugged the charger AGAIN, to see if it will boot up again. To me, it seems like there might be a hardware issue with my battery. Anyway, my 6P was rooted and running nitrogen OS (wasn't running the latest build but was 7.1.)
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
dontbeweakvato said:
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
Click to expand...
Click to collapse
As of now it is still boot looping and no it doesn't boot into recovery. Only symptoms I've noticed is the phone starts to get extremely hot when I plug in the OEM charger that came with my Pixel. I figured they were the same so that's why I decided to use it since it was OEM.
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
dontbeweakvato said:
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
Click to expand...
Click to collapse
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
e1ement08 said:
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
Click to expand...
Click to collapse
my first bootloop years ago i thought the same.
it wont fix itself. its not a software isssue because youd be able to at least boot into bootloader. it sucks to hear the truth but thats the truth.
its a hardware issue and you could take it to a repair shop because they will inspect and fix. small drops that dont harm the device can ultimately cause small breaks in the solder joints so who knows what is wrong without inspection
Related
Hey guys,
I've done some searching on this issue, yet I can't find much besides battery problems, or people who have contacted T Mobile and got warranty replacements. I've had some issues with my G1. Over the past month or two, my G1 has been rebooting repetitively, and this week it's gotten BAD. I would open a SMS, and then BAM. Start dialer, and then BAM. Reboot. Hell, even in the middle of a reboot it would reboot. Cool huh?
Anyways I called T-mobile customer support and they said I'm out of warranty. Great. Well, it still turns on, and it still operates when it's happy, so maybe I can work with this for a little bit... I did some searching, and some people attributed it to a software glitch in the gyroscope... Most people called T-mobile and got a warranty replacement. I'm over the one-year
I'm not about to say this is because I had CyanogenMod on it, because I would wipe, and put it back to an older version and it would still reboot... even in the SPL, it would reboot. But regardless, I decided to follow this how-to to unroot my G1: http://forum.xda-developers.com/showthread.php?t=491350
After step 6 (6. Push Alt+S on your G1 to flash it with update.zip), it came up with an error about the splash... "Cant store hboot image."
Well anyways, before I could do anything about it, guess what happened?
Yeah, it rebooted.
It came up with the unboxing logo at first, I didn't know what to do. I had forgotten what this meant, so I heled the power button down ( I realize this may have been the misteak I made, however there was nothing visual indicating anything was being done).
It shut down, the screen went blank, the charge LED remained on....
I pressed power.... Nothing.
I unplugged the phone, took out the battery.... put the battery back in... Nothing. The screen stayed black. Now my phone will not power up, and there is no LED charging indicator.
Anyways, I'm lost. This is my second G1. I'm slightly pissed and I feel bad for the T-Mobile rep on the other end of the call I just had, but, really, I can't spend $1200 a year on a slow phone.
Do any of you guys have any suggestions?
Home+power does nothing.
Camera+power does nothing.
Putting in the cable lights up no LEDs...
It is literally a brick. An unresponsive brick.
Well, I ended up taking the mainboard out of my old phone and putting it in this G1.... Everything should be back to normal however I'm still looking for responses as to what might be happening.
Right I feel silly, knowing this I just couldn't resist trying to fix my "phone", so I've bought a S7 Edge from eBay from a trusted company with a 14 day refund which is good right?
We'll I couldn't rest as the phone was going into boot loops, i.e booting once every 5 times, going into the black screen of death with blue LED.(Had to wait for the battery to drain to 0%) https://youtu.be/K9T_UF-_5ho (Even though it booted at the end after a minute of use it crashed and went back into a boot loop and crashed and then it was fine for like an hour)
It would get stuck if I went to stock recovery, get this weird static line. I did boot into recovery once so I did a factory reset hoping it would fix something, which it did not. So I guess I was going to return the phone, I then had the stupid smart idea that it booting up fully and me activating it and then resetting it would be a good idea, and boy I was wrong. So it went to you know the usual "erasing screen" in which it would get stuck on, I did the hard restart maybe 4 times then it sorta worked the android guy kept spinning until IT JUST DIED.
And here we are now me typing this out, I feel like the company isn't going to accept it back due to it not being "functional".
Absolutely no sign of life now. Not even charging, this has happened before with it when I went into the recovery menu and it got stuck. I waited out an hour and then pressed ALL the buttons and the charging icon appeared but now, now I think it's different.
TLDR: Bad eMMC of phone, caused me to try to reset it and now it's bricked?
Well lesson learned? When things aren't working at the first place don't try to fix them just refuse outright.
Some say the phone can't be bricked but I feel like I really did it this time.
No the phone wasn't rooted, no I didn't flash with ODIN.
http://imgur.com/SxA0Q9b
http://imgur.com/QLLwhot
Just return it.
There is nothing else you can do and I see no reason why they wouldn't accept it unless there's a physical damage.
Sent from my SM-G935F using Tapatalk
Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.
Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.
If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.
Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.
Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.
CookieDude_2332 said:
So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?
DEVILOPS 007 said:
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?
Click to expand...
Click to collapse
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.
CookieDude_2332 said:
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.
Click to expand...
Click to collapse
Did you enable OEM unlocking if you enabled Dev options?
DEVILOPS 007 said:
Did you enable OEM unlocking if you enabled Dev options?
Click to expand...
Click to collapse
I don't think so. Sorry, I'm not super technical.
Not wanting to make a new thread when this seems to be relevant; I appear to be experiencing the same issues as the OP.
I was at work and I noticed that my phone had switched off. I assumed it had ran flat and I hadn't noticed so plugged it in when I got home to no avail. The following day I was playing with the power button; holding it down for a period and pressing thinking it might be a loose connection and eventually it did turn back on but only for a few hours and since then the only response I get is a red LED when pressing the power/volume button whilst on charge.
I have replaced both the battery and the charging port/daughter board but this does not appear to have resolved the issue. Is there something I am missing or is my phone now a very expensive paperweight? If that is the case this will be the second Nexus device I owned which died in similar circumstances not long out of it warranty; I had a Nexus 6 which died after a year which I replaced with the 6P and it may be that the same thing has happened.
Any help, advice or suggestions anyone can give would be much appreciated!
Edit: Answering a question asked previously with regards to more information my bootloader is unlocked however I can't remember if USB debugging was enabled. I have a feeling that it is disabled as a work around for Magisk Hide and passing SafetyNet.
CookieDude_2332 said:
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad..
Click to expand...
Click to collapse
BLOD is a bad motherboard. If you can't access Recovery and are bootloader locked, you're at the end of the road.
Have you tried to keep it plugged in then hold the volume down button and power button at the same time, and hold it hard for a while and see if it goes to the recovery partition.
Otherwise, why don't you bring to a hardware store and talk to someone?
GLHF!:crying:
So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?
beejkitsune said:
So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?
Click to expand...
Click to collapse
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.
v12xke said:
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.
Click to expand...
Click to collapse
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.
beejkitsune said:
...I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Totally agree.
beejkitsune said:
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Final update. Apparently Huawei are struggling with a parts shortage and don't know when parts will be come available so they have offered me a "Limited Edition" Gold Mate 9. I'm not entirely happy about this arrangement as I really loved my 6P but they have had my 6P for about six weeks and I haven't had a fully working phone since August 18th so I'm left with little other choice since I can't afford the P2XL.
Thanks for your help and in general to everyone in the 6P threads who have helped me out of the past 18 months.
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
No fastboot or custom recovery ?
Then no theirs nothing really to do
Maybe a battery replacement would boot it up
Sent from my ONEPLUS A6010 using Tapatalk
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
easyxpress said:
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
Click to expand...
Click to collapse
Nope it's just a chip on a circuit board
Sent from my ONEPLUS A6010 using Tapatalk
easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
twistyplain said:
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
Click to expand...
Click to collapse
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
easyxpress said:
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
Click to expand...
Click to collapse
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
twistyplain said:
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
Click to expand...
Click to collapse
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
what happened to TWRP ? thats stock recovery
will it enter fastboot mode ? if you can get into TWRP their is a chance of off loading your userdata to a PC
easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Sent from my LeMobile Le X526 using XDA Labs
twistyplain said:
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Click to expand...
Click to collapse
Sorry bad news.
As twistyplain said, your phone is absolutely fried, and there is no solution.
It's definitely no brick, that is a hardware issue... Most likely shorted solder connections. The same thing happened to two of our X727s, we have one left that still works.
I highly recommend buying a seemingly unbrickable Xiaomi phone. Their budget models are awesome and of course their flagships are awesome. Everyone in my family has Migrated to Xiaomi . I currently have Android 10 working flawlessly.
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
easyxpress said:
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
Click to expand...
Click to collapse
If you are in China and located in a large city or tech industrial area you should have plenty of shops that repair at the component level.
Your phone could very likely be repaired by a shop that has a hot air rework soldering station with an electron microscope.
We used to have these types of places in the US but they have all gone out business, replaced by board swappers, who charge a lot. I would suspect that you could get it repaired in China for 100 yuan or less.
I worked in Beijing for 3 months, about 18 years ago and these types of places were everywhere.