• 5,604,208
    REGISTERED
  • 49,770
    ONLINE NOW

Posts Tagged: HTC Amaze 4g

Hasoon2000 toolkit

Tool kits are often one of the most useful things a user will ever download. They usually let users efficiently perform a variety of tasks including acquiring root, installing a custom recovery, and flashing various development work ranging from ROMs to kernels. In other words, it lowers the entry cost for new users, and allows even the more experienced users to enjoy easy flashing.

Now, thanks to XDA Recognized Developer hasoon2000, there are a variety of tool kits for many HTC devices. Currently supported devices include the HTC myTouch 4G Slide, HTC One S, HTC One X, HTC Amaze 4G, HTC Rezound, and the HTC Vivid.

For some users, this tool kit is not exactly a new experience. This is the tool was recently used in the post-update root tutorial for the HTC Sensation. However, it’s worth mentioning all of the great things this tool does for devices. In the case of the One X, the features include:

- Get Token ID
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
Interim Custom CWM
DoomRecovery Custom CWM
CWM 5.8.0.9 (Touch)
Stock
-Flash Kernels provided
Stock
- Link to this thread (Android-Dev / XDA)
- Link to PM me if you need a phone unlocked (Android-Dev / XDA)
- Link to the One X Development thread (Android-Dev / XDA)
- Boot Into Recovery
- Boot into Bootloader
- Relock Bootloader (must be in fastboot)
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!

In terms of tool kits, this does pretty much everything you’d expect, plus a whole bunch of other stuff as well, such as linking back to the device’s respective XDA-Developers forum. Users looking to get in on the tool kit action should proceed to their appropriate thread:

11-T-Mobile-HTC-Amaze-4G

Logic would dictate that our devices should survive thanks to their creators, and their continued existence would depend solely on their willingness to prolong it. If the aforementioned statement was in fact true, the creators (in this case the manufacturers) would release updates in a more timely manner. However, as we have seen time and time again, this is hardly ever the case, be it for quality assurance practices, carriers blocking the updates, etc.

Whatever the reason may be, we often find ourselves with devices that unfortunately do not make the manufacturers’ cut. That is, unless some brave soul would dare to go straight into the giant’s castle to retrieve this golden egg. The fairy tale also known as the tale of leaks is best told by no other than our favorite leaker, XDA Forum Member Football. His latest accomplishment in the giant’s castle was to provide Amaze owners with the update that never came (and would eventually come): Android 4.0 Ice Cream Sandwich.

Why do we make such a big deal out of something like this? The kernel that is present on this ROM is full ICS, which means that if a dev were to include this in a ROM, it would likely fix several outstanding issues such as broken camera, Bluetooth, and many more. Now, a few of the members who have already flashed this have been kind enough to provide step-by-step procedures on how to flash this ROM, as it seems that there are different methods depending on the status of the bootloader (S-ON or S-OFF). So, depending on what state your HBOOT is in, you will need to follow one set of instructions or the other. In case you just got your Amaze and you are really not sure, you can simply connect your device to a computer via USB and (assuming that adb is present in your computer and that you have USB debugging active on the device itself), type “adb reboot bootloader” in a command prompt (no quotation marks).

Well, what are you waiting for? If you were itching for a fully functional ROM for your Amaze, now is your chance. Please leave some feedback regarding your experience with it.

Here official ICS Update for Ruby

You can find more information in the original thread.

Want something published in the thread? Contact any News Writer.

[Thanks to charlatan01 for the tip!]

Advertisment
SuperCID

With the recent and not-so-tragic death of S-On for many HTC Devices, quite a bit of development has been underway for the newly freed devices. In essence, they seem to have gotten a development second wind, such as the recent ENG HBoot for the Rezound. Basically, there are now more devices having more development fun. Because of this, the HTC Amaze 4G and the HTC Rezound have SuperCID.

XDA Senior Member electronicrice and XDA Forum Member jefffeely have posted methods to get SuperCID on the Amaze and Rezound, respectively. What are the benefits of this? Well, electornicrice outlines one of the major benefits:

Basically, having SuperCID allows you to flash any ROM, regardless of which carrier it is for. Pretty handy if you have your phone SIM unlocked and wanted to use your Amaze on Wind Mobile or something.

The process itself only requires users to have access to Fastboot commands on their computers. From there, it’s a few terminal commands, and before you know it, you can flash pretty much anything you want. There’s also a process that will help you revert back to whichever CID you need.

