Updated Odin Images Available - Latest T-Mobile Stock


  1. Nu11u5

    Nu11u5 Well-Known Member Developer

    OEM 1.6 Packages are uploaded now!


    Odin files for the 1.6 OEM update are now available! All necessary files and instructions are included in the download. To use the update you will need a Windows PC, USB cable, your Behold II, and about 5 minutes.

    Root "patch" is now available here: http://androidforums.com/all-things-root-behold-2/128131-get-root-based-new-1-6-finally.html
    Flash this after getting the the OEM update.


    Download Behold II T939UVJE2 OEM Odin Files and Instructions

    Click "Save file to your PC" near the bottom right.

    Windows 64 bit (Vista and after) - FYI

    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:


    1. Reboot your computer, once it begins starting immediately hold F8.
    2. After a few seconds you will get the Windows Startup Menu.
    3. Select "Disable Driver Signature Enforcement".
    4. 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..

    1. Pull the battery and reinsert it.
    2. Hold down Volume Down + Call + End.
    3. When the [!] logo appears press 'menu'. This will perform the factory reset.

    Special thanks to Mazz35, ikhtiar, slmar123, and everyone else who supported this effort.


    Below is an outdated release!

    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 :eek:

    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.

    Update-T939UVIJ6-to-UVJA3-OnePackage.zip


    1. Turn off and disconnect your Behold 2 from your computer.
    2. Extract and setup the Samsung ADB drivers if you haven't already done this.
    3. Connect your Behold 2 via USB.
    4. Start the phone in Download Mode by pressing and holding the following buttons in order: Volume Down > D-Pad OK > Power/End.
    5. Run Odin Multi Downloader v4.03.exe.
    6. Click Reset Files.
    7. Click OPS - pick Behold2.ops.
    8. Under Options, check One Package.
    9. Click One Package - pick Update-T939UVIJ6-to-UVJA3-OnePackage.tar.md5.
    10. 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.

    T939UVJA3-Odin.zip



    1. Turn off and disconnect from your computer your Behold 2.
    2. Extract and setup the Samsung ADB drivers if you haven't already done this.
    3. Connect your Behold 2 via USB.
    4. Start the phone in Download Mode by pressing and holding the following buttons in order: Volume Down > D-Pad OK > Power/End.
    5. Run Odin Multi Downloader v4.03.exe.
    6. Click Reset Files.
    7. Click OPS - pick Behold2.ops.
    8. Click BOOT - pick T939UVJA3-BOOTLOADER-20100318.tar.md5.
    9. Click PHONE - pick T939UVJA3-PHONE-20100318.tar.md5.
    10. Click PDA - pick T939UVJA3-PDA-20100318.tar.md5.
    11. 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

    Advertisement
  2. BH_MAN

    BH_MAN Well-Known Member

    Nu11u5,

    Thanks Man :)
    Looking forward downloading this. Just wondering, was the Recovery Updated as well? I'm thinking they wont let down grading of the Recovery.

    Anyway, I couldn't get the New kernel to take correctly, so I'm looking forward to editing your Package of the Kernel :) I know enough to be Dangerous with hex, but that's about it lol.

    Thanks again :)
    BH_MAN
  3. Nu11u5

    Nu11u5 Well-Known Member Developer

    The recovery was not updated in this build.

    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.
    BH_MAN likes this.
  4. BH_MAN

    BH_MAN Well-Known Member

    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 :confused:

    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...

  5. BH_MAN

    BH_MAN Well-Known Member

    Wow thank you!!!!!!

    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..
  6. aznknightz17

    aznknightz17 Well-Known Member

    Thanks!!!!
  7. SoulCreator

    SoulCreator Well-Known Member

    Thanks man, I'm just really glad we are finally able to get these files out to everyone who has not yet received the update yet.
  8. spinwizard

    spinwizard Active Member

    PASS!!! Thank you! well done! Nu11u5, can I buy you a brew?? :D

    p.s. Can I now do BH_MAN's no twiz rom? :confused:
  9. Nu11u5

    Nu11u5 Well-Known Member Developer

    Packages are uploaded now! See the OP for links.
  10. aznknightz17

    aznknightz17 Well-Known Member

    Thats what Im planning to do also. Flash BH_MAN no twiz rom and when he comes out with a rev3 kernel that includes updated kernel from Nu11u5 we can odin that into the phone.

    Or BH_MAN got something up his sleeve and may updated his custom rom w/ no twiz AND custom kernel all at once. lol....
  11. paul89

    paul89 Well-Known Member

    he said he was optimizing it so im waiting till he comes out with a newer version of the rom
  12. xbrokdikdogx

    xbrokdikdogx Well-Known Member

    I get a "check images" error when I try to run the update.
  13. Nu11u5

    Nu11u5 Well-Known Member Developer

    Were you doing the "update" method or "full flash"?
  14. BH_MAN

    BH_MAN Well-Known Member

    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... :)

    Thanks again Nu11u5
    ~BH_MAN
  15. Nu11u5

    Nu11u5 Well-Known Member Developer

    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.
  16. BH_MAN

    BH_MAN Well-Known Member

    I don't think it anything you did. Like I said sometimes I get these as well, other time's it don't.

    I think what is happening it's checking the image before it been completely loaded into the program.

    Personally I think it's a minor bug in Odin Flasher as I get the same error's with the Factory Restore images.
  17. tritran18518

    tritran18518 Well-Known Member

    mine says checksum failed, but i ignored and clicked the button. ^^
  18. BH_MAN

    BH_MAN Well-Known Member

    Yeah same here lol...
  19. Nu11u5

    Nu11u5 Well-Known Member Developer

    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.
  20. aznknightz17

    aznknightz17 Well-Known Member

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

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

    Picture took at 2:40AM EST

    [​IMG] [​IMG]
  21. tritran18518

    tritran18518 Well-Known Member

    He already did.
  22. BH_MAN

    BH_MAN Well-Known Member

    File's Up...

    Um? I'm wondering if it's getting Corrupt during the download.
    My Odin is Failing the md5 I posted, so idk now.
  23. Nu11u5

    Nu11u5 Well-Known Member Developer

    The host files checked out OK. The links are back up.

    If Odin is repeatedly giving you checksum errors then its very likely your download is corrupted. Re-download the file and try again.
  24. aznknightz17

    aznknightz17 Well-Known Member

    Yea because mine works. (Full flash) =)
  25. Nu11u5

    Nu11u5 Well-Known Member Developer

    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 :cool:

Share This Page