Database Info

Cant Root, comp says superoneclick wont respond

Help, i just got my replacement phone and now superoneclick wont work to root my phone. any suggestions??
also my comp keeps trying to add the Same hardware over and over and if i kept plugging in the phone. does it on the other unit also

Windows PC?
Go into Device Manager and delete the Samsung device.
Reboot your computer
Download the USB drivers and install
Reboot again
plug in phone and see if it detects.

Uncle Irish said:
Windows PC?
Go into Device Manager and delete the Samsung device.
Reboot your computer
Download the USB drivers and install
Reboot again
plug in phone and see if it detects.
Click to expand...
Click to collapse
window xp,
do you have a link to the drivers?

bignate78 said:
window xp,
do you have a link to the drivers?
Click to expand...
Click to collapse
Do you have Samsung Kies?
(That's probably a dumb question now that I think about it..but that's where I got my drivers when I rooted it)

http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT

One of the superoneclick packages has drivers included, that's what I used.

Entropy512 said:
One of the superoneclick packages has drivers included, that's what I used.
Click to expand...
Click to collapse
None of the superoneclicks are working on my end

what exactly is happening?
does the one click program run through the process and fail or does it just fail to run.

infuse drivers
infuse drivers(windows):
http://org.downloadcenter.samsung.c...ATT_SGH-i997_Infuse4G_USB_Drivers_5_2_0_2.zip
You may need to powen off and power on phone for driver installation.
to root :
disable anti-virus
also put your phone in usb debugging mode.
download again superone click or lost1's zip file(there is root script file inside zip)

bignate78 said:
None of the superoneclicks are working on my end
Click to expand...
Click to collapse
That's most likely because you haven't uninstalled and reinstalled your drivers. That's why I suggested a package with known working drivers.

Need Help.... with getting a file onto the phone... (soft brick)

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

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

My phone has no system

I have CM13 on my Mi4C. Yesterday I want to upgrade to new version of CM13. But I did one mistake. I choose wipe all(with system too). So now I don't have any system on phone.
I tryed to push file via adb, but my computer not working with any drivers. I tryed with win10 and win7. The same thing. My computer not recognize phone, so I can't push file with system to phone.
Any idea?
I don't know why drivers not working. I try everything, wathing youtube, read forums....please help.

Solved....

how did you figure it out?