• 5,732,540
    REGISTERED
  • 49,554
    ONLINE NOW

Posts Tagged: HTC EVO 3D

htc evo 3d

It’s not Ice Cream Sandwich yet, but this new OTA update for the HTC EVO 3D should still bring some very nice improvements. Very nice, indeed.

Sprint’s official changelog doesn’t reveal much, except for the software version 2.17.651.5 and a generic “security update” bullet point. However, at least according to preliminary reports in our forums, Carrier IQ has been removed, which should be a very good reason for everyone to perform this update. Apart from that, there’s also a new kernel that’s said to improve battery life, and the new Android Market included.

The catch? It’s not rooted yet, so you may want to (or have to, if you’re perm-rooted) hold out for a bit. But then, automatic notifications for this update will only start on January 17 anway, so if you want to get it earlier you’d have to manually check by going to Settings > System updates > HTC software update > Check now.

Head over to the forum thread to join the discussion.

W3Devs-wmz-beats

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.

Advertisment
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 »

SVN

Flashing, upgrading, and more flashing. This is what most people at xda do to try and keep up with the times. This is almost a full time job/hobby for some people and sometimes, not even the devs can put out roms fast enough. Because of this, there are ways to provide junkies or ORD addicts with a faster fix. SVN, which really stands for subversion is a command that allows updates of software giving you the opportunity to easily roll back and update without any major difficulties. Basically, using SVN would allow anyone to update the builds directly from the developer’s repo. The advantage of this is that you will not have to download a full new build every time as this will allow you to simply update the builds every time with whatever changes the dev may have made from the previous one. This works great for people who release nighties. If you are curious as to how this is done, XDA Recognized Developer LiquidSolstice has put out a fantastic guide, which is in essence fool proof to get this up and running in no time. The guide is complete with explanations, examples, links to files and programs, and even a full list of repos from devs present in the EVO 3D area. However, this is universal enough to be used with any dev that works with a SVN server.

Intrigued? Please be sure to stop by the tutorial and make sure that you read the whole thing as you can end up flashing a bad zip if you don’t.

As promised, I’m posting this graphical guide up for those who wish to use SVN in order to obtain nightly builds of ROMs and all other items that utilize SVN for distribution.

You can find more information in the guide thread.

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

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!

Add Beats To Any Sense Rom

October 19, 2011   By:

beats-by_dr_dre-04

You have likely been hearing about the new Beats Audio technology that was implemented on the Sensation XE last month. This is essentially a sound enhancer app that makes using headphones a bliss (especially if they are Beats by Dr Dre). A few select roms on various devices have had this ported to them by their respective chefs, like this one. But, what if the particular rom that has it is not exactly your cup of tea? Fear no more because XDA member smokin1337 has just released a flashable version of this, which can be applied to any Sense 3.0 rom. Keep in mind that this has bits and pieces of framework and services.jar, so you can expect some odd behavior of a few things. For instance, the CRT animation seems to stop working after applying this. Not a major downer but something to consider.

The dev also recommends making a NANDROID backup, just in case. Please take this for a spin and make sure that you leave feedback behind if you thought this was useful or if it didn’t work right.

I personally didn’t think beats was all that great but alot of users like it so i made this flashable version for my rom.

You can find more information in the original thread.

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

3vo eternity

More than certainly, a lot of work goes into roms in this place, particularly when they are ports. You may remember a few days ago Sensation XE Roma loaded with Beats Audio started surfacing across several devices like the HD2 and a few others. Well, it finally came the time for the Evo 3D to join the exclusive XE club, all thanks to XDA Recognized Developer Virus. This port has a lot of man hours put into it as the Beats part was ported from scratch, which meant tons of editing by the dev to ensure that the final product was just right. The rom is also loaded with tons of other goodies which are certainly worth checking out if you happen to have an EVO 3D.

Please test this one out and leave some feedback for the dev, in case you come across any bug.

THE FIRST 3d rom to have FULL BEATS AUDIO from the Sensation XE!!

You can find more information in the rom thread.

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

Thanks Virus for the tip!

HTC Responds Once Again…

September 13, 2011   By:

privacy

A couple of weeks ago, you may remember that we posted an official response stemming directly from HTC regarding privacy and security of data (link to previous article). Not being entirely happy with the response, XDA Recognized Developer TrevE decided to take it upon himself to dig out some more stuff regarding the apps and pieces of code that were actually doing all the collection. He came up with a rather nice list of apps, most of which he has been working on constantly to try and decipher their true purpose. Well, to make a long story short, this information got to the desks of the good people at HTC and they decided to try and generate a response to these new concerns. Without further ado, HTC’s official response:

The most important of HTC’s core goals is to provide consumers with the best possible experience on their devices. We live by the principle that our best work is never good enough, and we continually strive to learn more about how to delight the customers that use HTC devices.

 

One of the most effective and statistically accurate ways for us to learn how to improve is through the depersonalized and permission-based collection of error and usage data from consumers’ phones. Each member of the HTC community who is willing to contribute this data in a depersonalized mannerhelps all members of the HTC community enjoy a better experience. 

 

HTC values our customers’ privacy and ability to make informed choices about data collection and sharing. For HTC’s own software, our policy is to provide notice and choice and to ensure that anypersonal information collected is appropriately protected. The protection of this data is our obligation and we take the trust you put in us to learn from that data very seriously.

 

HTC Software:

Tell HTC is an optional feature that people can choose to activate or not.  If you choose to activate Tell HTC and help us improve the products and services that you and other members of the HTC community use, we collect depersonalized error and usage data from the device and use the data to improve HTC products and services. Some of these improvements may be delivered to your device in the form of a software update and others will be delivered in future HTC products and services.  We do not share or collect any content of communications or any personally identifying information such as names, phone numbers, or e-mail addresses of customers or their friends and contacts using Tell HTC.   

 

If you choose not to participate in Tell HTC, we will not store error or usage data on the device and will not send data to Tell HTC servers.  Tell HTC can be enabled or disabled at any time in the Settings Menu, under “About Phone”à“Tell HTC”. 

 

HTC App Usage Statistics is a service on the device that powers the “Frequent Apps” feature, which is reached by tapping the checkerboard in the lower left-hand corner of the home screen. This service shares data with the Tell HTC service on the device.  However Tell HTC will not store or report the data if the user has chosen not to participate in Tell HTC.

 

HTC Check-in periodically contacts HTC FOTA (Firmware-Over-The-Air) services to check if new software is available. This service is set to “Automatic” by default, but can be changed to “Manual” by the user in the Settings Menu. When “Checking In” with the HTC FOTA Servers, HTC Check-in will send the device serial number (IMEI) and current software version.  This is needed to determine if the specific device has new software available.  This service is not connected to Tell HTC.

 

Third-Party Software:

It is also important to note that the phones we build are a compilation of not only software and services from HTC, but also from third parties. These third-party applications and services, such as Carrier IQ (CIQ) and Google Check-in, serve to further improve the customer experience and have their own privacy policies. We encourage consumers to understand the specific policies of any application or service that is enabled on their device.

It certainly looks like after the locked bootloader incident, HTC has decided to take a turn for the better and try to cooperate with developers a lot more, which is why you are seeing a lot more public appearances from them than ever before. Please keep in mind that this is a massive, multinational corporation with tons of legal blocks, trade secrets, etc. So, probably expecting a direct response from them, directly addressing code concerns may not be as viable as some people would think. Despite all this, they were able to provide a little bit of insight onto the first 3 services, which is a start in my opinion. If you read carefully the last paragraph of their response, you will notice something that we have covered before here in the Portal. There seem to be things in the code that are mandated by the carriers themselves and as such, HTC (or any manufacturer) may have little to no power to opt out of them.

Well, whether it is or not the exact answer that we were expecting, I would personally like to thank HTC for looking into our community and paying attention to their customer’s concerns. We certainly look forward to a more robust and technical response regarding the things that they do have control on.

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

htc-logo

You may recall a few days ago, we published an article about a HTC service present in the new OTA for the EVO 3D, which basically collected information regarding usage, location, and certain information about your device. Well, to all of you who believe that HTC is oblivious to our work here at XDA, well, they are not. They are very much aware of who we are and what we do, and believe it or not, are actually thankful to us despite everything that has transpired over the last few years.

Officials from HTC have replied to the concern regarding data and privacy security and has assured us that all the information that they obtain is nothing more than information for their “Tell HTC Customer Service App” and that all the data being sent is securely encrypted.

We’ve seen some questions about Sensation and Evo 3D and want to provide more information. HTC, like most manufacturers, has an opt-in error reporting function built in to our devices. If your phone experiences an error, you have the option of “Telling HTC” so we can make improvements to our phones. Details about this are in our privacy policy on each device and in order for data to be collected, you have to opt-in. If you do opt-in, we protect your privacy by de-identifing and encrypting the data.   

HTC is committed to protecting your privacy and that means a commitment to clear opt-in/opt-out as the standard for collecting any information we need to serve you better.”

