yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] AdamOutler:
Thanks.

I updated the jar. If you're having problems launching it, it's because I made the Ultimate UnBrickable Resurrector from source from my other project, Heimdall One-Click... I forgot to change something in the manifest at the last minute. Please redownload if it won't launch.

This should work on any device which identifies itself as an S5PC110 .... B/D. Sometimes, if you're lucky, any phone can brick itself in this state.
[Captivate Android Development] ostrianiel:
When using Virtual box, how will the phone show up on the USB list pre-Download mode download?
[Captivate Android Development] connexion2005:
It's honestly easiest if you have the time to dual boot an Ubuntu OS on your current machine. It has a major bug still but I figured out the issue and contacted Adam on the fix for it.
[Captivate Android Development] ostrianiel:
Yeah... I've spent a good bit messing with it and the settings in VB but it wont detect. (I hope it doesn't have to do with my soldering).

Ill try try the dual booting tomorrow and give it another shot.
[Captivate Android Development] AdamOutler:
Its not a bug... your computer is too old. 64bit only for now.
[Captivate Android Development] killer_raj:
great work adam.....appreciate it..though i m a riff box owner(just bought it for fun)..so wont need this mod....

but still its a great work for others....

cheerss!!!!!!
[Captivate Android Development] AdamOutler:
Why open the phone every time you have a problem? Apply UnBrickable Mod once and you will never need a screwdriver to unbrick your device. If you have spare time now, apply the modification, then use the tool later.

Btw... I have two RIFF JTAG boxes... :P
[Captivate Android Development] Rebellos:
LOL @ the understanding the way of "being lucky"

Added HIBL explanation

http://xdaforums.com/showpost.php?p=17135277&postcount=2

I'll be working 3 day in row today on win32 cmdline port. However, WIN32 drivers API is such big !@&#$*$@!&$&@. So may take abit more.
[Captivate Android Development] AdamOutler:
There is a bootloader combination which will put the phone into this mode. I don't know it though... so, lucky.
[Captivate Android Development] connexion2005:
Ok cool I'll dual boot a 64bit Ubuntu box to confirm this. I wasn't aware there were both x32 and x64 smdkusbdl tools but I didn't write this either! I just found it interesting that after replacing the suspect files in the .jar file that it worked perfectly on my "old 32 bit test mule"... ;)

Amazing work. I almost spit my drink out after using it.
[Captivate Android Development] mpencexda:
Please make this thread a sticky!!!!
[Captivate Android Development] killer_raj:
i m using cappy for almost 10 months now...but i never hardbricked my phone ...(touchwood)...:p

i never had to open my phone ..as i said i just bought the riff box for fun..and to help others....

but u r right.. for ur mod..i will hav to open my phone just once...and after that i can brick it as many times as i want.:cool:.and will never need to open it again to unbrick it....thats a plus point....
[Captivate Android Development] bulletproof1013:
I have never bricked my phone...but now I never will.
[Captivate Android Development] AdamOutler:
what does ModeDetect show?
[Captivate Android Development] funkym0nk3y:
debug mode,

windows executable shows this

and its stucked here
[Captivate Android Development] AdamOutler:
The windows drivers are crap. You need to run them a few times... try repeatedly with windows. Reset the device and try again. Windows is not a one-click because of this.
[Captivate Android Development] StrykerGT:
Hi, I'm having a problem trying to unbrick my Captivate. I followed all the instructions but I can't get the phone to boot after the bootloader installation it just shutdown. I tried this method several times without success maybe I'm doing something wrong. Any help will be more that appreciated it.

BTW as soon as I connect the phone Mode Detect finds the telephone. I can get it into download mode and Heimdall runs (I can see the progress bar on the phone). But after running for the second time the phone just power down.
[Captivate Android Development] AdamOutler:
If you checked the flash bootloaders button it will work or you will show an error message. There's instructions on the current one-click that you need to follow on Linux to make repartitioning work.
[Captivate Android Development] StrykerGT:
Yes I checked it the second time that I ran Heimdall it runs everything and you can see the progress bar running the 8 steps after is done it shows Device disconnected and nothing happens.
[Captivate Android Development] funkym0nk3y:
it doesnt works with linux too, everytime when i click on Download mode button, it just stucks @ a same place,

