Related
Hi all,
Have a kind of brick at the moment.
Whats working:
Download mode
Recovery e3
The device is booting up, but I did the wrong battery mod for this firmware so it just vibrats and turns on and of.
The PC doesn`t recognize the device, it just sometimes shows up an unkowm device.
I have found this tread http://forum.xda-developers.com/showthread.php?t=777872 and now I have some hope!
I have tried to pick the Kies Driver (16 Shrewsbury) and all the others from Kies and also the google drivers from the SDK. But none from the works.
Someone can point me to the rigth driver, plase
Fortunately I still have my G1
Sorry for my English.
If you have a black screen after booting then try resetting back to factory settings in recovery mode.
Thank you,
I wiped al i could in recovery e3.
The device is booting up, sound is coming, I see even the SGS logo, after No package was found that provides the FACTORY TESTKEYS
I guess it´s becaus I aplyed the wrong battery Mod for my firmware
If your phone can go in download mode try to reflash a rom with odin
I allways extract the latest kies install file to hdd and pick the latest drivers setup package out of it. I NEVER installed kies just to get some drivers
Sent from my GT-I9000 using XDA App
I'm running Serendipity 5.8, Kernel 2.6.32.9 hardcore at speedmod-i897-kl3a-500hz #34
Firmware 2.2.1
Was working great, but all of a sudden it's not being detected by computer. It was previously because I had to connect via USB to get the gtalk app and exchange mail app onto the phone.
I've tried uninstalling drivers, reinstalling, rebooting computer, rebooting phone.. every combination I can think of.
Anybody have any suggestions?
What happens when you plug usb in
Computer doesn't detect it, and phone doesn't do anything except begin charging (tried different USB ports at the back of PC)
If I uninstall the drivers then reinstall, the first time I connect the phone it completes the driver install but then still doesn't detect the phone.
Someone earlier had a similar issue. Really not sure.
Buggar....
Maybe try a different kernel
How can I download a kernel to the phone without using USB?
Easy
Dl astro file manager from market
Go to preferences, select download from browser.
Find kernel to flash. Dl on phone. I dl everything directly to my phone. Kernels, roms, etc
Thanks. You got a recommended kernel?
Mind you this is a bit of a shot in the dark cause I have not had that problem with hardcores but try this
http://forum.xda-developers.com/attachment.php?attachmentid=516546&d=1297588801
Dill pickle kernel. Voodoo based. 2.2.1
Well. That was the weirdest thing.
DLed, opened with ROM Manager, went through the reboot to install procedure, it got to recovery and gave me some weird installation aborted messages... wouldn't let me reboot from the menu - had to pull the battery. restarted and my phone was talking to me at the Samsung screen... took a couple of minutes.. booted up and USB detected right away, and DIllPIckle Kernel is on... so I dunno if it half worked and fixed the issue, or if it will get funky in the gfuture, but for right now i'ts fixed!
Thanks.
Do not use rom manager on custom roms. Get into recovery install zip from sd.
Voices was google
Happy to hear it worked
I can't use cwm with some custom roms and i have to do the battery pull to get back.
i had the same problem running serendipity 5.8... phone was charging but comp didnt detect it..tried for 2 days every possible way but no luck. odin didnt recognized it or adb. pretty much its hardware issue...rogers is sending me replacement
sorry
ok, I hate to ask, but honestly I've searched all day long and can't find a direct answer. I installed CM7. I don't like it, my battery drains like crazy with it. I can get into Recovery and Download mode. No problem. I've read you can flash CWM flashable ROMS that are 2.2 because CM7 uses 2.2 bootloaders. Well. I can't find any. I just want to go back to stock 2.2 with my root and existz kernel and voodoolagfix. Is there a CWM flashable stock rom??? if not, how the heck do I get odin to recognize my phone. I'm sitting in download mode right now. I have used it in the past, only flashed 1 other time. with CM7 installed do i need to install NEXUS S drivers for odin to recognize my phone? I'm just real fed up with how hard it has been to flash over CM7. please someone at least give me 1 answer.
You need to Odin Flash a stock ROM. Cwm won't change your file system like it needs to be changed. If you want 2.2, just Odin1 click to jf6, then use Kies mini to upgrade to kb1. If you prefer Heimdall, there's a thread with stock roms somewhere by ubershaximus.
Try nexus s and Samsung drivers. One of them should get your computer to recognize your phone.
ok so ODIN it is. My computer recognizes my phone because when I plug it in with Debugging on it wants to search for Captivate Drivers. which I already installed, so I'm not sure why it's still searching for them. is ODIN3 the same as ODIN or what? I have I897UCJF6-final-OCD-REV0 which I thought I had used before. This whole CM7 thing has been a irritating, the battery life is just awful on my phone with it.
Yes, that will work. It is actually Odin3 v 1.x. Its usually just shortened to Odin.
so I had to install some Gadget Serial drivers? and some other drivers.....
I am really pissed CM makes it so hard to flash back over. I have USB plugged into computer, open odin , HOLD down both volume keys and plug in USB and I get into download super quick. ODIN won't recognize my phone. even have the ODIN where you need to re-partition and add pit files. still, nothing.
I'm really fed up with this.
Geez, it's obvious you didn't read very well before you flashed CM7. It is not hard at all to flash back to stock. You need the Nexus S drivers for your computer to recognize your phone. Simple solution. Just read the FAQ and the CM7 thread and you wouldn't be so mad. It's not cm7 fault dude.
Sent from my SGH-I897 using XDA App
Well, from what I could find, I needed android sdk to install nexus so drivers, correct me if I'm wrong. Well to install sdk I needed java jdk so I installed that, then installed android sdk which took forever. Read how to install the nexus so drivers. So I plugged in my phone selected the location. It installed something, then it still kept saying install driver for gadget serial wtf ever that is. So I install that, then finally in all set and I plug my phone in and it says Unknown Device. So yes I do read. I however have only flashed one other time, back in February, so I'm a bit rusty. What is also great is in followed cm instructions on flashing to a tee and they didn't work, so I figured it out myself.
Sent from my SGH-I897 using XDA App
So I uninstalled KIES, KIES MINI, my Captivate Driver and the Android ADB Composite Device Driver (nexus S driver i believe) I rebooted computer. When I attached phone, it wanted a captivate driver, but I was told to install Nexus S, so I went into AndroidSDK picked out the driver and everything was hunky dory. When I plug my phone in, it no longer wants a device driver. HOWEVER, when I plug it in, in Download Mode, that's when it says Unknown Device. What the heck is going on!
I updated my rooted Captivate from Froyo (official build) to Gingerbread 2.3.5 (official build) today, and the process seemed to go smoothly until the phone needed to reboot at the end of the update. I found that my phone was showing the At&t animation and then going to the Galaxy S animation and then repeating the process instead of booting properly. I do not know why because I unrooted my phone using Super One Click before I updated. I am freaking out, what should I do now?
how did you update? what method? official stock? or official plus a CWM kernel?
there was no point of un-rooting. flashing stock will un-root a captivate. flashing a custom rom, it will be rooted already...
when in doubt, flash to stock again. but make sure its correct stock.. once again what method and where did you get it?
TRusselo said:
how did you update? what method? official stock? or official plus a CWM kernel?
there was no point of un-rooting. flashing stock will un-root a captivate. flashing a custom rom, it will be rooted already...
when in doubt, flash to stock again. but make sure its correct stock.. once again what method and where did you get it?
Click to expand...
Click to collapse
I updated (from official Froyo stock) using Kies Mini to the Samsung official stock (Gingerbread 2.3.5). I have never flashed before. How can I do this and how can I find the correct stock to flash to?
As a note to anyone who might find themselves stuck in the same predicament as I was in, the Odin3 One Click Downloader program by "designgears" is very useful. Using the button combinations I found here: http://forum.xda-developers.com/showthread.php?t=1351224 I was able to get my phone into Download Mode. I then used the Odin3 program (http://forum.xda-developers.com/showthread.php?t=731989) to painlessly flash my phone to the stock 2.1 rom. This was just a matter of connecting my phone to my computer, running Odin3, and clicking "start". After my phone rebooted, using Kies Mini, I updated to 2.2 Froyo. I waited for my phone to reboot, disconnected it from the computer, reconnected it to the computer and then (using Kies Mini again) updated my phone to Gingerbread 2.3.5 (which, so far, I am very happy with).
WARNING: Make sure you wait before Odin3 is completely done running!! When I was running the program I thought it was finished and almost unplugged my phone prematurely (I am fairly sure this would have ruined my phone, but do not quote me on this). If in doubt, just wait a few minutes.
captivateman111 said:
Will this Odin3 One Click Downloader by Designgears fix my problem?
Link: http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
Just flash a KK4 rom or leaked KK4 in dev section. Should fix it. BTW never use kies....its ebil....
I'm having a similar problem, with my Captivate stuck in a loop at the AT&T splash screen. However, I can't access Recovery mode or get to download mode - I've tried every 3-button combo variant I've found on the forums, as well as taking out the battery, holding the volume +/- keys, plugging into USB & re-inserting the battery.
Would it be safe to assume that the only way I'm going to be able to get into download mode now is with a USB jig?
EDIT: Prior to this, I was running Froyo 2.2 - went to flash the ICS for Captivate ROM - it didn't work, but I could still get into recovery mode. So I simply booted into recovery, did a factory reset and clicked the "reboot" option on CWM. That's when it started boot looping.
Okay, so I got a USB jig and put it into download mode. Plugged it into a free rear USB port and Vista started automatically installing drivers for it, so I ran the Heimdall One-Click Stock. It saw my device as connected so I went ahead and clicked "flash", and I got an error msg saying the device wasn't found. Prompted me to install drivers, so I followed the prompts and attempted to install the drivers from the zadig program.
The first time, the install timed out after 5 minutes. Rebooted my PC and ran the Heimdall One-Click utility again, and this time after a few seconds I got a prompt saying that the drivers have been successfully installed. However, in the taskbar I got a pop-up saying that driver installation failed.
Now, every time I plug into a USB port I get an error of "USB device not recognized", and when I run the Heimdall One-Click util it says my device isn't connected. I've tried it on two seperate PCs (both running Vista), on multiple USB ports and still get the same error.
Should I just uninstall all the Samsung drivers and reinstall?
EDIT FOR FUTURE REFERENCE: Hi! If you're reading this, you may've had the same problem. What worked for me was uninstalling Samsung Kies, uninstalling the Samsung mobile phone drivers, going into regedit and deleting all SAMSUNG registry keys. After that, reboot, put your device into download mode, plug into your USB Port, run the Heimdall One-Click package of your choice and just wait!
Malheurit said:
Okay, so I got a USB jig and put it into download mode. Plugged it into a free rear USB port and Vista started automatically installing drivers for it, so I ran the Heimdall One-Click Stock. It saw my device as connected so I went ahead and clicked "flash", and I got an error msg saying the device wasn't found. Prompted me to install drivers, so I followed the prompts and attempted to install the drivers from the zadig program.
The first time, the install timed out after 5 minutes. Rebooted my PC and ran the Heimdall One-Click utility again, and this time after a few seconds I got a prompt saying that the drivers have been successfully installed. However, in the taskbar I got a pop-up saying that driver installation failed.
Now, every time I plug into a USB port I get an error of "USB device not recognized", and when I run the Heimdall One-Click util it says my device isn't connected. I've tried it on two seperate PCs (both running Vista), on multiple USB ports and still get the same error.
Should I just uninstall all the Samsung drivers and reinstall?
Click to expand...
Click to collapse
You can't go wrong by uninstalling both sets of drivers (Samsung and Heimdall), rebooting, and reinstalling just the Heimdall Drivers. Heimdall also only installs drivers for one USB port, so trying different ports is key (I know you already did, and you're on the right track).
Here's a good Heimdall thread if you need it: http://forum.xda-developers.com/showthread.php?t=1113195
Download jig will save you
Sent from my SPH-D710 using XDA App
I had the exact same problem....Kies info said to wait til I got to idle screen before unplugging usb. No dice. Infinte loop. Got into recovery and did a factory reset and BINGO...Gingerbread...yum!
ok so i used kies to upgrade to gb then used odin to flash a rom problem os i guess it was t mobile rom so when booting up i see a att screen then gets stuck on galaxys 4g t mobile screen still have cmw in red but cannot read anything or mount tried flashing from cmw no luck there tried one click to stock no luck so any help would be awesome thanks
noobin said:
ok so i used kies to upgrade to gb then used odin to flash a rom problem os i guess it was t mobile rom so when booting up i see a att screen then gets stuck on galaxys 4g t mobile screen still have cmw in red but cannot read anything or mount tried flashing from cmw no luck there tried one click to stock no luck so any help would be awesome thanks
Click to expand...
Click to collapse
Wait you have a Captivate running a Tmo 4g variant rom?
Sent from my ICS powered Captivate using Tapatalk
How?
russhayden said:
I had the exact same problem....Kies info said to wait til I got to idle screen before unplugging usb. No dice. Infinte loop. Got into recovery and did a factory reset and BINGO...Gingerbread...yum!
Click to expand...
Click to collapse
I'm in the boot loop too. How did you get into recovery?
^
Hold volume + & - and power button until phone boots and u see the at&t screen Then release buttons.
Sent from my SAMSUNG-SGH-I777 using xda premium
I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below
k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!
KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help