So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Update: I've been trying different cables. I found one where the computers will see that a devices is connected, but am getting "USB device not recognized" with either set of drivers that I have on both computers. Making progress, but could still use some help.
DiGi760 said:
So I'm trying to fix a Xoom for a client. Her nephew was using it over Thanksgiving weekend and has managed to mess it up.
1) On a normal boot it never gets past the boot animation. The animation just loops and loops.
2) I was able to get into recovery and do a factory reset, but that didn't improve anything.
3) I can get to "Starting Fastboot protocol support" or "Starting RSD protocol support 0"
4) I have used two different moto drivers on Win 7 and Win 8, but neither computer ever recognizes the xoom is connected regardless of mode
5) Adb never sees the xoom either.
6) This device should have been completely stock, but no one knows what this kid did with this tablet.
7) USB debugging was probably off since the owner would not have known about it or had a reason to turn it on.
What are my options here? I'm thinking that I need to flash a good factory image, but I need to get some communication going first.
Click to expand...
Click to collapse
I had a problem similar to that about a year ago, somewhere in these forums was the suggestion to remove the SD card and then do a factory reset, it worked for me. My xoom just stopped working, I thought at first it was a flat battery but after charging the symptoms were the same as yours, might be worth searching through the forums if you haven't already
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
Sorry can't help , mine is just over 2 years old and except for that one problem have never had any issues so have never needed to even connect it to a PC
DiGi760 said:
There's no sd card in it, just the little plastic place holder. I've been looking all over the forums, but I normally deal with Samsungs. I've been figuring out Motorola's little quirks as I go along. Is there a recommended moto driver for these things?
Click to expand...
Click to collapse
I recently discovered these handy files when I needed to return to stock:
4G Xoom (MZ600) Restore
3G Xoom (MZ601/3) Restore
WiFi Xoom (MZ604) Restore
If you need to find out which Xoom model it is, power on whilst holding the volume down button, this will take you in to fastboot. Then (you sound like you'd know how do this, PM me if you don't) use "fastboot getvar all". This will return the model.
Unzip the file above, there's a batch file in there which will install the drivers, then fastboot the firmware over.
If you boot to fastboot, then run the batch file, it installs the drivers, then "adb device", then it asks if your device is connected - it won't show up cos it's in fastboot. Just ignore that and say yes, and it'll start flashing the files.
Sorry if I'm too late - don't visit these boards much these days. Good luck, let me know if this works.
Thanks for giving me something to try. I uninstalled the moto drivers I had and installed the ones included in the zip file and restarted my computers. The Windows 8 computer never recognizes that the xoom is connected in any mode. The 7 machine does see it in fastboot mode but as a "fastboot" device for which it fails to find drivers. When I run fastboot getvar all, all I get is <waiting for device>.
I do know that this is a wifi only (mz604) xoom. Thanks for the image files. If I can get this stupid thing to communicate with a computer, I think I'll be in business.
In fastboot mode (vol -) it won't acknowledge that it's connected. Just fastboot your image over and it will work.
If I try to do anything with fastboot, it just says "< waiting for device >". Fastboot doesn't see a device to flash to.
OK, it's either your cable or your driver. Many cables are for charging only, and have no data lines. I throw those away.
As to drivers, I'm Debian for 15 years so can't advise on Winduhs.
Oh, one more thing: I've noticed that on my old HP laptop I had to use a certain USB port, or else it wouldn't comm with my phone for fundamental actions like loading new firmware.
These were the drivers I used: https://motorola-global-portal.cust...sion/L3RpbWUvMTM4NjM1MjA0NC9zaWQvWEo3SWU5SGw=
They don't seem to be windows 8 certified though.
Sent from my Nexus 5 using Tapatalk
We finally got it. We used DriverEasy to look for drivers because we have a bunch of extra licenses and the drivers we had obviously weren't working. DriverEasy was able to install an "Android Bootloader" driver that must not be part of the SDK. Once that was installed, I was able to use fastboot to flash the images from above. The device is in good working order again and fully updated.
Thanks for all your help.
Always nice to hit the Thanks button for those who've helped.
Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk
ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.
LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
NOTE: I'm on a Mac
rajah sulayman said:
(crossposting from here as this looks like a more active sub and I'm desperate).
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
Click to expand...
Click to collapse
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Sent from my PH-1 using Tapatalk
sd_shadow said:
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Click to expand...
Click to collapse
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
rajah sulayman said:
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
Click to expand...
Click to collapse
do you know how to check which drivers are selected.?
Sent from my XT1254 using XDA Labs
sd_shadow said:
do you know how to check which drivers are selected.?
Click to expand...
Click to collapse
Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.
Actually I just remembered that Mac don't need drivers, right? Per Google:
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."
Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.
To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.
Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.
If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.
I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.
Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.
-------
Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"
None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.
bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.
A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!
Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!
Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com
This is installed and works with me
ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.
Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.
This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.
fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.