• 5,786,132
    REGISTERED
  • 52,034
    ONLINE NOW

Posts Tagged: HTC EVO 4g

AndroidFlasher

As we’ve stated in the past, one of the highlights of the Android OS is how it allows you to customize almost every aspect to your every whim. Often times, however, you wish to change more than the superficial by delving into the world of radio, bootloader, recovery, and splash screen modification. Assuming you have already achieved S-Off status on your device, XDA forum member danward brings us the perfect tool for your hacking needs.

Assuming you have USB debugging enabled and have the appropriate hboot drivers installed, Android Flasher allows you to flash these previously difficult-to-flash areas in just a couple of clicks. The Windows-based app currently works on the following HTC phones: Desire, Desire Z, Desire HD, EVO 4g, EVO 3D, Desire S, Incredible S, Thunderbolt, and Sensation. In the words of the developer:

This application flashes the specific parts of your device, ie. Bootloader, Recovery, Splash screen, and Radio.
It has taken many hours and much extensive research and testing on multiple devices to make a straightforward, efficient and reliable program to offer you the freedom in device customisation you are otherwise denied.
The app allows you to quickly customise your device in a way that is simple and alot goes on behind the scenes to guarantee you don’t get caught with error messages.
The splash screen is the image before the boot animation, (by default the white HTC logo.) With this application you can change it in under a minute.

If you’re interested in giving this a shot on your own device, make your way to the application thread. You’ll finally be able to (easily) get rid of that annoying HTC splash screen once and for all.

11x05101719

Ice Cream Sandwich ports are highly sought after, given the hype and price of the phone that runs it. However, providing there is support behind development, there is every chance you can run it on your device. This article is here to list the current ICS ports on our most popular  forums and their individual stages in progress. Should your device not be listed below, you can always visit your device’s development forum on XDA and search for any ROMs listed with “Ice Cream Sandwich”. Check out our list! READ ON »

Advertisment
wimaxdangerapp

I know that it has been a few weeks already, but we finally have green light to keep on going with our exclusive series of security holes on HTC’s latest devices. In case you just tuned in on the whole issue, we will be talking about vulnerabilities found on HTC handsets across the globe, particularly on the EVO family of devices as well as some of the newer ones like the HTC Sensation and Kingdom. XDA Recognized Developer TrevE has been doing a fantastic job in uncovering the holes one by one, and after much testing, he found some rather interesting results of things that could easily be obtained from your device(s) due to pieces of code inside of the manufacturer’s handsets that are exclusively in charge of collecting data and information about you, your usage, and many other things that you don’t want to see floating around on the internet. We are happy to report that HTC got their act together with the first vulnerability and got rid of the code responsible for the threat (htcloggers.apk).

As it was agreed between TrevE and HTC, our dev has been giving HTC head starts (5 working days) on virtually all issues before publicly disclosing them. Well, HTC has been making good use of their time for issue #2 as they are currently working towards a solution, but we will go ahead and let you know what this one is about. Those of you who enjoy the speeds of WiMax on their 4G enabled devices are doing so with an inherent risk. It turns out that WiMax is even more open than the HTC logger app. The more technical details are basically that an attacker who gains control over this can potentially manipulate data connectivity and to go even as far as being able to completely reprogram your device’s CDMA parameters remotely! This is done through two open ports that basically require no authentication and just as before, the only thing required for a malicious app to do anything is INTERNET permission. The other interesting thing that came out of this discovery is that apparently you can also send commands to the radio via the WiMaxmonitoring port, and sending a single coma can create an “out of bounds range exception” basically crashing your device. Here is a more detailed explanations of the whole thing:

——————————————————————————

Vulnerability: Android Security Elevation/Wimax Information Leak/Out of Bounds Crash
Products Affected: Any HTC device with wimax services running on ports 7773/7774/7775/7776
Vulnerability reported By: TrevE
——————————————————————————
Attached is a proof of concept showing manipulating wimax data connectivity.  Reading will only be demonstrated, but if someone was clever a few different attacks could be performed from stealing below information, to reprogramming with bogus/destructive values, possibly MITM data connections and more. WimaxMonitoring port also is able to crash the device if a comma is sent, it creates an index out of range exception.  The following services are able to be read and written by a malicious app with only permission INTERNETnetstat:
tcp        0      0 ::ffff:127.0.0.1:7775   :::*                    LISTEN      4327/system_server
tcp        0      0 127.0.0.1:7776          0.0.0.0:*               LISTEN      4230/wimaxDaemonsystem_server (port 7775) is a Wimax Monitoring socket. Not all commands are known at this time outside of:
getNaiDecoration
isDunMode
isReleaseKey/system/bin/wimaxDaemon (port 7776) Not all commands are known at this time outside of:
getMac
dumpMacTreeFromFlash
saveMacTreeToFlash
lockMacTree
unlockMacTree/system/bin/(get|set)WiMAXPropDaemon:
allows standard users read/write to root only file /data/wimax/wimax_properties used to manipulate wimax data connectivity (4g radio) by sending commands to TCP ports 7773/7774 with no authentication. Netstat:
tcp        0      0 127.0.0.1:7773          0.0.0.0:*               LISTEN      4210/setWiMAXPropDaemon
tcp        0      0 127.0.0.1:7774          0.0.0.0:*               LISTEN      4211/getWiMAXPropDaemon

