[Official thread] AT&T captivate rom brick problem affected users - Galaxy S I9000 General

I've made this thread to focus our investigations about the problem in just one thread.
The problem is originally made when you use a odin3 flasher for captivate, that downloads on your phone the stock version of the captivate rom, that has different radio version and locks the phone while booting, entering in a never-ending boot cycle.
As the captivate has different button layout, we can't enter in download mode, but it stills on the phone. The screen doesnt' show when the usb is plugged, i dont know why yet.
I've managed to get one loading circle by plugging and unplugging repeatedly the USB while pressing vol+,vol- and power button (i think its probability to get it, i'vent seen any specific thing that enables it) , and lasts until you stop pressing one of those buttons, but i haven't been able to connect the usb while its, and check if in that screen the phone answers the adb/fastboot commands. Every button combination you may imagine/read doesn't work, so we'll have to use a software method to get into the download mode
For all the people affected, make a batch file with this
Code:
cd [directory where you have adb.exe]
:1
adb wait-for-device
adb reboot download
goto 1
and plug/unplug the usb, to check if in a concrete phase of the boot procedure the rom listens to adb.
Threads of affected people:
http://forum.xda-developers.com/showthread.php?t=749546
http://forum.xda-developers.com/showthread.php?t=735462
and much more people that is not in this forum
We hope help from developers, thank you.

Any luck getting adb to recognize??

Here no luck

Any progress with this more and more users have problem with this wrong flash

I suggest contacting with the creator of the odin 3 captivate flasher to warn i9000 users that it'll brick the phone

Guzmanus said:
I suggest contacting with the creator of the odin 3 captivate flasher to warn i9000 users that it'll brick the phone
Click to expand...
Click to collapse
I agree... The programs look exactly alike, and so much for the "download mode always remains untouched" comment people were throwing out there... It appears Odin does make changes to the download mode, or at least the captivate's odin does... Is there another Odin for the vibrant as well? and what happens to the captivate and vibrant when they are flashed with the i9000's Odin?

I've read something about that vibrant users can flash i9000 roms without any problem, but im not sure about captivate users

samsung captivate brick
i have the same problem... im running windows 7 x64(64 bit) and i was updating my phone to the rooted 2.2 froyo update via odin with the "I897UCJI6-OCD-REV02-Low-designgears" while updating the phone when the odin program froze and ruined/bricked my phone... i have tried all the steps to try and un-brick my phone but at this point im about ready to give up.... at this point my phone will not power on in any mode nor will it go into recovery mode or download mode... if any one has any info on how to fix this please let me know....

Related

Help me "unbrick" my Galaxy S (I9000NEJG2)

