[Download] Samsung R720 Official Cricket Corporate EH29 Upgrade Utility [LEAKED].

Last Updated:

  1. Spz0

    Spz0 Well-Known Member Developer

    The following files I obtained from a site (that is down atm, but will post site if/once it goes back up). It is the Corporate flashing utility for the Samsung R720 (EH02) for programming the phone to the cricket Networks port of 2.3.4.
    The original PST software with the pack did not work, so I've added a PST software that is compatible.

    Disclaimer: I am in no way responsible for bricking of devices -- Use at your own risk!

    Here is the pack below.
    Samsung R720 Cricket.zip
    http://openzio.rtrnetwork.com/openzio/openvitality/Samsung R720 Cricket.zip

    Unzip to a folder, and follow the directions below.

    You may get an error during flashing stating something about not being able to access a log file. After passing through that, the flash should continue as normal.

    Please report results/comments/questions to this thread.


    gopran and theevildead84 like this.
  2. charssun

    charssun Well-Known Member

    Received an error dialog at this step; something about being unable to access a log file. If I ever run through the process again I'll remember to take a screenshot.

    Anyway, after clicking okay to the error dialog, the downloading proceeded. Right now my Vitality is booting up. I just heard the familiar startup sound, which I haven't heard in awhile. (I'm used to hearing the MetroPCS one.) The text SAMSUNG is displaying...

    (About a minute or so later.) Okay, it's back to how its original state. As in, the MUVE Music wallpaper I remember it having before I flashed it, the Cricket icons and other apps it originally had.

    Okay, connected via Wifi. Signed in to my Google account...apps are updating...manually updating others...installing App 2 SD, because I don't believe I'll be able to live without it on this phone...

    Okay, Android Market is now Google Play. That changed fast; very nice.

    So I'll play around with this a bit more and report on my findings (if I run into any trouble, etc.). I'm unable to test text, data or voice because I don't currently have a Cricket plan. If I get one, I'll let you know how well it works.
    gopran and Spz0 like this.
  3. Spz0

    Spz0 Well-Known Member Developer

    post your cricket default homescreen please :)

    edit: so your phone was bricked, or not functioning? The flash worked?
    gopran likes this.
  4. charssun

    charssun Well-Known Member

    Oh -- mine wasn't bricked, and it was functioning alright using another ROM. I just wanted to test this out in case I ever wanted to use Cricket again. I may simply continue using the WiFi for now...


    As you can see from the notification bar, I've installed Titanium Backup -- which required rooting and installing Superuser, of course. (Taking a screenshot also required rooting.) Just FYI.
    gopran and Spz0 like this.
  5. Spz0

    Spz0 Well-Known Member Developer

    Oh great :)

    Thanks for posting the homescreen wallpaper. This flash is the updated 2.3.4 OS for cricket (see my other post about 2.3.4 builds HERE ). If you look at the phone.apk for instance (look at the incall screen), it is updated as well as having the low volume fix (the 2nd phone I got which had the older OS on it had lower volume then my first).

    So this is great :) I have one more question for you before I test it out myself -- does it restore the recovery partition as well to AR 3e recovery module?
    Also, can you provide the framework-res.apk and systemUI.apk so I can diff them against my own copy to verify they are the same?

    Thanks for your testing m8 :) The community thanks you too. :)
    gopran likes this.
  6. charssun

    charssun Well-Known Member

    Spz0, do you mind explaining this a bit more? I'm not sure what you mean by recovery partition or AR 3e recovery module...
    gopran likes this.
  7. Spz0

    Spz0 Well-Known Member Developer

    Oh, ok.
    By ar 3e recovery I meant the stock recovery (not cwm). Reboot to recovery to see if you have "3e" recovery.
    Once I get the framework and systemui apk from you to diff it with my copy, I'll be flashing it myself to test it further. :)
    gopran likes this.
  8. Spz0

    Spz0 Well-Known Member Developer

    btw, if you didnt know already, heres the ADB command for pulling the specified files.

    Code (Text):
    1. adb pull /system/framework/framework-res.apk
    2. adb pull /system/app/SystemUI.apk
    Thanks m8.

  9. pedro1977

    pedro1977 Well-Known Member

    Looks like we have made some progress then. I salute you for having the balls to do it, i was weary because i wasnt sure if it would overwrite and potentially corrupt the bootloader (odin/ download mode).

    In fact maybe you should check this to make sure its all in tact
    hold down camera/muse button as youre powering it on.

    Let us know on the bootloader too it would be interesting to know if it removed CWM and put samsungs back on or cwm is still there.

    I assume to reboot into recovery he would use the same method as CWM
    power it on while holding down the back and volume down button.
  10. Spz0

    Spz0 Well-Known Member Developer

    That is correct.

    Also yes, entering download mode to check the bootloader is a must as well Charssun, as well as checking the recovery.
    If you could report back to us with the results, that would help out a tonne. :)

    • Boot to recovery : Hold Vol.down + back button + power til recovery starts.
    • Download mode: While phone is powered off, hold down the Muve button (camera) and insert the USB cable, then press vol.Up to enter DL mode.

    If everything is good with that, and once I get the framework-res.apk and systemui.apk files to diff them, I'll be more apt to flash it myself (since My phone is of the older 2.3.4 build, with the new build just restored from CWM, causing my signal to read as digital roaming).
  11. pedro1977

    pedro1977 Well-Known Member

    When he tests download mode he should continue on by pressing up again and ensuring that the comp detects his device.
    Im on a spanish computer here so I cant remember exactly the words but he should go to control manager (updated: control panel), system, then into device manager and look under modems, if a samung entry is listed all is well.
  12. Spz0

    Spz0 Well-Known Member Developer

    Control panel here. ;-)
  13. charssun

    charssun Well-Known Member

    Ah, okay. Actually, I had already flashed the stock recovery back to the phone before using the Corporate flashing utility. If you'd like, I can get CWM back on the phone and then try the Corporate flashing utility again. Let me know if that's what you'd like me to do.

    In the meantime, I'll get you that framework and systemui apk...
  14. charssun

    charssun Well-Known Member

    Okay, here are the files:


    I don't know if it matters, but I have yet to test whether the Corporate flashing utility replaces the stock recovery. I'm going to be switching over to CWM and then running the Corporate flashing utility again. I'll let you know my results.
  15. Spz0

    Spz0 Well-Known Member Developer

    Great, thanks for testing m8. :) Dont forget to test download mode again as well, as pedro stated above. ;)

    I'll diff these files tonight or tomorrow.

  16. charssun

    charssun Well-Known Member

    Alright, I used ODIN to install CWM recovery again, using the procedure from the "[Odin] Clockworkmod Recovery - Not compatible with Rom Manager yet" thread (http://androidforums.com/admire-all...-recovery-not-compatible-rom-manager-yet.html). Once I confirmed I had CWM as my recovery mode again, I followed the instructions in this thread to use the Corporate flashing utility again. By the way, here's an image of that error I get when I execute step #6 in those instructions:


    Once completed, I checked the recovery mode. It has, in fact, restored the recovery partition to Android system recovery <3e>. :)

    This is precisely how I confirmed that Android system recovery <3e> is the recovery mode.

    Download mode works.

    So now we know for certain that this procedure gets everything back to stock. Good news! :)

    I don't know if you need this or not, but I went ahead and pulled framework-res.apk and SystemUI.apk after this 2nd test. Here's the result (if you need it):


    I only wish I had a Cricket plan so that I could give voice, messaging and data a try. Aside from things requiring a Cricket plan, let me know what else I can test for us.
  17. charssun

    charssun Well-Known Member

    Yes, in the Device Manage it lists "SAMSUNG Mobile Modem #2" under the Modems item.

    So how do I know if the bootloader is the original one? Here's what is displayed:

    Also, I just tested download mode with ODIN by pushing CWM v5.0.2.7 to the device again. FYI
  18. Spz0

    Spz0 Well-Known Member Developer

    This is great news indeed. I'll be flashing this soon. Now I have a true stock copy to base my OpenVitality Rom off of.
    Once I get my nix tower set up again (just moved last month, so still trying to get the time between work to set up my server and nix towers / network) I'll dig into cwm for an ext 4 rom, as well as seeing about taking on cm7 for vitality (addressing beta issues).
    Thanks again for testing, and happy fathers Day!

    charssun likes this.
  19. Spz0

    Spz0 Well-Known Member Developer

    One more Question to clarify, test making a call for us. Does it send you to a cricket recording?

  20. charssun

    charssun Well-Known Member

    Result: "Your account could not be validated. Please contact customer services."
  21. charssun

    charssun Well-Known Member

    Update: My phone has been rebooting about once an hour. At least, I think it's been rebooting; every hour or so I hear the startup sound, so I assume it's been rebooting. I'll keep an eye on it to see if I can "catch it in the act".

    I don't know if this is due to any apps I've added to the phone or if this is a common occurrence with the Vitality. I do recall it having booted on its own a few times in its stock state a few months ago, before I first rooted the phone and began flashing it; I just don't remember it doing it this often.
  22. charssun

    charssun Well-Known Member

  23. pedro1977

    pedro1977 Well-Known Member

    I finally did it. The error log can be removed by creating the directories and file before starting the test, ensure the log file has write permissions. Unless you want a log of errors, its not important - no errors were recorded when i ran it (see post below).

    Differences noted between EH29/EH09

    *This flash EH29/Original flash (when I first purchased phone)
    Fixed accuracy (90 feet)
    Sometimes drops from 9 to 4 sats (coulple of times it dropped off even in favourable conditions)
    Orientation sensor sticks and spins wildly and requires constant calab (only horizontally)

    *Nandroid backup over at cricket users EH09
    Variable accuracy (down to 6 feet)
    Seems to be able to maintain connections to more sats
    Orientation sensors works fine

    For both versions though I have the same old problem with GPS, once i turn it off it will not work again for about 40 minutes. If I reboot the phone (especially shutdown and restart instead of quickboot - more success with gps button left on) most times it will restart, but conditions have to be excellent (unlike after that 40 minutes reset) at the time that it is run (not just turned on through the power control/ setting). If the sats dont immediately reappear then i have to reboot it again (crazy i know), sometimes it takes a few reboots anyhow. Otherwise its a 40 min wait and conditions do not have to be so good that time round i.e. i can sit in a semi sheltered area or close to a window o) odd?? Assuming its not a hardware fault, Im guessing that there are two problems, most of these problems center around the closing down of the GPSD server after each session (i.e. its not in the log and process apps reveal its still running and is only completed fully with a soft shutdown and reboot). This 40 minute period issue may have something to do with cache cleanup/ status listenining issues, im only guessing though.

    If your Standalone GPS is working fine under the following conditions
    before youre connected to the cricket network (as they may flash updates to you)) then im perplexed, maybe my gps chip is faulty.

    The orientation sensor issue was an annoying bug that I had before when i first got this phone, this cleared when I restored EH09 over at cricket users. I have noted that the follow libraries have been modified between the two versions.

    I have noted that there are not similar changes to any of the core GPS libraries, it is therefore most likely they have only modified that com.android.gpslocationprovider code (that illusive code), It does indicate that samsung are aware of these problems as they are modifying them with every build or update pushed over the network????. Otherwise why make it worse for both for GPS/ sensor services in a newer build?

    Recovery manger and bootloader (download mode - odin) appear fine at this time. I am certain that the bootloader is read only anyhow and cant be modified. If it could be modified how would you flash it back on?

    I tested it for one day without a root and one day with it rooted. There were more than a dozen apps installed both before and after the root. After the root i installed superuser and did a binary update, it did not reboot once. I did format everything before flashing. It also doesnt appear that the rooting process affected the gps/ sensor performance.

    Maybe we could extract the GPS/ orientation sensor files and put them in a flash for those who will flash this and continue using the phone, otherwise I would prefer to use EH09 over at cricket users. The flash in its current form it more suitable for those who wish to return the phone under warranty, sell on etc. This is based on the assumption that these changes arnt part of an update sent via crickets data network, something I would not receive. In concluding though this is a complete and working factory/ stock reset of the phone.

    Attached Files:

    charssun and Spz0 like this.
  24. Spz0

    Spz0 Well-Known Member Developer

    Sounds good. I"ll try when I get the chance.
    Still on the cricket network? *228 programming go OK? Same phone number and all?
  25. charssun

    charssun Well-Known Member

    I'll check out the GPS. I'm about to use the flashing utility to get back to stock again (since it's rooted and has CWM recovery in their now) to see if it'll stop rebooting all the time. I'll check GPS while I'm at it.

Share This Page