Related
So let me start by saying I have been researching these forums for the last 8 hours trying to following instructions on getting my phone to connect to my computer and with no luck, hoping someone out there can please help me step by step in correcting my problem.
1)I flashed DC's Rom, then flashed the most current radio, then flashed the most current Wimax.
2)I noticed that when I connect my phone to the computer, it says device is not recognizable. The phone charges but does cannot be seen by the computer as a disk drive (I'm trying to RUU to stock but the comp. will not see my phone and I've already tried running RUU but it also is having probs seeing the phone).
3)I've read Calculin's instructions in fixing the SD Card and USB as close as possible but also no luck. I've downloaded Android-SDK Tools and ran CMD with the Instructions saying type in "fastboot oem boot", from there, thats where I get stuck, it just says "waiting on device". Not sure where I go from there, I'm in Reboot mode where it has Fastboot on my evo screen.
Any help would be much appreciated, I'm just so frustrated and I'm trying to get back to square one.
Unplug your phone and restart it, then plug it back in. I had to do this 3 times before it started working again. Other than that, you might just need to download the new drivers.
And you posted in the wrong section.
Sorry about posting in the wrong section, what drivers should I install, are you talking about the new HTC Sync Files or something else? Can you point in the direction to get these files?
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
faquedado said:
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
Click to expand...
Click to collapse
You should be able to get the proper drivers from either Sprint or HTC's web site. There are links on both sites. Also, when you install / reinstall the sync drivers make sure anti-virus is disabled. If the situation continues and you've tried everything else other folks suggested look at program permissions in your anti-virus program. I was having something similar and CA anti-virus was not letting the program start-up. I had to toggle it to "allow".
Good Luck.
Purchased a gtablet, all went smooth after I installed the TNT Rom, but found some sound issues, and found out that seemed to plague a lot of other people, so decided to try another ROM - can't even recall which one now. But now where I'm stuck at is if I hold down vol up and power, I get "Recovery key detected Booting recovery kernel image" and it sits there forever. Even if I take out the microsd card, I get the same screen. A normal power attempt sits forever at the Viewsonic "birds" screen. I've tried just about every rom, none take . I'm pretty sure I had the clockwork recoverymod installed, but now I can't even get into that.
I tried volume down + power, (ATP mode?) but none of the drivers I've found are for Windows 7 64 bit, so I can't access the tablet in that mode because the lack of drivers.
Any suggestions on what to do from here?
Thanks!
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
http://forum.xda-developers.com/showpost.php?p=9302497&postcount=5
Bottom of instructions section -- a few users have written posts on nvflash for windows.
LGCubana said:
http://forum.xda-developers.com/showthread.php?t=989320&highlight=nvflash+windows
Good Luck
Click to expand...
Click to collapse
Hi,
Thanks for the link.. I think I've seen that - I don't see a APX driver missing in Device Manager - there is a ADB Interface, however when I let that install drivers, it says the Device cannot start - Code 10.
I may have another computer I can boot up and try
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
butchconner said:
phirephoto,
I wrote the USB post and used the files there to NVFlash in APX mode. I know the info there is accurate.
I also have found, however, that if you install the whole SDK kit instead of the files in my post, it installs ADB. I don't know much about ADB but I know it basically works about the same.
If you have the APX driver it says it is the nVidia USB driver in Device Manager. So I am assuming you have installed SDK.
I can only suggest you make sure what files are installed on your PC and what method you are using and then research this site. I know several people have used the ADB methods and posted about them.
Good luck.
Rev
If you have another computer -- try the method reobeet posted along with the Advent Vega USB files. I know that has worked.
Click to expand...
Click to collapse
It did work on my old POS XP Laptop I knew that thing was useful for something!
Thanks again.. Never thought I'd be so happy to see "TapnTap" again. And now I'm up and running on the Vegan rom
Hello, i am currently trying to root my sisters galaxy s 4g... Her Baseband is T949VUVKI1. Firmware is 2.3.5, Build Number is GINGERBREAD.VUVKI1. i remember flashing her phone to 2.3.5 and download mode working perfectly fine, and for some reason it wont go into download mode at all... the computer is not recognizing her phone either. YES, i do have usb drivers installed otherwise my galaxy s 4g wouldnt be recognized on my computer(odin specifically, not turning yellow). Please help, i have searched everywhere in the internet and tried almost everything... Volume up and down and plug charger, batter out volume up and down usb and battery in etc. PLEASE HELP!! Thank You in Advance.
Nvm
10c
1. Try reinstalling to drivers. Also make sure you're using the same USB port as Windows can be funny about it it sometimes.
2. if download mode is being difficult, go download the Android SDK from www.android.com. Install it, run it, and only download the platform tools. When that's done, open a command promt, CD to where the plaform tools installed (either c:\program files\Android\Android-sdk\platform-tools or c:\program files (x86)\Android\Android-sdk\platform-tools ), then issue the command: adb reboot download.
3. I suggest you check the dev section for bhundven's one-click collection. Uses Java and Heimdall vs. ODIN and works easily.
Sent from my SGH-T959V using XDA App
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Tytan0007 said:
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Click to expand...
Click to collapse
Get it back into download mode, go grab a bhundven's one-click. The one-clicks utilize Heimdall vs. ODIN, which means they use open-source USB drivers instead of the proprietary Samsung drivers. See if that enables the computer to see the phone. If so, flash the one-click
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Tytan0007 said:
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Click to expand...
Click to collapse
That's a good idea. Some people have reported conflicts between the drivers.
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Tytan0007 said:
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Click to expand...
Click to collapse
I wish I had a good answer. ODIN's a funny animal. I've been fortunate and not had any problems with it. I am hoping you are correct - maybe it was just a driver conflict. Let me know how it goes.
didn't work...
You could try downloading a terminal app from the market. Open the terminal and type:
reboot download
See if that does it.
***Update***
Okay, so Oneclick was not working at all no matter what I did with the drivers. However, in all my tinkering with it I installed the Samsung Driver, the Open Source one, and some gadget driver as well from oneclick.
Doing this put all these drivers in my computer. Then I went into my Device manager (Win 7) and looked at my USB driver and I uninstalled everything and went to the stock win 7 usb driver. Then I plugged my phone in and my computer began searching for drivers for this device when it decided that it would be a good idea to load all three drivers at once and voila my phone was then showing up on ODIN 1.85.
I then proceeded to flash my phone with a rom, probably the wrong one considering I was coming from 2.3.5 and my phone boot looped and then soft bricked(sorry if I used these term incorrectly, noobin it).
After, some nervous moment of scouring XDA I found the god-send of a post on getting in to download mode, using odin, and flashing stock 2.3.6 - thank you Raver(I believe). When I did this, my phone magically started obeying ODIN like a devout viking and is now running 2.3.6 superbly.
Keeping with my phones newly found viking heritage, I intend to figure out how to properly root it, update the kernal and modem(not sure which one is best), get CWM, and subsequesntly put in Valhalla Black.
Seeing as though this last rendevous with flashing caused me a little scare I may hold off and wait to see what the next big update is (maybe a port ICS variant) and then go with that.
Anyway, thank you Stephen for helping me out with this and to everyone in this post.
Here's some reading for you Tytan,
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29
PS: Unless you wanna brick your phone, do not flash anything that isn't intended for the SGH-T959V Samsung Galaxy S 4G. You're saying you wanna flash a Vibrant ROM. You can, if you want an expensive paperweight. Happy flashing!
2.3.5 may have been for vibrant...yeah I think I got lucky. I did it prior to knowing about xda.
Sent from my SGH-T959V using XDA App
Tytan0007 said:
didn't work...
Click to expand...
Click to collapse
How are you getting into download mode?
There was a post in another thread where the person apparently was using the power menu to get into download mode or maybe the adb command.
Have you tried both the old fashion volume +/- and plug in usb cable? Or the adb command?
Do you have access to another computer? Believe it or not sometimes just changing computers will make the difference.
Weird when I replied there was no posts other than the ones on the first page...oh well glad its working now.
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
I have read all types of forums to Reboot Bootloader. Yeah, I know stuck at the beginning, not a good sign.Any way I went to Developer.android and got SDK. Followed various suggestions and have it on machine. However the windows 7 won't recognize device. I downloaded Motorola Device Manager for the drivers (I beleive this may be the issue) and it found no updates. I have debugged checked on Xoom, but jellybean icon shows up intermittently. When I type in CMD prompt to adb reboot bootloader, it doesn't recognize the device.
Other CMD commands suggested during instruction video worked verifying I had ADB installed coirrectly. I checked the device in control panel and it is unidentfied.Device properties has this error" Windows has stopped this device because it has reported problems. (Code 43)"
Please, can someone assist. I think that I need the drivers, but the motorola Device manager is the only tool I can find and I dont think it has the drivers, I could be wrong, but this is what I'm guessing.
Ok. I found online that the new USB 3.0 has issues with this process. I plugged into a 2.0 USB and I'm in business. I've gone through unlocking. Now I can't locate the Universal Xoom Root Zip. All tutorial links that I could find go to a link that no longer has the file. can someone point me in the right direction or send me a link to the file- Thanks for the help
Ok status update. I was able to find the file and have successfully Rooted. The question, now is I restarted and I have an Green Android robot on my screen with Tiamat engraved on front stomach area. I believe I was in recovery last. IS the Xoom doing anything in the background. I don't want to interrupt something if it is running. I have downloaded BiGPART and Omni 4.4 components but I seem to be stuck
Wow... Not one response. I was able to figure it out and now am the owner of 4.4