So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.
ahs646 said:
So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can't reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.
Click to expand...
Click to collapse
Press and hold Volume + and Volume - with Power toghether.
Stay press until it don't self-reboot itself.
When the logo about bootloader will load up, you can choose what to do :
1 ) Reinstall the stock roms 4.4.4 (https://dl.google.com/dl/android/aosp/occam-ktu84p-factory-b6ac3ad6.tgz)
2) If you still have a modify recovery (CWM or TRWP) you can run it and install zip from sideload. Put the rom zipped you wanna install where did you have adb tools and run "adb sideload <file.zip>" and wait it should be install.
If that dosen't work, you need to use download mode from LG ( for the moment i can't found a guide to do it, check on XDA / Google).
Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.
ahs646 said:
Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.
Click to expand...
Click to collapse
Did you try download mode ?
{
"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"
}
I don't think I've seen this "download mode." Where is this - on the phone (in recovery?) or through adb or sideload. The problem seems to be (and I see there are a few others right now with the same problem) that windows sees that the phone is connected, but then there seems to be a driver error such that the device doesn't show up in explorer, and abd and fastboot can't see the phone either.
I've tried different drivers, but haven't systematically gone through every single option so far, which is my next stop. Is any one driver option more failsafe than the others? Also, perhaps related - in the past, any time I've installed the drivers and connected to my phone from my pc, it never seems to "stick." Invariably, I can't access the phone through MTP after a short while (maybe after a reboot?). Recently I found updating the driver to just a Portable Device/Standard MTP USB device driver (i.e. not Google, Samsung, Android, etc) made it work. So now I feel the driver troubleshooting part is even longer and more complicated - go through all of the uninstall/reboot/install with the four Android options, then all of the generic Windows options. So I was just hoping that someone out there might have already cracked this and could point me in the right direction.
Also, in digging through some posts on reddit on related problems, someone said that Windows Media Player is somehow critical for MTP functionality. Is this the case? I had never heard this before. I don't have WMP installed, and in trying to install it, have come up with a Windows error. I'm not clear on the relationship between MTP and ADB/fastboot. Is MTP necessary for the file transfer, or is that not relevant here?
And one final question - to use adb/fastboot, do I need to be in bootloader or in recovery? To install the drivers, do I need to be in either bootloader or recovery?
Thanks so much.
Related
Recently, I have not been able to get my Nexus 4 to show up in my computer. I am able to use ADB and the drivers work fine, but when I connect my Nexus 4 it will not install the drivers for MTP. Rather, it will say it has the correct drivers installed, but it cannot start (Code: 10) and the icon for the device has a yellow exlamation mark next to it. I tried switching it between MTP and PTP as well as enabling and disabling USB Debugging, but it wont show up. Next, I decided to try to switch ROMS, as well as uninstall and re install all the drivers for the phone. No matter what I do I am able to connect to the phone through ADB, but MTP will give me the same error over again. Even on PTP my PC wont install the drivers for the phone.
I have looked through numerous threads and tried all kinds of solutions people have suggested, but none of them have worked for me. I've even tried switching between USB ports, cords, and computers (32 bit, 64 bit) and have tried plugging it into a new computer which i have never plugged the phone into, and nothing at all will work.
I am really at a loss here as I have spent many hours going through the solutions posted on these forums and others. I use USB for backing up my device as well as adding files etc. , and I dont want to do anything with my phone without being able to connect to it by USB at the very least. Airdroid will work as a temp. solution but it is way too slow when i transfer bigger files. My Nexus has worked fine with MTP since I bought 3 months ago, and even after rooting and updating the MTP has still worked regardless. I am running Windows 7 ultimate 64 bit, and my phone is on 4.3.
To anyone who will tell me to look on other threads I realize there are a ton of them out there, but I have tried using so many of the methods described, and none of them have worked.
Is there anyone that can help me with this problem? My phone is having issues and I need to backup up my stuff so I can flash to stock, factory wipe, etc.
Sent from my Nexus 4 using xda app-developers app
What rom and kernel are you running? Have you tried on stock firmware and stock kernel, with USB Debugging turned off? It sounds like an issue with the software in your phone.
Also when you connected your device, look in Device Manager and tell me the exact name listed for your Nexus 4, it should be saying "Nexus 4" or "Google Nexus 4 ADB Interface".
You can back up your files through adb: adb pull /sdcard/ C:\backup\
Instead of AirDroid you can try WorkGroup/Samba sharing. Enable a Workgroup shared folder on your PC then use ES File Explorer to access it and transfer file that way.
Here is my system info:
{
"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"
}
I have tried enabling and disabling debugging but it doesn't make much of a difference. It'll show up as MTP USB Device under portable devices with a yellow exclamation mark next to it, as well as Google ADB Interface Device under Android Device. Sometimes it will show up in Other Devices as Nexus 4, but then it install the drivers for ADB and it goes away.
I have also tried getting it to connect with AOKP milestone 2 (4.2.2) and the latest version of Carbon ROM which was also 4.2.2. I had Franco.kernel installed on both of these. The only thing I haven't done is a factory reset of all my data or flash back to stock rom.
Thanks for the backup tips I'll try those to see if I can get everything off it.
Sent from my Nexus 4 using xda app-developers app
Try uninstalling the driver, select the checkbox option to delete the files as well. Then reconnect it while in ADB mode and use the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=2263822
Also this will sound strange, but on your Pc, go into "Disk Manager" and make sure there are no blank partition or disk that might vaguely resemble your device. If there is one and without a driver letter, assign to it any drive letter.
Make sure there aren't conflicting ADB or USB drivers from other Android device, if there are, remove them.
Try live booting into Ubuntu 13.10, if it still can't copy your files, the phone is the problem.
Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.
Well let me know when it stopped working.
sent from xda premium app
Oh, one more thing. Is there a way for me to know what I can put onto the folder that shows up in the windows file explorer. Sometimes, I will put a folder in /sdcard, and it won't show up on the computer. It is really confusing sometimes when I need to move certain files to my computer.
Microsoft's MTP is a ****ty protocol, that's just my opinion.
The new files won't show up if it's not been read by the Media Server (I think), you have to do a media scan and replug the phone. If you still don't see it, just reboot the phone and let it scan the files for a few seconds before plugin it in. You should be able to move any files to the phone, just ignore the warning if it say the file might be incompatible.
sent from xda premium app
I often have to disable/uninstall the ADB device in Windows device manager to get MTP working...but that was on a Windows XP machine.
afff53 said:
Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.
Click to expand...
Click to collapse
Something similar happened to me once. I reinstalled the drivers several times unsuccessfully and then it just started working. It seemed like a Windows 8 issue to me but I never determined for sure what caused it. Good luck.
I solved my problem at this way. Maybe it will help.
So my xiaomi m2s was bricked pretty bad, I couldn't even enter the recovery. So I followed this thread and restored my phone by installing the 'aries_images_4.11.21_4.1_cn' fastboot package. So when my phone finally booted up I noticed some problems I also had prior to this brick. My sdcard storage couldn't be mounted, not in the ROM and neither with an usb cable. I tried, for example downloading something but always got an error. When I go to fastboot and try to flash m11kkaa's flashtools with miflash, I always get this error:
{
"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"
}
This happens with all fastboot packages by the way, not only m11kkaa's. And I've tried this on 3 different computers with each having the windows driver signature enforcement disabled on boot.
So my question is: Is my phone DEAD?
infinitely said:
So my xiaomi m2s was bricked pretty bad, I couldn't even enter the recovery. So I followed this thread and restored my phone by installing the 'aries_images_4.11.21_4.1_cn' fastboot package. So when my phone finally booted up I noticed some problems I also had prior to this brick. My sdcard storage couldn't be mounted, not in the ROM and neither with an usb cable. I tried, for example downloading something but always got an error. When I go to fastboot and try to flash m11kkaa's flashtools with miflash, I always get this error:
This happens with all fastboot packages by the way, not only m11kkaa's. And I've tried this on 3 different computers with each having the windows driver signature enforcement disabled on boot.
So my question is: Is my phone DEAD?
Click to expand...
Click to collapse
Connect with usb cable and boot to recovery.In cmd "adb reboot dload" .Now you can flash a miui fastboot package with miflash.
T3sla said:
Connect with usb cable and boot to recovery.In cmd "adb reboot dload" .Now you can flash a miui fastboot package with miflash.
Click to expand...
Click to collapse
I don't get an adb connection with my computer. This was also a thing I had prior to this brick... It seems like my phone cannot communicate with my computer (except for the pin shortcut method and regular fastboot).
infinitely said:
I don't get an adb connection with my computer. This was also a thing I had prior to this brick... It seems like my phone cannot communicate with my computer (except for the pin shortcut method and regular fastboot).
Click to expand...
Click to collapse
Try these.
T3sla said:
Try these.
Click to expand...
Click to collapse
I gave this a try, even though I already had the latest platform-tools installed through android studio > SDK manager. Anyway this little installer puts it in C:/adb. It didn't work either. This is what I always get:
This is what my driver looks like in windows when I connect in fastboot:
EDIT:
I seem to have gained a working sdcard again by flashing m11kkaa's 'aries_core_recovery_single' package through fastboot (pin short circuit method) but I still have no connection with my computer through USB. The only way I can transfer files to my phone are through FTP.
infinitely said:
I gave this a try, even though I already had the latest platform-tools installed through android studio > SDK manager. Anyway this little installer puts it in C:/adb. It didn't work either. This is what I always get:
This is what my driver looks like in windows when I connect in fastboot:
EDIT:
I seem to have gained a working sdcard again by flashing m11kkaa's 'aries_core_recovery_single' package through fastboot (pin short circuit method) but I still have no connection with my computer through USB. The only way I can transfer files to my phone are through FTP.
Click to expand...
Click to collapse
I had a similar problem, i tried installing and uninstalling drivers with no luck.I concluded that something with the driver or windows files was wrong and could not fix it so finally i made a fresh install of windows and everything is fine now.?I know it's not the easiest thing to do so you can try first on a different pc to check if the problem is with the phone or your pc.
T3sla said:
I had a similar problem, i tried installing and uninstalling drivers with no luck.I concluded that something with the driver or windows files was wrong and could not fix it so finally i made a fresh install of windows and everything is fine now.?I know it's not the easiest thing to do so you can try first on a different pc to check if the problem is with the phone or your pc.
Click to expand...
Click to collapse
I've tried the same on a clean installed windows 7 in VMware, got the same result:
The driver looks different though:
I have also checked with google's adb driver installer but it doesn't find any attached devices.
infinitely said:
I've tried the same on a clean installed windows 7 in VMware, got the same result:
The driver looks different though:
I have also checked with google's adb driver installer but it doesn't find any attached devices.
Click to expand...
Click to collapse
If it's not working on the host machine then it doesn't on the virtual installation on vmware.I tried that too.You can make a backup of your current windows installation and then try a clean install and see if it's working.Or you can try on another machine.
T3sla said:
If it's not working on the host machine then it doesn't on the virtual installation on vmware.I tried that too.You can make a backup of your current windows installation and then try a clean install and see if it's working.Or you can try on another machine.
Click to expand...
Click to collapse
Wouldn't it be a hardware issue then? Lol...
infinitely said:
Wouldn't it be a hardware issue then? Lol...
Click to expand...
Click to collapse
How can be a hardware issue if after a clean windows and adb drivers install it's working fine?Lol...
T3sla said:
How can be a hardware issue if after a clean windows and adb drivers install it's working fine?Lol...
Click to expand...
Click to collapse
I was talking about the computer. Anyway, I doubt that will fix my problem since I have already tried it on 3 different computers and it was always the same outcome...
Hi guys - please assist!
My wife's phone started to behave really strange:
- mic level during calls was super-low, but while recording vids: just fine
- started to be extra slow on simple tasks like opening sms messenger etc.
- sometimes I couldn't connect it to PC in order to transfer files
SO... I decided it's time to load new FW. It was also quite surprise because there was 5.0.1 release for her GT-I9506.
Declaimer: I have loaded FW via Odin multiple times for S3, S4, S5 and some other Samsungs so I consider myself quite semi-pro user.
I've downloaded proper software from site, new version of Odin and started the process. After just few seconds some error was displayed on Odin and it crashed. Phone stuck on Downloading phase with progress bar already displayed.
After a while I rebooted it and got this screen:
{
"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"
}
So, I dig a net a bit and I've tried following:
1. I tried to recover my old software with KIESv3 but phone wasn't detected (used XDA tutorial)
2. Tried to reflash again with Odin, but I got "There is no PIT partition" error - I downloaded some pit file for S4(9506) from some Indian site, but I wasn't able to check it
After above I read a net a bit more and wanted to check that pit file I've downloaded and... since then I am not able to connect phone to PC. I contantly get "Unknown device" notification on my Windows. What I have tried:
1. Rebooting multiple times Windows and phone
2. To start a phone in Download and normal (well, not normal now because of the error state but still...) mode multiple times
3. Reinstall USB drivers multiple times
4. Change USB slots - right now I am NOT able to use different cable nor different pc
5. Manually update USB drivers via Device Manager (I extracted drivers from exe file, but I got "up to date drivers" message)
After all it seems I am done. No new ideas whatsoever.
Phone is dead now.
I cannot connect it PC.
Crap.
Any ideas folks? Anyone?
unster said:
Hi guys - please assist!
My wife's phone started to behave really strange:
- mic level during calls was super-low, but while recording vids: just fine
- started to be extra slow on simple tasks like opening sms messenger etc.
- sometimes I couldn't connect it to PC in order to transfer files
SO... I decided it's time to load new FW. It was also quite surprise because there was 5.0.1 release for her GT-I9506.
Declaimer: I have loaded FW via Odin multiple times for S3, S4, S5 and some other Samsungs so I consider myself quite semi-pro user.
I've downloaded proper software from site, new version of Odin and started the process. After just few seconds some error was displayed on Odin and it crashed. Phone stuck on Downloading phase with progress bar already displayed.
After a while I rebooted it and got this screen:
So, I dig a net a bit and I've tried following:
1. I tried to recover my old software with KIESv3 but phone wasn't detected (used XDA tutorial)
2. Tried to reflash again with Odin, but I got "There is no PIT partition" error - I downloaded some pit file for S4(9506) from some Indian site, but I wasn't able to check it
After above I read a net a bit more and wanted to check that pit file I've downloaded and... since then I am not able to connect phone to PC. I contantly get "Unknown device" notification on my Windows. What I have tried:
1. Rebooting multiple times Windows and phone
2. To start a phone in Download and normal (well, not normal now because of the error state but still...) mode multiple times
3. Reinstall USB drivers multiple times
4. Change USB slots - right now I am NOT able to use different cable nor different pc
5. Manually update USB drivers via Device Manager (I extracted drivers from exe file, but I got "up to date drivers" message)
After all it seems I am done. No new ideas whatsoever.
Phone is dead now.
I cannot connect it PC.
Crap.
Any ideas folks? Anyone?
Click to expand...
Click to collapse
You can calm down. Nothing wrong with the phone. This is just something that can happen.
In 99% of the cases this is solved by the following:
- use a different usb port when flashing with Odin
- Use a different usb cable when flashing with Odin.
Oh and for the low volume: Make sure the mic holes are clean. There could be dust in it.
unster said:
1. I tried to recover my old software with KIESv3 but phone wasn't detected (used XDA tutorial)
Click to expand...
Click to collapse
Kies V3 does not support S4. You can try recovery mode with the proper - former - version :
http://www.samsung.com/latin_en/support/usefulsoftware/KIES/
Lennyz1988 said:
- use a different usb port when flashing with Odin
- Use a different usb cable when flashing with Odin.
Click to expand...
Click to collapse
OK it's alive AGAIN! So... It seems that she isn't really taking proper care of her phone as she claims to, because its' charging port seems to be loose a bit. I changed cable, set myself in strange yoga position also changed port and after about 20x added/removed notifications it stopped and allowed me to upload a system.
Thanks!
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
loganwaffle8 said:
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
Click to expand...
Click to collapse
see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Ill try the rootjunky method in a few hours, I tried the terminal emulator installed and it just forceclosed all apps and rebooted.
Sent from my KFTBWI using XDA Labs
So I got a bit impatient, and decided to retry the w0lfdroid method. The same thing happened from last time (apps wouldnt open) and so I decided to reboot.
As the device began to shutdown, SuperSU appeared for a few seconds, then my device switched off. I believe I have bricked my device as it has been stuck on the 'fire' logo for the past 10 minutes. Congrats to me ._.
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
loganwaffle8 said:
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
Click to expand...
Click to collapse
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing or XDA
extract files
run KindleDrivers.exe
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"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"
}
Sent from my KFFOWI using XDA Labs
Thanks
Have I done it right? I hope I've done everything. Also when I open ADB a load of text flashes down the cmd box for about a second then it closes. Ran as administrator and everything. Hoping I can get this fixed by the weekend...
Ok, I think I got it.
Doing adb devices gives me G000HH0454340LB9, I beleive this is the correct device?
Anyways, plan is:
Boot into recovery on device and select apply update from adb
Get the 5.1.1 update (firmware it originally had) and place it in the folder adb installed in.
Do adb sideload (file name)
Wait (maybe grab a cup of coffee?)
Hopefully success, back to stock firmware!
Afterwards ill root with kingroot and then remove using rootjunky supertool.
Ok, this is getting kinda annoying.
Placed the update-kindle-32.5.4.1_user_541112720 .bin file in the same folder I have adb installed.
Booted devices into recovery mode, selected apply update from adb
Open adb, do adb sideload update-kindle-32.5.4.1_user_541112720
Get error message 'cannot read update-kindle-32.5.4.1_user_541112720'
Have ALL correct drivers and stuff installed @sd_shadow
Can anyone help? I really need this fixing...
loganwaffle8 said:
Can anyone help? I really need this fixing...
Click to expand...
Click to collapse
try downloading the firmware again, or try a different version like 5.1.2
which version is on it now?
Sent from my KFFOWI using XDA Labs
The version on my device before it was bricked is 5.1.1. I'm staying on that version since its the easiest to root.
If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"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"
}
Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.
I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.
Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.