1 more thing, my phone gets detected in unbrick debug mode even without having the battery placed,

Please wait.... Uploading..

-------------------------------------------------------------

Hummingbird Interceptor Boot Loader (HIBL) v1.0

Copyright (C) Rebellos 2011

-------------------------------------------------------------

arch":

i686

Building command list

Building command list

Requesting Permission to access deviceSMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

S3C64XX Detect Please wait.... Uploading..

-------------------------------------------------------------

Hummingbird Interceptor Boot Loader (HIBL) v1.0

Copyright (C) Rebellos 2011

-------------------------------------------------------------

arch":

i686

Building command list

Building command list

Requesting Permission to access deviceSMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

S3C64XX Detected!

=> found device: bus 001, dev 009

=> loaded 24576 bytes from /tmp/kanishkHeimdallOneClick677C53F9/UnBrickPack/HIBL.bin

=> Downloading 24586 bytes to 0xd0020000

=> Data checksum 5d9c

=> usb_bulk_write() returned -19

failed to write 24586 bytesed!

=> found device: bus 001, dev 009

=> loaded 24576 bytes from /tmp/kanishkHeimdallOneClick677C53F9/UnBrickPack/HIBL.bin

=> Downloading 24586 bytes to 0xd0020000

=> Data checksum 5d9c

=> usb_bulk_write() returned -19

failed to write 24586 bytes
[Captivate Android Development] guilleglad:
Thank you man, i flashed the bootloaders and now it's working :)
[Captivate Android Development] b-eock:
Your welcome.
[Captivate Android Development] illusoryphoenix:
So I finally got around to checking whether libusb was installed, and it was. I tried to update it using the rpm package management in FC11, and re-tried the whole setup. Still failed the same way.

Instead, I decided to grab an Ubuntu image from the VMWare website and this time the password dialog box _did_ pop up. I entered the wrong password initially, then entered the correct one, and went ahead. The following is my output:

lease wait.... Uploading..

-------------------------------------------------------------

Hummingbird Interceptor Boot Loader (HIBL) v1.0

Copyright (C) Rebellos 2011

-------------------------------------------------------------

arch":

i686

Building command list

Building command list

Requesting Permission to access deviceSMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

S3C64XX Detected!

=> found device: bus 001, dev 007

=> loaded 24576 bytes from /tmp/userHeimdallOneClick6344E874/UnBrickPack/HIBL.bin

=> Downloading 24586 bytes to 0xd0020000

=> Data checksum 5d9c

=> usb_bulk_write() returned 24586

SMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

failed to find device

At some point during the flash, my device got disconnected (from the software standpoint, not physically- the cable was still firmly in), and re-connected. After it reconnected, the output from lsusb said that my phone was now connected to device 8 (explaining why the Unbrick tool could not find it, perhaps?). A few more retries of the Unbrickable tool yielded the same result- at some point my phone would disconnect, and would then reconnect with a new device id.

My question is- does your code handle this case? Does it also handle the case where the bulk transfer transferred fewer than the requested number of bytes, and tries to download the rest again?
[Captivate Android Development] AdamOutler:
it is supposed to disconnect once, then reconnect with the same ID, then disconnect and reconnnect in download mode. This is because of the 3 stage bootloader..

the HIBL enables an unsecure download. we send the SBL, which allows "download mode"

Use the ModeDetect utility.
[Captivate Android Development] illusoryphoenix:
Well, Mode-Detect says that it's an UnBrickable Debug device after the Unbrick utility says that it can't find the device after the first successful flash, subsequent disconnect/reconnect. I am noticing that the device id keeps incrementing upon reconnect. I'm gonna check out the source code to see if I can put in a fix for my scenario.

