A new "security feature" in Windows prevents installing and loading of drivers that have not been signed by Microsoft. If you have a 64bit operating system, Vista or newer, you will have to follow special procedures to install and use the included drivers. If signed drivers exist they will be added to the download when they are found.

Before you installed the drivers and whenever you want to use the ADB / Odin functionality later you must do the following:

Reboot your computer, once it begins starting immediately hold F8.

After a few seconds you will get the Windows Startup Menu.

Select "Disable Driver Signature Enforcement".

Install or use your driver/device in Windows.

CAUTION:Some users are reporting that after the update the phone will temporarily be stuck in a boot loop. This seems to happen when the user has previously installed certain custom ROMs such as Take5 and Galaxy R12.

The work-around requires a complete factory wipe of the phone, meaning you will lose all of your data and apps not on the SD card. If you want to proceed in this case do the following:

When the phone appears to be stuck in the boot loop..

Pull the battery and reinsert it.

Hold down Volume Down + Call + End.

When the [!] logo appears press 'menu'. This will perform the factory reset.

Special thanks goes to SoulCreator for giving me a working ROM dump after I botched mine in test #1 - don't worry it works now

Use these firmware images to update your phone to the latest official firmware (UVJA3) if you haven't received it automatically yet. If you've been using a custom ROM, you can return to the updated stock build with these as well.

The downloads contain the Odin software, Samsung ADB drivers, and images (update or full flash depending). This is everything you need to perform the firmware flash - no root or other special tools/knowledge is necessary.CAUTION: Interrupting the flashing process may render you phone permanently unusable. Keep this in mind while you set everything up.

Update: Do this if you want to keep your apps, settings, and data. You will only loose root and custom ROM features.

Click Start. Odin and your phone's screen will begin to display the status of the firmware download process. After a minute your phone will reboot while Odin continues its timer. Your phone is flashed at this point and you can begin to use it after it boots.

Full Flash: Do this if you want to revert to the (updated) stock firmware after using a custom ROM. You will loose all applications, settings, and data on the phone.

Extract and setup the Samsung ADB drivers if you haven't already done this.

Connect your Behold 2 via USB.

Start the phone in Download Mode by pressing and holding the following buttons in order: Volume Down > D-Pad OK > Power/End.

Run Odin Multi Downloader v4.03.exe.

Click Reset Files.

Click OPS - pick Behold2.ops.

Click BOOT - pick T939UVJA3-BOOTLOADER-20100318.tar.md5.

Click PHONE - pick T939UVJA3-PHONE-20100318.tar.md5.

Click PDA - pick T939UVJA3-PDA-20100318.tar.md5.

Click Start. Odin and your phone's screen will begin to display the status of the firmware download process. After a minute your phone will reboot while Odin continues its timer. Your phone is flashed at this point and you can begin to use it after it boots.

These Odin images were made by myself, not released by T-Mobile or Samsung. Some members of the community may like to know how this was done, so I am working on a guide. Its relatively simple and can be done by anyone comfortable with a command line. The guide is found here: Creating Custom ROMs/Backups for Odin

I haven't tried to flash one with Odin yet because I don't think there is a backup way to flash it like in other Android phones in case something goes wrong.

Recovery allows you to enter download mode and flash the phone. If its not working then you can still boot into Android, but you will be unable to do major updates.

In most other phones there is a flasher built into the main OS that only has access to the recovery partition. This way if your recovery gets damaged you can always boot into Android and try again from there.

I might have over looked it but I haven't seen a recovery flasher built into the Behold 2.

Since we now have a way to flash custom ROMs directly to the phone what other benefits could we get by having a custom recovery?

It may be possible to get Odin to flash these partitions. I suspect it may have to do with the Debug ONLY > Phone Boot Update option, but I haven't experimented with it yet.

The Recovery wouldn't be for the Standard user for one I've Been able to Flash an edited Recovery fine but, It's not taking effect. Which is why I'm thinking they only let ugrading be Possible. IDK

Getting adb access inside recovery is very Helpful when porting stuff.
Push a Bad file & no longer boots can easily be undone.
I've help Dev. for the Cliq / Mytouch / Droid / G1 / Hero & know the end's and out's of using Recovery.

New Recovery benefits would help get A2SD / EXT2 / EXT3 / EXT4 & swap if written into the Recovery to add Support for these Feature Like Amen_ra Does. But, that will also require a Build-able Kernel source as well which I've not yet be able to do.

Edit*
Wonder how many Times I've hit the Refresh button looking for a link lol...
Either way it's going to be Nice using a New Version to restore with, when a Build goes Bad lol...

I haven't tried to flash one with Odin yet because I don't think there is a backup way to flash it like in other Android phones in case something goes wrong.

Recovery allows you to enter download mode and flash the phone. If its not working then you can still boot into Android, but you will be unable to do major updates.

In most other phones there is a flasher built into the main OS that only has access to the recovery partition. This way if your recovery gets damaged you can always boot into Android and try again from there.

I might have over looked it but I haven't seen a recovery flasher built into the Behold 2.

Since we now have a way to flash custom ROMs directly to the phone what other benefits could we get by having a custom recovery?

It may be possible to get Odin to flash these partitions. I suspect it may have to do with the Debug ONLY > Phone Boot Update option, but I haven't experimented with it yet.

If you get an Invalid Error that Pops up... But the Start button is not Grey... Then it's safe to flash, I'm not sure why this happen either.

I get this several time's & sometime not at all when I edit image's...
Remember, if you can't afford to brick a Phone, then it's best Not to even try it...

But, I'm Positive Nu11u5
Wouldn't Post something that would brick your Phone on Purpose as I just tried to Flash what was Posted..... Said invalid image, Hit okay... Then I hit start, work perfect for me...

But, I'm Positive Nu11u5
Wouldn't Post something that would brick your Phone on Purpose as I just tried to Flash what was Posted..... Said invalid image, Hit okay... Then I hit start, work perfect for me...

Thanks again Nu11u5
~BH_MAN

Click to expand...

Well I did test them before posting - no error messages. Maybe I forgot something.

Some details one what is happening would help me fix it in case something is wrong with the procedure.

Hmmm.. maybe the files were corrupted during upload. The checksums are correct with the originals and Odin does not complain. I'm going to remove the links until I can verify what is going on. I don't want people trying to flash corrupted images.

Hmmm.. maybe the files were corrupted during upload. The checksums are correct with the originals and Odin does not complain. I'm going to remove the links until I can verify what is going on. I don't want people trying to flash corrupted images.

Click to expand...

Erm not me. All my files were fine. NO checksum errors on all 3 files. I did the full flash. Lucky me?

Currently running on Nu11u5's ODIN updated ROM stock. Waiting for BH_MAN reup on the new flash with custom kernel...hehe

Some how I've been over looking the Debug Option's... I'll try that ASAP with the Recovery.

*EDIT*
Awe, the Debug don't do much good... oh well was worth the try..

Click to expand...

Regardless of how we get it to flash I figured out a way to safely test recovery images without risking the ability to flash back.

Just flash the recovery as the kernel! The partitions are the same size and both RAW file systems, with an ELF binary starting at offset 0x00. They should be completely compatible. The phone will boot right into the new recovery for testing, and if it is non-functional, the original recovery is still untouched. Start up in download mode to flash back the kernel image and the phone is like new.

The trick is still getting Odin or another method to flash the recovery, but once we find it testing can start right away