Additionally, for HTC Amaze 4G users, XDA Senior Member benjamminzIS has created two automated scripts to do this for you, if you don’t feel comfortable enough with ADB to do it yourself. One gives you SuperCID, and the other reverts you to the stock T-Mobile CID. While Rezound owners are “stuck” with the manual entry method for now, it’s really not that difficult.

For more information, download links, discussions and more, hit up the HTC Amaze 4G thread or the HTC Rezound thread.

Amaze4G_SOFF

HTC’s locking of the bootloaders during last year was nothing short of a spectacular feat. It was really a battle of the titans, where the original line-up of Sensation-like devices came with a locked bootloader, which was later unlocked and S-OFFed, only to be updated to yet another revision of the HBOOT. But the second time around, it was locked to an almost unlockable state. Having heard many complaints from the user base (and us), HTC decided to offer the olive branch and simply gave up on locking the HBOOT. In fact, they themselves provided a way to unlock this and allow the flashing of custom code on the devices (of course, your warranty flew out the window if you did). Several giants came along such as Revolutionary, but now the next step in the evolution of S-OFF has arrived, and its name is Juopunutbear, and it has been delivered by XDA Forum Members Fuses and globatron.

Details on the unlock process are somewhat scarce (and quite frankly, that is indeed a good thing), but it seems to be that the devs found some sort of exploit common on most dev unlocked devices. The process seems to include what the devs have called a “wire trick”, which according to the pictures involves placing the device in download mode by touching a contact in the device’s board with one end of a wire (accessible without having to take it apart) and the other end of the wire to the device’s sd card slot metal casing. Everything else is done by the software, but your timing in doing everything must the right or else it will not work. Also, since the devices are somewhat different from each other, the devs have added a set of instructions, with video demonstrations, for each one of them.

The program has been extensively beta tested by a closed yet somewhat large group of people. However, as it is customary, the devs do state that the process is not perfect and that there is the likelihood that the devices could be bricked in the process. Having said that, proceed with extreme care and ensure that the device that you are going to S-OFF is in fact the one for which you are following instructions on.

The main unlock webpage can be found here. However, there are threads in each individual device section, such as this one for the Amaze 4G.

Want something published in the Portal? Contact any News Writer.

lockscreen

We’ve said it before, and we’ll say it again: touch-based recoveries are the future. Aside from giving end users easier access to device firmware modification, they add a much needed element of polish to the Android hacking experience. While some may say that these upgrade recoveries take away from the feelings of thrill and excitement, I argue that they offer a more efficient interface and enable some truly unique new features not available in the recoveries of yesteryear.

In a rather large update to what is arguably the most popular touch-based recovery around, XDA Recognized Developer Dees_Troy presents to us Team Win Recovery Project (TWRP, for short) version 2.1. Aside from simply bringing a friendly UI, TWRP 2.1 packs a healthy feature punch by offering zip queuing, a basic file manager, and dual storage support for backups.

TWRP supports scripting via a new scripting engine called OpenRecoveryScript for use with GooManager. With ORS, users can install multiple update.zip files from within Android, wipe cache & dalvik, and run a backup. Furthermore, in the name of openness, Team Win has submitted ORS as a commit to ClockworkMod.

In the words of the developer:

Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

New features for version 2 of the recovery software:

Zip queuing as seen in TWRP 1.1.x is back
Dual storage capable (backup, restore, and install zips from internal or external storage – you choose)
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added – Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme – makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI – makes all builds about 100KB smaller

If you’re itching to get started, please visit the development threads listed below. If instead you are looking to theme the recovery, visit their theming guide.

NFC

AT&T Samsung Galaxy Note users might want to have a look at this. With all the interesting stuff going on with NFC (Near Field Communication), from using Google Wallet to make real-life purchases with your phone to contact sharing and even initializing multiplayer games, it’d be a shame to have a NFC chip in your device and not be able to use it. Some of the more notable devices that have the NFC chip include the Samsung Galaxy S II, the Motorola Droid RAZR, and the HTC Amaze 4G.

The Korean version of the Galaxy Note has an activated NFC chip. Now, thanks to XDA Forum Member fox689, AT&T Note users can enable the NFC chip on their own devices. From the original thread:

 This flash contains an xml permissions file and the Tag.apk from the Canadian ROMs.