P.S. The only reason I'm not dual booting linux straight out is that I don't have a way to perform a restore on this laptop (it's a netbook without a cd drive).
[Captivate Android Development] AdamOutler:
you could always do it from the command line... grab the smdk tool, HIBL and the SBL..

smdk-usbdl -f HIBL.bin -a D0020000
sleep 5
smdk-usbdl -f Sbl.bin -a 40244000
[Captivate Android Development] illusoryphoenix:
Yep.

I realized that when unzipping the included zip file. I believe there's another parameter for the device ID in there as well?
[Captivate Android Development] illusoryphoenix:
I get the same problem when running the script directly. I tried increasing the sleep timeout to a minute- this time it did pick up the new device, but the second transfer still failed, and ModeDetect didn't detect download mode.

Oddly, if I run each command individually, but making sure that I replace the battery/replug in the cable for the second transfer, the second transfer goes through as well. Nonetheless, Heimdall fails to see my phone, and ModeDetect tells me that I'm not in download mode (it shows the usual debug board image).

Would flashing the HIBL, SBL in this manner work (i.e., one flash a time, removing the usb wire, removing/replacing battery, plugging wire back in in between the two flashes)? I never got any indication of download mode, as I said. If I've read this thread correctly, this wouldn't work because power is lost and we're back to starting from scratch for the SBL flash?

Thanks again.
[Captivate Android Development] AdamOutler:
Try a new battery.. it could be that your battery is as dead as can be. It wont boot from USB power alone because the device takes 1a, but USB supplies only 0.5a.
[Captivate Android Development] illusoryphoenix:
I gave up and bit the bulllet. Got a dual boot working without a USB stick or CD drive and installed Ubuntu. Obvious statement of the year, but this was much smoother than running over a virtual machine within Windows. Flashes went as expected, and now I've got stock KH3 on my phone :).

Thanks, Adam.
[Captivate Android Development] Rebellos:
You can swap xOM1 and xOM5 resistors, even if their resitance does differ, both will work fine.

Phone gets detected as UnBrickable Debug mode because not connecting pad to GND or VCC makes its state UNDEFINED, so CPU cannot for sure tell if it's LOW(0) or HIGH(1) and the result of reading pad state is unpredictable because of electrical noise (sometimes it gets 1 and other time 0).

But you definietly should not leave xOM lines unconnected - CPU is unstable then because various electrical noises aren't compensed by any power line and they are getting into CPU gates, making alot of mess there.

In other words:

With xOM not connected to anything phone will just hang randomly.
[Captivate Android Development] funkym0nk3y:
omg, many many thanks mate for making it clear, will try to redo the mod and will post results, thanks again :D
[Captivate Android Development] adisa:
I can reliably confirm that xOM5 and xOM1 are equal. I got to know this when my mod was being applied the (first two times following an earlier post from Adam that stated "Connect the active side of xOM1 resistor to the active pad on OM5's resistor pads" this made my mod to be applied twice yet not working. Sometimes later, i checked the post again and found there was an update and it stated "Connect the active side of xOM0 resistor to the active pad on OM5's resistor pads", i did it and my mod worked and i was able to unbrick my phone. Thanks to the unbrickable mod team for their unrelenting effort.
[Captivate Android Development] tennyleaz:
Hi,

First thank for the Unbrickable Mod.

I have the Unbrickable Mod applied from some ebay seller, and have the "phone-/!\-PC firmware update failed" screen again.

JIG or any key combo always goes to this "phone-/!\-PC firmware update failed" screen.

Now I'm trying to run the Resurrector on a RedHat machine. It gives the following message:

Please wait.... Uploading..

-------------------------------------------------------------

Hummingbird Interceptor Boot Loader (HIBL) v1.0

Copyright (C) Rebellos 2011

-------------------------------------------------------------

arch":

x86_64

Building command list

Building command list

Requesting Permission to access device

Then it stops.

Should I turn on my phone or do something else?
[Captivate Android Development] b-eock:
that phone! computer screen can be used as download mode
[Captivate Android Development] guilleglad:
Run ModeDetector, if it doesnt show S5PC110 then you have something wrong
[Captivate Android Development] AdamOutler:
Hrm... maybe you do not have the gksudo command on redhat? try using a Ubuntu Live CD.
[Captivate Android Development] adisa:
If you are still able to get phone-/!\-PC, then it means you only now have a soft unbrick and not a hard brick. see thread linked below for how-to;

http://xdaforums.com/showthread.php?t=1153310

If that doesn't work, then you may want to try to use the win32 unbrick method (winXp 32bit may work better), I have tried it before on windows when it failed on my linux dualboot (perhaps because i didnt have a swap partition) only for it to work when i tried it on my winXP virtual machine. it did work later on both my linux vm and my dual booted linux (after installing ubuntu (ubuntu-11.04) dual boot afresh). try it out and lets hear from you.
[Captivate Android Development] tennyleaz:
I tried, Oden could recognize my phone, but it showed "Failed" every time I start flash anything.

---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------

Thanks.

I'm on a 64bit windows 7, I will find a 32bit XP VM to try.

OneClick.jar fails, shows a "unspecified error" message. Should I have Heimdall installed, because it is asking?

UPDATE:

OneClick unbrick works on Ubuntu! Great!
[Captivate Android Development] adisa:
Welcome limitless Unbrickable captivate world.

I have observed that most people who have odin bricks while trying to flash bootloaders may only need the One-click unbrick tool (usually for fixing phone+computer screen), i recall doing this first after using unbrickable resurrector to bring my device to download mode then later i thought i should go ahead to flash everything out with heimdal SGH-i897-UCKH3-One-Click.

One advantage of using the phone+computer OneClick unbrick is that you will have your phone back the way it was before the brick and you can backup your apps(+data) if you want and then go ahead to do a full flash to what ever rom you want but be sure you clean the bootloaders using heimdal so as to have a much cleaner phone.
[Captivate Android Development] bulletproof1013:
You just confused me really bad
[Captivate Android Development] adisa:
Did I? what i said before were things i've tried out. let put it like this.

1. Apply UnBrickable Mod to your device: http://xdaforums.com/show....php?t=1206216

2. Run UnBrickable Resurrector: http://code.google.com/p/hummingbird...downloads/list This will only work on linux currently. Install Linux or dual boot if you have windows.

3. Run Heimdall One-Click: http://xdaforums.com/show....php?t=1238093 (or odin3 one-click),

4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).

Yes I meant that at (3) you could either use the Oneclick unbrick used for phone+pc error or the 'SGH-i897-UCKH3-One-Click' actually referred to as Oneclick unbrick in the unbricking tutorial (first post of this thread).
[Captivate Android Development] wesbound:
Hey Guys,

Can any one help me to point out what did I wrong, please? Below is a log from the one-click resurrector running in Ubuntu (not VM). I think I did OK job on the soldering part.

---

Building command list

Building command list

Requesting Permission to access deviceSMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

SMDK42XX,S3C64XX USB Download Tool

Version 0.20 (c) 2004,2005,2006 Ben Dooks <ben-linux@fluff.org>

(gksudo:1611): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",(gksudo:1611): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",(gksudo:1611): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",(gksudo:1611): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",failed to find device
[Captivate Android Development] adisa:
If you are sure your soldering is okay. then try the following;

1. use mode detector ( or "lsusb" in terminal you should see samsung electronics as on of you usb devices) if its okay then move ot then next step but if not then check your soldering again.

2. If soldering is but unbrickable is not working(in yur linux installation), then run the win32 unbricking within winxp 32bit.

3.You may also consider re-installing you ubuntu with version 11.04 check here http://linux.softpedia.com/get/Syst...istributions/Ubuntu-Natty-Narwhal-62881.shtml. I believe your phone should work now, God willing. lets have your feedback when you are through.
[Captivate Android Development] Rebellos:
Hey there, I just build HIBL v2.0 which does support Infuse 4G series. Also made some slight, probably unable to be seen improvements.

http://code.google.com/p/hummingbird-hibl/downloads/detail?name=HIBL.zip

example usage:

You can find the right SBL for your device over there

https://code.google.com/p/hummingbi...ngBirdInterceptorBootloader/Captivate_SBL.bin

Can you guys try this HIBL and post results? Don't flash anything, just check if it enter download mode properly.
[Captivate Android Development] AdamOutler:
Bump. Please test this. I currently do not have a UBM captivate. This works on my infuse 4g. My UBM captivate is out of commission right now. My other two aren't modded.

We need this tested to release the new version of the resurrector.
[Captivate Android Development] b-eock:
I will do it for you!

---------- Post added at 03:49 PM ---------- Previous post was at 03:34 PM ----------

When I put these on my phone, what should I be trying to do?

---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------

Works, goes directly to download mode!
[Captivate Android Development] AdamOutler:
k. Great

This is the HIBL 2.0. It contains logical checks in order to allow booting of the Infuse4g. Rebellos can probly tell you more, but the infuse4g has a few extra logical twists at the beginning. This 2.0 bootloader tests weather its a GalaxyS style irom or a infuse style irom and then boots it.
[Captivate Android Development] b-eock:
What does this mean, can infuse ROMS be run on Cappys
[Captivate Android Development] AdamOutler:
The same binary can be used on more devices. Just needed to check backwards compatibility.
[Captivate Android Development] AdamOutler:
The new version of the Resurrector will display like this when you plug in a UnBrickable Modded device.

get it from our SVN server at googlecode here: http://code.google.com/p/hummingbird-hibl/

For full instructions see here: http://rootzwiki.com/files/file/57-ultimate-unbrickable-resurrector-galaxy-infused-edition/
[Captivate Android Development] j8994:
hey guys need some help, my phone is showing no signs of life, this is what happened i was on fusion x, i flashed to max Q but didnt like it so i went in to recovery mode and wipe/factory, cache and davik and restored backup of fusion x that i made with cwm. well the phone kept hanging on the att logo, and i could get it into recovery but recovery was borked. wouldnt do anything. so i used aio toolbox and tried to flash to stock bug mistake, not my phone will not boot or turn on, will this fix my phone. im new to roms, but not to electronics. i can solder very well.

will the unbrickable mod help me restore my phone back to life??

PS i have already tried a jig :(
[Captivate Android Development] bulletproof1013:
Yes it will help ur phone...but try mode detector. By adam outler first
[Captivate Android Development] AdamOutler:
I have something better now. Check out the Ultimate UnBrickable Resurrector (Galaxy Infused Edition).

http://rootzwiki.com/files/file/57-ultimate-unbrickable-resurrector-galaxy-infused-edition/

if you see this then you're not bricked.
[Captivate Android Development] bulletproof1013:
So its all in one program now eh? Guess I gotta update lol
[Captivate Android Development] j8994:
thanks fixed my phone, works great. the glue was a bugger, but i took some stuff we use in my shop to remove epoxy and it dissolved the glue. applyed the mod and now unbricked, getting ready to flash custom rom now.
[Captivate Android Development] matejcz:
re:

Hi, I've just applied Unbrickable mod on my Captive, but when I need flash boot loader in Heimdal One-Click it said:

Ready for flash.Repartition was requested but bootloaders are not to be flashed.
IBL+PBL SBL PARAM KERNEL FACTORYFS DBDATAFS CACHE MODEM
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Beginning session...
Handshaking with Loke...

Downloading device's PIT file...
PIT file download sucessful

Uploading KERNEL

KERNEL upload successful
Uploading MODEM

MODEM upload successful
Uploading FACTORYFS

FACTORYFS upload successful
Uploading DBDATAFS

DBDATAFS upload successful
Uploading CACHE

CACHE upload successful
Uploading IBL+PBL

IBL+PBL upload successful
Uploading SBL

SBL upload successful
Uploading PARAM

PARAM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...

Device not connected.
Ready for flash.
Device not connected.

My captive can run, but after about 1-60 minutes it freeze and I must turn it on...

I can't root it and apply custom ROM...
[Captivate Android Development] AdamOutler:
That log says everything went properly and your device is now working. You might want to check in another thread to root your device.

edit: Now i understand. Your captivate runs for 1-60 minutes before it freezes.

It sounds like you didn't apply the mod correctly. This will happen if the high is not applied to xOM5. check your soldering.
[Captivate Android Development] matejcz:
re:

2AdamOutler: Thank you, I will check it
[Captivate Android Development] Gautch:
I have to thank AdamOutler for his work! My Captivate bricked about 3 weeks ago. I went to AT&T and was SOL. So I bought a $20 dallar phone to hold me over till i can get an upgrade.

Last saturday i popped onto xda from a twitter link to this thread. I was skeptical. But it worked!! AdamOutler, you saved me about $200 bucks that i would have had to spend on a new phone! Thank you. Thank you. Thank you!!