Database Info

Updated 3-3-09 - JFv1.43 for UK RC9 firmware! also ADP 1.5 post 2

Official APD1.5 image in Post 2
Here's the new JFv1.43 RC9 for all you UK users. Enjoy!
--- announcement for JFv1.43 Holiday
New! JFv1.43 is a bugfix release for the Holiday (ADP1.1h) version. This release fixes the issues most people were having with Latitude hanging after clicking "I agree". More info on my blog.
The links below have been updated with the new versions.
--- announcement for JFv1.42
The ADP1.1h version of JFv1.42 is out! This is based on the new ADP1.1 OTA that was put out this morning. I've also released a JFv1.42 version of RC33, that fixes the issue with adb not being enabled in recovery mode. You can find more details here
The links below have been updated with the new versions.
--- announcement for RC33
The RC33 version of JFv1.41 is here! Links are below. It is essentially the same as the RC30 version, as far as my changes are concerned. You of course get all the goodies included in RC33.
Note: RC33 contains a radio update. I chose not to include this in the RC33 update itself, because I personally don't want it re-flashing the radio every time I apply this update. Here (md5: cf8714d273fb0274574d9e3831e11fdd) is a separate update that *just* flashes the radio. You only need to install this update once (unless you happen to flash an nbh at some point in the future, in which case you should re-flash the radio afterwards).
To check if you have the new radio, go into the about phone screen in settings and check the baseband info. It should end with 1.22.14.11
note: I have no clue what the differences are in the new radio. I just assume they are good, and that it's better to use the new radio than the one from RC30.
note: (yes, I love Notes ). You shouldn't need to do a wipe if you're going from RC29 or RC30 to RC33. I've even had reports that you don't need to do a wipe going from ADP1.1 to RC33. Give it a shot if you want, and let us know if you had to wipe. Don't forget to do a nandroid backup first
note: (couldn't resist). The first/initial boot after upgrading to RC33 make take a minute or two. Just give it some time before concluding that you need to do a wipe.
------------------------
(original release annoucement for JFv1.41)
This version contains... *drumroll* multi-touch support! Thanks to lukehutch, zinx and ryebrye, this build allows android applications to receive multi-touch events. The built-in browser now supports multi-touch zooming! It also includes an "Auto-Rotate" setting that you can enable, to allow it to change screen orientation, based on the orientation of the phone. You can turn on auto-rotate in the browser settings (it's off by default).
See lukehutch's blog post for more information about the new multi-touch support, as well as a few other demo multi-touch apps he created that you can try out after installing JFv1.4. He also mentions a few issues that are present in browser, that you might run into while playing with zoom.
Other changes of note for JFv1.41 include:
a console in recovery mode. You can press alt+x to exit out of the recovery program and go directly to a console.
the ADP1 build is now based on the ADP1.1 firmware. See this thread for information about the changes in ADP1.1
the ADP1 build now includes .odex files for all of the system apks and jars. This means that you will have more space available in /data for all of your apps and caches, although less space available in /system
busybox's vi should now save files correctly, instead of saving them as blank files
One thing that I would like to point out about the ADP1.1 build is that it allows you to skip the initial google registration. This will make registering over wifi painless. You just click the "skip registration" button in the registration app, enable wifi in settings, then open the registration app again by trying to access one of the google apps (gmail, market, etc.), and then you can register over wifi.
Downloads:
ADP1.1: (md5: 076ba12c3e733805ba1c865ab48d370c)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.43/JFv1.43_Holiday.zip
http://jf.andblogs.net/2009/02/11/jfv143/
RC33: (md5: 6ecf0ea8175e1aece8a770253447b6a8)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.42/JFv1.42_RC33.zip
http://jf.andblogs.net/2009/02/10/jfv142/
RC9: (md5: 5a722ad92c9dd1081987b2ad9814111f)
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.odiness.com/v1.43/JFv1.43_RC9.zip
http://jf.andblogs.net/2009/03/03/jfv143-rc9/
In the console in recovery mode, there are a number of "special keys" that you should be aware of:
Code:
ctrl search
caps lock menu (on the keyboard)
arrow keys call + w,a,s,d
change virtual console call + 1,2,3...0
scroll console home + w,s
page up menu (above the trackball) + w
page down menu (above the trackball) + s
home menu (above the trackball) + a
end menu (above the trackball) + d
escape back
reboot menu (above the trackball) + search + backspace
Also, you can type "reboot" to reboot, and type "recovery" to go back into the recovery program.
JFv1.41 can be installed in the usual way. Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. If you are switch between versions, e.g. from RC30 to ADP1, you must also do a wipe in recovery mode (alt+w). This will clear all your data/settings/apps, and you will have to re-register once it boots back up. If you are staying on the same build, i.e. from JFv1.31 RC30 to JFv1.41 RC30, then you shouldn't have to do a wipe.
NOTE: If you are on the stock ADP1 image, you will need to upgrade to JFv1.31, then boot normally at least once, before upgrading to JFv1.41, to keep from having to perform a wipe. If you try to go from stock ADP1 -> JFv1.41 directly, you will have to do a wipe.
NOTE: If you end up with 2 Superuser whitelist apps in the app menu, you can uninstall one of them in Settings->Applications->Manage Applications. There will only be 1 that is uninstallable, so don't worry about uninstalling the wrong one.
Note: To install these updates, you need to have a recovery image that uses test keys. If any of the following are true, you most likely have a recovery image that uses test keys
you have installed my modified recovery image in the past
you have an ADP1
you currently have one of my modified firmwares installed
If this is your first time installing one of my firmwares, you may be interested in the other changes that have been made in previous versions, which are included in this version. Some of the notable features include:
Many more commands are available to use on the terminal. busybox is included, to provide standard commands like cp, grep, less, more, vi, sed, cp.. etc.
A secure way to get root access, through Koush's superuser application. To get root, open up terminal emulator and type su. A new window will open asking if you want to allow root access. Click "Yes" or "Always", and it will go back to the terminal emulator, and you'll have root access
A number of useful kernel modules that you can use. For example, ext2, cifs, and a host of others
A full phone backup utility. Boot into recovery mode with home+power, and then press alt+b to perform a backup. It stores the backup as .img files in a subfolder of the nandroid folder of your sdcard. To restore the backup, you have to have the engineering spl or hardspl installed, and then flash the images with the fastboot utility
ota updates are disabled. This is to prevent t-mobile from automatically updating your phone with a new update that removes your root access.
some applications that are missing on RC8 (the uk version) have been added. For example, the voice dialer and the amazon mp3 store.
when you connect to the phone using adb, you have root access
I've attached a full changelog vs the official builds for each version.
Here are the updated Build Environments for JFv1.41. These can be used to create an update identical to JFv1.41, or to create one modified to suit your tastes/preferences. You can find more info about the build environments over at my v1.31 post
ADP1.1: (md5: ce591333f2252d805c5eaccae332f5e7)
http://jf.odiness.com/v1.43/JFv1.43_Holiday_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/02/11/jfv143/
RC33: (md5: b3b0bc89c4b417b6ce6728fd9cc2c7fc)
http://jf.odiness.com/v1.42/JFv1.42_RC33_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/02/10/jfv142/
RC9: (md5: 0d0845f85382e5689f015a2904f928a0)
http://jf.odiness.com/v1.43/JFv1.43_RC9_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://jf.andblogs.net/2009/03/03/jfv143-rc9/

Official ADP1.5 image
JesusFreke’s AndBlog
The official 1.5 firmware is here finally!
When is your 1.5 coming out?
May 1, 2009
The answer is… wait for it.. wait for it..
NOW!
If only i had a nickel for every time someone asked me that over the last week or two
This build is based on the official HTC ADP1.5 image. You should install the 1.5 radio from that HTC page before using this build.
Some of the important changes/features
* I’m now including a much better Superuser app, courtesy of zinx
* I’ve rebuilt the kernel and enabled netfilter support, to allow tethering.
* You can see/download both paid and protected apps in the market
* Luke’s multitouch kernel patch and browser patch have been ported to the .27 kernel and 1.5 browser.
* Support for the “apps to sdcard” hack. There’s not a separate “apps to sdcard” build. You can use the same build whether you are doing apps to sdcard or not. Thanks to haykuro for explaining how he’s done this in his images, so I can make my builds compatible. See here for a tutorial on setting this up.
* I’m not including a recovery image in this build. I ran into some snags getting all of the recovery features to work with the 1.5 recovery image, so I’ll forgo that for now. If you don’t have a spiffy recovery image yet, I’ve packaged up the most recent recovery image from JFv1.43 as a separate update.
If you are already running a “rooted” build (ADP/mine/haykuros/the dudes/whatever), it is available for download via the jf updater app (available on the market). If you don’t see it, open up the app settings, and choose either ADP1 or “All the updates” for the “System Mod Version” setting.
Or you can always download the update.zip file below and install it yourself. If you have a G1 and this is your first time installing a community firmware, you’ll need to follow any of the multitudes of tutorials out there for rooting your phone.
You can try to upgrade without a wipe, but if you run into any problems (for example, su/Superuser doesn’t work), you’ll need to perform a wipe. If you don’t want to wipe, take a nandroid backup before upgrading, so you can revert back to the backup.
JFv1.50 ADP1.5
JFv1.50 ADP1.5 Build Environment
JFv1.50 ADP1.5 CHANGES
JFv1.43 Recovery Only

Nothin but the best from the best! Works great man!
Thanks to you and everyone else that helped make this possible.
Stericson

Awesome! Great job mate, about to install.

OMG YES!!!!

Third!! Great Job JF, LukeHutch, Zinx, RyeBrye and everyone else who helped with this. Working great for me!

superb
will give it a go in a few hours
u've got to be the top supporter of the android community.
keep it up!!

Awesome!
Couldn't wait for a new update. You delivered like a champ!
Thanks peeps!
EDIT: Just a question, do I need to format my SD again like the other post says?

hey JF
for each of your releases you have said "If you are staying on the same build, i.e. from JFv1.31 RC30 to JFv1.4 RC30, then you shouldn't have to do a wipe" but every time i install one of your builds i get stuck with an infinite boot loop and have to perform a wipe. Any ideas? btw ive only used your adp builds on an adp

Great job, to you and all who contributed. Works great so far, loving the multi-touch zoom.

Installing now, i'll post in a sec when it works
Edit: of course, it works great!! multitouch is something I would have never expected
Edit2: just installed rc33 and the radio update, everything works great . Posting from it now!

yesssssssssssssssssssssssssss

do the jf rc30 1.3 themes work with the new update or we going to need to update the themes

awesome job everyone! installed and loving it. thanks for all your hard work

Manacit said:
Installing now, i'll post in a sec when it works
Edit: of course, it works great!! multitouch is something I would have never expected
Click to expand...
Click to collapse
Nobody expects the Spanish Multi-Touch Inquisition!

kron2 said:
do the jf rc30 1.3 themes work with the new update or we going to need to update the themes
Click to expand...
Click to collapse
The themes for RC30 and RC8 should work. The only thing you have to watch out for is if the theme overwrites Browser.apk, you'll lose the multi-touch browser.
The themes for ADP1 will most likely need to be updated to work with ADP1.1 unfortunately.

This Is Great!

thx jf and the update works great

ok so i need to resign my browser.apk before doing the template or not? thank the best release yet
JesusFreke said:
The themes for RC30 and RC8 should work. The only thing you have to watch out for is if the theme overwrites Browser.apk, you'll lose the multi-touch browser.
The themes for ADP1 will most likely need to be updated to work with ADP1.1 unfortunately.
Click to expand...
Click to collapse

..wow
/10char

[Updates] TwistedZero Instaler w/GUI For NOOBS

Im removing the Download till i Fix a bug. I will upload a new version Tomorrow and re post link.
Sorry about this. Im new to this.
I have finished my GUI interface for Twisted Zero's new updating methods.
It is still very early beta but i updated my phone with it. It is a very simple Visual Basic app that runs Twisted Zero's Preparation.bat file. Because no files are built into my program they can be swapped for other Twisted Zero builds(that have the same configuration).
The requirements are all of the ones on Twisted Zero's post for the roms and the New Recovery by Cyanogen And maybe the newest .net by Microsoft I haven't tested any others than the newest.
Once you open the program in order to start the update you must check the button asking if you have the new recovery (Its not required to have but is a good idea). Then you can start the update It will ADB push all necessary files then reboot your phone into Recovery mode. Once in Recovery mode press update from update.zip This is the only input needed by the user. After that restart and Welcome to Hero.
Version 0.0.1
This is the M build by Twisted Zero
YOU HAVE TO EXTRACT THE HERO INSTALLER TO C:\Program Files IT WONT WORK ANYWHERE ELSE!
Some thoughts
1. Read Twisted Zero's post
2. Make sure you have apps to sd (this program wont ADB without it)
3.Twisted Zero, Cyanogen and Me are not responsible with what you do with this.

Has anybody used it. I need some feedback to fix stuff.

So, this installes twistedZero rom from any rooted rom?

any rooted Rom already using apps to sd could technically just download hero update and do system only update then update only update. There is a download issue right now but I'm fixing it as I post this.

This is to update from your phone via pc from any rooted rom to the new rom without the android sdk for adb

[KERNEL] OTA 1.47.651.1 stock boot.img in update.zip

CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded

I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.

Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!

I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???

snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.

Any comments from people that have this applied (and working with full root)?

Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.

That worked Thanx

Kernel's working just fine with Avalaunch's Froyo ROM.

joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.

Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.

lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!

Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.

Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk

[Q] Simply Honey Revolution 5.1 on SGS

I've got some questions regarding the install documentation of Simply Honey 5.1 Revolution for SGS ROM
Install Instructions Coming From Froyo OR ECLAIR(CM7/MIUI ODIN TO STOCK FIRST)
First Question regarding CM7 - Does this include CM7.1 as well? The example outside the parenthesis says Froyo or Eclair - CM7 is GB so this is not clear
- 1. Disable any Lagfix.
- 2.Download - xxx LINK REMOVED xxx This is the light version with hardly any apps and only one keyboard and 4 lock screens.
- 3. Flash via ODIN. USE 512PIT FILE.
- 4. Let phone boot. Wait 15 minutes and reboot.
- 5. Enjoy. You may now proceed to the MediumOR Large.
What is the difference between medium and large? Where are these files? I see a Light and Full but nothing else.
[/SIZE]
Install Instructions
Coming from Any Gingerbread Rom (If bootloaders aren't installed or you have trouble follow steps above.)
CM7 issue listed above. Any GB rom sounds like any - including CM7 this adds to the confusion of what will/won't work here.
1. You must first be running a Gingerbread rom (Doesn't matter Lindroid, Rainbows, your cousins top secret GB rom.) If you are not then please follow instructions above.
2. Place SimplyHoney5Beta1.zip on your SD card
Filename is out of date. Please link new file or list correct filename. If the ROM is out of Beta, the filename in the instructsions should reflect this.
3. Use rom manager or flash through recovery.
4. Let phone boot. Wait 15 minutes and reboot.
5. Enjoy
The new script is wipe for who come from SH <3.3 and from Froyo/GB!
It doesn't do wipe if you're running SH 3.5+ ROMs! Very Simple and automatic!
I've called it the "Anti-Noob" Script!
ONLY FOR CWM VERSIONS!! ODIN VERSIONS ALWAYS DO WIPE!!
Downloads CWM Full Roms
Simply Honey 5.1 Final
Light: xxx LINK REMOVED xxx 5 Locks Screens/ Modify Power Control Menu Options
Full: xxx LINK REMOVED xxx 10 Lock Screens
What is the purpose of Update1? Should this be flashed after Full? Is it flashed through CWM recovery? Some additional information here might be helpful. It is linked but no indication of why or when one would use it.
- Update1 - Gallery3D, Polaris Office, SNS Account -
xxx LINK REMOVED xxx
Is this section below a second set of instructions - you seem to list a If you have problems section above; however this one is more comprehensive. I'm not sure which one to follow if I have problems.
HOW TO
The anti-noob install script is a double edge sword so to speak. On one hand it is convinient as it doesn't do a wipe install if already on Simply Honey 3.5 and up. On the other some data needs to occasionally be wiped. That said if you experience ANY problem please follow the steps below.
1. Force Close of certain apps...go to settings/applications/manage applications/all and clear data of the offending app.
If that doesn't work then use Tiatnium backup to wipe data and uninstall the app (as long as it's not a system app such as phone or contacts or settings, you get the picture. Now you are free to re-install the app.)
2. The next step is to try and re-install the rom. Boot into recovery and select install from SD. After it's done and you reboot give it the 15 minutes. Now try again to recreate the original problem.
3. If the problem persists then boot recovery and wipe data factory reset and re-install the rom.
4. Problem still there then ODIN to stock (Stock ROM recommendation?)with repartition, ODIN the Simply3.8 Odin/Heim package. After rebooting boot into recovery and install the latest release of Simply Honey.
If these instructions are still useful, please link to SH 3.8 Odin/Heim package pls.
5. If all else has failed make a backup of everything you want saved to your computer. Boot recovery and go to mounts and storage and select format SD. After it's done reinstall Simply Honey's latest release.
6. If your problem still remains after doing all of this or just the last step then I suggest finding another rom as this one may not be for you.
I made an attempt to convert from CM7.1 this weekend; it wasn't clear what was going wrong but I couldn't get SH 5.1 to load properly. I tried to Odin the SimplyHoney 5.1 light version as per the first group of instructions, however, it was unclear whether I needed to repartition or not. the phone began the robot voice indicating partitions were not correct. I odin'd back to stock and reflashed CM7 with no problems.
Please understand I'm not trying to be critical, and I have rooted/flashed a number of phones over the years. Although I've been a fan of CM in the past, it's absolutely not where it needs to be on the Galaxy S/Vibrant and the Nightlies are not getting there fast enough. After reading the settings/features and positive comments for this ROM I'd really like to try it out, but the vague instructions and lack of links are not making this process easier.
If one of the developers can answer some of these questions, I'd be willing to assist writing documentation for this and future SH releases.

[HOW TO] v6 SuperChager - ready patched services.odex - HTC One S (Stock) ONLY

I'm sure that a lot of people already know about the -=V6 SuperCharger=- by zeppelinrox.
If you are not familiar with his great work please follow the link above and read more about it on his thread.
Those of you who have already tried it on their HTC One S (stock) will probably know that there is a whole different level of complexity when it comes to installing it on an ICS ROM. First of all, on any ICS ROM you have to patch the framework library services.jar to get the full functionalaty of the V6 SuperCharger. To make matters worse the HTC Sense is an odexed ROM meaning that you have to do all the patching manually, which is by no means a trivial exercise. Of course you may decide that you don't want to go patching any files and you may be happy with the limited functionality that you get from the V6 SuperCharger as it is. If that's the case you probably won't find this thread very useful...
However, if you're one of those who will not settle for anything less than the full functionality, you need not worry anymore!
Over the last few days I've done all the hard work of decompiling and manually patching the stock services.odex library so people don't have to do it themselves anymore. Not only that, but I've prepared separate versions of the services.odex for each of the three launcher SuperCharge options available:
1. Hard-to-Kill (downloads 1 & 5)
2. Die-Hard (downloads 2 & 6)
3. Bullet-Proof (downloads 3 & 7)
In addition, I'm also including the stock services.odex file so you can restore it back to your system in case you have any problems with the patched files.
4. Stock services.odex (download 4)
Installation procedure:
DISCLAIMER: I take no responsibility whatsoever for anything that might go wrong with your phone, for any and all data loss, for bricking your phone, etc. You do this at your own risk and it is 100% your responsibility.
WARNING! The files provided are specifically for, and have only been tested on, HTC One S with Stock Sense ROM v1.53.401.2 (Europe). These files may also work fine on different versions of the Stock Sense ROM but I haven't tested that. However, if you use them on any other (custom) ROM they are most likely to get your phone either stuck at boot or into a boot loop!
REQUIREMENTS:
a. First and foremost your phone needs to be rooted and have BusyBox v1.16.2 or higher installed. This is a requirement for the V6 SuperCharger script to run so there's no way to get around it.
b. To install the patched services.odex file you ideally need to have a custom recovery installed, such as ClockworkMod. This way you can just flash the patched services.odex from the recovery and if anything goes wrong, simply flashing the stock services.odex over should get you out of trouble (stock file also provided as a recovery update). While it is not absolutely necessary to save a recovery image of your ROM, I would strongly advise you to do so as it's always a good idea to have a recent recovery image to hand just in case (e.g. there is a chance that the stock services.odex included in here may not work if you have a region/operator specific Sense ROM on your HTC One S). Please keep in mind that the stock services.odex included in here comes from Stock Sense ROM v1.53.401.2 (Europe) so it may not work on other versions of Sense ROM!
c. If you don't want to use the recovery update file, you can also download just the services.odex and install it manually. However, if you choose to do this then you're on your own as I don't have enough time to write a tutorial on how to install it manually.
Step 1. If you haven't already done it, go to the -=V6 SuperCharger=- thread by zeppelinrox and read up on the script and what it does.
Step 2. Follow the instructions on the thread (see Step 1) on how to install the -=V6 SuperCharger=- on a typical non-ICS system.
You can get the latest version of the script from this post: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Step 3. Forget about manually patching the services.jar or the services.odex file! Just download the version you need from the bottom of this post AS WELL AS THE STOCK VERSION! You will need the stock if your phone gets stuck on boot. For the installation, see the two options below. Before you do anything however, I strongly advise you to save a system recovery image just in case.
a.The first 4 attached files, named update-services.odex-[something].zip, are recovery update files meant to be flashed via a custom recovery such as ClockworkMod. After flashing the recovery update, also wipe cache and dalvik cache and then reboot.
b. The last 3 attached files are just archives of the patched service.odex files. If you want to go this route you can find some guidance on the -=V6 SuperCharger=- thread in terms of where it needs to be installed and what permissions it should have. Also, if you're using this method don't forget to do a SuperClean & Reboot using the option in the V6 SuperCharger script.
Step 4. It is normal for the first boot after installation to take longer than usual. If your phone has gone past the boot animation and is displaying a windows saying something like 'upgrading applications...' then it's all gone fine so just wait for it to finish. If your phone hangs on the boot animation longer than usual it means that it's probably stuck there and the patched services.odex file is not compatible with your ROM. DO NOT PANIC! Simply go to the recovery instructions further on.
Recovery.
a. If you phone is stuck on the boot screen, hold the power button pressed for about 10 seconds so that the phone goes into hard power off (the touch keys below the screen will start blinking after a few seconds, that's normal).
b. After that just boot into recovery as you nomally do (while holding the volume down pressed, also press the power button briefly and the phone should start into the boot menu; in there, scroll using the volume up / down keys and select the RECOVERY option by pressing the power key).
c. In the recovery simply flash the stock services.odex update file, wipe cache and dalvik cache and reboot. Now the phone should start up fine but your services.odex will not be patched.
d. If your phone is again stuck on the boot screen, you'll have to do a full restore of your ROM from the image that I have strongly advised you to save earlier.
Good luck and I hope you find this useful! ​
Oh, and pleeease use the Thanks button! ​

thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0

Bxrxyxaxn said:
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Click to expand...
Click to collapse
Thanks, but if you're using this patch on Noble 4.0 it will have absolutely no effect.
That's because Noble 4.0 is a deodexed ROM which means that the services.odex file you've just installed is simply ignored by the system.
Instead you should patch the services.jar file using the online patching tool for deodexed ROMs provided on the V6 SuperCharger thread.

will try on stock T-MobileUS nand later...but thanx for the heads up, will do, edit: Noble already has it

Flashed bullet-proof on stock TMOUS rooted ROM. Caused boot loop. No surprise, it's a different ROM but thought I would give it a go anyways.
Thanks for the post, will definitely use if I go with an EU ROM.

tmobile us
Will this work on the tmobile us one s? Update: noticed the post above stating it doesnt work for T-Mobile us.