Just Installed Leaked Epic 4G Froyo ROM

Just Installed Leaked Epic 4G Froyo ROM

I just installed the recently leaked Android 2.2 (Froyo) ROM on my rooted Samsung Epic 4G phone using ClockworkMod, and after playing with it for a bit, I plan on finally starting development in EliteBomb to get automatic limit removal working on rooted Android 2.2 devices once and for all. I’m really excited to finally be able to start working on fixing this, and I really hope to have a proper fix for EliteBomb and InfiniteSMS (EliteBomb Plus will receive the fix first) out soon, hopefully within a couple of days, at least before Google decides to release Android 2.3 (Gingerbread). 😉 Anyways, I just wanted to let you guys know that I’m actively working on fixing the problem, and I hope to have a fix out soon. Take care. 🙂

UPDATE: The post describing how to manually remove the SMS sending limitations has been updated to fix a permission denied issue. The old instructions are still there, as they worked for a lot of people and only a small few are having problems with permissions being denied.

Automatic Limit Removal Still Broken On Certain Devices

Automatic Limit Removal Still Broken On Certain Devices
Sorry, but it looks like automatic limit removal is still not working on certain rooted Android 2.2 devices. If you want to get your limit removed, and automatic removal did not work, I suggest trying the manual removal method, which has been tested and proven to work. I want to get automatic removal working very badly, but unfortunately, I don’t actually have a 2.2 device, so it’s a lot harder to make it work. When I get 2.2 on my Samsung Epic 4G, I will do everything I can to get the automatic removal working, as I know it is very important to many of my users. I’d like to apologize for how long it has been taking to get this fixed, but developing for an operating system I don’t have is hard to do. I’d like to let you all know that fixing this is very high on my priority list, and I’m trying to get a fix out as soon as possible. Thank you for your understanding.

Successful Android 2.2 SMS Limit Removal!

Successful Android 2.2 SMS Limit Removal!

An EliteBomb user, Jacob Miller, and myself managed to get the SMS limit removed successfully in Android 2.2 on his Motorola Droid (Original). I’d like to personally thank Jacob for spending the time with me in the chat in order to get the limit removed on his phone. The process on the post that describes how to remove the SMS sending manually has been updated to reflect what we had to do in order to get it to work. If you have a rooted Android device running version 2.2 (Froyo), and you have not been able to automatically remove your SMS sending limitation automatically, I highly recommend trying the method on that post, as I now know that it works. In addition to Jacob’s Droid, I personally managed to get the limit removal working perfectly in an Android 2.2 virtual machine running in the Android emulator included in the Android software development kit. I now know exactly how to remove the limit manually on most devices, and I really hope to have an automated limit removal tool out soon. If you try that method, and experience issues, do not hesitate to contact me, so I could try to get the limit on your device removed. This marks a new milestone for SMS limit removal, as nobody else has any documentation on how to remove the SMS sending limit in Android 2.2 yet. Thanks to everyone who notified me of the issue, and all of you who purchased EliteBomb Plus, which encouraged me to work on getting the limit removal working. I couldn’t have done it without you guys! 🙂

EliteBomb Plus 2.6 Released

EliteBomb Plus 2.6 Released

EliteBomb Plus 2.6 is just another release that is just an attempt to fix the automatic Android 2.2 SMS limit removal. If you download this new release and have a rooted device, please, let me know if you get it working. Thanks! I will have a similar version of the free version of EliteBomb out soon! If it still doesn’t work, feel free to try to remove the limitation manually.

New EliteBomb Advertisements!

New EliteBomb Advertisements!

I don’t think this matters to many of you, but I’m excited to announce that I just finished completely revamping the AdMob advertisements for my EliteBomb application. If you’ve ever seen my old EliteBomb ads, you may remember them as being boring, plain-text advertisements. Well, that’s all about to change, as I just finished creating some new, awesome looking EliteBomb ads, for both the free version of EliteBomb, and the EliteBomb Plus. I already stopped running the old advertisements, and the new advertisements are already running as I’m writing this post. The EliteBomb advertisement will be running in all of my applications, except for EliteBomb itself, and the EliteBomb Plus advertisement will be running in the free version of EliteBomb. Look out for these ads:


Closer to a Proper Froyo Limit Removal Fix

Closer to a Proper Froyo Limit Removal Fix

