Database Develop

xiaomi mi3 hard brick cold dead?

Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool

Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/

it sounds like a driver issue. just download all the drivers you can find for your phone.

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution

if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,

ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file

Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?

agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.

Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?

androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.

Qfil & testpoint-edl for zs620kl

DISCLAIMER: IM NOT RESPONSIBLE FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. ONLY TWEEZERS SHOULD CONTACT THE POINTS NOT ANY THING ON MB, WHICH WOULD RESULT IN SHORT CIRCUIT AND CAUSE PERMANENT MO-BO DAMAGE. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
I finally managed to find the EDL test point for 5Z. Took risk of opening it and randomly testing the points...
Things Required:
1. Type C Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges.
3. Patience & Concentration.
HOW TO ENABLE EDL WITH TEST POINTS:
1. Plug the type C to phone charging port.
2. While shorting the points with tweezers, plug in the USB to the system USB port.
3. Wait for 5 to 10 sec...Device manager will show either USBDiagnostics9008 or Qloader9008 points, based on the drivers installed. If system shows earlier one...then select and udpate driver and you will see Qloader9008 driver..select and install it. If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
As of now, programming files through QFIL and QMCST are both present in the raw zip file. firehose_ddr.elf is present in the factory image.
Since im testing them, I cannot assertain the success rate, as it depends on nature of brick. Currently im testing QFIL on my bricked phone...
Hope it helps...
Please check the photo

DroneJC said:
DISCLAIMER: IM NOT RESPONSIBLE FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. ONLY TWEEZERS SHOULD CONTACT THE POINTS NOT ANY THING ON MB, WHICH WOULD RESULT IN SHORT CIRCUIT AND CAUSE PERMANENT MO-BO DAMAGE. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
I finally managed to find the EDL test point for 5Z. Took risk of opening it and randomly testing the points...
Things Required:
1. Type C Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges.
3. Patience & Concentration.
HOW TO ENABLE EDL WITH TEST POINTS:
1. Plug the type C to phone charging port.
2. While shorting the points with tweezers, plug in the USB to the system USB port.
3. Wait for 5 to 10 sec...Device manager will show either USBDiagnostics9008 or Qloader9008 points, based on the drivers installed. If system shows earlier one...then select and udpate driver and you will see Qloader9008 driver..select and install it. If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
As of now, programming files through QFIL and QMCST are both present in the raw zip file. firehose_ddr.elf is present in the factory image.
Since im testing them, I cannot assertain the success rate, as it depends on nature of brick. Currently im testing QFIL on my bricked phone...
Hope it helps...
Please check the photo
Click to expand...
Click to collapse
After trying this my mobile not detecting in pc and fast charging also not working

Ashwin18d said:
After trying this my mobile not detecting in pc and fast charging also not working
Click to expand...
Click to collapse
me too. not detecting PC

Ashwin18d said:
After trying this my mobile not detecting in pc and fast charging also not working
Click to expand...
Click to collapse
The one you flashed through process is factory firmware to restore the device only...You need to update the same through Fastboot firmware for phone to work as intended.
Download fastboot firmware and flash it.

DroneJC said:
The one you flashed through process is factory firmware to restore the device only...You need to update the same through Fastboot firmware for phone to work as intended.
Download fastboot firmware and flash it.
Click to expand...
Click to collapse
Boot to fastboot but not detect on pc
I try
- change cable
- connect another computer

4rm4uto01 said:
Boot to fastboot but not detect on pc
I try
- change cable
- connect another computer
Click to expand...
Click to collapse
same problem service center guys charge for 25000 bugs .for the changing of mother board

4rm4uto01 said:
me too. not detecting PC
Click to expand...
Click to collapse
Hold the power key with them

I Messed Up My phone fastboot not working!!!!!

Hello Everyone, so 2 days ago i hard bricked my MI 8 with flashing an eu rom over global mi 8 rom with twrp then when i rebooted the phone it stuck at mi logo so i tried to goto recovery mode again but nothing happens when i press power + volume up its just mi logo and i tried to go to fastboot mode but not luck i get a black screen....................so i decided to connect it to a computer but no signs of anything(not detected).....so i searched google a little and i found a solution wich envolved disassembling the phone the method called EDL method with test point,,,,,,,so i opened my phone with my friends and tried to do the test points,,,when i joined the testpoints and then connecting the phone to pc.....nothing happened.....it should detect the phone but nothing happens.....please help guys!!!

Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone ?

