[Q] Total Noob in Need of Lots of Help :( - Nexus S Q&A, Help & Troubleshooting

I just got my SNS yesterday and it's my first android phone (was previously using an LG cookie) First thing I did was try to root it, and I seemingly succeeded, or so I thought. It looks like it's rooted and the superuser apps there but I can't install apps using any of the guides I find or even update to 2.3.2 (keep getting and error 7 msg). When I try to install using APKInstaller it tells me it can't find the device, which I think is the problem.
I think the problem is that someway or another windows 7 64 bit stopped recognizing my phone as a Nexus S and now recognizes it as a portable device in device manager (There's also an Android Phone, with an Android Composite ADB interface) I used the SDK to install all the updates available including the google usb driver rev. 4. I tried updating the Portable device driver using the google usb driver but windows keeps it as a WPD Filesystem Volume Driver. Also I noticed when I checked to see if adb gave me a serial number for the phone using the cmd prompt commands in the rooting guides it comes up blank.
I used usbdeview to delete everything seemingly related to Android, but everytime I reconnect the phone it, installs the drivers for the portable device.
I need help to make windows recognize the phone as a nexus s again so I can update and install apps and games etc. If anybody out there can help i'll really appreciate it. Explain the steps to me as if you were talking to a child, leaving nothing out plz. Thanks for any assistance.
I live outside the US (no android market) and would hate to think I messed up and expense phone purchase in just one day

Not quite sure where to start. But my intuition tells me its the Windows 7 64-bit and drivers that's not playing along. You might want to google if other users are having trouble with W7 64-bit with Android drivers. Otherwise, find another computer and repeat the steps. If not, flash a custom ROM to see if that eliminates the problem. You haven't damaged your phone. Don't worry.

just install directly from android market website
Sent from my Nexus S using XDA App

I assume you mean instal the update from the market (which I can't do because I don't have wifi)?
I managed to get the adb to list a device number after I installed java x32 & x64 bit. I still can't install apps or get the update to work, but I'll try unrooting and then rerooting my phone as see how that goes.
Oh, I haven't done the initial sign into gmail thing yet in case that makes any difference
Edit: god I feel stupid. I didn't realize that I had to upgrade from 2.3 to 2.3.1 and then to 2.3.2. I did that an everything upgrade without any problems. Now just got to figure out how to install apk's and I'm golden
Edit 2: Ok, I figured everything out and now i'm up to date with updates and I can install apps and games. Oh Happy Day Thx for all the help

Related

anyone else having problems with 64bit galaxy S drivers?

I did the one click root with no problem, now can't do the clockwork mod because the drivers keep failng , even tried the root again and it won't work either because of the drivers. I can get it to sync like 1 in 10 times, verified because I can get adb shell working. but it seems if I try to do anything, the drivers basically reset themselves. i didn't have this problem previously, although i did have to reinstall the drivers everytime, now that isn't even working, has anyone got this working correctly? I only have windows 64 bit machines.
EDIT: if someone could post a link to drivers that are known to be working, that would be appreciated, then at least I know I'm using ones that are working for people.
What version of windows are you running?
does it give you any errors, or does it just not regonize it? Maybe an issue with driver signing.
Sent from my SPH-D700 using XDA App
windows 7 ultimate 64 bit. the device manager usually shows errors, i show a bunch of drives listed, after a few tries of deleting the J drive, I get it to show up as wpd file or something like that, then it works for a minute or so, it will let me into adb shell and I can do SU, but if i try adb push, it hangs. same thing when trying to do the 1 click scripts, I know if its working or not, because if it isn't working, the script just hangs, then 10 tries of unplugging and plugging in and it finally connects and runs the scrips although giving errors and such, I did root just fine using the scripts, so I'm not sure whats going on with these drivers. maybe if I knew which things to uninstall from the device manager, i could start from scratch, using back usb port, front usb port, makes no difference. i'm gonna wear out the micro usb port if I keep plugging and unplugging the phone like this.
Hmm it sounds to me that finding the associated driver files in the registry/file system and clearing them. Rebooting. And reinstall of driver would be the best plan of action.
In device manager you should notice a new driver pop up when you plug in your phone. From there you could uninstall the driver, but be aware if you just uninstall the driver without removing the driver files 7 will auto find them and reinstall them when it sees your device.
Without being able to look specifaclly at the computer its hard for me to tell if its a corupt/broken driver causing the problem. There could be a few things doing it.
Sent from my SPH-D700 using XDA App
is there a way to clean everything out? like what things in device manager would I clean out? I can't seem to find them all.
Nanncee said:
Hmm it sounds to me that finding the associated driver files in the registry/file system and clearing them. Rebooting. And reinstall of driver would be the best plan of action.
In device manager you should notice a new driver pop up when you plug in your phone. From there you could uninstall the driver, but be aware if you just uninstall the driver without removing the driver files 7 will auto find them and reinstall them when it sees your device.
Without being able to look specifaclly at the computer its hard for me to tell if its a corupt/broken driver causing the problem. There could be a few things doing it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
It's not so much in device manager that your looking to remove it. Usually when a driver is installed, it places a directory on your c drive with all the files needed. now those files could be located in /windows or /program folders, or they could be in their own folder for titled samsung for example. (this usually isn't the case for storage drivers like we are dealing with)
I am not sure how samsung wrote their driver package, but you may be able to run it again and have it remove the files for you. I would verify on a windows system, but I don't have one running right now. You may also be able to use the driver installer to follow the path to where it places the files. again it all comes down to how the driver installer was written.
also just thought of this, and it is a long shot, but verify that you don't have an antivirus/firewall blocking the connection.
I don't know if you have another computer, if you do I would try it on that system as well.
Sorry I can't be more definitive on where to remove them. But without a windows system I hate to send you looking in the wrong spot and deleting things that shouldn't be.
http://www.nirsoft.net/utils/usb_devices_view.html this program will let you wipe any usb device from the history... worth a shot/try a different port
On 64-bit Windows, you'll probably need to manually set the driver for the ADB composite device. Just do update driver from the device manager, browse for drivers and hit let me pick from device drivers on my system.
Worked for me anyway.
But it sounds to me like your problem is not driver related. Try another USB cable. The stock one is pretty poor. My first Epic's had this problem, so I got another cable and it magically started working again. Also, front USB ports are more finicky, so you could try the back ones.
Linux FTW.
I never got the most recent clockwordmod one click method to work, I always have to use 2.5.0.9, then do the update.zip method for 2.5.1.0., I tried on both of my laptops, one running 7U64, the other running 7U32.
did this and tried two cables from both of our epics, also, it worked fine to do the clockwork mod. used front and back usb ports. no luck.
Firon said:
On 64-bit Windows, you'll probably need to manually set the driver for the ADB composite device. Just do update driver from the device manager, browse for drivers and hit let me pick from device drivers on my system.
Worked for me anyway.
But it sounds to me like your problem is not driver related. Try another USB cable. The stock one is pretty poor. My first Epic's had this problem, so I got another cable and it magically started working again. Also, front USB ports are more finicky, so you could try the back ones.
Click to expand...
Click to collapse
Try a NON Samsung cable. Not one from another Epic box.
i finally got it to work, used the wifes laptop, something apparently is screwed up on my machine. wish I knew what.
robl45 said:
i finally got it to work, used the wifes laptop, something apparently is screwed up on my machine. wish I knew what.
Click to expand...
Click to collapse
Glad to hear you got it solved. As to whats wrong with your computer, I have no clue. Good luck though. If all else fails, wipe and reinstalls are your friend.
Sent from my SPH-D700 using XDA App
robl45 said:
EDIT: if someone could post a link to drivers that are known to be working, that would be appreciated, then at least I know I'm using ones that are working for people.
Click to expand...
Click to collapse
.....
I have had many problems with drivers on my windows 7 64 bit machine.
To get the epic drivers to work I had to uninstall all other samsung phone drivers first. Download the x64 drivers from that post, upzip.
Plug your epic in mount it. Open the device manager and manually point it at the unrecognized device at that folder. I had to do this for 3 or 4 separate entry's.
Play with it a bit and you should be able to get it working with those.
Hope this helps.
Bah new user bs. Cannt post the link. Go over to SDX developers epic development section. There is a sticky "Confirmed Working Drivers"
I said screw it with the Samsung Drivers. Just installed PDAnet when I got this computer a week ago and no issues (win7 home 64-bit). It asks during setup what phone drivers you want to install. Select Samsung, let it do its thing, and you're all set. ADB works flawlessly, no need to mount sd card to get it to work.

No driver for my Nexus S 4G, please help

Hi,
I have tried PDAnet to install driver for my phone. When it got to where it asked me to plug in my phone, i plugged in nothing happen so i had to click on cancel. Then i installed SAMSUNG_USB_Driver_for_Mobile_Phones. After it was installed i went to Devices and My phone showed as Unknown Device. i went in to update driver and there was not ADB device in the selection for me to choose. Please help... thanks..
what OS are you using
the most up to date win7 finds it pretty accurately. If not your BEST bet that i have found is use those sammy drivers, THEN install google android SDK/corresponding JAVA. It sounds like alot but you will get alot more as you fiddle with your phone down the line.
When you get the sdk and java sdk installed you can download googles USB drivers through the sdk list and then you should be able to find the ADB device listing IF your computer doesnt find your phone automatically after that.
Ive done this alot now and have had a different config almost every time.
XP has ALWAYS needed the sdk's to work for me.
I have windows 7 home. I have not update my windows 7 at all. I already got SDK and JDK installed. I checked the google USB driver when i was at the list of things to package to download.
tevil said:
what OS are you using
the most up to date win7 finds it pretty accurately. If not your BEST bet that i have found is use those sammy drivers, THEN install google android SDK/corresponding JAVA. It sounds like alot but you will get alot more as you fiddle with your phone down the line.
When you get the sdk and java sdk installed you can download googles USB drivers through the sdk list and then you should be able to find the ADB device listing IF your computer doesnt find your phone automatically after that.
Ive done this alot now and have had a different config almost every time.
XP has ALWAYS needed the sdk's to work for me.
Click to expand...
Click to collapse
i have updated my windows and still no luck. What is a sammy driver ...
tevil said:
what OS are you using
the most up to date win7 finds it pretty accurately. If not your BEST bet that i have found is use those sammy drivers, THEN install google android SDK/corresponding JAVA. It sounds like alot but you will get alot more as you fiddle with your phone down the line.
When you get the sdk and java sdk installed you can download googles USB drivers through the sdk list and then you should be able to find the ADB device listing IF your computer doesnt find your phone automatically after that.
Ive done this alot now and have had a different config almost every time.
XP has ALWAYS needed the sdk's to work for me.
Click to expand...
Click to collapse
Here are the drivers I installed from Samsung when I manually updated my prl
http://www.mediafire.com/?yns6ianoai12z6n
I uploaded this last week, just extract the rar and run the exe
Sent from my Nexus S 4G using Tapatalk
i already had this driver install however i still followed the Setup. I uninstalled the existing driver and install this again and still no luck
fergie716 said:
Here are the drivers I installed from Samsung when I manually updated my prl
http://www.mediafire.com/?yns6ianoai12z6n
I uploaded this last week, just extract the rar and run the exe
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
are you letting window just give you the list of drivers or are you browsing for the adb one? windows will initially give you a list of like 20 drivers, then you select "let me pick" or something like that and you go through the list of like 1000 instead.
if your on 7 and have everything installed then maybe you have a bad cable. do you get anything that even loks like your computer is trying to install yoru phone.
It was the cable. Last night i went to Sprint and bought their 20 dollar cable and everything was fixed. Drivers were installed with PDAnet and i already rooted the phone , unlocked bootloader, put on CWR and installed CM9 Thank you for your help.
tevil said:
are you letting window just give you the list of drivers or are you browsing for the adb one? windows will initially give you a list of like 20 drivers, then you select "let me pick" or something like that and you go through the list of like 1000 instead.
if your on 7 and have everything installed then maybe you have a bad cable. do you get anything that even loks like your computer is trying to install yoru phone.
Click to expand...
Click to collapse
Ughh $20.. They use to give them for free.. Or atleast the corporate store near me did when I had my Samsung Moment.
But yea I just bought the wrong cable (Nexus One) like a dumb ass from amazon. It fits but super short
Sent from my Nexus S 4G using Tapatalk
i was this close to buying a cable for 3 bucks from Amazon. Now i look at my Sprint cable , it does look different from the cable i saw on amazon. i dont know man, on ebay and amazon those cables are all Nexus S OEM cable, dont know if they would have worked or not
fergie716 said:
Ughh $20.. They use to give them for free.. Or atleast the corporate store near me did when I had my Samsung Moment.
But yea I just bought the wrong cable (Nexus One) like a dumb ass from amazon. It fits but super short
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
i like how i was in class and i went in to your wallpaper HERE and half your wallpapers were half-naked women
fergie716 said:
Ughh $20.. They use to give them for free.. Or atleast the corporate store near me did when I had my Samsung Moment.
But yea I just bought the wrong cable (Nexus One) like a dumb ass from amazon. It fits but super short
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Here is how I got mine to work.
install android sdk here
http://developer.android.com/sdk/index.html
navigate to you android sdk folder. typical path:C:\Program Files\Android\android-sdk
double click sdk manager.exe
under extras, install google usb driver package. See screenshot here for example.
http://developer.android.com/sdk/win-usb.html
bob13bob said:
Here is how I got mine to work.
install android sdk here
http://developer.android.com/sdk/index.html
navigate to you android sdk folder. typical path:C:\Program Files\Android\android-sdk
double click sdk manager.exe
under extras, install google usb driver package. See screenshot here for example.
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Doesn't work it says windows can't find driver
Im struggling here the only thing keeping me form fun is some stupid usb drivers nothing wants to work at all.
Phone will mount when on, but when in fastboot mode it makes a dudududu sound and under deivces it says android 1.0 and when i try to update the driver it cant be found online, and when i have the actual driver on computer it still says windows cant find the driver.
Download the adb drivers attached below
Google search for: Samsung_Mobile_USB_Driver_V1.3.800.0.msi
Install the Samsung "Samsung_Mobile_USB_Driver_V1.3.800.0.msi" drivers and then reboot.
Then plug in your NS4G and let it do it's thing. It will say that it needs a driver. Select no and advanced.
Then go to where you saved the attached file drivers and in the root select it and let is load the Android ADB drivers.
Then reboot.
Then in your device manager you'll see the Android ADB device with a yellow triangle.
Right click and update driver.
Then select the bottom choice so that you can look at all drivers and in the list is the Android ADB.
Select it and next to update the drivers.
Then reboot and you should be good to go.
It took me several hours to figure this out and I used every other method I could find and they did not work, but this did.
This is on Windows XP Pro SP3
If this helps, please hit Thanks!!!

[Q] SK4G not being recognized on PC

I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.

Samsung WP7 USB - to - PC not being recognized ?!?!?

Hi all !
This is so simple but it is driving me crazy.
I run Win 7 X64 and have a new [ network unlocked ] Samsung Focus 2 SGH-i667 phone.
No matter what I do, the PC will not fully recognise the phone when it is usb connected to the PC.
Zune *does* see it
Kies [ latest version ] does *not* see it.
Windows Phone 7 Developer Tools does *not* see it.
Windows *partially* does see it but it does not load the "Qualcomm CDMA MSM" drivers - as such,developer unlocking so as to side-load application XAP's is impossible.
I have tried numerous USB cables / numerous different USB ports / the *latest* Samsung USB drivers / forcing Windows Update / even a clean machine etc..... all to no avail.
I plug the phone in, it starts to load the driver and then it comes up with Device Driver not found - I let Windows Update do its thing, but still no go.
Please Help !
This is such a simple thing,
How can I make Win 7 X64 *see* my Samsung WP7 phone fully so that I can developer unlock it to side-load application XAP's ?
All help will be hugley appreciated.
Ben
I pl
my first suggestion would be to remove all the drivers you have installed and get it working correctly with zune, the best way I find to do that is use This program, it lists all USB devices, delete all the ones that maybe associated with WP, delete and uninstall!
then remove zune
install zune, restart then plug in your phone, see what happens then, for now, forget any other driver you may think you need,
dazza9075 said:
my first suggestion would be to remove all the drivers you have installed and get it working correctly with zune, the best way I find to do that is use This program, it lists all USB devices, delete all the ones that maybe associated with WP, delete and uninstall!
then remove zune
install zune, restart then plug in your phone, see what happens then, for now, forget any other driver you may think you need,
Click to expand...
Click to collapse
Hi RC
Genuinley - many thanks for helping out.
Did what you suggested - everythinhg is clean as a whistle - still the same issue - Zune sync's and see's the phone, but Win 7 X64 see's some of it but not enough for the developer unlock [ chevronwp7 ] to proceed - it jusy comes up with the error saying something like cant connect via usb - try re-opening zune etc.....
Please see the attached " devices.jpg " to see what my system is " seeing " .
My phone is a newer Focus 2 SGH-i667 WP7.5 phone - maybe its too " new " ?
Any help will be grealty appreciated.
Thanks again,
Ben
ben ifin said:
Hi RC
Genuinley - many thanks for helping out.
Did what you suggested - everythinhg is clean as a whistle - still the same issue - Zune sync's and see's the phone, but Win 7 X64 see's some of it but not enough for the developer unlock [ chevronwp7 ] to proceed - it jusy comes up with the error saying something like cant connect via usb - try re-opening zune etc.....
Please see the attached " devices.jpg " to see what my system is " seeing " .
My phone is a newer Focus 2 SGH-i667 WP7.5 phone - maybe its too " new " ?
Any help will be grealty appreciated.
Thanks again,
Ben
Click to expand...
Click to collapse
if its syncing with zune then your at least half way there, did you leave zune open when using the XAP deployer? did you install the full SDK? I know there are "smaller" packages out there but where theres doubt there are potential problems, we need to turn them in to real problems or rule the out so uninstall whatever SDK you used, make sure the full SDK is re installed.
Im actually about to try installing my Focus S on a brand new Win 8 x64 system So ill double check all the steps but I didn't think we needed the Samsung drivers to XAP install, I thought that was cab updates and QPST stuff.
Anyhow, make sure zune is running and is synced, make sure you remove and reinstall the full SDK and get back to me, ill check all the steps today
its connected to win 8 at the moment, no zune, no SDK and its installed as a portable device (Samsung SGH blar blar) im just getting the zune package, ill sync it, then ill install SDK and attempt some XAP deploying
dazza9075 said:
if its syncing with zune then your at least half way there, did you leave zune open when using the XAP deployer? did you install the full SDK? I know there are "smaller" packages out there but where theres doubt there are potential problems, we need to turn them in to real problems or rule the out so uninstall whatever SDK you used, make sure the full SDK is re installed.
Im actually about to try installing my Focus S on a brand new Win 8 x64 system So ill double check all the steps but I didn't think we needed the Samsung drivers to XAP install, I thought that was cab updates and QPST stuff.
Anyhow, make sure zune is running and is synced, make sure you remove and reinstall the full SDK and get back to me, ill check all the steps today
its connected to win 8 at the moment, no zune, no SDK and its installed as a portable device (Samsung SGH blar blar) im just getting the zune package, ill sync it, then ill install SDK and attempt some XAP deploying
Click to expand...
Click to collapse
Thanks - I'll do that and report back - look forward to hearing how you go at your end too.
Ben
ok, exact step by step - clean install of win 8
plug phone in (device manager lists it as a portable device - Samsung SGH-i937)
Download zune 4.8 and install, it will ask you to unplug the device so unplug it
plug in device and sync it properly
turn off zune
download and install the full 7.1 SDK note that it will throw up all sorts of errors, just install it anyway
don't restart
then download the SDK 7.1.1 patch, that will let it run on windows 8
don't restart
turn on zune and sync (note that device manager still lists it as a portable device - Samsung SGH-i937)
open up application deployment from the sdk and upload your XAPs (assuming you have it unlocked that is?)
the mere fact that is installing other drivers tells me its maybe conflicting, remove all traces of the drivers using USBDVIEW, also uninstall them, check the add remove programs in the CP and remove anything in there as well, the strange thing is I get those drivers installed when I mess about with the low level hardware using QPST, oh try a different USB port as well, not on the same bank, use a different set if you can.
dazza9075 said:
ok, exact step by step - clean install of win 8
plug phone in (device manager lists it as a portable device - Samsung SGH-i937)
Download zune 4.8 and install, it will ask you to unplug the device so unplug it
plug in device and sync it properly
turn off zune
download and install the full 7.1 SDK note that it will throw up all sorts of errors, just install it anyway
don't restart
then download the SDK 7.1.1 patch, that will let it run on windows 8
don't restart
turn on zune and sync (note that device manager still lists it as a portable device - Samsung SGH-i937)
open up application deployment from the sdk and upload your XAPs (assuming you have it unlocked that is?)
the mere fact that is installing other drivers tells me its maybe conflicting, remove all traces of the drivers using USBDVIEW, also uninstall them, check the add remove programs in the CP and remove anything in there as well, the strange thing is I get those drivers installed when I mess about with the low level hardware using QPST, oh try a different USB port as well, not on the same bank, use a different set if you can.
Click to expand...
Click to collapse
Hi dazza
In your Device Manager, do you get any " yellow flags " like I do with the .jpg I posted above ?
Ben
ben ifin said:
Hi dazza
In your Device Manager, do you get any " yellow flags " like I do with the .jpg I posted above ?
Ben
Click to expand...
Click to collapse
nope, I don't sorry.
have you played with the diagnostic tool at all? perhaps changed the USB mode?

[Q] RCA 7" 8GB Tablet

I need help figuring out how to root a RCA RCT6077W22 tablet. It has Android Jellybean 4.1.1- v1.0.1, 8GB built in storage, 1GHZ processor, Google apps installed, kernel is [email protected]#132.I'd like to try to root it from the tablet itself if not I'm familiar with SuperOneClick as I've used it for my Samsung Galaxy S 4G before I should it. If it comes to that option I need to be able to use a rooting program on my computer that does not require internet the only internet I am able to use is the libraries. I have a laptop but no charger so my laptop is dead. I'm not a noon when it comes to rooting as I've mentioned I've done it before. Just need help finding a root for this tablet. I appreciate any help I get and thank you. If you need more info feel free to ask. I've also looked at the topic about the 4GB but its not that helpful is why I created my own topic.
deathscreations said:
I need help figuring out how to root a RCA RCT6077W22 tablet. It has Android Jellybean 4.1.1- v1.0.1, 8GB built in storage, 1GHZ processor, Google apps installed, kernel is [email protected]#132.I'd like to try to root it from the tablet itself if not I'm familiar with SuperOneClick as I've used it for my Samsung Galaxy S 4G before I should it. If it comes to that option I need to be able to use a rooting program on my computer that does not require internet the only internet I am able to use is the libraries. I have a laptop but no charger so my laptop is dead. I'm not a noon when it comes to rooting as I've mentioned I've done it before. Just need help finding a root for this tablet. I appreciate any help I get and thank you. If you need more info feel free to ask. I've also looked at the topic about the 4GB but its not that helpful is why I created my own topic.
Click to expand...
Click to collapse
Did u figure out how to root your rca tablet....I have one and I need mine rooted also I can't store any apps on my ad card
Can you give more specifics such as the the model number, what version of android is it running?
Sent from my Nexus 5 using xda app-developers app
I have the rct6378w2 RCA 7' 8GB tablet (4.2.2 JB). (Black Friday 2013 Walmart for $49)
I was able to root it by first installing the pdanet drivers (for adb access). And then using the kingo app, which you can get from http://www.kingoapp.com/.
Its free but closed source. I found it via this youtube video. https://www.youtube.com/watch?v=8MiZtZCqu4k
Worked even with the 1.0.2 update installed (which I have no clue what it did (17MB).
Takenover83 said:
I have the rct6378w2 RCA 7' 8GB tablet (4.2.2 JB). (Black Friday 2013 Walmart for $49)
I was able to root it by first installing the pdanet drivers (for adb access). And then using the kingo app, which you can get from http://www.kingoapp.com/.
Its free but closed source. I found it via this youtube video. https://www.youtube.com/watch?v=8MiZtZCqu4k
Worked even with the 1.0.2 update installed (which I have no clue what it did (17MB).
Click to expand...
Click to collapse
TAHNK YOU Takenover83 you are amazing. I rooted my tablet same model and set up as yours.
frarredo here is the information you were asking about in the picks below..
Please take notice to picture Screenshot_2013-11-29-23-15-32.png running bubble launcher, xposed framework , and xhalofloaingwind, to muliwindows on the tablet and all android phones,
Sorry here is the last pic it did not let me upload
Help
Takenover83 said:
I have the rct6378w2 RCA 7' 8GB tablet (4.2.2 JB). (Black Friday 2013 Walmart for $49)
l]
Worked even with the 1.0.2 update installed (which I have no clue what it did (17MB).
Click to expand...
Click to collapse
I cannot get pdanet to get the drivers. I cant find any drivers anywhere. Pdanet says to click ok after connecting, and it just says no android device found..I think there's an error box too.. I don't know how to fix it. I also have the tablet from the black friday event. Exact same one. Also, I have USB debugging on...
UPDATE: I found out the problem! The support files weren't in the root file I had the .exe in. I just moved the .exe to the same folder with the support files, and now I'm rooted and ready! Thanks!
wy3r5 said:
I cannot get pdanet to get the drivers. I cant find any drivers anywhere. Pdanet says to click ok after connecting, and it just says no android device found..I think there's an error box too.. I don't know how to fix it. I also have the tablet from the black friday event. Exact same one. Also, I have USB debugging on...
UPDATE: I found out the problem! The support files weren't in the root file I had the .exe in. I just moved the .exe to the same folder with the support files, and now I'm rooted and ready! Thanks!
Click to expand...
Click to collapse
how are you turning on usb debugging? I also have this tablet(purchased on black Friday from Walmart like everyone else) and mine doesn't seem to have that option anywhere. in fact, compared to the previous two android products I have, this device seems to lack ALOT of available functions. though I am capable of navigating a recovery menu at boot. but that doesn't do me any good for using pdanet. that seems to be my biggest road block. pdanet wont install because the onl;y way I can allow my device to connect to my pc with adp is using the adp updater in the recovery boot menu.
Desarial said:
how are you turning on usb debugging? I also have this tablet(purchased on black Friday from Walmart like everyone else) and mine doesn't seem to have that option anywhere. in fact, compared to the previous two android products I have, this device seems to lack ALOT of available functions. though I am capable of navigating a recovery menu at boot. but that doesn't do me any good for using pdanet. that seems to be my biggest road block. pdanet wont install because the onl;y way I can allow my device to connect to my pc with adp is using the adp updater in the recovery boot menu.
Click to expand...
Click to collapse
It is a hidden option that needs to be enabled. Follow this guide: www ninjaromeo com / enable-usb-debugging-developer-options-jelly-bean/
I just enabled this option on my Walmart BF 7" RCA RCT6378W2 tablet.
Sorry I had to mangle the link because XDA wont let me link external sources yet.
Glad I could help a few. Now, someone get on a functional recovery ;p
I have poked around a little at the stock recovery, backing it up, etc.. But am not brave enough to try and get CWM working on it.
I was able to use th Xposed framework for a few mod's no problem. Battery mod, reboot menu, hide navbar, etc.. But Xposed can only do so much.
Edit: I heard on reddit this tool also works for rooting. I have not tested it (already rooted with the other method).
http://www.cydiaimpactor.com/
Getting Debugging to work.
I was not drunk when I made this post...I have the RCT6378W2 if you go to about tablet in your settings and repeatedly tap the build number...the deveolper options will appear...I fell out of my seat when i discovered this.
On a side note...if you repeatedly tap the android version...a cute picture of the android jellybean will appear. Try it.
rca 7" dual core tablet root
Takenover83 said:
Glad I could help a few. Now, someone get on a functional recovery ;p
I have poked around a little at the stock recovery, backing it up, etc.. But am not brave enough to try and get CWM working on it.
I was able to use th Xposed framework for a few mod's no problem. Battery mod, reboot menu, hide navbar, etc.. But Xposed can only do so much.
Edit: I heard on reddit this tool also works for rooting. I have not tested it (already rooted with the other method).
http://www.cydiaimpactor.com/
Click to expand...
Click to collapse
im not down with kingo, too risky! gonna try impactor. i will report back soon :fingers-crossed:
---------- Post added at 09:31 PM ---------- Previous post was at 09:15 PM ----------
1: Install drivers. Seeing as RCA does not provide drivers, we had to find some that work. That's where PDANET comes in. Their drivers support a very wide range of Android devices. We are not installing it to tether. We just want the drivers it provides. So download PDANET, install, let it detect your device, install the drivers, and then afterwords you can uninstall it.
2: Enable Developer Options. Settings>About tablet> Tap Build Number a bunch of times till it's enabled.
3: Enable USB Debugging. Options>Developer Options>Click On (up top)>Then checkmark USB Debugging
That should clear up some of the confusion in this thread. How you root after step 3 is up to you. Personally, I did it with Kango. Which was straight forward. Connect device, hit a button, Say yes to a couple questions, reboot, presto done.
cueballs said:
It is a hidden option that needs to be enabled. Follow this guide: www ninjaromeo com / enable-usb-debugging-developer-options-jelly-bean/
I just enabled this option on my Walmart BF 7" RCA RCT6378W2 tablet.
Sorry I had to mangle the link because XDA wont let me link external sources yet.
Click to expand...
Click to collapse
Thanks, that sorted things out.
To make clear, and aid in any other inquiries, I managed to find an ADP connection mode, among other android update features. with the device off, hold volume up while turning the device on. it should boot to an image of an android with an open chest panel and the words, "no command". if you push volume up again it will provide you with options and instructions on how to execute. you can manual update the device with an SDK through USB ADP mode this way. I'm not sure if that makes anything simpler or generates a work around but I hope it helps with future development for this device.
Well got root now we need a recovery...
For some reason when trying to make sure I can send adb commands to my tablet, I am showing no devices connected. I check in device manager and it shows up as Android ADB interface for the tablet. These drivers were installed with the latest version of PDANet. Thoughts or how were you all able to get the drivers fully loaded and working? I have developer options already enabled and USB debugging mode is checked.
Info: RCA RCT6378W2 Tablet
Android 4.2.2
Kernal 3.0.36+
PDANet+ 4.12
Windows 7 64 Bit (I also tried it on my windows 7 32 bit computer)
GloryFreak said:
For some reason when trying to make sure I can send adb commands to my tablet, I am showing no devices connected. I check in device manager and it shows up as Android ADB interface for the tablet. These drivers were installed with the latest version of PDANet. Thoughts or how were you all able to get the drivers fully loaded and working? I have developer options already enabled and USB debugging mode is checked.
Info: RCA RCT6378W2 Tablet
Android 4.2.2
Kernal 3.0.36+
PDANet+ 4.12
Windows 7 64 Bit (I also tried it on my windows 7 32 bit computer)
Click to expand...
Click to collapse
You need to create "adb_usb.ini" in "Users>Username>.android".
Inside "adb_usb.ini" insert "0x2207" and save.
Source: http://blog.fh-kaernten.at/wehr/?p=1182
I need some help rooting this tablet. The point is when im installing the pdanet drivers the screen hangs saying installing drivers.. i finally was able to get the driver installed. but then king root can not connect to it. i checked the device manage and the abd phone is installed. so im not sure what im doing wrong.
scooter29 said:
I need some help rooting this tablet. The point is when im installing the pdanet drivers the screen hangs saying installing drivers.. i finally was able to get the driver installed. but then king root can not connect to it. i checked the device manage and the abd phone is installed. so im not sure what im doing wrong.
Click to expand...
Click to collapse
I had this problem too. make sure you're using the most recent version of pdanet. for whatever reason the older version just hang there and dont work right.
Installed the latest pdanet. It wont install the driver. I checked the device manager and it still shows the device without the driver. not sure what else to try..

Categories

Resources