XDA has always been, and will always be, a place for development. However, there are a lot of people who come to XDA to find and flash custom ROMs. In fact, a lot of newer developers attribute their joy of flashing ROMs as their primary motivation for getting into development. As long as there are developers, there will be users that want to play with it. For HTC EVO 4G owners, there is now a mod that makes the flashing process a little more fun.
The mod is called Just the Basics. It is a small package of popular and often used applications that flashers can quickly add to their ROM installations. Basically, you download the AROMA-enabled zip and flash in recovery after the ROM. From there you can choose what applications you want installed, reboot, and not have to use a backup app or the Play Store to download them again.
The list is pretty limited right now, and includes:
browsers: firefox and dolphin
original apps: the goodies
games: everyones favorite HTC game………TEETER!
XDA Senior Member lreyes says that there will be updates and additions as time goes. After a few decent updates, this could definitely be a go-to mod for frequent flashers who want as many of their applications installed as possible before the first boot.
To learn more, head to the original thread.
The last time we brought you news about TWRP, it was to announce that TWRP 2.2.2 had been released. It had fixed a lot of bugs from the initial release of TWRP 2.2 and added a few new features. Very recently, TWRP has been updated again to version 2.3.
There were a whole bunch of awesome improvements with TWRP 2.2 and a lot of unique and brand new features as well. TWRP 2.3 promises no less. The official change log includes:
Rebased onto AOSP Jelly Bean source code
Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
ADB sideload functionality from AOSP is included in 2.3, see this link for more info
Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
Faster boot times
Added charging indicator while in recovery (only updates once every 60 seconds)
Additionally, XDA Recognized Developer Dees_Troy has reported that there is now support for spaces in backup names. Before, if you added a space to the name of a backup, it would not restore. Now users can use whatever naming convention they want.
One of the biggest changes, though, is all of the TWRP being rewritten in C++ and its move to recovery API 3 instead of API 2. With the code rewrite, it will allow TWRP to update more quickly and with more stability. With the API 3 change, it means that some flashable zip files may stop working because the developer needs to update the update-binary. If you don’t want to wait for the developer, or the developer has ceased working on the project, you can find one to use on TWRP’s official website. To install the latest TWRP, you can use the Goomanager application. Simply open the application, hit menu, and install open recovery.
If you want to check out the latest TWRP recovery for your device, check one of the links below.
August 2, 2012 By: Former Writer
For most devices, obtaining init.d support is no big deal. Usually, users need to only install a kernel or ROM that supports init.d, and then they can install any scripts requiring it. However, not all devices have such ROMs or kernels. Alternatively, some users may enjoy their current ROM/kernel setup and would rather not change it just to gain support. For HTC EVO 4G users on ICS, this may no longer be a problem.
The solution is called init.d Stapler. It’s a modification that EVO 4G users running an ICS ROM to gain init.d support in their ROM without having to swap ROMs or kernels. Developed by XDA Forum Member Mephistonian, the mod is easily flashable in custom recovery making init.d simple. As Mephistonian explains:
This is a flashable .zip file that will essentially inject (or staple as I like to say) the support of the INIT.D script into your current ICS rom. As I said above, this SHOULD (YMMV) allow the support of any tweaks that require the INIT.D script.
As with any mod, there is a possibility that it may not work for you. It has been confirmed working by a number of users, though, on a couple of different ROMs.
For more info, check out the original thread.
July 29, 2012 By: Former Writer
Not long ago, CyanogenMod 10 was announced. Not too long later, there were preview and unofficial builds released for so many devices that XDA TV’s Jordan has spent the last two weeks talking about it. Well, following in those footsteps, unofficial AOKP Jelly Bean has been announced and released to a few Nexus devices, and has begun expanding into the non-Nexus area. Among the first non-Nexus devices to pick up AOKP Jelly bean are the HTC EVO 4G, AT&T Samsung Galaxy S II Skyrocket, and the AT&T Samsung Galaxy Note.
As should be expected by now, all three ROMs have their issues. Very few Jelly Bean ports are fully functional, but the AOKP builds have about as much working as the CM10 builds at this point. So while they may not be daily driver for most, they are definitely something to try out and have fun with. XDA Recognized Contributor Mazda, along with the rest of Team DIRT, are responsible for bringing the unofficial AOKP to the EVO 4G. They are also the ones who brought unofficial CM10 to the EVO 4G. The AT&T Skyrocket build comes from XDA Senior Member armyveterangunner29 with some help, and the AT&T Galaxy Note build comes from XDA Senior Member JamieD81.
In the list of things not working, all three ROMs cite that they have similar issues to CM10 builds on the same devices. This includes some hiccups in Google Now functionality, camera issues, some video codec issues, and other bugs. These bugs are expected to go away in later releases, so if you’re looking for something more solid, all you need to do is wait.
For additional information, check out the thread links below.
Jelly Bean is everywhere. Coming down from Google like sweet, jelly bean-like raindrops all over XDA, the newest version of Android is being enjoyed on devices as old as the HTC HD2 and as new as the Samsung Galaxy S III, and its US Variants. Now, the now legendary HTC EVO 4G is getting its own taste of Jelly Bean. This adds yet another old timer to the list of devices running Jelly Bean.
The EVO 4G Jelly Bean ROM, which is an unofficial CM10 port, comes to us from XDA Recognized Contributor Mazda along with the rest of Team Dirt and quite a number of other contributors. The ROM is surprisingly stable with only a few known issues, including:
- NO 4G (did you really expect that to work???)
- NO Netflix, Hulu Plus, HBO or whatever you guys watch….is not working!
- “System” in settings FCs (possible fix in v1.2)
- A few other things, just let me know
Given that 4G has been a problem on EVO 4G AOSP ROMs since the days of CyanogenMod 6, that issue was more than expected by EVO 4G users. The rest are typical of the various Jelly Bean ports going around on different devices. If you can live without camera, video playback, and 4G, then this ROM could perhaps be a daily driver. If not, it certainly won’t be too long before these issues get fixed.
For more info, check out the original thread.
July 19, 2012 By: Former Writer
Not too long ago, we brought you news that allowed HTC EVO 4G LTE users to customize their bootloaders. The process was pretty cool, allowing users to make their bootloader look however they want—including making it look unhacked. After the initial project was released, users clamored for this to be made available to more devices. The requests were heard and responded to. Now, the plugin has been made available to make the bootloader customizer for a number of HTC devices.
The process for a developer to port this is not hard. XDA Recognized Contributor regaw_leinad, who developed the application and plugin, takes a time out from the stags (yes, that’s really him) to explain how:
it’s basically all written, they just need to fill in the values for their hboot, and embed the hboot.img into the exe. I already have a placeholder for the hboot.img and android-info.txt so a drag and drop over them should keep it embedded.
Regaw_leinad is also creating the application for the supported devices, but wanted to release the plugin first so users had a chance to get it sooner. The current list of supported HTC devices include:
While the list is quite large, one must keep in mind that not all of these devices have S-Off, and users must have S-Off in order to actually use this application. To get started, visit the original thread.
Recently, we brought you news of Paranoid Android being ported to the Sony Xperia Play. Well, we are happy to report that the list of ported devices is growing fast. For the uninitiated, Paranoid Android is a hybrid ROM that allows users to scale and project every app, every widget, even system components individually. As described in the Galaxy Nexus Jelly Bean port by XDA Forum Member molesarecoming:
To be honest, this is not tablet mode at all, it has nothing to do with silly build.prop hacks. This is the first and only Android rom to feature true Hybrid mode. This rom lets you scale and project every app, every widget, even systemcomponents individually. Remember, android is modular, everything is an app: Lockscreen, navigationbar, dialogs, popups, keyboards, widgets, and your regular apps of course. Apps have the capability to switch into various designs or layouts according to the device they run on. This can result in a complete new experience as many apps will transform to the better.
Now for every element that you like chose a mode (PhoneUI, Phablet/Nexus-7UI, TabletUI) and/or a size. You are 100% independent of the system DPI which runs nicely in whatever value it has been assigned to. You do not need to boot your phone into a certain DPI. Neither will most of the changes you apply require a reboot. You will not suffer from the myriads of troubles which normally haunt you under build.prop tablet mode. Your market, phone, etc. will all work, apps won’t shrink on you unless you shrink them yourself. This project will entirely transform your device, but retain the aesthetics and the feel of your phone.
In addition to the Galaxy Nexus, T-Mobile LG G2x owners now can enjoy a port thanks to XDA Recognized Contributor tonyp. I personally own this device, so I can speak from experience that it is stable enough to be used as a daily driver. Check out the ROM thread for more information and download links.
Other devices that have received ports include the HTC EVO 4G and EVO 4G LTE thanks to XDA Recognized Contributor mazdarider23. To get in on the action, visit the HTC EVO 4G ROM thread and EVO 4G LTE ROM thread. The list is growing very fast and is already quite large, check this page out to see if your device has received a port yet.
While it is still impossible (legally, anyhow) for users to transfer CDMA devices from one big provider to another (e.g. Sprint to Verizon), it is quite possible to switch from a big CDMA service provider to a smaller one. With tutorials on how to flash various CDMA devices to smaller carriers such as Boost or Virgin Mobile, users with CDMA devices may very well have more freedom than they initially assumed. For instance, owners of any of the HTC EVO devices, including the HTC EVO 3D, HTC EVO Shift 4G and the HTC EVO 4G can now flash their phones to a service provider named Page Plus.
XDA Senior Member Nevell has written a universal tutorial for all three devices that will get them off of Sprint’s network and onto Page Plus’ network with a little patience and a few modified files. The process is pretty long and will definitely take some time for first time users. The list of required software is pretty decent as well, including:
CDMA WorkShop (Paid or Demo) http://www.cdma-ware.com/workshop/demo/cdma_workshop.rar
Page Plus PRL’s (See below)
APN Backup and Restore
Page Plus APN’s
Of course, you’ll need to be rooted in order to get the MSL and the HTC Drivers, including the Diagnostic Drivers to make it work as well. Next, there are many of small tasks, from obtaining the MSL to changing the APN. All in all, not a difficult process, but users attempting to do it should be very careful to follow all instructions to the letter to avoid messing anything up.
More information, the download link for the Page Plus files required for flashing, and the full instructions can be found in the original thread.
January 30, 2012 By: Former Writer
Boot animations are one of those unique items on the short list of things that every single Android device has in common. Turning on the device, seeing the splash then seeing that little animation can mean a lot to some people.
Now, the power to make your very own boot animation is easier than ever with a step by step guide from XDA Senior Member Skullmonkey. The guide is pretty long, but relatively easy to follow and includes everything from recommended software to pro tips like using Notepad++ instead of Microsoft Notepad due to Windows formatting causing errors in the script you’ll be writing.
The requirements and recommendations are pretty straightforward and include:
-Each frame must be 480*800 px (thats 480 pixels wide by 800 pixels tall).
-Each frame must be saved in a .png format. (If you are using Photoshop, File > Save for Web & Devices to reduce the file size drastically.)
-Each frame needs to have some numarical value.
+Recommended would be something like frame0001.png, frame0002.png, frame0003.png, etc.
+Try to keep it under 300 images total
This tutorial is written for those who have the HTC EVO 4g, but the process of creating images and packaging them can be universal as long as you change the packaging from how it’s done on the OG EVO to whatever you’re device is.
For those interested in making some boot animation magic, you can find the full tutorial, suggestions, download links to the recommended software and discussion in the original thread. As per the norm, don’t forget to make a full backup of your device before you start testing, just in case something goes wrong!
January 26, 2012 By: orb3000
Not much ago we informed you about Sprint sending updates For HTC EVO 4G and EVO Design 4G which will remove the infamous Carrier IQ; well now it seems that not only Carrier IQ will be removed as the company included HTC EVO 4G and EVO View 4G on the most updated list of devices coming to End-Of-Life.
This means that both HTC devices are ending their days on the shelves. EVO 4G is expected to leave this week, and the EVO View 4G -Sprint´s version of HTC Flyer- will leave next week.
It´s amazing how carriers dictate when a device has become “old” even if it is not. Or perhaps the sales of those specific models are not going so well? -which I don´t think so-. Maybe it´s just another way to make space for the new upcoming line of devices that will pop out from MWC in just a few weeks.
Please tell us what you think and thanks for reading.
January 21, 2012 By: liwen
Last week, owners of the HTC EVO 3D began to receive an OTA update that, most notably, removed Carrier IQ. As Sprint has later confirmed, it is indeed looking to remove the tracking software from all its handsets, and has now begun to push out further updates for the HTC EVO 4G, EVO Design 4G and Samsung Epic 4G.
Besides removing Carrier IQ, the HTC devices are also getting updated Peep clients for Twitter and improvements to the battery life. For the Epic 4G there’s a speaker feedback fix, and some apps are no longer preinstalled, instead pointing to the Android Market. As usual with such updates, they are rolling out gradually. The HTC devices will receive automatic notifications starting on the 24th, or you can manually check right now, while the Epic’s update is being pushed in stages till the 29th, at which time all devices will have received the update.
For detailed changelogs, see Sprint’s support forums (1, 2, 3). To share your experience with the updates, visit the thread for the EVO or the thread for the Epic. If you like it rooted or deodexed for the EVO 4G, visit this thread.
With ROMs ranging from HTC Sense 1.0 to HTC Sense 3.5, from 2.1 Eclair to 2.3 Gingerbread, there isn’t much the original Evo hasn’t gotten. They’ve had CyanogenMod6 and CyanogenMod7 and there’s even some works for Ice Cream Sandwich and talk of CyanogenMod9.
However, there is one thing the HTC EVO 4G has never had before: Wimax on an MIUI port. That is, until now.
XDA Recognized Developer Sinistertensai, along with the very dreamy Team Nocturnal, has released an MIUI port that’s based on CyanogenMod7 (affectionately nicknamed CIUI…get it? CyanogenMod-IUI). It looks like MIUI and it feels like MIUI but it’s based on the legendary CM7 which, as Evo users already know, can get 4g Wimax. So, now, people who love the feel of MIUI can finally feel the love of 4g data.
Now, this is a brand new ROM. This means beta release which means there’s a few bugs, but we won’t hold against anyone because they’ll inevitably get fixed. Additionally, Sinistertensai has asked that any themers or developers who want help out with this super sexy ROM get a hold of him. The more the merrier, as the old saying goes.
If you’re looking to try out this highly optimized, super sexy, WiMAX-capable and MIUI-style ROM, then you can find a full feature list, installation instructions and download links in the original thread. For you MIUI fans on the OG Evo who’ve wanted WiMAX, you can now finally have it!
It’s rare when a ROM is so popular, the number of thread views are almost equal to the total number of members on XDA. As is the case with the original Warm ROM TwoPointTwo. One of the most popular of all time for those toting the HTC Evo 4g.
Now those who have migrated to the HTC Evo 3D, you can once again get a taste what is arguably XDA Recognized Developer (and all around good guy) Myn’s greatest work thanks to the work of fellow XDA Recognized Developer JoelZ9614 and the rest of Team Warm.
The sexy, lightly themed and totally awesome ROM has received a bunch of upgrades from it’s last public release on an Evo device beginning with going from Froyo 2.2 to Gingerbread 2.3 and including:
Added GPU UI Acceleration (instead of CPU) Added Additional Reboot options (Recovery, Bootloader, Hot Restart, Reboot) (NOTE: Hot Restart currently not working properly) Added DSP Manager (Thanks cyanogen) Added CRT TV shutdown animation Added HW Acceleration Tweak To Adreno_config Added SMS Backup/Restore Added Tweak to increase sdcard read ahead buffer (Thanks Misfit) Added 3D Home Screen (Toggable in Settings | Warm Tweaks) Added Native Screenshot Functionality (Press Home + Power at the same time) Added Zeus Mods [kinda] Quick Settings Changed WiFi Scan Interval To 180 seconds to further conserve battery Added Tweak to persist home app in memory Added various battery tweaks
So for those who want the good old feel and look of the original Warm ROM, you can head on over to the original thread for download links, installation instructions, a full change log and all the Warm goodness those from the HTC Evo 4g remember.