So, I think my phone is a bit bricked at the moment, I have this image of a phone, an exclamation mark, then a computer connected by a row of dots. I can't use links because I'm a new forum member, but you can see an actual picture of this image on the "[STOCK ROM] Odin3 One-Click Downloader" thread by Darkstrider.
I can still get into "download mode" using the keypress and Odin still picks up the device on the COM port.
It had this firmware before I tried flashing it (16Gb model locked to the Three UK network):-
PDA: I9000NEJG2
PHONE: I9000NEJG1
CSC: I9000HCGJF2
The steps leading up to the bricking:-
I was firstly trying to follow the instructions on Darkstriker's 2nd post from his topic " [REF] BIG FAQ Thread! {Flash/Root HOWTO} {ADB&Tutorials} {T&T} [READ BEFORE POSTING!]"
So I got JG5 firmware from a link on the Modaco forums (from the " 22/Jul r3 (JG5) - MoDaCo Custom ROM for Samsung Galaxy S with Online Kitchen" topic, the ROM was hosted on coblitz.codeen.org.
Installed the "usb_drivers_GalaxyS_x64.zip" drivers from the "USB Driver for Galaxy S and Misc Info" (xda forums) topic. Windows XP picked up and used the drivers in the extracted "03_Swallowtail" folder. It added "Samsung Mobile Modem" and "SAMSUNG USB Composite Device" to Device Manager.
So, I did everything on Darkstriker's guide, added the .pit file, chose the "re-partition" option because I was flashing to JG5. The process got stuck on "File analysis..", waited 20-30mins and it didn't move from this status.
Didn't work, so then I tried some different drivers, I googled and found "I9000_USB_driver.rar" on hotfile.
This time Odin got to the "Do not turn off target!!" status and it didn't move for around 20-30mins.
Restarted my computer, detached and reattached the USB cable, I decided to not use the re-partition option and try again, the status got to "factoryfs.rfs", this time the phone display went blank, which didn't happen before, but again it seemed stuck, nothing happened after waiting 20-30mins. So I aborted and closed Odin.
At this point I just wanted to use the phone to make a call when I notice the image/symbol above that I described at the beginning of this post. Help!
What's the best way to fix this? I spent nearly 2-3hrs trying to flash my phone and now it's half dead! I've nearly run out of mental stamina, but will give it a fresh attack today/tomorrow if someone can offer some suggestions.
Was thinking about trying the "fix" on the "[STOCK ROM] Odin3 One-Click Downloader" topic but not sure if it is only for the Captivate.
Hope you guys can help me out
All I wanted to do was to put the "(ROM Galaxy Europe) Doc's StockRomMod V2 (XWJG5)(deoxed) 30/07/10" ROM on my device, and add the JIT compiler and Flash 10.1 player if possible
Go read the guides from the development area.
It's just too easy and you're making it overcomplicated to yourself.
If you have the connect to pc error logo.. remove battery and then proceed.
1. if you installed kies ever, you already have the needed drivers.
2. start odin and select correct files (pit,code,modem,csc in respective order)
3. put phone in download mode (home + volume down + power)(hold long enough)
4. plug it to computer (odin should say "added")
5. press start (in less than 5 mins you phone should restart and go into special mode where it does some magic and reboot again and your done).
My god Buddy, you are right, I was overcomplicating things, I did it in the exact order you said and now I'm getting the progress bar for the first time.
I'm feeling optomistic now! Thanks dude!
It worked! If I was gay I'd kiss you on the lips! Thanks again buddy, it was stupidly simple after all.
Tundraswan
Glad your issue is resolved... just feel warm and cosy knowing that its not possible to brick your Galaxy S.
HELP!!!!
twisted_mind said:
Tundraswan
Glad your issue is resolved... just feel warm and cosy knowing that its not possible to brick your Galaxy S.
Click to expand...
Click to collapse
Really? I can't get my Captivate to even boot up...........no signs of life.........HELP!!!!!!!!!!!!
Stupid me: I pulled the USB cable and cancelled a ROM update (that was mid way) with Odin because i realized the SIM and SD card were still in the phone....so i pulled it to remove those and now NOTHING>>>>
Please help, following the instructions and it won't go back into download mode. Is there any other way?
Hello !
Where do i find those files for PIT , PHONE , PDA and CSC ?
i have i9000 galaxy s Problem solved , i already repaired my phone
These forums are for the Samsung Galaxy S i9000, you want to go here...
http://forum.xda-developers.com/forumdisplay.php?f=703
the galaxy s gt 1900 screen
Hi,
after a fail at rooten my device my phone keeps hanging on the galaxy s I900 screen for about 20 sec and then it turns it self off and on. He will repeat this until he runs out off juice.
this topic was usefull.. because the hole odin set up worked. But because of the turning off and on he cant complete the hole progress.
can anyone help me?
buddy01 said:
Go read the guides from the development area.
It's just too easy and you're making it overcomplicated to yourself.
If you have the connect to pc error logo.. remove battery and then proceed.
1. if you installed kies ever, you already have the needed drivers.
2. start odin and select correct files (pit,code,modem,csc in respective order)
3. put phone in download mode (home + volume down + power)(hold long enough)
4. plug it to computer (odin should say "added")
5. press start (in less than 5 mins you phone should restart and go into special mode where it does some magic and reboot again and your done).
Click to expand...
Click to collapse
I may have bricked mine too. Can anyone tell me where i would be able to get these files please? Thanks in advance!
fieldop said:
I may have bricked mine too. Can anyone tell me where i would be able to get these files please? Thanks in advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=846913 that has all stock roms.. just choose the one u need and job done !! That is providing you can get into download mode ???
If you cant get into download mode, theres a clever little tool you can make to force the phone into download mode.. http://forum.xda-developers.com/showthread.php?t=819551
Good luck
azzledazzle said:
http://forum.xda-developers.com/showthread.php?t=846913 that has all stock roms.. just choose the one u need and job done !! That is providing you can get into download mode ???
If you cant get into download mode, theres a clever little tool you can make to force the phone into download mode.. http://forum.xda-developers.com/showthread.php?t=819551
Good luck
Click to expand...
Click to collapse
Thanks soo much!! Done it! =)
Hi, i have semi bricked my galaxy s which is from the african region, but purchased in dubai. i've managed to cut open a micro usb jack and i can clearly see the pins i need to use, my question is, does the resistor value have to be exactly 301k or it can vary up or down slightly. also instead of using 3 100k resistors can i add up other values as well to make it close to 301k? sorry im noob at this stuff atm but i find such hacking very intriguing. also when i tried it with the resistors that add up to 300k, i join them to pins 4 and 5 with the phone switched off, after 5 seconds it shows the same thing 'phone ! pc'. by which i know all hope is not lost yet.
6stringster said:
Hi, i have semi bricked my galaxy s which is from the african region, but purchased in dubai. i've managed to cut open a micro usb jack and i can clearly see the pins i need to use, my question is, does the resistor value have to be exactly 301k or it can vary up or down slightly. also instead of using 3 100k resistors can i add up other values as well to make it close to 301k? sorry im noob at this stuff atm but i find such hacking very intriguing. also when i tried it with the resistors that add up to 300k, i join them to pins 4 and 5 with the phone switched off, after 5 seconds it shows the same thing 'phone ! pc'. by which i know all hope is not lost yet.
Click to expand...
Click to collapse
I did 300k and it worked. 3 x 100k ohm resitors.
Solder just one pin and leave one pin loose.
Connect that micro usb when phone is shut down.
Touch with that loose end to that pin which you did not solder. 4 or 5.
Keep it pressed until phone goes to the download mode.
You can try my jm8 guide.
Section B is for flashing stock 2.1, to get a fresh clean install.

