EDIT: I finally got fastboot to see it. I uninstalled moto usb drivers, and installed a different version. I am back on 3.0.1 now. My camera still doesn't work though. The app starts, but the back camera just shows a black screen. The front one works.
Any ideas?
I am having serious issues with fastboot. I was running Tiamat Rom 2.2.1 Moray. My camera didn't work with it though. I flashed the stock 3.2.2 ROM. The camera still doesn't work, and wifi won't connect now.
I figured I would start over, and flash the original images for 3.0
I have the sdk installed, and the motorola drivers. ADB sees my xoom, but fastboot doesn't. It just says waiting for device when I try to send it commands. My xoom is in fastboot mode when I send them.
I have tried to use the PDANet drivers as suggested by others while searching google for answers, and that didn't do anything.
When the xoom is in fastboot and connected to my PC, the device manager doesn't list anything for it. What other drivers do I need?
Any help would be appreciated.
Did the back camera work when the Xoom was in out-of-the-box-state? That means before you laid your hands on it and flashed a custom ROM?
I'm inclined to think it's a hardware defect since the front camera works and thus the app seems to work...
That is what I am leaning towards now also. It did work when I first got it. I am not 100% sure when it stopped, as I only used it a few times right after I purchased it.
Related
Hello, I recently decided to root my phone and place Cyanogenmod on it. When I did that I realized my radio was no longer working. In an attempt to just get back to a working phone for the time being I flashed a rom that I believe was just for the Nexus S and not Nexus S 4G. Due to my stupidity I am unable to communicate from the device to my computer using USB. When I attach the device to the computer nothing happens. The device does not even appear in the device manager. I have tried on multiple computers as well. On top of that the rom seems to have put me back into the stock recovery. If anyone could help me figure out just how to get USB working again I would be very appreciative.
I should note that I can still transfer files to the phone using the sd card or via ftp.
Thank you for your time and help.
Change the USB cable?
Yes, forgot to mention that. I have tried 2 cables both of which work on other devices.
What if you hold in the middle of the volume buttons (i.e. both up and down at the same time) and keep holding, then plug in to your usb port? It should come up as download mode. If it will do that you might try using Odin.
Or try a different machine perhaps?
are the drivers the same for the S as the 4g?
do you have clockwork on the phone or have you tried to run recover by holding volume up and power?
just throwing things out.
Hello, I appreciate any and all suggestions and help.
I have Odin downloaded and installed, but the computer can not find the device so Odin can not do what it needs to do. This is even the case in download mode.
In terms of recovery I am on the stock recovery. I was on clockwork but made a small mistake and now am back to stock.
I know if I can just get the computer to see the phone exists I can fix it.
If you can find the full OTA package for NS4G, you can try putting it on the SD card and flash it via stock recovery.
Also another thing worth trying is connecting the phone to an Ubuntu machine and see if it's detected or not.
I have tried looking for the original full OS. I will continue looking, but the different OS thing is a good idea I did not think of. I will attempt that now. Thank you.
I installed Ubuntu and the Android SDK and Ubuntu was unable to see the phone as well. I am going to keep searching for the original firmware to see if that will fix it. Thank you for your help so far, it is greatly appreciated.
I have found the only rom my phone will accept now is
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Which is for the M200 variant. This apparently the Korean version.
Hello and thanks for clicking in!
I am broadcasting an SOS to anyone who may be able to help.
I am also aware that because of the recent stock OTA which I have already installed (build 35b), this may be game over, but if anyone has any ideas, I am ready to try anything.
A brief history: I was jumping between SkyDragon and Jasmine and at one point, my phone was acting funny so I wanted to go back to stock.
I flashed stock using kdz to 24b and everything was going fine for a bit until I updated to 35b OTA (big mistake).
Now my phone is completely unusable - for awhile I could get it to work for an hour or so by factory resetting, but any time I installed any apps, system processes would constantly fail, display would become unresponsive, and at one point, all audio just stopped working (headphones, speaker and ringtones, notification sounds, alarm, even bluetooth). I tried to flash stock again and now my computer won't recognize Android MTP device. I have tried all the LG drivers I could find, Koush's adb drivers, Verizon LG drivers, and no matter how I try to get my computer to recognize my phone I always get this error:
'Device driver software was not successfully installed:
MTP USB DEVICE FAILED'
I have tried TOT and KDZ methods to downgrade to stock and nothing will work because my computer won't recognize my phone.
Does anybody have any advice?
Thanks in advance.
a9u1tar1st said:
Hello and thanks for clicking in!
I am broadcasting an SOS to anyone who may be able to help.
I am also aware that because of the recent stock OTA which I have already installed (build 35b), this may be game over, but if anyone has any ideas, I am ready to try anything.
A brief history: I was jumping between SkyDragon and Jasmine and at one point, my phone was acting funny so I wanted to go back to stock.
I flashed stock using kdz to 24b and everything was going fine for a bit until I updated to 35b OTA (big mistake).
Now my phone is completely unusable - for awhile I could get it to work for an hour or so by factory resetting, but any time I installed any apps, system processes would constantly fail, display would become unresponsive, and at one point, all audio just stopped working (headphones, speaker and ringtones, notification sounds, alarm, even bluetooth). I tried to flash stock again and now my computer won't recognize Android MTP device. I have tried all the LG drivers I could find, Koush's adb drivers, Verizon LG drivers, and no matter how I try to get my computer to recognize my phone I always get this error:
'Device driver software was not successfully installed:
MTP USB DEVICE FAILED'
I have tried TOT and KDZ methods to downgrade to stock and nothing will work because my computer won't recognize my phone.
Does anybody have any advice?
Thanks in advance.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
Try seeing this guide it will help you restore your stock ROM as it should correctly.
Good luck!
nilac said:
Hi and thank you for using XDA Assist
Try seeing this guide it will help you restore your stock ROM as it should correctly.
Good luck!
Click to expand...
Click to collapse
I have been through and tried both methods thoroughly, including going through it with a friend. It seems that the root of my problem seems to be that I can't get my phone to connect MTP to any computer. It just won't get recognized by any computers. I tried on my desktop and laptop and my friend tried on his and his roommates machines. We put our heads together and still couldn't figure out how to get it work.
He suggested that it is a kernel/baseband error as I had installed a custom ROM with its own kernel and when flashing back to stock, it was conflicting with the custom kernel that was on the phone and this is what is causing my phone to malfunction so miserably.
a9u1tar1st said:
I have been through and tried both methods thoroughly, including going through it with a friend. It seems that the root of my problem seems to be that I can't get my phone to connect MTP to any computer. It just won't get recognized by any computers. I tried on my desktop and laptop and my friend tried on his and his roommates machines. We put our heads together and still couldn't figure out how to get it work.
He suggested that it is a kernel/baseband error as I had installed a custom ROM with its own kernel and when flashing back to stock, it was conflicting with the custom kernel that was on the phone and this is what is causing my phone to malfunction so miserably.
Click to expand...
Click to collapse
Hi again, well try then to ask over the Q&A thread. Right here:
Good luck!
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.
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.