File Accessed by method proving it should not be read from other than root or written at all:

-r–r—–    1 root     root       1048576 Oct  5 23:25 wimax_properties

Props able to be read/written:

persist.wimax.Cold_Boot_Flag 
persist.wimax.STANDBY_TIME 
persist.wimax.SCAN_RATE 
persist.wimax.Realm 
persist.wimax.CenterFrequency 
persist.wimax.Bandwidth 
persist.wimax.0.Man 
persist.wimax.0.Mod 
persist.wimax.0.FwV 
persist.wimax.0.HwV 
persist.wimax.0.SwV
persist.wimax.0.MAC 
persist.wimax.0.TO-FUMO-REF ./FUMO
persist.wimax.TO-WiMAX-REF ./WiMAXSupp
persist.wimax.IPv4 
persist.wimax.IPv6 
persist.wimax.ServerInitiated 
persist.wimax.CLInit.PollSuprt 
persist.wimax.CLInit.PollIntrvl
persist.wimax.WorkMode
persist.wimax.Session_Conti
persist.wimax.Scan_Timeout
persist.wimax.Scan_Retry
persist.wimax.Idle_Sleep
persist.wimax.Entry_RX 
persist.wimax.Entry_CINR
persist.wimax.Entry_Delay
persist.wimax.Exit_CINR
persist.wimax.Exit_Delay
persist.wimax.0.H-NSP-ID 
persist.wimax.OperatorName 
persist.wimax.PollingInterval 
persist.wimax.Primary.Name 
persist.wimax.Primary.Activated 
persist.wimax.0.METHOD-TYPE 
persist.wimax.0.VENDOR-ID 
persist.wimax.0.VENDOR-TYPE 
persist.wimax.0.USER-IDENTITY 
persist.wimax.0.PSEUDO-IDENTITY 
persist.wimax.0.PASSWORD 
persist.wimax.0.REALM 
persist.wimax.0.USE-PRIVACY 
persist.wimax.0.ENCAPS 
persist.wimax.0.VFY-SRVR-REALM 
persist.wimax.0.S-RLM.0.S-RLM 
persist.wimax.0.To-IP-REF ./IP  

 

 

 

 

Now, according to TrevE there are a few things that simply stand out as big “Why”‘s in here. Why is there a need for a WiMax monitoring port that can gather every single bit of information about your device and that can easily grant access to the device? This monitoring port also can check what you are running on your device (release keys) and finally it can check on the tethered state of the device. Secondly, and while this could be a simple coincidence, the timing from Sprint to limit the previously unlimited 4G seems a little odd. There could be a correlation between the existence of this reporting port to the usage of 4G in the network, which if TRUE, would mean that Sprint has been playing rather dirty all along, all that while putting our privacies at risk.

Well folks, there you have it. The holes in the different areas seem to have rather large implications if they are not taken care of soon enough. That being said, we have always been a proactive bunch when it comes to fixing broken code. Let’s get our heads together to ensure that HTC gets it done right the first time around, and as an added bonus for HTC, TrevE has been kind enough to provide a patch that completely eliminates this, which can be found here. Also, here is a description if you would rather apply this by hand:

To use edit init.shooter.rc to appear as below (or wherever binaries are started in ramdisk) and manually start them when you are going on 4g with attached app. 
———————-
service wimaxDaemon /system/bin/wimaxDaemon
   user root
   group root
    disabled
    oneshot

# setWMXPropd daemon
service setWMXPropd /system/bin/

setWiMAXPropDaemond
    user root
    group root
    disabled
    oneshot# getWMXPropd daemon
service getWMXPropd /system/bin/getWiMAXPropDaemond
    user root
    group root
    disabled
    oneshot

 

And remember, there are still more vulnerabilities to come, so please stay tuned for more.

