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.

Unbrick your hardbricked Max M2

DO NOT BLAME ME FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
The phone was dead...no fastboot... no recovery...no boot logo...no LED...
Only it was being detected by PC when connected and showing as
Qualcomm HS-USB Diagnostic device or QUSB_Bulk
in device manager
Finally managed to find the EDL test point for Max M2 (X01AD).
Be aware that once you open your back cover screws your warranty becomes void.
Things Required:
1. Usb Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges (preferably to make two contact point shorted).
3. Patience & Concentration.
HOW TO
Install QPST
open QFIL...there is a good guide in help topic...refer that for basics. (Qualcomm Flash Image Loader).
1. Remove battery then Plug the usb 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
Right click-->update driver-->browse computer-->Let me pick--> un tick compatible driver-->Qualcomm-->and you will see Qualcomm HS-USB QDLoader 9008 driver..select and install it.
If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
Open QFIL-->flash.
select programmable_.._.._ ddr.mbn && rawprogram_unparse.xml during flash.
IMEI and serial number will be gone. Need to fix.
You need to short circuit the two test point as per attached picture during entire QFIL flash.
ROM link
https://vnrom.net/2018/12/rom-raw-ch...ne-max-pro-m2/
Use WW_ZB632KL or WW_ZB632KL file.
Look for zb632/633 KL and find 15.2016.1902.159
Hope it helps...

<Mod edit: Quoted post deleted>
Congratulations...???

[email protected] said:
DO NOT BLAME ME FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
The phone was dead...no fastboot... no recovery...no boot logo...no LED...
Only it was being detected by PC when connected and showing as
Qualcomm HS-USB Diagnostic device or QUSB_Bulk
in device manager
Finally managed to find the EDL test point for Max M2 (X01AD).
Be aware that once you open your back cover screws your warranty becomes void.
Things Required:
1. Type C Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges (preferably to make two contact point shorted).
3. Patience & Concentration.
HOW TO
Install QPST
open QFIL...there is a good guide in help topic...refer that for basics. (Qualcomm Flash Image Loader).
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
Right click-->update driver-->browse computer-->Let me pick--> un tick compatible driver-->Qualcomm-->and you will see Qualcomm HS-USB QDLoader 9008 driver..select and install it.
If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
Open QFIL-->flash.
select validated_.._.._ ddr.mbn && xx_xx_no_fsg.xml during flash.
You need to short circuit the two test point as per attached picture during entire QFIL flash.
ROM link
https://vnrom.net/2018/12/rom-raw-ch...ne-max-pro-m2/
Use WW_ZB632KL or WW_ZB632KL file.
Look for zb632/633 KL and find 15.2016.1902.159
Hope it helps...
Click to expand...
Click to collapse
Why type-C cable ? Our phone has micro usb port

Jay_1212 said:
Why type-C cable ? Our phone has micro usb port
Click to expand...
Click to collapse
U r right.... I meant to normal usb. Rectified.

Test point
Help me I am unable to find the test points on my Asus ZenFone max 2 pro

I am getting this error while flashing above mentioned file with above mentioned steps. Why I am getting this error can anyone help me out about this?

Love you !
All the all the repairer in my city say : your phone is dead and I have already try to buy an other when I say this solution : it hurts the finger but gives a deep satisfaction.
Thanks a lot

clement_mint_android said:
Love you !
All the all the repairer in my city say : your phone is dead and I have already try to buy an other when I say this solution : it hurts the finger but gives a deep satisfaction.
Thanks a lot
Click to expand...
Click to collapse
This method no bad, but if you have firehose fail... what? How to fix?

Did you try with..?
UnBrick (EDL) - ZQL1830_Factory_201812181515_ChangeFlash.zip

Huawei P10 Hard Brick

