- 4,430,935
REGISTERED - 29,966
ONLINE NOW
April 18, 2012 By: PoorCollegeGuy
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
QPST http://conflipper.com/Software/QPST_2.7_366.rar
Page Plus PRL’s (See below)
APN Backup and Restore
Page Plus APN’s
MSL Reader
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: PoorCollegeGuy
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.
Source
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.
January 5, 2012 By: PoorCollegeGuy
For those who are still holding on to their HTC EVO 4G phones, among the most developed and popular phones of all time on XDA, you are in for a treat.
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!
January 2, 2012 By: PoorCollegeGuy
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.
December 6, 2011 By: Will Verduzco
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.
November 28, 2011 By: Sam Caplat
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 »
October 27, 2011 By: egzthunder1
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!
October 26, 2011 By: egzthunder1
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:
We’ll see you on PoC#2! Hopefully, you will consider some of this.September 27, 2011 By: egzthunder1
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.
September 23, 2011 By: egzthunder1
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.
September 15, 2011 By: egzthunder1
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.
YouTube
Follow
Like
Google+