You can find more information in the original thread ( http://forum.xda-developers.com/showthread.php?t=1322437) and here ( http://infectedrom.com/showthread.php/600-Vunerability-2-WiMax-Connectivity-Reprogramming)

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

Thanks TrevE for everything!

evoviewupdate102511

Earlier today, we saw that Sprint decided to hit the EVO family of devices with a much needed update for the security updates depicted in what we like to call PoC#1 (proof of concept #1), which was presented by XDA Recognized Developer TrevE. This security vulnerability basically allowed open access to sensitive device information thanks to a service built into the device of an apk called htclogger. As of the latest patch rolled out by HTC, this issue has finally been put to bed. It was confirmed that HTC has indeed removed said apk from the system thus effectively taking care of the original concern regarding consumer’s sensitive data being at stake. This was a good move by HTC and considering that the amount of bureaucracy and legal hoops that they must have gone through (let alone the amount of Quality Assurance and Final Testing by both HTC and the carriers), it was a remarkable thing that they were able to get a patch out in such a short period of time.

On the other hand, as with most processes that involve more than just one entity, there is always a bottleneck, something that will almost 100% guarantee that the update will not get to you at the same time as others. In this case, we have Sprint to blame for that and the reason is rather simple. Just think about the massive amount of data that needs to be moved and pushed to the millions of customers across their network, even if it is only 5 MB, as it was the case with the latest patch, when you multiply this by the number of users who will need this, the capacity of the network becomes a concern. They need to maintain service also for those millions of customers and if they were to push out the update to everyone all at once, you’d likely experience service interruptions. Sprint’s (and really most carrier’s) technique to avoid this is to push the OTA updates in waves.

Now that we laid down the groundwork for the point, lets cut right down to the chase. The roll-out to customers via OTA updates is a rather unnecessary step in this whole process. Why? I don’t know about you, but my EVO 3D is fitted with a wonderful tiny radio chip that allows me to connect via Wifi and I also have a quizillion other ways to get to the internet. See where I am going? What is the point of rolling something like this via OTA? I have personally followed HTC’s website for a very long time and as far as I can remember, they have always offered updates via direct downloads in their site. I understand that not everyone will know how to run a RUU or to even flash a zip as not every Android owner knows what he/she has in their hands, but allowing the end user to apply the patch directly from the manufacturer’s site would have the following impacts:

  • Much less strain on the network;
  • Reduced download times for consumers (although, due to this being such a small update, the speed is somewhat arguable);
  • Faster response time to an inherently bad problem;
  • You’d get to educate your customers as to what is going on rather than simply saying “here, install this… it is for your own good”;
  • You get to use your site a little more, which in turn will provide more exposure to your products as people may navigate to the products page to see what’s new.
Having to put this through a network certainly adds an extra step to the overall process. On top of that, the “waves” approach only ends up delaying the patch for everyone. You have got to keep one very important thing in mind, your customers know that you are the makers of the devices and not the carriers. When they see faulty code, it will likely fall on your lap and not on Sprint, T-Mobile, etc. Regardless of your contractual obligations with the other carriers, you should still offer the update as a direct download from your site. You will benefit from much reduced turn around times, which in turn will make people happy about the fact that you are responsive, which in turn will likely ensure that your current customers don’t jump ship to someone else, which in turn will turn said current customers into repeat buyers. The tl;dr (too long; didn’t read) version of what I just said? Fast support ensures continued sales. Remember this very important rule about manufacturing and sales… “you can always sell a box once, but if your support for that box is poor… that one box will be the last one you sell.”
All in all, kudos for the fast response, HTC :) We’ll see you on PoC#2! Hopefully, you will consider some of this.
Want something published in the Portal? Contact any News Writer.
Thanks GODZSON and joshman99 for the tip!
inducting

At this point in time, I guess it would be safe to assume that when someone asks us about warranty left on our devices, we cannot help but to either laugh or at the very least, smile. The reason for this is that we all know how to properly break it by flashing the device(s) that we have. But there are others out there who truly believe that improvements to a device can also be done in the hardware side of things. XDA member asmd6230 is such one individual as he posted a guide with instructions on how to make your device be able to charge via induction. Now, this is a concept that comes from the Palm Pixi and a few other devices of its kind. Basically, you will simply lay your device in the charging station and it just starts charging, Olin and simple. Also, you do not need to spend them money on a Power Mat or any such product. You will need the back cover and the charger of a Pixi and a few tools to do this yourself.

Please ensure that you understand what you are doing and that you are at least somewhat familiar with soldering to avoid royally messing up your phone. Have fun and happy modding.