Hello,
So I happen to somehow hard brick my huawei p10 via HiSuite while downgrading from EMUI 9.1.0.262 to 9.0.1.180 and to 8.0.0 (dont know which version). After phone finished downgrading to 8.0 its suddenly turned off and it wont turn back again. When I plug it to the charger the phone gets warm, while on computer (connected via usb) its recognized as fastboot device. I tried shorting testpoint but I couldnt get SERAIL recognition.
Please help me, I wanna save this bease I know it still has potential.. Huawei is so damn dumb when it comes to software support and firmware updates via PC unlike Xiaomi, Samsung whom have Odin and MiFlash.
its sad, big minus for huawei

kenzyyy said:
Hello,
So I happen to somehow hard brick my huawei p10 via HiSuite while downgrading from EMUI 9.1.0.262 to 9.0.1.180 and to 8.0.0 (dont know which version). After phone finished downgrading to 8.0 its suddenly turned off and it wont turn back again. When I plug it to the charger the phone gets warm, while on computer (connected via usb) its recognized as fastboot device. I tried shorting testpoint but I couldnt get SERAIL recognition.
Please help me, I wanna save this bease I know it still has potential.. Huawei is so damn dumb when it comes to software support and firmware updates via PC unlike Xiaomi, Samsung whom have Odin and MiFlash.
its sad, big minus for huawei
Click to expand...
Click to collapse
Tip for getting the testpoints to work:
* Disconnect the battery. You'll have to remove the plate over the battery connector.
* Plug in your USB cable to the phone - leave it disconnected from the computer.
* Short the testpoint.
* Plug the cable into the computer while keeping the testpoint shorted.
It should now come up in serial mode. You can, at your own risk, reconnect the battery now - I've never had a problem doing this, but the socket is now live so...

irony_delerium said:
Tip for getting the testpoints to work:
* Disconnect the battery. You'll have to remove the plate over the battery connector.
* Plug in your USB cable to the phone - leave it disconnected from the computer.
* Short the testpoint.
* Plug the cable into the computer while keeping the testpoint shorted.
It should now come up in serial mode. You can, at your own risk, reconnect the battery now - I've never had a problem doing this, but the socket is now live so...
Click to expand...
Click to collapse
Thanks for replying..
I get the testpoint working but after I get it to work PC doesn't recognize testpoint mode. I tried everything the phone is dead, it's stuck in fastboot..
I just want to get it to work it's all I want, I just want to flash any system on it I tried LINUX method but it's the same issue testpoint not recognized by PC other modes are recognized.

kenzyyy said:
Thanks for replying..
I get the testpoint working but after I get it to work PC doesn't recognize testpoint mode. I tried everything the phone is dead, it's stuck in fastboot..
I just want to get it to work it's all I want, I just want to flash any system on it I tried LINUX method but it's the same issue testpoint not recognized by PC other modes are recognized.
Click to expand...
Click to collapse
On Windows, you'll have to dig up some very specific drivers for the port.
On Linux, you need to make sure things like ModemManager aren't installed, as Linux directly recognizes the serial port exposed by the device, and if you have a package installed that tries autodetecting modems, it screws with the serial mode of the device - it's not terribly tolerant of protocol data that it doesn't understand.

irony_delerium said:
On Windows, you'll have to dig up some very specific drivers for the port.
On Linux, you need to make sure things like ModemManager aren't installed, as Linux directly recognizes the serial port exposed by the device, and if you have a package installed that tries autodetecting modems, it screws with the serial mode of the device - it's not terribly tolerant of protocol data that it doesn't understand.
Click to expand...
Click to collapse
Thank you again for replying.
Now I'm getting this in device manager (see picture)
So I've got this how in the heck do I get it working again? Is there any software that allows me to get it running? Plz don't recommend DC phoenix I've paid them and I didn't have so much luck with them..

:good:

kenzyyy said:
:good:
Click to expand...
Click to collapse
From there, you need to load the IDT mode fastboot, and then in theory you can reflash everything else.
Check elsewhere, I've seen a package floating around for restoring from a brick situation here. Otherwise, your choices are pretty much DC Phoenix or to go tracking down internal Huawei tools, as those are the only other pieces of software I know of for flashing the device back from such a brick situation.

