Database Info

Phone is stuck on a screen maybe bricked during flashing????

Ok I was flashing back to stock 2.1 useind odin when mid process my phone fell battery out usb disconnected and bam thats it. Now my phone is locked on a screen that shows a picture of a phone ! and a computer. I can get it back to download mode and odin will se the phone but gets no further then do not unplug device, my computer beeps when its plugged in but it dose not show the phone in my computer section. Any fixes or am i screwed?
PS phone is only two weeks old if need be could I take it back like this????

Hmm I think I may hove gotten past this problem. Uninstalled odin reinstalled and now it seems to be hopefully working

Here is the fix
I was in this same situation yesterday. Here is how to get it back into download mode.
•Be sure the Samsung USB drivers for the phone are installed on your computer.
•Remove and replace the battery.
•Connect the phone to the computer with the USB cable. The "phone-exclamation mark-computer" picture should display on the phone's screen.
•Hold the Volume Up+Volume Down+Power buttons down simultaneously.The screen should go blank, then the picture should appear again. When the screen goes blank a second time, release the Power button while continuing to hold the Volume Up+Volume Down buttons down

If that doesn't work,i had a similar problem where I could get into odin, but it would progress beyond the pit file. Take the battery, sim and memory card out of your phone. Start odin. Put the battery only back in. hold volume up and down. Plug the phone in while holding these buttons. Don't let go until you are in download mode. Now try restoring. It should work.

Thanks for the input i am back up and running!!
Sent from my SAMSUNG-SGH-I897 using XDA App

Bricked replacement Captivate - Orange Screen
Just to let you know. I recently received a replacement captivate thru warranty exchange. The phone was apparently a new one with JF6. So I decided to do an update to JH7 using Kies mini. A little over half way to the update procedure, the phone screen turned orange and stayed there for a long time, eventually I had to pull the plug. Of course I had to manually go to download mode and launch Kies mini emergency recovery, the damn thing again got stuck at the orange screen.
If anybody has this experience do no proceed further and throw that damn thing back at At&T's face. Do not attempt to do anything. I made a mistake of then doing an ODIN one-click back to stop and the phone got stuck half way, went to the orange screen.. and then it was over.. The phone was dead, wouldn't turn on, no recovery or download mode with any button combo. When I plugged in to the wall, no battery indicator.
save yourself the trouble and return the damn thing

still there
I am a "noob" to posting here, and a noob to the android due to being an avid iPhone user. I am having the same problem, phone -!- computer and have tried every method i can find in this forum to get passed it. Are there any other thoughts or suggestions? (got hung at do not turn off target in odin) Thanks in advance to any help.

I would look at this thread http://forum.xda-developers.com/showthread.php?t=1153310

Stephenv1971 said:
I would look at this thread http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
went that route, still cant find dl mode. have resistors built and all. any way i try to boot shows me the phone -!- computer, and the computer doesnt attempt to recognise it so there is no communication between the computer and phone. unfortunately, i dont have a v/ohm meter, so i am not sure of the accuracy of the resistors i used to make my jig.

I fixed this many times with phone that had the button download mode and didn't.
Getting into download mode while softbricked like this wont show the normal download screen. IT will still show the error screen....
With download mode working still:
Simply remove the battery and replace,
Open odin
Hold down volume keys and plug it in till you see odin recognize ur phone.
Then continue to use odin.
Dosent work, repeat.
If you know ur button combo dosent work:
Just open odin.
Remove battery & replace.
Use jig (3k 100k ohms twisted)
Then when the phone turns on and your see the pc! screen plug in usb.
See if odin sees it.

Assuming your flash didn't fail on the PBL.bin or SBL.bin you should be fine.
Follow the methods suggested by other users here and you will get back up and running in no time at all.

Don't sweat the 'phone-!-pc' screen. I'm a little surprised that no one has given you the good news....that is just a version of the download screen for later hardware revisions. It looks bad, but if Odin recognizes your phone (if one of the COM fields goes active), just start your flash again.
Now if Odin does not recognize the phone when plugged in via USB, then you have some more work to do.

I had forgotten about posting here, and my problem has been resolved. So here it is... I tried everything that I could find within this forum, almost. I built my own jig with inferior radio shack components that would not activate download mode, though it would turn the phone on. I got wise, spent 8 dollars at ebay and purchased a JIG there. Instant download mode after 3 days (shipping). Reflashed with one click, updated w/ kies, made kernal changes and am now rockin my captivate. Thanks to those who assisted.

