Database Users

[HELP] Is my vibrant completely bricked?

Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?

this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App

merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.

skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?

cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.

yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??

rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)

ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it

rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.

skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B

vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.

I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this

Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.

I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help

Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7

Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.

Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App

May god bless you and your children, and your childrens children, and their children!!!!!!!!!

[Q] Double wammy, boot loop and clockwork fail

I am on root on 2.2 with Dk28 and epic all in one.Yesterday I decided I wanted to put baked snack on my phone. Everything went great and was working so i decided to install step 2 to get better battery life and I shut down to boot into clockwork. Therein started my problems. It refused to boot in to clockwork, so i tried to boot back up and it wont get past the Samsung with their .com boot screen (sorry first post cant post the full screen due to url). I have nandroid backups but cant make use of it as clockwork wont boot up. Drivers were originally working fine on my pc but overnight they got screwed up. (they working now on my other pc)Before that i tried to use odin to reset with the .tar file pda method and it said invalid image file and wouldnt work. Please leave suggestions as i dont know where to go next. I am working on a new pc now and will try after download, running dsl and slowgoing. Currently my phone is a break

irule9000 said:
I am on root on 2.2 with Dk28 and epic all in one.Yesterday I decided I wanted to put baked snack on my phone. Everything went great and was working so i decided to install step 2 to get better battery life and I shut down to boot into clockwork. Therein started my problems. It refused to boot in to clockwork, so i tried to boot back up and it wont get past the Samsung with their .com boot screen (sorry first post cant post the full screen due to url). I have nandroid backups but cant make use of it as clockwork wont boot up. Drivers were originally working fine on my pc but overnight they got screwed up. (they working now on my other pc)Before that i tried to use odin to reset with the .tar file pda method and it said invalid image file and wouldnt work. Please leave suggestions as i dont know where to go next. I am working on a new pc now and will try after download, running dsl and slowgoing. Currently my phone is a break
Click to expand...
Click to collapse
Which tar are you flashing..whats the filename?
also have you checked to make sure it downloaded correctly without corruption via md5checksum?

checksum and tar
i used this page i used thread number 794138(cant post links) by whosdaman. I tried using dk28 and di18, Dk28 got checksum and di18 got invalid image. I just downloaded a new tar for dk28 and am currently trying odin on a different computer

Let us know what happens,I'm here to help for atleast 2 more hours.
Sent from my Frankenstein FROYO ROM using XDA App

dk28 got checksum, working on di18, i hate you dsl

irule9000 said:
dk28 got checksum, working on di18, i hate you dsl
Click to expand...
Click to collapse
any updates man?

hash dash invalid
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> SPH-D700-DI18-8Gb-REL.tar.md5 is invalid.
<OSM> End...

Clockwork fixed
Goodnews bad news, I fixed clockwork and flashed clockwork backup, still wont boot tho

irule9000 said:
Goodnews bad news, I fixed clockwork and flashed clockwork backup, still wont boot tho
Click to expand...
Click to collapse
*Assuming that you want to return to the current official build used by sprint which is at this moment DI18*
*Assuming your phone can power up at all (if it doesn't there's a trick you can try for that mentioned elsewhere in the forums)*
*Only use main/direct-to-motherboard USB slot on PC (not on the face of your PC)*
*Only use high quality USB cable shorter than 3' and not the stock cable*
*Make sure SAMSUNG USB drivers are Installed*
*Make sure your battery is more than 50% charged*
1. SD Card is REMOVED, USB is UNPLUGGED and Battery is REMOVED from phone
2. While Phone is UNPLUGGED from USB, place battery in phone
3. Press and Hold the "1" key and Power button together to reach Download Mode
*KEEP USB UNPLUGGED FROM PHONE and phone in Download Mode*
4. Extract and Run Odin3.exe (Ignore the .pit file included in Odin3+v1.61andepic.pit.zip)
*Leave the "PIT" selection empty*
5. In Odin Uncheck "F. Reset Time", make sure "Auto Reboot" is the only box checked
6. In Odin click PDA and select your .Md5 file (SPH-D700-DI18-8Gb-REL.tar.md5)
7. Plug USB in PHONE and wait for yellow COM box highlight to appear in Odin
8. In Odin Press Start and WAIT patiently
Download SPH-D700-DI18-8Gb-REL.tar.md5 from the link on the first page of this thread where it says DI18 Update:
http://forum.xda-developers.com/showthread.php?t=794138
Download Odin from the link on the Wiki --look for "Odin3+v1.61andepic.pit.zip" under where it says "Odin Stock Flashing" at:
http://forum.xda-developers.com/wiki...Stock_Flashing
Download Samsung USB drivers from the link on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=770388