HTC is indeed making leaps and bounds in attempts to get us back on their side, and by listening to customer demands and concerns, more specifically ours, we can see a paradigm shift in the way their business structure is moving. Sure, they may have released incomplete sources for kernels and shipped out locked devices, but they are working towards accommodating the needs and wants of their biggest customer base…. us. Changes will not occur from one day to the next, but the shift in direction and reaching out to the community like this is certainly a good indication that they are indeed aware of the problems and attempting to fix their past mistakes as well.  Thank you for listening, HTC.

Please leave your comments below.

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

htc-evo-3d

There has been a lot of hype over the last few months about privacy, security, tracking of data and GPS coordinates, etc. One would think that after all this mess, companies would be a bit more transparent as to why they collect the kind of information that they do. However, it seems that it is still believed that information is a powerful thing to have, so companies keep on collecting it. According to a message that was sent to us by XDA member TrevE, there is something in the Gingerbread 2.3.4 OTA for the Sensation called User Behavior Logging, which has the ability to record virtually every single action on your device. You can expect it to record things like: apps you install and open, amount of time on each app, virtually every intent you open up, and location information in what seems to be hex format, among a few other things. All this data is then sent to an Amazon cloud storage IP. TrevE goes on to tell us that this CIQ app itself is not new, but the stuff located in the framework and the kind of data that it puts out is different from before.

Luckily for all of you EVO 3D owners out there, the dev has successfully removed this app from the framework, so if you are concerned about your privacy, I’d strongly suggest that you take a quick look at what the dev has to offer.

The new OTA update from HTC on the evo3d in 2.3.4 included CIQ app and stuff in framework called User Behavior Logging.

You can find more information on how to remove it in this post. And if you are interested about the information being sent, you can see it here.

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

Thanks TrevE for the information!

htc-quietly-brilliant-logo1-450x300

It’s been too long, really. We all wanted this to be released a long time ago, but with HTC being HTC, it wasn’t. If you follow developments from HTC, you’ll know that they recently announced that they’ll be unlocking the bootloaders on the Sensation and EVO 3D, about months later than potentially helpful. They also recently released the kernel source code for the Incredible 2, but it would have helped for it to actually, you know, work.

At 11 AM EST, HTC made another announcement on their Twitter page stating, “Check out HTCdev.com. New SDKs, kernel source code, and the future home for our bootloader unlocking solution.”

What have we learned from this tweet? They have a new domain called HTCdev.com, on which features the new release of their OpenSense SDK, along with kernel source codes for their devices. Fantastic development, don’t you think?  Unfortunately, this is not the case.

Shortly after this announcement, our own XDA Recognized Developer supercurio tweeted asking @TeamAndIRC, “Tell me if you manage to compile #Sensation kernel from sources, fails here with msm8660_defconfig.” What have we gathered from tweet? It’s not working properly. HTC made a boo-boo.

Don’t get me wrong here, I’m happy that HTC finally pulled through and released something they said they would, especially something as fantastic as an SDK for Sense. It’s good they’re trying to get stuff right, but here’s my biggest gripe:  They’re not trying hard enough. Azrienoch says, “It’s like a billion-dollar circus, and free to watch.” He’s right. It’s surprising that a billion-dollar company can mess up this much and still be praised by those who revel in its developments as a breakthrough.

Despite these issues, I do wish HTC the best in resolving and overcoming them.  Many developers on XDA-Developers look forward to working with your SDK and kernel source code to develop unique and creative content.

htc-sensation-aluminio

XDA member kaintfm let us know some great news for all HTC lovers with newer devices out there. According to HTC´s Facebook page, the Bootloader Unlock tool will be web-based, require a valid email address, a device-specific token, and it will require your consent to void parts of the warranty. After all is said and done, you will be given a code which will unlock the phone’s bootloader permanently.

The first unlocker will be for the global HTC Sensation, followed by the HTC Sensation on T-Mobile, and finally the HTC EVO 3D on Sprint. A software update will take place before the web unlock tool goes live to prepare the devices for the unlocking process.
Phones will continue selling with their bootloaders locked for the indefinite future because of security and warranty concerns. Keep in mind that there is still no set date for the official release, so keep an eye out for more.

Originally posted by kaintfm
HTC Offering Web Bootloader Unlock!

Finally! A way to make the voided warranty and bootloader unlocking official. This way HTC can allow their phones to be unlocked without opening themselves up to the hordes of people bringing in their bricked phones for warranty work.

Continue on to the discussion thread.
Read more on HTC´s Facebook page.

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