Steve_O_1971 said:
I had forgotten about posting here, and my problem has been resolved. So here it is... I tried everything that I could find within this forum, almost. I built my own jig with inferior radio shack components that would not activate download mode, though it would turn the phone on. I got wise, spent 8 dollars at ebay and purchased a JIG there. Instant download mode after 3 days (shipping). Reflashed with one click, updated w/ kies, made kernal changes and am now rockin my captivate. Thanks to those who assisted.
Click to expand...
Click to collapse
Using the 3-resistor method takes A LOT of patience, at least in my experience. Glad everything worked out.

beast534 said:
Using the 3-resistor method takes A LOT of patience, at least in my experience. Glad everything worked out.
Click to expand...
Click to collapse
Patience is a virtue, and my Ex's name. LOL! I can do without patience.
Jokes aside, i actually soldered the resistors to a plug that i had cut up, and made sure it was covered so my skin wouldnt come in contact. The Radio Shack here buys inferior products and sells them at reggular retail. Unfortunately my $300.00 V-Ohm meter is on the fritz, and i have not had the time or money to replace it yet, but I have intentions to check the actual resistance of the jig I made. ^^

[SOLVED] Yet another phone bricked...

I know this had been posted all over this forum but I can't for the love of me find a way solve this. By phone won't boot, nothing comes up in the screen everything is black. This happened while trying to do the 3 button fix.
This is what I have tried so far:
All the possible combinations of buttons
Trying to get it to connect with adb on 3 different computers
Tried to see if the usb connection was read by the linux kernel
And nothing...
At this point the only thing I haven't tried is the Jig method that I will try tomorrow. Aside from this is there anything else before having to go to ATT and beg for a new one?
Thanks in advance
Additional Info:
I was running Serendipity 5.10 with the kernel included

Some people have had success getting back into download mode by removing the battery for 30 seconds to a minute then plugging in the USB cable, holding the volume buttons and (continuing to hold the buttons) inserting the battery.

opcow said:
Some people have had success getting back into download mode by removing the battery for 30 seconds to a minute then plugging in the USB cable, holding the volume buttons and (continuing to hold the buttons) inserting the battery.
Click to expand...
Click to collapse
My phone was soft bricked last night, this method above helped me get back into download mode. Good luck to the op!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Drkstar81 said:
My phone was soft bricked last night, this method above helped me get back into download mode. Good luck to the op!
Click to expand...
Click to collapse
I had the same experience last week. Took several tries, but I finally got back in and flashed a new ROM onto it.

