Hello everyone and thanks in advance for anyone replying to my dumb question.
Today I was preparing to use the Aroma Toolkit to restore my phone to a basic stock. I placed it in a folder called ".rom" on the internal sdcard so it would appear at the top. (can you believe it?) I have CWM Red and it doesn't see ".rom" as it is now hidden. (I guess) Unfortunately, I already wiped AND formatted "system" so I can't boot the phone up to change the folder to something more sensible. I cannot restore from Odin OR Heimdall because my phone won't show up on ANY PC and it only shows "Unknown USB Device." I've been up and down with that one too. Also, I tried to put the toolkit on the external sdcard both as is and as update.zip but it says there are no files. I think my only way(s) out of this would be to Odin or Heimdall, if I can get either working again, or if there is a way to get the CWM Red to see that hidden ".rom" folder.
ANY help at all would be greatly appreciated.
Thanks for reading this.
folders and files that begin with a dot are hidden in linux systems like android. you are seeing an unknown device because you dont have samsung drivers installed. you should be able to go into mounts and storage and select usb mass storage or something like that and it will mount as a mass storage device where you can rename the file in windows where that doesnt show as a hidden file.
if you wiped system, if you turn off your device, you might not be able to get back into recovery and youll have to use odin or heimdall. you can download the samsung drivers from http://d-h.st/xEG and when you are in recovery mode, go to device manager and select from the list of device and choose samsung composite device or something like that i dont remember.
next time you want a folder to show at the top of the list, i think you can start it with an underscore. i could be wrong about that though. you can try it out and see.
I don't recall if red CWM has the mount as usb storage option. If not...
Next step is getting the drivers on your PC. Easiest option from there is Odin or Heimdall - unless you want to download the android SDK and use adb shell to rename the directory.
Underscore should work for sorting...
fwiw I use exclamation points.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
well, if youre not going to download mode to run odin, and you cant do usb mass storage in red cwm, and you want to do it from recovery, you need to choose samsung adb device in device manager. then you need adb and can do adb shell and run "mv /sdcard/.rom /sdcard/_rom"
mrpectate said:
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
Click to expand...
Click to collapse
sd_ext in red recovery does not refer to the external sd card (even though you would think it does from the name)
For compatible drivers, remove all Samsung phone related drivers from your system and install the first driver package located here (not the mini-kies one):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
Some things that may help:
http://forum.xda-developers.com/showthread.php?t=1982306&page=2
Also, turn off auto driver install in Windows 7 - could be your PC is deciding what is best for you before you can install working drivers:
Go to Control Panel > System > Advanced System Settings > Hardware > Device Installation Settings > "No / Never"
Then install the driver, then connect your phone. Once the driver and devices are fully installed you can change the above setting back to what it was or to "No / Install" (that's where I usually leave it)
Good luck
Well I sincerely appreciate all the help from you guys, and Zen Arcade, thanks for the toolkit that brought me back from disaster quite a few times. I tried all of your suggestions, but it seems like I might have a hardware failure which occured before all this. I was able to connect to USB fine and out of nowhere it just wouldn't anymore. That was OK. I still rom-hopped along with straight to phone rom aquisition, but then I made a mistake. One I have learned from. I'm not able to get the phone to show up AT ALL. I even tried a clean install of WinXP then the drivers from Zen's post, and Nicky's Win7 laptop. I also tried several versions of Linux. Only Mint's Gparted could see it as /sdb/ with a corrupted partition. I even gave Haiku's Drive Probe a shot. Jack of Clubs, I tried the SDK shell but it just scans and sees nothing. I just think that the USB thing is roadblocking any hope of saving this heap. Recovery is there, download mode is there, but the connection required to utilize either of those is gone.
Again, I truly appreciate the help.
Well I've been trying to get CWM to see the Infuse Toolkit (and various roms) on external_sd but it keeps saying:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard
I've tried 4 different microSD's formatted as FAT, FAT32, and I used SDFormatter (I saw someone recommend that somewhere). I really see this as the very last ember of hope for this phone before I let it go.
Any ideas?
BTW, my CWM is v2.5.1.3 - Voodoo lagfix
Thanks again and in advance.
Infuse GB recovery menu will not see external SD card.
If you can get adb working - connection to your PC - you have some options. From adb there are commands that will allow copying files from PC to phone ... also from external to internal sd card depending on which kernel you are running. You could also rename your hidden folder too.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks again for your continued help Zen. I just can't get it recognized (in a constructive way) by anything. I tried Santoku linux today and nothing. I've just been beating my head with this thing. Well here it is: CWM is accessible, as is download mode, and it charges fine, but no PC connection. When it was given to me, the glass was cracked, but it always worked fine for me. It's in a Ballistic case. If your interested in it, I'll be happy to send it to you, even if it's just for parts. I loved this phone, and had a lot of fun with it. (thanks to this community and all of its' contributors) I think it's time to move on.
I'm gonna start looking at a phone with a good selection of custom roms cuz I just love flashin' 'em
Let me know if your interested in this phone Zen.
Related
This is a a new one from what I have seen, after several random restarts I flashed back to stock and was able to install the jh7 update. I rooted with z4root. I wanted to enable sideloading and used a guide that allowed you to change the settings.db file in sqlite and reinstall to the settings folder under dbdata. The instructions were to delete the file and so I did, but to my horror I was not able to past the new file into the directory using root explorer. Knowing that something bad was going to happend I restarted anyway and low and behold, the phone no longer boots past the S screen. The screen goes black and the buttons on the bottom turn on but thats all you get. I tried the hold volume buttons and plug in. I also tried hold volume buttons and power. I tried to make my own jig using three 100 ohm resistors as shown on youtubne and nothing gets me into download or recover modes. I have ordered a jig from a guy over and androidforums hoping for user error in my jig attempt. Anyone have any suggestions, my build is 1009 rev .04. My computer does recognize the the partitions when I plug it, but of course I can not mount. Is there a way in either windows or linux to force a mount, and to get into the file system to restore the back up I made. Without this settings.db file will I even be able to enter recovery or download mode? Thanks for any help you can give.
hd779 said:
This is a a new one from what I have seen, after several random restarts I flashed back to stock and was able to install the jh7 update. I rooted with z4root. I wanted to enable sideloading and used a guide that allowed you to change the settings.db file in sqlite and reinstall to the settings folder under dbdata. The instructions were to delete the file and so I did, but to my horror I was not able to past the new file into the directory using root explorer. Knowing that something bad was going to happend I restarted anyway and low and behold, the phone no longer boots past the S screen. The screen goes black and the buttons on the bottom turn on but thats all you get. I tried the hold volume buttons and plug in. I also tried hold volume buttons and power. I tried to make my own jig using three 100 ohm resistors as shown on youtubne and nothing gets me into download or recover modes. I have ordered a jig from a guy over and androidforums hoping for user error in my jig attempt. Anyone have any suggestions, my build is 1009 rev .04. My computer does recognize the the partitions when I plug it, but of course I can not mount. Is there a way in either windows or linux to force a mount, and to get into the file system to restore the back up I made. Without this settings.db file will I even be able to enter recovery or download mode? Thanks for any help you can give.
Click to expand...
Click to collapse
Can't you get into download mode through vol up + vol down + usb cord? That's used by sbl.bin, which shouldn't be affected.
Sent from my SAMSUNG-SGH-I896 using XDA App
A) this is not a brick, your phone still powers on
B) if you were rooting, you should have enabled USB debugging before attempting to do so, so when you turn your phone on, plug the USB in and use adb from the android sdk to get into download mode. "adb reboot download"
Kaik541 said:
A) this is not a brick, your phone still powers on
B) if you were rooting, you should have enabled USB debugging before attempting to do so, so when you turn your phone on, plug the USB in and use adb from the android sdk to get into download mode. "adb reboot download"
Click to expand...
Click to collapse
Might as well be a brick. The root went fine, everything was good till I deleting the settings file. What I am hoping for is a way to force mount the internal memory if possible and cut and paste the back up copy in.
you just need to go through the various methods to get into download mode.
pull battery -> Pull sim card -> Insert battery -> hold power up and down while plugging in the USB with Odin already open
adb should work in recovery and likely where the phone is hanging during boot as well.
Sent from my ADR6300 using XDA App
hd779 said:
Might as well be a brick. The root went fine, everything was good till I deleting the settings file. What I am hoping for is a way to force mount the internal memory if possible and cut and paste the back up copy in.
Click to expand...
Click to collapse
if you have the setting.db file saved on your computer you can do an adb push.
I am not really sure of adb, I downloaded the android development kit, and it told me I needed the Java SDK, so I downloaded and installed that. But the development kit tells me Java is not installed.
hd779 said:
I am not really sure of adb, I downloaded the android development kit, and it told me I needed the Java SDK, so I downloaded and installed that. But the development kit tells me Java is not installed.
Click to expand...
Click to collapse
I am assuming that you are on a 64bit windows.
the android sdk installer is looking for the 32bit version of java, so go download and install the java jdk/sdk for 32bit windows.
I am not able to put my phone into debug mode will adb still work?
Also do you have to be in debug mode for Odin if so then I guess I am really screwed.
You do not need to have it in debug for odin and adb is enabled in recovery regardless of debug setting.
Well that is very good to hear, now if I could only get into recovery mode.
Well good news, I followed this dude's tutorial and am back. Thanks for all the replies guys.
http://www.youtube.com/watch?v=Rdn5GoRjhn0
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.
So, just made a mistake, moved the wrong SystemUI.apk over trying to deal with the 3 dots issue and now it doesn't boot, is there any way for me to get the stock files back on??
ADB isn't working in CWM recovery, it doesn't have an SD slot so even i have made a flashable fix, i can't push it to the phone to fix it...
I have tried fastboot the system.img back but says its too large...
Im out of ideas... Thanks in advance for any help!
If you can at least mount USB in CWM, you could make a zip file that simply pushes the correct SystemUI.apk over. Just have to package it correctly and flash it.
What about flashing the stock RUU?
I can mount but nothing happens... I hear the USB connect sound on the computer but can't access mass storage at all, if I click mount USB storage it just says Unable to open ums lunfile
I think I may have to try the stock RUU then, but that will be back to square one after all I have done these past two days.. was hoping it wouldn't come to that...
Is that really all that is left to do?
zytho said:
I can mount but nothing happens... I hear the USB connect sound on the computer but can't access mass storage at all, if I click mount USB storage it just says Unable to open ums lunfile
I think I may have to try the stock RUU then, but that will be back to square one after all I have done these past two days.. was hoping it wouldn't come to that...
Is that really all that is left to do?
Click to expand...
Click to collapse
If USB won't mount....yup. Next time make a nandroid backup after you get everything setup!
I posted this in the cwm thread but figured you to be looking here first...
You might need the naked drivers, I had to do that with my prime... Go here http://forum.xda-developers.com/showthread.php?t=1426502
[ADB/FB/APX Driver] Universal Naked Driver Beta 0.6.1 (250+ Devices, HTC Added)
These are the naked drivers I had to install in order to have cwm recovery ADB detect my device... Hope this helps
Sent from my ROOTED HTC One X using xda premium
I know... backup will be done next time
just trying out the naked drivers... it doesn't seem to want to install or use them though...right click install on the inf doesn't have any luck, neither does update driver with Have Disk... even dropped them into the inf folder..
Am I doing something wrong?
Go to device manager you should see android emulator... Right click update driver... Use your own files for update (browse)...browse to the folder where the naked drivers are... Should do the rest on its own... Once drivers are in it should say something other than android emulator...mine said nexus S but that's irrelevant... Hope this helps
Sent from my ROOTED HTC One X using xda premium
Hi guys,
I just have received a i9023 from a friend to repair. I put fastboot on and the device is unlocked, then I copied over Matr1x kernel via USB to the SD card and flashed CMW to recovery.
From here things went bad.
When trying to update the kernel to Matr1x, it showed that the file wasn't on the SD card anymore, so I tried to mount the SD card to copy it back, but it my computer wouldn't see it. Since then I tried many things to get the USB working - updating drivers etc... after awhile I decided to format SD card, which didn't help, so I formatted all the partitions on the phone.
Now, every time the phone comes on, it boots straight to fastboot, but also the PC will still not recognise the phone via USB.
I've tried getting into Download mode and using ODIN to flash a new kernel & ROM, but this wont work without USB working.
Can anyone help?
PS. I have read many other guides and posts, but nothing has helped.
Many thanks.
*Bump*
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
bedalus said:
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
Click to expand...
Click to collapse
Yes, I tried to mount as USB Storage in the Recovery Menu - didn't work, but now, I've only got fastboot - Booting up the phone normally jumps straight to fastboot, trying to boot into recovery doesn't work (just the fallen over Android pic with the red "!" on his chest).
I'm using Windows 7 and computer will not recognise the phone at all (it was working before this & the MicroUSB port is not damaged).
My GT-i9100 works perfectly via USB.
Piemo said:
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
Click to expand...
Click to collapse
If I can get it to connect to my PC so I can throw a stock ROM on there via ODIN I should be right (Pretty sure SAMFIRMWARE has some).
I've found often that the sdcard only gets mounted when you "choose zip from sdcard" in recovery. I panicked once with a galaxy s when I had forgot to put any rom on the sdcard and couldn't mount it subsequently. Ended up using heimdall with success. Also make sure you have latest version of fastboot, from platform tools 4.0.3.
Yeah, try Odin
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
twadda218 said:
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
Click to expand...
Click to collapse
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Can you try Ubuntu? Any luck with Odin?
KLoNe1 said:
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Click to expand...
Click to collapse
Does it say unknown device in device manager?
Sent from my ice cream powered Nexus S
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
KLoNe1 said:
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
Click to expand...
Click to collapse
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
DarkhShadow said:
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes, I did - it said that this inf (driver) doesn't contain information about the device in question.
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Many thanks for all your help everyone; unfortunately I still have yet to figure out how to get this working. Please keep throwing out your ideas
bedalus said:
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Click to expand...
Click to collapse
I gave this a go as it sounded like a great idea, but unfortunately it still isn't working.
I ended up deleting the drivers it was installing which wouldn't work & now it will only show up as 2x Unknown device under 'Portable Devices' heading.
I think you should try installing ubuntu, and the android sdk so you have access to fastboot again.
Hello, I rooted my tablet for 1 year ago and had been using Revolution HD ever since. This evening I decided to upgrade to something more new and came across goomanager so I downloaded the Cyanmode cm-9.1.0tf101 via the app. I flashed with TWRP (easyflasher) v.2.3.1.1. The issues I am having now are:
1. The loading screen (the guy with spinning circle behind him) keeps appear randomly and constantly and resets everything each time (wifi etc)
2. I cannot access the folders (the file manager is gone). I cannot access to the folders even when the tablet is connected to PC, the folders show emptiness.
3. The TWRP I am using don't allow me to flash anything from external usb. Therefor I dont know how to install another rom or how to fix these problems
EDIT: I have tried to flash the stock version 9.2.1.27 with easyflasher but it failed. The problem is that I cannot enter apx mode. I installed Universal Naked Driver 0.7 but everytime I try to enter apx mode, it resets and says "drivers could not be installed".
EDIT2: I was able to install CWM recovery v.3 with Brk.root.toolkit.v7.1 but can't access sdcard to flash roms, it says "cant mount sdcard, unable to open ums lunfile
Where do I go from here to get anything working?
PLS help
Regards,
Anh
woodendick said:
Hello, I rooted my tablet for 1 year ago and had been using Revolution HD ever since. This evening I decided to upgrade to something more new and came across goomanager so I downloaded the Cyanmode cm-9.1.0tf101 via the app. I flashed with TWRP (easyflasher) v.2.3.1.1. The issues I am having now are:
1. The loading screen (the guy with spinning circle behind him) keeps appear randomly and constantly and resets everything each time (wifi etc)
2. I cannot access the folders (the file manager is gone). I cannot access to the folders even when the tablet is connected to PC, the folders show emptiness.
3. The TWRP I am using don't allow me to flash anything from external usb. Therefor I dont know how to install another rom or how to fix these problems
EDIT: I have tried to flash the stock version 9.2.1.27 with easyflasher but it failed. The problem is that I cannot enter apx mode. I installed Universal Naked Driver 0.7 but everytime I try to enter apx mode, it resets and says "drivers could not be installed".
EDIT2: I was able to install CWM recovery v.3 with Brk.root.toolkit.v7.1 but can't access sdcard to flash roms, it says "cant mount sdcard, unable to open ums lunfile
Where do I go from here to get anything working?
PLS help
Regards,
Anh
Click to expand...
Click to collapse
Remove all Asus drivers installed on your laptop and restart. Now try installing universal naked driver, if your your laptop still says "drivers could not be installed" then unzip the driver and place it in a folder and then go to device manager and look for "unknown devices"... select it and update driver manually by selecting the unzipped folder.
Sent from my Transformer using xda app-developers app
I had the same problem with drivers. The naked universal didn't work, nor any other driver I found on xda.
I uninstalled them and when reinstalling let Windows choose driver from whole c:. After a few minutes a driver was installed.