I brought my brother a Realme 5i and he'd been happily using it for about a month (mostly as an MP3 player) and then one day he went to charge it from his PC and it briefly showed it was on 71% but then said it was rebooting and froze on the Realme logo. It was stuck on that for hours, so he left it overnight in the hope that it would run out of power and shut itself off and he could try restarting it after recharging but the next morning it wouldn't come on at all.
It's not entirely dead, as when I plug it into my PC "Qualcomm HS-USB QDILoader 9008 (COM4)" shows up in device manager and if I hold power+vol up (or vol down) for 10 seconds it seems to reboot as device manager refreshes but the screen never comes on but I guess that could just be a small chip that's being powered via USB and the rest of the phone could be fried. I've tried adb devices and fastboot devices and they don't shows any devices connected.
Is there anything I can do to fix this or will I have to try and get it repaired? I bought it from the Realme Direct Store on Aliexpress and it probably won't be cost effective to post it back to China to repair but maybe the UK service centre will accept it.
doveman said:
I brought my brother a Realme 5i and he'd been happily using it for about a month (mostly as an MP3 player) and then one day he went to charge it from his PC and it briefly showed it was on 71% but then said it was rebooting and froze on the Realme logo. It was stuck on that for hours, so he left it overnight in the hope that it would run out of power and shut itself off and he could try restarting it after recharging but the next morning it wouldn't come on at all.
It's not entirely dead, as when I plug it into my PC "Qualcomm HS-USB QDILoader 9008 (COM4)" shows up in device manager and if I hold power+vol up (or vol down) for 10 seconds it seems to reboot as device manager refreshes but the screen never comes on but I guess that could just be a small chip that's being powered via USB and the rest of the phone could be fried. I've tried adb devices and fastboot devices and they don't shows any devices connected.
Is there anything I can do to fix this or will I have to try and get it repaired? I bought it from the Realme Direct Store on Aliexpress and it probably won't be cost effective to post it back to China to repair but maybe the UK service centre will accept it.
Click to expand...
Click to collapse
Well you need to flash your device. Go to Oppo/Realme service center in your area. Or you can get online flashing support after paying some amount. Because Realme flash tool require username and password. Hope it will help you.
https://techsaft.com/2020/05/02/realme-5-rmx1911-latest-flash-file-download/
Thankfully the service center repaired it under warranty. They had to replace the main board before flashing it, so it seems it wasn't just the software that got corrupted and the hardware actually fried. I asked them to flash it with ColorOS 6/Android 9 rather than 10 and they did, which is great as I should be able to restore my TWRP backup to get it back to how I want it quickly.
As the main board has been replaced, I guess I shouldn't restore any backups of the lower-level partitions (boot, modem, etc.) but will it be OK to restore System and Data or might there be hardware-connected stuff in System that could cause problems?
Related
Hello,
so here's what happened: I got a fully working N5 with 16GB and a 32GB version which has a broken screen.
Today I tried to replace the logicboard of the 16GB version with the one built into the 32GB one.
The phone didn't start up, neither it reacted to getting plugged into a charger (usb pc & wallcharger both didn't do anything).
I came to the conclusion that the logicboard of my 32GB N5 must be broken aswell, so I put the original 16GB logicboard back in.
The phone booted up normally when all of the sudden it just turned itself off after 5 minutes.
Since then it doesn't start up anymore. Having it plugged in into the charger doesn't do anything either.
I've already tried to get it into bootloader etc but nothing works.
The phone simply doesn't turn on anymore.
When I had it plugged in on my pc I once got a NON-flashing red light, but it seems like I can't reproduce this.
Any ideas?
It would be nice if there is anybody who could help me with my problem.
Swapping the logic board shouldn't prevent the v phone from booting unless something happened during the swap process.
When connect to a windows computer, do you see anything about qhusb load in device manager?
audit13 said:
Swapping the logic board shouldn't prevent the v phone from booting unless something happened during the swap process.
When connect to a windows computer, do you see anything about qhusb load in device manager?
Click to expand...
Click to collapse
After holding the powerbutton + vol up + vol down "QHSUSB_BULK" popped up
That type of "device" is an indication of a hard brick. Disconnect and reconnect without touching anything on the phone. If you see something similar with 9008 in the device name, it could be a soft brick.
After installing a driver it showed up as Qualcomm HS-USB QDLoader 9008. Followed a tutorial using "BoardDiag" to unbrick the device. unfortunately the device remains "dead", no sign of life
:crying:
After having it appear as a "...9008" in your computer, disconnect it from the computer and leave it alone for about 30 minutes. After 30 minutes, try and boot to the bootloader.
I bought an LG G4 H810 from a 3rd party seller on newegg.com just over a month ago. It was working normally since I got it until 2 days ago when the screen went dark while I was using it. After this I couldn't get the screen to come back on, and couldn't get any sign of life from it at all. Plugging it into a charger seems to do nothing, with or without a battery installed. Holding the power button for 30+ seconds also does nothing. When I plug it into my Windows 10 PC without the battery in, I get a "connected device" sound within about a second and Device Manager shows "Qualcomm HS-USB QDLoader 9008 (COM5)." This goes away when I unplug it, and I get the "disconnected device" sound. If I plug it in with the battery installed, the "connected device" sound happens after 10 or so seconds and Device Manager instead shows "Unknown USB Device (Device Descriptor Request Failed)." In either case, it does not appear under "This PC" on Windows Explorer. It did when before it died.
When I got the phone I rooted it and discovered that there's no established way on the forums here to install a custom rom without losing network functionality. I instantly regretted getting the AT&T version, as I have Ting, which uses T-Mobile's network anyway. I had to follow instructions on Ting.com just to get data working with the network. I now regret buying a refurbished phone through newegg without buying an extended warranty.
It would be great if there's some way to get this phone working again, but failing that, I'd love to be able to recover the data on the device. I haven't been able to find much on what might be wrong, but almost all searches lead me to a boot loop problem, which I don't seem to be having. I get no signs of life from the phone at all (no screen, lights, sounds, or vibrations). I might try getting a new battery, but I don't expect that to help because before the phone died, the screen would come on when I plugged it in without a battery (indicating the lack of battery). Now there is nothing.
UPDATE: The seller agreed to refund the purchase price if I send it back, so I that's what I did. I thought I was stuck with this brick.
I've got an unlocked 128GB dual-sim HTC U11 (marking on the back says 2PZC300 U-3u), bought in Taiwan last year but I'm currently using it in Sweden (Europe). Haven't had any major problems up until now, except for some touch screen issues.
This morning I for some reason navigated into the update section of the settings menu, and saw that there was a new update available (I believe it was 2.42.617.1, containing the December Android security updates and "system enhancements"). My phone was not connected to the charger at the time but close to 100% charged and had Wi-Fi access. I downloaded the update and chose to install it. I haven't had any battery issues and it didn't prompt me to plug the phone into a power source.
It proceeded to start the update, but somewhere around 64% it seemed to get stuck for a while, slowly moving to 65% or so after a few minutes. I then left the phone for a while and took a shower. When I came out of the shower the screen was completely black. I left it for a while, but nothing happened. I then tried to long press the power button, but it was still dead.
Now it seems to be completely bricked. Power button does nothing. Volume down plus power button for 2 mins does nothing. Plugging it into the charger does nothing. When I connect it to my Win10 PC using the USB cord it does show up as "COM3" and the driver is "Qualcomm HS-USB QDLoader 9008 (COM3)". It is not recognized by HTC Sync Manager. Feels like I'm in deep ****... And I haven't in any way rooted it or installed anything custom. I'm so disappointed that something like this can even happen.
If anyone here has any ideas I'd be eternally grateful... I'm hoping I won't have to send it in, since that probably means I'll be without the phone for a month or something and probably lose all the data on it (some photos which have not been backed up)... And I'm not even sure if I can send it in here in Sweden. Since it was bought in Taiwan I guess I might have to send it back there.
TrialsOfTime said:
I've got an unlocked 128GB dual-sim HTC U11 (marking on the back says 2PZC300 U-3u), bought in Taiwan last year but I'm currently using it in Sweden (Europe). Haven't had any major problems up until now, except for some touch screen issues.
This morning I for some reason navigated into the update section of the settings menu, and saw that there was a new update available (I believe it was 2.42.617.1, containing the December Android security updates and "system enhancements"). My phone was not connected to the charger at the time but close to 100% charged and had Wi-Fi access. I downloaded the update and chose to install it. I haven't had any battery issues and it didn't prompt me to plug the phone into a power source.
It proceeded to start the update, but somewhere around 64% it seemed to get stuck for a while, slowly moving to 65% or so after a few minutes. I then left the phone for a while and took a shower. When I came out of the shower the screen was completely black. I left it for a while, but nothing happened. I then tried to long press the power button, but it was still dead.
Now it seems to be completely bricked. Power button does nothing. Volume down plus power button for 2 mins does nothing. Plugging it into the charger does nothing. When I connect it to my Win10 PC using the USB cord it does show up as "COM3" and the driver is "Qualcomm HS-USB QDLoader 9008 (COM3)". It is not recognized by HTC Sync Manager. Feels like I'm in deep ****... And I haven't in any way rooted it or installed anything custom. I'm so disappointed that something like this can even happen.
If anyone here has any ideas I'd be eternally grateful... I'm hoping I won't have to send it in, since that probably means I'll be without the phone for a month or something and probably lose all the data on it (some photos which have not been backed up)... And I'm not even sure if I can send it in here in Sweden. Since it was bought in Taiwan I guess I might have to send it back there.
Click to expand...
Click to collapse
I would try removing sim and sd card ( if there is one) and then try power and power and volume down combo. Just my 2 cents. Good luck.
hammered58 said:
I would try removing sim and sd card ( if there is one) and then try power and power and volume down combo. Just my 2 cents. Good luck.
Click to expand...
Click to collapse
Thanks for your reply. I just tried removing the SIM card (don't have an SD card) and then attempting to start it normally and attempting to start with power and volume down. Unfortunately no change And it still behaves in the exact same way when connected to the PC (shows up as COM3)... Feels like it's really bricked I'm so shocked to be honest, that a regular OTA update can completely brick the device like this Maybe I'll have to send it in after all.
try to google search Qualcomm HS-USB QDLoader 9008 no tools to flash it
if it in warranty send it to htc
seem to hardbrick
me ever happend in lg optimus gk korea
i am flashing firmware but not finish i took usb cable out...can power on but when connrct to pc it show Qualcomm HS-USB QDLoader 9008 same you
try to download driver Qualcomm HS-USB QDLoader 9008 and flash it not work
last... i sale it for parts
centrino3 said:
try to google search Qualcomm HS-USB QDLoader 9008 no tools to flash it
if it in warranty send it to htc
seem to hardbrick
me ever happend in lg optimus gk korea
i am flashing firmware but not finish i took usb cable out...can power on but when connrct to pc it show Qualcomm HS-USB QDLoader 9008 same you
try to download driver Qualcomm HS-USB QDLoader 9008 and flash it not work
last... i sale it for parts
Click to expand...
Click to collapse
Hi Centrino! Thanks for your reply. Yep, I guess I'll have to send it in. I did try to google a bit and that was the feeling I got as well, that it really is hardbricked and very hard to fix. I wonder if I just happened to hit some very unfortunate circumstances to have this happen or if it's some more widespread bug... Guess we'll see if anyone else sees the same thing during the coming days.
TrialsOfTime said:
Thanks for your reply. I just tried removing the SIM card (don't have an SD card) and then attempting to start it normally and attempting to start with power and volume down. Unfortunately no change And it still behaves in the exact same way when connected to the PC (shows up as COM3)... Feels like it's really bricked I'm so shocked to be honest, that a regular OTA update can completely brick the device like this Maybe I'll have to send it in after all.[/QUOT
I found this on the HTC website regarding different key combos, may be worth a shot if you have not tried already,
Click to expand...
Click to collapse
hammered58 said:
TrialsOfTime said:
Thanks for your reply. I just tried removing the SIM card (don't have an SD card) and then attempting to start it normally and attempting to start with power and volume down. Unfortunately no change And it still behaves in the exact same way when connected to the PC (shows up as COM3)... Feels like it's really bricked I'm so shocked to be honest, that a regular OTA update can completely brick the device like this Maybe I'll have to send it in after all.[/QUOT
I found this on the HTC website regarding different key combos, may be worth a shot if you have not tried already,
Click to expand...
Click to collapse
Thanks a lot Hammered. I did try those combos, unfortunately to no avail I think I'm really SOL.
Click to expand...
Click to collapse
Maybe connect ur phone to a pc and leave it for few hours.
gm007 said:
Maybe connect ur phone to a pc and leave it for few hours.
Click to expand...
Click to collapse
Thanks, I'll give it a try... I've pretty much given up though Think I'll have to send it in.
So now how it is?
I have u11 dual sim, last night i had update ota so it 100% done and restart but not on sceen, i try soft reset but it only vibrares and silent , my battery 100%
I think ota form htc have problem .
Do you have any idea ?
bitmat said:
I have u11 dual sim, last night i had update ota so it 100% done and restart but not on sceen, i try soft reset but it only vibrares and silent , my battery 100%
I think ota form htc have problem .
Do you have any idea ?
Click to expand...
Click to collapse
I had to send the phone to HTC for a motherboard replacement.
What does it say when you plug your phone into the computer with the USB cable? Do you see it as COM3 and Qualcomm HS-USB QDLoader 9008? If you do, you might've encountered the same problem I had
TrialsOfTime said:
I had to send the phone to HTC for a motherboard replacement.
What does it say when you plug your phone into the computer with the USB cable? Do you see it as COM3 and Qualcomm HS-USB QDLoader 9008? If you do, you might've encountered the same problem I had
Click to expand...
Click to collapse
Was the repair covered by the HTC warranty? If not, what was the cost of the repair? Did HTC say what caused the issue? How long did it take to get the repair done? Sorry about all the questions but I had to send my U11 in to the HTC service center here in the US and I wanted to understand the cost and turnaround time. Thanks.
mauiblue said:
Was the repair covered by the HTC warranty? If not, what was the cost of the repair? Did HTC say what caused the issue? How long did it take to get the repair done? Sorry about all the questions but I had to send my U11 in to the HTC service center here in the US and I wanted to understand the cost and turnaround time. Thanks.
Click to expand...
Click to collapse
Yep, I'm in Sweden and they didn't charge me anything even though the phone was bought in Taiwan. They did not say what caused the issue, just repaired it and sent it back. Unfortunately I lost all my data. It took a little bit more than a week. The repair center in Europe is located in Poland so I sent it to a Swedish "agent" and they sent it to Poland, considering that the turn-around time was very good.
TrialsOfTime said:
Yep, I'm in Sweden and they didn't charge me anything even though the phone was bought in Taiwan. They did not say what caused the issue, just repaired it and sent it back. Unfortunately I lost all my data. It took a little bit more than a week. The repair center in Europe is located in Poland so I sent it to a Swedish "agent" and they sent it to Poland, considering that the turn-around time was very good.
Click to expand...
Click to collapse
Thanks for replying.
Wow! Seems like EU HTC customer service and repair center is much more considerate and positive experience than the US counterpart. It's a damn shame. Maybe HTC isn't as big a company in the US and not as popular in the US than it is in China and Asia and even the EU.
Sent from my HTC6545LVW using Tapatalk
Taiwanese and USA devices have a one time "oops" warranty where you can have your phone fixed once no matter the problem at any time during its life. Europe doesn't get such luxuries.
shivadow said:
Taiwanese and USA devices have a one time "oops" warranty where you can have your phone fixed once no matter the problem at any time during its life. Europe doesn't get such luxuries.
Click to expand...
Click to collapse
I did a quick search on the HTC "Uh Oh" warranty and the U11 is not covered. Oh well.
I am still holding out that the fix for my U11 will not be too complicated and that HTC will have pity for me. Ha! Next week will be 3 weeks since the phone was admitted into the repair center queue. In the meantime I have my new HTC U12+ and I've been using it for the last three days now. I've not toyed with the U12+ and will be keeping stock for now.
Sent from my coconut frond hut using Tapatalk
Hi!
TL,DR:
Phone froze while using, and it kept freezing. Now phone wont boot at all, only EDL Mode works. However, after EDL phone wont still boot.
Longer story:
I've got quite a problem here. I was playing Pokemon GO with my friend yesterday. Suddenly my phone went quiet. I saw PoGo froze for 5 seconds and then phone rebooted itself. It went back to LineageOS (17.1) which I've installed successfully via TWRP. Then the phone rebooted itself again many times again and again, and each time it crashed earlier than before. When LineageOS did fail for booting for several times, the phone went straight to bootloader. I tried to open recovery but it crashed too. Then It came back to bootloader and I said Power Off.
I waited for half an hour but the phone was failing boot. It wen't even worse: the phone wont go to bootloader any longer, it just stays black.
I've done an EDL Mode recovery couple of times before when I was messing around my first custom ROM installation with Lineage. Now when I set the phone to EDL Mode via cable I made (it was an easy task) I can hear Windows detecting my phone (which it didn't detect before) and uses the QDLoader 9008 EDL Driver.
Then I use the "update_image_EDL.bat" to regenerate the partitions.
Now here's the tricky part: After the .bat file the phone should reboot to bootloader, however this doesn't happen, and the phone just exits ELD mode (I can hear it from Windows it doesn't detect the phone anymore) and then just stays black. It doesn't react to any buttons or cables, and Im also sure it has battery. I even opened the case and removed the battery from its port and putting it back to see if the phone reacts then my actions, but no.
It feels like the only thing I can do here is the ELD mode. I tried it several times later, and that's all.
Also trying to continue with the instructions with QDLoader 9008 fix (the flashall_AFT.cmd) won't lead anywhere, because Windows doesn't detect the phone after that.
Thank you in advance for any tips and tricks.
Edit: Just to add; I've tried removing SDcard and SIM cards also. No effect.
Edit2: Here's the copy of the 'update_install_EDL.bat' results: https: //paste.ofcode.org/bPLQA6T484rKEEb2URa8yv
After more failed tries and thinking, my friend was looking at my log from update_install_EDL.bat he was thinking about the warning it gave. Well, I went looking for the sector limit which was put by rawprogram4.xml and I added the missing sector to the count. Now the error is missing from log but it went nowhere in the progress however. I've done the .bat now many times, but nothing seems to be working. I've removed the battery and put it back before edl and after edl and tried booting with just the powerbutton and with the Vol+ and power btn, but nothing comes up.
If you got a log from the update_install_EDL.bat, I'd appreciate if you could post it somewhere for me to see did you get the same warning as I did.
I also want to point out that ANY comment is welcome... I keep you posted whenever theres some progress.
Okay. I decided to take my Zenfone 6 to Asus authorized repair shop. They said I've got short circuit in the motherboard. God knows how that happened. However I can't get it under the warranty because earlier I repaired my broken screen glass in a unauthorized repair shop. which has voided the warranty. Asus told me that the repair would cost me 527,2 EUR (624,30 USD). I'll not be paying that much for a repair, so it looks like Im out of the business..
I also want to note that I purchased the phone 4.6.2020 and it was in the screen repair for 30 days. So with my quick calculations I paid totally 12 eur for each day I had a chance to use it.
Edit: I want to say here that the repair shop takes 60€ (71 USD) for their excellent service. Okay, I admit that they we're quick on the result, for about 30 hours they responded, but ofc I'd like to have more info but they told the phone must be taken to the ASUS factory then.
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
abx12 said:
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Click to expand...
Click to collapse
Yeah Im sorry for the log. The warning on there was basicly telling that the bios.img is larger by one sector than the sector size given to the update_install_edl.bat. It was fixed by adding the one sector to the rawprogram4.xml file.
I was aware of the sahara fail, it was fixed by unplugging the cable and back in (restarting the edl mode ofc). And I also tried another cable.
What comes to the directory (folder) names I was aware of that too, the script don't do a very good job with folders having spaces or special letters.
homerlovesbeer said:
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
Click to expand...
Click to collapse
My working theory is that this high failure rate is affecting all of series so they have no way to determine which units should be fixed/replaced. It's very sketchy but they've put themselves into this situation with poor QC in the first place.
I woke up around 1am tonight to a glow from my wifes Zenfone 6. Wondering why I looked at her screen to find the ASUS logo glowing fully bright like It does upon start up.
Thinking this is odd I tried rebooting it but every single button is unresponsive. I tried holding the power button down for around 30 secs, nothing.
My wife wakes up wondering what I'm doing then tells me her phone updated around 11am that day.
So it appears the ASUS pushed update has potentially stuffed her phone?
Her phone is a totally stock ASUS Zenfone 6.
Ideas on fixing? What has happened?
Cheers.
Homer
EDIT: Now DEAD
Did you try power + vol up + vol down for about 30secs?
papete said:
Did you try power + vol up + vol down for about 30secs?
Click to expand...
Click to collapse
Yes.
I waited for the battery to die and after charging the phone powered up. It lasted 12 hours before suddenly shutting itself down when the wife was changing settings to pull the time from the network.
Now dead as a brick. Charge light no longer lights. Totally unresponsive. No amount of power button/volume button combination or time will do anything to make it work again.
Pretty pissed off as it's 1 year and 16 days old and has already been sent back to ASUS to have the charge port fixed after it stopped working.
I do not know what to do now except push for a repair under warranty.
As a last resort you could try this guide: https://forum.xda-developers.com/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
If that does not work I guess warranty would be the only option left.
Thanks for the link. Unfortunately the phone is totally unresponsive so I have no idea how steps involving any sort of power up can work.
PC also doesn't recognize the phone when plugged in to the USB port.
Could the USB power board have failed again?
If pc can't recognize the phone, you ran out of options. Anyway check device manager on windows just to be sure that it is not recognized as Qualcomm HS-USB QDLoader 9008" device at your Windows devices'. The proper guide to try to fix your state is this one: https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
papete said:
If pc can't recognize the phone, you ran out of options. Anyway check device manager on windows just to be sure that it is not recognized as Qualcomm HS-USB QDLoader 9008" device at your Windows devices'. The proper guide to try to fix your state is this one: https://forum.xda-developers.com/zenfone-6-2019/how-to/qdloader-brick-t3980165
Click to expand...
Click to collapse
Nope nothing showing. Completely stuffed which is why I'm wondering if it's actually the USB power board again or if it's the main motherboard.
homerlovesbeer said:
Nope nothing showing. Completely stuffed which is why I'm wondering if it's actually the USB power board again or if it's the main motherboard.
Click to expand...
Click to collapse
https://www.androidpolice.com/2019/...-crashes-asus-blames-motherboard-malfunction/
give update brother ?
Ishan303 said:
https://www.androidpolice.com/2019/...-crashes-asus-blames-motherboard-malfunction/
give update brother ?
Click to expand...
Click to collapse
Can't do it if dead brother....
homerlovesbeer said:
I woke up around 1am tonight to a glow from my wifes Zenfone 6. Wondering why I looked at her screen to find the ASUS logo glowing fully bright like It does upon start up.
Thinking this is odd I tried rebooting it but every single button is unresponsive. I tried holding the power button down for around 30 secs, nothing.
My wife wakes up wondering what I'm doing then tells me her phone updated around 11am that day.
So it appears the ASUS pushed update has potentially stuffed her phone?
Her phone is a totally stock ASUS Zenfone 6.
Ideas on fixing? What has happened?
Cheers.
Homer
EDIT: Now DEAD
Click to expand...
Click to collapse
There have been issues with few units doing bootloops and not recovering; and Asus had acknowledged it as motherboard issue with the few early units that were made. You could get it to a service centre and get a free motherboard replacement.
Thank you @homerlovesbeer for your description. Very similar to my phone which is now also dead as a brick:
Recover files from bootlooping Zenfone6
Dear all, from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots...
forum.xda-developers.com
Will send it to repair. I bought it 10 months ago.
EDIT: Small correction: Pressing all 4 buttons while it was plugged to a PC, the charging light lit up for perhaps 20 seconds. Unfortunately not reproducible.
abx12 said:
There have been issues with few units doing bootloops and not recovering; and Asus had acknowledged it as motherboard issue with the few early units that were made. You could get it to a service centre and get a free motherboard replacement.
Click to expand...
Click to collapse
I'd love to however I'm in Australia and their isn't an ASUS mobile service centre in this country. I've tried reaching out to Taiwan but the language barrier makes it hard.
No joy so far.
I will RMA mine tomorrow. We'll see how it goes. Except for that issue, I really like the device.