I looked into it and found the the palm pre also had this and some chap on the net had figured out how to shoehorn the unit into an evo. 

You can find more information in the original thread.

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

android101

As you are probably aware, there are a large number of guides on how to do virtually everything on your devices. You can do anything by simply following written instructions and trying to understand what you are doing. However, due to the simplification of several tools, there are things and knowledge that gets lost due to this so called simplicity. In order not to let it die, XDA Recognized Developer lithid-cm has decided to take it upon himself to educate the masses on the hidden arts of Android development. For this purpose, he has decided to start his own Google + help sessions to teach and educate everyone who wants to join in. Moreover, he has already started a thread in the EVO section where he has already placed some pointers and basic information to get people started.

This is just a fantastic way to help our community grow together and we strongly encourage you to join in the fun if you have ever wanted to dev, but didn’t know how to get started. Please leave some feedback for the dev.

I am here for one simple reason. To teach people how to develop on android correctly. 

You can find more information in the original thread.

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

Runnymede Port For The EVO 4G

September 15, 2011   By:

hjgh (copy)

Looks like a good month to have an EVO 4G. Yesterday, we posted an article regarding a port of the latest Sense 3.5 rom to the Desire HD and the Desire S, which came from the unreleased HTC Runnymede. After having worked on the original build from XDA Recognized Developer capychimp, XDA Recognized Developer eVoKINGS has successfully ported this new build to the HTC EVO 4G. This build is by far a final one, but so far it seems that it comes loaded with a “real” version of Sense 3.5 and it also comes loaded with Android 2.3.5 as a rom base. Much like it was the case for the Bliss port that we spoke about last week, the current project (as it is less than 24 hours old), still has a lot of broken options such as wifi, inability to mount the SD card, broken wallpaper previews, no cameras, and last but not least rather low storage space right after flashing (some people have reported about 40 MB left without installing a single app). On top of that, if you were looking forward to the Quick Launcher widget from the Bliss build, it seems that you will not be getting that either or at least not until someone brings it into this build (currently being worked on).

If you don’t mind the aforementioned bugs and would like to test this, please help out the EVO community and leave good feedback on bugs, so that the devs working on this will have a better shot at making this fully usable.

This rom is based on Runnymede WWE ruu
0.82.401.1 android 2.3.5

You can find more information in the port thread.

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

flyer express

A little while back, we spoke about a rather interesting port for the EVO 4G, courtesy of XDA member the_plattypus. Well, while it seemed that the project was stalled for a while,the dev has been silently working on improving it and working out bugs and kinks. A few days ago, he posted that the rom was indeed getting better and that several things that people were longing for were finally fixed such as the ability to mirror your device onto a high definition screen/monitor through the device’s HDMI out. Other improvements include the newer Gingerbread 2.3.4 build being used as a base, and finally a smoother Rosie to play with.

The development will be put on hold momentarily due to technical difficulties with the dev’s computer in the form of his power supply being hit by lightning. He should be back shortly though. However, if you want to try it out and report back, it will certainly be useful to the dev.

Rebased on 2.3.4 – check
Faster more responsive Rosie and lockscreen -check
Camera fc not fc’ing – check
Hdmi mirroring – check
Camcorder recoding – in progress
Hidden Phone app – found

You can find more information in the port thread.

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

Thanks apheonixboy for the tip!

 

 

HTC Bliss Sense 3.5 For HTC Evo 4G

September 6, 2011   By:

ROMSep-02-2011RCMix3d-Bliss-v1.0-The-Original-android-2.3.4-incl.-sense3.5OC-xda-developers

It seems more and more devices are getting the latest version of Sense running. First, the port was completed for the Desire HD and Desire S,  and now thanks to XDA Recognized Developer eVoKINGS, Evo 4G owners can enjoy it too.

This is the first beta version and some bugs are expected. Please be patient and give the devs some time to work out the kinks. However, if you are itching to flash it and see what the new Bliss feels like, give it a go and leave some feedback behind.

Originally posted by eVoKINGS
[WIP][PROJECT] HTC Bliss Sense 3.5! (IT LIVES!!!)

Team Bliss so far:

OWNERS:
Myself,wdfowy, newtoroot, joelz9614, wildstang83, jermaine151,and Team Nocturnal

What’s this? Sense 3.5 on EVO 4g Supersonic
Thanks to JoelZ9614 for helping me to start this project!
Editing my ramdisk and pointing me in the right direction!

Thanks to WDFOWTY for asking me to take hold of this project
and for setting me up with svn!

Thanks to cappychimp for the first
initial port of the Bliss!

And thank you to all the other Developers
that are working on the Bliss, for other devices
and coming together to perfect this build!

