I got my phone back for repair today. (flashing full ramdump).
I haven't been able to try everything again. But the first step is that the reprint reader doesn't work, it's like it's not even in the phone, I can't set up a reprint anymore. Has anyone met anyone like this?
Mods maybe some help? @Gustav_ASUS @CH_ASUS @Irene2_ASUS
Should I send it back again?
Update: Got my phone to charge and did some digging.
Shows up as Qualcomm HS-USB Diagnostics 900e under USB devices when its plugged into my computer. FYI this is bad news for the prosumer/ tinkerer/ enthusiast.
What you'd want to see if you were trying to flash a new ROM onto an Android device using a Qualcomm chipset (Huawei, OnePlus, Samsung, etc.) is Qualcomm HS-USB QDLoader 9008. There are tools and guides online about fixing a device stuck in Diagnostics 900e mode and manually switching it to QDLoader 9008. Not specifically an Asus or an Asus Zenfone 8/8 Flip but other manufacturers.
Special programs and hardware are required. Maybe some folks here are familiar with EDL cables or deep flash cables. Amazon, eBay, Aliexpress, etc. have loads of them for cheap. There's also sketchy community developed software for diagnosing issues shared across XDA. Lots of guides bits and pieces can be taken from.
Now everything that's attempted has a higher chance of breaking the phone further than actually working, especially if Asus's only fix at the moment is to replace the motherboard. That isn't very suspicious considering Asus is an OEM and corporations like to waste precious time and resources doing anything to avoid liability. It is well known that other Android phones with similar issues can be restored, albeit dubiously, simply by flashing new firmware.
Asus isn't going to cover my phone under warranty and the eBay seller is going to ignore my requests for a refund. Might as well try fixing the phone and coming up with a guide that will be posted on the XDA forums if and only if any attempts are successful. No promises for a solution and you will only know if anything is fixed because something will be posted about it. I'm very busy so don't expect updates like, "tried this doesn't work". There will be no timeline or schedule.
Everyone here who is in the same boat is encouraged to make some lemons from lemonade and tinker with me. More heads are better than one. I'm relatively savvy in this field but by no means an expert. Of course I will not be liable or responsible for anything that happens to anyone's device. There's even a good chance this post will be deleted by Asus.
TL;DR going to try and fix this phone on my own, don't expect anything though.
Maybe open up a thread at xda. I suppose there will be more people supporting you there.
Just thought I'd add that this has happened to my ZenFone8 this evening. Browsing the Internet, screen went black - as if it had powered off, then the 'Waiting for flashing full ramdump...'.
I'll admit that I've not finished reading this thread yet but it seems like some sort of software failure as there's a lot of recent posts reporting the same issue - a mass hardware failure would seem unlikely (my 2 cents anyway).
Just thought I'd add an update, found a similar issue happened with some Pixel phones recently, (https :// support . google . com/pixelphone/thread/113517096/pixel-3-xl-bricked-overnight-computer-recognizes-as-qusb-bulk-cid-likely-caused-by-security-update?hl=en) further suggesting this issue isn't limited to just Asus. I've also had a web chat with the US support, and although they weren't able to assist with fixing my phone they did say it wasn't an Asus specific issue but an Android one. I doubt it helps anyone though, but thought I'd share.
Ho seguito le tue istruzioni ma vogliono mandarmi telefono ancora in assistenza per riparazione !!! Dicono che sarà il centro assistenza che dovrà dire se riparare, sostituire o rimborsare
the phone when it updates the apps ... I watch videos .. I listen to music ... I use the navigator etc. etc. it overheats a lot !!!! fingerprint non-existent .... rustling during conversation and while I phone I find myself with pages for management modification never open .... all this after changing motherboard !!! They want to bring SMA back to assistance !!!! I am exhausted from this Asus purchase !!!! I will hire a lawyer at the cost of spending a lot of euros
Is it the same ramdump error though? Phones can brick for multiple reasons but for ZF8 it seems to be fairly consistent, If you look at the photos posted here by most of us it's the same.
Well that's the trick isn't it, nobody actually knows what's triggering the ramdump/bricking at the moment - there is just speculation.
The symptoms presented within the Google Support article are very similar to those experienced by the people posting here, and myself - I have not seen any mention of the "Waiting for flashing full ramdump..." on the article (although there are plenty of other links to explore) but for all we know the Pixel handsets just don't display this. What is interesting is that it appeared to be triggered by an OTA (which are usually staged and could be why groups of people are affected at seemingly the same time) and that connecting the phone to a computer confirms that the device is in the EDL state - which is what mine does. It also appears that this is a QualComm recovery mode the devices are entering - if we had access to the OEM image (not the firmware image available on the Asus download page) used by the QualComm recovery tools it's likely we could re-flash the devices out of their bricked state:
For the time being we all should be raising support cases with Asus and sending the phones back to them as requested. This gives them the opportunity to actually look at the devices and investigate, there is no magic wand for them to wave that will explain what has caused the issue, or to fix them - and with the current state of global shortages for everything right now we all to be a little bit more understanding that these things take time.
That's not to say that I'm not disappointed that my 3 month old phone is no longer working but I'm not ready to throw Asus under a bus yet, I have my support case open and will wait to see what happens.
For those wanting to keep track of anything potentially related to batches, MFD and BATT are below:
@xonics Thank you for your voice of reason in this whining thread. The most valuable posts since lot of pages, as I see it.
I agree so much👍
I come here to read the newest info's on this issue and I pity those who have enough time to whine without any news.
Was any data ever available of the number of active / in use Zenphone 8 units?
I understand that not every user is on this forum, and that not all problems are reported here, but do we have any/enough numbers to try and calculate what percentage of phones are affected?
Also, I've seen that somebody made a spreadsheet with all reported cases here, but it only included MFG date and date of failure. Maybe it would be useful to also gather data on region / country of purchase and firmware region? Also, information if the failed phones were unlocked and/or running alternative kernels/OS images.
Regarding first part, there is no chance anyone else than Asus would have this information. Shame, it seems they are not very likely to communicate what's going on. I'm still hoping they are working on figuring out what's happening and will issue a statement, but frankly, it has been too long now.
Buddy most of us here have lost money, time and data dealing with Asus and this device, it helps to have a little empathy. I'm sure a lot of people came here looking for answers and not complains but we like you at one point is also asking for answers from Asus. The reason we became aggressive is because they are not giving us any explanation at all.
So we have to do the investigations ourselves such as speculating if issue is isolated to certain batches or getting feedback from those that got their phones back from repairs. All these should have been done by Asus and not us but since they are so incompetent we have to do their job for them.
You didn't lose data because of Asus, backup is a must these days. Doesn't matter which device you have. There are reports of devices of all brands catastrophically failing (including Apple, Samsung, Google, Sony, Huawei....). Also you shouldn't have lost money as the devices are covered by warranty. You did lose some time and went through some hassle though.
Try to look at a bigger picture here. If Asus sold only 100.000 Zenfone 8 phones (for comparison it sold 500.000 phones in 2020), and if 100 of those have failed with "ramdup issue" that is 0.1% failure rate. It is almost in the range of a statistical mistake.
I'm only here to complain and I don't care. Asus screwed me right up, by selling me a doggy device, so I'll mourn as loud and as much as I can. The device died on me, out of the blue, when I was travelling to work, lost my sat nav, lectures and all the data I needed at that point. The worst part was then to findout that this affects others as well, so I'm well posses off as Asus should do a recall ad this phone is faulty! They took the phone away for repair on 7.9.21. Its now 9.10. 21 and I still don't have the handset, so I'm not going to be happy am I!
I understand that it's annoying to see people whine, and of course it can happen to have an problem on an electronic device, and you should always back your data up. But the situation here is a bit more complicated, and I think people have the right to be upset by Asus' attitude.
First, Asus doesn't cover everyone under warranty and try to find excuses all the time. I litteraly had to threaten to sue them like 6 times until they agreed to fix it for free instead of for 500€, and they didn't even tell me or apologize.
Second, lots of people have been waiting for over a month for their phone, this isn't normal at all, even at a time of shortages (the phone is still in stock if you want to buy it, so are the shortages only for repair centers?).
Third, their communication is absolutely terrible. They didn't acknowledge the issue, and seem to treat it as individual cases in an automated RMA process. I'm not even sure they are investigating, collecting data or even referencing the cases of defect ZF8. I hope you're right with your 0.1% number, but it could as well be 1%, we have no way of knowing at this point.
On a more positive note, I have to say the repair has been done properly for me and I'm not experiencing any issue with the new motherboard, if anything it seems to heat up a bit less.
I'll keep using the phone personnally, but still wouldn't recommend the brand to anyone given how I've been treated by customer service, and the fact that we don't know how likely the issue is to occur.
I'm not sure the issue is software, because we also have several cases (including mine) of devices not even displaying anything, not heating when plugged in, and that are just pure bricks, which definitely seems hardware to me. Maybe it's an entirely different issue, but it seems weird that there are so many cases of both issues just for this phone, and not that many on other Android phones.
Also, if it was software, it would be really weird of them to just replace motherboards, and therefore waste pefectly working hardware just because they don't want to flash the OEM image. But again, I wouldn't really be surprised by Asus' incompetence at this point, so maybe you're right.
I don't really have ideas to help you guys in the process of fixing the phone, but if you want me to extract some data from my working ZF8, I'll gladly do it for science (Discord flood#4171 if you need anything).
Doesn't seem like you can use the quote function for specific parts of someone's post. I only wanted to comment on the software vs. hardware fault.
As we don't really know enough about how each device was used, how long they've been active etc. all we can do is speculate, it could be software or it could be hardware. Not all devices with the same manufacturing date are apparently affected, for example, my device is an April 21 build, I purchased it in June and have been using it roughly 3 months before experiencing the problem - why did I not have the issue in August or September like many other 0421 builds? The link I shared on my original post is for Pixel 3 handsets experiencing similar problems within the same time frame as the ZenFone 8's, evidently from an OTA update. As OTA updates are usually staggered it would explain the flow of the failures and how they've affected different devices at different times. Maybe it's just a coincidence but I'm not a big believer in coincidence, it's usually because we don't have enough pieces of the puzzle to understand why something happened (which is why I said we don't know enough about how each device was used).
Whilst it's possible the failures are triggered by some soft of hardware issue, why now? Do the phones have 3 or 4 months of running time before a component failure? The swapping of the motherboard may only be something they are doing for devices that no longer power up, like your device, whereas mine still powers up - perhaps that'll be a re-flash, won't know until I hear back from Asus. It's also possible that the repair centres have been told to replace the boards and not re-flash, maybe Asus feel that is a better option than a re-flash (maybe to have the boards sent back for inspection/review), or the centres have no ability to re-flash so they can only do a board swap - we simply don't know.
I'll post any updates I get to my case here to keep everyone updated. Currently I'm attempting to let the battery drain down and see what happens after that.
but in your opinion, after spending 800 euros I have to solve the problems of a smartphone that Asus has put on the market with many defects !!! I am the injured party and I have the duty and the right to complain and ask for explanations !!!! In your post you wrote phrases from an unskilled person