Maybe this is something I've just missed (and yes I've searched), but I thought when I installed Sideload Wonder Machine (SWM) after getting my Captivate way back when I just turned on USB debugging.
With my Note, I rooted it following http://forum.xda-developers.com/showthread.php?t=1518962 which was fine. I wanted to see if I could find a way to setup a mobile hot spot so I downloaded an APK.
I installed SWM. I forgot to turn on USB debugging, and when I ran SWM to load the APK it didn't give me an error. However, the app didn't load. I realized that I hadn't turned on USB debugging.
So, I switched on USB debugging, plugged the Note back into the PC, and MTP started up. But then I run SWM and get a device not found error.
I'm running stock.
Questions:
Is MTP supposed to initialize when I plug the Note into the USB? I'm assuming yes.
If USB debugging is on, why does MTP start?
Can SWM work when MTP is running, and if so, why is mine saying device not found?
Thanks
You don't need SWM with the Note. Just enable unknown sources in the phone settings.
Wow dude... Unknown sources was added in to kb2 which is the last official FROYO build.
SWM has been obsolete for about a year on that device. Unless you kept it on stock eclair and never updated it.
studacris said:
Wow dude... Unknown sources was added in to kb2 which is the last official FROYO build.
SWM has been obsolete for about a year on that device. Unless you kept it on stock eclair and never updated it.
Click to expand...
Click to collapse
I rooted the Captivate when it was running Eclair then loaded custom ROMs and didn't think twice about sideloading.
I assumed sideloading was still required on AT&T stock ROMs which is what I have on the Note. Obviously a bad assumption on my part.
Related
anyone have a 64-bit adb driver for the slide
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
fermunky said:
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
Click to expand...
Click to collapse
it took a few days after nexus release to get a proper driver so im thinking we will be waiting a day or 2.
I used the 64bit driver for the Dream and my Vista64 had no trouble connecting to my Slide in ADB.
Thanks Fordude on Android Fourums!!!
1. Used USBDeview to uninstall all of the HTC drivers/ports
2. Unplugged HTC from PC
3. Installed PDANet software for Android (free).
4. When prompted, plugged in slide
5. After successful report of drivers being installed and program, accessed adb just fine!
Click to expand...
Click to collapse
Worked great for me on win7/64. SDK and Android Browser both work, still need root though
Also tried to use Apps2sd update zip, needs to be signed for this phone if anyone would be willing.
apps2sd--http://paulw.hardmilk.com/downloads/r1-a2sd-desire-dalvik-fresh-signed.zip
and the instructions for ADB were found here
http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
I'll have to give this a try. I remember using PDANet a while back and it worked, so probably will work again. Thanks
awesome i got it working now thanks
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
chrisinaz said:
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
Click to expand...
Click to collapse
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
the HTC Sync update for the phone was released for the phone. it should contain the necessary and appropriate drivers.
fermunky said:
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
Click to expand...
Click to collapse
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
poetik517 said:
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
Click to expand...
Click to collapse
Got it. For some reason Chrome had me Cached outside of the US, so it wasn't showing up for me.
For everyone's reference, make sure your selected country is US or just go here:
http://www.htc.com/us/support
chrisinaz said:
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
Click to expand...
Click to collapse
You'll want to remove the driver again via USBDeview. THEN make sure Charge only is selected, reinstall PDANet, and then plug in phone. If it still doesn't work, you are doing something wrong, trust me.
So I was hoping some of you guys could help me out.
Recently my Vibrant started to give me trouble with my computer. But it's only my vibrant with my computer. I can connect to any other computer no problem. Any other device is easily recognized by my computer except the vibrant.
It started after using PDANET's tethering app. I was at one point tethering all the time putting my phone in usb debugging mode and running pdanet on my computer. Then I also started using the bluetooth tethering. Once I finally got internet at my new place i stopped using the tethering option. But then I realized when i tried to get files off my phone my computer wouldnt recognized my phone anymore.
The error I get is
USB Device Not Recognized.
One of the usb devices on this computer has malfunctioned and windows does not recognized it.
Usb Root Hub Unknown device.
Try Reconnecting the device if windows still does not recognized it replace the device.
In the device manager the properties of the "unknown device" says
Status: Windows has stopped this device because it has reported problems. (Code 43)
I've tried the solution posted under here
USB Fix - Win7 x64 - USB Device not Recognized
and I've used both drivers from Samsung Kies and here
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S
(Sorry can't post links apparently)
When I try to update the driver manually for the unknown device it says that it has already selected the best driver for the device. So i don't know if it really updated it.
Any Suggestions would be really helpful. Thanks!
espy1988 said:
So I was hoping some of you guys could help me out.
Recently my Vibrant started to give me trouble with my computer. But it's only my vibrant with my computer. I can connect to any other computer no problem. Any other device is easily recognized by my computer except the vibrant.
It started after using PDANET's tethering app. I was at one point tethering all the time putting my phone in usb debugging mode and running pdanet on my computer. Then I also started using the bluetooth tethering. Once I finally got internet at my new place i stopped using the tethering option. But then I realized when i tried to get files off my phone my computer wouldnt recognized my phone anymore.
The error I get is
USB Device Not Recognized.
One of the usb devices on this computer has malfunctioned and windows does not recognized it.
Usb Root Hub Unknown device.
Try Reconnecting the device if windows still does not recognized it replace the device.
In the device manager the properties of the "unknown device" says
Status: Windows has stopped this device because it has reported problems. (Code 43)
I've tried the solution posted under here
USB Fix - Win7 x64 - USB Device not Recognized
and I've used both drivers from Samsung Kies and here
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S
(Sorry can't post links apparently)
When I try to update the driver manually for the unknown device it says that it has already selected the best driver for the device. So i don't know if it really updated it.
Any Suggestions would be really helpful. Thanks!
Click to expand...
Click to collapse
I have the same problem on my PC. I would plug in the phone and my mouse would stop working. No tethering app installed or anything.
Anyway, I just tried the ports on the back of the PC and those worked. Try a port closer to the MB
I've tried all my ports. It's still not recognized.
Check the cable and power source. Be sure cable is with good quality. I hade the same issue. I fixed it with original HTC cable and back panel USB from my deskop computer. Front USB of desktop computers often are not enough to power that consumption.
After updating to Froyo it started working again. Thanks though. I still have no clue what caused it.
Bumping to confirm, I found this thread after getting the same error. I had tried several of the USB ports on my computer but after reading this tried the 2 I hadn't yet, they both worked. Not sure why only those work now, but they do work.
Hope this helps someone.
I have a bricked galaxy s which doesn't do anything. Windows 7 reconizes an unknown device and it's not possible to install the samsung driver. Windows says that it allready has the right driver.
I can't seems to reincarnate my galaxy s. Only this small sign of live in windows 7.
It happened when I was flashing 2.3.5 and the connection went down just seconds after the start of flashing so I guess the bootloaders are corrupt.
Anyone any idea how to solve this one?
Vibrant UnBrickable Mod
The same thing is happening to my Vibrant. Tried Rooting and installing various ROMs and it is still "Not Recognized". Tried all ports on all PCs (4) and Laptops (1) and non of them work. espy1988, how did you upgrade to Froyo 2.2 if you could not connect to PC and Kies? This used to work without an issue.
Thanks
Tombias said:
I have a bricked galaxy s which doesn't do anything. Windows 7 reconizes an unknown device and it's not possible to install the samsung driver. Windows says that it allready has the right driver.
I can't seems to reincarnate my galaxy s. Only this small sign of live in windows 7.
It happened when I was flashing 2.3.5 and the connection went down just seconds after the start of flashing so I guess the bootloaders are corrupt.
Anyone any idea how to solve this one?
Click to expand...
Click to collapse
Like said above u might need to be debricked.
seems like ur phone is hard bricked.
---------- Post added at 04:33 AM ---------- Previous post was at 04:26 AM ----------
have u tried Odin back to stock using Odin or hemidal ?
I have the same problem now. I have had my Vibrant for over a year never with an issue. I have Odined it back to JFD dozens of times but now it will not recognize the usb device.
I have GB bootloaders, but never a problem before. When changing Roms I usually Odin back to JFD first and start clean.
My problem started with the phone getting stuck in landscape mode. I was running a 2.3.4 GB rom Sensation. I reflashed a few times but whenever a restored anything from Titanium it would revert back to landscape only. I decided to go back to a 2.2 rom and plugged in the phone to Odin and it was not recognized, also not as a mass storage device, no go. I used Samba to copy a 2.2 rom, Trigger, to the phone and flashed from there. The phone is good now except the computer still won't recognize it. I can use Samba to access the SDCard but I hate not being able to use Odin if things go south. Tried all usb ports and a new cable, no go. Really wierd.
Looking for suggestions......
If you're still under warranty claim it & send it.
Had same problem. There is no fix short of replacing USB port.
I found my problem. It was dirty/corroded usb port. I carefully cleaned it out (took a few times) and it's all functioning again. I also cleaned the contacts on my original usb cord and it is working again also.
I'm just now having this problem for the first time. I've tried all USB ports and cleaning the port on the phone with no luck so far. Can someone point me to the unbrickable mod mentioned early in this thread?
jnusz said:
I'm just now having this problem for the first time. I've tried all USB ports and cleaning the port on the phone with no luck so far. Can someone point me to the unbrickable mod mentioned early in this thread?
Click to expand...
Click to collapse
Have you tried installing the installing/re-installing the Samsung drivers (LINK), using another USB cable, or even another computer? I just want to make sure you've tried it all before attempting to do a hardware mod.
Anyhow, you can find a link to the unbrickable mod and other hardware mods in the "Official XDA Vibrant Bible Thread", under the "MODS/SCRIPTS" section (LINK).
Mine is the cable btw. My wife has a GSII and I was able to use her cable.
I just bought a pre-rooted fascinate. The dude i bought it from said he had MIUI flashed on it, and I trusted the guy. The rom was a TSM Voodoo kernel based Rom. I was dumb and didn't read up on Voodoo and MTD. Since I know that MIUI and CM7 are very similar, I flashed CM7 on top of the rom running.
Everything runs fine, except USB DOES NOT WORK! I cant even enter download mode to use Odin. Is there a way to get this fixed?
Thanks in advance!
The Mtd based roms such as cm7 and miui actually use the nexus drivers of I am remembering right. If I were near my computer I would gram you a link to one of the threads
Sent from my cm7 SCH-I500 using Tapatalk
It is not the fact that the computer will not recognize the phone.
The phone itself does not recognize the fact that a usb is plugged in even with the usb debugging on it does not pop up with any usb commands on the phone. usb mass storage will not come up and because the phone will not recognize the usb i am not able to get the phone to access download mode.
couple simple things to try..
1) make sure your using a factory oem usb cable
2) clean the usb port with some contact cleaner(make sure phone is off and battery pulled)
if this does nothing than maybe the phone itself has a problem and will need to be repaired/or replaced.
I know you probably already tried this but, have you got the latest samsung drivers installed on your computer you are using. From what I have seen it it most likely doesn't use these drivers but, it is worth a shot I guess. Like the guy said before there might be something wrong with the USB port. Even when I have completely bricked my phone and it will do absolutely nothing, I am always able to get into download mode. That mode is like a pre-boot mode that doesn't use any drivers or files associated with any of the roms we flash on them (as far as I am aware of). May be the reason the guy sold it to you in the first place. He couldn't do anything with it.
Ok i have been looking EVERYWHERE and it seems like all the guides are outdated and may not work if i have android 2.2.1 on the phone already.
I have
PVT 32A
HBOOT-1.33.0013 (SAPP31000)
in the settings on the phone it says my baseband version is 62.50Sj.20.17U_2.22.28.25 which doesnt seem to match up with the different guides out there.
PLEASE somebody link me to a guide that still works nowadays with android 2.2.1!!!!
Thank you!!!!!
The old guide on the cyanogenmod site should work fine. An image is provided to downgrade to like Cupcake or something, then you can root it. I was able to follow the directions a few months back on my wife's old mytouch 3g with no issue.
Where are you running into a snag?
Sent from my HTC Sensation 4G using XDA App
Thanks for replying. Well to start, here it says.
wiki.cyanogenmod.com/wiki/HTC_Magic_(32A):_Rooting
About Screen
While booted go to Settings ยป About and look at the baseband version. You will see a long string with the last piece that looks like: 6.35.10.18 or 3.22.20.17 - that is the radio version
Except my baseband is something entirely different. I posted it in the original post.
Actually, if i just knew how to downgrade to cupcake for starters that would be great.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Help somebody???? Everything on the net doesnt match up with my phone for some reason. Like its all outdated.
Which mytouch 3g do you have?
T mobile my touch 3g. Its white and DOES have the regular headphone jack. And right now it has android 2.2.1 on it.
32A
HBOOT-1.33.0013 (SAPP31000)
baseband version says 62.50Sj.20.17U_2.22.28.25
Currently this phone is incredibly slow! I mean to the point of some people considering it unusable. I use it. But its a real pain. This is why i want to root. See if maybe an older version of android or a custom rom like cyanogen will speed it up.
If i simply put SAPPIMG.nbh on a freshly formatted fat32 sd card and fast boot or whatever it says unknown fail update fail.
injo503 said:
T mobile my touch 3g. Its white and DOES have the regular headphone jack. And right now it has android 2.2.1 on it.
32A
HBOOT-1.33.0013 (SAPP31000)
baseband version says 62.50Sj.20.17U_2.22.28.25
Currently this phone is incredibly slow! I mean to the point of some people considering it unusable. I use it. But its a real pain. This is why i want to root. See if maybe an older version of android or a custom rom like cyanogen will speed it up.
If i simply put SAPPIMG.nbh on a freshly formatted fat32 sd card and fast boot or whatever it says unknown fail update fail.
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=925182.
Yay!!! This appears as if it might work for me! Thanks so much!
Ok so im running into a snag even though im following this guid exactly. Im at the superoneclick part.
In the left pane of superoneclick it says
Killing ADB server Killserver 0.10s *server not running*
Starting ADB server Startserver 4.30s *daemon not running. starting it now on port 5...
In the right pane it says
*Daemon not running. starting it now on port 5037*
*daemon started successfully*
But its just sitting there forever. Nothing is happening. I have an hour glass for a mouse cursor. I have usb debugging on the phone turned on.
In my previous attempt to root my phone (following some other guide) i did use superoneclick and it said its been rooted but then wasnt. Or at least i couldnt do a su command (or whatever) from a terminal app on my phone. Could this previous attempt be messing with it?
injo503 said:
Ok so im running into a snag even though im following this guid exactly. Im at the superoneclick part.
In the left pane of superoneclick it says
Killing ADB server Killserver 0.10s *server not running*
Starting ADB server Startserver 4.30s *daemon not running. starting it now on port 5...
In the right pane it says
*Daemon not running. starting it now on port 5037*
*daemon started successfully*
But its just sitting there forever. Nothing is happening. I have an hour glass for a mouse cursor. I have usb debugging on the phone turned on.
In my previous attempt to root my phone (following some other guide) i did use superoneclick and it said its been rooted but then wasnt. Or at least i couldnt do a su command (or whatever) from a terminal app on my phone. Could this previous attempt be messing with it?
Click to expand...
Click to collapse
Yes, it could mess with it. Did you reboot your device before trying this? It is recommended that you reboot your device after every root attempt.
I have definitely rebooted several times since the last attempt.
So, i just tried a factory reset and then tried super one click again with the same results. I of course enabled usb debugging and to allow non market apps.
What should i try next?
injo503 said:
I have definitely rebooted several times since the last attempt.
So, i just tried a factory reset and then tried super one click again with the same results. I of course enabled usb debugging and to allow non market apps.
What should i try next?
Click to expand...
Click to collapse
When using Superoneclick, did you follow all of its instructions correctly (especially disabling and enabling USB debugginig many times)? See here: http://forum.xda-developers.com/showthread.php?t=803682 and read the "Read me" for 11/10/2011.
Yeah i have disabled and reenabled usb debugging on the phone while superoneclick it trying to root like 10-15 times.
injo503 said:
Yeah i have disabled and reenabled usb debugging on the phone while superoneclick it trying to root like 10-15 times.
Click to expand...
Click to collapse
Okay. Try this method instead: http://forum.xda-developers.com/showthread.php?p=4314039.
Ok, ill try that method next. But i just tried a previous version of superoneclick and its giving me the same results except it also says waiting for device.
If i look in my device manager on windows xp pro the only thing i have for drivers says android phone and if i expand that it says android composite ADB interface.
Is this right? Or do i need mytouch drivers on my pc? Are these drivers i am seeing part of the android sdk program?
injo503 said:
Ok, ill try that method next. But i just tried a previous version of superoneclick and its giving me the same results except it also says waiting for device.
If i look in my device manager on windows xp pro the only thing i have for drivers says android phone and if i expand that it says android composite ADB interface.
Is this right? Or do i need mytouch drivers on my pc? Are these drivers i am seeing part of the android sdk program?
Click to expand...
Click to collapse
You do need drivers for your device installed on your pc. Yes, they could be for that (but you still need your device specific drivers).
Another thing is im using a mini usb cord but the plug on the mytouch is shaped differently. But it fits anyways and works for charging and file transfers.
Where can i find device drivers for my mytouch 3g? I havent seen any anywhere.
there are many topics out there right now guiding people through this but I'm a bit confused with what actually needs to be done to root the aria currently.
I would like to root and run CM7 on my Aria which is currently running stock FroYo 2.2.2. Do I need to s-off first, then use unrevoked or am I able to follow a video guide such as this one: http://www.youtube.com/watch?v=qwDNRQelpr4 and be done? Then how would I go about getting CM7 on the phone...?
First time rooting.
Sorry I'm just confused and want to make sure I have a current answer for this before starting.
See here: http://forum.xda-developers.com/showthread.php?t=1159237&highlight=root.
ah figured it out. had to turn off debugging mode when trying to recover with android flasher. that was a lot easier than I thought. Thanks!
[un]necessary said:
ah figured it out. had to turn off debugging mode when trying to recover with android flasher. that was a lot easier than I thought. Thanks!
Click to expand...
Click to collapse
Glad you were successful, but actually you don't have to turn off USB debugging when using Android Flasher.
it wouldnt read it for me if the debugging was on. as soon as I turn off usb debugging my laptop says there is a usb mass storage device connected but when usb debugging is on, there is nothing visible. oh well, it ended up working fine.
I actually ran into the same problem yesterday. Even tried two separate machines before trying to turn off usb debugging. It's weird because I've never had a problem before.