[Q] Is my Tab done for? Is it fixable? Help!

I'm having the following problems with my TAB and would like to know it's fixable. I treid almost everything to fix it without success. I'm hoping someone can help me. Anyone have these problems before?
1. Doesn't charge normally. It would charge but charge really slow like it's connected via us. It shows an x next to the lightening icon when I charge it using the original charger and cable.
2. I cannot go into recovery mode. I get the black screen with the white line. There's also no boot animation when it boots up.
3. The camera doesn't work. I get a fail message when I open it.
4. My computer doesn't detect it in download mode, kies or mass storage. My computer detect my samsung galaxy s i9000 without any problems so I know it's not the computer. I cannot change the firmware because my computer doesnt detect it.
5. I dont have the receipt to do a warranty repair. What are my other option?
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build XXJMA
Any help is much appreciated! Thanks!
Did you register your Tab with Samsung?
If so, they have a record of your purchase and will be able to provide support.
If not, then try this which I got from their online chat: Hope it helps.
"Kyle: To recover the device via the hardware keys, do the following:
Kyle: 1. Power off the handset.
Kyle: 2. Hold the Vol Down Key + Vol Up Key + Power Key for 15 seconds then release.
Kyle: 3.When the recovery screen comes up, use the volume up key and volume down key to navigate through the selections and the power key to select item.
Kyle: 4. Select Delete all user data to recover the device. To confirm, scroll down and select Yes – delete all user data. The phone reboots and again displays the recovery screen.
Kyle: 5. Select Reboot system to restart the handset again. "
Thanks but I cannot get to that recovery screen like I said above. All I get is a black screen with a white line when I try to go into recovery mode. I also purchase this used with no receipt.
U just need to flash a working rom. Try roto jm... in the dev forum
Your tab was modified. I wont blame Samsung if they wont fix it for u
Sent from my SGH-I987 using XDA App
How do i flash to a different rom if a computer wont detect it?
Do you have the latest kies installed? Is USB Debug on? If it still doesn't detect, have you tried android-sdk or heimdall. Each comes with usb driver. I find it hard to believe your PC doesn't detect the tab. I never heard such thing before unless you're the real first victim then...yeah, try to call Samsung and pay a fee.
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
starbuck123 said:
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
Click to expand...
Click to collapse
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Benjamin Dobell said:
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Click to expand...
Click to collapse
Thanks for your advice but I already tried above. I didn't have any problems/trouble connecting my Verizon Tab and Galaxy S phone to the computers to change the roms. There is most likely something wrong with the Tab. I gave up and contacted Samsung yesterday. I sent the Tab to them yesterday and hopefully they won't charge me to fix it.

[Q] SGS Problem That Nobody Can Fix?

