unroot, no usb - Galaxy S I9000 Q&A, Help & Troubleshooting

My Galaxy S i9000 (running 2.3.3) won't connect to my computers via USB. Is there a way I can unroot (and get rid of a custom kernel) it so that I can send it for USB repair?
at some point i was able to get USB working long enough that I installed XWJVB and get it rooted with a custom kernel.. but the blasted thing won't connect to usb any more. either it doesn't react to usb connection, or it says usb device not recognized..

Related

[Q] (Q) Hardbricked phone and usb doesnt work

It all started when my phone didnt connect to the pc with my own microusb cable anymore. After lots of reinstalling drivers i tried another usb port, now the phone did connect. In a rush i started up odin to flash standard firmware so i could get my warranty for the usb failure. Then during the flash the phone lost connection again and hardbricked. I can only get it to download mode but the phone has the usb problems mentioned before again, i cant connect to odin/kies/pc. all pc's told me that the usb driver could not be installed
try removing all usb drivers with usbdeview, make sure that KIES aint running in the background, boot phone into downloadmode, connect is and as soon as you'll see the yellow com-port sign; hit start (with the proper .tar files at pda/phone/csc).
only one way to find out =/
Thanks for the help but the problem is that the yellow com-port sign wont come because the device isn't recognized.
You have download mode but no USB .
Remove existing KIES and all USB drivers reboot reinstall KIES and try .
Not work try on a different PC .
But unless you have fixed the initial error you are wasting your time .
Initial Error you said >>>It all started when my phone didnt connect to the pc with my own >>>>> microusb cable <<<<<<<<<<<<< anymore
jje
Tried another cable and another computer, still no connection. I think probably an internal failure in the phones motherboard?

[Q] SGS doesn't recognizing by USB

3 days ago i flashed my sgs with Ultibread v1.3
Today i decided to flash back 2.2.1 firmware, but all of my 3 computers (10 usb ports) couldn't recognize my phone.
Try to search any solve of this problem, but no one tutorial has not helped.
What did i do?
uninstall all of samsung usb drivers
clean register of all garbage with "samsung"
reboot my computer 3 times
download latest samsung usb drivers v1.3.2000.0 (25.jan.2011)
get out battery for 15 minutes
try plug in other usb port
take computer, wich never connected my phone, install latest drivers (see previous step) and connect sgs to him...
In all cases, the result is one: Unknown USB Device.
System can load and "debug mode" switched on.
Please, help me...
My PC forgets my SGS on a regular basis. When I plug the USB into my phone it is usually a good 50/50 if it recognizes it.
I have found the best way to deal with it is to reboot the phone while it is still connected by USB to the PC. When the phone comes back up with the USB connected, the PC always discovers it right away.
Also avoid connected through a USB hub if possible, that always gives me trouble.
Omg! Solved.
Ultibread v1.3 and, maybe, 1.4 got issue with check in debug usb mode.
And without this check - windows can't recognize phone.
Solution:
turn on debug usb mode in settings, then put out battery when phone is ON.
Then you can get in download mode.
Case closed

Any Other Way To Bring My Phone Back To Life

My SGS isn't bricked. But lately after I flashed a deodexed 2.3.3 ROM, I have a hard time connecting my USB (USB not recognized). This afternoon, my phone jammed and won't boot (Stuck in Samsung Galaxy S I9000 Screen). I can't enter the recovery mode either for no reason (used to be able to).
Now I can't flash a stock ROM because my USB isn't recognized and recovery mode is unaccessible too. Trying to install the drivers for the USB now. Anyway as it's installing, any other ways to bring my phone back?
Flash a rom through odin. You could try darky's 9.2 ressurection edition.
The problem now is I could not flash with Odin because my USB isn't working
smiles.smiley said:
My SGS isn't bricked. But lately after I flashed a deodexed 2.3.3 ROM, I have a hard time connecting my USB (USB not recognized). This afternoon, my phone jammed and won't boot (Stuck in Samsung Galaxy S I9000 Screen). I can't enter the recovery mode either for no reason (used to be able to).
Now I can't flash a stock ROM because my USB isn't recognized and recovery mode is unaccessible too. Trying to install the drivers for the USB now. Anyway as it's installing, any other ways to bring my phone back?
Click to expand...
Click to collapse
seriously try using other computer or laptop.. install the required drivers on your friends computer and then try to flash a different rom via odin
tried that. on different comp. same problem. USB not recognized with the drivers installed
I guess this is the problem. When I can't boot my phone, I did a backup restore. Maybe something is messed up and drivers don't recognize my phone as Samsung Galaxy S anymore. Anyway to force it to recognize?
http://www.nirsoft.net/utils/usb_devices_view.html
REMOVE USB DEVICES .
USB connection must be a motherboard connector .
jje
I'm sorry for being a noob. I've downloaded USBDeview. I should remove USB devices and? What do i do after that?
My USB device is Not Recognized. will it show on USBDeview?
Shows old usb drivers delete the lot on that port .
jje
Deleted everything. Plugged in my SGS in Downloading Mode. Still don't get anything.
smiles.smiley said:
Deleted everything. Plugged in my SGS in Downloading Mode. Still don't get anything.
Click to expand...
Click to collapse
if you can go into download mode then you surely can get it flashed with odin ..
try downloading the drivers again and then installing again and then try again....
... if everything fails then you should send it to the service center
Try unplugging and plugging the usb repeatedly. I've had this happen before, and I was able to get the phone recognised by doing this.

