Root [ROM] EvilKingdom - Stock Rom De-Odexed/Zipaligned.

[Apache Thunder]

Please note this is only for Boost phones at the moment.
​

CWM is no longer required to flash this rom.
If you don't have or want CWM, then you can download the hboot version and flash it to your phone via hboot. Link further down in this post.
​

Here's my first ever rom. It's stock rom with the latest OTA installed. It's de-odexed and zipaligned with root preinstalled. It also includes Titanium Backup built-in. I tested it on my phone and nothing broke, so it looks like it works correctly.

New Features as of Version 3:

1. Rooted.

2. De-Odexed both apps and framework folder.

3. Init.d support in kernel.

4. Titanium Backup pre-installed.

5. Quick Reboot widget built into system. It's a useful app for easy reboot into bootloader/recovery.

6. Pre-configured build.prop with edits to re-enable feature disabled by Apple vs HTC lawsuit

7. Un-secured kernel allowing root access over ADB when Android OS is booted up normally. (Before, you can only get root over ADB by booting into Recovery. But now I fixed that. )

5. Custom Boot Animation support for bootanimation.zip located at /data/local (not tested yet)

6. New graphical based installer using the Aroma Installer. (available only for CWM version of the rom)

To install simply copy the zip file somewhere to your SD card and install using ClockWorkRecovery. This wont wipe your phone so you should still have your apps and personal settings/data untouched.

Future features I may add in the next version:

1. Unsecured kernel. If I find out how to do this, (feel free to step in if you know what needs to be done to make it happen) I will add this in the future. Now available in v2!

2. Remove bloatware. As soon as I figure out what's safe to remove, I'll remove the bloatware from the rom. Removed bloatware. Some may still be present, but removed all the major ones.

3. More fancy CWM installer.Now uses the Aroma Installer for the graphical touch enabled installer.

CWM Installer:

EvilKingdom_v3_OptimizedDebloated.zip


Kernel Installer (flashes custom kernel in hboot. You MUST do this to update the kernel! Due to S-On kernel can only be updated in hboot!):

PH44IMG.zip
(now with root access via ADB! Be sure to redownload to get the latest version!)

hboot version: (this method will wipe personal data, if you have CWM, CWM version is recommended if you want to avoid losing personal data)

EvilKingdom_PH44IMG.zip

(remove "EvilKing_" form file name then save to root of sd card. Then flash using hboot. It will take a while to load. This is normal. This has been updated to be the same version as the new v2 release. Redownload this if you have downloaded it in the past.)

The PH44IMG.zip is installed using hboot. Hold Volume Down+Power to get into the bootloader screen. Make sure PH44IMG.zip is at the root of your sd-card prior to booting into hboot. Once booted, it will automatically load it and will ask you if you want to flash it.


No issues found thus far but let me know if you run into any bugs.


EDIT:

If something goes wrong or you need to send your phone back to stock in a hurry then try this hboot installer:

fullstock_PH44IMG.zip

Place that at the root of your sd card and rename the file so it doesn't have "fullstock_" at the beginning.

The boot,system,recovery are the official images pulled from RUU ICS leak. This will flash your kernel, system, and recovery back to stock.

 

[haris163]

Great work! I am sorry if it is obvious, but I have to ask: is any way to return back to stock (as if the root and/or custom ROM never happened)?

 

[zombu2]

you know getting htc to hand you the source code is like trying to get a hold of the president ...... next to impossible ..

these ppl either just play dumb or just say no
but i m not done pestering them .

 

[guyphs]

Awesome! I was running the rom over at SDX but for whatever reason it was showing 1.05. I'll swap it out for this, and still get to use 2fast's power menu mod and the nonsense patch that's floating around over there.

You da man.

 

[guyphs]

Great work! I am sorry if it is obvious, but I have to ask: is any way to return back to stock (as if the root and/or custom ROM never happened)?

The only way I can think of is to restore to a pre-root nandroid backup via CWM, then flash stock recovery back onto the phone via hboot or adb then relock the bootloader. Even then, though, the bootloader would be "Relocked" and not "Locked" so I'm not sure it's possible to return the phone to 100% oem stock after you've unlocked the bootloader, but you can get close.

 

[Apache Thunder]