mi_guel said:
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone
Click to expand...
Click to collapse
I have been trying....but no luck till now:crying::crying::crying:

alandxaled said:
I have been trying....but no luck till now:crying::crying::crying:
Click to expand...
Click to collapse
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.

tsongming said:
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
Click to expand...
Click to collapse
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager

alandxaled said:
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
Click to expand...
Click to collapse
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.

@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.

tsongming said:
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
Click to expand...
Click to collapse
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"

alandxaled said:
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
Click to expand...
Click to collapse
The EU rom does not lock the bootloader, the developers actually removed the bit of code that will allow MiFlash to lock the bootloader. Whenever leaving or returning to Miui, storage must be formatted.
The problem with these custom roms for the Mi8 is that These mi8 developers do not work together ( like most do, on other threads) These developers are always fighting and arguing and accusing each other of stealing their code, while they do it themselves and they all have their own way of doing things. Ideally every rom should use the same device tree, firmware and vendor...The basics! But no, everyone does things differently.
I would suspect that your phone bricked due to firmware encryption or just corruption. Even though it seems that it can't be fixed, you will surely be able to fix it eventually.
Many people were eventually able to solve this exact issue in the past with success. so start with the basics., and dont give up when or if it fails, just try again on a different device, and be sure to disable Windows defender. Because it's possible you could have your computer setup in a way that it will make this process harder to resolve, temporarily disable the antivirus and firewall etc.
Download the All in One tool: https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807 If it gets flagged, and completely disabled. then your computer is helping contribute to this issue.
If you can successfully install and open the tool, use it to update adb and android drivers and to apply system wide adb access. Next manually setup the phone , even if it claims to not see a fastboot device. and attempted to remove encryption. if this fails find a Linux machine to complete these tasks.
See if you can leave EDL, by pressing and holding the power and volume down. >>>>> Even if you dont see the fastboot screen the computer may see the phone in fastboot.
I definitely believe that you will have a easier path to getting this issue resolved sooner by using linux. If you can "format" ( not wipe) user data, install TWRP and root the rest will obviously be easy.
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
Boiisxu said:
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
Click to expand...
Click to collapse
He didn't format user data, or the file was somehow corrupted

Nokia TA-1004 JTAG?

Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot ?

Nokia_8_fan said:
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot
Click to expand...
Click to collapse
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.

emufan4568 said:
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
Click to expand...
Click to collapse
Thanks for getting back to me.
I have done both suggestions and they don't work.
It is probably a hard bricked device, the only thing I can get is a 9008 recognition in Device Manager.
QFIL, OST and NOST doesn't seem or want to communicate with the device either

Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem

emufan4568 said:
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
Click to expand...
Click to collapse
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!

Nokia_8_fan said:
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Click to expand...
Click to collapse
EDL mode is Emergency Download Mode in Qualcomm devices for recovering the device at a low level. QFIL calls it download mode but it really is not. Download mode in Nokia phones is really fastboot mode or bootloader mode where you basically communicate with the bootloader and flash/erase images from the device. From what I have seen though NOST supports EDL mode too (with the Emergency Download option) but it does not really work well.

Asus Rog Phone 3 Uber hard brick

Hi Guys,
I really need help with this one. I have tried almost everything.
Here is my problem.
I have an Rog phone 3 strix edition QUALCOMM based.
I repaired the screen because i dropped the phone.
Everything was fine working well. Me with my big head decided to do an factory reset to wipe everything clean from the phone and then the problem started.
The phone was restarting every time i plugged in a usb c cable. If i wanted to listen to some music on headset wont work because it will end in a bootloop.
Now the phone is stuck in CSC Fastboot mode and PC wont recognized it. The screen will turn on and send me to CSC fastboot but that's it. I can turn it back off.
Can i Revive the phone or is it food for the recycling bin?
Please Help.
Sincerely,
Ayolyas

With some effort you should be able to get back on track - unless it's hardware related to the display change you've done.
Can you do a reboot to bootloader from the boot menu? If you can confirm if you have fastboot access. If you do, RAW flash the device.
Worst case, you force the device into EDL mode and do a flash from there, but leave at as the last option.
If the relpaced display is causing harware issues, that's a bigger problem...

Hi Andrologic,
I cannot reboot to the bootloader. I am stuck in csc fastboot. I was trying to put it in edl mode i even bought an edl cable. But i have no idea how to use it or how to put the phone in edl.
I went back to the repair shop but the phone was working fine when it left the phone shop. The problem started when i decided to go for factory reset.