Continue on to the original thread to find more information.

Enter God Mode

July 20, 2011   By:

quad

How would you like to have an incredibly fast rom, based on the latest of the latest for your EVO? Sure, you can find a few roms that will fit this description and many will indeed offer some speed improvements and enhancements, but in order to make your device truly fly, people fall back on overclocking the processor. As a result of this, most tasks performed by the device become a considerable percentage faster and more responsive. Well, XDA member Virus. has made a major improvement to his already popular Kingdom rom for the EVO 4G. The newer versions of this rom come pre-loaded with what he called God Mode. But wait, what is this God Mode? Leaving all the technical aspects aside (as they are not 100% clear to me), God Mode in essence is a new yaffs2+ext2 partition made in the rom, which drastically improves the I/O performance on a device. While I understand that people don’t exactly believe in benchmark results, the EVO 4G (which need I remind you has a 1 GHz Snapdragon on it) yields Quadrant results of well over 1900 without it being overclocked.

If you are interested in learning more about this, the dev has a full wiki page where he clearly explains everything. Moreover, you can find a link to a PowerPoint presentation for the original concept behind this mod.

in a nutshell we are setting up a yaffs2+ext2 partition. The concept I based this mod on was was originally presented by Hansung Chun written up here This combines yaffs for wear leveling ontop of ext2 for performance.

You can find more information in the rom thread and in the wiki.

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

SD Card Partitioning 101

July 13, 2011   By:

Android-SD-partitioning

The eternal quest to get the most out of our non expandable, very limited internal storage has been a paramount objective since the early days of mobile devices. We have, through the years, gone through solutions such as removal of bloatware, which is software bundled in our devices by manufacturers and carriers, compressing apps, having files online on systems such as dropbox or ftp, and much more. On Android, one rather big limitation was that you could originally not place apps on your external card. Thanks to app2sd scripts, this is no longer the case. In ordere to maximize the effect of these scripts, a good solution is always to partition your sd cards, but the how to do this on Android is not always common knowledge. To make this more available to others, XDA member Dredz decided to create a guide addressing this concern. The guide is straight forward, so you really cannot go wrong if you follow it correctly.

Please leave some feedback if you found this useful.

The main reason people partition is to take advantage of Apps2SD script. This allows for more internal memory and, depending on which version, control over various system settings

You can find more information in the guide thread.

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

4in1

We all like and enjoy the ability to reboot into diferent modes on our Android devices. It saves us from having to manipulate our devices in weird and strange ways as well as having to perform weird button combination presses. If you updated to the recent update to Gingerbread on the EVO and like the stock rom, you will likely be missing out on this great feature and the ease of a one click access to Recovery. Well, fear not because XDA member ca1ne has released a mod to add this functionality to your rooted and Sprint powered EVO. Needless to say, this is available in other custom roms, but if you are not into flashing a whole lot, then this should prove to be a good solution for you. The installation of the mod is relatively straight forward, but you do need to be rooted for this to work.

Please leave some feedback for the dev if this work well for your device.

This is a ported reboot mod for the new 4.24 OTA based roms.

You can find  more information in the fix thread.

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

Evo-wireless-n

Many of you are aware of the fact that Sprint, in all of their infinite wisdom decided to cut 802.11 n support from the EVO 4G when they released the latest update for the device (4.24.xxx.x). As weird as that move sounds, it is quite an annoying one, particularly if you stay with the stock version of this update or if you go to one of the various custom roms that still have this disabled. If you find yourself missing out on much higher data speeds on your N network, then check out what XDA member MultiDev has come up with. The dev found that the driver for this needed to be replaced for it to support N, so he took it upon himself and released a guide on how to get this functionality back on the EVO 4G. The dev gives two possible ways of getting this done, one of which involves adb and a few commands, while the other is simply flashing a zip file via recovery. Several members have tried this already and it seems to work well with some members reporting the longer range as well as increased speeds, typical on N networks.

Please try it out and leave some feedback for the dev.

As many of you know, wireless N support was removed in all the GB updates for the Evo (both the 4.22 and 4.24 stock ROMs lack Wireless N support)

You can find more information in the original thread.

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

Advertisement

XDA TV: Most Recent Video

Buy/Sell on Swappa

  • Nexus 5 (Unlocked) buy | sell
  • Galaxy Note 3 (T-Mobile) buy | sell
  • HTC One M7 (Verizon) buy | sell
  • Galaxy S 5 (Unlocked) buy | sell
  • Nexus 7 2013 buy | sell
  • Swappa is the official marketplace of XDA