irony_delerium said:
From there, you need to load the IDT mode fastboot, and then in theory you can reflash everything else.
Check elsewhere, I've seen a package floating around for restoring from a brick situation here. Otherwise, your choices are pretty much DC Phoenix or to go tracking down internal Huawei tools, as those are the only other pieces of software I know of for flashing the device back from such a brick situation.
Click to expand...
Click to collapse
How can I find it? I have found this thread currently I am downloading all necessary files + it's for Kirin 960 which is good I think. So do you think this will work? Here is the link: https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693

U dont need hikey, just use image download tool 2.0.0.9

kikson112 said:
U dont need hikey, just use image download tool 2.0.0.9
Click to expand...
Click to collapse
So even if my device is recognized in fastboot and serial port (test point) mode it means I can unbrick it with Image Download Tool by flashing stock firmware? Cause my device is super duper dead black screen stuck in fastboot tried every single key combination plus I've let it charge for 2 nights still nothing and PC still recognizes in fastboot only..
EDIT: My bootloader is locked.
Thanks for replying btw! :highfive:

writing by idm is from test point usb com 1.0, i cant promis u that all goes well, probably imei will gone, beckup oem info from fastboot it may be help for future,
and if all goes bad, u cant do anythink more, feel free to contact me

kenzyyy said:
So even if my device is recognized in fastboot and serial port (test point) mode it means I can unbrick it with Image Download Tool by flashing stock firmware? Cause my device is super duper dead black screen stuck in fastboot tried every single key combination plus I've let it charge for 2 nights still nothing and PC still recognizes in fastboot only..
EDIT: My bootloader is locked.
Thanks for replying btw! :highfive:
Click to expand...
Click to collapse
3 Step Game
1st Write Board Firmware By Furious Gold Or DC Phoenix & Free TOOL IDT 2.0.0.9
2nd When Phone Powered On write Oem Info Model: VTR-L29 Vendor: hw , Country: eu
3rd Flash Stock Firmware 9.1 Or 9.0 ( C432 )
Game Over
if you need board firmware or stock firmware let me know

imeicodes said:
3 Step Game
1st Write Board Firmware By Furious Gold Or DC Phoenix & Free TOOL IDT 2.0.0.9
2nd When Phone Powered On write Oem Info Model: VTR-L29 Vendor: hw , Country: eu
3rd Flash Stock Firmware 9.1 Or 9.0 ( C432 )
Game Over
if you need board firmware or stock firmware let me know
Click to expand...
Click to collapse
Could you please post the necessary FW for P10 VTR-L29 9.0.1.185(C432E1R1P9)?
As I understand it would be the firmware with XML so i can use the Image download tool to flash it?
Thank you

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

Stuck in bootloader mode, phone not connecting to pc

I was trying to upgrade from A9 to A10 and phone booted into bootloader. probably because i didn't clear internal memory. but it didn't even let me boot back into twrp recovery, which i upgraded to be compatible with android 10.
i have done all that before and never had problems that my pc didn't recognise the phone. tried on linux, not just windows - same story. tried on different windows machine - again the same. doesn't even show it as unrecognised device under device manager. tried cleaning usb ports, still no difference. even cahnged the battery as i've read somewhere that low battery can cause phone not being recognised.
now i don't know what else to try. could be loose data pins at side usb c port that would cause this?
any help is appreciated
edit: i disassembled the phone and checked all the pins from side port. now i can't say for sure, but it seems like few pins are be shorted to ground. i'm not sure if i accidentally poked with multimeter shielding instead of pin, but i tested few times on continuity and last three pins all beeped on ground. can't really see inside the port that good, but it looks all untouched. could it be that damage is already done when they shorted for the first time or is there any hope?

Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?

VarDes said:
Did you use side usb when trying to access fastboot? Also in my opinion its a simple matter of switching active slot, like from A to B or viceversa. Also, did you update with an ota file, thru TWRP or how?
Click to expand...
Click to collapse
ofcourse i used side port. how to switch active slot if i can't access recovery nor connect phone to the pc to boot up twrp?
i updated through twrp with full android 10 zip downloaded from asus