Database Develop

[Q] Stuck on boot screen... how to use recovery mode?

My I9000 is stuck on the boot screen, after trying to install EZbase (was stock eclair). Odin/heimdall don't see the phone in download mode. I CAN get into recovery mode.. i have Clockwokmod recovery 2.5.1.0 speedmod ULFK on there. I have tried a factory reset, but this didn't help.
So what do i do here?
I am under the impression i need to flash with an update.zip; but i don't have a clue what should be my update.zip.
Sorry if this has been asked many times, but i searched and have read many threads and got nowhere.

ok well download the android SDK tools and isntall all the USB drivers. Unplug your USB cable and change the port from the one you are using, boot your phone into download mode, once in download mode fire up ODIN v 1.7 and plug your phone in, it should find it in odin, once you can see it in odin you should be able to continue flashing EZbase and then onto Cyanogen if that is what you were trying to do

Once you get odin to recognize your phone in download mode you need to flash a Kernel/Rom
http://forum.xda-developers.com/showthread.php?t=991792
since you were trying to do that try the link above

Thanks for the quick response!
spectre85 said:
download the android SDK tools and isntall all the USB drivers.
Click to expand...
Click to collapse
do you mean Android SDK Starter Package? Or?

http://developer.android.com/sdk/index.html

This is what i downloaded; what do i do now? Do i have to run SDK Manager.exe and install java (i would like to avoid this, if i can)??
Thanks for your help.

ya unfortunately you have to install java. so maybe your phone isn't being recognized because your doing it in the wrong order....try this before you install anything, unplug the phone, boot into download mode, fire up odin then plug the phone in. you should see it on some com port on the top left

Ok; Java installed, ran SDK Manager and added Google USB Driver for Windows, Revision 4. [ as developer.android.com/sdk/win-usb.html ], which is in \android-sdk-windows\extras\google\usb_driver
The directions provided by google (url above) suggest plugging the phone in first. This installed the samsung drivers automatically, however.
Odin3 1.7 now showed a port; but the flash stalled at 'SetupConnection..'
I tried using 'update driver' via Device Manager, but all that i see is;
Modems -> SAMSUNG Mobile Modem
Universal Serial Bus controllers -> SAMSUNG USB Composite Device
Neither would update with the drivers in \android-sdk-windows\extras\google\usb_driver
[Also, Yes, I am opening odin and booting in download mode before connecting the USB cable]

Ok try flashing just a kernel go to the Dev section and find a kernel from hardcore it is called speedmod kernel. That should flash in 20 seconds or so. Flash the froyo one he has one for gingerbread so don't use that one they are separate threads so its easy to tell which is which
Sent from my GT-I9000 using XDA App

..now if i try to turn the phone on it shows a phone and a PC with a /!\ warning symbol between them, and i can't boot in to recovery mode. I CAN boot into download mode, and the PC makes a noise to acknowledge something has been connected, but Odin doesn't see it.
EDIT: I reinstalled Keis, and selected 'install drivers' on the menu from within the app.. this meant Odin was able to see the phone and i have sucessfully (apparently) updated the kernel to speedmod froyo. The phone is back to the 'Galaxy S' screen again. Now what? How long should the phone take to boot if it is sucessful (ie. how long should i wait before restarting?)
EDIT 2: Ahh, EZbase flash worked too! .. thank F, a working phone!
So i guess the key was to get the drivers (again) from the submenu in the Keis App NOT the android SDK.

Glad it worked out, sorry it took so long to reply, ya after you get a kernel on there then you need to flash a rom again, which is exactly what you did later

My Captivate not visible in Odin after following the CM wiki guide for flashing Cm9!

I was a first timer when I tried to flash Cm9 nightly on my Rogers captivate following the CM guide I installed the software from the heimdall directories as instructed. After everything when I tried to Odin back to stock 2.3.3 the device was not visible; so here's how I solved this problem:
1. Plug your phone in download mode and find it in the device manager and uninstall it.
2. Download Samsung Kies software and install it ( it will install the correct drivers for your captivate) .
3. After installation open Odin and plug the phone back in download mode, hopefully Windows will recognize your device and start installing the drivers from the folders. If the the phone is not recognized pull the Micro-USB cable out of the phone, while still in download mode, and plug it back again.
Hopefully this will help anyone in trouble

[Q] HELP! Question - why can't I flash CWM on my Galaxy S!

