Develop Bugs

[Q] Samsung EPIC 4g BRICKED - won't boot!!!

Hello Everyone,
I tried flashing Cyanogen7 onto my rooted EPIC 4G using ClockworkMod Recovery v3.0.2.4 and this immediately bricked my phone and kept it from booting up.
When I try to boot up my phone it gets stuck at the SAMSUNG boot up screen and the four capacitive buttons (menu,home,back,search) say lit up. When I try to boot into Recovery Mode I get the following screen:​
ClockworkMod Recovery v3.0.2.4
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and Restore
- Mounts and Storage
- Advaned
- Power Off
- *****Go Back*****
------------------------------------------------------------------
E:Missing bitmap icon_clockwork (Code -1)
ClockworkMod Recovery v3.0.2.4
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]​
When, for example, choose Wipe data/factory reset from the menu above it simply shows:​
-- Wiping data...
Formatting /data...
E:unknown volume "/data"
Formatting /cache...
E:unknown volume "/cache"
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard/.android_secure"
Data wipe complete.
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]​
I'm really not sure what to do here. Any help would be appreciated.​
Thanks guys...

Have to tried to Odin back to stock and then retrying it? Your phone isn't bricked. It's not even close to being bricked. In fact, it's just fine. A simple couple clicks in Odin and your right back to stock let me know if ya need anything else

Ur not bricked go into download mode by holding 1 on the keyboard while powering on and Odin back to stock I am truly bricked where as my phone won't get into anything or even charge

tried looking into Odin...seems to only work on Windows...don't suppose there's an alternative that I could use on my Mac is there?

Heimdall. Read the directions twice.

And in the future, don't touch ROM Manager or any of the CWM versions it offers. Ever.
EDIT: This thread title gets more annoying every time I see it...

Failed to Detect Compatible Device
Hey all,
So I was able to get Heimdall up and running (thanks a bunch for that) but for some reason my phone doesn't seem to be able to connect to my computer when it's in downloading mode (screen where the yellow android with a shovel pops up). When I click 'Start' on Heimdall it just tells me that it cannot detect a compatible device. But I'm sure that my Epic is plugged in correctly.
The only thing I can think of is that my cord is messed up for some reason. Going to give it a try with a different one. Is there anything else it could be?

I don't know mac but the same thing happens on windows if after you installed samsung drivers you did not re boot pc. Maybe a problem you might run into is that when the phone is running and you connect it will install the drivers. Hopefully it installs what you need without a running connect.
Sent from my SPH-D700 using XDA App

ldartez said:
Hey all,
So I was able to get Heimdall up and running (thanks a bunch for that) but for some reason my phone doesn't seem to be able to connect to my computer when it's in downloading mode (screen where the yellow android with a shovel pops up). When I click 'Start' on Heimdall it just tells me that it cannot detect a compatible device. But I'm sure that my Epic is plugged in correctly.
The only thing I can think of is that my cord is messed up for some reason. Going to give it a try with a different one. Is there anything else it could be?
Click to expand...
Click to collapse
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X. Samsung fixed this for certain bootloaders running on certain devices however I'm unsure about the Epic 4G. I recommend starting a thread asking about it. If no one knows then unfortunately you'll have to use Windows or linux.

