ADB device offline - myTouch 4G Q&A, Help & Troubleshooting

I decided to post this in Q&A primarily for the reason that I had to leave the MT4G forums to find the answer to my query.
I ran into the problem of encountering the error device offline, and couldn't quite figure out what the problem was so I of course did what everyone should do and used the search function.
After about an hour of reading and searching XDA MT4G forums I decided to go else where, found many similar posts for the Vibrant, Desire, Defy and Thunderbolt all of which someone had posted suggesting the change of the USB cable. So after work this evening, that is exactly that I did, and it works fine.
So in closing, try the kill-server, start-server command first and if that doesnt help, try swapping out the USB cable. Oh and be sure USB DEBUGGING *IS* enabled.

Related

how would you unlock this wizard (only experts)

im trying to unlock this wizard but there is one problem
it wont sync, it only charges (i´ve seen other wizards with the same issue) there's in fact another thread and i have already posted there.
it wont sync over bluetooth because the first sync has to be with cable.
im out of ideas, maybe someone can help me out.
thanks for any help.
i know in ebay some people sell the unlock codes, but as you can tell by my english im from mexico and things are not OK at the moment.
maybe there is an app that can calculate the codes or maybe other alternative
You must have active sync version 4.5. If you have older - update.
Or to check usb cable.
Actually I have a solution for your problem, but I'm no expert, so that leaves me out of the thread.
Bye.
I shall declare myself an expert, so that at least someone gets help (regardless whether I am, in fact, an expert or not). hmotwr's response is the kind of thing that gets users banned...just saying.
Syncing is not an unlock problem. It might be a problem that you already have two accounts in your phone, and you need to delete one of them. It could be that you're using a Vista computer (known problem). It could be that your version of WM5 is corrupted. It could be that your Wizard's microUSB connector is broken.
I suspect the solution that hmotwr is withholding is the legendary "Flash from an SD card" which has seen lots of thread activity, but very few successes. Here is a possible answer: http://forum.xda-developers.com/showthread.php?t=293387
Don't be afraid to use the site's search engine, it's not bad. Search engines are your friends. Get to know them, and love them.
hmotwr said:
Actually I have a solution for your problem, but I'm no expert, so that leaves me out of the thread.
Bye.
Click to expand...
Click to collapse
yes i can tell, thanks any way
Myrddin Wyllt said:
I shall declare myself an expert, so that at least someone gets help (regardless whether I am, in fact, an expert or not). hmotwr's response is the kind of thing that gets users banned...just saying.
Syncing is not an unlock problem. It might be a problem that you already have two accounts in your phone, and you need to delete one of them. It could be that you're using a Vista computer (known problem). It could be that your version of WM5 is corrupted. It could be that your Wizard's microUSB connector is broken.
I suspect the solution that hmotwr is withholding is the legendary "Flash from an SD card" which has seen lots of thread activity, but very few successes. Here is a possible answer: http://forum.xda-developers.com/showthread.php?t=293387
Don't be afraid to use the site's search engine, it's not bad. Search engines are your friends. Get to know them, and love them.
Click to expand...
Click to collapse
yes the problem is the mini-usb port, didnt know that flashing was possible via SD card, i've been out of this forum for awhile (not totally im in the shift and the fuze forum)
thanks for the link, will see if it can help me out and will let you know.
activesync is out of the question since i've been able to sync via bluetooth AFTER the first sync with cable (with other phones).
thanks once again.
to all the others.....
when i wrote "only exprets" i didnt mean it in a offensive way i just wanted to get ideas and not the classical "check the cable" "try a different computer" "different version of acticvesync" because all of that has already been done, but i apologize if it was taken in a wrong way.
i appreciate all the help.

[q] my fascinate will not connect to my pc

