Related
Hello, I received my T-Mobile 16GB Galaxy S III today and my intentions were to flash it right out of the box( I am no stranger to doing so) but I've seem to run into a few complications. I can't even begin my rooting process since it fails to connect to my PC( Windows XP Service Pack 3) or my iMac (Lion). (With multiple USBs during each attempt)
I've downloaded Kies re-installed drivers multiple time (on both platforms)
I've tried connecting via download mode on Odin/Heimdall.
Factory Resets on the device.
I've tried the Android File Transfer on Mac, no luck either.
I've tried to simply connect it to my PC through MTP/PTP. (This resulted in the closest effort it acknowledged my phone as "Digital Still Camera" and began to open a file) When I re-install the drivers it lists the phone and Samsung modem in the task bar, but nothing happens, I still cannot access either SD card.
Any help or insight would be greatly appreciated, thank you for your time.
I'm beginning to think the device may be defective myself.
Again, thank you.
jasonren29 said:
For Mac, connect your device through usb cable. Pull down the notification bar and select PTP as connection. Fire up the Android file transfer app, you should be good.
For PC, download the tool kit from development Page, and select appropriate device, then select 1 to install device driver. Reinstall even if you have the driver already. After installation, connect your phone and select MTP. Let the pc update the driver settings, etc. Wait for a minute or two, open my computer and you should be able to transfer files now.
Let me know if you experience any issues afterward
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I tried the Mac way again made sure ptp was checked, still received a "cannot connect to device" error. Trying the toolkit way on PC now.
I had the same problem with my PC, download the toolkit and install the drivers. Thats what worked for me.
saldebot said:
I had the same problem with my PC, download the toolkit and install the drivers. Thats what worked for me.
Click to expand...
Click to collapse
Yeah, I just did that, the serial numbers never appeared on the toolkit program, so I assume it did not work. I'll give it another try though.
Dont worry, you dont even have to connect the phone to install the drivers. Just re-run the toolkit and install the drivers.
saldebot said:
Dont worry, you dont even have to connect the phone to install the drivers. Just re-run the toolkit and install the drivers.
Click to expand...
Click to collapse
Yeah, I did. I just keep getting "New Hardware Found" messages and that's it. I'll re-install the drivers a third time, after this attempt I have no idea what to do.
Well try rebooting both the phone and your computer. If you still cant get to work then the only real fix would be to exchange the unit. I hope it works and you dont have to exchange it. I hate going thru that hassle.
If you ordered from T-Mo directly call them up and speak to the loyalty department and have them send you another unit with the return kit. Make sure to tell them you use your phone for bussines and you need to have a phone. Thats how I have done my exchanges while still having a phone to play with until the new one arrives. Good luck bro.
saldebot said:
Well try rebooting both the phone and your computer. If you still cant get to work then the only real fix would be to exchange the unit. I hope it works and you dont have to exchange it. I hate going thru that hassle.
If you ordered from T-Mo directly call them up and speak to the loyalty department and have them send you another unit with the return kit. Make sure to tell them you use your phone for bussines and you need to have a phone. Thats how I have done my exchanges while still having a phone to play with until the new one arrives. Good luck bro.
Click to expand...
Click to collapse
Yeah, I think I will have to try that, unfortunately. Haha, kind of spent my whole day trying to fix is, bit of a bummer to be honest. Thanks for the luck.
No worries, hope the next unit is a winner.
Replace ASAP!
or try another PC computer.
saldebot said:
Well try rebooting both the phone and your computer. If you still cant get to work then the only real fix would be to exchange the unit. I hope it works and you dont have to exchange it. I hate going thru that hassle.
If you ordered from T-Mo directly call them up and speak to the loyalty department and have them send you another unit with the return kit. Make sure to tell them you use your phone for bussines and you need to have a phone. Thats how I have done my exchanges while still having a phone to play with until the new one arrives. Good luck bro.
Click to expand...
Click to collapse
usually when i request a defective replacement, or insurance, i get the new phone within 2 days, anyhow.
I have the same probleme with my sgh-t999v so i guess i will have to get a replacement too
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Did you wait a couple of minutes between steps 3 and 4 before giving up. I just re-did this last night; I didn't time it but my PC must have taken a minute to show COM to be ready to start Odin on the stock tar.
I was also having USB driver issues and reinstalled. My PC has been having USB issues in general with Windows 8.1 updates; had to uninstall and reinstall the same PC generic USB driver. Circa 2009 era PC needs an overhaul or replacement.
BTW, if you're using an older CF Auto root, CF went back to Odin 3.07 and updated to superSU v2.45
I did, because I was unsure what was going on. This is only the second time I've rooted a phone, so I was unsure what would happen if I pulled the battery. I think I waited about 20 minutes while looking online to figure out what was going on.
I'm not sure what you mean by an older version. I downloaded the version for my phone from chainfire.eu
http://redirect.disqus.com/url?url=...&thread=3459253652&zone=thread&area=discovery
http://redirect.disqus.com/url?url=...&thread=3443914612&zone=thread&area=discovery
Some questions I should have asked earlier: USB debugging enabled? Using USB 2.0? Tried different USB cables?
Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
PS. Did you use Kingo to root your note 4? I might give it a try.
No, I just posted links for the thoroughness of checks. I used CF Auto root. Good luck.
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
I'm thinking the MTP might be the issue, but I don't seem to have a MSD option on my note 4?
Any more ideas?
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
faile486 said:
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Click to expand...
Click to collapse
Press volume up to confirm download mode?
rawintellect said:
Press volume up to confirm download mode?
Click to expand...
Click to collapse
Yes, that has to be done to get to download mode? I'm at the screen where it says 'Downloading...Do not turn of the target!!'
faile486 said:
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
Click to expand...
Click to collapse
I'm sorry but I don't recall seeing this reply because I don't understand it now. I may have overlooked it?
Are you saying the phone appears to download but boot loops? You should see success and 0 failures prior to auto boot. Is that the CF Auto root flash in Odin or another Odin flash like recovery or stock tar? If that's happening, did you try to pull battery and delete cache and dalvik cache in recovery? Is the phone semi bricked or just not rooted? Can you Odin the recovery tar for TWRP recovery? If so, you could just flash the superSU zip file in TWRP.
http://download.chainfire.eu/supersu
Another suggestion, if you're getting anywhere with Odin, you should close and reopen Odin if doing multiple flashes. Close after each flash; i.e., power down, flash stock tar, close Odin, open Odin, flash CF Auto root, close Odin, flash recovery (download mode steps omitted since you know that already).
Again, someone might could help with detailed setup details and steps taken. Sorry if I'm not following well; I'd like to help, if possible.
samep said:
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
Click to expand...
Click to collapse
I'm using Windows 7. Using another PC is a good idea, I'll try that.
faile486 said:
I'm using Windows 7. Using another PC is a good idea, I'll try that.
Click to expand...
Click to collapse
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
samep said:
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
Click to expand...
Click to collapse
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
faile486 said:
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
Click to expand...
Click to collapse
Glad to see you among the rooted in Sprint Note 4 XDA. Hopefully your solution can be repeated for future updates. Lollipop well be here some day.
Does Kingo root Trip Knox?
Sent from my SM-N910P using XDA Free mobile app
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.
And you've removed all drivers to android and lg for it.
secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.
Which version of windows are you running? On both desktop and laptop???
secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.
Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.
I have this phone at least for another year. So at least someone out here is still willing to help.
secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.
After the update to Nougat, my PC does not recognize my OP3, doesn't even show any mobile device in Device Manager! Please suggest, tried resetting phone, restarting laptop, installed drivers also, nothing working
Update: So after starting from scratch, following the guide https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757 I reinstalled 4.0.2 and everything working smooth as ever, surprisingly, laptop recognizes phone in fastboot and adb, but not MTP.
What can be done? anyone
And of you boot into fastboot?
Puddi_Puddin said:
And of you boot into fastboot?
Click to expand...
Click to collapse
it doesn't recognise there also
Dipinn Verma said:
it doesn't recognise there also
Click to expand...
Click to collapse
It doesn't boot? Try unbrick method 2.
Puddi_Puddin said:
It doesn't boot? Try unbrick method 2.
Click to expand...
Click to collapse
no, the phone is working fine, and surprisingly works with any other laptop, but not the one through which I updated it to nougat, the one which I have always used it with
Dipinn Verma said:
no, the phone is working fine, and surprisingly works with any other laptop, but not the one through which I updated it to nougat, the one which I have always used it with
Click to expand...
Click to collapse
Hmm, and when you phone is on does it show something in the notification row?
Puddi_Puddin said:
Hmm, and when you phone is on does it show something in the notification row?
Click to expand...
Click to collapse
no nothing out of ordinary, even when I switch on mass storage, nothing, I have the verity-error also, can that be the problem? coz I lost my twrp and root when updated, should I do everything again from scratch ?
Dipinn Verma said:
no nothing out of ordinary, even when I switch on mass storage, nothing, I have the verity-error also, can that be the problem? coz I lost my twrp and root when updated, should I do everything again from scratch ?
Click to expand...
Click to collapse
DM verity should be a issue, I do recommend you to start from scratch..
Puddi_Puddin said:
DM verity should be a issue, I do recommend you to start from scratch..
Click to expand...
Click to collapse
thanks a ton for prompt reply ! I'll post here how it goes, it might help someone else
Dipinn Verma said:
thanks a ton for prompt reply ! I'll post here how it goes, it might help someone else
Click to expand...
Click to collapse
DM-verity is a non issue with MTP/fastboot/adb. It's usually related to the USB cable or port itself, or a driver issue (fastboot/adb or device).
When you connect and toggle the USB setting to MTP, toggle it to charge only then to MTP again. I've noticed in the past that it takes longer for the PC to recognize or it requires a second try.
Hw4ng3r said:
DM-verity is a non issue with MTP/fastboot/adb. It's usually related to the USB cable or port itself, or a driver issue (fastboot/adb or device).
When you connect and toggle the USB setting to MTP, toggle it to charge only then to MTP again. I've noticed in the past that it takes longer for the PC to recognize or it requires a second try.
Click to expand...
Click to collapse
okay, so this is strange, i did what you said, PTP mode is working, only pictures are accessible though, nothing else, so the problem seems to be with MTP only
It's from windows. I think youre on windows 10 and have updated without knowing. Then youre phone it's not recongnise by pc.
Reinstall windows.
null0seven said:
It's from windows. I think youre on windows 10 and have updated without knowing. Then youre phone it's not recongnise by pc.
Reinstall windows.
Click to expand...
Click to collapse
windows 8.1 only, hasn't changed. I'll try following this guide tomorrow : https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
and start from scratch, please suggest if I should be following any other guide if there is one. Thanks.
Mate, i can't tell you what to do.
On my case, it was windows 10. How i know? I try co connect at work (windows 7) & it workt fine. Reinstal windows, all ok.
FIRST, i suggest to check on another PC. If it works, 100% it's youre windows.
Ok so this is what I did. I went to device manager > right click mtp > update driver software > browse my computer > let me pick > mtp USB device > happy me ??
Good for you buddy, the mtp option doesn't even come up in device manager, it used to earlier, but not anymore
Dipinn Verma said:
Good for you buddy, the mtp option doesn't even come up in device manager, it used to earlier, but not anymore
Click to expand...
Click to collapse
Then idk what to tell yu
It may sound stupid but my windows 7 couldnt detect my op3 as well ytd..
Then I restarted both my phone and pc and it worked.
No buddy, not at all stupid, though that didn't work for me
I need some help because I am puzzled on what to do. The other night, I tried to change roms on my Pixel XL. I'm used to being able to just flash everything once in whatever order and be fine (it was much simpler years ago when I got started with modding).
Anyways, I flashed FireHound rom and gapps, but forgot the vendor. I flashed twrp and that put me into a bootloop. It would reboot back into recovery each time. So I reflashed Pixel Dust, the rom I was on before, since I didn't have a backup. I forgot to make one. Lol.
Flashed the vendor, rom, and twrp. Rebooted to a clean rom. However, I'm not rooted. I attempt to go back to twrp - and I can't. It goes straight to Android recovery/ no command screen. I can't get back into twrp.
Since this, I downloaded the newest factory image so I could just reflash and start over and fix it. But I cannot connect to any computer. I've tried multiple cables, multiple computers, and each time I get a "USB device not recognized" error. Device manager shows my device as "Unknown USB device (device descriptor request failed)." I've attempted to reinstall/update the USB drivers, windows won't update it because it says it's already up to date. Windows 10 is what I'm using.
So I am stuck. Can anyone help me? Or did I completely screw everything up?
Thanks in advance,
Sam
Enable USB debugging in Developer Options.
Sent from my Pixel C using Tapatalk
Thanks, I tried that. Still nothing different.
Do you get any response on the phone when in bootloader and USB cable is plugged in?
Have you checked to make sure that your adb/fastboot programs are at the latest revision?
Sent from my Pixel C using Tapatalk
pkelly517 said:
Do you get any response on the phone when in bootloader and USB cable is plugged in?
Have you checked to make sure that your adb/fastboot programs are at the latest revision?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I've updated the adb/fastboot versions from the sdk. I've updated the USB drivers. Or attempted to. And I get no response from the phone when in any mode.
Got any friends with a Linux machine? It's been ages since I used Windows to talk to my phone. I'll plug it in when I get home, though, to see if my phone is recognized.
Sent from my Pixel C using Tapatalk
pkelly517 said:
Got any friends with a Linux machine? It's been ages since I used Windows to talk to my phone. I'll plug it in when I get home, though, to see if my phone is recognized.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No I don't. But I suppose I could set up a Linux virtual machine and try it that way. It's been a while since I've used Linux. You think it could work?
droidian1441 said:
You think it could work?
Click to expand...
Click to collapse
Yes
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb)
droidian1441 said:
You think it could work?
Click to expand...
Click to collapse
I'm not sure. I think a virtual box would still use the windows drivers. Good luck.
Sent from my Pixel XL using Tapatalk
droidian1441 said:
No I don't. But I suppose I could set up a Linux virtual machine and try it that way. It's been a while since I've used Linux. You think it could work?
Click to expand...
Click to collapse
DR3W5K1 said:
Yes
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb)
Click to expand...
Click to collapse
I was referring to Linux not a virtual machine. Sorry if I confused you.
DR3W5K1 said:
I was referring to Linux not a virtual machine. Sorry if I confused you.
Click to expand...
Click to collapse
No problem. Going to give Ubuntu alongside windows a shot. See if it works. Thanks for the idea!
hello did you find any solution >??
droidian1441 said:
I need some help because I am puzzled on what to do. The other night, I tried to change roms on my Pixel XL. I'm used to being able to just flash everything once in whatever order and be fine (it was much simpler years ago when I got started with modding).
Anyways, I flashed FireHound rom and gapps, but forgot the vendor. I flashed twrp and that put me into a bootloop. It would reboot back into recovery each time. So I reflashed Pixel Dust, the rom I was on before, since I didn't have a backup. I forgot to make one. Lol.
Flashed the vendor, rom, and twrp. Rebooted to a clean rom. However, I'm not rooted. I attempt to go back to twrp - and I can't. It goes straight to Android recovery/ no command screen. I can't get back into twrp.
Since this, I downloaded the newest factory image so I could just reflash and start over and fix it. But I cannot connect to any computer. I've tried multiple cables, multiple computers, and each time I get a "USB device not recognized" error. Device manager shows my device as "Unknown USB device (device descriptor request failed)." I've attempted to reinstall/update the USB drivers, windows won't update it because it says it's already up to date. Windows 10 is what I'm using.
So I am stuck. Can anyone help me? Or did I completely screw everything up?
Thanks in advance,
Sam
Click to expand...
Click to collapse
@Siddhantroyal
Did you try this solution: https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625
Cheers...
5.1 said:
@Siddhantroyal
Did you try this solution: https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625
Cheers...
Click to expand...
Click to collapse
hello thanks for responding.the issue is a little bit different with my phone.it is showing up as a usb device and not as a mobile/unknown device