So, I recently managed to get the limit removed (manually) in the Android 2.2 emulator found in the Android SDK. This proves that it is possible, and I hope to have an automated fix out soon. For those of you who can’t wait (rooted device required) — try this:

  • Download the Android SDK
  • Put your device into development mode (Go to Settings > Applications > Development, and make sure USB Debugging is enabled)
  • Plug your device into your computer’s USB port
  • Make sure you are connected to your device by running adb devices
  • Use cd to change directory to the tools directory of the SDK
  • Run adb shell
  • Type su and hit enter
  • Type remount rw and hit enter. Depending on your phone, this may not work, and you might get a command not found error. If so, try “mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system“. If you are testing this on the Android Emulator, the command you want is “mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system“. If none of these commands work, look for your device’s command to remount the filesystem in read-write mode by searching on Google, and type that instead. This step in not optional. It will not work if you skip this step.
  • Now type exit and hit enter, repeat if you aren’t out of adb shell yet
  • Type adb pull /data/data/com.android.providers.settings/databases/settings.db and hit enter
    • If you get an error saying “failed to copy ‘/data/data/com.android.providers.settings/databases/settings.db’ to ‘./settings.db’: Permission denied”, make sure that you remounted your filesystem in read-write mode. This could be the problem. If it still does not work after you make sure that you remounted your filesystem properly, try these steps which worked for me:
      • Go back into adb shell
      • Type su and hit enter to get root access
      • Type, letter for letter, “cat /data/data/com.android.providers.settings/databases/settings.db > /data/local/settings.db” and hit enter
      • Now type exit twice to get out of adb shell
      • In your regular terminal (not adb shell) type “adb pull /data/local/settings.db” and hit enter.
  • Type sqlite3 settings.db and hit enter
  • Type (letter for letter) these lines, hitting enter after each one:
INSERT INTO gservices (name, value) VALUES ('sms_outgoing_check_max_count', 999999999);
INSERT INTO secure (name, value) VALUES ('sms_outgoing_check_max_count', 999999999);
INSERT INTO gservices (name, value) VALUES ('sms_outgoing_check_interval_ms', 0);
INSERT INTO secure (name, value) VALUES ('sms_outgoing_check_interval_ms', 0);
.quit
  • If you are on Android 2.2 or newer, it is perfectly normal to get “no such table” error messages when entering the gservices lines. Just ignore those. It will still work.
  • You should be out of the sqlite editor, and back to your shell.
  • Type adb push settings.db /data/local/ and hit enter
  • Now, go back into adb shell (just type adb shell and hit enter)
  • Verify that you have a # in your shell(not a $), which means that you have root access.
  • If you do not have a # in your shell, try typing su
  • Type cd /data/local to get to the directory where we just stored the modified settings database
  • type ls to list the files in the directory, and verify that settings.db is in the list of files
  • Now, letter for letter, type cat settings.db > /data/data/com.android.providers.settings/databases/settings.db and hit enter
  • Nothing should appear on the screen. This is perfectly fine.
  • Now, let’s verify that the file was written properly before rebooting the phone…
  • Type cmp -l /data/local/settings.db /data/data/com.android.providers.settings/databases/settings.db
  • Nothing should come up from that either. If something does, the database was not copied properly. Go back to the last cat command step. Otherwise, your database has been modified successfully. Congratulations!
  • Now, exit the shell again, by typing exit and hitting enter until you are no longer in adb shell, just like last time.
  • The settings file should be updated on your device. This will not be applied until you reboot your device.
  • To reboot your phone, type adb reboot and hit enter.

I haven’t tried that method, since automatic removal works perfectly on my Samsung Epic 4G running Android 2.1, but let me know if that works for you by leaving a comment on this post, or by sending me an email. This method has been updated, and it works perfectly on my Samsung Epic 4G running a leaked ROM of Android 2.2.

UPDATE: I recently found out that WordPress changes certain characters slightly, which causes the SQLite commands above to not work properly. The SQLite commands are now in <pre> tags to prevent this from happening. This may be the reason that manual removal failed before for some users. Also, rather than pushing the file directly to the settings database, the guide is updated to push it to /data/local/ and overwrite it as root using cat.

UPDATE 2 (10/21/2010): I successfully got this working on someone’s phone, and they no longer have a sending limit (verified)! Special thanks to Jacob Miller for helping me out and for his patience while we tried commands on his Droid (Original), until we eventually got it working! 🙂 This guide has been updated to reflect the changes in the process that were necessary in order to get it to work.

UPDATE 3 (11/12/2010): On my Epic 4G running the leaked Android 2.2 Froyo ROM, I was unable to pull the settings.db file directly. I updated the instructions to include a workaround that worked for me.

NOTE: I have tested this method on the Android 2.2 emulator three different times, and it worked each one. I want to automate the process on actual, rooted devices, but at the moment, it only works on 2.1 unfortunately.

adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

Behold, Rapid Fire Mode!

Behold, Rapid Fire Mode!

Some of you have been wondering why there have been several releases in a row. I have been working on fixing as many crashes as possible, and preparing to introduce the one feature that will set EliteBomb Plus worlds apart from EliteBomb, without removing anything currently in EliteBomb. Rapid Fire Mode sends SMS messages in rapid succession, without waiting for any previous messages to send, resulting in much faster message sending. This feature will be available in the Android market soon for all “Plus” users. Please note that rapid fire mode is very experimental, and unstable. It is not recommended with unlimited, or any “high” numbers of messages.