I just got the update and I think I may have forced it going threw this thread I saw that the file was hosted and then I downloaded it then used anycut from the market to open the device management and clicked start dm then I noticed the red and blue arrows minutes later I got the notification and boom update
plz someone try it and tell me if this works
The Following User Says Thank You to thugjedi91 For This Useful Post:
I just got the update and I think I may have forced it going threw this thread I saw that the file was hosted and then I downloaded it then used anycut from the market to open the device management and clicked start dm then I noticed the red and blue arrows minutes later I got the notification and boom update
plz someone try it and tell me if this works
this is great news for the developers if it works, and for all the rest!
I just got the update and I think I may have forced it going threw this thread I saw that the file was hosted and then I downloaded it then used anycut from the market to open the device management and clicked start dm then I noticed the red and blue arrows minutes later I got the notification and boom update
plz someone try it and tell me if this works
im still waiting but all it sid after i pressed start dm was not initialized
and then i looked under the menu and tried the soft. update tab and it went "force close" blah blah blah
well you got the update should you not be able to just look at the app info on them
or not im not sure
no I need to know their .apk name, not there tagged name or whatever you call it. for example, Telenav is called tn55-android-Houdini-signed.apk
so in order to remove the apk telenav you would need to do the following...
thats what i was thinking after i sent the post
ithink i have midnight bowling as a game so ill look to see if i can fin out whaty it is called as for the waldo game i have no clue
I just got the update and I think I may have forced it going threw this thread I saw that the file was hosted and then I downloaded it then used anycut from the market to open the device management and clicked start dm then I noticed the red and blue arrows minutes later I got the notification and boom update
plz someone try it and tell me if this works
No go for me, tried 2g/3g/wifi in all three modes (prod, lab, mformation).
__________________
Please take a second to search for your answer, and keep the forums clean of repeat postings. Thanks!
I'm not on the t-mobile network, so my phone is unable to reach fota.t-mobile.com, seems like i cannot even resolve it, can any of you guys that are on the t-mobile network check what fota.t-mobile.com resolves to? Maybe we'll be able to reach it outside of the t-mobile network if we have the ip?
I'm not on the t-mobile network, so my phone is unable to reach fota.t-mobile.com, seems like i cannot even resolve it, can any of you guys that are on the t-mobile network check what fota.t-mobile.com resolves to? Maybe we'll be able to reach it outside of the t-mobile network if we have the ip?
The server certainly lies within t-moble's firewall, meaning its inaccessable from any connections not originating from inside the network. The domain probably resolves to multiple IPs for load distribution across regional servers.
For me fota.t-mobile.com resolves to 10.176.56.93.
If you are wanting the update while off network, I'm working on a flash image that can be used with the ODIN tool. The process needs to be tested first, though.
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
Quote:
Originally Posted by thugjedi91
I just got the update and I think I may have forced it going threw this thread I saw that the file was hosted and then I downloaded it then used anycut from the market to open the device management and clicked start dm then I noticed the red and blue arrows minutes later I got the notification and boom update
plz someone try it and tell me if this works
I did this. Got the Message and update is available. I clicked proceed. After reboot nothing new. I can do it repeatedly and get the same results (I have) after reboot, nothing has changed.
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.
I updated the partitioning table with the above.
Last edited by Nu11u5; March 11th, 2010 at 01:49 PM.
Reason: sp
@Nu11u5 - Let me know if you can get the Update to reinitiate. I ODIN'ed back to stock expecting that I would be able to re-download the Update and that has not been the case. No one at TMO has been able to help. Consequently they are shipping me a "new" phone that will "hopefully" have the update on it.
@Nu11u5 - Let me know if you can get the Update to reinitiate. I ODIN'ed back to stock expecting that I would be able to re-download the Update and that has not been the case. No one at TMO has been able to help. Consequently they are shipping me a "new" phone that will "hopefully" have the update on it.
Its possible that T-Mo has flagged our IMEI's as having already received the update. If that's the case then the system does the updating a little half assed, making assumptions about the phone instead of querying it.
The alternative to getting a replacement from T-Mo (btw, would they charge for that?) would be to find another community member who does have the update successfully installed. I could walk them through the ROM dump process and if it works everyone can get the update
I have to wonder if you're not right about the flagging of IMEI's since it's been like 10 days since I got the update and after trying everything I could come up with I can't get it to start again.
TMO is not charging me as I'm still in my warranty period.
If you can point me to some good directions on I'd love to know how to do a dump. I have googled it but clearly I am not catching the right phrase since all the results are related to posts about finding a ROM dump, but not how to perform one.
Final question, how do you restore from a ROM dump? I am quite experienced with ODIN at this point, but this seems something different.
If you can point me to some good directions on I'd love to know how to do a dump. I have googled it but clearly I am not catching the right phrase since all the results are related to posts about finding a ROM dump, but not how to perform one.
Final question, how do you restore from a ROM dump? I am quite experienced with ODIN at this point, but this seems something different.
The ROM dump process uses the *nix tool 'dd' which reads and writes to/from any enumerated device or file. You can find its man page to learn how to use it better, but the command I'm using is just "dd if=/dev/block/stl9 of=/sdcard/stl9.dd bs=4096". The parameters in order mean input file, output file, and block size. Specifying a larger block size (default is 512 bytes) makes the copy more efficient and faster, but too large and you can get issues.
You will need root to use dd this way.
The device /dev/block/stl9 on the phone is the system partition. Other partitions can be seen in my previous post listing them.
The idea happened when I noticed that the files inside the ODIN tarballs exactly matched (with some extra zeroed data at the end) the block device dumps. If you take these dumps and re-tar them in the usTar format, ODIN should take them just fine. This way you can custom flash your phone without needing to install root first.
I used Cygwin tar to create my usTar files, see its man page for instructions.
If you mess with this yourself leave out the boot, amss, and recovery images from the tarballs when using ODIN. They didn't change since the update so no need to flash them, and corrupting any of these will permanently brick your phone.
Sorry to bump and old thread but its related to this discussion.
I was wondering if anyone ever figured out how to apply this type of update file. From what I know its a "redbend Embedded Feature Delivery package" and the program redbend_ua is what I think is used to apply it.
The Samsung Galaxy Indulge had an update pushed recently to a few people. Of those who got it the installation failed on a high percentage.
I was able to finally get a copy of the file and its of the same type as mentioned in this thread. It is my strong opinion that redbend_ua is what applies this patch.
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