The three button fix requires you to flash a new sbl, right? Chances are pretty high that you permanently bricked your phone and a jig won't do you any good. If the jig doesn't work (and I don't expect it to), you have one of two choices: Buy a riff box and revive your phone by taking out the motherboard and connecting it to the riff box, or mail it back to Samsung and have them do it for you.
Note that using the riff box will definitely void your warranty and Samsung will be able to tell that you took it apart in the event that you eventually send it back to them. Custom roms and bricking supposedly void your warranty, but if you're clever enough over the phone, they'll be none the wiser. Especially in your situation, where the phone doesn't do anything when the power button is pressed.

Thanks to all for your help and will update this thread on what happens for future reference. The jig did not work so the next step is to go beg at an AT&T store for a new phone... Here goes nothing.

masterkoppa said:
Thanks to all for your help and will update this thread on what happens for future reference. The jig did not work so the next step is to go beg at an AT&T store for a new phone... Here goes nothing.
Click to expand...
Click to collapse
Just tell them the official 2.2 update did it. "My phone turned off by itself while I was trying to do the update through kies".
Also, if you deal with Samsung directly, they'll mail you back the same phone, so if you got one of the lucky ones with a functioning GPS, you might want to hang on to it by dealing with Samsung instead of ATT.

I took out the SIM, and battery for more than 30 seconds, enter recovery using 3 button mode, open ODIN, attach cable and flash to Eclair...worked fine. Installed SIM after everything worked.

As modest_android pointed out nothing at this point works. I managed to get a hold of AT&T yesterday and they'll send me a new phone overnight.
Thanks to everyone for their help.

[Q] {HELP} I thought it was a good deal...really!

A little background before I describe what brought me here to the forum for assistance. I had an SGS II (Telus - T959D) that I tried to upgrade...1st 3 Flashes went beautifully until I noticed that there was an ICS upgrade available...so I jumped on it...problem was the upgrade (while Odin said everything was right with the world) caused the phone to go into a permanent boot cycle (never going past the ICS flash screen). I took the phone into the local phone shop and they tried everything they could think of to reset or at least get it back into download mode...nada...zero zilch.
I then had a $600 paper weight. Luckily I still had my Motorola Milestone but I longed for my SGS back.
Yesterday I found an i9000 for sale. Already set up with ICS, running smooth and supposedly in mint condition...all this for $150. I got to the guys house who was just finishing wiping his personal data for me and reinstalling the Custom ROM ([ROM][MIUIv4][ICS][4.0.3][BETA8.1]drZMIUIv4- MULTI LANGUAGE[08/02/2012]).
I look at the phone...great condition...phone is cycling through the install and shows all the right partitions on the screen so I pay my money and walk out.
The phone never actually boots to an active screen and by the time I get the darn thing home it has gone completely dead.
Power button - NOTHING
3 button Download - NOTHING
3 button Recovery - NOTHING
battery pull 3 button Download - NOTHING
left charging all night - NOTHING
I tried to message the guy I bought if from and surprise, the 2 minutes it took him to respond to my offer to purchase has now gone 14 hours when the phone does not work.
I saw a post about a Brick Recovery option that involves ripping open the phone and soldering some jumpers...which I am fine to do...if there is some assurances that that will get the darn thing to at least boot up again.
Anyone who can help with this...my wife is none too happy right now...and in all honesty...neither am I. So I turn to the Android fellowship...HELP

Have you tried a two-dollar jig off eBay? Might be worth a shot before you go ripping her clothes off
Alternatively, you need to see AdamOutler's work
EDIT: Oh and for the price, if it's in good condition you got a good deal

But your phone was on and goes on?
If the phone turns on, its not bricked and there should a way to fix it.
Otherwise go to service point and tell them you don't know what happend, it doesn't work anymore...they should send it in and you get a worked one back.
Good luck.

archiv said:
But your phone was on and goes on?
If the phone turns on, its not bricked and there should a way to fix it.
Otherwise go to service point and tell them you don't know what happend, it doesn't work anymore...they should send it in and you get a worked one back.
Good luck.
Click to expand...
Click to collapse
Correct, but if you try the three-button combo and can't get into download mode, I think you need a jig

Jig no go
I had a jig from my last experience of bricked phone joy. Nothing.
I am thinking that the unbrickable mod is worth a shot...having a tough time finding magnet wire...not to keen on spending $20 on 3 spools when I need less than 1cm of wire.

[email protected] said:
I had a jig from my last experience of bricked phone joy. Nothing.
I am thinking that the unbrickable mod is worth a shot...having a tough time finding magnet wire...not to keen on spending $20 on 3 spools when I need less than 1cm of wire.
Click to expand...
Click to collapse
Someone in the i9000 forums may have some if you ask in the QnA section?
Sent from my Galaxy Note using XDA Premium

bricked sgs2
Hi,
I am with galaxy s2 I9100 on Lite'ning rom 3.6 and CF root kernel.
I flashed it with mobile odin pro.
Earlier I switched and tried to remove the yellow triangle by the method wit 1tar and 2tar and jig described by anonymous572 ("How to remove yellow triangle on any firmware with JIG") somewhere else in the xda. I did not see that this thread was about the Galaxy note and it said 'works on all ICS'...and missed the warning not to use it for sgs2. It worked indeed for the sgs2 to remove the yellow triangle.
But since then I can't enter clockworkmode, downloadmode and recovery mode anymore. Not via the buttons and not with the options in CWM manager and LRT toolbox and Odin Mobile Pro. I mean that I did not get any startup screen until after some minutes the lock screen.
Another reason could be that I restored backup via Titanium and also restored the system apps and data - which I know now I should not have done with a different new rom....
Last try was to start sgs2 with usb connected to PC and Odin activated. This worked and I could flash
according to the method as described in:
http://forum.xda-developers.com/showthread.php?t=1457458highlight=problems+with+recovery+modeed
I ticked re-partition and flashed the whole package including the pit file and this solved my problem.
(flashing without flashing the pit did not work).
After that I switched back to Lite'ning rom 3.6 and it's OK !
Jac

S6 100% unresponsive with irreplaceable photos contained within... need options

Changing the thread around to reflect the current situation, new text at the bottom of the post.
While out to dinner with my family an hour or so ago, my phone suddenly stopped working. I had been checking some emails when the food arrived, so I pressed the power button to shut down the screen and set the phone to the side. About 30 minutes later, I tried to open my phone to continue where I had left off, only I got no response at all from the device. I immediately tried the normal troubleshooting actions (holding power button for 30+ seconds and attempting to go into recovery mode), but still got no response from the phone. I have since tried charging it at home with it's original quick charger, but even after 15 minutes on the charger, there isn't even a red light indicating it is charging. Is there anything that I can try to fix this on my own, or is it likely that I've got some technical fault that only Verizon can deal with?
Thanks.
PS: I'm 100% sure that no liquid came in contact with my phone during dinner. Even if I wasn't so sure, both the phone and case have been bone dry through the entire ordeal.
New situation:
The "techs" at Verizon were less than useless... While there, they tried fewer fixes than I was able to attempt before telling me that the only option they could offer is to replace the phone. The problem, as I've said a little lower in this thread, is that I've got some irreplaceable photos of my recently deceased cat of 19 years stuck on the phone that I never got the chance to back up before this event.
And so now I need options. I'm willing to do pretty much anything, up to and including tearing the phone apart to manually access the memory unit, but the end result absolutely has to be those photos recovered.

Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution

DroidXrei said:
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
Click to expand...
Click to collapse
I've tried soft reset (hold power only), hard reset, and recovery, all to no avail, and holding each for long after it's supposed to respond (at least 60 seconds).

Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.

Theodric58 said:
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Click to expand...
Click to collapse
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.

treblesum81 said:
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
Click to expand...
Click to collapse
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.

Theodric58 said:
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Click to expand...
Click to collapse
All of this was done before taking it to Verizon. All key combinations were tried unplugged then plugged into 3 different chargers and also my computer with 3 different cables and several different USB ports. When I went to Verizon, they tried the key combinations unplugged and then tried plugging it in and seeing if it would take a charge... hence the assertion that they tried less than I was able to attempt at home.

Time to find someone who can repair the phone locally. Any type of warranty or factory repair will cost you the pictures.

Sounds like it's safe to say the phone is beyond simple trouble-shooting. I found myself in a similar predicament last year when I busted the screen on my S4. I dropped my phone on some concrete steps and the screen (in addition to being shattered) went completely black, but I knew the phone was still working because I could still hear the person I was taking to on the phone lol.
I ended up replacing the phone through Verizon. They referred me to some third party company that agreed to replace the phone for $100 and sent me a replacement with a box to put the busted one in. At this point I found myself presented with a unique opportunity, given the fact that I had both a working S4 and my broken one.
Because I didn't have the chance to back up the phone before I lost access to it (it's pretty hard to unlock a phone without the screen) I looked up a guide on how to disassemble the S4 on YouTube in order to gain access to the motherboard. The whole process was relatively easy to carry out and I was able to disassemble both phones, switch the motherboards, backup the information I needed, and switch them back.
Sorry for the long-winded response. I realize this is a pretty drastic measure to take and that you may not have access to a second S6. It's also entirely possible that the motherboard on your phone is part of the problem so switching it wouldn't help much in that case (like I said, I knew my phone was still working despite the screen). Just wanted to offer another option =).

I am in a similar predicament, desperate to get my photos and videos back and have been watching your thread for some ideas. My 7 week old Verizon Samsung Galaxy S6 G920VVRU4BOG9, android version 5.1.1. ceased to do anything on Monday for reasons unknown. It is now back on but it has been wiped clean. I had to do a hard reset. Samsung & VZW tech support were not helpful. May I ask what model your phone is? Provided you are able to get yours back on, I'm wondering if you may have some success with some of the following:
Wondershare Dr Fone for Android
Asoftech Data Recovery
Kvisoft Data Recovery
Ease US data recovery.
I could not get them to work because you must first have a rooted phone to retrieve them and mine apparently can't be rooted. I apologize if this is redundant but I thought I'd throw that out there in case you might have a change of recovering those photos. I'm sorry for your loss. It's very hard to lose a beloved pet.

Zenfone 6 stays black after EDL Mode

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.