fck me
I really shouldnt have screwed with odin while tired and pissed. Lost clockwork mod and tried again. Now im stuck with a paperweight that can go into download mode or boot to a screen that shows an old flip phone triangle with an exclamation mark and a pc/laptop. If anyone knows what that means, please post

I've reached that screen 3 times and twice I've been able to get my phone back out of it (not something I'm exactly proud of).
try:
1. Remove sd card and battery and unplug USB
2. While first holding 1+Power button, re-insert the battery
and if that doesn't work try it with the USB first plugged in.
next try
1. remove battery and sd card
2. insert USB
3. press and hold down vol up + vol down (not power) and Replace battery
next try
1. remove battery sd card
2. plug in USB
3. re-insert battery
4. hold power + vol down only
and lastly try
calling sprint or samsung repair as applicable and plead complete ignorance as to how it happened and any knowledge of smart phones and android beyond what's in the basic user manual. Say something like "It was like that when I woke up"
that seems to be the certain solution for this problem from what I've read.

I see ur problem rename ur .tar.md5 file to just .tar you might have to enable extensions to be seen. I don't remember how I did it but I remember googling something like how to enable file extensions. If you successfully rename it you will get a warning and just click ok on it or whatever enables you to change the extension.then use that file in odin.
Sent from my SPH-D700 using XDA App

The flip phone triangle thing was something I had too. Make sure ur tar file is some where around 150mb to 200mb. The first time download my tar it was like 5mb for some reason
Sent from my SPH-D700 using XDA App

I tried the tar thing it worked better but im having issues with drivers and connection issues with odin. Its working better but im getting stuck at pram or something like that

Sry I really can't help you much more. I'm not a dev so I really don't know. I only speak from experience. Also you should be more specific I posted two things about the tar file.
I also checked how big the tar should be and it is 255 mb
Sent from my SPH-D700 using XDA App

i hate my phone
Every time i fix one problem another appears. My computer wont see my phone. The drivers are fine as my brothers epic 4g appears as normal. It seems that something in the phone is messed up. I have no other computer to test it on. Help me fellow xda members, what should i do.

Are you using the same cable thst your brother used? I couldn't get my computer (or a second one ether) until I used my wife's cable.
George
Sent from my SPH-D700 using XDA App

i tried about 5 different cables, but now for some reason im getting the original recovery? to load. Its really wierd, when i leave the phone something happens even when it is off. is there anyway to restore from the original recovery. Is there anyway to mount an sdcard without loading the phone. I dont have clockwork, but i have an update.zip file on my sd and i want to see if it will load anything. Unfortunately i took it out under the directions of someone else and the phone wont remount it. I was wondering if there is a way to trick the phone to remount it allowing to do the update via stock recovery

I'm sure that would be possible via adb...but I'm not well versed in that lol
Does your phone connect to the computer at all anymore?
Sent from my SPH-D700 using XDA App

thank you all the help. You guys were correct, i had an extension problem. After erasing md5 i was able to use odin. This was after i got lucky and my computer saw it as a modem on my much higher quality microusb. Im in the middle of a nandroid restore bringing back from stock di18 to good old dk28. Thanks all for help.

[Q] Stuck with phone ! pc screen. Help?

I was using Odin to install [KERNEL] stock+Voodoo stable 5.x for Vibrant and something went wrong, I'm not sure what but now I am stuck with the phone ! pc screen.
Odin will not recognize that there is a phone there if I just start a download Odin tells me <OSM> All threads completed. (succeed 0 / failed 0)
In another thread (whose fix didn't help me out) I read
masterotaku said:
Because..... "Phone ! PC" is not a hard brick. I've "Phone ! PC" bricked my Vibrant dozens of times.
Glad you've recovered though. It can be a scary screen if you're not used to seeing it!
Click to expand...
Click to collapse
Are there other recovery techniques?

Did you get where it says Download Mode? If not, take the battery out, put it back but don't turn on the phone. Then open Odin load the pit files and pda. The next step with the phone off, hold the volume up and down the same time and plug the usb cable while holding up and down buttons and voila....you will have COM # showing up in your Odin and ready to flash again
Check here :http://forum.xda-developers.com/showthread.php?t=810130&highlight=odin

dany865, following your instructions Odin did recognize that there was a phone attached. 0:[COM5] and I'm flashing the PIT and PDA from the thread you linked me to now. It's a slow moving process!
So slow that I swear it was frozen so I took and chance and closed ODIN, after all what was the worst that could happen I was already staring at a brick, and rebooted the phone. PRESTO, it was back to JI6.
I went straight to MiniKies and put 2.2 on that phone, then spent a bunch of time reinstalling applications and configuring ADWlauncher.
So far all I know for sure that was lost was my finely tuned setup, root access, and a month of SMS messages that were not backed up.
Thank you!

I you are gonna root I would highly recommend to get "Titanium backup pro". It makes the setting up process 10x's faster and has a tin of other great features.

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

[i9505]I think I've hard bricked my phone

Hi guys,
So apparently I did a very stupid thing today. I have a MAC and a Windows 7 on my bootcamp. I've downloaded the firmware for my country (Philippines) from sammobile link: http://hotfile.com/dl/234886746/526112d/GLB-I9505XXUBMG5-20130710140005.zip.html.
I've used heimdall(basically odin for linux/MAC) and if you're familiar with it you actually need to extract the .tar files and flash them one by one on heimdall whereas on odin you just put it on PDA.
Here's what exactly what I did:
1. Booted to download mode(obviously)
2. I then fired up heimdall and added the pit file which I've downloaded from my device. Again if you're familiar with heimdall, you actually need the pit file everytime you flash unlike odin.
3. This is the part where I think I've screwed something up, I've flashed these files which I've extracted from the MG5 .tar file:
- modem.bin
- NON-HLOS.bin
- boot.img
- recovery.img
- aboot.mbn
- cache.img.ext4
- hidden.img.ext4
- rpm.mbn
- sbl2.mbn
- sbl3.mbn
- system.img.ext4
- tz.mbn
According to heimdall the flash was successful and immediately exited download mode. This is the part when the phone was supposed to reboot but it didn't. The blue led was lit and the phone is not rebooting at all so I manually rebooted it via the power button. Now the phone is not booting at all. Literally no power.
I cannot enter recovery mode and the worse part, I cannot enter that damn download mode to try and re-flash the firmware again. The phone has about 90% charge left before I rebooted manually. Also the phone is not charging. I mean even if it's turned off it should charge with the charging animation to indicate that it's charging or the led is lit up, but in this case there was no led lit up nor the charging animation.
I'm quite frustrated right now and I know I should have used ODIN considering that I have bootcamp with Win 7 installed, but I did it for testing purposes and I paid the price and ended up with a $650 brick
Now I know I'm screwed and have probably voided my warranty by doing all this but I just wanna know where did it go wrong or is there something else that I could do before I send it for repairs?

Honestly ... Go back to shop and tell them that Kies told you that there is an update ... and after the phone havent start ...
Or try like this:
Pull out the battery
Plug USB
Hold volume up
and plug the battery
Should see it.. if not try with JIG to enter in download mode

spinky360 said:
Honestly ... Go back to shop and tell them that Kies told you that there is an update ... and after the phone havent start ...
Or try like this:
Pull out the battery
Plug USB
Hold volume up
and plug the battery
Should see it.. if not try with JIG to enter in download mode
Click to expand...
Click to collapse
Yeah I'll go to the shop tomorrow, just wanting to know if there is something else that can be done as the repairs could take months.
There'll be no way for them to know what actually happened and if I'm lucky I would still have warranty and not pay any single cent lol. I'm guessing that they'll replace the motherboard or sumthin. Thank you anyway I'll try that

perhaps your file is corrupted.
even if redownload the firmware and use odin to check the MD5 sum.
you must do your self a JIG usb dongle to force the download mode on your phone.
hope that help you.

mkh.mourad said:
perhaps your file is corrupted.
even if redownload the firmware and use odin to check the MD5 sum.
you must do your self a JIG usb dongle to force the download mode on your phone.
hope that help you.
Click to expand...
Click to collapse
Maybe, but I'm pretty sure it won't hard brick the phone even if it's corrupted. Worst case scenario is that it would be a soft brick. Jig will probably work but I don't have access to it.
Something might have gone wrong on the way I've flashed it via heimdall. I've probably messed up and accidentally flashed the wrong pit(but I'm pretty sure I didn't) or probably the bootloader. Anyway I'll just save myself the trouble and just send the damn phone for repairs and suck up the 1 month wait. I just hope that they won't void my warranty. Not much I can do really.

chickentuna said:
Maybe, but I'm pretty sure it won't hard brick the phone even if it's corrupted. Worst case scenario is that it would be a soft brick. Jig will probably work but I don't have access to it.
Something might have gone wrong on the way I've flashed it via heimdall. I've probably messed up and accidentally flashed the wrong pit(but I'm pretty sure I didn't) or probably the bootloader. Anyway I'll just save myself the trouble and just send the damn phone for repairs and suck up the 1 month wait. I just hope that they won't void my warranty. Not much I can do really.
Click to expand...
Click to collapse
Take an usb cable and make a JIG... Less then 1 min to make it
Sent from my GT-I9505 using xda app-developers app

chickentuna said:
Maybe, but I'm pretty sure it won't hard brick the phone even if it's corrupted. Worst case scenario is that it would be a soft brick. Jig will probably work but I don't have access to it.
Something might have gone wrong on the way I've flashed it via heimdall. I've probably messed up and accidentally flashed the wrong pit(but I'm pretty sure I didn't) or probably the bootloader. Anyway I'll just save myself the trouble and just send the damn phone for repairs and suck up the 1 month wait. I just hope that they won't void my warranty. Not much I can do really.
Click to expand...
Click to collapse
---Repair dead boot I9505 via usb cable---
QHUSB Qualcomm driver download

samersh72 said:
---Repair dead boot I9505 via usb cable---
QHUSB Qualcomm driver download
Click to expand...
Click to collapse
This is just in case that his pc is geting signal from phone
Sent from my GT-I9505 using xda app-developers app

spinky360 said:
This is just in case that his pc is geting signal from phone
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
it will help also to get into download mode :good:

samersh72 said:
it will help also to get into download mode :good:
Click to expand...
Click to collapse
If his eMMC is not giving signal to start QHUSB ... Is useless
Sent from my GT-I9505 using xda app-developers app

samersh72 said:
---Repair dead boot I9505 via usb cable---
QHUSB Qualcomm driver download
Click to expand...
Click to collapse
Thanks but it didn't work. It gave me a little hope though no harm in trying. Really not sure if jig will work but one thing is for sure, I now have a $650 paper weight.
I just hope that the samsung guys won't be able to bring this back to life. I hope that they just replace the motherboard straight away because if they are able to resurrect the phone, I'm screwed. They will find out that I've modified it. Worse part is I will need to shoulder the repair costs which I wouldn't want if they void the warranty
Sent from my Galaxy Nexus using Tapatalk 4