ayolyas said:
Hi Andrologic,
I cannot reboot to the bootloader. I am stuck in csc fastboot. I was trying to put it in edl mode i even bought an edl cable. But i have no idea how to use it or how to put the phone in edl.
I went back to the repair shop but the phone was working fine when it left the phone shop. The problem started when i decided to go for factory reset.
Click to expand...
Click to collapse
So, when you turn on the device, it falls into CSC FB and you can't navigate anywhere at all from there?
What happens if you try to do a RAW flash from CSC FB?
Flashing it in EDL mode may otherwise be the only option. Power off the device completely. Then hold Vol up+down pressed and connect to the USB side port. You should land with a completely black screen and on your pc see the device identified in 9008 mode - that's EDL. Since you have a flash cable, you can obviously use that too.
Remember you need Qualcom drivers installed to work in EDL mode. There is a guide with steps for EDL flashing somewhere here on the forum. All the steps are explained.

Andrologic said:
So, when you turn on the device, it falls into CSC FB and you can't navigate anywhere at all from there?
What happens if you try to do a RAW flash from CSC FB?
Flashing it in EDL mode may otherwise be the only option. Power off the device completely. Then hold Vol up+down pressed and connect to the USB side port. You should land with a completely black screen and on your pc see the device identified in 9008 mode - that's EDL. Since you have a flash cable, you can obviously use that too.
Remember you need Qualcom drivers installed to work in EDL mode. There is a guide with steps for EDL flashing somewhere here on the forum. All the steps are explained.
Click to expand...
Click to collapse
I cannot navigate anywhere from csc. If i try to reboot bootloader i will end in the same place.
I try to connect like you told me Vol up + down but i ended up at the same place. An raw flash from csc fb how do i do that?
And the steps for edl if you can help where to find those steps because my google history is full off items and still no luck finding the right one.

ayolyas said:
I cannot navigate anywhere from csc. If i try to reboot bootloader i will end in the same place.
I try to connect like you told me Vol up + down but i ended up at the same place. An raw flash from csc fb how do i do that?
And the steps for edl if you can help where to find those steps because my google history is full off items and still no luck finding the right one.
Click to expand...
Click to collapse
Yes, you have flash cable, so getting into EDL shouldn't be an issue any way.
This is a useful video on how to use your flash cable to force the device to EDL:
Just remember you need QCom drivers installed to flash in EDL mode, the normal drivers won't do it in EDL.
What is the device identified as on your PC when in CSC FB? Can you send any FB commands to the device at all? Does 'Fastboot Devices' return your device id? If so, try first to do a RAW flash from the Fastboot state you are stuck at. You don't really want to mess with EDL if you can avoid it. Download one of the RAW rom's from the links here on the forum. Version number doesn't matter as long as it matches with your device version, i.e. WW assuming you're on Global.

ayolyas said:
Hi Guys,
I really need help with this one. I have tried almost everything.
Here is my problem.
I have an Rog phone 3 strix edition QUALCOMM based.
I repaired the screen because i dropped the phone.
Everything was fine working well. Me with my big head decided to do an factory reset to wipe everything clean from the phone and then the problem started.
The phone was restarting every time i plugged in a usb c cable. If i wanted to listen to some music on headset wont work because it will end in a bootloop.
Now the phone is stuck in CSC Fastboot mode and PC wont recognized it. The screen will turn on and send me to CSC fastboot but that's it. I can turn it back off.
Can i Revive the phone or is it food for the recycling bin?
Please Help.
Sincerely,
Ayolyas
Click to expand...
Click to collapse
Have you fix it?

osomakohj said:
Have you fix it?
Click to expand...
Click to collapse
Hi,
Nope. I can get into EDL mode so i think it is hardware related. You can say it is fresh for the garbage.

ayolyas said:
Hi,
Nope. I can get into EDL mode so i think it is hardware related. You can say it is fresh for the garbage.
Click to expand...
Click to collapse
maybe try edl cable maybe it'll work? its very cheap in online store

osomakohj said:
maybe try edl cable maybe it'll work? its very cheap in online store
Click to expand...
Click to collapse
I did use a EDL cable and i also build one but no succes for both.

ayolyas said:
I did use a EDL cable and i also build one but no succes for both.
Click to expand...
Click to collapse
Hope you did the proper way of entering edl mode. btw you can still send that to service center. but first try some other way as your phone still boot