Once you’ve flashed this you will have the option to turn on NFC in Wireless Settings as well as be able to install NFC apps from the Play Market.

If you’d like to give it a shot on your Note, check the original thread for download links and install directions. You will have to flash this mod through recovery, so be sure to make a full backup of your device and read all instructions before you jump in.

Lock Ring

Despite how many consider HTC Sense 3.0 and 3.5 as being very bloated, there is at least one place where HTC hit a home run–the lock screen. The customizable Sense lock ring is, far and wide, one of the most popular and functional lock screens. Of course, for rooted users it only gets better, as they can actually modify the lock ring to make it look how they want.

XDA Senior Member mohit1234 has written up a tutorial on how to theme lock rings for HTC Sense 3.0 and 3.5 that outlines the correct file size and the exact steps to take if you happen to own Photoshop. Additionally, the guide author also takes requests for lock rings, and the collection is already pretty extensive. While there are other guide threads available to accomplish the same, this one is among the most detailed and universal out there.

Despite being written for the HTC Amaze 4G, most of the steps can be used with other Sense 3.0 and 3.5 devices, as long as users take note of the appropriate PNG size for their display resolution, and modify the way it gets packaged. There are a few drawbacks, however. Mohit1234 does’t quite explain how to package the lock rings into a flashable update.zip, although we have covered update.zip creators in the past. Furthermore, users have to modify the individual APK of any Sense 3.0 or 3.5 skin they’re using to apply their lock ring.

For additional information, screen shots of the many lock rings already created, and additional tips and tricks, visit the modification thread.

blog.htc

The billion dollar question right now in the Android world is whether or not your device will receive Android 4.0 Ice Cream Sandwich. As they so humorously put it:

Few innovations have improved upon ice cream as much putting it between two cookies and making a sandwich. Which is why we all want Ice Cream Sandwich! Ok, that’s not the real reason, but we’re all excited about Android 4.0, Ice Cream Sandwich, coming to HTC.

While there is constant speculation as to which devices will be added to the ICS list, not very many firm answers are to be found. Luckily, HTC has just released a public statement as to which devices are slated to receive Google’s latest tasty treat.

Timing is the next important question. HTC has spoken up on this issue as well, stating that the updates for the Sensation and Sensation XE would begin in the coming weeks, with the Sensation 4G andSensation following thereafter. However, the schedule still remains unclear for the other devices slated to receive the OS update.

As for timing, we’re in the early stages of rolling out Android 4.0 for the HTC Sensation and HTC Sensation XE and upgrades will be more widely available in the next few weeks. The update for the HTC Sensation 4G and HTC Sensation XL will follow. Please note, once we start pushing out updates it will take time for all carriers in each country to get the update. We are working closely with our carrier partners to nail down update schedules for our other smartphones and will have more to share very soon.

While many of us are still irked at the fact that HTC’s first generation Snapdragon devices such as the original HTC Incredible and the legendary Evo 4G are not on the update list, their omission is understandable given that not even the HTC-built Google Nexus One is receiving ICS in official capacity. However, the fact that these devices will be receiving Sense 3.6 rather than Sense 4 is a bit of a bigger blow. However, you can bet that our developer community will have that covered, as they have already begun to do so.

Source: HTC Blog

[Thanks to all who sent in the tip!]

htc amaze 4g

When the HTC Amaze 4G was first released, there was much furor over its light leak issue. For those who don’t now what light leak is, it’s when the lights from the touch buttons leak onto the actual screen of a device. While it isn’t harmful to the device and doesn’t cause any decrease in functionality, it is incredibly annoying.

XDA Senior Member jul644 has posted a modification that will turn down the intensity of the touch buttons so the light doesn’t leak onto the touch screen. This not only fixes the problem, but it might even save you a few minutes of battery life.

The modification requires some knowledge of .apk compiling and decompiling, apk and xml editing, and some elementary usage of ADB, so for those who aren’t as tech savvy, you might need to do some homework before attempting. This could be very useful for developers to add to their ROM or for people who are brave enough to attempt. As usual, be sure to create a backup for any apk you intend to modify, just in case something goes wrong.

For those who are willing to attempt, or for developers who want to add to their ROMs, you can find the full modifications and prerequisites in the original thread.

Advertisement

XDA TV: Most Recent Video

Buy/Sell on Swappa