Database Info

[RESOLVED] Charge root problem - adb drivers

Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.

droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Hi - Would really appreciate your help here. Thanks for the tip on turning debugging off to get to the phone so I could install the USB drivers. Problem now is that ADB just refuses to connect to it. It shows up asa disk drive in Devices, but when I do a kill-server then start-server then adb devices, it doesn't list any devices, and an adb shell just says device not found.
Do I need to reboot Windows, or the phone? Seems unlikely. I can open a window to the phone, but can't get access to install the Gingerbreak and su files I need to root it. Going crazy!
Thanks,
Eric

Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App

Black-Falcon said:
Try rebooting both. Couldn't hurt.
Oh yeah, and if you haven't make sure the phone is back in debug mode.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!

Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App

ClarkSt said:
Well, I'll be a monkey's brother in law. I rebooted both, checked debig mode - and it wasn't on, to my surprise. I've turned it on and off a bunch of times, so...
Anyway, I was able to finally get adb working!!! Yaaaayyy! But now I'm trying to root it, and Superuser doesn't show as an app, and Root Explorer says the f-er isn't rooted. And the Gingersnap Root Utility I've been trying to use, says it's all good to go, but its not.
Gonna try a different method, but if anyone has any ideas, I'm open.
Thanks!!!!
Click to expand...
Click to collapse
Try downloading busybox from the market, or downloading titanium backup and hit the "problems" button when you open it and select get busy box

Black-Falcon said:
Use gingerbreak.
You gotta download superuser from the market
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Tried GingerBreak. No good. "permission denied".

Good idea - I got Busybox installed this way, but still no joy from Gingerbreak.

Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App

DroidXcon said:
Just flash the ED1 odin package and done
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.

ClarkSt said:
If I could flash anything I'd be rooted already, wouldn't I? How do I flash? ROM Manager needs root. Vicious circle.
I've heard that its not possible to root the Charge using current methods since the f-ing update the other day.
Click to expand...
Click to collapse
Check the development thread for the Charge. There's a thread on how to rollback to ED1 with root using Odin.
Edit: Direct link: http://forum.xda-developers.com/showthread.php?t=1085190

droidmark said:
Edit: Kept messing around until my Charge finally mounted itself again as a CD drive; then I opened the "drive" and quickly grabbed the USB driver package, which I installed from the desktop. Now my Charge is recognized and I was able to root using adb with no problem.
The driver package is an 8.1MB .exe file; PM me if you need it emailed to you.
Problem:
I'm trying to root my Charge and can't get adb to see the device. I have Samsung drivers installed and my Fascinate is seen just fine. Not only can I not access the Charge via adb, I can't even connect to USB storage to see the Micro-SD card on it.
Any help much appreciated!
Edit: Thanks to a post by imnuts on another forum, I learned that the Charge has its own drivers which can be installed if it is first connected with USB debugging turned OFF. It mounts as a virtual CD drive, from which the drivers can be installed. This at least allows me to open the SD card on the device. However, when I turn USB debugging back on, my computer STILL can't find the drivers and isn't happy with any directory I point it to.
Click to expand...
Click to collapse
Dude - THANK YOU!!!! I could not get those drivers to install!!!
Please - Stickie!!!

If you want the drivers and don't trust the sources posted anywhere (we're not trustworth ?) you can get them from the phone itself. They are located in the file /system/etc/autorun.iso and you can extract them from it.

i9023 - HELP! "No Boot or Recovery IMG & can't connect via USB

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.

Help please

hello and pardon by the English because I am translating.
I have a HTC S and I wanted one 2 days ago I put a ROM nandroip and everything but I realized and I wipe the entire phone erasing all the ROM and everything I had.
the problem is I can not install a ROM on my phone now because every time I try from windows CMD when you start the installation makes me daemon not running, and sends me error: device not found.
I've tried with another tutorial that you have with the application all in one kit but also not let me access this sd every time I try to enter telling me insert disk into drive E: \.
I can do?
I think it may be by the drivers of PC but not sure I instadao have 5 or 6 drivers and nothing.
an administrator's name is called android MYHTC ADB and other android or something.
I am desperate thank you very much took 2 days doing everything.
thank you very much.
my windows is XP.

Ok, Sorry but im having difficult understanding everything you say, But i think i got the basics.
I would suggest you re download the drivers, Remove HTC Sync if you have it. Move all of your ADB files in to 1 folder so its easier to navigate to when using ADB.
Can you boot the phone into recovery ? I assume you have CWM as you say you installed a nandroid ? If so, Use ADB whilst in recovery, USB Debugging is always enabled when in recovery so you should have no issues finding your device from there.
If all goes well and you find the device, You can then PUSH and INSTALL files / roms from there
Keep us posted

Help a noob with root issue

I'm trying to do the simple one click root found on this forum. When I go through the process using the root debug FS program, I get the message 'adb' is not a recognized internal or external command, operable program, or batch file. The adb program is present in the folder with the rootdebugfs program. I have tried downloading a fresh copy of the folder and re-extracting. I've also tried putting a copy of the adb program in various places on my computer but I have no idea where rootdebugFS searches for it. My phone is connected and the USB drivers are installed. Debugging mode is enabled and unknown sources is enabled.
This is obviously a simple and stupid mistake on my part. Can someone point me in the right direction please? Thanks!

ice456789 said:
I'm trying to do the simple one click root found on this forum. When I go through the process using the root debug FS program, I get the message 'adb' is not a recognized internal or external command, operable program, or batch file. The adb program is present in the folder with the rootdebugfs program. I have tried downloading a fresh copy of the folder and re-extracting. I've also tried putting a copy of the adb program in various places on my computer but I have no idea where rootdebugFS searches for it. My phone is connected and the USB drivers are installed. Debugging mode is enabled and unknown sources is enabled.
This is obviously a simple and stupid mistake on my part. Can someone point me in the right direction please? Thanks!
Click to expand...
Click to collapse
I can't really tell you much about this method as I haven't used it but it is pretty simple to just download a pre rooted stock ROM and flash through Odin. Very simple and can confirm this works.
http://forum.xda-developers.com/showthread.php?t=1984436
sent telepathically

Rootdebugfs exploit only works on ICS TW ROMs.
Sent from my SCH-I535 using xda app-developers app

ADB Offline and no access to bootloader

A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?

andrei1015 said:
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
Click to expand...
Click to collapse
It is Vol-Up + Power for bootloader. And you can't have adb access in bootloader mode. Only fastboot access.

Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S

andrei1015 said:
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
Click to expand...
Click to collapse
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.

_android_ said:
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
Click to expand...
Click to collapse
Yup, I have all of the above.. Still offline >.<

andrei1015 said:
Yup, I have all of the above.. Still offline >.<
Click to expand...
Click to collapse
Do you have the Samsung Galaxy Nexus ADB interface showing in your device manager?
Try uninstall and reload again.

Almost = https://dl.dropbox.com/1/view/xiulpm329s4wxcd/Apps/CloudShot/shot_25022013_192328.png
Still it says offline.
(thank you for trying to help me )

In fastboot mode it looks like this:

just tested at work and it says "device" instead of "offline" which is good I think. The only difference is that at work I installed the SDK long after I got it at home and it has a slightly different folder structure and it also comes with eclipse.

Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?

andrei1015 said:
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
Click to expand...
Click to collapse
Good for you.
Anyway, if you followed post #4 and installed the new SDK Tools, would have saved you a lot of time.