The main Samsung Approved Service Center here in Kenya has just given up on my SGS 1900 UK Model Nov 2010, originally 2.1 firmware upgrade via KIES to Froyo 2.21 in March 2011. They have handed it back unfixed after a week. Cant find a problem like this on any forum/google. Can find one that is fixable with the resistor jig, but Samsung dealer says his jigs don't help:
1) Press power, on comes B&W Samsung GT I900 screen, then the mosaic graphic that resolves to the glowing big "S". Then it buzzes feebly. Eventually it goes black but keeps buzzing now and then. Power off works.
If you poke around trying to get it into 3 touch reset, the Menu and Back keys light up and stay lit.
2) 3 Touch reset will not work. Dunno if it ever did as never tried before.
3) Plug into USB charger, it charges fine and shows the charger icon.
4) Plug into KIES and after a lot of attempts, KIES identifies it + firmware and connects. I can see and save my contacts and it displays CONTACTS, INTERNAL SD and CALENDAR folders in KIES. No more
5) ODIN ( which I dunno how 2 use but have) sees the SGS's COM when I plug it to my comp.
6) The dealer claims to have tried to resart/reflash with Samsung jigs. He has handed it back with a "cant fix".
What the heck is going on here? Looks like I have lost a few hundred bucks and have to throw it away.
When did this start? Phone was working perfectly. Suddenly a solid red icon with large white star labelled "Web Page" appeared on home page but no such App was found in SETTINGS>ETC. In any case, "Web Page" just led me to a totally innocuous page I use all the time as a homepage on INTERNET app. A few starts and shutdowns after that ( the battery was getting low so swx'd on and off like 3 times over an hour), it just went into (1) above.
Phone is STOCK, no mods, no reflashes,no rooting etc
Thanks
Peter in Darkest Africa
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. Get your phone into download mode by pressing volume down+menu button+power button until you get the yellow screen showing the android working. then open odin 1.7 and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
flash Darky Rom 10.1 with JVO Modem . Best GPS i´ve ever had, and my GPS was really bad.
frostygenius said:
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. then open odin and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
Click to expand...
Click to collapse
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Ok, I dunno if this is gonna help but I had a very similar issue when I first got my phone, within a week of owning it.
Points 1-3, exactly what happened mine.
Points 4 & 5 I didn't try, (was fairly new to Android)
Left it in to my local Vodafone shop & within 5 days I had it back in perfect working order, the maintenance report stated faulty hardware, the display module had to be replaced. Maybe worth mentioning to the service guy?
R34L2Pac said:
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Click to expand...
Click to collapse
Thanks for the heads-up I forgot to mention those points. I've updated my original post.
Sent from my GT-I9000 using Tapatalk
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Yes you are correct, I can't get download mode. The phone has never been reflashed or messed with. It came with 2.1 and using KIES in March I reflashed to 2.2 and it worked perfectly for 10 weeks until it semi-bricked.
There is the Black Screen of eath...then there is the pulsasing S screen of limbo! That's what I have.
The only harwdare clue I have is the SGS blew the fuse in my car charger shortly before "expiring"...yet if connected to USB or other charger, it charges the battery and displays the logo.
peterg123 said:
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Click to expand...
Click to collapse
..But download mode doesn't display the S logo or even the first Galaxy S 1900 logo...it goes straight in.
Try looking up in the Development section - I'm sure there is a jig method in there and it might be worth trying yourself, you've not got mush to lose now.
If you can get into download mode eventually, search for and flash Ezbase, that will get you onto a rooted firmware and it works EVERY single time for me. Good luck.
@R34L2Pac
Hi, thanks. As posted, the stock UK model SGS 1900 with 2.1 Eclair worked perfect from Nov to March 2011, was firmware upodated by KIES in March 2011 to 2.2.1 Froyo and worked like a dream until it went "semi-bricked" with the "Logo of Limbo" screen ( the pulsating giant S) for no reason.
A week before this, I changed SIMs when I changed countries and for some reason lost all added apps. I had to re-install them and even then, sometimes twice as I got many "android process stopped" errors --- even on some of the Sansung installed ones like Layar. That is the only problem I ever had.
The phone has only had apps from Market and never been modded whatsoever. Many thanks
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
R34L2Pac said:
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
Click to expand...
Click to collapse
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Try en carefully learn hw to use odin coz I gt tha same exact model. I hav flashed mine many tyms en am on 2.3.4 XXJVP. if u do gt into download mode odin will sort u. Regards frm K.poly.
Sent from my GT-I9000 using XDA Premium App
peterg123 said:
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Click to expand...
Click to collapse
how long have you tried holding down the 'volume down+menu+power' keys? a simple quick press of the three buttons does not work. you have to keep holding them all down for a bit (sometimes upto to 15-20 seconds) for it to go into download mode.
Sorry for the fast answer but I'm at work atm... I think he needs to do the 3 combo button fix on his phone first. I know it's on the forum somewhere... Can anyone check it for him? I lost the 3 combo the first time I updated with Keys from 2.1 to 2.2 and I had to fix it using a program that I can't remember to go on download mode and apply that fix.
Then he can use Odin to flash a stock rom as he needs, plus having 3 combo fixed!
Good luck mate!
Sent from my GT-I9000 using XDA App
Possible fix for your problem
Hi peterg,
I was looking through the general forum and found this post, where user beamzuk1 describes method how he fixed his semibricked phone. Symptoms are the same (not booting, glowing soft-keys, vibrating, no recovery and no download mode). So he used 'adb reboot recovery', I would say that proper command is 'adb reboot download', but you can try both. Also go through guide HOWTO use ADB, which I posted here the link in earlier post.
Hope this will help.
PS: Try follow beamzuk1 step-by-step, because if you start phone earlier than you connect it to pc, adb might not recognize the phone. Also be sure that you have correctly installed drivers and android-sdk before you try this.
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
LiverpoolFCfan said:
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
Click to expand...
Click to collapse
+1
Also think that Samsung should repair it or replace it.
The fact your repair center has done nothing to fix your phone, in several occasions, now entitles you to brand new replacement or your money refunded in full, contract terminated and expenses paid for your losses incurred as a result of their negligence.
Why not hit them up for the SGS 2.
I had the same issue with my first Galaxy S...wifi stopped working at first, I turned it off then on again but nothing changed. So I rebooted to see if it would correct itself. Bootloops and no 3 button combo (download or recovery)
Sent it off to Samsung through the Carphone Warehouse in the UK. I'd contact a Samsung Service Centre directly if I were you.

Unbricked a Hard Bricked Captivate - Truly Invincible Phone - No JTAG

Past few days were the worst for me as I had Hard Bricked my Captivate.
*** History*** (You may skip this is you wish)
This all started few days ago, like every cappy owner I too had a craze of testing different Roms, untill i settled for RemICS. But soon after a month I got bored and moved to Nostalgic 6.2. The rom looks good, but then when I called someone, there was a lot of static on the line and the other person could not hear me. So I decided to try a different modem, so I installed a different modem and things went back to normal.
Later I found another post on XDA, a comparision table for different modems on captivate. So i wanted to give a try, & this is when things started to get rough.
I installed a few modems and then found that my mobile would not get any network signal. So I planned to use ODIN One-Click (I897UCJF6-final-OCD-REV0) and go back to factory. I used ODIN and was able to go back to factory and everything was back to normal.
***When & How I Messed up my Cappy***
As I was back to Factory (2.1) I wanted to upgrade it to GingerBread. I used Samsung Kies to update it to 2.2 Froyo and while this happened, Kies downloaded the firmware, however while flashing the phone it was stuck at 3% and was there for about 4 hours and wouldnt move further, and the screen was solid green and no images or characters. So I took the risk and manually killed Kies and rebooted the phone. Now the phone would come to AT&T screen and was stuck there, tried the firmware update again and still had the same issue. This is when I decided to go back to Factory using ODIN. Used Odin to flash the phone again and it wouldnt move ahead of Factoryfs.rfs and would be stuck there for hours. So I took the risk and disconnected the cable (I know there is a risk of hard brick, but I trust this phone so much and was impatient to give it another go) and restarted the process. It again did the same thing, but this time the phone shutdown and was on a Black Dead screen. I disconnected the phone and tried to put it to download mode and it wouldnt work. The phone would just not show any signs of life. Connected the charger to check if there is any display and still had a dead screen & no sound. ODin would not recognise the phone anymore and no signs of any PCI device in device manager. Even tried Heimdal and still no go. Tried this for the whole day and i was preety satisfied that this might need JTAG.
I had also left a post for connexion2005 on http://forum.xda-developers.com/showthread.php?t=1041042
By now I had started to surf ebay looking for another Cappy or Infuse. All the signs that the phone gave me were of a Hard Bricked Captivate. However I did notice that if I reseat the battery and then try to power ON the phone, there was no sign of life, but after leaving it for 20 minutes the phone would get a little warm. So I knew that the phone was still alive, just a no video/no post kind of situation.
It was 11:00 pm when it just struck to me that I should try Linux, as there was a faint possibility that Linux may recognise the phone if it was in any kind of life mode.
So i grabbed a copy of Ubuntu and installed it on the same laptop, where the phone showed no life and used the same usb cable. Well once the OS was installed all I did was tried using the Vol UP + Vol Down + USB to put it into download mode and to my surprize the phone immediately went into Download Mode and there was display. :good::good::good::laugh::good::good::good:
Then I just flashed the phone with ODIN and went back to factory........ and everything is back to normal. :laugh::laugh::laugh:
I wouldnt be trying to brick the phone again, but if anyone has a hard bricked phone can definately try this and hopefully should be able to boot back. Please let me know if it wokred for you.
I am not sure if this is the right section to post this but, definately it worked for me where the phone showed all the symptoms of a Hard Bricked Cappy. If the moderators feel it should move to a different section, please feel free to move it.
I am now convinced that Captivate is Immortal...... :angel:\m/:angel:
Please use the Thanks:good: button if this worked for you.:good:
I may not be able to recreate the issue and havent captured any images, but if you have a dead cappy, you can definitely try this and let me know.
Glad your phone got fixed, thanks for taking the time to write it. I'd suggest moving it to captivate general though. This is the development thread.
You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
fohdeesha said:
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
believe it or not my cable got pulled out right in the middle of the factoryfs and since i cud still enter download mode i tried it again and then my power got cut in boot.bin part, and i was actually still able to boot into download mode even when nothing showed up on my screen, all i did was first pull the battery, hold the down and up volume button, insert usb into phone and insert battery, and somehow it booted into download mode according to odin, so idk the phone may not be invincible, but its close
fohdeesha said:
You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
And unbrickable mod fixes this. Therefore the captivate is pretty much immortal. You can even take a hard bricked cappy, do the unbrickable mod once it's already broken, and still have it return to working order.
Way say you now?
Arisenhavok91 said:
Way say you now?
Click to expand...
Click to collapse
What*
I would say of course JTAG'ing a hardbrick is capable of unbricking it, same for about any other device in the world with volatile memory based firmware. this is not a magical new discovery.
They aren't called hard bricks because they become impossible to recover, corrupting bootloaders is called a hardbrick because it takes HARDware modification to fix, not software utilizing the preexisting hardware. Anything else? Anyone else have some wonderful insider info as to how linux can make download mode magically appear? I'm loving the knowledge in here, really. If you're going to spread misinformation, we please ask that you do it in the correct subforum.
Of course, I argued that the Samsung Captivate is "immortal" due to it's ability to be resurrected at times when even a JTAG would fail.
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Edit: If you can't take someone poking fun as such, please don't bother to respond. I won't look back at this even if you do reply, so please, take a chill pill... or some midol.
Arisenhavok91 said:
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Click to expand...
Click to collapse
I would continue to say the captivate is far from immortal, in the same context as my original post you seem so excited to quote - in a software recoverable situation. We are not talking about JTAG and hardware modification anywhere in this thread. he was claiming the captivate is immortal in regards to all situations being software recoverable by magically switching to a different OS, if you could please put on your reading comprehension and context goggles the pieces of the puzzle might start coming together. Also, do not ask questions you won't bother reading the answer to. Thanks!
I say the captivate is pretty much inmortal! xD even without power button ive been using it with no problem and getting into DLmode.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

Really Bricked my new Galaxy Tab 2 7 inch. I have tried everything :(

Hello, I so hope someone can help. I just updated my galaxy tab 2 7 p113 to Android 4.0.4 UEBLH2. That was done automatically from samsung. I wanted to then install the newest update to 4.1.1 jellybean. So I downloaded it from this link. http://www.trickytweaks.com/update-...ecli4-4-1-1-jelly-bean-ota-test-firmware.html. I put the official Android 4.1.1 UEBLH2 Firmware on my sdcard then held down my power and up volume and installed it. HOWEVER, it never finished installing. Went all the way to the end. Now I HAVE NO USB CONNECTION and NO BOOT UP. Just black Since I dont have usb connection I cant us oden. CAN ANYBODY PLEASE HELP? I still can put files on my micro disk card and then put sd disk in my tab and use the power button up arrow to install something but I tried installing clockwork mod but that did not work. Iam out of ideas. P.S. My tab IS NOT ROOTED. I tried updating back to and original rom 4.04 I download but that did work. Thank you.
I think you need to enter the download mode volume down+power or recovery mode volume up+power to be able to restore the tab
Try multiple times close the tab even with long pressing power then try the button combinations (press both for multiple seconds) and release to see if you could enter any mode
If you reached download mode try flashing stock firmware for your tab specific model 3113 or 3110 or 3100 via odin (install kies and reboot before)
If you reached recovery (stock) then connect with kies and choose recover firmware from kies options (near the word file in top) you should have active internet connection
You could try charging tab even for some hours before trying button cobinations
If not try to return as not rooted so warranty is goood
Sent from Galaxy S2 or Galaxy Tab2
Mohamedselim said:
I think you need to enter the download mode volume down+power or recovery mode volume up+power to be able to restore the tab
Try multiple times close the tab even with long pressing power then try the button combinations (press both for multiple seconds) and release to see if you could enter any mode
If you reached download mode try flashing stock firmware for your tab specific model 3113 or 3110 or 3100 via odin (install kies and reboot before)
If you reached recovery (stock) then connect with kies and choose recover firmware from kies options (near the word file in top) you should have active internet connection
You could try charging tab even for some hours before trying button cobinations
If not try to return as not rooted so warranty is goood
Sent from Galaxy S2 or Galaxy Tab2
Click to expand...
Click to collapse
Yup, this should get you going again. If you can get into download mode, you should be okay. That's what Odin needs.
Download mode is volume down plus power. Then volume up
Recovery mode is volume up plus power.
I want to thank both the posters on trying to help me. I did hold down the power and download button and it went in to the download mode. HOWEVER, since I can not access usb it did not do anything. Just kept saying downloading. As I mentioned in my first post I CAN ACCESS MY SD DISK FILES by doing the power up button thing. Thats the only way I can get files on. But the DOWNLOADING down arrow just does not do anything. hmmmmmmm will keep plugging away.
I can not understand how you can not access usb, is it a lacking driver so download kies and reboot and try connect again ,also try a different usb ports (esp the rear of case) of your computer
Was usb working before the problem?
do you have cwm or stock recovery?
If cwm so download cm10 or cm9 from www.teamhacksung.org and put in usb card and flash but do a cash delete and dalvik delete afterwards not for boot loop
If stock so try stock firmware from www.samfirmware.com (register their first) and put in sd card and try to flash
Sent from Galaxy S2 or Galaxy Tab2
growthweb said:
I want to thank both the posters on trying to help me. I did hold down the power and download button and it went in to the download mode. HOWEVER, since I can not access usb it did not do anything. Just kept saying downloading. As I mentioned in my first post I CAN ACCESS MY SD DISK FILES by doing the power up button thing. Thats the only way I can get files on. But the DOWNLOADING down arrow just does not do anything. hmmmmmmm will keep plugging away.
Click to expand...
Click to collapse
I think you're misunderstanding download mode. When you get the device in download mode, connect it then to the computer, with Odin open. The only reason Odin wouldn't recognize it would be a driver issue. In that case, do as the previous poster stated. When you're in download mode, you're strictly flashing through Odin. You aren't going to see the device as a storage device on the computer. The only way your computer can interact with it at this point is Odin. Via Odin, flash the proper p3113 firmware file from sammobile/samfirmware (will be a large 600mb+ file). Once that's done, you should then be back to completely stock and healthy recovery and ROM. Reboot tab and see what happens. If it boots, and you still want to update, then make sure you get the correct ota for the base file you just flashed (that is, if you're trying to upgrade to say Jellybean). If you need more help always ask, but you should be fine. If I lived nearby I'd do it for you.
All I can say is unbelievable help here! Thank you. I am spending hours on this (plus a fortune on this new Tab 2 7). After studying up I do now understand how Odin works and how grabbing the correct firmware will do the job. HOWEVER (maybe others come across this huge roadblock) nothing can be done with out usb interaction. I DID DOWNLOAD KIES and installed it. But no matter what I do can not get any storage device listed or anything going on between tab and computer. Only thing my Tab does is when I plug it in to the computer via usb is go in to charging mode with the charging icon showing. Loading Odin does not show any connection. I have tried different computer USB plugins, 3 different computers (all I have loaded Kies on). Iam sooooooo close. If only while in the POWER BUTTON DOWN ARROW DOWNLOAD MODE and running ODIN on my computer there would be a connection I would be home free and able to flash firmware.
dictionary said:
I think you're misunderstanding download mode. When you get the device in download mode, connect it then to the computer, with Odin open. The only reason Odin wouldn't recognize it would be a driver issue. In that case, do as the previous poster stated. When you're in download mode, you're strictly flashing through Odin. You aren't going to see the device as a storage device on the computer. The only way your computer can interact with it at this point is Odin. Via Odin, flash the proper p3113 firmware file from sammobile/samfirmware (will be a large 600mb+ file). Once that's done, you should then be back to completely stock and healthy recovery and ROM. Reboot tab and see what happens. If it boots, and you still want to update, then make sure you get the correct ota for the base file you just flashed (that is, if you're trying to upgrade to say Jellybean). If you need more help always ask, but you should be fine. If I lived nearby I'd do it for you.
Click to expand...
Click to collapse
growthweb said:
All I can say is unbelievable help here! Thank you. I am spending hours on this (plus a fortune on this new Tab 2 7). After studying up I do now understand how Odin works and how grabbing the correct firmware will do the job. HOWEVER (maybe others come across this huge roadblock) nothing can be done with out usb interaction. I DID DOWNLOAD KIES and installed it. But no matter what I do can not get any storage device listed or anything going on between tab and computer. Only thing my Tab does is when I plug it in to the computer via usb is go in to charging mode with the charging icon showing. Loading Odin does not show any connection. I have tried different computer USB plugins, 3 different computers (all I have loaded Kies on). Iam sooooooo close. If only while in the POWER BUTTON DOWN ARROW DOWNLOAD MODE and running ODIN on my computer there would be a connection I would be home free and able to flash firmware.
Click to expand...
Click to collapse
How about you just gtalk me, lol. I'll probably reply faster there anyway. deliberation at gmail dot com.
Don't use kies. Install the Samsung driver for mobile phones (Google it).
Sent from my GT-P5113 using Tapatalk 2
Download Mode
growthweb said:
All I can say is unbelievable help here! Thank you. I am spending hours on this (plus a fortune on this new Tab 2 7). After studying up I do now understand how Odin works and how grabbing the correct firmware will do the job. HOWEVER (maybe others come across this huge roadblock) nothing can be done with out usb interaction. I DID DOWNLOAD KIES and installed it. But no matter what I do can not get any storage device listed or anything going on between tab and computer. Only thing my Tab does is when I plug it in to the computer via usb is go in to charging mode with the charging icon showing. Loading Odin does not show any connection. I have tried different computer USB plugins, 3 different computers (all I have loaded Kies on). Iam sooooooo close. If only while in the POWER BUTTON DOWN ARROW DOWNLOAD MODE and running ODIN on my computer there would be a connection I would be home free and able to flash firmware.
Click to expand...
Click to collapse
Once you are in download mode, connect your tab to the computer with the usb connection.....you should see a com xx number pop up in Odin in yellow reporting your device is connected thru a communication port. From there you will be able to choose the file you want as a PDA uncheck everything else...reboot...reset timer....whatever. Just make sure you have the correct firmware. There is a Odin flashback to Stock rom in the development section. Make sure it's for your device. Once you start Odin, should take about 4 mins...disconnect and hold the power button down to reboot. That's it....
Hello Everyone Again, I just want to say thank you for all of you who took the time to help. I hopefully will become knowledgeable enough to help people in the forums as I gain knowledge. I finally did find the solution. I did everything that was mentioned. And no matter what what I did with KIES drivers Samsung usb drivers, etc could not get a connection so I could us Odin to keep me back to the orgiginal 800 mb 4.04 original file. My solution was (as mentioned) I deleted all my windows drivers dealing with usb, kies, etc. Then rebooted. I notice even though I did not have a direct usb connection showing up now Odin was showing a connection! So using Odin I got to restore everything and now back to like new. Lesson learned. Hope this helps others that almost fatally brick their tablets. Thanks again for all our help
growthweb said:
Hello Everyone Again, I just want to say thank you for all of you who took the time to help. I hopefully will become knowledgeable enough to help people in the forums as I gain knowledge. I finally did find the solution. I did everything that was mentioned. And no matter what what I did with KIES drivers Samsung usb drivers, etc could not get a connection so I could us Odin to keep me back to the orgiginal 800 mb 4.04 original file. My solution was (as mentioned) I deleted all my windows drivers dealing with usb, kies, etc. Then rebooted. I notice even though I did not have a direct usb connection showing up now Odin was showing a connection! So using Odin I got to restore everything and now back to like new. Lesson learned. Hope this helps others that almost fatally brick their tablets. Thanks again for all our help
Click to expand...
Click to collapse
Glad you got it sorted.
i jus did the same thing u did
hi how r u doing. i jus did the same mistake u did and i really need your help please
Maxwell255 said:
hi how r u doing. i jus did the same mistake u did and i really need your help please
Click to expand...
Click to collapse
Hi.if u have done the exact same thing then just read the previous page and comments.
Sent from my GT-P3110 using xda app-developers app
Glad to see you resolved your issue. In the future, question/help threads belong in Q&A only.
Thank You.
Because your issue has been resolved...
Thread Closed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
PeartFan40 said:
Glad to see you resolved your issue. In the future, question/help threads belong in Q&A only.
Thank You.
Because your issue has been resolved...
Thread Closed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Click to expand...
Click to collapse
Thread is still actually open, lol
Is there any way to save my tablet if there is NO firmware out?
Im talking about the SCH I705, I followed the root guide, and it got ****ed up.
Unable to boot into recovery (it goes to Odin "could not do normal boot.")
Tablet seems unresponsive sometimes (to power on/off)
Will boot cycle occasionally
???????????????????
igotbricked said:
Is there any way to save my tablet if there is NO firmware out?
Im talking about the SCH I705, I followed the root guide, and it got ****ed up.
Unable to boot into recovery (it goes to Odin "could not do normal boot.")
Tablet seems unresponsive sometimes (to power on/off)
Will boot cycle occasionally
???????????????????
Click to expand...
Click to collapse
You have to reflash your tablet using ODIN. It's not that hard. Just follow the second method here (you don't need to download android SDK)
copy this in your navigator bar : rootzwiki . com/topic/37272-verizonsch-i705-root-for-all-current-firmware/ ( delete space around the dot)
Plus, your tab will be rooted.
You're welcome.
P.S : This limitation of URL is annoying as hell.

Categories

Resources