Benjamin Dobell said:
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X
Click to expand...
Click to collapse
This may be, but the stock Samsung cord is a notorious piece of horse ****. (Yes, it's that bad.)

Benjamin Dobell said:
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X. Samsung fixed this for certain bootloaders running on certain devices however I'm unsure about the Epic 4G. I recommend starting a thread asking about it. If no one knows then unfortunately you'll have to use Windows or linux.
Click to expand...
Click to collapse
I've tried starting a thread b4 on this and no one responded to it
Sent from my SPH-D700 using XDA Premium App

Honest suggestion? Just find a friend with a Windows computer and use Odin on his. Also, I've never had any problems with my Samsung data cable, but I also bought a blackberry micro cable for like $1.50 on amazon and free prime shipping, and it works great too.

Phone fixed!!
I ended up being able to fix my phone. The problem ended up being that Mac, for some reason, is not able to detect samsung phones (or at least mine..Epic 4g) while they are in Download Mode. I loaded the .msi drivers that I needed, Odin ( as opposed to heimdall for the sole reason that Heimdall requires Visual studio files to be installed on Windows) and the stock android image onto a flash drive.
I plugged these into a windows machine and everything worked perfectly.

k0nane said:
And in the future, don't touch ROM Manager or any of the CWM versions it offers. Ever.
EDIT: This thread title gets more annoying every time I see it...
Click to expand...
Click to collapse
if not rom manager or CWM then what do you usually use for flashing roms?

He's just saying don't use Rom Manager or the versions of CWM it specifically installs. Just use the CWM versions found here on the Epic 4G forums. Yes, CWM is how we flash roms.
ldartez said:
if not rom manager or CWM then what do you usually use for flashing roms?
Click to expand...
Click to collapse

well i just ran into this problem, with rooted stock froyo (think its EC05) and the customized purple cwm for the epic... so clearly using the recovery image found on these forums is NOT foulproof... and all i wanted to do was perform a back up so i could try out a eg22 rom... sigh... anyway thanks to odin im back up but now i have to re do everything and i was not able to back up my STOCK!!! image. is there a different recovery available or perhaps one that works?

duplissi said:
well i just ran into this problem, with rooted stock froyo (think its EC05) and the customized purple cwm for the epic... so clearly using the recovery image found on these forums is NOT foulproof... and all i wanted to do was perform a back up so i could try out a eg22 rom... sigh... anyway thanks to odin im back up but now i have to re do everything and i was not able to back up my STOCK!!! image. is there a different recovery available or perhaps one that works?
Click to expand...
Click to collapse
Did you go into recovery with the 3 finger method or did you use quck boot or ROM manager? Never use any of those when doing a backup or restore. The purple recovery worked well for me when I needed it but now am using Bonsai's recovery rooting with Masterkey Unlocker. You can find Bonsai's site by googling Bonsai Android.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Did you go into recovery with the 3 finger method or did you use quck boot or ROM manager? Never use any of those when doing a backup or restore. The purple recovery worked well for me when I needed it but now am using Bonsai's recovery rooting with Masterkey Unlocker. You can find Bonsai's site by googling Bonsai Android.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
yeah, i used the three finger method...
bonsai eh? ill have to look it up. edit: or i could just click the link in your sig... lol
off topic: im new to the epic (finally retired my weary hero), so anything you would recommend?

duplissi said:
yeah, i used the three finger method...
bonsai eh? ill have to look it up. edit: or i could just click the link in your sig... lol
off topic: im new to the epic (finally retired my weary hero), so anything you would recommend?
Click to expand...
Click to collapse
I try not to advertise the link in the sig (shhh). I do recommend trying the Masterkey Unlocker if you are unhappy with CWM 3.1.0.1. It is a nice graphical interface and works well. You can Odin to either EB13 or EC05 stock, root with the MK and then 3 finger to nand backup your phone or use Titanium Backup.
Sent from my SPH-D700 using XDA App

Can no longer flash a rom

So I have an issue. After I was formatted system and wiped my data to install 1.9 I accidentally reboot the phone before I installed the rom, now when I'm in clockwork mod I get a
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard/
error whenever I try to select the zip to install. How do I fix this?
The phone won't load past the boot screen either because there is no rom installed. I even tried to reset it to stock and it won't load past the startup screen

This happened to mine too. Looking for answers

There's always a usb jig to force it into download mode. Then just reflash a tar. Look for the thread "the jig is up"
Sent from my SPH-D710 using xda premium

This happened to me. I odin'd an older version of cwm, and installed a rom from the internal storage. For some reason the older one worked for me.
Sent from my SPH-D710 using XDA App

Or you can try to mount USB in mounts and storage, transfer rom to internal storage, and flash from there.
Sent from my SPH-D710 using XDA App

Happened to me tons of times. Just Odin the recovery again and it'll work fine.

OP, much like others have suggested, boot into odin mode and reflash recovery

Having major issues here please help and thanks!
My phone-Samsung Galaxy S2 Epic 4G Touch (Sprint) SPH-D710
RUNNING AOKP ICS ROM DOWNLOADED FROM EPIC4GTOUCHROOT DOT COM
From my understanding i should have flashed this rom through odin instead of my rouge recovery.I enjoyed the rom for a day or two than decided to flash back to a different rom and rouge recovery no longer showed up. Anroid system recovery <3e> shows up instead. i went to try to flash a rom here and it started than the android guy came up laying down with the chest area open and an exclamation mark above him than said
E: failed to verify whole-file signature
E: signature verification failed
installation aborted.
My computer no longer recognizes my phone iv tried re-installing the drivers and no luck. I've tried installing from sd card and still no luck. Ive tried mobile odin and it doesnt pick up anything in my sd card.
SOMEONE PLEASE HELP WHAT DO I DO???
-THANKS

boot loop after flashing latest manhatten project rom

Ok have been running foxhound 1.1,tried a couple of other roms,kernels,etc and no problem. But now all of a sudden tried to flash manhatten and endless boot loop. I have tried to wipe from cwm several times but no luck. I dont want to lose my pictures from virtual sdcard. I have no access to adb but cwm and fastboot of course. I'm using linux so is there any way to use fastboot to erase everything but keep virtual sdcard. If that can you point me to instructions on how to from fastboot. I have the GSM version

Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot

Samsuck said:
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Click to expand...
Click to collapse
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????

tman7510 said:
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
Click to expand...
Click to collapse
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.

9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk

Samsuck said:
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
Click to expand...
Click to collapse
I have formatted everything but davik cache but when I do that I get" E:unknown volume for path /sd-ext Dalvik Cache Wiped " then reflash foxhound and now I am back to the boot loop all I get is Google with unlock symbol at the bottom and it just loops. There has to be a way to get info off my virtual sdcard..I dont care how hard it is

demon2112 said:
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I didn't use the gapps but the rom should still boot without that gapp version. Also shouldn't I be able to flash another rom without having this issue??? All I did was flash from clockworkmod. maybe the zip file I downloaded got corrupted but I am unable to fix the problem. I had installed the manhatten rom yesterday but went back to foxhound because lack of performance/undervolting settings that apperently are on the rom. just want it to work again..I'm unable to use adb becasue it wont boot. all I have is fastboot and cwm recovery

That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA

Samsuck said:
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Click to expand...
Click to collapse
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???

"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"

tman7510 said:
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
Click to expand...
Click to collapse
You can use ADB in CWM Recovery. I do it all the time in Windows.

El Daddy said:
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
Click to expand...
Click to collapse
yes I know and I have no problem using what little I know of fastboot commands but is there a way to use fastboot to copy my virtual sdcard to my pc?????

Be sure to "mount data" in Recovery
adb shell
type su for superuser.
then ls to list the dirs
and cd to change
You might have to pull files one by one. I'm not sure if there's a way to pull the entire contents of it.

Samsuck said:
You can use ADB in CWM Recovery. I do it all the time in Windows.
Click to expand...
Click to collapse
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!

Actually, do this.
Once you have the drivers installed for Windows, and your phone is being recognized "adb devices"
Run
adb pull /data/media/DCIM C:Urname\example\blah
Replace the C:Urname\example\blah with an actual directory of the Windows PC
It might take some time but that should drag your pictures and stuff.

Here's the link with instructions to return to stock. http://forum.xda-developers.com/showthread.php?t=1366806

tman7510 said:
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Click to expand...
Click to collapse
Hit, Install SDK on the toolkit. It will do it very quick and easy for you.
Since the SD Card on our Nexus is actually /data/media, like I said earlier, just mount data.

Gnex toolkit is a great tool. I'm wondering why I have permission issues with adb in cwm recovery in Linux. not complaining but I wish there was a kit like that for us linux users

any body know why in cwm recovery if run ./adb device in linux you get
devices listed
?????????? no permissions
any linux users out there? I'm saving my files thanks to a windows program gnex tookkit by mskip.
Special thanks to Samsuck for all his help and the rest of the forum

Flashed without Correct CID

Hi Everyone,
I did a boo boo. I flashed my One X without a supported CID with the Android Revolution 14.2 ROM. Is there a way to correct this and revert back to my previous ICS? Help please.

There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom

ClydeB1 said:
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
Click to expand...
Click to collapse
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Is there any other way to flash the phone? I tried "fastboot flash zip rom.zip". It showed OKAY for the copy, however, a second line remark "writing 'zip' ... FAILED (remote not allowed)" appeared. The process then was aborted.
I also tried formatting the sdcard and then tried to mount the sdcard. Same 'unable to open ums lunfile...' error constantly appears. Just afraid that my phone is now a brick. Can anyone help? Thanks in advance.

kevintan12 said:
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Click to expand...
Click to collapse
Install a version of CWM that isn't ancient, I.e., 5.8.4.0.

I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?

kevintan12 said:
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
Click to expand...
Click to collapse
No, everything is recoverable, if your phone won't turn on at all, then you're bricked for real.
Just flash the one from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
then put in the same folder as fastboot and use command:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img

Thanks everyone for the advice. Really appreciate it. I finally managed to use TeamWin Projects and it allowed me to mount the USB. Managed to then transfer an ICS ROM for flashing.

[Q] Is my Galaxy Gio bricked?

Hello, today was the day I got back to the Android world after a good 2 years in the shadow. Right off when I had opened my box I started to root and flash. Well, stupid me I didn't know what I was doing and now I'm here with a phone that doesn't get past the start-up logo anymore.
Is the phone bricked?
Here is what I can do:
Get into recovery-mode "OK-button and ON-button"
Get into "downloading..."-mode (I'm not sure of this one because it just says downloading... in yellow text)
Whenever I'm in recovery-mode and to do anything it only gives me error.. for example:
I downloaded the official firmware for my GIO named "S5660XXKTK_COVKS1_Sweden_Android..." gives "E:Short write of /tmp/sideload/package.zip (No space left on device)"
I then went to do wipe of data/factory reset and cache partition. This gives "Formatting data... E:format_volume:rfs format failed on /dev/stl13 Formatting cache... E:format_volume:rfs format failed on /dev/stl14 Data wipe complete.
When I go back and try to install official firmware it still says: "E:Short write of /tmp/sideload/package.zip (No space left on device)"
So I then try CM10-firmware (which is named: cm-10-20121204-unoffical-gio.zip (this one: http://forum.xda-developers.com/showthread.php?t=1804646) )but this gives "Finding update package... Opening update package... Installing update... "E:Error in /tmp/sideload/package.zip (status 0) Installation aborted.
IS MY PHONE BRICKED? OH AND BY THE WAY. MY PC (Windows 8) DOESN'T RECOGNIZE MY PHONE.........
Edit: I have Clockwork Mod

SwedroidBobby said:
Hello, today was the day I got back to the Android world after a good 2 years in the shadow. Right off when I had opened my box I started to root and flash. Well, stupid me I didn't know what I was doing and now I'm here with a phone that doesn't get past the start-up logo anymore.
Is the phone bricked?
Here is what I can do:
Get into recovery-mode "OK-button and ON-button"
Get into "downloading..."-mode (I'm not sure of this one because it just says downloading... in yellow text)
Whenever I'm in recovery-mode and to do anything it only gives me error.. for example:
I downloaded the official firmware for my GIO named "S5660XXKTK_COVKS1_Sweden_Android..." gives "E:Short write of /tmp/sideload/package.zip (No space left on device)"
I then went to do wipe of data/factory reset and cache partition. This gives "Formatting data... E:format_volume:rfs format failed on /dev/stl13 Formatting cache... E:format_volume:rfs format failed on /dev/stl14 Data wipe complete.
When I go back and try to install official firmware it still says: "E:Short write of /tmp/sideload/package.zip (No space left on device)"
So I then try CM10-firmware (which is named: cm-10-20121204-unoffical-gio.zip (this one: http://forum.xda-developers.com/showthread.php?t=1804646) )but this gives "Finding update package... Opening update package... Installing update... "E:Error in /tmp/sideload/package.zip (status 0) Installation aborted.
IS MY PHONE BRICKED? OH AND BY THE WAY. MY PC (Windows 8) DOESN'T RECOGNIZE MY PHONE.........
Edit: I have Clockwork Mod
Click to expand...
Click to collapse
Which CWM u have? ext4 or ext4+rfs? U can try to fix it by going to recovery mode and format sdcard then try to wipe data and cache

Don't worry
Resolve this problem, install stock ROM through odin.
Note there are problems in the win 8 in terms of hardware identification (can not identify on entrances com devices) use an operating system win7 or XP to install rom on your phone.

animezeroo said:
Don't worry
Resolve this problem, install stock ROM through odin.
Note there are problems in the win 8 in terms of hardware identification (can not identify on entrances com devices) use an operating system win7 or XP to install rom on your phone.
Click to expand...
Click to collapse
Well.. I do not have a Windows 7 PC and my pc (Windows 8) won't detect my Gio.. says "unknown driver" when I plug it in.
batman38102 said:
Which CWM u have? ext4 or ext4+rfs? U can try to fix it by going to recovery mode and format sdcard then try to wipe data and cache
Click to expand...
Click to collapse
How do I check that?
Edit: This was the CWM I used. No clue where on XDA I got it though..
http://dl.xda-developers.com/attach...91d018f0d97c7/50e588cc/6/1/6/5/2/5/Update.zip

Did u installed kies? U need that for drivers
Sent from my GT-S5660 using xda app-developers app

AngSanley said:
Did u installed kies? U need that for drivers
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Yes I installed Kies and when I did. I went into task manager and deleted all process with Kies before I opened Odin.
Still no luck
I will try to opererate on a Windows XP-pc now. Hopefully it will work out good
Edit: Did not work with XP either.....
Edit2: Now I used Gio Recovery on this site: clockworkmod.com/rommanage r and trying to replace it with stock recovery.
But I am stuck with this message: Replacing stock recovery with ClockworkMod recovery.
HELP!

SwedroidBobby said:
Yes I installed Kies and when I did. I went into task manager and deleted all process with Kies before I opened Odin.
Still no luck
I will try to opererate on a Windows XP-pc now. Hopefully it will work out good
Edit: Did not work with XP either.....
Edit2: Now I used Gio Recovery on this site: clockworkmod.com/rommanage r and trying to replace it with stock recovery.
But I am stuck with this message: Replacing stock recovery with ClockworkMod recovery.
HELP!
Click to expand...
Click to collapse
DO NOT USE ROM MANAGER TO INSTALL CWM! Use the original way to install cwm

Your phone is in a soft bricked mode as you can still open although you are in a soft brick mode I suggest that you search the forums for more information on how to fix your soft bricked device good luck

MistedEvo said:
Your phone is in a soft bricked mode as you can still open although you are in a soft brick mode I suggest that you search the forums for more information on how to fix your soft bricked device good luck
Click to expand...
Click to collapse
Oh ok thanks. But I'm searching and I'm searching for an answer nowhere to be found.
If I go back to store now will they be able to tell if this is rooted or not? I mean even if I do a factory reset?

They might find out.. You should just flash stock firmware with odin. Search YT or Google if you don't know how. It's far more simple than taking it to service.
Sent from my GT-S5660 using xda app-developers app

Jyrx said:
They might find out.. You should just flash stock firmware with odin. Search YT or Google if you don't know how. It's far more simple than taking it to service.
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
I have tried Odin with different windows versions and USB ports. No luck. So if I can't swap my phone for a new at the store I will try to make a USB jig contact.
Since my phone won't connect with my pc at all
Edit: well the only way my phone connects to Odin is through emergency dload mode. But when I am in that mode, set everything up in Odin and push start the timer will just go on and on and on. I gave up when it showed 210 minutes. And no, I do not have a crappy PC mine is 3 months and in the top end

SwedroidBobby said:
I have tried Odin with different windows versions and USB ports. No luck. So if I can't swap my phone for a new at the store I will try to make a USB jig contact.
Since my phone won't connect with my pc at all
Edit: well the only way my phone connects to Odin is through emergency dload mode. But when I am in that mode, set everything up in Odin and push start the timer will just go on and on and on. I gave up when it showed 210 minutes. And no, I do not have a crappy PC mine is 3 months and in the top end
Click to expand...
Click to collapse
you should shut kise program in to be able odin contacted your phone

animezeroo said:
you should shut kise program in to be able odin contacted your phone
Click to expand...
Click to collapse
Doesn't matter if I exit Kies or not. But I went to the store today and if they would had a Galaxy Gio on the store I would be able to swap but they didn't so it went into repair. So I'm getting my old but fixed Gio back in a week.