Captivate i896 - Absolutely unable get Windows to recognize it

I'm trying to root my friend's Rogers Captivate i896 using Odin but can't get the computer to recognize the device. I tried installing the drivers mentioned throughout other threads. I've tried uninstalling Keis, uninstalling the drivers, connecting to different USB ports, tried several computers/laptops running XP & Win7, tried USB desbugging on/off, tried "mass storage/kies firmware update/ask when connected."
He got the phone with Eclair and when it became available he then updated to Froyo through Keis. Ever since that update he hasn't been able to get any computer to recognize the phone. When I root my sgs i9000 I did have an issue with "mtp application error" that ended up being a missing driver but with this i896 model I've tried several different drivers and still nothing.
I can't root if the Odin can't 'see' it, or is there another way? Any others out there that have had success? Any help is much appreciated.
First of all, you don't use Odin to root it. Odin won't see it when the phone is on; only in download mode. You will just need SuperOneClick in order to root.
It is also unclear whether you are trying to say that Windows won't recognize it, or just Odin
Sent from my ICS Samsung Captivate
Windows in general won't recognize it. Even when I connect it to a mac, I hit the 'connect storage to pc" and it says it's connected but the internal/external hd do not mount. I used odin to root and put a rom (darky10.2) on my sgsi9000 and used the same instructions because the same steps also work for the captivate. I thought I read somewhere that I use Odin to go from Froyo to Gingerbread?
I'll looking at a SuperOneClick youtube vid & it says to connect the device to the pc & run superOneClick on the pc but how will that work if the issue is that the pc's can't detect the phone in the first place? btw thanks for the help.
retrolab said:
Windows in general won't recognize it. Even when I connect it to a mac, I hit the 'connect storage to pc" and it says it's connected but the internal/external hd do not mount. I used odin to root and put a rom (darky10.2) on my sgsi9000 and used the same instructions because the same steps also work for the captivate. I thought I read somewhere that I use Odin to go from Froyo to Gingerbread?
I'll looking at a SuperOneClick youtube vid & it says to connect the device to the pc & run superOneClick on the pc but how will that work if the issue is that the pc's can't detect the phone in the first place? btw thanks for the help.
Click to expand...
Click to collapse
Sure, you can use Odin/Heimdall to flash any stock firmware, but it's not going to help you if the phone can't be recognized. It sounds like something is physically malfunctioning. Are you using the USB cable that came with the phone? I suspect that either the cable or USB port is malfunctioning.
I thought the same thing but I am using the cable that came with the phone and I tried different ports. I also tried different laptops running different versions of windows. So strange. Ah well thanks for the help.
I had a similar problem with my captivate before I changed the ROM, but only on one particularly stubborn computer. I ended up having to go through this process to get my phone to connect:
- Uninstall the USB driver
- Reboot computer
- Connect phone with debugging off
- Install USB driver
- Reboot computer
- Connect phone with debugging on.
After that, it worked just fine in whatever mode I wanted.
You may have already tried that process, but if not I hope it helps.

Root on Note5 w/o usb port connection

I'm using a Note5 (SM-N920G) with a USB port ~almost~ dead... Can't charge on fast mode, can't connect on PC and some ****s...
My question: Can I root w/o getting my Note5 connected to PC? How I do that?
Not possible, to use Magisk you first need to change the recovery; the same for CF Auto Root. Odin is needed in both methods.
Can you flash a stock rom via stock recovery?
No. Use Odin. I'm sure it'll work. Use a different usb port or a different device. Ensure it's usb 3. And also fast charge only works on the dedicated charger, unless there's some weird kernel bug.

Categories

Resources