yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] AdamOutler:
They're still in the repository... We have not made an official release yet...

http://hummingbird-hibl.googlecode.com/svn/trunk/HummingBirdInterceptorBootloader/

hibl http://hummingbird-hibl.googlecode.com/svn/trunk/HummingBirdInterceptorBootloader/HIBL.bin

Sbl http://hummingbird-hibl.googlecode.com/svn/trunk/HummingBirdInterceptorBootloader/Sbl.bin

It will be in a command-line package soon enough (I think rebellos will handle this) and I'll write up a readme tonight.

I'll try to package the windows utility into the same one-click over the weekend.
[Captivate Android Development] bulletproof1013:
@rebellos, my PayPal willnot let me donate to you?
[Captivate Android Development] Rebellos:
Removed package as it doesn't seem to be working. Sorry, please take a look there:

http://xdaforums.com/showpost.php?p=17202523&postcount=27
[Captivate Android Development] comdei:
Captivate confirmed for best device ever
[Captivate Android Development] Rebellos:
*Captivate confirmed to get in hands of the best hardware reverser ever - Adam Outler.
[Captivate Android Development] Nitro_123:
EVERYONE PLEASE 5 STAR THIS THREAD AND A SUBMIT TO THE PORTAL WOULD HELP :D

I'm done :D