I can upload an hboot archive that will restore your phone to full stock in one go. I'm uploading it now.

EDIT: File updated. Check the first post.

EDIT:

Also, the system.img file I made works! But root was broken. I forgot to manually enter the chmod command to pass root permissions back to the su binary and Superuser.apk. If I can get root working again, the system.img method will work!

However one downside, flashing the system.img to the phone via hboot wipes personal data. Don't ask me why it happens. Probably not avoidable due to the nature of how it works.

But on the plus side it comes with Titanum Backup preinstalled so it won't take long at all to reinstall your apps with it.

 

[asusodin]

How do you install ClockWorkRecovery?

 

[Apache Thunder]

Now now, let's not let this devolve into another shouting match.

As for the original question, there is only one version of CWM available but can't can't be posted here since it violates gpl liscense. But pop me a PM and can point you in the right direction.

 

[asusodin]

Likewise my Friend..................

 

[smith058]

Hboot kernel wont flash.... says
"main version is older!
Update fail!"

 

[Apache Thunder]

You may have flashed a zip in the past that used a newer version string in the android-info.txt file. If you have not installed the OTA update from June yet, then try this one first:

(can be found under "mainver" setting in android-info.txt file in the PH44IMG zip file)

1.10.653.3

Only if the above doesn't work, try this one:

2.12.651.5

Do not use the second one if the first one works for you.

Also note that this is NOT compatible with the Sprint version and you'll get the version is too old error if you attempt to flash the hboot zips on the wrong carrier phone. You may also get an invalid CID error as well.

 

[ak47bluntz]

hey Apache Thunder with ur rom did u see a increase in speed?

 

[asusodin]

Apache Thunder Is a God...among infidels........


Thank you for all your hard work..........................:smokingsomb::smokingsomb:

 

[Apache Thunder]

Looks like I just found out how to "unsecure" the kernel so that ADB can have root access when Android is booted. (since before, only CWM can give you root with ADB when booted into CWM)

I will include it in my next release shortly.

EDIT: Android Commander confirms root access with ADB (Android Commander is basically a GUI version of ADB. It simply pass commands over to ADB seamlessly in the background)

 

[transitoyspace]

If i wanted to make updates to this rom, how do i go an make a signed zip?
by thanks for the wonderful rom

 

[Apache Thunder]

I used Android Kitchen to sign it. Though I don't really know what impact signing it does since CWM doesn't really care.

 

[Apache Thunder]

--- DELETED --- Forum failed to reload. Thought first post didn't go through.

 

[2fast4u88]

You may have flashed a zip in the past that used a newer version string in the android-info.txt file. If you have not installed the OTA update from June yet, then try this one first:

(can be found under "mainver" setting in android-info.txt file in the PH44IMG zip file)

1.10.653.3

Only if the above doesn't work, try this one:

2.12.651.5

Do not use the second one if the first one works for you.

Also note that this is NOT compatible with the Sprint version and you'll get the version is too old error if you attempt to flash the hboot zips on the wrong carrier phone. You may also get an invalid CID error as well.

This isn't picking at you or anything, I just want to explain it so you actually know how the ph44img.zip is working.

Cidnum:
Is your cid, and is checked upon. If it isn't supercid aka all 0's, it will always check it. So this means Sprint Design, HeroS and Boost Design will need a matching .txt for the cidnum. If it doesn't match it will throw a cid error if only on the htc unlock.

Mainver:
Is your firmware version, which is stored in the misc image. Where the .txt checks against your firmware version number. If the number is lower in the .txt then that of the misc. You will get a firmware version to old. If it is the same it will flash, along with if it is higher it will flash.

Now comes the other thing with the Mainver: In the .txt. If you run a img.zip with a higher mainver it will update the misc image. Which means if you never ran the new ruu or similar. The misc image will show the new version if you ran a img.zip with a newer firmware version number. In turn it will cause issues for people wanting to run the last ruu they had ran.

In turn everyone that has used the 2.12.651.5 just borked any update for there boost design. So now they will need a fixed misc image. You need to use 1.10.653.3 for the boost design in the .txt. It is obvious you really had no clue what a fastboot image was doing. In turn it would have been best to ask me instead of looking in my files.