Okay so I am running windows 7 64bit and have the drivers for my phone and have read many threads and done everything I have read to the T its getting really frustrating and I am so annoyed I need help I never had this much problem with my Droid and I can't clockworkdmod recovery to work either I am rooted and have tried flashing it even done it twice in a row but nothing has worked to get it on there so I wanna try the Odin approach but I need to connect it to my comp first
Thank you for any help and I hope you guys can suggest a solution that will make this my favorite device
What is the error message you get?
may or may not help , but i was going crazy the other day because my windows 7 wouldnt read mine either. then i realized i was using the cable from my droid x . it fit , and it charged it , but for whatever reason would not relay data.
Make sure its the one for that phone . not for another or one from walmart. helped me at least .
jeffreymeyer99 said:
Okay so I am running windows 7 64bit and have the drivers for my phone and have read many threads and done everything I have read to the T its getting really frustrating and I am so annoyed I need help I never had this much problem with my Droid and I can't clockworkdmod recovery to work either I am rooted and have tried flashing it even done it twice in a row but nothing has worked to get it on there so I wanna try the Odin approach but I need to connect it to my comp first
Thank you for any help and I hope you guys can suggest a solution that will make this my favorite device
Click to expand...
Click to collapse
What exactly is going on when you plug in your phone?
You need to odin or redbend to install the hacked recovery for clockwork to work.
http://forum.xda-developers.com/showthread.php?t=788099
on the computer it says all the drivers are installed but when i connect the usb it says that no device is attached and its the cable that came with the box now something i just thought of is this is my third fascinate from verizon i was having issues with the hearing people and finally got one that worked and i connected and rooted both of those devices on this comp could it be that it wont read this one because it wants to read one of the previous devices if so how would i go about fixing that...thanks for all your help guy i really appreciate it i feel like a noob again coming from my flash happy days with my droid...and i wasn't trying to be sarcastic about the cord cause i thought of that too i just reread this and wanted to make sure i am showing gratitude and not seeming like an a**hole so thank u
i figured it out
i was using the same cable from my old fascinate with my new one and it wasnt detecting it on the comp so i got a usb from another on used it and worked like a champ i got clockwork woot woot thank u all
I am having a similar issue suddenly. My original cable began having intermittant connection problems while charging right after I spent 3 days charging my phone from my laptop due to a massive power outage. I recalibrated my battery stats but the physical connection from the cable is flaky during charging and now during data too. My laptop sees it as drive e but it wont let me access it, it tells me to insert a disk into drive e, however pdanet works fine. I did perform the hack to reprogram the 3g hotspot app to bypass the dun setting prior to this happening. Did qpst change something else or did mess something up? Any help is greatly appreciated.
Update: The intermittant connection from the cable seems to have corrupted the USB mass storage driver. Had to uninstall/reinstall it & everything worked. BTW the vzw store replaced my cable with a Motorola micro-usb and it works great; the plug end is about 1mm longer and it fits in the socket much better.
Sent from my SCH-I500 using XDA App

[Q] Nexus 7 wont connect to usb, charge when on, but usb-otg works

