Related
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Dulu93 said:
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Click to expand...
Click to collapse
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
k0rax said:
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
Click to expand...
Click to collapse
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i dont think so.. tried a few different cables
Dulu93 said:
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Click to expand...
Click to collapse
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
k0rax said:
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
Click to expand...
Click to collapse
i can only find die x.15 version but i think it should be enough. the problem is that ze2 is not reacting to pc commands when in bootloader.. so i can not operate in with fastboot commands and asus flash tool requires fastboot mode
maybe my last option is to flash my phone via intel phone flash tool which operates via the soc. but i dont have the necessary files. as i remember i would need some flash.xml and image
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Dulu93 said:
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Click to expand...
Click to collapse
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
k0rax said:
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
Click to expand...
Click to collapse
This did:
Make sure you go to settings-->apps-->default apps and select the dialer as your default application to make calls.
k0rax said:
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Click to expand...
Click to collapse
thank you very much for your help.
the first point chaning it to 4 zeros did the trick. i was able to reinstall the bootloader.
but i still dont have connectivity via fastboot. im sure all drivers are installed and even on linux i cant see my phone. what is that special google driver?
k0rax said:
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Click to expand...
Click to collapse
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Dulu93 said:
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Click to expand...
Click to collapse
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
k0rax said:
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
Click to expand...
Click to collapse
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
k0rax said:
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
Click to expand...
Click to collapse
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
You can leave flash tool and xfstk open same time. I flashed with xfstk, waited some time and moves between the bootloader options. Make sure no residual adb or fastboot exes are running. Then unplug the phone and plug it back in. Then it will show up. Select the option you have and click start. See if the bootloader shows any life or incoming partitioning happening . If that doesn't work reboot to bootloader scroll around in it to make sure it's loaded , it brings in the correct serial intermittently. But I don't think it's necessary.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
So xfstk reboots
Xfstk round two no reboot scroll around
AFT
Unplug USB from phone and reconnect
Should show up .
Then click start. Did it give an error with that X?
Look at processes and see if it's launched adb or fastboot
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
I think you're close - it's flashing what's needed, and recognized the phone, although it did for me also but fastboot didn't work until the drivers with adb and fastboot. The last things I would think is reinstall the Google adb fastboot drivers with the phone connected to the USB port that got you this far, and if there is some serial no verification, look for .14 version of AFT.
Tl;dr: DM-VERITY error after upgrading, SIM card not recognized. Can't get fastboot to work to try out a solution. Everything is going to ****.
So... this one's a doozy.
I tried to install the update by dropping it onto my phone and using TWRP to install it, which I ended up having to update. After I updated, I get a brief second popup screen when I reboot telling me that there is an invalid DM-VERITY (it only pops up for a second). When the phone loads, it doesn't recognize SIMs.
I did some research and it looks like the issue can be fixed by flashing the stock recovery. So I go to flash the stock recovery, which requires the usage of fastboot. Which I always have problems with.
Sure enough, adb recognizes my device but fastboot doesn't. I have all the drivers downloaded, so I go check on my device in device manager. For some reason, it's always listed under "Portable Devices" no matter what I do... no matter whether I enable/disable USB debugging, MTP/PTP/Charging, etc. I was under the impression that a device not being recognized by fastboot meant that you had to go find it under "other devices" and manually update the drivers. However, the only options here are ADB drivers, not bootloader ones.
So I did more research. Turns out that Windows 10 is ****ty and you have to disable secure boot to install unsigned drivers. So I went into my BIOS, disabled it, booted into safe mode, reinstalled the drivers, and... nothing.
So I'm basically where I started and for the first time in a while, I have no clue what to do. Nothing's working. I even tried to load an older version of OxygenOS and install it with TWRP (sideloading didn't work), which didn't work. I'm totally stuck and I have no idea what to do.
If you don't care about your data, just use the unbrick guide method 2. Don't know about the first one, I have never used that. That will get you to a like new phone. You could even get 4.0.3 version, using the newer unbrick toolkit.
Windows 10 x64 isn't that sh**y. I've never had issues with the drivers, and they all install automatically (fastboot, adb, unbrick tool). They all work with 4 phones without any issues: OP3, Nexus 5X, Nexus 5, Nexus 4.
True, I had just unbrick my op3 2 days back by method 2 .
Well this was wild
So I did try to unbrick and got the Sahara communication error.
But I ended up fixing my problem! Someone on Reddit correctly pointed out that the dm-verity screen often exists simply as a result of unlocking the bootloader. I was assuming that one symptom caused the other. They suggested just reflashing OnePlus's 4.1.3 full ROM. I did it exactly the same way as I had when I got the error (with TWRP) and... it worked!
I'm astounded. My phone wouldn't work with fastboot, wasn't recognized by the unbrick toolkit, and had a host of other issues. I did 7 hours of work on it and the solution ended up being that I just needed to reinstall the OS (again). My hypothesis is that there was some hidden issue that resulted in part of the firmware being incorrectly updated, and when I wiped my device as part of my troubleshooting process it was ready to be reflashed with the OS.
Thank you guys so much anyway!
Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.
I'd tried Fastboot already, will try again momentarily though.
D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.
Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Raeffion said:
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Click to expand...
Click to collapse
First of all, TWRP doesn't work.
This link would help you to restore your device
https://forum.xda-developers.com/oneplus-7t/how-to/op7t-unbrick-tool-to-restore-device-to-t3994835
Raeffion said:
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Click to expand...
Click to collapse
I had a similar, but not as terrible experience when first attempting to get root on the 7T using the patched boot images that you used. I tried several other patched boot images, but none of them would allow the device to boot. I downloaded the full update of 10.0.5, then extracted the boot.img and it allowed me to boot the device again. Then I patched it in Magisk Manager, and everything went fine and I have root. If you have fastboot access, you can try booting your device using these images with the command fastboot boot boot.img or fastboot boot magisk_patched.img to see if your device even boots up from the images. I got stuck booting from partition b at one point, and used the command fastboot getvar current-slot to see the active partition, then I used the command fastboot --set-active=a to set partition a instead. If those commands fail then you need to update to the latest adb and fastboot and the commands will work.
This is the stock boot.img for the H1905 7T update version 10.0.5:
https://www.dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
This is the Magisk patched version of the same boot.img:
https://www.dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
If you have fastboot access, you can try booting your device using these images with the command fastboot boot boot.img or fastboot boot magisk_patched.img to see if your device even boots up from the images.
Click to expand...
Click to collapse
I've attempted both, I was still in a bootloop sadly.
SkippRunning said:
I got stuck booting from partition b at one point, and used the command fastboot getvar current-slot to see the active partition, then I used the command fastboot --set-active=a to set partition a instead. If those commands fail then you need to update to the latest adb and fastboot and the commands will work.
Click to expand...
Click to collapse
My current partition was still in partition A.
Aswin08 said:
This link would help you to restore your device.
Click to expand...
Click to collapse
My first try with the unbrick tool didn't even sense my phone. I saw the FAQ and then tried to find the Qualcomm drivers in my device manager to no avail, although I did find Kedacom drivers which I could not even attempt to flash over since Windows told me that the driver I was trying to push was out of date. Here is my original post on that thread:
Raeffion said:
I see neither QDLOADER 9008 nor QHUSB_BULK in my device manager and my device is not detected by the MSMDownloadTool. I do see, however, a Kedacom USB device in my device manager titled "Android Bootloader Interface". I just want to be sure that I should download the driver you provided onto my phone before I brick it any further.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
As you can see, I did not yet mention that I still tried pushing the driver since I haven't had a reply yet. I don't want to double-post there but I'm getting no luck elsewhere. I really want this tool to work, is there some way to force push these drivers or is that a bad idea? If it is, any other ideas?
EDIT: Nevermind. I think it's bricked pretty good, I'll probably have to give up on this. When I plug it in, it only goes to bootloader, doesn't boot into recovery, system, or even show the battery percentage when charging. Bootloader hasn't been giving me many options either since the commands I've tried aren't going through. Updating ADB right now, don't know if it's likely that it's causing issues right after I already updated it.
Raeffion said:
I've attempted both, I was still in a bootloop sadly.
My current partition was still in partition A.
My first try with the unbrick tool didn't even sense my phone. I saw the FAQ and then tried to find the Qualcomm drivers in my device manager to no avail, although I did find Kedacom drivers which I could not even attempt to flash over since Windows told me that the driver I was trying to push was out of date. Here is my original post on that thread:
As you can see, I did not yet mention that I still tried pushing the driver since I haven't had a reply yet. I don't want to double-post there but I'm getting no luck elsewhere. I really want this tool to work, is there some way to force push these drivers or is that a bad idea? If it is, any other ideas?
EDIT: Nevermind. I think it's bricked pretty good, I'll probably have to give up on this. When I plug it in, it only goes to bootloader, doesn't boot into recovery, system, or even show the battery percentage when charging. Bootloader hasn't been giving me many options either since the commands I've tried aren't going through. Updating ADB right now, don't know if it's likely that it's causing issues right after I already updated it.
Click to expand...
Click to collapse
Are you starting the programs as an Administrator?
SkippRunning said:
Are you starting the programs as an Administrator?
Click to expand...
Click to collapse
Yeah, tried it again for good measure. Is there any chance I could get this issue resolved spending less than $100 by sending it to a OnePlus repair center or elsewhere? I'm not sure they do software repairs such as this, I didn't purchase a warranty since I figured I'd root this phone and I no longer know my IMEI since I can't access the phone to check.
Raeffion said:
Yeah, tried it again for good measure. Is there any chance I could get this issue resolved spending less than $100 by sending it to a OnePlus repair center or elsewhere? I'm not sure they do software repairs such as this, I didn't purchase a warranty since I figured I'd root this phone and I no longer know my IMEI since I can't access the phone to check.
Click to expand...
Click to collapse
Ive never sent my devices in for service so Im not sure about that. The fact that you have access to fastboot still though makes me think that you arent totally screwed yet. When I had stuff go wrong and I went to use to MSM tool, I didnt have the proper drivers installed, and my device never showed up in device manager. After installing a different set of drivers and rebooting my pc, the device showed up in device manager under the Ports section. I was able to get back into my device without the unbrick tool by switching the active partition. Did you say you already checked your active partition with command fastboot getvar current-slot? If you are on slot a, have you tried setting slot b as the active and seeing what happens? This is the command fastboot --set-active=b.
Here is a driver for the unbrick tool to recognize your device that might work for you. https://www.dropbox.com/s/lgt1qanfqs8pvbe/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0
SkippRunning said:
Did you say you already checked your active partition with command fastboot getvar current-slot? If you are on slot a, have you tried setting slot b as the active and seeing what happens? This is the command fastboot --set-active=b.
Click to expand...
Click to collapse
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
SkippRunning said:
After installing a different set of drivers and rebooting my pc, the device showed up in device manager under the Ports section. I was able to get back into my device without the unbrick tool by switching the active partition.
Here is a driver for the unbrick tool to recognize your device that might work for you.
Click to expand...
Click to collapse
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
EDIT: I installed the driver but nothing has changed from before. The MSM tool still doesn't detect my phone, I made sure it was run as Administrator. My device drivers are still Kedacom which I attempted to update the driver using a file on my computer once again and Windows wouldn't allow it. Am I simply looking in the wrong place to manually install this driver? My device manager is set to view devices by type and plugging in my phone causes only the Kedacom USB device to appear, so I assume I don't have QDLOADER 9008 or QHUSB_BULK devices listed there. I can provide screenshots of my device manager window if it helps.
Raeffion said:
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
Click to expand...
Click to collapse
Hooray! Almost haha! It is the worst feeling when you mess up your brand new device, but as long as I have fastboot I dont stop trying to fix my mistakes. You should be able to fix it for sure.
---------- Post added at 04:35 AM ---------- Previous post was at 04:21 AM ----------
Raeffion said:
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
EDIT: I installed the driver but nothing has changed from before. The MSM tool still doesn't detect my phone, I made sure it was run as Administrator. My device drivers are still Kedacom which I attempted to update the driver using a file on my computer once again and Windows wouldn't allow it. Am I simply looking in the wrong place to manually install this driver? My device manager is set to view devices by type and plugging in my phone causes only the Kedacom USB device to appear, so I assume I don't have QDLOADER 9008 or QHUSB_BULK devices listed there. I can provide screenshots of my device manager window if it helps.
Click to expand...
Click to collapse
On my pc, I didnt have any issues with the drivers, but when I was helping a friend over TeamViewer trying to do the same thing you are trying to do, the drivers just didnt help no matter what and it wasnt listed in the device manager. I was able to make it show properly on his pc by using the steps explained in this article. https://docs.microsoft.com/en-us/wi...boot-configuration-option?redirectedfrom=MSDN After restarting his pc, the device showed up properly in device manager with test mode enabled.
Are you able to access adb now, or still only fastboot?
SkippRunning said:
Are you able to access adb now, or still only fastboot?
Click to expand...
Click to collapse
I embarrassingly don't even really remember all the specifics about how ADB works, although I don't think I have access since I'm in a bootloop when I launch Android. Unless I have access to ADB via fastboot or recovery, I don't think I do.
SkippRunning said:
On my pc, I didnt have any issues with the drivers, but when I was helping a friend over TeamViewer trying to do the same thing you are trying to do, the drivers just didnt help no matter what and it wasnt listed in the device manager. I was able to make it show properly on his pc by using the steps explained in this article. After restarting his pc, the device showed up properly in device manager with test mode enabled.
Click to expand...
Click to collapse
Yeah I had no idea what Windows test mode was. Before I rebooted just now to install the drivers you provided, I actually launched into Windows test mode with no command from me telling Windows to. I thought Windows invalidated my license yet again tbh, glad to know it didn't. I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Raeffion said:
I embarrassingly don't even really remember all the specifics about how ADB works, although I don't think I have access since I'm in a bootloop when I launch Android. Unless I have access to ADB via fastboot or recovery, I don't think I do.
Yeah I had no idea what Windows test mode was. Before I rebooted just now to install the drivers you provided, I actually launched into Windows test mode with no command from me telling Windows to. I thought Windows invalidated my license yet again tbh, glad to know it didn't. I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Click to expand...
Click to collapse
It will just make driver installing issues less likely. When you boot your phone, what happens on the screen? Does it get stuck on a certain screen or just restart over and over? You can see if adb can see your device with the command adb devices, and it should list your device. If not, try fastboot devices and it should be listed. You need to put the device into EDL mode for the unbrick tool to work, and for it to be shown in device manager. My friends device manager listed Kedacom just like yours, and I didnt do anything to that at all. I just used test mode, installed the Qualcomm drivers, put the phone into EDL mode and the unbrick tool should recognize it. If your phone is listed when you type adb devices, you can use command adb reboot edl to enter that mode needed for the unbrick tool.
Raeffion said:
I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Click to expand...
Click to collapse
Sadly my drivers haven't changed. I uninstalled and reinstalled the installation file you gave me since I first installed it via WWAN-DHCP instead of ETHERNET_DHCP. I use a VPN so I figured that may have affected the installation, although for some reason I didn't think to just turn off the VPN when I reinstalled. Regardless, I don't think my VPN or the way I installed the driver is the cause of the drivers mentioned not being found in my device manager, so I'm likely not going to bother.
Raeffion said:
Sadly my drivers haven't changed. I uninstalled and reinstalled the installation file you gave me since I first installed it via WWAN-DHCP instead of ETHERNET_DHCP. I use a VPN so I figured that may have affected the installation, although for some reason I didn't think to just turn off the VPN when I reinstalled. Regardless, I don't think my VPN or the way I installed the driver is the cause of the drivers mentioned not being found in my device manager, so I'm likely not going to bother.
Click to expand...
Click to collapse
Another problem that can cause your phone to not show up in device manager is the usb port you are using. Have you tried any other ports? Are you able to shut your phone all the way off by holding power until it turns off? If you can unplug the phone and turn it off, then hold the volume up and volume down buttons together, then plug the cable back into the phone and it should put it into EDL mode.
SkippRunning said:
When you boot your phone, what happens on the screen? Does it get stuck on a certain screen or just restart over and over?
Click to expand...
Click to collapse
It just shows the boot animation, it doesn't restart.
SkippRunning said:
You can see if adb can see your device with the command adb devices, and it should list your device. If not, try fastboot devices and it should be listed.
Click to expand...
Click to collapse
ADB shows no devices attached, fastboot shows my device.
SkippRunning said:
You need to put the device into EDL mode for the unbrick tool to work, and for it to be shown in device manager. My friends device manager listed Kedacom just like yours, and I didnt do anything to that at all. I just used test mode, installed the Qualcomm drivers, put the phone into EDL mode and the unbrick tool should recognize it. If your phone is listed when you type adb devices, you can use command adb reboot edl to enter that mode needed for the unbrick tool.
Click to expand...
Click to collapse
I seem to have been missing a vital part of information. I don't know why the term "EDL" just went over my head, I probably just associated it was fastboot mode when I looked it up. How do I get into EDL mode? Is it safe to assume the method listed here works for the OnePlus 7T?
Raeffion said:
It just shows the boot animation, it doesn't restart.
ADB shows no devices attached, fastboot shows my device.
I seem to have been missing a vital part of information. I don't know why the term "EDL" just went over my head, I probably just associated it was fastboot mode when I looked it up. How do I get into EDL mode? Is it safe to assume the method listed here works for the OnePlus 7T?
Click to expand...
Click to collapse
Fastboot mode and EDL mode are two different things. I have never used the fastboot to EDL method, but I have read about it and I assume it should work atleast on some devices. Unplugging from pc and turning the phone off, then holding both volume buttons and then plugging the cord into the device should enter EDL mode without commands.
SkippRunning said:
Fastboot mode and EDL mode are two different things. I have never used the fastboot to EDL method, but I have read about it and I assume it should work atleast on some devices. Unplugging from pc and turning the phone off, then holding both volume buttons and then plugging the cord into the device should enter EDL mode without commands.
Click to expand...
Click to collapse
I must have assumed that it was fastboot mode since when I held those buttons and plugged it in, I'd always launch into fastboot mode. Perhaps it's different with the US version? That's the version I have.
Raeffion said:
I must have assumed that it was fastboot mode since when I held those buttons and plugged it in, I'd always launch into fastboot mode. Perhaps it's different with the US version? That's the version I have.
Click to expand...
Click to collapse
The only version I have used at all is the US one. You could try holding both volume buttons for a few seconds before plugging the cable into the phone, but if that doesnt work you can try the fastboot to edl method. I have no experience with it at all though so I dont know if it works with this device or not, but you would just open the edl.cmd file and it should put the phone into edl mode.
https://www.dropbox.com/s/951fm98u5rd2kjr/FASTBOOT-EDL-MODE.zip?dl=0
SkippRunning said:
The only version I have used at all is the US one. You could try holding both volume buttons for a few seconds before plugging the cable into the phone, but if that doesnt work you can try the fastboot to edl method. I have no experience with it at all though so I dont know if it works with this device or not, but you would just open the edl.cmd file and it should put the phone into edl mode.
https://www.dropbox.com/s/951fm98u5rd2kjr/FASTBOOT-EDL-MODE.zip?dl=0
Click to expand...
Click to collapse
It just boots me into Android sadly. I don't know that there's any way to get into EDL mode for me. Possibly due to my use of the experimental TWRP and mauronofrio's Stock Fastboot ROM tool.
Raeffion said:
It just boots me into Android sadly. I don't know that there's any way to get into EDL mode for me. Possibly due to my use of the experimental TWRP and mauronofrio's Stock Fastboot ROM tool.
Click to expand...
Click to collapse
What happens if you use command fastboot boot boot_stock_10.0.5_US.img using this file?
https://www.dropbox.com/s/cl9l662xkyey5oq/boot_stock_10.0.5_US.img?dl=0
SkippRunning said:
What happens if you use command fastboot boot boot_stock_10.0.5_US.img using this file?
Click to expand...
Click to collapse
No dice.
My problem started when I attempted to bypass the FRP by flashing a custom TOT file. I neglected to notice the file was specified for a 32GB version. I flashed it on a 16GB version using LGUpgrade Tool. The phone then froze at the splash page that just says "Google" . I thought I was fortunate enough to be able boot to recovery mode and so I flashed the stock firmware through ADB - the same ROM version that was previously on my phone and from a copy which I had used in the past with no problems. Everything seemed to be working again except my PC doesn't detect the USB connection anymore. I've tried the same procedure but now the command 'adb devices' doesn't list the phone. However, there is a point when I boot to recovery mode the PC makes a sound as if it detects the phone but then moments later it makes the other sound as if it gets disconnected. As I stated earlier, my phone seems to be where I was stuck at FRP with Android version 7.1.2 but my problem now is I can't get the PC to detect the phone when it's plugged into its USB connection. Nothing shows in Windows Explorer as well as Device Manager? I tried re-installing the drivers. Stopping and restarting the ADB server... still no detection. Is there a way to set USB mode to MTC while in FRP mode? Should it matter in Recovery Mode?
I'm going to wait for a response before I attempt to flash again but this time through the SD card because this will be a first time for me using that method and I hope there's a less risky solution.