**Updated mistyped path: correct is /data/data/com.wssyncmldm **Organized Links, removed redundancies
**Added firmware file link (see bottom)
In case visitors are wondering, this won't get your phone updated. It may help find a method later, though
Binary cache files were found in /data/data/com.wssyncmldm that specify various URIs related to T-Mobile's management system and firmware OTA updates. There is also a file 'fota_delta_dp' (~40MB) which I assume is the update file. I haven't had a chance to analyze it yet but it is not a zip file.
The URIs can only be accessed from within T-Mobile's wireless network.
I was able to load the Update "Page", but it was a binary encoded file that Dolphin tried to display. So I can get it, but can't do anything with it.
I haven't been able to download it with a browser either. You will probably need to use something like 'wget' from a console. Busybox supposedly has it implemented.
I haven't been able to download it with a browser either. You will probably need to use something like 'wget' from a console. Busybox supposedly has it implemented.
when I entered that link in my phones browser I started to see those red and blue bars people were talking about and it would not let me use my phones internet what so ever I was rally hoping I was about to receive the update but nothing at all man I wish never heard about this update cause there seems to be little hope
when I entered that link in my phones browser I started to see those red and blue bars people were talking about and it would not let me use my phones internet what so ever I was rally hoping I was about to receive the update but nothing at all man I wish never heard about this update cause there seems to be little hope
Just downloading the file won't do much. We still haven't figured out how to force it to install.
Device(s): LG G2x, Behold II, Nokia N95, and a drawer full of dinosaurs (BH2 being one of them they get old so
Thanks: 30
Thanked 9 Times in 6 Posts
Maybe a dumb question
I was wondering. Like most on these forums I run a task killer. Could there be a process that we are killing, inadvertently, that is looking for the download? Is this OTA updated pushed to our phones or does our phone go looking for it?
I was wondering. Like most on these forums I run a task killer. Could there be a process that we are killing, inadvertently, that is looking for the download? Is this OTA updated pushed to our phones or does our phone go looking for it?
Maybe a dumb question but maybe not....
Thoughts?
a lot of ppl dont think task killers on a reg behold 2 does any good they just come right back. The ota gets pushed to your phone
In case visitors are wondering, this won't get your phone updated. It may help find a method later, though
Binary cache files were found in /data/data/com.wssuncldm that specify various URIs related to T-Mobile's management system and firmware OTA updates. There is also a file 'fota_delta_dp' (~40MB) which I assume is the update file. I haven't had a chance to analyze it yet but it is not a zip file.
The URIs can only be accessed from within T-Mobile's wireless network.
Some of the links just go to status pages, others download files. I'm also making the assumption that all downloads from these links will be the same firmware - that would need to be tested.
I can summarize Behold 2 Update like below according all related posts.
[What to be updated]
Known issues solved:
Bluetooth error: Unable to Pair or Unable to connect device
Battery indicator may display more charge than the phone has
Holding menu opens keypad, but does not respond, now goes to contacts
Phone constantly vibrates
Memory card un-mounts and re-mounts intermittently
Music plays automatically when accessing the music player
Incoming emails do not show the return email address
Corporate emails stop syncing
New additions:
Evernote application added
Where’s Waldo game added
Midnight Bowl 2 game added
Music Player auto-play upon launch corrected
“About” phone menu added to Settings, Quick List>Settings>About Phone
Boot screen animation change (now Samsung logo)
Delay reduction for proximity sensor while on a call
Battery icon status in notification bar now matches screen lock battery status
[Version before update] Baseband version T939UVIJ6 Kernel version 2.6.27 behold@sep-01 #1
Build number 76XXCSDCBALUM6375
FTA SW VERSION: T939.006 (by pressing #9999#, this may be applied to all samsung phones)
[Version after update] Baseband: T939UVJA3 Kernel: 2.6.27 root@sep-26 #1 Sat Jan 16 21:15:14 KST 2010
Build Number: 76XXCSDCBALUM6375
FTA SW VERSION: T939.006 (by pressing #9999#, this may be applied to all samsung phones)
[Update method]
- Not using Android System Update according to above post
- Above urls are related OMA FUMO (Firmware Update Management Object) over OMA DM (Device Management) protocol
- If the url below is valid for all phones, you can download the update file but it may be different from update.zip which is used by Android system update. In conclusion you cannot install the update file if you cannot find the the method. Speaking again Behold 2 may not use Android system update which is used on almost android phones. https://fota.t-mobile.com:443/agents/10475/1001/delta_T939UVIJ6Plus_to_T939UVJA3
- You can find the difference UI while doing update.
Finally I wonder why you cannot wait for update notification. I think it is because the operator does not inform detail information. In general the DM server sends bulk notification by IMEI range. The ordering policy will be determined by the operator or server administrator.
Last edited by RaymondHong; March 4th, 2010 at 08:00 AM.
The Following 2 Users Say Thank You to RaymondHong For This Useful Post:
I had to try like 5 times to get it to download all the way, it would stop at random % and then say bad sector, so I would have to start over. I'm on Edge network at home, maybe thats why. When I go to work so I will try again with 3G speeds!
Can we take an image of the whole device? Kind of like Mac Time Machine?
I've found a way to take an image of the whole device. However, the only way I can figure out how to write it back is possibly ODEN and a script for user data.
I haven't tested this yet, but I do have a fresh ROM dump to play with (once I learn more about how).
Last edited by Nu11u5; March 4th, 2010 at 12:56 PM.
Reason: spelling, doh
I've found a way to take an image of the whole device. However, the only way I can figure out how to write it back is possibly ODEN and a script for user data.
I haven't tested this yet, but I do have a fresh ROM dump to play with (once I learn more about how).
sweet thats good news!
@Kam, The only link that gave me a download was https://fota.t-mobile.com/omadl/desc?id=2955&r=4975348 and I tried to redownload it through 3G, it said saving! but then after that download unseccesful again
I've updated the OP. When I have the chance I will get my copy of the firmware file hosted ASAP.
I did run the update on my phone and am now running T939UVJA3. The update file is still in the /data/data/com.wssyncmldm folder.
The update file 'fota_delta_dp' is likely a difference file judging by its name and size. This means its meant to be run by some patching engine. Finding out where this is and how to force it needs to be done.
Looking at the file some more. It seems on my system at least the last 28M of the data is blank (0xFF and then switching to 0x00 for some reason for the last few sectors).
This would mean the people who have been getting a 12MB file probably have the whole thing!
There are no recognizable strings in the data aside from "RBMT" for the first 4 bytes. These do not correspond to any magic numbers that I can find. Possibly a proprietary file type.
News: While the update file still exists it is actually blank after the update! The system must maintain a 40MB image, probably to reserve space in the file system. The file downloaded from the URI is then inserted into the image for updating.
Last edited by Nu11u5; March 4th, 2010 at 02:11 PM.
I've posted a couple messages about this a while back, yet just now you guys find it. You can use AnyCut to access the Device Management app, which will show said urls are split into three groups, Production, Lab, and Test. You can even schedule it to check for an update. Though that doesn't mean you'll get it, as I did that a couple of times with no luck. It would pop up with the update notification, reboot and thats it, no update until it just happened on its own. More then likely as this app is simply a client program to a server program managed by the network engineers at Tmobile(Oh and of course these urls wouldn't work on your pc, they only exist internal to Tmobile).
As for the update itself, like its said above, its probably just a patch file that the app uses to patch the os and probably isn't in the format of updates to other android phones. Also that means more then likely that others who haven't gotten the update yet, cannot use the file to force the update. It will still require the Device Management app to talk to the mothership to probably check IMEI and then have access to the update and then apply it.
Of course thats just speculation, but if I ran the network, thats how I'd see it work. So if you haven't gotten the update yet, as I've said in another post, call Tmo to check your IMEI is right. Also would like to point out this tweet I got a while back from Tmo
They said about two weeks(which just means its going to take how ever long its going to take) on Feb 22. Which means as of today we are still in the "two week period."
__________________
"Physics is like sex: sure, it may give some practical results, but that's not why we do it."
-- Richard P. Feynman
sweet thats good news!
@Kam, The only link that gave me a download was https://fota.t-mobile.com/omadl/desc?id=2955&r=4975348 and I tried to redownload it through 3G, it said saving! but then after that download unseccesful again
I tried that link and it downloaded through 54% and then closed and said "bad socket" whatever that means
I've posted a couple messages about this a while back, yet just now you guys find it. You can use AnyCut to access the Device Management app, which will show said urls are split into three groups, Production, Lab, and Test. You can even schedule it to check for an update. Though that doesn't mean you'll get it, as I did that a couple of times with no luck. It would pop up with the update notification, reboot and thats it, no update until it just happened on its own.
For those running the BH_Man Modifications Device Management is not initialized thus I believe that it will not send the update. When you press any buttons after creating the shortcut to Device Management you get the error that "DM is not initialized". So I guess that might answer some people's questions as if the update can come through the mods.
How did you dump the rom? are you using dd or something on a partition?
Be VERY carefull about trying to odin any image back to the phone. Its EXTREMELY dangerous. (except the proper odin files of course).
Can you host you're update file?
I've added the link to the update file to the bottom of the OP. It's zipped down to the 12MB on account of the extra 28MB being zeroed. I left it this way just to be safe.
Some brave soul who hasn't updated yet can try placing this file in the proper directory and letting us know what happens, for example, if they reboot or go to Settings | Software Update. I have tried it on mine but I was already updated at the time - no prompts for an update.
Oh Snap! I keep messing up the path! Its fixed now!
Recommended code below, extract from zip and copy the fota_delta_dp file to the sdcard. Requires rooted phone.
Code:
su
cat /sdcard/fota_delta_dp > /data/data/com.wssyncmldm/fota_delta_dp
exit
As for the ROM dump, I used dd to read out the /dev/block/bml# block devices. These correspond to the phone's flash partitions on a physical level, with /dev/block/bml0!c being the entire flash device.
Friendly Advise: DO NOT TRY TO WRITE TO BLOCK DEVICES!
Anyway, the images dumped from the bml devices correspond to the partitions and files referenced in ODIN. I've compared the dumps per byte and they are the same. Partitions that contain file systems rather than raw data are headed with metadata (possibly a bitmap of file usage). The actual file system begins on offset 0xA80000 on these partitions.
The exception to this are bml1 and bml2. For both of these, the data from the 'arm9boot' file is split between them. These are different partitions on the device and have different functions during bootstrapping.
An arm9boot file consists of bml1 joined with bml2 at offset 0x200000 (the end of bml1).
Partitions 3, 10, and 11 are blank on my device.
Partition 7 seems to have some kind of file system on it, but has no corresponding ODIN image. Contents are unknown.
Partition 13 is 99% blank aside from a few stray bits at the very beginning.
Summery of block devices and partitions follows. Partition names originate from the 'partition' ODIN file (in the BOOTLOADER archive).
Partitions with file systems should be accessed via STL devices with no offset - edited table.
What this means is we can make custom ODIN images! If not by editing the partitions manually (or building them using tools) then by modifying them on the device and dumping it.
Update: Simply hexediting the flash file system header out so that the remaining image matches the contents of the original ODIN images does not seem to work.
The problem is that dumping the BML devices with files systems on them (vs RAW) produces an image that is too large. In the originals, all the files were allocated near the beginning of the ROM, and the rest was zeroed (in NAND flash this means 0xFF). After the update I noticed that files were allocated at the end as well. This means one cannot simply remove the extra zeroed space to make it fit for ODIN.
The STL devices work at a higher level, translating addresses in flash so they can work with normal file systems. Using an STL image instead of the edited BML image may work.
The downside of using STL devices for file system dumps is that they are only enabled on specific partitions. The good thing is these other partitions do not really concern us unless we want to edit the radio code (lets leave this alone).
Unfortunately the error in trying to flash the BML image forced me to ODIN back to the UVIJ6 firmware. Once I receive the update again I will test the new ROM dump and release a no-root-needed ROM update via ODIN if it works.
Last edited by Nu11u5; March 11th, 2010 at 01:49 PM.
Reason: table fix, spelling
The Following 4 Users Say Thank You to Nu11u5 For This Useful Post:
Interesting you can access EFS2. Thats a filesystem for the baseband. It holds protected nv items and other info for the REX RTOS that the baseband runs.
So i guess we could construct odin files from some dumps and a bit of hexediting.
The Following 2 Users Say Thank You to kam187 For This Useful Post:
Some brave soul who hasn't updated yet can try placing this file in the proper directory and letting us know what happens, for example, if they reboot or go to Settings | Software Update. I have tried it on mine but I was already updated at the time - no prompts for an update.
Recommended code below, extract from zip and copy the fota_delta_dp file to the sdcard. Requires rooted phone.
Code:
su
cat /sdcard/fota_delta_dp > /data/data/wssyncmldm/fota_delta_dp
exit
quote]
I would love to try this out! I get home at 5:30. If anyone wants to beat me to it, be my guest!
The Following User Says Thank You to paul89 For This Useful Post:
Hmm there is a partition called FOTA, wonder if that plays any part in updates. BTW is this the only android phone with Device Management from Tmobile? Considering this phone has such an interesting program, that from another thread, a rep over the phone was able to tell the phone was on/off and pushed the updated, sounds like alot was put into development for this.
Some brave soul who hasn't updated yet can try placing this file in the proper directory and letting us know what happens, for example, if they reboot or go to Settings | Software Update. I have tried it on mine but I was already updated at the time - no prompts for an update.
Recommended code below, extract from zip and copy the fota_delta_dp file to the sdcard. Requires rooted phone.
Code:
su
cat /sdcard/fota_delta_dp > /data/data/wssyncmldm/fota_delta_dp
exit
quote]
I would love to try this out! I get home at 5:30. If anyone wants to beat me to it, be my guest!
I tried it however it still states No Update Firmware File Exists...
Nonetheless, I am running the BH_Man's Stock w/touchwiz firmware at the moment.
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
OTA Firmware URIs Found - Work still needed
Overview of Behold 2 Update