Im aware that one or two other threads have been created with this same general question but one thing they didnt ask is what to do if you cant fix it?
As the thread topic states my Nexus 7 will not connect to my PC via USB (It is not seen at all, its not a driver issue I've tried). It will not charge when turned on but it was charging when turned off last night. When I checked this morning it said I had a full battery but after turning the tablet on it said I only had 60% battery. All the started happening after I charged it with a battery pack at work the other day because I forgot my charger at home (some people have had similar problems after using car chargers). It will let me connect a flash drive to it via USB-OTG. I have tried 3 different cables on 2 different PCs (One running Windows 7 and the other running Windows 8). I really dont know where to go for help anymore as Ive spent the past 2-3 days googling like a mad man trying to find an answer and noone seems to have one.
I would love for someone to really help me out and get some steps that could fix this, however, if its not fixable how do I RMA it? I cant lock the bootloader and I cant flash a factory image.
You say it is not a driver issue, but your symptoms indicate it is. I would start over with the removal and re-installation of the proper drivers.
Groid said:
You say it is not a driver issue, but your symptoms indicate it is. I would start over with the removal and re-installation of the proper drivers.
Click to expand...
Click to collapse
I've uninstalled them. Every time I go to manually install them the guides always say to find where the nexus is and my nexus never shows up. If it was drivers it would still charge when its on. So how can drivers cause the tablet not to charge from the ac adapter?
Try Wugfresh's program. I had issues w/o it.
Sent from my SCH-I535 using Tapatalk 2
dennyjones said:
Try Wugfresh's program. I had issues w/o it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thats the toolkit I have installed. Its also the "guide" I am following when it comes to drivers. I tried to see if I could make the nexus connect to the pc while in fastboot and nothing happened then either. Everything he says to do involves the PC actually seeing the nexus :/
Ive changed it from mtp to ptp, toggled debugging, went to different back ups, flashed a new rom, etc etc. I really feel like Ive tried just about everything. Someone mentioned in one thread about some specific code in the nexus being wrong and possibly changing it could fix it but I do not know how I would go about doing that.
I also originally used the Wugfresh toolkit and had problems getting the drivers installed properly on Win7-64. Ultimately, I think I installed pda.net on my computer and on the N7 and was able to connect after that. Haven't had a problem connecting since. Re-read some of the Wugfresh posts about driver problems. You should be able to get it sorted out.
Groid said:
I also originally used the Wugfresh toolkit and had problems getting the drivers installed properly on Win7-64. Ultimately, I think I installed pda.net on my computer and on the N7 and was able to connect after that. Haven't had a problem connecting since. Re-read some of the Wugfresh posts about driver problems. You should be able to get it sorted out.
Click to expand...
Click to collapse
I sent you a PM but I really dont think this is an issue with drivers. I have been able to connect the N7 to my PC perfectly before the other day. Never a problem at all. Now I have uninstalled/reinstalled the drivers as best as I could (currently I have the samsung drivers because they are the only ones that will install without having to verify that the phone is connected via ADB and I had them left over from my Fiance's GNex so they have been here all along when the N7 was actually connecting).
The N7 is not connecting to the PC at all. It does not show up in device manager. You cannot make an ADB connection to it. It has already been rooted and it is running the latest version of Paranoid Android. On top of that the AC adapters will not charge the N7 while it is turned on. Its like the N7 turns away any usb connection other than a USB-OTG cable while it is on.
Also I really do appreciate the help. This has just been really frustrating for me.
Hello,
Since yesterday, I have exactly same issue with my Nexus 7 3g.
Everything is working perfectly but computer doesn't see Nexus at all (nothig works Bootloader, ADB, MTP,PTP).
Charging is fine (looks like), USB HDDs, pendrives are working as before.
Reinstaling drivers, changing to PTP, switchin on/off USB debugging didn't help.
Checked : other Nexus connects to the computer without problems, so its not drivers issue.
I assume it happened after Nexus was connected to my car charger.
Does anybody have solution/fix for that ?
Unfortunately my Nexus comes from USA, can I RMA it in Europe ?
I feel badly for everyone having these issues. I feel very lucky I'm not having them. It sounds as if the microusb port may have been altered/damaged by certain kinds of connections, like the battery pack or car charger. I don't know why this would happen and my own car charger (Moto oem for my Bionic) has worked fine on the N7. I did pick up the usb cable attached to my pc one day and created a static shock to the connector. Since then, that bank of 4 usb ports will not show either my N7 or bionic, but my usb mouse, keyboard, and printer work with them. The other bank still works, as does the pci port expansion card and my front ports. If I do have a glitch with the pc connection, I restart both the computer and the N7 and then it works. Sorry I don't have a solution.
I also assumed a damaged/fried USB post on the Nexus 7. There are 2 data lines and 2 power lines in the charging socket I think. If the power lines are damaged, usb otg may still be working. Its also tying in with the use of a power pack.
davidoff59 said:
I also assumed a damaged/fried USB post on the Nexus 7. There are 2 data lines and 2 power lines in the charging socket I think. If the power lines are damaged, usb otg may still be working. Its also tying in with the use of a power pack.
Click to expand...
Click to collapse
Have you tried switching between MTP and PTP and seeing if that works? If I used the PTP setting for the USB it shows up, I can then move files onto the PICTURE folder and once there move to another folder while using the Nexus.
-AkWingnut
Wow or strange should be more of the reply. I have done this before but it never worked. Thanks for the help. For anyone else needing help here is what I did. First opened the Nexus Tool Kit, then Full Driver Installation Guide, launched USBDeview, then - In particular look for devices with Vendor ID - "18d1" or... "04e8" - Simply right click these devices, and select the option to: - "Uninstall Selected Devices", final step unplugged the device and plugged it back in and it worked. Also MTP enabled USB Debug unchecked. Thanks again...
-AkWingnut
Tried this and haven't had any luck so far. I'm going to try pdanet or samsung drivers again later today and post results.
Sent from my Nexus 7 using xda app-developers app
Have exactly the same trouble. I'm with you guys. USB host works, no reaction in device manager. Did your nexus was unlocked? Rooted?
xxut said:
Have exactly the same trouble. I'm with you guys. USB host works, no reaction in device manager. Did your nexus was unlocked? Rooted?
Click to expand...
Click to collapse
Bump!
I'm experiencing similar issues with my Nexus 5. This is the only thead I can find that has a similar problem. My Nexus 5 worked on SlimKat, I flashed stock L Preview, now my device won't charge when it is powered into the OS. Bootloader works fine and charges when turned off. I upgraded to 5.0 which came out today (Yay!) and the problem persists.
Have any of you lads or ladies had any updates?
nintennuendo said:
Bump!
I'm experiencing similar issues with my Nexus 5. This is the only thead I can find that has a similar problem. My Nexus 5 worked on SlimKat, I flashed stock L Preview, now my device won't charge when it is powered into the OS. Bootloader works fine and charges when turned off. I upgraded to 5.0 which came out today (Yay!) and the problem persists.
Have any of you lads or ladies had any updates?
Click to expand...
Click to collapse
In my case it was a hardware trouble. Fixed by motherboard replacing in official service centre.

Difficulty Rooting Nexus 7

Hey, everyone. I browse XDA a lot but I've never really had a reason to post. I do now, however.
Basically what I'm trying to do is unlock and root my Nexus 7. I discovered Wug's Nexus Root Toolkit which seems to be the best way to go about the process. From all the hubbub about it, I figured it was going to be quick and painless. Lucky me, I was wrong lol. At least for me. All I needed was to get the ADB installed with the device so I could get started, then my adventure began.
You see, whenever I connect the device via USB with debugging mode on, my PC goes mad and the device automatically connects and disconnects itself in a rapid fashion. I cannot get it connected long enough to install the correct drivers for it, the usb driver found with the Android SDK, or whichever one's the Toolkit provides as well. If it's not in debugging mode, all is normal, and the Nexus 7 installs as a simple portable device (due to windows). However, I'm unable to update it's driver with the "android_winusb".
I am running Windows Vista Home Premium and looked up ways to disable the automatic driver installation, since Windows wants to install specific drivers, figuring that was the issue. The Local Group Policy Editor is not found in my versions of Vista, so I can't disable it that way. When I disable it in Hardware of Advanced System Settings, it simply just doesn't work.
My USB cables are fine, so it's not that. I've tried every drive method in the Toolkit, and have had mild success getting the ADB drive to install properly and have "Android device" appear in the Device Manager with the ADB listed. However for it to be listed, it must be in debugging and the problem remains, it wont stay connected long enough to do anything with it. Much less root, unlock, or backup...or anything for that matter. Then windows tries to install the unwanted drivers again...ugh.
The problem seems to be narrowed down to the debugging mode issue when connected. It's hopefully my only hurdle. Has anyone else had this issue, and if so, found a working solution? This has become very frustrating and not something I expected to endure at all. Having spent a few hours trying to solve this, I hope someone else out there can help me out from here. It'd be much appreciated!
MegaMac said:
Hey, everyone. I browse XDA a lot but I've never really had a reason to post. I do now, however.
Basically what I'm trying to do is unlock and root my Nexus 7. I discovered Wug's Nexus Root Toolkit which seems to be the best way to go about the process. From all the hubbub about it, I figured it was going to be quick and painless. Lucky me, I was wrong lol. At least for me. All I needed was to get the ADB installed with the device so I could get started, then my adventure began.
You see, whenever I connect the device via USB with debugging mode on, my PC goes mad and the device automatically connects and disconnects itself in a rapid fashion. I cannot get it connected long enough to install the correct drivers for it, the usb driver found with the Android SDK, or whichever one's the Toolkit provides as well. If it's not in debugging mode, all is normal, and the Nexus 7 installs as a simple portable device (due to windows). However, I'm unable to update it's driver with the "android_winusb".
I am running Windows Vista Home Premium and looked up ways to disable the automatic driver installation, since Windows wants to install specific drivers, figuring that was the issue. The Local Group Policy Editor is not found in my versions of Vista, so I can't disable it that way. When I disable it in Hardware of Advanced System Settings, it simply just doesn't work.
My USB cables are fine, so it's not that. I've tried every drive method in the Toolkit, and have had mild success getting the ADB drive to install properly and have "Android device" appear in the Device Manager with the ADB listed. However for it to be listed, it must be in debugging and the problem remains, it wont stay connected long enough to do anything with it. Much less root, unlock, or backup...or anything for that matter. Then windows tries to install the unwanted drivers again...ugh.
The problem seems to be narrowed down to the debugging mode issue when connected. It's hopefully my only hurdle. Has anyone else had this issue, and if so, found a working solution? This has become very frustrating and not something I expected to endure at all. Having spent a few hours trying to solve this, I hope someone else out there can help me out from here. It'd be much appreciated!
Click to expand...
Click to collapse
I had that problem too, and it was solved by plugging the usb cable at the back of your pc.
Leonhan said:
I had that problem too, and it was solved by plugging the usb cable at the back of your pc.
Click to expand...
Click to collapse
Now that you mention it, I have heard of certain USB ports not liking certain things. What a simple solution. You know, lol...it'll probably work. Thanks so much for commenting. I'll edit this post if all is well.
I would have edited my previous message, but I'm afraid I still need help and needed to bump this up.
I plugged the USB cable into the back of my PC and all seemed well. I was able to painlessly get the ADB all set up without any interruptions. Needless to say, I was excited and ready to unlock and root and...not so fast. After a short bit, the disconnecting and reconnecting bull****, for the lack of a better word, began again. Windows ceaselessly wants to install the damn drivers as the MTP or Camera, regardless if it failed or succeeded. Because of this, the device manager loses the Android Device drop down and the ADB Composite interface along with it. It just doesn't exist and therefore, I can't proceed with the Nexus Root Toolkit.
This is insanity. Is there anything I haven't tried that could remedy this? It shouldn't be this nerve wracking just to root a device, I swear...lol.
Any chance you have access to another PC' maybe a family member? That way you can rule out your PC as the problem.
Sent from my Nexus 7 using xda premium
zPacKRat said:
Any chance you have access to another PC' maybe a family member? That way you can rule out your PC as the problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Well, I did plug it into my girlfriends laptop once to see if it would act up, and with USB debugging turned on, it did not. That may be my last resort, but ideally, I'd prefer to use my own PC for any business such as this, and it irritates me when there's an issue that shouldn't even be that I can't solve. I'm sure some out there can understand that feeling.
So at this point, I'm just looking for a possible solution on my end. If there isn't one, then I guess I'll have to submit and abduct her laptop...lol
MegaMac said:
Well, I did plug it into my girlfriends laptop once to see if it would act up, and with USB debugging turned on, it did not. That may be my last resort, but ideally, I'd prefer to use my own PC for any business such as this, and it irritates me when there's an issue that shouldn't even be that I can't solve. I'm sure some out there can understand that feeling.
So at this point, I'm just looking for a possible solution on my end. If there isn't one, then I guess I'll have to submit and abduct her laptop...lol
Click to expand...
Click to collapse
There was a time when my aunt's galaxy tab 2 will act like this. What I did was turn off usb debugging first and let it install the drivers. Then I turned usb debugging on again and I didn't have the problem. It could also mean that the cable you got is faulty or somethin.
Leonhan said:
There was a time when my aunt's galaxy tab 2 will act like this. What I did was turn off usb debugging first and let it install the drivers. Then I turned usb debugging on again and I didn't have the problem. It could also mean that the cable you got is faulty or somethin.
Click to expand...
Click to collapse
Well, if I connect it with debugging off, it installs as a typical portable device and when I try to update the drivers with the winusb drivers needed, it doesn't install properly. So far, it must be connected to where it creates the section in the device manager "Unknown Devices" and appears in its drop down list. I'm still tryin' guys. Thanks for the help so far!
MegaMac said:
Well, if I connect it with debugging off, it installs as a typical portable device and when I try to update the drivers with the winusb drivers needed, it doesn't install properly. So far, it must be connected to where it creates the section in the device manager "Unknown Devices" and appears in its drop down list. I'm still tryin' guys. Thanks for the help so far!
Click to expand...
Click to collapse
Hmm, try this. Connect your device and use it as PTP not MTP. Then install your drivers.
Leonhan said:
Hmm, try this. Connect your device and use it as PTP not MTP. Then install your drivers.
Click to expand...
Click to collapse
Already attempted. It seemed to alleviate the connection issues for a little bit, but the drivers still wont install the right way.
bump.
was OP able to fix his issue?
jt.one said:
bump.
was OP able to fix his issue?
Click to expand...
Click to collapse
Not sure how you would have missed the OP replying to the last suggestion, what maybe 20 minutes before your post.
zPacKRat said:
Not sure how you would have missed the OP replying to the last suggestion, what maybe 20 minutes before your post.
Click to expand...
Click to collapse
OP might have handled it himself and forgotten to update his thread you know.
but yeah, thanks for replying to me and not contributing to the OP's thread :highfive:
Quite the coincidence we posted around the same time. But yeah, still giving me trouble. I will try to tackle it again tonight, but if I can't find a solution soon, I suppose I'll at least get the unlocking and rooting done on the laptop I spoke of, then for future stuff, try to get the ADB working on my PC.
You can do what i did and just download one of the toolkits to install the drivers.
Sent from my Nexus 4 using xda premium
jnewman1991 said:
You can do what i did and just download one of the toolkits to install the drivers.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Toolkits? You mean like Wug's? I am using his Nexus Toolkit, or trying to rather. The issue lies within getting the Nexus 7 to stay connected correctly as an "Unknown Device" in Device Manager, in which to properly install the drivers to get Windows to identify it as an "Android Device" and have the ADB recognized successfully.
win vista
vista it's junk win8 working well for me
vital982 said:
vista it's junk win8 working well for me
Click to expand...
Click to collapse
I actually enjoy Vista. It had a rough start, but still. I don't think it's Vista because my gf's laptop runs it too, and when I tried connecting and doing everything with it, none of the connecting and disconnecting crap happened. I'm thinking there's a setting or something I'm overlooking on my own PC that's causing it in particular to do it.

Random question

Hey the title kinda says it all. I've just been theorising a smidge in my head and wonder if I'm crazy. That or posting in wrong forum lol.
Anyways basically I started thinking about running kali or any other Linux on my s8 but if I remember correctly I had a ton of trouble setting up network adapter for pen testing use. What I'm wondering is if there is any way at all a usb WiFi such as a tp-link could be ran via a usb adaptor? Could be madness but id like it enough to throw my madness out for more knowledgeable opinions.
Thanks
Boogs ?
I can't give you an exact answer because what you're searching is very specific. But I will advise you 2 things :
1/ Rename your post because titled it "random question" is just useless
2/ If you don't find anything on Google, maybe you can just try and see You seem to have the knowledge to accomplish your wish so why not trying, it's not risky !
Good luck

Categories

Resources