I have samsung galaxy S GT-I9000 and Android 2.1.
I was trying to install CMD 10 and as a preparation to install CMD recovery I flashed Semaphore_2.7.4 with ODIN.
Since then, my phone has been going in reboot loop as soon as samsung logo comes. I am able to access Download mode but not the recovery mode (shows error "Forced upload by Key Pressing"). I've tried flashing using Heimdall but it gives me libusb error (tried everything from uninstalling samsung drivers, changing usb port, changing usb chord)
How can I install CMD 9/10 despite the fact that I only can use download mode?
Can anyone help me here?
Related
my samsung galaxy is stuck in recovery mode (clockworkmod recovery) and will not connect to the computer via usb. I have reinstalled the usb drivers but they constantly fail to install, tried on different computers and manually installing them seems not to work, what would be recommended?
regards
edit: manged to fix with odin yay
Hi everyone
So here it is : No program is able to recognize/detect my Galaxy S i9000M (Bell Vibrant) when it's in download mode, so I can't flash any ROM. My phone is currently fully bricked and unusable. I cannot access to the recovery mode with the three-button thingy or by "adb reboot recovery"
I bricked using Odin 1.8, trying to flash a 2.2 froyo stock ROM from Samfirmware. The flashing went ok, but it failed to reboot. Actually, the screen was turned off and nothing was happening. I figured out it was fully bricked so I made a USB JIG, it worked. I can access my download mode.
I connected the phone to my Windows 7 computer and used Odin to flash back to 2.1 Eclair, with a stock ROM from Samfirmware. It failed (I don't remember the error message, it was a couple days ago...).
I tried with Heimdall Frontened. It had a problem uploading the .pit file, so the flashing didn't work.
Now each time i connect the phone to my computer, Windows (and Heimdall frontened and Odin) doesn't detect it,which means that I can't flash anything on it even though it is in download mode.
I have tried reinstalling like every driver on earth, still not responding.
I tried on another Windows 7 machine and on Ubuntu, the device is not detected.
I tried with different USB cables, nothing happens.
This is my hypothesis (maybe silly) : Could the problem be the Download mode being corrupted?
Whatever... I could use some help from you guys.
Thank you,
Sam
I had/have the same problem.
I installed the Samsung Kies and now my computer recognize my phone again.
But I have still no idea what I need to flash to make my phone working.
goldsage said:
I had/have the same problem.
I installed the Samsung Kies and now my computer recognize my phone again.
But I have still no idea what I need to flash to make my phone working.
Click to expand...
Click to collapse
That is strange... I tried installing Kies and it didn't detect the phone. And you could just flash any 2.3 stock ROM with Odin I guess.
Hello, today i tried to flash cm10 on my Galaxy S i9000, using these instructions.
This guide assumes the Samsung Galaxy S already has Android 2.3 or higher installed on it. If the Samsung Galaxy S already has the clockworkmod recovery installed, skip this section.
WARNING: INSTALLING A custom recovery IMAGE ON THE SAMSUNG GALAXY S WILL VOID THE WARRANTY.
Download hardcore's Kernel with the clockworkmod recovery and the heimdall Suite:
hardcore's Kernel with the clockworkmod recovery 2.5: Downloadmd5: be7f5e02254c9c3fa91d1067f815dac1
Windows:
heimdall Suite 1.3.2: DownloadNOTE: The heimdall Suite requires the Microsoft Visual C++ 2010 Redistributable Package installed on the computer, which can be downloaded here.
Ubuntu 32bit:
heimdall Suite 1.3.2 Command-line Binary: Download
Ubuntu 64bit:
heimdall Suite 1.3.1 Command-line Binary: Download
Mac OS X:
heimdall Suite 1.3.2: DownloadNOTE: The source code for the heimdall Suite is available on Github.
Windows ONLY:
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Run the included zadig.exe in the drivers folder of the heimdall Suite.
From the menu, choose Options » List All Devices.
From the drop down, select Samsung USB Composite Device or Gadget Serial.
Click Install Driver.NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
heimdall can now be used safely on the Windows computer.NOTE: For more information about the heimdall Suite, please read the included README.txt.
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar hardcore's Kernel into the heimdall directory.
On the computer, open terminal and run the following command from the heimdall directory:heimdall flash --Kernel zImage
A blue transfer bar will appear on the phone showing the Kernel being transferred. The device will reboot automatically.
The Samsung Galaxy S now has the clockworkmod recovery installed. Continue to the next section.
Now, after I did this my phone got stuck at the Samsung Galaxy SI9000 loading screen. I was kinda scared because it was my first time flashing a rom, but I waited for ~10 minutes. After this I tried flashing another kernel, semaphore kernel JVT 1.9.1 but it didn't help, I'm still stuck in the boot screen. I'm really starting to worry, I'd really, really like some help .
try to instal a fresh android 2.3.4 or 2.3.5 (stock)
after that try again to instal what u want. during instal or after instal the phone enter again in bootloop, moment when u instal again the rom. after second try should be ok.
manueln06 said:
try to instal a fresh android 2.3.4 or 2.3.5 (stock)
after that try again to instal what u want. during instal or after instal the phone enter again in bootloop, moment when u instal again the rom. after second try should be ok.
Click to expand...
Click to collapse
Hi, I've been trying to do this all day, but the problem is that I can't go into recovery mode, but only in download mode. Any ideas?
Alkyno said:
Hello, today i tried to flash cm10 on my Galaxy S i9000, using these instructions.
This guide assumes the Samsung Galaxy S already has Android 2.3 or higher installed on it. If the Samsung Galaxy S already has the clockworkmod recovery installed, skip this section.
WARNING: INSTALLING A custom recovery IMAGE ON THE SAMSUNG GALAXY S WILL VOID THE WARRANTY.
Download hardcore's Kernel with the clockworkmod recovery and the heimdall Suite:
hardcore's Kernel with the clockworkmod recovery 2.5: Downloadmd5: be7f5e02254c9c3fa91d1067f815dac1
Windows:
heimdall Suite 1.3.2: DownloadNOTE: The heimdall Suite requires the Microsoft Visual C++ 2010 Redistributable Package installed on the computer, which can be downloaded here.
Ubuntu 32bit:
heimdall Suite 1.3.2 Command-line Binary: Download
Ubuntu 64bit:
heimdall Suite 1.3.1 Command-line Binary: Download
Mac OS X:
heimdall Suite 1.3.2: DownloadNOTE: The source code for the heimdall Suite is available on Github.
Windows ONLY:
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Run the included zadig.exe in the drivers folder of the heimdall Suite.
From the menu, choose Options » List All Devices.
From the drop down, select Samsung USB Composite Device or Gadget Serial.
Click Install Driver.NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
heimdall can now be used safely on the Windows computer.NOTE: For more information about the heimdall Suite, please read the included README.txt.
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar hardcore's Kernel into the heimdall directory.
On the computer, open terminal and run the following command from the heimdall directory:heimdall flash --Kernel zImage
A blue transfer bar will appear on the phone showing the Kernel being transferred. The device will reboot automatically.
The Samsung Galaxy S now has the clockworkmod recovery installed. Continue to the next section.
Now, after I did this my phone got stuck at the Samsung Galaxy SI9000 loading screen. I was kinda scared because it was my first time flashing a rom, but I waited for ~10 minutes. After this I tried flashing another kernel, semaphore kernel JVT 1.9.1 but it didn't help, I'm still stuck in the boot screen. I'm really starting to worry, I'd really, really like some help .
Click to expand...
Click to collapse
try to boot to download mode and flash this in odin------> http://forum.xda-developers.com/attachment.php?attachmentid=536163&d=1299530452 :good:
Alkyno said:
Hi, I've been trying to do this all day, but the problem is that I can't go into recovery mode, but only in download mode. Any ideas?[/QUOT
i m sorry but i forgot to mention a step. (step 2)
now i resume explanation
1. instal stock rom
2. root stock rom
3. enter recovery mode and try to instal your rom, probably incomplete
4. restart and go again in recovery mode and instal again your rom this time u will finish instalation successfully.
Click to expand...
Click to collapse
Somehow odin stop recognizing my phone? :S? But my pc recognized it (i heared the sound).
Alkyno said:
Somehow odin stop recognizing my phone? :S? But my pc recognized it (i heared the sound).
Click to expand...
Click to collapse
try to reinstal the samsung drivers
restart PC
Hello fellow members,
Before you go and advice me to search the forums before posting; I did that and did not find any solution... Here's my horror story;
I own a Galaxy S (GT-i9000). A while ago I installed Tsunami X on it along with Semaphore. When my phone was booting up, I accidentally removed the battery and when I tried to turn it on, I got stuck on a bootloop. The phone does not go in the recovery mode, and when I put it on download mode it does not get recognized by the computer (used 3 different computers, all with Samsung drivers and Kies.) which means that I cannot use Odin to flash it with a different ROM...
I am in a desperate need of your help as I searched all the forum for answers and did not find any... Thank you in advance
AW: Bootloop, Can't go to recovery mode and device undetectable on Windows... Help?
Maybe the usb cabel is corrupt. Did you already tried anotherone?
Sent from my GT-I9300 using xda app-developers app
For getting into recovery, try the 3 button option (Power + Home + Volume Up). Press these 3 buttons till you see the kernal logo.
For boot loop, try re-installing the ROM with data/cache wipe.
For USB,
(i) re-install these drivers 64 bit | 32 bit and then
(ii) check cable
(iii) follow this link for exhaustive solution http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571
http://forum.xda-developers.com/showthread.php?p=35683353#post35683353
I too have the same problem:
- SGS wont be recognized by PC (tried 2 differnet laptops and also different usb cables, nothing worked)
- Tried Odin and Heimdall (both didn't recognize the device)
- tried to flash the broccoli-aokp ROM: aokpcb_galaxysmtd_r2.1-beta-20120610-1843
- when i try to go (by the 3-button-option) into the recovery menu the device boots, shows the normal Galaxy S screen and then instead of recovery the ROM itselve tires somehow to boot (i get the bootscreen from the ROM)
- Also tried to make it visual for Odin/Heimdall via zadig.exe, didn't work...now the driver won't even install
- even tried it via cmd and the adb command, also no devices attached
Alltogether: i cant falsh any ROM via Odin nor CMW
Is it bricked? (Never had a bricked phone and dont know how to recognize this)
Greets Vauvenal7
Vauvenal7 said:
I too have the same problem:
- SGS wont be recognized by PC (tried 2 differnet laptops and also different usb cables, nothing worked)
- Tried Odin and Heimdall (both didn't recognize the device)
- tried to flash the broccoli-aokp ROM: aokpcb_galaxysmtd_r2.1-beta-20120610-1843
- when i try to go (by the 3-button-option) into the recovery menu the device boots, shows the normal Galaxy S screen and then instead of recovery the ROM itselve tires somehow to boot (i get the bootscreen from the ROM)
- Also tried to make it visual for Odin/Heimdall via zadig.exe, didn't work...now the driver won't even install
- even tried it via cmd and the adb command, also no devices attached
Alltogether: i cant falsh any ROM via Odin nor CMW
Is it bricked? (Never had a bricked phone and dont know how to recognize this)
Greets Vauvenal7
Click to expand...
Click to collapse
Can you go to recovery mode??
Sent from my GT-I9001 using Tapatalk 2
maddy2384 said:
Can you go to recovery mode??
Sent from my GT-I9001 using Tapatalk 2
Click to expand...
Click to collapse
Nope, neither the 3-button combination works (i get the normal galaxy s start up screen, and then instead of getting the recover ui the ROM somehow tries to start and i get the bootscreen...and then the bootloop starts) nor through the adb commands in cmd (no device detected)
Greets Vauvenal7
Sent from my HTC Vision
I cannot boot the device into Recovery mode. If I attempt to the device stays on the Samsung boot screen. Since I have gotten the device all I have done is rooted the device and it is running android version 2.2
When I put the device into download mode it is not recognised by my computer (tried using Windows 7, 8.1 and 10 build 9926) and Odin (v4.38) does not register that the device has been plugged in. In Device Manager I get Unknown USB Device (Device failed Enumeration). Re-installing drivers and the device does nothing to fix this.
Any assistance with this issue would be welcomed.
~Edit - The device is not booting at all now. It is stick on the Samsung Boot Screen.
~Edit - For some reason putting the device into Download Mode then plugging it into a my laptop and allowing Windows Update to find the drivers worked and allowed ODIN v4.38 to detect the device.
Then by following this guide I was able to flash CWM to my device. After doing this I was able to boot the device normally and I was able to boot it into the custom recovery.
The best way to boot to recovery in case you aren't able to.
The best way to boot to recovery in case you aren't able to is using ADB. Use the command adb reboot recovery and for sure you will either know what the exact problem is, or will be taken to recovery.