Also this in your first post is wrong: > Kernel Installer (flashes custom kernel in hboot. You MUST do this to update the kernel! Due to S-On kernel can only be updated in hboot!):

You can h-boot the boot.img, flash the boot.img from clockworkmod or fastboot the boot.img. Then for flashing a zimage you need to mod the boot.img. Where it then will allow flashing of the kernel in recovery. S-on doesn't matter, so that is some food for the thought.

 

[Apache Thunder]

I have since fixed the mainver of all my hboot images.

Keep in mind I originally did those edits just as I was getting into modding this phone. So pardon my ignorance over some of the details. But yes I have been aware of it for that last week or so and all my images have since been fixed to reflect that already. But none the less thanks for the information.

I have since removed the CWM installer zip and modified any other zips I had that had contained CWM so they no longer have CWM. I have also fixed the version string on all the zip files. So if anyone is continuing to get the error it's because someone else is passing around the files with the bad txt file and is beyond my control.

As for the misc image, is there any way of rolling back the version stored in it?

Also your boost release of the new CWM version still has the old 1.10.653.2 version string. Thus anyone who had gone through the June OTA update will get a version is too old error when they try to flash your image. Why not set it to 1.10.653.3? Since RUU and hboot can still flash same version images, there's no harm changing it to the latest string. Wait unless the current RUU is the older version? I recall the leaked RUU had the 1.10.653.3 version string?

EDIT:

I found this:

http://forum.xda-developers.com/showthread.php?t=1526316

Looks like it can fix the stored version string in the phone's misc partition so that RUU updates and hboot images will pass version checks. I will test it first and will make use of it in all my CWM installers.

 

[Jaay Dogg]

Just curious on how you built/made this rom ? did you build from source ? or is this extracted via ADB ? Or ????

 

[2fast4u88]

Just curious on how you built/made this rom ? did you build from source ? or is this extracted via ADB ? Or ????

Ok looks like I can post in this thread now. He either dumped the system partition or started with a cwm backup. Then packed it into a .img. Which in all honesty is a waist. It is a pain to do and really nothing to offer at all. I recommend to just stay with recovery flashable zips if wanting custom. Basically what is going on in here is the same I have seen on the sammy's. Which I never understood the real purpose of it.

O ps htc roms have no source code

 

[Apache Thunder]

Yeah the main purpose of the system.img is for users to flash a custom rom without using CWM. Mods won't let me post any link to your CWM for already mentioned reasons.

I provided links to CWM installers and users who already have CWM can use that. Plus flashing the system.img will result in a data wipe anyway so it's only recommended for new users.

The system.img method could still be useful for a full CWM/Rooted rom install in one go. Sorta like a super backup. Rather then installing CWM, then installing rom in CWM. One could use hboot to install CWM and custom rom at same time. Of coarse I have not made a flashable zip that includes CWM in my rom, but that's just one example of it.

I've already had one user report rooting using my stock root hboot image where he had problems trying to get other methods of rooting to work. So the hboot images still have their place. My hboot images are meant mostly for new users who are just now unlocking their phone.

Since that results in a data wipe, installing the rooted rom or my custom rom via hboot would be faster for them then trying to hunt down CWM installing that and then flashing the rom from there.

Yes it is a bit more involved to make the system.img files, but I'm mainly just covering a little used method of rom flashing that may still be usefull for some users.

Also, I am not aware of an RUU installer that includes the June OTA update unless the one I have now is the one. Then maybe wasted my time doing it from CWM dumps, but none the less the result is the same.

 

[Jaay Dogg]

I'm having problems when I try to recompile the framework via apk manager, means something 's not stock in the framework, so I'm gonna have to re-extract the framework. Gotta have pure stock framework to decompile, I've done this before, so I'll fire up the laptop & get to extracting.

 

[Apache Thunder]

I haven't changed anything in the framework apk. Odd that it would say it's not stock.

 

[Jaay Dogg]

well i know from personal expierence when decompiling CM7 or ICS roms that if anything has been changed it won't recompile without errors & the size of your framework is 10.2mb & when i catch errors it only recompile's 6.82mb this is no good, Do you now how to decompile with apk manager ? If not it's all good i'll extract the framework via adb & then should be cooking with fire. just fired up my laptop so i'm on it