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.
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:
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 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
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.
Turn off and disconnect your Behold 2 from your computer.
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.
Under Options, check One Package.
Click One Package - pick Update-T939UVIJ6-to-UVJA3-OnePackage.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.
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.
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
Last edited by Nu11u5; July 21st, 2010 at 05:55 PM.
Reason: Warning for custom ROMs
The Following 47 Users Say Thank You to Nu11u5 For This Useful Post:
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.
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 Following User Says Thank You to Nu11u5 For This Useful Post:
Device(s): Behold 2 w/ BH_MAN Galaxy 1.6 / R7
Do Not PM me With Problem's
Post in Thread!
Thanks: 156
Thanked 1,672 Times in 433 Posts
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...
Quote:
Originally Posted by Nu11u5
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.
Last edited by BH_MAN; March 18th, 2010 at 04:08 PM.
PASS!!! Thank you! well done! Nu11u5, can I buy you a brew??
p.s. Can I now do BH_MAN's no twiz rom?
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....
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....
he said he was optimizing it so im waiting till he comes out with a newer version of the rom
Device(s): Behold 2 w/ BH_MAN Galaxy 1.6 / R7
Do Not PM me With Problem's
Post in Thread!
Thanks: 156
Thanked 1,672 Times in 433 Posts
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
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.
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
Picture took at 2:40AM EST
Last edited by aznknightz17; March 19th, 2010 at 02:43 AM.
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..
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
Device(s): Behold 2 w/ BH_MAN Galaxy 1.6 / R7
Do Not PM me With Problem's
Post in Thread!
Thanks: 156
Thanked 1,672 Times in 433 Posts
Quote:
Originally Posted by Nu11u5
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
Yeah I was thinking the same thing lol..... I'll have to try that in the morning..
Still waiting for reboot....
<1> amss download..
<1> 1/3 Finished.
<1> kernel download..
<1> 2/3 Finished.
<1> system download..
stuck looking at this in odin and timer is at 9min
Did the file load into Odin without any errors?
It looks like you are using the Update package. This one poses practically no risk of damaging your phone if it fails to flash. If it continues to sit there just restart Odin and try again.
Last edited by Nu11u5; March 19th, 2010 at 01:07 PM.
no errors on load do i just close odin and restart it?
Yea it failed again. I give. Got it to boot wats funny is when i press *#9999#
It shows pda as old and phone as new lol. Think this is enough for vibration issue lol.
*got it working i slept on it and tryed it this evening works great thanks.
Last edited by i2hi4u; March 19th, 2010 at 09:13 PM.
Reason: finally
So which Android version will this give me? Can you post what is customized in the ROM that you have included in the ODIN files? i.e. is it just the TWiz taken out or ....?
I have been using the galaxy ROM on my BHII and like how fast it is. The only bummer to me is the 1.5 Android so I am hoping this at least gives the 1.6?
So which Android version will this give me? Can you post what is customized in the ROM that you have included in the ODIN files? i.e. is it just the TWiz taken out or ....?
I have been using the galaxy ROM on my BHII and like how fast it is. The only bummer to me is the 1.5 Android so I am hoping this at least gives the 1.6?
Thanks for your hardwork regardless!
There are not customizations in this ROM - it is still Android 1.5.
It gives you the official T-Mobile UVJA3 firmware build without having to wait for it to be downloaded to your phone over the Internet. Some people still haven't gotten the OTA update even though it came out a month ago. There are also reports that you can only get the OTA update once - so if you flash another ROM and want to go back, the only way to get the updated firmware is with this.
Hey everyone i have a problem i download the file and i tried too extract the samsung adb driver but it gave me an error screen shot below please help me out or can you re uploaded on another mirror because i think the file on there server is corrupted.
So I have a question that I didn't see answered in this thread. Since I never got the update and am still on the old baseband, if I flash to the new base band and then got back to using BH_MAN's No/Twiz rom will it revert back to the old baseband?
The reason I ask is because with BH_MAN's latest 1.5 stock android rom I still have the proximity sensory bug. I was curious if flashing these files than back to his rom will help at all.
I believe that BH_Man is using the kernel and system files from UVJA3 (latest official version), but his thread says its still only UVIJ6 (the original, old release version).
Your "baseband" version would be whatever version of the kernel and system files are included in his release as the flashing process overwrites these.
Ok thanks. I have another question for whatever reason I can't root not now that I have done a full flash with the updated files. Is there something we have to do different with the updated stock T-mobile rom to root now. I keep getting permission denied when trying to adb push try3 (first step in persistent root instructions).
Ok thanks. I have another question for whatever reason I can't root not now that I have done a full flash with the updated files. Is there something we have to do different with the updated stock T-mobile rom to root now. I keep getting permission denied when trying to adb push try3 (first step in persistent root instructions).
I've gotten root just fine on my device. Is it failing on "adb push try3 /data/local" or somewhere else?
Ok just an update for anyone who might want to know. After doing the full flash to the updated stock t-mobile rom my baseband changed to the new one, but my kernel stayed to what it was when I flashed BH_MAN's latest stock no twiz adroid 1.5 rom. I couldn't get root working so I figured it would just flash back to BH_MAN's rom since I would rather have the bloatware gone than the t-mobile updated stock rom with not root. After doing so I noticed that My baseband remained at UVJA3. Also, my phone seems to be running smoother than before when I was on BH_MAN's rom and the proximity sensor issue I had before with the extremely long delay has been fixed.
I don't know if any of that information will help anyone, but I hope it does some how.
Ok just an update for anyone who might want to know. After doing the full flash to the updated stock t-mobile rom my baseband changed to the new one, but my kernel stayed to what it was when I flashed BH_MAN's latest stock no twiz adroid 1.5 rom. I couldn't get root working so I figured it would just flash back to BH_MAN's rom since I would rather have the bloatware gone than the t-mobile updated stock rom with not root. After doing so I noticed that My baseband remained at UVJA3. Also, my phone seems to be running smoother than before when I was on BH_MAN's rom and the proximity sensor issue I had before with the extremely long delay has been fixed.
I don't know if any of that information will help anyone, but I hope it does some how.
That is probably because my ROM updates the AMSS. I think BH_Man left it out.
That is probably because my ROM updates the AMSS. I think BH_Man left it out.
I don't know why you couldn't get root before.
Enjoy your phone!
Yeah i'm not sure why I couldn't get past the first step in the root process. When I typed adb devices my phone showed up but it wouldn't let me do anything with adb shell. I would show up with the $, but gave me the premission denied when trying to push try 3.
Regardless of that though between having the updated baseband along with BH_MAN's stock No/Twiz rom my phone is running smoother and faster than it ever has before. I mean before doing the update odin the phone worked fine nothing really forced closed or anything but it seemed to be unpolished if that makes any sense.
Just to be clear I don't think this was BH_MAN's rom's fault or anything like that. Seems like the fixes that the t-mobile update had + BH_MAN's odin stock rom = one happy Behold 2 user. Thank you both and anyone who helped you for all of your work. I've always liked this phone a lot unlike some people, and even got it running pretty smoothly with long battery life before doing anything to it except rooting and removing as much bloatware as I could, but not I am absolutely loving my phone. I'm even happy enough with it I'm gonna hold off on moving to 1.6 until it's even more stable and we can get things like swype and the samsung camera to work if it's even possible since I don't know anything about the developing process.
Sorry this was so long. Thank you again for all your work out there guys.
The Samsung Behold 2 for T-Mobile greatly improves on the first version of the phone by adding Android to the mix, providing for a powerful combination of hardware and sowftware. With Android, Samsung's custom TouchWiz UI, a 3.2-inch AMOLED Tou... Read More
Updated Odin Images Available - 1.6 Release
