Hi guys, is it just me or does any TWRP above 2.3.2.3 not get detected by ADB when in recovery mode? I've tried using TWRP 2.5.0.0 that's linked in the development section but my computer does not detect the phone at all when it is plugged in (USB 2). I've also tried other computers and none detect it, they don't even make the plugged in notification sound.
Using TWRP 2.4.0.0, all computers (3 different PCs) manage to detect it being plugged in but it shows up in device manager as "Unknown device" and no amount of reinstalling the drivers help at all.
So now I am using the 2.3.2.3 as it's the only recovery that seems to work properly with ADB. I have tested with CWM so can't comment on that but it seems like ADB is broken on TWRP above 2.3.2.3.
Just tried the new experimental 2.6.0.0 in the development section and it has the same problem as 2.5.0.0. My computer doesn't detect the phone being plugged in at all.
I have had the same problem, I'm honestly not sure that this feature is supported anymore.
It used to be(on my older Atrix) that in recovery, when you mount sd or external sd, it would pop up on the computer with its own drive letter, and with adb support. Did this ever work for you with your Razr M? And if so, what recovery/version?
Now(with the Razr M) I have tried cwm and twrp, and mounting sd or external sd does nothing as far as the computer is concerned. My device manager doesn't even show unknown devices. I think it has something to do with the fact that the razr has no drive letter(s) when you plug it in, but I could be wrong about that.
If you find a driver that works, I would really like to try it out as well.
stesaint said:
I have had the same problem, I'm honestly not sure that this feature is supported anymore.
It used to be(on my older Atrix) that in recovery, when you mount sd or external sd, it would pop up on the computer with its own drive letter, and with adb support. Did this ever work for you with your Razr M? And if so, what recovery/version?
Now(with the Razr M) I have tried cwm and twrp, and mounting sd or external sd does nothing as far as the computer is concerned. My device manager doesn't even show unknown devices. I think it has something to do with the fact that the razr has no drive letter(s) when you plug it in, but I could be wrong about that.
If you find a driver that works, I would really like to try it out as well.
Click to expand...
Click to collapse
even if a device doesnt have a drive letter it should still show up in device manager
True, I only mean having no drive letter might be the reason mounting from within recovery isn't functioning.
I tried out like 4 different drivers before I found one that worked for ADB. It might be that my computer thinks it has a driver for it, and it just doesn't work. I do hear the device inserted sound..
stesaint said:
I have had the same problem, I'm honestly not sure that this feature is supported anymore.
It used to be(on my older Atrix) that in recovery, when you mount sd or external sd, it would pop up on the computer with its own drive letter, and with adb support. Did this ever work for you with your Razr M? And if so, what recovery/version?
Now(with the Razr M) I have tried cwm and twrp, and mounting sd or external sd does nothing as far as the computer is concerned. My device manager doesn't even show unknown devices. I think it has something to do with the fact that the razr has no drive letter(s) when you plug it in, but I could be wrong about that.
If you find a driver that works, I would really like to try it out as well.
Click to expand...
Click to collapse
The Razr M doesn't get a drive letter because starting with Honeycomb (Android 3.0) USB mounting was ditched in favor of MTP. The problem isn't a driver issue because for TWRP 2.5.0.0 and 2.6.0.0, in both those versions, the phone doesn't get detected at all by any computer. If it were a driver issue, the phone will at the very least show up in device manager as "unknown device".
This is more to do with a recovery problem concerning TWRP. For some reason, those two versions somehow break USB support on the phone when in recovery.
Does anyone know where a flash-able version (zip) of TWRP 2.3.2.3. might be?
We could easily flash "back" , reboot recovery and try the older version.
For the 'm of course.
keyman91 said:
This is more to do with a recovery problem concerning TWRP. For some reason, those two versions somehow break USB support on the phone when in recovery.
Click to expand...
Click to collapse
I guess I just thought the issue had a slightly larger scope than the recoveries being bugged. I don't recall every having a recovery on the M be able to mount USB, though my experience is limited to the last week and a half. I had CWM at first, I tried one(don't remember the version) and then updated to 6.0.3.2, and it still wasn't able to. I tried with twrp 2.3.2.3, 2.5.0.0 and 2.6.0.0 and it wouldn't work in any of them.
Related
First some background:
Playing around with some ROMs, I loaded up MIUI. I wanted to see what all the fuss was about. While installing from ROM Manager, the subsequent boot into CWM started my backup and installed the ROM. During the process CWM notified me the install was attempting to overwrite the recovery partition. I inadvertently said yes, one of the bad things about touch recovery...fat fingers.
Result:
CWM was blown away. MIUI failed to install Google Apps.
I connect the N7 up to my PC. It is not detected. No ADB available, however I can use wireless ADB so I installed ROM manager and reflashed CWM. This was were the fun began. Everything on my internal storage got nuked during the install and attempted recovery. I had to format internal storage.
No biggie, I have backups on my laptop through WUGFresh Root Kit. I will restore back to stock and start over.
Problem:
No computer I connect the N7 to detects it, regardless of USB connection method nor OS on the PC (Ubuntu, Win 7, Mint). I still have wireless ADB but that doesn't help with fastboot.
Current Status:
Currently I am running AOKP, after flashing multiple ROMs and Recovery between TWRP (current) and CWM. Also I have done many factory resets, cache cleaning, etc.
My diagnosis:
I think my boot, recovery or bootloader partition is borked due to the fat finger in CWM while installing MIUI. The added bonus...without being able to connect the N7 to any PC, I can't get into recovery unless I get lucky (1 out of 10 tries I get lucky and can get into recovery). I can get into recovery as long as I can boot into a ROM and do any common method to reboot recovery.
Question:
Now my question, does anyone have any ideas what I can do to get the USB connection working again to allow ADB/Fastboot connections?
Additional info/Review:
I have a GNex that I can ADB/Fastboot into without issue.
I have tried multiple different cables to connect to PC/Laptops.
As mentioned, I have tried multiple PCs to attempt a connection running everything from Windows 7 to variations of Linux (Mint and Ubuntu)
All the cables work fine with GNex, excluding one cable I deemed trashworthy.
I am fairly certain that the micro-USB port is fine, I can charge without issue even connected to a PC. OTG cable works perfectly fine.
I did something saying a port was open from the N7 that cause USB connection to fail. I forget what I did to find that message or what program I was using. I think I was trying to do a adb usb command from the command line on the N7.
USB Debugging is enabled.
More info:
No errors in logcat when connecting N7 to PC.
Try to do complete wipe & flash stock . My desktop has never detected the n7 but the fastboot works. I was able to flash stock using wugs toolkit.
Sent from my GT-I9300 using Tapatalk 2
That is the problem, I can't get any PC to recognize the n7 is connected. therefore, wugs root tool kit wont work. it uses fastboot and adb. without the drivers loaded and the device detected, I can't use wugs. this happens even on machines I have never plugged the n7 into.
If I could find a flashable zip of stock, that might do the trick.
I am wondering if I can use the otg cable and connect from my phone with adb? I don't think I can run fastboot commands from the phone though.
Sent from my Nexus 7 using Tapatalk 2
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
panjaby said:
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
even in boot manager, the device does not show in device manager on windows and it can't be seen on Linux either when looking for attached devices.
With my old viewsonic gtab I use to verify there was a device connected from command line, that doesn't work either. I'll post that command later today, just for reference.
Sent from my Nexus 7 using Tapatalk 2
OK, I have verified the problem is on the tablet side. I can connect my OTG cable to the tablet and mount my GNex allowing me to perform adb commands sent to the phone. I can not mount my tablet to the phone reversing the cable.
N7 ---> OTG ---> USB ---> GNex (works)
GNex ---> OTG ---> USB ---> N7 (fails, phone does not recognize the tablet being connected. I verified I could connect to a USB stick without issue.)
I think this narrows it down to MTP/PTP being disabled somewhere. Since it affects fastboot as well, I am assuming something in boot or bootloader. I ruled out recovery due to recovery working correctly when I can get to it.
Any ideas?
So, I made the ludicrously stupid mistake of somehow accidentally basically wiping the OS from my tablet with TWRP because I was having problems with it and was trying to figure stuff out. Anyways, I didn't have a backup on the device so I found a stock rom online for it. I tried plugging it into my computer and directly transferring the zip to the device, but it just flat-out refuses to do so. It tells me the device is either not responding or disconnected. I found out that if I try dragging it into a folder it should work, but all it does is give me a different error, telling me that it exceeds the size limit or something. Anyways, next I tried using ADB sideload but the device isn't recognized at all. As a last resort, I finally got a USB-OTG cable and tried that. However, TWRP refuses to mount the thing. It isn't recognized at all. I'm using TWRP v2.8.0.1. Tell me, am I completely screwed?
My device model is SM-T230NU, if that helps at all.
Jorvalt said:
My device model is SM-T230NU, if that helps at all.
Click to expand...
Click to collapse
Download one of the following files to PC, extract with either 7zip or WinRAR, and flash with Odin (boot your tablet into download mode: home, vol-, and power; and connect with USB):
--SM-T230NU UEU0AOD1 XAR Region (USA)
--SM-T230NU UEU0AOD1 XAC Region (Canada)
--Nook Edition SM-T230NU OVU0AOG1 BNN Region (Nook Edition)
thisisapoorusernamechoice said:
Download one of the following files to PC, extract with either 7zip or WinRAR, and flash with Odin (boot your tablet into download mode: home, vol-, and power; and connect with USB)
Click to expand...
Click to collapse
Forgot to mention, Odin doesn't recognise it either.
Jorvalt said:
Forgot to mention, Odin doesn't recognise it either.
Click to expand...
Click to collapse
install drivers and stop kies if running, also reinstalling drivers will help if you already have drivers
thelous said:
install drivers and stop kies if running, also reinstalling drivers will help if you already have drivers
Click to expand...
Click to collapse
The problem is that my computer doesn't actually recognize the device type, and therefore doesn't have any drivers for it and can't find any drivers for it.
Jorvalt said:
The problem is that my computer doesn't actually recognize the device type, and therefore doesn't have any drivers for it and can't find any drivers for it.
Click to expand...
Click to collapse
I'm pretty sure you can get the drivers from here:
http://www.samsung.com/us/support/downloads
Jorvalt said:
So, I made the ludicrously stupid mistake of somehow accidentally basically wiping the OS from my tablet with TWRP because I was having problems with it and was trying to figure stuff out. Anyways, I didn't have a backup on the device so I found a stock rom online for it. I tried plugging it into my computer and directly transferring the zip to the device, but it just flat-out refuses to do so. It tells me the device is either not responding or disconnected. I found out that if I try dragging it into a folder it should work, but all it does is give me a different error, telling me that it exceeds the size limit or something. Anyways, next I tried using ADB sideload but the device isn't recognized at all. As a last resort, I finally got a USB-OTG cable and tried that. However, TWRP refuses to mount the thing. It isn't recognized at all. I'm using TWRP v2.8.0.1. Tell me, am I completely screwed?
My device model is SM-T230NU, if that helps at all.
Click to expand...
Click to collapse
you don't have an sd slot? just copy a FLASHABLE zip onto the card and flash in TWRP from there.
thisisapoorusernamechoice said:
I'm pretty sure you can get the drivers from here:
Click to expand...
Click to collapse
I meant that I have drivers for it, but neither my computer nor Odin actually recognizes it, so having the drivers is pointless anyways.
Droidphilev said:
you don't have an sd slot? just copy a FLASHABLE zip onto the card and flash in TWRP from there.
Click to expand...
Click to collapse
I don't have an SD slot in my computer, no. I also don't happen to have a spare micro SD card laying around either. As soon as I'm able, I'll try and get one and let you guys know if it works.
Side note: The ROM doesn't necessarily have to be flashable considering TWRP can install zips directly. Obviously it has to be in connected storage that the device recognizes, though.
Jorvalt said:
I meant that I have drivers for it, but neither my computer nor Odin actually recognizes it, so having the drivers is pointless anyways.
I don't have an SD slot in my computer, no. I also don't happen to have a spare micro SD card laying around either. As soon as I'm able, I'll try and get one and let you guys know if it works.
Side note: The ROM doesn't necessarily have to be flashable considering TWRP can install zips directly. Obviously it has to be in connected storage that the device recognizes, though.
Click to expand...
Click to collapse
TWRP can only flash *TWRP flashable* zips or .img for kernels/radios but nothing more. i meant sd slot in the tablet of course.
im having the same issue, because odin will say it worked , but simce it doesnt show the device , in win 10 device manager it only shows samsung usb composite drivers, in idin it doesnt show anything , if im not mistaken , odin need to recognize the device, so how do i get win 10 to recognise the tab 4?
Vintage144 said:
im having the same issue, because odin will say it worked , but simce it doesnt show the device , in win 10 device manager it only shows samsung usb composite drivers, in idin it doesnt show anything , if im not mistaken , odin need to recognize the device, so how do i get win 10 to recognise the tab 4?
Click to expand...
Click to collapse
Only odin will detect your tab if there is no rom booted up. Try flashing deodexed stock rom from twrp
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Download : TWRP For Catfish
Source Device Tree: Device Tree For Building TWRP
reserved
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
tfpiaoyang said:
Thanks.
However...is there anyone would share a twrp backup of Chinese version stock rom? Thanks in advance.
Click to expand...
Click to collapse
https://mega.nz/#F!BEFGBQKI!uetGnJxWqvG-JRmQNPeBvw
btw any qq grp to communicate?
MicrosoftBug said:
What's the command to install this?
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery ***.img
restore to chinese version cant OTA, will get a big red "!" in recovery...
I have been out of the custom recovery world too long and never tried on a watch before. Trying to flash twrp on my new TW Pro (H) so I can flash janjans rom. Have ADB and drivers (windows 7), have twrp.img ready.
cmd prompt not recognizing adb command. Cant remember how to proceed...how to open fasboot, unlock bootloader.
I know im missing something simple but stuck. Can anyone help jumpstart me?
Update: Got twrp installed after flailing about for awhile. Bottom line, operator error.
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
Did you try running fastboot from bootloader? Also maybe try sideload the rom from twrp, that worked for me.
haplohaplo said:
This may be the wrong place to post, but I can't seem to find my issue anywhere and I'm getting a little desperate.
I'm Stuck! Accidentally deleted 'system' int twrp when deleting data for a reset for the watch. Now no OS installed and computer doesn't want to recognize the ticwatch pro through usb (directly attached to dock and then usb to windows 10). I'm not sure it's a driver issue because it should at least be recognized in device manager as 'unknown' but nothing is showing. I now only have bootloader and twrp recovery on my watch. I have everything I need to reinstall the os, but without a way to connect to the watch I can't move the files to the watch to flash it, nor can I connect through usb to push them over! I'm stuck! I'm missing something simple I'm sure, but I don't know what? I just want a way to connect the watch from it's dock to windows 10 through usb cable from watch dock. Then I'm good to go. But I can't.
HELP Please!
Click to expand...
Click to collapse
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks. I've tried three different chargers (though I'm not sure if the other two that I bought are actually capable of transmitting data) and three different computers. I ordered a new charger that says it is able to transmit data, so hopefully when that arrives it will work. Makes no sense to me that I can get into bootloader and twrp and yet not see the watch in device manager.
Kellicros said:
That is probably a faulty USB cable, try a different cable or a different PC, Windows 10 should recognize your watch automatically and if you have generic adb drivers previously installed, it should work.
You may also try to manually install the drivers from here:
https://www.xda-developers.com/where-to-download-android-usb-drivers/
Click to expand...
Click to collapse
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
haplohaplo said:
Thanks for the reply. I've got 4 different chargers (including the oem one) two of the additional ones I have state they are capable of data sync. I've tried them on 3 different computers and the watch doesn't not show in device manager, recognized or otherwise. I just can't see this as a cable issue, but I don't know what else to think. I just received the newest sync cable I ordered the other day (now my fourth) and still nothing. I'm stuck. If it would at least show in device manager then it would only be a matter of drivers, but it doesn't. Seems a little odd to me that it stopped when I accidentally deleted the OS. The OS isn't even required for bootloader or TWRP and both of those load on the watch. I can't figure it out and I opened a repair ticket with Mobvoi a few days ago, but there has been no response yet. So frustrating!
Click to expand...
Click to collapse
You deleted the OS? What do you mean by that? Is the watch still working on its own?
Sounds to me like a faulty connector, I would send it back if it is still under warranty.
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
haplohaplo said:
I wiped the system folder by mistake. I got click happy when doing an advanced wipe. My fat thumbs ticked the system folder. So no OS installed now. Just bootloader and TWRP. But since the watch isn't recognized by any PC on any of the 4 cables I have, I can't move a Rom on to it to flash it. Nor can I push one over on adb as neither fastboot in bootloader or adb in TWRP see the watch. Not a driver issue since I've tried every one I could find and because device manager doesn't see the watch at all, know or unknown.
Click to expand...
Click to collapse
Try 1. Flash boot.img via fastboot
2. Reboot and connect, check via adb if it's detected
3. Install via sideload ROM
(adb sideload file.zip)
This issue was that I couldn't connect with fastboot at all. That being said, it turns out the problem was with the watch itself. Mobvoi, replaced the watch with a brand new one free of charge so it's all good now.
Any chance you have, or know of, a TWRP for the TicWatch E2/S2 ?
Would be much appreciated.
Hey, is it possible to connect a SD card or usb flash drive to the watch via otg when booted into twrp to create a full backup?
Hello, what would I need to do in order to port this to the TicWatch Pro 2020? The hardware is almost identical, except it has more RAM, the codename is catfish_ext. I have an unlocked bootloader and tried to boot this recovery, but I get FAILED (remote: 'dtb not found').
EDIT: Nevermind, I have found that the recovery for the 4G EU verison also works with mine. Here is the link to a working image: https://drive.google.com/file/d/1XNejRoLecLeadEj1CAW_zrTUP5bkUJZ8/view?usp=sharing
And here is the original source: https://forum.xda-developers.com/smartwatch/other-smartwatches/rom-kernel-t3821013
i made the boneheaded mistake of deleting everything off my phone in twrp (3.2.1-0) and ive had little success in trying to recover it.
1. my pc will not recognize it when its plugged in, this was also an issue when it had an os on it. ive tried to install the google usb drivers as well as the hisuite drivers with no success
2. i bought a usb otg adapter so i could possibly push the new os through there but when ever i try i get 0mb when trying to select the storage in the mount section of twrp. ive also tried reformatting the usb multiple times but that didnt work either.
3. there is no connectivity while in fastboot as well as adb
I'm caught in a tight situation and don't have the means to buy a new phone if anyone could help me out i would greatly appreciate it
shpadza said:
i made the boneheaded mistake of deleting everything off my phone in twrp (3.2.1-0) and ive had little success in trying to recover it.
1. my pc will not recognize it when its plugged in, this was also an issue when it had an os on it. ive tried to install the google usb drivers as well as the hisuite drivers with no success
2. i bought a usb otg adapter so i could possibly push the new os through there but when ever i try i get 0mb when trying to select the storage in the mount section of twrp. ive also tried reformatting the usb multiple times but that didnt work either.
3. there is no connectivity while in fastboot as well as adb
I'm caught in a tight situation and don't have the means to buy a new phone if anyone could help me out i would greatly appreciate it
Click to expand...
Click to collapse
Powerdown your phone and boot to bootloader by pressing powerkey and holding vol- then connect to your computer you should see the Nexus 6p on your pc and. from your computer download any rom of your like,gapps,root optional and copy it to your internal storage. Then just flash.
Gearswar said:
Powerdown your phone and boot to bootloader by pressing powerkey and holding vol- then connect to your computer you should see the Nexus 6p on your pc and. from your computer download any rom of your like,gapps,root optional and copy it to your internal storage. Then just flash.
Click to expand...
Click to collapse
that doesnt work either. i have all of the appropriate drivers and still nothing.
That could be your pc. Try a different port or even better another pc.
Guys I really need your help here as I'm beyond frustrated and a few hours from busting this ****ty brick of a phone.
My wife's been having that "no network issue" since the beginning of the year and some updates or roms seem to work, but only for a few days before the same damn error pops up and it renders her phone usesless.
About 2 months ago her phone got the error, so she tried installing a new rom which apparently required her to format the internal storage which wiped her current rom and EVERYTHING else. She's currently got the bootloader unlocked and TWRP Recovery, but every time I try to fastboot flash a rom or do TWRP adb sideload, her device isn't being recognized by the platform tools. I tried switching cables and PC and now the PC recognizes device (I get the sound that a device connected) but it won't show on fastboot devices or adb sideload devices.
What can I do? I've tried a few different platform tools and have install the Essential drivers to make sure it works, but no go.
In device manager under ports does it show "Qualcomm HS-USB QDloader 9008"? If so, it's not recoverable except by Essential. Can't hurt to ask them for help. Read some recent posts here in the Q/A section for others with this problem.
If you still have TWRP then it's a simple fix. Get a USB to USB C dongle and copy a ROM like LineageOS to a USB stick (along with gapps etc if necessary) and plug it into the bottom of your phone. TWRP will read and flash from the external storage.