lets try to find the 13.37 ota update url and zip!!

This is a discussion on lets try to find the 13.37 ota update url and zip!! within the Motorola Backflip Development & Hacking forums, part of the Motorola Backflip category; Once you have updated the firmware on the phone, even if you do a factory reset, you still are on the same firmware....

Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 49

Thread: lets try to find the 13.37 ota update url and zip!!

  1. #11
    Senior Member jmgib's Avatar
    Join Date
    Mar 2010
    Location
    Kentucky
    Posts
    1,350
    Once you have updated the firmware on the phone, even if you do a factory reset, you still are on the same firmware.

  2. #12
    Junior Member Skrilax_CZ's Avatar
    Join Date
    Mar 2010
    Posts
    7
    You can use the SBF and RSD Lite to downgrade it back.

  3. #13
    Junior Member met3ora's Avatar
    Join Date
    Apr 2010
    Posts
    10
    I got the update URL, but it's encrypted. I don't think there's gonna be a way for us to get that URL easily at all. I'm not too good with networking, but I'll see if I can try to capture the update.zip via WiFi next week when I get my replacement Backflip (mine's acting funny, got ATT to send me a refurbished one).

    In the meantime if anyone can find a good reference on how to capture WiFi packets, I'd appreciate it and we can open it up for others to try as well.

  4. #14
    Junior Member andershizzle's Avatar
    Join Date
    Jun 2010
    Posts
    22
    How can I download 13.37? USing your encrypted url? I just got a refurbished free backflip so... How would you go about getting it

  5. #15
    Senior Member jmgib's Avatar
    Join Date
    Mar 2010
    Location
    Kentucky
    Posts
    1,350
    There isn't a way at the moment to install 13.37 as the download has been disabled for now. It was only released on a limited testing basis and thus far hasn't not been captured for side loading.

  6. #16
    Member Monotremata's Avatar
    Join Date
    Mar 2010
    Posts
    64
    Quote Originally Posted by met3ora View Post
    I got the update URL, but it's encrypted. I don't think there's gonna be a way for us to get that URL easily at all. I'm not too good with networking, but I'll see if I can try to capture the update.zip via WiFi next week when I get my replacement Backflip (mine's acting funny, got ATT to send me a refurbished one).
    Hate to say it but the download is closed now and youre not going to be downloading anything when you get your replacement until its released to the general public.

  7. #17
    Junior Member MLBZ521's Avatar
    Join Date
    Jul 2010
    Posts
    25
    I completely forgot I used the Log Collector App for this.

    Here are the logs I saved. Just going to include them all just in case.

    Log 1 = Check that update was available, it was, I canceled, so before I downloaded the update.

    Log 2 = Check that update was available, it was, I canceled, so before I downloaded the update. (Did this twice.)

    Log 3 = Realized I was supposed to download the update then use the Log Collector App, before installing it. This is that, after download, before install.

    Log 4 = This log is after I installed the update.


    Hopefully maybe there's something useful...?

  8. #18
    Junior Member andershizzle's Avatar
    Join Date
    Jun 2010
    Posts
    22
    You said you did a log before downloading and a log after downloading. Did you do a log WHILE downloading? Maybe this wasn't necessary? dunno

  9. #19
    Junior Member met3ora's Avatar
    Join Date
    Apr 2010
    Posts
    10
    Here are the lines that might be useful from MLB's logs (from log 3):

    Code:
    06-24 09:32:40.048 I/Updater (17403): OTA download accepted by user!
    06-24 09:32:40.778 I/cUs     (  136): CusSM.runStateMachine: found version Blur_Version.0.13.35.MB300.ATT.en.US in database (Getting)
    06-24 09:32:41.378 I/WSBase  (  136): doRequest(): url: http://ws-cloud105-blur.svcmot.com:80/blur-services-1.0/ws/upgrade/1/report_upgrade_status/0000062D9069/4503599731019881?k=android&l=100000062d9069&f=pb&p=176&h=2HC7Ai4Jh0mvMqjEjBWlIntHFdg&of=0&ssl=0
    06-24 09:32:41.508 I/ActivityManager(   91): Process com.motorola.blur.updater (pid 17403) has died.
    06-24 09:32:41.628 I/WSBase  (  136): doRequest(): url: http://ws-cloud105-blur.svcmot.com:80/blur-services-1.0/ws/upgrade/2/download_upgrade/0000062D9069/4503599731019881/Blur_Version.0.13.35.MB300.ATT.en.US?k=android&l=100000062d9069&f=pb&p=40&h=FMEWiXN.IW.CZKT8TJFkYaUoCmO&of=0&ssl=0
    06-24 09:32:43.028 I/ActivityManager(   91): Start proc com.motorola.blur.updater for broadcast com.motorola.blur.updater/.UpdateReceiver: pid=17412 uid=10041 gids={}
    06-24 09:32:43.188 I/global  (17412): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
    06-24 09:32:53.798 I/ActivityManager(   91): Process com.motorola.blur.updater (pid 17412) has died.
    06-24 09:32:53.988 I/ActivityManager(   91): Start proc com.motorola.blur.updater for broadcast com.motorola.blur.updater/.UpdateReceiver: pid=17418 uid=10041 gids={}
    06-24 09:32:54.128 I/global  (17418): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
    06-24 09:33:07.188 W/AudioFlinger(   54): write blocked for 194 msecs
    06-24 09:33:10.288 I/ActivityManager(   91): Starting activity: Intent { comp={com.android.settings/com.android.settings.deviceinfo.CheckUpdate} }
    06-24 09:33:10.478 W/AudioFlinger(   54): write blocked for 192 msecs
    06-24 09:33:10.578 I/ActivityManager(   91): Displayed activity com.android.settings/.deviceinfo.CheckUpdate: 287 ms
    Of course, going straight to the download URL doesn't work. It looks like we need to find a way to use Motorola's packages to initiate the download.

  10. #20
    Junior Member turnyourbackandrun's Avatar
    Join Date
    May 2010
    Posts
    18
    Hi, I'm rbmyr8 from m3. I've got a couple ideas. First, I have the post data for the update url from the packet sent by the phone. I may be able to create a fake form that posts this data, but it seems kind of unlikely. I think the better way would be to actually replay the packet sent by the phone and listen for the response... I'm just not sure how to do that...

    As far as the update.zip that I captured, after hex editing an update.zip from the droid, it looks extremely similar. So I know it's not too far off!


    Update:

    I just posted this over at m3, and thought I'd repost here in case anyone here isn't watching m3.



    So, apparently I captured all the packets I needed quite a while ago. Now that I learned how to merge capture files properly, I have a complete capture file from the update. Wireshark will even automagically export the update.zip (it's not called that, of course), which makes the hours I spent hacking the file together completely futile :P Anyway, I am 99.9% certain that I've got everything we need for a signed update.zip. Now, on to the bad news... The update.zip that wireshark exports (which, incidentally, is precisely the same as the one that I hacked together previously) still won't extract! However, I was noticing that although the bulk of the packets are sent to the same port on the phone, there are a few packets being sent to two other ports. I've got a sneaking suspicion that the data sent on the other ports- which is unrecognizable (by me, anyway), is important- maybe even part of update.zip. Is it possible that the phone combines file with a few bytes sent on other ports to create the final update.zip?

    The capture file itself is about 30 mb (most of the 14mb update file is duplicated, plus resent packets, headers etc...) so I'm not going to upload it until somebody expresses interest (I'm on a pretty slow connection). But by all means- if anyone is interested, it's yours. I think it's gonna take a bigger brain than I've got to figure it out, but I'm definitely not stopping now.

    One final thought: is it at all possible that the correct update.zip won't open in a regular zip program? Does the phone have a special way of unzipping it? Seems unlikely, but I thought I'd throw it out there. I'm tempted to just throw the file on an sd card and try to flash from the bootloader, but I'm not sure what happens when you flash a corrupt update.zip (probably nothing).

Page 2 of 5 FirstFirst 1234 ... LastLast

Remove Ads

http://www.scramblerducati.org/

Sponsored Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Search tags for this page

blur.svcmot.com
,
can't open ota zip corrupt
,
jabber-cloud105-blur.svcmot.com
,
jabbercloid
,
jaber-blur.svcmot.com
,
motorola backflip update 2.2 download
,
motorola backflip update 2.2 download zip
,
motorola mb300 ota update
,
o.13.37.mb300 softwere
,

rom motoblur mb300.sbf

,
sniff 3g traffic
,
update blur version.0.13.35.mb300.att.en.us dawnload
,
update.zip for motorola backflip using system recovery
,

what is ws-cloud105-blur.svcmot.com:80

,
ws.cloud***-blur.svcmot.com
Click on a term to search our sites for related topics.
Android Forum