Ok guys I read that many had problems and I had that problem, I tried it around 100 times for 3-4 ****ing hours until I finally succeeded. I noticed that the installation would always fail when somehow connection between PC and phone was cut, you notice that with beep sound it makes, same sounds like when you put flash drive in or out. So I thought to change USB ports, I changed first time, did not work and I gave up but in the end I changed it again, connected it behind the PC instead of connecting it in front and woala!!! It worked. If still will not work try with other PC, the problem is always on PC if that does not work. Unfortunately I have a very bad PC and I was about to break it in half when I could not install the ROM. Good luck to y'all.
What are you trying to do exactly, adb sideload the ROM?
Related
for the past few weeks i have not been able to connect my phone with any computer using any cord. all are either vista computers or they have active sync 4.5. at this point i have reached the conclusion that the problem lies with the phone itself. i may have deleted the whatever it is that runs the usb on the phone.
any suggestions or past experience would help. i don't really feel like spending money on a new one. it gets frustrating when many mods are done from (or at least started) on the computer, and then require my to connect my phone.
btw... i have synced the phone many times before the problem started using all the same components i am trying now.
EDIT: the battery icon shows it is charging when i plug it into a usb, but from there, i have nothing, and i have also reset memory a few times since then too.
Thanks again from a modding newb!
-mike
How are you trying to sync it? Plug it in and wait for Active to launch? Launching Active yourself and clicking connect, or from within the phone itself?
I wonder if disabaling USB charging would allow you to sync it up again.. Have you reinstalled the computer software from the CD again?
I am sure there is something you can do aside from a full phone reset...
At first, i just plugged it in, like i do every day, and wait for active to launch, but it didn't, so i opened it manually.
I tried reinstalling from the OEM disk, and also downloading directly from Microsoft (both AS 4.5).
ill poke around and see if i can disable USB charging like u suggested. thank you.
Earlier today I was at my brother in laws house, was gonna copy some music from my phone to his computer (always have a usb cable in my car ). For some reason windows (vista) kept giving me unknown device and the option of mounting the sdcard never appeared.
I thought that was odd, never had the problem before, was short on time and didnt mess with it besides tryin to unplug and plug it back in. Well I get home and I see there is a new cyanogen build (a couple actually, mine is about 2 weeks old).
I plug in my phone with the normal usb cable I use and nothing. The phone charges (as it did on my brother in laws computer) but I the option to mount it doesnt come up on my phone. I dont see it in device manager and adb also cant find the device. USB debugging is turned on as well.
My only worry is that it is not a software problem because I got pretty drunk the other night and fell on my phone. The touchscreen is cracked a little but its just cosmetic damage, the phone has functioned 100% after that until now. Is there anything I can try here short of wiping and flashing my ROM again?
Tried searching but "sdcard mount issue" and other similar searches come up with pages and pages of unrelated stuff
Vista never sat well with my phone, ADB was a pain to get working and then, of course, I lose my data cable
But as far as that goes, I'm not even sure Vista works with the Android SDK, because I never got it to work. I was able to succesfully mount and unmount like it was a stock phone.
Your best bet is to, indeed, wipe and reflash. Use Cyan's recovery to make a backup and you can restore that after you sort things out with the sync'ing problems.
Well I have had the SDK working just fine, well adb and fastboot is all I have used on both my desktop and laptop.
Guess I will have to dig around for my adapter and give try giving it a wipe.
Well I just wiped and flashed the lastest cyanogen, before doing that I booted into recovery, hit the back button and it went into fastboot mode. I tried giving it the command to reboot, fastboot reboot, cmd prompt showed as it should be successful but it would never reboot.
I didnt think that was a good sign but I went ahead and wiped and flashed, same problem still persists. The sdcard worked fine in the adapter and both my ext3 and fat32 partition are working fine through the phone.
Anyone have any ideas? Would be nice if I didnt crack my screen, although its just cosmetic damage (phone functioned 100% for weeks now), I am pretty sure that will void my warranty if the phone were still under warranty.
This problem isn't huge, would like to be able to use adb again and not have to turn my phone off and use the adapter if I want to flash a new ROM.
Have you tried uninstalling/reinstalling the drivers in Windows?
It isn't showing up in device manager (only way I know to uninstall the drivers).
I think it has to be a hardware issue though, tried multiple computers, couple of different usb cables, wiped and flashed a different rom. Guess it's time to call up asurion
rondey- said:
It isn't showing up in device manager (only way I know to uninstall the drivers).
I think it has to be a hardware issue though, tried multiple computers, couple of different usb cables, wiped and flashed a different rom. Guess it's time to call up asurion
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=531310
try that. if that doesn't work, its a hardware problem.
Yeah that didnt work either. Thanks for the help though guys, just sucks this is gonna have to cost me money through insurance for a stupid crack in the screen.
Long story short, I've been about to flash a couple custom ROMs, but I understand that the safest way to do so is to first flash back to the stock ROM using Odin. That's where I hit a dead end.
Now, I've rooted my Captivate, but done practically nothing else.
When I plug my phone into my computer (both my desktop and my laptop- W7 Ultimate x64 and Professional x86 respectively), I get a rather long message about how the device has malfunctioned and basically cannot be worked with (poor wording, apologies).
I have installed the proper (x64/x86 on their respective OS's) samsung drivers, and I have tried connecting my phone from within the booted Android interface, as well as download mode (which I have little to no problem getting into).
I have also tried checking the 'debug mode' box within the phone's settings.
I'll concede that I'm no pro when it comes to this level of phone-play. I've built many a computer, and solved many a software problem, but this has me stumped.
I've thought about doing a master reset of some sort, but don't know if that would solve it.
I'd appreciate any and all advice, so thank you in advance.
[Oh, and I sincerely apologize if this was posted in the wrong section. It is, quite honestly, the first thread I've started.]
Try plugging it into another usb port. I have seen windows continue to say a device is not working even after installing the drivers if you had already plugged it in.
I am at a complete loss for words.
I'll at least make it clear right now that I think my problem is solved.
I had been plugging the phone into one of the usb ports located on the actual chassis, and took your advice and instead plugged it straight into my mother board (the back).
B
I
N
G
O
Windows auto-detected it and installed two sets of packages (drivers, I assume).
I feel like a fool, but in an odd, good sort of way.
Thank you, brother.
Not a problem glad I could help.
Absolutely! Me too, bro!
Thanks again.
This started yesterday out of nowhere, I had my phone connected to my desktop copying some music files to the SDcard. I finished copying the files and disconnected my phone. I immediately realized I missed one album I wanted so I plugged the cable back in. Boom, instant reboot. So i tried it a few more times thinking it was a fluke, same thing. I tried 2 different USB cable thinking mine may have shorted out, and I also tried connecting it to 3 different computers. All give instant reboots. So i then tried turning my hero off, taking out the SDcard, putting a different one in, and booting up. Again, reboots instantly. So, i did a full wipe and restored a nandroid from 2 days ago.... and it still reboots.
Finally I tried turning off USB debugging, and it worked fine! So no mater what I do, i can't connect to a PC with USB debugging on without it rebooting.
Any thoughts on what might be causing this strange condition? I'm going to run a RUU tonight to see if that will fix it. However even if that fixes it, i would still like to be able to understand whats actually happening here.
RUU fixed it
Just a thought: maybe the notification sound you used had become corrupt somehow? and every time you connected the USB and it attempted to play the notification sound for the USB debugging (which maybe became a corrupt file?), it caused the phone to reboot itself?
I've been having issues with my phone for a while. If I let my phone battery die to the point that the phone shuts off, it is nearly impossible to get back on. I can boot into bootloader but that's it. The status will say "Battery OK (charging)" which is a lie. The battery is not OK and it is not charging, which is why I can't leave the bootloader and boot android. It also says "Connect USB Data Cable" even though it is connected but I'm not sure if that's typical. I usually have to play around with various combinations of restarting my phone/unplugging the USB cable until it finally starts accepting a charge.
Anyway, I'm trying to flash M but when I get to the point of using the bootloader, fastboot does not work. fastboot devices returns no devices and it fails. ADB works perfectly fine and can detect my device. I know my drivers are good because a) they were untouched and worked previously and b) I fully uninstalled everything and installed Android SDK and can access my filesystem.
I believe these two issues are related. I'm running 5.0.1 LMY47I and my phone is decrypted using whatever method Wug uses in his toolkit.
Addressing your points.
1) just because adb works doesn't mean fastboot will / should
2) SDK doesn't install drivers.
Do check device manager and uninstall the driver and reinstall the naked driver following instructions in my thread. Nexus general > sticky roll up > adb and fastboot.
You're probably right, they may well be related but I just wanted to point out that 1 and 2 don't necessarily point to that being the case.
well I did get further but it is not fixed. It is a driver issue possibly. I think I may have messed my phone up, its stuck on the "google" splash screen now
Each time I loaded something to my device, ie radio, it went back to "Connect Data cable" but if I disconnected it and reconnected it, it would then transfer.
RandoTheKing said:
well I did get further but it is not fixed. It is a driver issue possibly. I think I may have messed my phone up, its stuck on the "google" splash screen now
Each time I loaded something to my device, ie radio, it went back to "Connect Data cable" but if I disconnected it and reconnected it, it would then transfer.
Click to expand...
Click to collapse
This sounds dodgy and could be multiple issues.. Really.it's a case of ruling out the hardware.. Cable, USB port,.computer. .it's tricky because it could be driver related too.
So I tried again right after getting stuck on the Google screen and got Marshmellow working, but I still had to unplug the cable after every fastboot command completed. Windows would popup with an "Unrecognized device detected" window, and the device would show as Unknown Device in device manager under USB ports. After the fastboot command completed the message would go back to "Connect USB Data Cable" and would not work unless I re-plugged it..
I tried reinstalling the naked drivers but Windows says they're all the same and that there is nothing to update. I also have gone through the full uninstall using USBDeview . I have tried other cables, even with the charging fiasco. The one thing I have not tried is another PC but that doesn't explain charging issues.
Sounds like my Nexus 7's dodgy USB port. It's gotten a bump somewhere along the road and doesn't connect properly with the USB cable anymore. Only way I can flash anything is by firmly pressing the cable into the port the whole time.
What I'm trying to say is that it sounds like your USB port is broken. Possibly...
Well I'm just going to stick to stock Marshmallow so I don't have to worry about fastboot and I'm never going to let my phone battery die. I'll see how long I can go