Hi There,
I am trying to use the general adopted approach for flashing CWM onto my Galaxy S, that is:
Download the correct CFRoot file, Download Odin, Boot the phone in Download Mode and run Odin..
I am unfortunately stuck at the last stage - I have booted in download mode only to find there is no USB connection and therefore Odin will not detect the phone.
My phone boots into Recovery Mode 3e
I have the following:
A Galaxy S running 2.3.6 Gingerbread XXJW4
A CF Root TAR File: CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
(I believe I have the correct matching file please can someone confirm this for me??)
Odin v1.85
Odin v3.07
Samsung Kies Uninstalled
the Devguru Samsung galaxy S drivers for windows 7 x64
I have tried:
Running USB mode - Samsung Kies, Mass Storage
Enabling USB Debugging
Running Odin in Compatibility mode for windows xp
What am I doing wrong here?!

b.cummins said:
Hi There,
I am trying to use the general adopted approach for flashing CWM onto my Galaxy S, that is:
Download the correct CFRoot file, Download Odin, Boot the phone in Download Mode and run Odin..
I am unfortunately stuck at the last stage - I have booted in download mode only to find there is no USB connection and therefore Odin will not detect the phone.
My phone boots into Recovery Mode 3e
I have the following:
A Galaxy S running 2.3.6 Gingerbread XXJW4
A CF Root TAR File: CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
(I believe I have the correct matching file please can someone confirm this for me??)
Odin v1.85
Odin v3.07
Samsung Kies Uninstalled
the Devguru Samsung galaxy S drivers for windows 7 x64
I have tried:
Running USB mode - Samsung Kies, Mass Storage
Enabling USB Debugging
Running Odin in Compatibility mode for windows xp
What am I doing wrong here?!
Click to expand...
Click to collapse
Try odin 1.3 and when you enter download mode and connect to PC .. if odin is not showing the phone being connected, make sure the drivers are properly installed by going to device manager of your windows..

b.cummins said:
Hi There,
.
I am unfortunately stuck at the last stage - I have booted in download mode only to find there is no USB connection and therefore Odin will not detect the phone.
My phone boots into Recovery Mode 3e
What am I doing wrong here?!
Click to expand...
Click to collapse
Check USB
if its not the USB
Install drivers http://forum.xda-developers.com/showthread.php?t=728929
If it connects
enable USB debugging
use odin

1nstan7riod said:
Check USB
if its not the USB
Install drivers http://forum.xda-developers.com/showthread.php?t=728929
If it connects
enable USB debugging
use odin
Click to expand...
Click to collapse
Thank you both for replying
Unfortunately none of this has worked
I have now tried Odin 1.3, 1.85, 3.07 No joy.
I have tested the drivers I had and removed and reinstalled the link you gave me - on both occasions the phone does appear in device manager as 'SAMSUNG Android' but odin completely fails to detect the device until it's powered on and out of download mode.
Any idea?

[Q] Stuck after flashing with Semaphore

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?

Help rooting Samsung Galaxy S4

Hello, recently I buyed a Samsung Galaxy S4 i9500 phone. I read xda-developers articles to root, and can't root it. I use Linux in my computer, but have a Live HBCD WinXp boot. S4 is booted in download mode with USB Depuration checked and Verify USB Apps unchecked.
With Live HBCD WinXp I install samsung drivers. Putting S4 into download mode runs right and WinXp device manager recognizes the Samsung device. Error is opening Odin 1.85 or Odin 3.04. Odin can not open communications port with S4 to flash image.
With Linux Mint 17.3 Samsung device is recognised in dmesg command. using Heimdall 1.4.0 (Ubuntu), commandline or frontend, can not send data to S4.
I can not root S4 phone.
Anyone can help?
Thanks.

eb4bgr said:
Hello, recently I buyed a Samsung Galaxy S4 i9500 phone. I read xda-developers articles to root, and can't root it. I use Linux in my computer, but have a Live HBCD WinXp boot. S4 is booted in download mode with USB Depuration checked and Verify USB Apps unchecked...
Click to expand...
Click to collapse
Your best bet is to post this question within the following thread.
https://forum.xda-developers.com/showthread.php?t=2192886
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

After readed link, solved in bad way. I need to instal windows to flash with odin, heimdall in linux does not detect two hardware devices in phone like odin (total of three hardware devices in phone).
Using odin i can not flash with cwm recovery. Flash is successfull but can't start cwm recovery. After pushing buttons s4 loops in start and restart itself. But cf-autorun runs fine, not much like cwm recovery, but enough in this case. Cwm recovery is better.
Thank you.