A client of mine rooted his Galaxy Tab 10.1 and immediately lost USB connectivity; he could no longer get the computer to recognize his tablet in order to sync music, pictures, etc. I have verified the issue on multiple computers running both Windows 7 and Windows 10. I have also verified that the drivers on these machines are current, still to no avail.
In an effort to resolve the issue, I attempted to restore the stock firmware onto the tablet by putting it into download mode and using Odin to install the firmware. When it finished reinstalling, the tablet still shows a padlock symbol upon startup and still has no USB connectivity, which I can only assume means that the tablet is still somehow rooted. Can anyone confirm the meaning of the padlock symbol? Any suggestions pertaining to the next best troubleshooting steps? Have I perhaps gotten the wrong firmware? If so, where would I find the correct release?
I thank you all in advance for your insights and expertise.
Related
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hello community,
I have been trying for 8 hours (5 last night and three so far today) to get this to work but have failed utterly each and every time. I own the Samsung Galaxy Tab 10.1 (the Verizon 4G LTE model), and I'd like to revert back to the stock Honeycomb 3.1 that came with my tablet when I first purchased it from my local Verizon Wireless store.
I've followed this guide as closely as my understanding of it allowed me to (http://forum.xda-developers.com/showthread.php?t=1171089), and I also followed the video linked to in that topic (http://www.youtube.com/watch?v=krQDP7xYlWg) but I was not able to get Odin to work properly. After trying this on three different computers, I was able to get the third computer to recognize my tablet plugged in via USB and the yellow "COM4" box appeared in Odin, but when I clicked "Start" in Odin, it went all the way up to "Setup Connection" and then sat there for at least 10 minutes, showing no signs of a connection having been established. I've installed the Samsung USB drivers from both the topic linked to previously and from the video linked to previously (uninstalling one before trying to install the other, of course), and my tablet is recognized by the computer, yet Odin still stalls at "Setup Connection". I have not been able to push past this first step to rooting my device in order to revert back to stock Honeycomb 3.1, and this is very frustrating. I did have Download Mode open and the terminal that appeared on my tablet did say "Connected to USB, click [Start] in Odin" (or something to that effect). For what it's worth, all three computers I've tried this on were running Windows 7 64-bit (Ultimate and Professional editions).
Please, if anyone could help me, I'd greatly appreciate it. Also, once this is all sorted out, I am not exactly sure how to proceed after getting Odin to push past "Setup Connection". I don't even know if I'm following the correct path to reverting my device back to stock Honeycomb 3.1... as I mentioned before, I am a complete and utter Android noob (just got this tablet for Christmas) and I need all of the assistance that I can receive.
Thanks again, community. Hopefully we can get this sorted out and I can get back to using my tablet soon.
Excellent news: I was able to accomplish my goal without any problems using this concise, yet effective, tutorial: http://forum.xda-developers.com/showthread.php?t=1342995
I successfully reverted my Samsung Galaxy Tab 10.1 (SCH-I905, Verizon 4G LTE model) back to stock Honeycomb 3.1, removing the TouchWiz UX update completely. It's as though I've just picked it up out of the box for the first time, and I am thrilled.
I realized that Windows 7 was creating some issues that was leading Odin to stall at "Setup Connection", so I tried it again in the Windows XP Mode VM on my machine and, after a couple of hours of tinkering and reinstalling Kies, it finally worked. Thanks to XDA for such great tutorials and developers! Hopefully this topic will help others in my shoes in the future.
This is what happened. I want to upgrade my Samsung Galaxy tab 10.1n from 3.2 into 4.0 . I try to root and somehow I do some stupid error.
The bootloader screen become rolling. I found the solution from this thread http://forum.xda-developers.com/showthread.php?t=1555984 and it runs perfectly. my bootloader become normal.
But another problem come out after that. my PC can't detect my samsung through USB. any guide for this problem??
Change usb port or cable
Dont use usb hub
Reinstall kies 2
And retry
Sent from my GT-I9300 using xda app-developers app
noob here.
Galaxy Tab 10.1 P7510 Wifi
I have a similar problem to the above.
When I connect using the usb lead to the pc, nothing happens. I have reinstalled the drivers (both with and without Kies 2) and upon connecting the usb it acknowledges a connection and goes through some steps and proclaims the device is installed and ready to use. Except it's not. It doesn't show up in My Computer or when I remove and re-connect the usb, there is nothing - the same as before I resinstalled the drivers. Kies cannot find it either.
My issue is further matched by the above issue as I also followed the same guide as above. I previously tried to root the device several times and each time the recovery screen was doing the rolling / flicker thing. So I returned to stock. But inevitably I would get infuriated by all the things I couldn't do.
So when I found the guide http://forum.xda-developers.com/showthread.php?t=1555984 that further linked to http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41 I was thrilled because I could finally read the Recovery screen.
So I proceeded to root the device as per http://forum.xda-developers.com/showthread.php?t=1474971. This was working fine with one exception. Which was that after the screen went into sleep mode and I pressed the power button to wake it up, the tablet was in a variant of the rolling / flicker screen. This happened every time. I repeated the rooting process making sure to wipe data / cache / dalvik.But it remained.
So I became adventurous and decided to flash an experimental CM9 sourced from droidbasement.
And that is where I am now. Unable to enter sleep mode and unable to connect to the pc to return to stock or try different roms.
Any suggestions or help welcome.
perhaps I should have opened a new thread but wasn't sure. please advise if so.
I used a different usb port and the pc could find it.
Now back on stock.
re:
Go to settings>labs>. Uncheck USB error (don't know the exact english terms)
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
Hello,
I have a rooted Ematic EGS-102. Following some instructions to swap my internal sd with the external one (as the memory where the apps' data get downloaded to was only 500MBs), I believe I have typed something incorrectly inside the vold.fstab file, because after rebooting my tablet it's forever stuck on the logo screen. This is my first android tablet so please bear with me. The solution that comes to mind is to open the root files by some program on my PC and edit the vold.fstab file back (I even have a backed up version of it from a few weeks earlier), or even flash a new ROM. Now, the problem is, my computer cannot see my tablet when I connect it through USB. At all. Back before when the tablet was fine, I could use the USB to transfer files to and from my computer, but after I killed my tablet, my computer doesn't even make the sound which indicates that a USB device has been connected.
I have tried changing the USB cable and the port where I connect it to (never mind that the same cable and port work with other devices), to no avail. Having given up on the USB method working, I decided to follow some instructions on installing a custom ROM that has worked on EGS-004, and according to the one who posted that, would work on other variants such as EGS-102. Basically It was steps to installing the ROM from the external card through Recovery mode, which I followed thoroughly to no avail. The tablet still gets stuck on the "ematic" logo start screen.
I've noticed that in the Device Manager my tablet is displayed as "USB Device(VID_1f3a_PID_efe8)" with a yellow triangle mark indicating that it's not working properly (code 10). I tried searching that error code and trying all the solutions I found to no avail, including updating the driver (just refuses to update and keeps telling me that my driver is up to date.)
Sadly all the other methods that would have a decent shot at working (Root explorer on PC, android recovery program, even a flash EGS-004 firmware method on ematic's website) requires USB. I'm out of solutions, and unless I can get the USB to work somehow, or find out why the ROM method didn't work, my tablet would officially be dead. I'm utterly miserable that such a stupid mistake on my part ruined my tablet, and I have no way of buying another (broke student here) or returning it (out of warranty and I'm pretty sure I voided it anyway). I would absolutely appreciate any help, and thanks in advance.
Edit: It's stuck on logo screen, not a bootloop. I'm terribly sorry for this confusion, my head isn't straight right now.
Still haven't found a solution :/