Related
GOOD NEWS EVERYONE! WE'VE GOT A DELIVERY
Hello,
First of all, some good news to everybody in Turkey who has been afflicted by the IMEI problem. We have produced a working solution and intend to make it available to the Turkish public for FREE, as promised.
The procedure was tested on my i-mate k-jam which I unlocked successfully. I cannot express the sheer joy when my phone picked up the signal and remained connected! It worked!!!
Alas, my own overconfidence in this victory that came after a lot of hard work and research, resulted in me baking my i-mate's ROM during an attempted ROM upgrade. So I cannot enjoy my phone right now, however, this was not caused by our IMEI update process, which works fine. I just damaged my DOC while being careless with the latest "Self-Cooked" ROM, a most cavalier act indeed.
Now, this whole IMEI issue has drawn a lot of heat on the forums. I have been personally accused of being a thief, a hacker, among other things. I only have good intentions in mind, but I also want to consult with everybody in this forum, to put my ideas to the test of the real world (especially Richard's vicious criticism will at least provide a reality check as to the feasibility of our ideas).
Project goals:
1) Mechanism should only work in Turkey
2) Mechanism should only work once for each person
3) Mechanism should be free
4) Mechanism should be easy to use
Proposal for implementation:
1) To realize a Turkey-lock, we'll impose an IP address restriction. No IP outside of Turkey will ever work.
2) To realize the person-lock, we'll prevent the unlock wizard from running more than once on any given piece of hardware. We will also ban the tool from running on VMware/Virtual PC systems, to make sure people cannot side-step our hardware lock.
3) Free - that's easy! We just won't charge for it.
4) Easy to use - that can be harder, but we'll give it our best.
Please let us have your thoughts...and thanks to everybody who contributed to this project.
We'd like to make the product as solid as possible, so the restrictions cannot be circumvented, and this won't become a tool that the real thieves can use to unlock their phones. Any technical implementation suggestions on getting this done, including making our product binaries harder to hack, and making it harder to sidestep our limitations, are VERY welcome.
Don't worry - we won't force you to use a dongle! But we'll still do everything in our power to guarantee fair use of the tool, once per person.
Good work mimarsinan. We'll chat later... just reinstalled Comprexx Time for bed now
V
Hope CXX took in the serial now!
Re: Proposed Solution for IMEI Problem in Turkey (Good News!
mimarsinan said:
The procedure was tested on my i-mate k-jam which I unlocked successfully. I cannot express the sheer joy when my phone picked up the signal and remained connected! It worked!!!
.
Click to expand...
Click to collapse
and why is necessary to unock the phone when user want to change the imei?
Re: Proposed Solution for IMEI Problem in Turkey (Good News!
decided to remove my post
I had to CID unlock the phone before our IMEI method would work. The method is not limited to Universal, but works on a wide variety of HTC phones, including Wizard which was my model.
It is really a shame nobody had a public tool that did this before. And Raskal, in all fairness, if you had made it easy for me to find a solution, I wouldn't have bothered to setup this project, work on it for a week, and finally manually unlock my phone.
I now have to keep my promise to the community and make the tool available for free as promised.
mimarsinan said:
I had to CID unlock the phone before our IMEI method would work. The method is not limited to Universal, but works on a wide variety of HTC phones, including Wizard which was my model.
It is really a shame nobody had a public tool that did this before. And Raskal, in all fairness, if you had made it easy for me to find a solution, I wouldn't have bothered to setup this project, work on it for a week, and finally manually unlock my phone.
I now have to keep my promise to the community and make the tool available for free as promised.
Click to expand...
Click to collapse
you have not made solution becuase you simply not have the background to do such tools. it is from mamaich, he is good in this what he do, you are just an "ibne", nothing more or less...
Guys. please be respectful to each other.
You can argue about technical solutions, but I'm not going to be your mother and spank you for being naughty.
Treat each other with the same respect you would like to be treated, and then we'll all be happy.
Hi Raskal,
I understand you feel angry and threatened that soon a free tool will be launched which does the same thing your commercial tool does.
While some people in Turkey would take great offence to being called "gay" (ibne means ****** in Turkish for those who do not know), I am very comfortable with my heterosexual sexual identity, and I have no problems with homosexuals, be they gays or lesbians. Of course, it hurts if some girl I have a crush on turns out to be a lesbian, but such is life :lol:
I have done nothing to offend you, other than complain about the difficulties of your fulfillment process, which drove me to implement this project in the first place. If you had had a better fulfillment process, this would never have happened.
Yes, I most certainly do not have the background to implement this project, but I have been helped by people (I don't think mamaich - unless he uses a different nick on other forums I have visited). I most certainly could not have done this alone. I am grateful for the help and support I have received from people during this project.
The sole intent of this project has been to solve a problem, I have stated from the beginning it is a non-commercial venture. I am getting PMs from people on the forums asking for help - these people need help, the same way I needed help. I have been called a hacker, a thief, a government agent under cover, and now gay, for this effort. Sorry, but by now I would have thought that you'd have already figured out these defamations and assaults do not deter me, but instead increase my motivation to get the job done faster.
I wish there was some way I could make peace with you and Richard, but you guys seem truly hell bent on doing everything in your power to stop me, well, what do you want me to do?
Am I going to be nice to the two people who have been unfriendly at best and outright hostile and rude in every sense of the word, and cease this project? Or am I going to honor the request of all those people who have kindly asked me for help with this situation?
You have a commercial tool and you are making a profit out of people who are either in possession of stolen cell phones, or are inconvenienced by government regulations. I rest my case.
Well said mimarsinan.
The board is aimed at XDA Developers. Mimarsinan set his mind to a task and came up with a solution. The burden is on him to take control of the release of that solution.
V
mimarsinan said:
Yes, I most certainly do not have the background to implement this project, but I have been helped by people (I don't think mamaich - unless he uses a different nick on other forums I have visited).
Click to expand...
Click to collapse
I confirm it was not me. My method works for HTC Universal only.
You are welcome Mimarsinan! We are waiting for the solution of your hard work. I lost my original IMEI number after a repair. The technician changed my ROM chip, the IMEI was changed and he said that he could not get the IMEI back. Now I want to get it back.
raskal said:
mimarsinan said:
I had to CID unlock the phone before our IMEI method would work. The method is not limited to Universal, but works on a wide variety of HTC phones, including Wizard which was my model.
It is really a shame nobody had a public tool that did this before. And Raskal, in all fairness, if you had made it easy for me to find a solution, I wouldn't have bothered to setup this project, work on it for a week, and finally manually unlock my phone.
I now have to keep my promise to the community and make the tool available for free as promised.
Click to expand...
Click to collapse
you have not made solution becuase you simply not have the background to do such tools. it is from mamaich, he is good in this what he do, you are just an "ibne", nothing more or less...
Click to expand...
Click to collapse
raskal ben ingilizce bilmiyorum ama sözlükle cevirerek anliyorm asil ibne your father diyorum adam ol adam
raskal bunuda sen sözlük bul cevir esseogluessek
Xda 2
Hi, Mimarsinan i tried your tool with my Himalaya but it detect the all imei number as 000000000000...... so i failed to update my imei, what is the algorithm of the imei changer? It search for the imei on a range of memory then update the addresses? Is there any check sum protection for imei changing?
I will be very happy if you help me for changing my himalaya's imei, thanks
mimarsinan said:
GOOD NEWS EVERYONE! WE'VE GOT A DELIVERY
Hello,
First of all, some good news to everybody in Turkey who has been afflicted by the IMEI problem. We have produced a working solution and intend to make it available to the Turkish public for FREE, as promised.
The procedure was tested on my i-mate k-jam which I unlocked successfully. I cannot express the sheer joy when my phone picked up the signal and remained connected! It worked!!!
Alas, my own overconfidence in this victory that came after a lot of hard work and research, resulted in me baking my i-mate's ROM during an attempted ROM upgrade. So I cannot enjoy my phone right now, however, this was not caused by our IMEI update process, which works fine. I just damaged my DOC while being careless with the latest "Self-Cooked" ROM, a most cavalier act indeed.
Now, this whole IMEI issue has drawn a lot of heat on the forums. I have been personally accused of being a thief, a hacker, among other things. I only have good intentions in mind, but I also want to consult with everybody in this forum, to put my ideas to the test of the real world (especially Richard's vicious criticism will at least provide a reality check as to the feasibility of our ideas).
Project goals:
1) Mechanism should only work in Turkey
2) Mechanism should only work once for each person
3) Mechanism should be free
4) Mechanism should be easy to use
Proposal for implementation:
1) To realize a Turkey-lock, we'll impose an IP address restriction. No IP outside of Turkey will ever work.
2) To realize the person-lock, we'll prevent the unlock wizard from running more than once on any given piece of hardware. We will also ban the tool from running on VMware/Virtual PC systems, to make sure people cannot side-step our hardware lock.
3) Free - that's easy! We just won't charge for it.
4) Easy to use - that can be harder, but we'll give it our best.
Please let us have your thoughts...and thanks to everybody who contributed to this project.
We'd like to make the product as solid as possible, so the restrictions cannot be circumvented, and this won't become a tool that the real thieves can use to unlock their phones. Any technical implementation suggestions on getting this done, including making our product binaries harder to hack, and making it harder to sidestep our limitations, are VERY welcome.
Don't worry - we won't force you to use a dongle! But we'll still do everything in our power to guarantee fair use of the tool, once per person.
Click to expand...
Click to collapse
So, where is the solution??
I couldn't see any solution changing IMEI for universal.
where is the tool?
is it developed yet?
download?
i also can't find any tool ?!!! where is it ?
There's no way you can imagine how far Turkish people go when it's about "swearwords", let's take a look simply...
ahmetce said:
raskal ben ingilizce bilmiyorum ama sözlükle cevirerek anliyorm asil ibne your father diyorum adam ol adam
Click to expand...
Click to collapse
Exact translation: raskal I don't know English but I can translate using dictionary and understand, I'm saying "the true fag is your FATHER, behave yourself!!"
ahmetce said:
raskal bunuda sen sözlük bul cevir esseogluessek
Click to expand...
Click to collapse
Exact translation: raskal Find a dictionary and translate this you jackass!!!
-----from communist russia with love-----
Help needed
Hey
Am desperate with this phone registration process here. I've paid the tax and turkcell is still playing around and not completing the registration. My last resort is to change the IMEI number of my cell. How can I use this service of yours? They are going to shut down my cell in three days... darn!
I've noticed that a some developers (myself included) would be substantially aided in their efforts if they had access to one or more Galaxy S test devices.
I don't know how successful this will be however I've created this thread as a central place for developers to “apply” for device donations and for members to put their (presumably broken) devices up for donation.
My phone is broken, can someone fix it?
If your phone is broken and you want it fixed then a Samsung Service Centre or your place of purchase is the place to get it done. However if for some reason Samsung won't fix your phone then you can list it here and it might inadvertently get fixed, but please make sure you read this whole post very carefully!
Deciding to donate... zero liability!
If you do decide to list a device here regardless of whether you're donating or lending it to someone the developer that you donate/lend it to is in no way liable for what happens to your phone. The purpose of this thread is so users can donate devices for experimental development. As such there is definitely a chance devices could get bricked or permanently damaged (if they're not already). If your warranty isn't already voided then it certainly will be. If you're not willing to accept this then do not donate!
I would like to think that developers who have been donated devices will return the device to the donator upon request, regardless of whether the phone was donated or lent. However, just in case I would like “donators” to make clear what they expect in regards to their donation, whether they intend to donate, lend, donation time-frame etc.
Which developer gets which phone?
I think it should be up to the donator to decide what projects are more worthy or more relevant to the donator. I'm not going to assign phones to projects unless the donator requests that I do so.
How are broken devices useful?
Obviously that depends on what the developer is doing. To some developers a bricked device may be totally useless. However, for developers working on low-level interfacing (JTAG etc.) then bricked devices are basically the perfect test subject.
Shipping the device and costs.
I think it's only fair that people donating their phone shouldn't have to pay the cost to ship the phone to the developer. However, the return shipping costs (if the donator wants the phone returned) should be negotiated on per donation basis.
If the phone turns on the donator MUST disable all security features, in particular the mobile tracker functionality!
Applying/Listing
Developers or donators should fill out the following forms respectively.
--- Developer Application ---
Project Title:
Project Description:
Device Requirements:
Example 1. A Bell I9000M that in the past had access to download mode.
Example 2. Any device that charges.
Location:
Extra Information:
--- Donator Application ---
Donation Type: [Donating/Lending]
Phone Type:
Phone Status:
Example 1. Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Example 2. Doesn't respond to power button or charger... it's dead!
Location:
Developer Requirements:
Example 1. Need the device back in a month.
Example 2. If the device gets fixed I would like it returned.
Extra Information:
----------------------------------- Developers -----------------------------------
Benjamin Dobell < celtichazard* (Returned)
dagentooboy
----------------------------------- Donators -----------------------------------
celtichazard -> Benjamin Dobell* (Returned)
Bold - Assigned
Regular - Unassigned
* - Lent
Project Title: Heimdall (and JTAG Research)
Project Description:
Heimdall is an open-source, cross-platform replacement for Odin. It is currently in alpha and is in need of testing. For more detailed information refer to the Heimdall thread.
I'm also interested in doing some JTAG research that will hopefully help bring "fully bricked" phones back to life.
Device Requirements:
Any Galaxy S (or derivative) phone in any state what-so-ever.
Location:
Melbourne, Australia
Extra Information:
I'm good with being lent or donated devices. I'm also happy to return donated devices if I'm able to fix them.
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
andrewluecke said:
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
Click to expand...
Click to collapse
I don't think it should be up to me to decide who is qualified. However I will add something to the original thread that makes it clear it is the donators choice as to who they donate to (I'm not going to automatically assign phones to people).
Lending
--- Donator Application ---
Donation Type: Lending
Phone Type:Samsung Galaxy S i9000 european version
Phone Status:
Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Location: Country : Mexico State: Chihuahua City: Juarez
Developer Requirements:
If the device gets fixed I would like it returned.
Extra Information: The device was flashed with AT&T Rom
celtichazard will be lending me his bricked phone so that I can perform some JTAG research into unbricking Galaxy S phones.
If anyone is interested in this research and would like to donate to help cover the cost of shipping, JTAG adapters, wires, components, solder etc. that would be very much appreciated.
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
jjwa said:
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
Click to expand...
Click to collapse
First of all, thank you very much for the donation.
The research that I'll be doing with celtichazard's phone is in regards to finding a way to unbrick any bricked Galaxy S phone. The research is not immediately related to Heimdall. However, if I do manage to work out how to unbrick a phone it will definitely be beneficial for everyone. It will also have a positive effect on the development of Heimdall, as it will allow me to try more experimental functionality without worrying about having to send my phone off to the UK for repair if something goes wrong.
Project Title: JTAG
Project Description:
Trying to figure out a way to unbrick "fully bricked" phones.
Device Requirements:
Any Galaxy S (or derivative) phone in a "fully bricked" state.
Also a fully working one would be nice so I can dump the bootloader.
Location:
Madrid, Spain
Extra Information:
JTAG can bring a bricked phone back to life. If I figure out how to make this work your phone will be fully working. If not then it will still be bricked. I would be willing to return the phone in whatever state it is in when I am done. If you are in the United States a USPS flat rate priority mail box to me is $15. If you have a device that you want to ship let me know and if I need it I will pay for shipping one way.
andrewluecke said:
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
Click to expand...
Click to collapse
I only just realised you edited your post.
The liability statement is mostly in place to ensure developers aren't held responsible for damage (which may or may not have been their fault) or postage related issues.
I understand your concerns in regards to having the device returned, but quite simply there is absolutely no way to enforce such a policy. International law is largely a myth so attempting to enforce any such clause would be near impossible. If you're donating to someone within the same country then you certainly could write-up a contract. I'm not a lawyer, but if a donator wants to organise such a contract with a developer then they're certainly free to do so.
The best thing you can do is to make sure you donate to a reasonably well known developer. If the person you're donating to has a reputation to uphold then you've definitely got some leverage if things get nasty.
Regardless I sincerely hope that we won't see that sort of situation here.
dagentooboy is still looking for someone to donate or lend him a phone. His JTAG research is similar to the work I'll be doing and is extremely important. The more people we have working on it the more likely we'll come across a fix.
If someone has a bricked phone they are willing to donate/lend that would be fantastic.
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
neldar said:
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
Click to expand...
Click to collapse
Great idea, I just finished updating the first post.
neldar said:
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
Click to expand...
Click to collapse
Yeah all phones are accepted depending on what particular developers are after. However thus-far I believe myself and dagentooboy have been willing to accept any SGS phone (including derivatives).
yeah any GSM galaxy s phone would be fine... if it is CDMA I won't be able to test the cell side (to make sure I didn't break it).
Project Title: UnBrickable Mod
Project Description:
An end user solution to unbricking fully bricked phones with only a wire and soldering skills
Device Requirements:
an i9000 device which can have the processor removed and not replaced.
Location:
Louisiana, USA
Extra Information:
UnBrickable Mod has been performed on the Captivate and I'd like to get this modification out to you guys in the i9000 sector. This mod allows you to flash bootloaders and not think twice. Thereby increasing development and allowing for repurposing of our phones at the end of their lives as a Ubuntu device, or similar.
This modification will be fully documented and open-source. It will help the entire community get out of a jam without any additional hardware if they have the skills to solder two points on the board. I must locate these points and it requires removal of the processor. I can return the device which will be inoperative if required.
See video for explanation of how easy it will be to unbrick with UnBrickable Mod.
The execution of a single device will allow resurrection of all others.
Project Title: Thor (an alternative to Heimdall)
Project Description:
Thor is aiming to be more stable and up-to-date.
Here is an XDA thread about it.
Here is a list of new features that I want to test:
1) Ability to flash from BL/AP/CP/CSC .tar archives directly
2) Ability do download latest firmware and flash it automatically
3) Ability to flash compressed (.lz4) files directly (newly discovered)
4) You can shut down the device from GUI immediately (no reboot)
5) PIT viewer built-in, with more accurate information
6) Ability to do NAND Erase All (actually it just erases userdata)
7) Ability to do DevInfo (information about the device: model, carrier id, region, serial code)
Device Requirements:
1) Any Samsung device with Odin v3 protocol
2) Lending only, as my parents would tell me to **** off
Location:
Obviously you don't need this.
Extra Information:
None
Project: PostmarketOS, UBPorts on galaxystmd
Old device: but I have multiple. Willing to send one to device to multiple developers with experience and desire to port for proof-of-concept and/or restoring functionality to this device via mainline Linux (PMOS).
UBTouch would be a secondary effort: as it had been ported during the initial launch, but did not get migrated to the UBPorts project.
3rd effort would be porting latest Lineage, modded/optimized ROM, stripped down/optimized kernel. "One final rodeo."
1 Device per person Per Effort.
So realistically I would give each person up to three devices.
I have read at least 50 disinformation type posts on this site about unlocking a branded Xperia (Verizion in my case) they all seem to be wanting me to pay money to Alejandrissimo or Jinx13 but when I click on those hyperlinks they are all "Invalid post" so what am I supposed to be finding here that I missed?
There is not any topic stickied that is describing how to unlock the thing & every article / forum post / google search I find is another disinformation post with no real evidence.
I know how to flash ROM's onto android using recovery loaders.
I know how to access the program menu's in various phones
I know what the CDMA spectrum is.
I'm not some newb making this post because I need my hand held step by step to do something.
I just need some real information
If anyone has a link to a real method or anything helpful please let me know
I have researched (and watched the welcome video) on this site to find an answer and I haven't found anything.
Thanks
-Jon
Ok, so the links to the unlockers in my thread are broken. Does it mean that my post has "disinformation"? Is there any other way to unlock the bootloaders? No to both, as far as I know. I'll try to fix the links, but seriously...
About why my post (or any other helpful resource about the matter) is not stickied, I don't know nor do I care. No one reads stickies anyway.
Logseman said:
Ok, so the links to the unlockers in my thread are broken. Does it mean that my post has "disinformation"? Is there any other way to unlock the bootloaders? No to both, as far as I know. I'll try to fix the links, but seriously...
About why my post (or any other helpful resource about the matter) is not stickied, I don't know nor do I care. No one reads stickies anyway.
Click to expand...
Click to collapse
By disinformation it would seem that some exists.
droid-life reported 4 months ago ashergray(XDA) found a method to unlock the bootloader.
Why none of the methods being released or talked about is beyond me.
Also I'm confused why the method is being charged for by others but not officially it would seem.
You have to pm users on the forum to arrange a sale. Why does a topic not exist for this purpose?
All this confusing data is leading to a big headache right now. I was hoping for answers and all I find is rabbit holes on this elusive topic.
Thanks for the reply tho.
Ashergray's method was dried out (it exploited a flaw, and the flaw was fixed).I mention ashergray in the thread, as it is only fitting, in the thanks part.
About why they ask to be contacted privately or publicly, it's their business... Is there something that should be cleared in my thread, aside of the links of course? I mean, I can try to rebuild the first post if necessary.
Logseman said:
Ashergray's method was dried out (it exploited a flaw, and the flaw was fixed).I mention ashergray in the thread, as it is only fitting, in the thanks part.
About why they ask to be contacted privately or publicly, it's their business... Is there something that should be cleared in my thread, aside of the links of course? I mean, I can try to rebuild the first post if necessary.
Click to expand...
Click to collapse
You could start off by explaining why in 7 months time the boot loader is sill locked.
Or why your links to the unlock threads are dead. Both of them.
Or how I'm supposed to unlock the bootloader if these users can't provide that service any longer.
Also you could mention why Sony. being developer and hacker supportive hasn't assisted in taking Verizon's clutch off the bootloader
It is rather annoying coming from Droid x where the device is locked down with a fuse but yet a wide array of custom roms exist that bypass the locked bootloader and then coming to this phone that appears to have not progressed beyond hello world.
So you tell me where to look for an unlock because I'm fresh out of searches and ideas.
Thanks
-jon
P.s I also wonder if the exploit you speak of was patched. Why not just flash to an earlier rom with the problem still existing.
You could start off by explaining why in 7 months time the boot loader is sill locked.
Or why your links to the unlock threads are dead. Both of them.
Or how I'm supposed to unlock the bootloader if these users can't provide that service any longer.
Also you could mention why Sony. being developer and hacker supportive hasn't assisted in taking Verizon's clutch off the bootloader
It is rather annoying coming from Droid x where the device is locked down with a fuse but yet a wide array of custom roms exist that bypass the locked bootloader and then coming to this phone that appears to have not progressed beyond hello world.
So you tell me where to look for an unlock because I'm fresh out of searches and ideas.
Thanks
-jon
P.s I also wonder if the exploit you speak of was patched. Why not just flash to an earlier rom with the problem still existing.
Click to expand...
Click to collapse
1) I kindly would like to ask how I'm supposed to know why the bootloader is locked. It's a corporate decision by carriers and Sony Ericsson in which neither I, nor anyone in this forum, have any input. If I had any hard data about why Sony Ericsson doesn't cooperate in the issue, I'd say it. However, I just don't know why, and I prefer not to speak of what I don't know.
2) It seems that both threads have been wiped out of existence (which I didn't know until right now), and I see that a new site appears in Alejandrissimo's signature (http://unlock-bootloader.com/) where he's promoting his services externally (not only the unlocking, but the TA fix and hard-brick fix too). I'd guess that somebody complained about these people making business inside XDA, but then I question the idea of wiping their threads like... months afterwards. At any rate, don't worry, you still can unlock your bootloader with Alejandrissimo's help.
3) On Droid X the bootloader was bypassed because Motorola wouldn't ever unlock it. The FreeXperia team, who had bypassed older Xperia models' bootloaders, decided against it as they saw the new policy of Sony Ericsson's (unlocking phones which didn't come with carrier subsidy). I could unlock my bootloader from day one, and I'm happy to say I've helped devs here therethrough.
4) The exploit was related to the website where you could unlock R800i models. In order to unlock your bootloader, you need to give your IMEI number (an ID code for GSM phones). Ashergray could convert MEID numbers used by CDMA phones into bogus IMEI numbers, which could be used to unlock the devices. Sony Ericsson patched the website so ashergray's trick didn't work anymore.
5) My thread is a "how-to", do you really expect me to add points 1), 3) and 4) to it?
4 months is an eternity for this kind of business. Exploits get fixed (look at the PSXperia case), policies change (like HTC's and Motorola's) and threads are wiped on short or no notice.
Logseman said:
1) I kindly would like to ask how I'm supposed to know why the bootloader is locked. It's a corporate decision by carriers and Sony Ericsson in which neither I, nor anyone in this forum, have any input. If I had any hard data about why Sony Ericsson doesn't cooperate in the issue, I'd say it. However, I just don't know why, and I prefer not to speak of what I don't know.
2) It seems that both threads have been wiped out of existence (which I didn't know until right now), and I see that a new site appears in Alejandrissimo's signature where he's promoting his services externally (not only the unlocking, but the TA fix and hard-brick fix too). I'd guess that somebody complained about these people making business inside XDA, but then I question the idea of wiping their threads like... months afterwards. At any rate, don't worry, you still can unlock your bootloader with Alejandrissimo's help.
3) On Droid X the bootloader was bypassed because Motorola wouldn't ever unlock it. The FreeXperia team, who had bypassed older Xperia models' bootloaders, decided against it as they saw the new policy of Sony Ericsson's (unlocking phones which didn't come with carrier subsidy). I could unlock my bootloader from day one, and I'm happy to say I've helped devs here therethrough.
4) The exploit was related to the website where you could unlock R800i models. In order to unlock your bootloader, you need to give your IMEI number (an ID code for GSM phones). Ashergray could convert MEID numbers used by CDMA phones into bogus IMEI numbers, which could be used to unlock the devices. Sony Ericsson patched the website so ashergray's trick didn't work anymore.
5) My thread is a "how-to", do you really expect me to add points 1), 3) and 4) to it?
4 months is an eternity for this kind of business. Exploits get fixed (look at the PSXperia case), policies change (like HTC's and Motorola's) and threads are wiped on short or no notice.
Click to expand...
Click to collapse
I've sent you some PM's to remove spam / offtopic / rant from the board.
Thanks for the information tho. I wasn't aware of any of that.
It seems that the name FreeXperia is a bit of a misnomer because my Xperia is going to be locked unless I pay 25$ apparently and thats sad when I only paid 90$ for the phone used. Could have been cheaper if I had bought bad ESN(I probably should have tried)
Imagine my surprise coming from Droid X to this phone where droid X has heaps of ROM's available to everyone for free and now I have to worry about getting this device to function at the same level as my old DX with Gummy JAR rom.
I Just wish the spirit of opensource would be in this sub-forum so we could have some real development in terms of flavors of roms and such.
Do you think their is any reason the developers are all charging fee's to show the method through team viewer? I thought it could have something to do with leaking the method and then it could be fixed in later updates. but then again maybe I'm wrong.
It's not that they "show" you the method. They "perform" the method for you. I'm not sure if you can do it with Omnius as well... but if you can, it will be marginally cheaper (unlocking credits are needed anyway!) and you have no assistance.
And about the old "why charge for open source software" dead horse, which is pointless here because there is no open source software involved (the bootloaders are closed-source, SETool is closed-source, and so on):
The Free Software Foundation said:
“Free software” does not mean “noncommercial.”
Click to expand...
Click to collapse
Additionally, as I said before, the FreeXperia team has this policy: http://forum.xda-developers.com/showpost.php?p=15253598&postcount=217
Logseman said:
It's not that they "show" you the method. They "perform" the method for you. I'm not sure if you can do it with Omnius as well... but if you can, it will be marginally cheaper (unlocking credits are needed anyway!) and you have no assistance.
And about the old "why charge for open source software" dead horse, which is pointless here because there is no open source software involved (the bootloaders are closed-source, SETool is closed-source, and so on):
Click to expand...
Click to collapse
Right on. I'm following you thus far.
Question tho. I read that sony was the best company for hackers and developers right now because they actually are allowing people to get access to the bootloaders. If all this is true why are they not assisting in the unlock of branded phones?
I might be wrong on this but aren't most peoples phones branded anyways through buying a contract?
and that leads to why FreeXperia didn't realize that and find an exploit / workaround for the bootloader being locked on branded phones.
If Setool and Omnius (or whatever it's called) are able to unlock the phones then why was sony. the engineer of the device not able to perform this same task?
Also I thought locking the bootloader violates the FCC regulation. open access provision so why didn't Sony assist the FCC to bypass Verizon.
God another douche, you pay 90 bucks for your phone and you think this community owes you something. Go complain to sony.
What do you mean, Sony can't do it? Of course they can. But they have chosen to do so only with R800i non-branded phones. Considering that they locked bootloaders without any official way to unlock them on previous Xperia models, that's a big step forward. That's as far as Sony Ericsson can go: on branded phones, they must obey what the carriers want.
Please do read Bin4ry's statement:
Now think about, if we would try to hack and bypass devices what will happen with future phones? In our opinion future phones will be locked down again like X10 was, eventually even more.
So why don't use the possibilties which are give by SE? Stick to their rules and hope for more support and maybe even nicer implementations (for example a accessable bootpartition from recovery).
We like SE devices, so we don't want to hijack this (i call it) "test" which SE drives with us?
I can fully understand that U.S. users which cannot unlock are quite unhappy with the actual situation, but sorry we will NOT work on anything else than development for officially unlocked devices! That was a team decision.
Click to expand...
Click to collapse
Note that this is costing them a lot of flak because they don't use R800x models for testing purposes either, and CM7 has many issues in R800x phones.
Also I thought locking the bootloader violates the FCC regulation. open access provision so why didn't Sony assist the FCC to bypass Verizon.
Click to expand...
Click to collapse
If this is correct, sue. I'm sure you'll have backing from everyone here.
Logseman said:
What do you mean, Sony can't do it? Of course they can. But they have chosen to do so only with R800i non-branded phones. Considering that they locked bootloaders without any official way to unlock them on previous Xperia models, that's a big step forward. That's as far as Sony Ericsson can go: on branded phones, they must obey what the carriers want.
Please do read Bin4ry's statement:
Note that this is costing them a lot of flak because they don't use R800x models for testing purposes either, and CM7 has many issues in R800x phones.
If this is correct, sue. I'm sure you'll have backing from everyone here.
Click to expand...
Click to collapse
So what your saying is that CM7 is not even worth flashing even if i was unlocked?
I would be better off to root / Titanium backup / delete bloat and be done with it?
Its a shame that they are forcing most people to stay stock SE/Verizon ROM because they are scared of the repercussions of angering SE. I think even if they stay inert that SE will eventually add more DRM to "protect" the devices.
About the lawsuit. I don't believe I'm the first person to mention it. Verizon has already been sued for 25 Million i believe on another occasion and it's been said by others that they are breaking FCC Regulation. The problem would be to get something done about it and I wouldn't have those resources.
The reason for the charge is very simple. In order to unlock our version of the Play (R800x), it takes a hardware dongle and the purchase of credits to allow the software to work. All you are paying Al or whoever for is the cost of the number of credits necessary to unlock your phone. They aren't getting rich off anyone.
If there was another way to unlock the Verizon version, someone would have posted it by now. There isn't, and that's just how it is.
There is a good spirit of free info sharing on this site. You might have to do a little digging but it's there. For example, how to unroot the R800x without having an unlocked bootloader. Takes about a whole 5 minutes to do.
EDIT: I do have to say that after digging around a bit more, I don't blame you for being perturbed. While no one owes us Verizon Play owners anything, there could have been something posted and sticky to make it a bit easier to find out what is going on. And perhaps have had a bit less condescension toward us as well. Must be that UK mentality toward us Colonists!
Re: Droid X vs XPlay development -
Different phones from different brands on different carriers require entirely new learning to develop for, not to mention owning a device to work on. I'd say there's probably only about a dozen people worldwide putting in serious work on this phone.
That's not a lot. If you want more options, you may have to do it yourself.
Before you start to think I am about to scream "GPL, GPL, GPL," stop for a second, take a deep breath, and sympathize with the thousands of power users and developers who have been left in the dark and/or ignored in regard to their device being partially unlocked with a seeming false advertisement. This is an opinionated piece in the regard of actually getting what we asked for and were promised to receive.
Not long ago, users and developers alike relied heavily on hackers and logic to achieve S-OFF to get the full experience of their desire for a great(er) experience on their Android phone. Some people buy an overlay device like HTC with Sense, Motorola with Blur, and so on, knowing what entails when they get it, but they anticipate running a stock experience or a heavily optimized build from one of the developers in this community. Recently we took a moment to talk with ToastCFH and Dees_Troy from TeamWin, who are responsible for HTC Dumlock. HTC Dumlock makes the unlocked device further accessible for a few more phones.
Last week we purchased some T-Mobile One S units for our developers and one of them was chosen to go for a test drive and to try out HTC Dev Bootloader Unlock. This is where we got to know each other and a bit more about HTC's online utility, which nonetheless has disappointed thousands more than just a bit. I am going to let everyone know now: do not plan on just stopping at rooting this and calling it a day, I tried to remove bloat with Root Explorer and came to a brick wall of denial. I found out you also cannot flash custom kernels in recovery mode.
"What is affected in retrospect when I unlock?" Let me answer that: It actually cripples your phone. It's probably less risky to take a chance and go for an S-OFF method that could potentially brick your device. As per numerous reports, and some insight from ToastCFH and Dees_Troy, there is a plethora of issues with this process and many gripes and speculation just coming from myself.
A cobb without a Kernel: Flashing a kernel is similar to trying out walking on coals. You have to do the following (coming from ToastCFH at XDA):
fastboot boot recovery alternaterecovery.img
Here's some thought: If you flash a crap/test kernel that doesn't boot, not only can you not pull the battery you have to relentlessly use your power button to get yourself out of the mess to get the phone to shut off (HTC One series). The reason you can do it through "booting" recovery as opposed of using the one you flashed: The boot method is actually using the boot/temp partition, which in the end, is not really the boot partition.
HTC, why are you doing this? Aren't you supposed to be trying to deter users from chasing exploits and trying to gain S-OFF? It sure doesn't seem like it. From this perspective, it seems you will be are pissing off and running away potential customers instead. The image you see above is the warning you receive in HBOOT after unlocking the device via HTC Dev. Note that it doesnt say "unlocked" but a very menacing "Tampered," a word that carries a different set of connotations altogether.
All your system are belong to HTC: ROM Manager uses a script to replace your recovery while in Android. The slight issue is, it requires root. Root is the center of the development universe when it comes to ROMs, kernels, mods and the likes of the bunch. HANDS DOWN, most of the alterations you make to your phone while booted in Android utilize root and the system partition. This is not only a P.I.T.A., it can be a deal-breaker. I will get to that point in a bit. First, let's take a look: How do I tinker with something if the manufacturer tells me I can but in reality I can't? Conundrums. It's amazing: You cannot remove the bloat from your phone, you cannot replace the recovery and you sure cannot replace the boot image while booted in Android/Sense.
Radio killed the kernel dev star: Yes, radio. Those cool P*IMG.zip files you flash in HBOOT, that's out the window... Unless you get an RUU (ROM Update Utility) and go back to the stock firmware. With older HTC devices with S-OFF, you could slap a P*IMG.Zip (essentially a firmware/radio update in HTC's update.zip format) on the SD card and boot into HBOOT. It would check and flash it for you. That whole proces is gone; this entire process of being able to do this on the mobile side is now gone. You will now need a computer to flash the file.
To need or not to need... That is the question: Toast brings up another excellent point: If these measures have to be in place (maybe due to carrier request) why not provide the proper documentation to support the device? We're pretty sure when someone unlocks this device they understand they are giving up any firmware support from HTC.
Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
- ToastCFH
An excellent point, and most of you will probably agree with his bomb of logic. At the end of the day, he is right; the unlock method is crap and we find it more of a hinderance and crippling intent rather than a compliance to the developer community who has made them the number one development device for so long. Recently Samsung has taken the torch and led its dedicated developers with fulfilled promises and standards.
HTC, why would you do this? That is far too easy. Clarification, reason, justification, etc., it isn't needed. It's about doing the right thing. HTC has kept the proverbial sprinklers on and now the unlock tool is watered down. My advice for the power user/modder/dev is that this tool is essentially useless. We have been the number one spot for developer support by giving free devices to developers and UI designers to make the device even more fun and unique. We will continue to support, drive, and advocate open development on a supposedly open platform and follow those who make it what it is today. With that being said, it makes us skeptical in giving devices to people that HTC seems to have set a navigation route to Failure Avenue, and know that the developer on hand won't feel shorted. HTC, let us own our devices. Some love the hardware, some love the software, but in the end we love Android.
Lastly, GPL. It is is not made to stretch the maximum time available and take your time. It is probably a good suggestion to set up an HTC gitweb or something of the nature to ensure that when the device is available, the developers that you "support" so much can have free reign at improving your device and moving forward at their own pace. That making the final connection to the developer house, letting the user and developer free you from providing software support. Release the source, fully alert and vigilant. We know it takes time to clean code, but the One X (international) community could really use some tasty kernel source code right about now.
One last note: HTC may not be able to further assist with the firmware/software/OS once unlocked, but you can still support your hardware by giving some documentation on how to proceed with an unlocked device. Giving someone a flashlight with no batteries in a dark house isn't an ideal method of answering our call.
Sincerely,
Your Customer.
If you read this, please take a moment and support your developers and modders that enhance your phone life everyday, by tweeting, sharing or posting on Facebook the following quote:
" @HTC we want our phones back! http://tinyw.in/LNSn "
Thanks to everyone who has read and contributed to this piece.
****
My contribution.
I made it about 60% through and I still don't see s-off released. ;p
acer73 said:
Before you start to think I am about to scream "GPL, GPL, GPL," stop for a second, take a deep breath, and sympathize with the thousands of power users and developers who have been left in the dark and/or ignored in regard to their device being partially unlocked with a seeming false advertisement. This is an opinionated piece in the regard of actually getting what we asked for and were promised to receive.
Not long ago, users and developers alike relied heavily on hackers and logic to achieve S-OFF to get the full experience of their desire for a great(er) experience on their Android phone. Some people buy an overlay device like HTC with Sense, Motorola with Blur, and so on, knowing what entails when they get it, but they anticipate running a stock experience or a heavily optimized build from one of the developers in this community. Recently we took a moment to talk with ToastCFH and Dees_Troy from TeamWin, who are responsible for HTC Dumlock. HTC Dumlock makes the unlocked device further accessible for a few more phones.
Last week we purchased some T-Mobile One S units for our developers and one of them was chosen to go for a test drive and to try out HTC Dev Bootloader Unlock. This is where we got to know each other and a bit more about HTC's online utility, which nonetheless has disappointed thousands more than just a bit. I am going to let everyone know now: do not plan on just stopping at rooting this and calling it a day, I tried to remove bloat with Root Explorer and came to a brick wall of denial. I found out you also cannot flash custom kernels in recovery mode.
"What is affected in retrospect when I unlock?" Let me answer that: It actually cripples your phone. It's probably less risky to take a chance and go for an S-OFF method that could potentially brick your device. As per numerous reports, and some insight from ToastCFH and Dees_Troy, there is a plethora of issues with this process and many gripes and speculation just coming from myself.
A cobb without a Kernel: Flashing a kernel is similar to trying out walking on coals. You have to do the following (coming from ToastCFH at XDA):
fastboot boot recovery alternaterecovery.img
Here's some thought: If you flash a crap/test kernel that doesn't boot, not only can you not pull the battery you have to relentlessly use your power button to get yourself out of the mess to get the phone to shut off (HTC One series). The reason you can do it through "booting" recovery as opposed of using the one you flashed: The boot method is actually using the boot/temp partition, which in the end, is not really the boot partition.
HTC, why are you doing this? Aren't you supposed to be trying to deter users from chasing exploits and trying to gain S-OFF? It sure doesn't seem like it. From this perspective, it seems you will be are pissing off and running away potential customers instead. The image you see above is the warning you receive in HBOOT after unlocking the device via HTC Dev. Note that it doesnt say "unlocked" but a very menacing "Tampered," a word that carries a different set of connotations altogether.
All your system are belong to HTC: ROM Manager uses a script to replace your recovery while in Android. The slight issue is, it requires root. Root is the center of the development universe when it comes to ROMs, kernels, mods and the likes of the bunch. HANDS DOWN, most of the alterations you make to your phone while booted in Android utilize root and the system partition. This is not only a P.I.T.A., it can be a deal-breaker. I will get to that point in a bit. First, let's take a look: How do I tinker with something if the manufacturer tells me I can but in reality I can't? Conundrums. It's amazing: You cannot remove the bloat from your phone, you cannot replace the recovery and you sure cannot replace the boot image while booted in Android/Sense.
Radio killed the kernel dev star: Yes, radio. Those cool P*IMG.zip files you flash in HBOOT, that's out the window... Unless you get an RUU (ROM Update Utility) and go back to the stock firmware. With older HTC devices with S-OFF, you could slap a P*IMG.Zip (essentially a firmware/radio update in HTC's update.zip format) on the SD card and boot into HBOOT. It would check and flash it for you. That whole proces is gone; this entire process of being able to do this on the mobile side is now gone. You will now need a computer to flash the file.
To need or not to need... That is the question: Toast brings up another excellent point: If these measures have to be in place (maybe due to carrier request) why not provide the proper documentation to support the device? We're pretty sure when someone unlocks this device they understand they are giving up any firmware support from HTC.
Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
- ToastCFH
An excellent point, and most of you will probably agree with his bomb of logic. At the end of the day, he is right; the unlock method is crap and we find it more of a hinderance and crippling intent rather than a compliance to the developer community who has made them the number one development device for so long. Recently Samsung has taken the torch and led its dedicated developers with fulfilled promises and standards.
HTC, why would you do this? That is far too easy. Clarification, reason, justification, etc., it isn't needed. It's about doing the right thing. HTC has kept the proverbial sprinklers on and now the unlock tool is watered down. My advice for the power user/modder/dev is that this tool is essentially useless. We have been the number one spot for developer support by giving free devices to developers and UI designers to make the device even more fun and unique. We will continue to support, drive, and advocate open development on a supposedly open platform and follow those who make it what it is today. With that being said, it makes us skeptical in giving devices to people that HTC seems to have set a navigation route to Failure Avenue, and know that the developer on hand won't feel shorted. HTC, let us own our devices. Some love the hardware, some love the software, but in the end we love Android.
Lastly, GPL. It is is not made to stretch the maximum time available and take your time. It is probably a good suggestion to set up an HTC gitweb or something of the nature to ensure that when the device is available, the developers that you "support" so much can have free reign at improving your device and moving forward at their own pace. That making the final connection to the developer house, letting the user and developer free you from providing software support. Release the source, fully alert and vigilant. We know it takes time to clean code, but the One X (international) community could really use some tasty kernel source code right about now.
One last note: HTC may not be able to further assist with the firmware/software/OS once unlocked, but you can still support your hardware by giving some documentation on how to proceed with an unlocked device. Giving someone a flashlight with no batteries in a dark house isn't an ideal method of answering our call.
Sincerely,
Your Customer.
If you read this, please take a moment and support your developers and modders that enhance your phone life everyday, by tweeting, sharing or posting on Facebook the following quote:
" @HTC we want our phones back! http://tinyw.in/LNSn "
Thanks to everyone who has read and contributed to this piece.
****
My contribution.
Click to expand...
Click to collapse
Done
Sent from my HTC Desire HD using Tapatalk
Done
I would share it but its got to many bad grammatical mistakes that makes its a hard read plus doesn't specifically request things like S-OFF. The sentiment surely is right though.
I read that jellybean was rumoured to be released to other network providers by the end of this week so..
I decided to check with an "o2 Guru" if they could tell me when Jellybean will be rolled out to the O2 branded HoX
As expected they could not answer my query - see below for the chat
You're through to Guru Steve.
Steve: Hi I'm Steve. How can I help?
Andy: Hi steve
Steve: Hello.
Andy: I was hoping you can tell me when Jellybean firmware will start to roll out on my HTC One X handset?
Steve: I'll check the info for you.
Andy: Thanks
Steve: Whenever a new software is launched by the manufacturers, we investigate and make sure that there is no issues in it which may affect the phone. Once it's done, it's shared for all our customers on our website. As of now, the investigation isn't done, so you'll have to wait for a few weeks until it's launched by us. Your patience and understanding is appreciated.
Andy: What stage are you guys currently at with testing? Do you have a ETA for the rollout to O2 customers?
Steve: I'm sorry this done by our software engineers and there is no exact timescale but once it is released on o2 you'll surely get the update about this.
Andy: The update has been released by HTC for unbranded devices and other service providers, o2 are always behind the pack with updates which is frustrating, Do you know how I can unbrand the device?
Steve: Yes the HTC has released for phones which are not network locked. Just to inform you that we don't want our customers to face the difficulty after upgrading the software that's the reason it is first tested and then it is released to network phones.
Andy: If the handset was not branded by O2 then I could flash the generic one that was released by HTC - Some customers have an idea what they are doing when it comes to software for their devices, I think it would be good to have an option to opt in for branding or opt out for development purposes
Andy: This is making me think twice about renewing my contract next summer - I would rather be paying money for a device I have full control over than to be treated like just another consumer
Steve: I respect your decision but I hope you can also understand my limitations as software are released by the manufacturer and then it is sent to service provider.
Andy: Yes I can understand you cannot answer any of my questions as your role is limited to a service desk and you can only give out information given by each division within your organisation. This is not directed at you personally, O2 can never clarify these things - your software team should give out better communication to you guys on the front end
Steve: Yes I can understand and I'll also surely forward your feedback to our relevant team.
Andy: LOL, Ok Im sure that will help me - Goodbye
So still no answers for O2 branded devices - My next move is to approach HTC and ask if they can tell me how to SuperCID
Don't expect any better help from HTC UK.But good luck in your quest.
I think tc was kinda rude, it's pretty obvious this call center guys don't know anything..
In fact most companies are hiring external help, so they know even LESS about the situation
Sent from my HTC One X using Tapatalk 2
The solution is simple:
Bye bye htc and scamming branded phone companies, buy your handset unbranded without a contract!
Hi Guys
Can we keep anything to do with confirmed updates in here:
http://forum.xda-developers.com/show....php?t=2009525
And anything to do with JB discussion (including what this thread is in respect of)
in here:
http://forum.xda-developers.com/show....php?t=2028941
Cheers peeps
Peace out
Thread closed. See post above mine for reasons.
Let's keep a MINIMUM of structure, please.