And guys really no way to do this without soldering ?? like attaching a small wire or something ?? i saw the distances between the resistors and everything today and the resistor is the size of a sand grain :( im not sure i can soldier that, even with a sharp soldering iron :( (although im a good soldierer )
[Captivate Android Development] tonyb81:
pardon my ignorance, i read through the thread and just want to clarify on one thing. I need to solder something to the phone correct? There is no way to do this without soldering something to my phone?

thanks
[Captivate Android Development] mijoma:
There is a very small chance of finding some other solution, but would require some hardware analysis first. The IROM download mode should run also when there's something wrong with reading BL1 from OneNAND. If you're able to convince the IROM there's OneNAND failure or the image checksum is incorrect then should end up with the same result (this is why some people reported their phone reporting as SEC S5PC110 Test B/D on USB without doing any hardware modifications - their BL1 image was damaged). If you are able to do that without soldering considering it's all in PoP then you got yourself an alternative.
[Captivate Android Development] Nitro_123:
:D:D Lets do it :)

The hardware Mod is really scary because the resistors are SERIOUSLY small...

I just saw them and changed my mind...

Thanks Adam but i think your next project may be what Mijoma just said:D:D:eek:

@tonyb81 yes no other way !! that's why i am thinking this will be TOO difficult for the ordinary user.. so we have to find an alternative way which is easier

P.S. congrats on the portal mention!! this thread is getting attention that it deserved from day 1...
[Captivate Android Development] Rebellos:
Please try it again with restarting device. Is it constant problem? Looks like these drivers are big piece of sh*t and I need to work on them more when I get my own dev board.
[Captivate Android Development] bulletproof1013:
very constant, but i had some probs with odin yesterday also ...so i wanted to

verify if anyone else getting this?

Has anyone else done the mod lol?
[Captivate Android Development] mystichobo:
So we need to do some tactical corruption then? :P
[Captivate Android Development] AdamOutler:
That was the plan from Day 1. I would love to figure it out more, but I think we have the official samsung answer. Convincing the IROM that the OneNAND is corrupt, may involve actually damaging the OneNAND... considering they are a package-on-package system. The only hope of this would involve I2C or UART, which would involve a $25-$50 box to perform the communications and would likely involve soldering to rediculously small points still.

I think we have a solution which will get you out of a jam which is free and easy enough already. It involves no hardware and all parts can be obtained from radio shack (if you don't have them around your house)...

We need to work on it...

I can confirm this on my virtual machine.

This MAY be possible via UART from Call processor or mainboard i2c

Mainboard i2c:

1. locate i2c points

2. figure out communication protocol

3. hope that it is possible to communicate with another device which can communicate with OneNand as there is no direct comms via I2C

4. hack the device (likely the Application Processor)

5. find appropriate firmware to upload to the APP processor via i2c

6. get that program running

Results: Likely 200+ hours of hacking, No gaurantee it will work, Hardware to communicate via i2c costs $40~, Soldering is still required, it will be a one-time deal, not permanent.

Call processor UART

1. locate call processor UART

2. try to communicate with Call Processor (Fully undocumented)

3. figure out how to make Call Processor communicate with iRAM, DRAM or OneNAND

4. Figure out how to reset Application Processor without clearing iRam and Dram.

Results: Likely 80ish hours of hacking, No gaurantee it will work, Hardware to communicate via UART costs $30+, Soldering may be required(or an adapter of some sort for about $10), it will be a one-time deal, not permanent.

I truly believe UnBrickable Mode is as simple and cheap as it gets. I do not plan on researching other methods.

Let me clarify a bit... we knew there was a probability that UnBrickable Mod would work because of a rather obscure, not well documented method used for development of the KIT-S5PC110 System On a Chip platform. It was a shot in the dark at a small point of light that we knew existed, but we didn't know where it was or if it was still there.... Other methods would be like a 5 year old shooting at the North Pole to kill Santa Clause... its a long shot and there's no proof he exists.
[Captivate Android Development] Blagus:
Hi Adam. Is something like this possible on Qualcomm chips?
[Captivate Android Development] Rebellos:
Let me answer for the question.

Yes, for some chips at least. But this strictly depends on board configuration. If you want to find out if this method is possible for a specific device, PM me as many tech infos as you can get about it. Including onboard chipsets models, datasheets, phone service manuals and I can try to find out something. One of the most important parts is dumping and analysing Qualcomm chip iROM.

@Win32 port. For now please try the tool posted here: http://xdaforums.com/showpost.php?p=17202523&postcount=27

Its confirmed to work... usually.

I'm taking few days or weeks from such hardcore development and tests for now.

@Other methods development:

I agree with Adam it's the simpliest way to unbrick totally bricked phone, we are likely not going to develop other methods for now.
[Captivate Android Development] AdamOutler:
it only works on windows 32... let me get drivers and stuff together. I'll put it in the first post.
[Captivate Android Development] bulletproof1013:
dude i must be missing something... its still output the same stuff...with no dl mode
[Captivate Android Development] AdamOutler:
The windows drivers are buggy. Try running it a couple of times. Also, try reinstalling the drivers for the S5PC110. The new ones are required.

Also, don't forget that once a bootloader has been loaded, the phone must be reset... Usually just reset USB cable, but sometimes you must also remove the battery.

This has been tested on Windows XP32
[Captivate Android Development] bulletproof1013:
well i installed provided drivers , tested multiple times... and still no download mode...( is it supposed to pop up like in linux?) unbrick.bat , dnw app...nothing
[Captivate Android Development] AdamOutler:
No. This is a command lime program. It will run from the command line only. I can't make it one-click until it works every time. I've had best luck with running it and then connecting my phone immediately.
[Captivate Android Development] bulletproof1013:
Well what I ment was. When it works, does your phone go into dl mode..and when you unplug the cable it cuts off. Like in linux
[Captivate Android Development] AdamOutler:
Yeah. The phone boots from USB the same way it boots in linux. When the phone sees USB is gone, it cuts off immediately. It would be nice to change this so you could have a single Linux box... Maybe even a battery powered USB cable of sorts would do the trick..
[Captivate Android Development] mijoma:
Yup. I believe as well there's no solution without soldering.

I never analyzed the connections between the oneNAND and CP (even if there is any), but that should still be on the second port of the controller making it affect AP port signals bit difficult. I don't even would like to consider writing through CP an option.

All the options at some point narrow down to soldering or science fiction, so the solution is as good as we can probably get.
[Captivate Android Development] AdamOutler:
I just wanted to let everyone know that I just fixed the first ever "White-Screen" Brick... LOL. This occurred after playing with Nexus S firmware.

This works well guys.
[Captivate Android Development] ostrianiel:
Jeeze I cant seem to get it to work :(

I'm gonna hunt some one down who can hopefully do the soldering and try again.
[Captivate Android Development] adisa:
Regarding the Unbrickable MOD, I plan to apply to my bricked cappy but i just wanted to know from anyone who already applied it what effect it has on the battery life/temp.
[Captivate Android Development] bulletproof1013:
No effect that i know of...just awsomeness
[Captivate Android Development] AdamOutler:
None. It only applies to the sequence of boot. When the power is off and the device is unplugged, it is off. when you plug in USB, it awaits a firmware upload. When you hold the power button, it takes 5 seconds instead of 1 to turn on because you have to get past the firmware upload part. If you hold the power button for 4 seconds and release while plugging in the power cable at the same time, it will go into battery charge mode.

This simply adds USB and UART booting to the startup sequence, allowing for upload of download mode, or any other bootloader durring the startup sequence.
[Captivate Android Development] AdamOutler:
Updated UltimateUnBrickResurrector.zip It now is as good as it will get for Linux.

We still need better windows drivers to make this work on Windows. I cannot add it as a one-click yet without better drivers for windows.
[Captivate Android Development] Smasher816:
Double post same thing?

Or am i missing something.

Edit: Nvm. Your right. Disregard this post.
[Captivate Android Development] AdamOutler:
read it again. It's small stuff
[Captivate Android Development] Master Melab:
Looks like I did a pretty good job, then. I declare myself an (not the) explanation guy.

AdamOutler, I am a little confused when you say LMAO processors don't support secure boot mode even though they perform signature checks.

I think I understand the '"secure JTAG" bit. In addition to the 160-bits of fusee that represent a hash value of the RSA key, there is another 80-bit hash represented by eFuses. The manual says that Samsung's JTAG hardware contains a value, that when hashed by the boot ROM, is compared to those 80 eduard. If they match, the JTAG module has elevated or complete access. You can compare to how some websites store passwords.
[Captivate Android Development] AdamOutler:
Rebellos was reading the manual today and GTalking to me while I was at work. That was what I understand. It's not secure boot as we think of it. Supposedly it's internal boot which is insecure. That's the gist I got, however Rebellos may have intended to tell me something else.

Rebellos, please quote and edit my post when you wake up man. don't forget to remove the quote tags so the BBcode remains.
[Captivate Android Development] kofijay:
Hello Adam,

I downloaded and dual booted Linux 64bits ... I have done the Ubrickable Recovery Mod hardware soldering with the help of an expert.

But I am having issues here ... The Ultimate Unbrickable Resurrector doesn't pull through to the end. This is what I get.

This will place your UnBrickable Modded device into download mode.

Instructions:

1. Apply UnBrickable Mod

2. Remove Device battery

3. Insert Device battery

4. Connect to computer via USB.

5. Click the Download Mode button

6. Download new software with Heimdall.

Credits:

AdamOutler -Hardware Analisys/modification/high level software development

Rebellos-Firmware development

mijoma-Firmware Support

TheBeano-UART Output Debugging/Firmware Support

Midas5-Uart Output Debugging/Hardware analysis

Please wait.... Uploading..

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

Hummingbird Interceptor Boot Loader (HIBL) v1.0

Copyright (C) Rebellos 2011

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

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>

Please wait.... Uploading..

Then it stops.

What am I doing wrong Adam?
[Captivate Android Development] AdamOutler:
Please copy and paste the results of the terminal command 'lsusb' with the device plugged in. If you see 04e8:1234 Samsung Electronics Co., Ltd as a device, then the mod is performed correctly. Otherwise, there is a problem. This device must be present for the mod to work.
[Captivate Android Development] kofijay:
This was what 'lsusb' came up with:

Bus 002 Device 004: ID 0c45:6481 Microdia

Bus 002 Device 003: ID 1199:9001 Sierra Wireless, Inc. Gobi 2000 Wireless Modem

Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 007: ID 413c:8160 Dell Computer Corp.

Bus 001 Device 006: ID 413c:8162 Dell Computer Corp.

Bus 001 Device 005: ID 413c:8161 Dell Computer Corp.

Bus 001 Device 004: ID 138a:0008 DigitalPersona, Inc

Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

There is no 04e8:1234 Samsung Electronics Co., Ltd amongst the list.

What could be the problem?

Soldering issue?
[Captivate Android Development] AdamOutler:
Undoubtedly the mod was not performed correctly, or there is a power supply issue.
[Captivate Android Development] connexion2005:
I concur. I've see the mod not work but only on a board with power supply issues in which when working correctly the board wouldn't supply power correctly nor detect a battery correctly. Do you know the history of the board?
[Captivate Android Development] connexion2005:
Also is this in a VM? If so it's probably not attaching the device correctly.
[Captivate Android Development] Smasher816:
(Slightly off topic)

I have a Captivate and cannot get my 32bit 10.10 ubuntu virtualbox vm to work with it. If I change the device to the vm then nothing happens, or the usb connected notification spams until i unplug it.

Is their some magic thing I should be doing?
[Captivate Android Development] AdamOutler:
For now, the Windows Drivers are flakey. Under WIndows, you must have drivers in order to connect a device to Linux. It does not work the same the other way around. Linux is not abstracted so that each device requires drivers. It's assigned a type.

We are working on the Windows drivers... Actually Rebellos is heading that up. The Windows drivers are flakey at the moment and take anywhere between 1-40 attempts to upload firmware. It's pretty screwey.

You should install Linux as your primary OS, or dual boot. If you need Odin, run Windows in a Virtual Machine. This is my setup.
[Captivate Android Development] Smasher816:
Thanks Adam.

Yes I know I should really set Ubuntu as my main OS. I really like it too.

Its just that I am also a gamer and have a huge collection of PC only games.

I once dual booted but always booted windows for some reason and gradually forgot/ignored the other one.

VM is nice because i can do both, and without rebooting.

And my dads new Infuse arrived, and I rooted it and all that stuff.

But that means that his old captivate is the house extra, and they said I could put it to use.

I'm still not sure if I want to do this mod yet. If I see a booted Nexus S/Captivate Frankenstein thing, then I will defiantly do it. Working windows drivers would be nice too (but i'm not apposed to dual booting for an unbricakbleMOD captivate).

Thanks for all you guy's great work and support.
[Captivate Android Development] bulletproof1013:
Man this UBMOD works so good. *grins*
[Captivate Android Development] kofijay:
Well, I the board as far as I know has no issues in that, I only happen to have flashed a wrong bootloader and in that process bricked my captivate so, I guess the board is as good as new.

I am not on VM ... I actually have a dual boot in place.

I would do get the Mod checked on and try again ... Will update you on whatever happens.
[Captivate Android Development] adisa:
Thanks. keep up the good work.
[Captivate Android Development] adisa:
Ragarding quote below,

Is it possible to add a connection/circuit analyzer to the ubrickable Mod program to check whether or not the mod was actually applied corrected (before clicking on the download mode button) since there is no way yet of knowing if the soldering was perfect or not.

I think this extension to the program will help those who probably tried their best to ensure a good soldering (while applying the unbrickable Mod) but yet were unable to successfully use the software to bring their bricked captivates back to life even while actually using Linux as their main OS or dual booted.
[Captivate Android Development] bulletproof1013:
If the mod is done correctly. U will show sec soc smdk board in windows..linux type lsusb output should be samsung

Sent from my unbrickable cappy *bam*
[Captivate Android Development] bulletproof1013:
Sorry if thus is off topic. But my buddy brought his motorola in today.its bricked. Do you think this mod will work on it?

See pic below

Sent from my unbrickable cappy *bam*
[Captivate Android Development] AdamOutler:
HAHHA... Does this guy hang out with Zach Morris?
[Captivate Android Development] bulletproof1013:
Lol...hes got all the paperwork.charger.VHS user manual. MINT! Wonder if it would sell in the forums?

Sent from my unbrickable cappy *bam*
[Captivate Android Development] AdamOutler:
I was thinking about that last weekend. I will write it this weekend.
[Captivate Android Development] kofijay:
Adam ... I'm here to say thank you a million times ... my 4 months dead captivate came to life today!

You and your software dude are just a rare kind!

I however realized something ... I don't know if it's just me or there is more to it:

I realized that, when I plug in my earphone and unplug it, the phone's earpiece stops working except loudspeaker.

Do you know anything about this Adam?

Thank you once again and well done with your achievement! You're a maestro!
[Captivate Android Development] AdamOutler:
That's normal operation. When you plug in a headset, you don't get earphone.

Thank you.
[Captivate Android Development] kofijay:
What I mean is, I happen to have plugged in my earphone to use and it worked alright but after using it and unplugging it, I have not been able to hear the voice of the caller via the phones built in earpiece unless I put it on loudspeaker or plug in the earphone.

Have you experienced anything like this?
[Captivate Android Development] AdamOutler:
No... but there is a switch that might be stuck. Try inserting and removing the headphones a few times to scrub it loose.
[Captivate Android Development] kofijay:
Tried your suggestion but it ain't working. I would try opening it up again and check if something isn't sitting well.

Will update you!
[Captivate Android Development] adisa:
When i first bought my now bricked cappy, it came with this problem and even engineers (at our local computer village in Lagos) couldn't help it, however i was able to fix it by flashing (back to stock) with bay_wolf's all in one tool and since the i have being helping them put whenever they had same problem.

see this thread for details and downloads http://xdaforums.com/showthread.php?t=944418
[Captivate Android Development] Rebellos:
Most likely this is badly connected JACK flex or rubbish in jack socket. Also it can be eventually kernel with invalid JACK INT driver.
[Captivate Android Development] manny05:
so i was trying to flash back to stock using odin and the process stop midway...my cappy's screen was just white (which has never happened) so i unplugged it to see if i could restart it since its been sitting there like that for 10 mins...

now the phone wont turn on, (tried going into download mode and recovery) but nothing..

no error comes on or anything..wont even charge (not that i can tell anyways)

so im assuming i completely bricked my phone? correct? lol .

if so im going to send it to mobile tech and have them fix it for 40 dollars.. i just want to confirm with you guy if there is anything i can do before i pay and send it.
[Captivate Android Development] AdamOutler:
It's still kinda ugly, but you can play around with this app, and see if you can get it to detect any sort of mode from your device. If you see S5PC110, and a picture of a microchip, then you're good.

You will need to be running Linux.

This app is beta http://xdaforums.com/attachment.php?attachmentid=715865&stc=1&d=1315683188
[Captivate Android Development] manny05:
it just says device not found :(
[Captivate Android Development] Rebellos:
Then the only way is DIY or send it to someone who has got enough experience and knowledge to fix it.
[Captivate Android Development] manny05:
DIY???? whats that
[Captivate Android Development] bulletproof1013:
Working well here. Thanks

Sent from my unbrickable cappy *bam*
[Captivate Android Development] AdamOutler:
Do it yourself. Do the UnBrickable Mod. Its very small soldering, but its how you use post 1 of this thread, unless you're lucky and your device goes to the mode above... the program only works under Linux.
[Captivate Android Development] manny05:
yea i was looking into that but it seems like its suppose to be done before its brick...am i correct? lol
[Captivate Android Development] Rebellos:
Do It Yourself.

This means you take a soldering iron and start a construction of UnBrickableMod on your mainboard... or a destruction of board.

But well... I think 40$ is much less than for a new mainboard. I'd just pass it to MobileTechVids.

//edit: :o @ posting speed

UnBrickableMod can be applied after bricking, and it will allow you to unbrick a phone.
[Captivate Android Development] AdamOutler:
Nope. Rebellos and I developed this mod on a totally bricked Captivate.
[Captivate Android Development] manny05:
oh.. wow lol

ill take a look at the steps to see if its difficult to do, if it is then i wont risk it.

it doesnt look complicated though. any tips though? things i should look out for, or not break lol?
[Captivate Android Development] manny05:
i held down volume up and down plus power with the USB plugged into my pc and got this menu:

its in attachment..

any thoughts?!?
[Captivate Android Development] bulletproof1013:
Why are u pressing vol up down pwr. This is unbrickable mod. Phone needs to be off.

Sent from my unbrickable cappy *bam*
[Captivate Android Development] manny05:
EDIT: So i just had a miracle and i just finished flashing back to stock

OH YEAAAAAAAAAAAA

that just made my night lol. thanks for the help guys, i think im gonna try this mod pretty soon lol.

isnt there anyone i can pay to do the mod for me though? i dont have those materials. plus i dont have experience...
[Captivate Android Development] AdamOutler:
I can do it. Send me a PM.
[Captivate Android Development] bulletproof1013:
Is this a hard brick state?

Sent from my unbrickable cappy *bam*