ORIGINAL START OF MY WORK THREAD:
http://forum.xda-developers.com/showthread.php?t=1576844
PORTAL WRITE UP:
http://www.xda-developers.com/android/simons-wildfires-utility-brings-intact-warranty-root-and-more/
Hello everyone, you may have heard of my unlocking tool for windows. It unlocks HTC devices and i am slowly but surely adding support for new devices. The sensation happened to be next on the list. I will be adding it to the official GUI app once this is confermed, so for now it is a batch file that needs testing. If you dont trust me for any reason, just open up the zip and view whats inside the batch file, i have nothing to hide Please report back any errors, not just "it dont work" I will ask the mods to look at those types of posts.
Download v1
TEST 1
unlock sim? Bootloader or else? Please provide more details
Bootloader without voiding the warranty (htc voids warranty apon unlock in countries that dont forbid it eg USA) original thread located here:
http://forum.xda-developers.com/showthread.php?t=1576844
ok if unlock hboot 1.27 is very good news for sensation users but i can't help because i already have unlocked bootloader. Thanks for your work
in theory this will unlock any device in which the s-off method's root works. Jupno bear i think its called? I can change root methods, but the method inside is definitively solid enough to unlock with root.
Thanks for wanting to include the Sensation with your tool simonsimons34 we can always use good utilities to make unlocking and modding our devices easier. But just to let you know the Sensation already has two great tools. Here is kgs1992's Super Utitlity and the article featuring it just yesterday in the Portal. The Sensation also has the HTC Sensation 4G All-In-One Toolkit by hasoon2000 that is stickied in the Sensation Android development forum.
This does something the others cant :/ which is why i included it. This works for any hboot revision and any rom as long as you have root (or can get it with the method i icluded -thanks jcase for finding it) This Unlocks the phone WITHOUT the need to contact htcdev and submit a token. Sure it doesnt S-off or anything, but for new phones or phones which there are no ways to install roms except by contacting HTCDEV.com and voiding your warranty, this is a life saver. Just check out what it does before you say its already been done please. I mean no offence to you, just however am annoyed you posted saying its been done before you looked into what it does
simonsimons34 said:
This does something the others cant :/ which is why i included it. This works for any hboot revision and any rom as long as you have root (or can get it with the method i icluded -thanks jcase for finding it) This Unlocks the phone WITHOUT the need to contact htcdev and submit a token. Sure it doesnt S-off or anything, but for new phones or phones which there are no ways to install roms except by contacting HTCDEV.com and voiding your warranty, this is a life saver. Just check out what it does before you say its already been done please. I mean no offence to you, just however am annoyed you posted saying its been done before you looked into what it does
Click to expand...
Click to collapse
Sorry man I did not mean to offend. I can not actually use your tool because I am already S-off with Revolutionary Hboot 1.17.1111. I downloaded your tool and yes this is awesome that your tool unlocks the bootloader. But did you actually look at the links I gave you? the Super Utitlity allows you to use Juopunutbear S-off without having to use HTC Dev Unlock first by utilizing the download from Unlimited.io (scroll to the bottom) wich is the website for the Juopunutbear S-off and it supports all Hboot versions, . So even though the Super Utility does not unlock the bootloader forsay, still the ability to not have to use HTC Dev has been done. But at the same time it has not been done. I am in no way trying to criticize you or your tool. What you have done is great and amazing work and most definitely has and deserves a place her. This tool will only make things easier for some users if not all. I just want to keep the facts staight is all.
Related
I bought HTC RHYME and Unlocked it through www.htcdev.com
I still have s-ON but on top is writen UNLOCKED
few questions i got please HELP
1) do i need s-OFF? if its unlocked?
2) i would like to install Recovery any Recovery accept the STOCK ONE
3) is there a way to get ARABIC ROM on it through any other ROMS?
i got on my sensation and it works flawlessly it has SENSE 3.5 with arabic.
i am willing to donate 100$ if someone helps me to make it arabic. Thanx
Can you tell me how you unlocked this ?
Because on the Site htcdev.com the HTC Rhyme is not listed...
DominatingSystem said:
Can you tell me how you unlocked this ?
Because on the Site htcdev.com the HTC Rhyme is not listed...
Click to expand...
Click to collapse
Already answering ur question .. just visit the website he mentioned. And u have to get some quote by adb (all procedure explain on website while doing the procesdure) then they email u some code and u have to enter it by adb. And u r unlocked.
But the question is still there from my side too that y its not s-off?
Sent from my Dell Streak using XDA App
Ok thx,
and the answer why its not s-off are explained also on the site ^^
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
Thats good, but not perfect...i hope any developer will get a solution..^^ (Donation guaranteed)
DominatingSystem said:
Ok thx,
and the answer why its not s-off are explained also on the site ^^
Thats good, but not perfect...i hope any developer will get a solution..^^ (Donation guaranteed)
Click to expand...
Click to collapse
But suppose I also unlock my htc explorer via this site. And after I want to flash cwm recvry via rom manager. But my device is not listed in its drop down list from wich u have to select ur device before flashin.
What should I do in that case. If I flash somehow. Will mine be brickd or something
Sent from my Dell Streak using XDA App
Mhmh, i think the developer will add the Rhyme soon..
I would wait on each case...a brick is not excluded
The problem with unlocking the bootloader via HTC's site is IMHO that it's not only pointless, but you also loose warranty.
It's pointless for 2 reasons:
1. Most custom ROMs for other HTCs require the device to be S-OFF, so chances are low that the bootloader unlocking via HTC will give you any advantage in the future when it comes to installing custom ROMs.
2. If there will be any custom ROMs from the devs in the future, there surely will be a way to unlock/S-Off/root the device available before these custom ROMs will appear. This way will most likely be revertable, and you won't loose warranty.
There should be a Rhyme forum!
....so we need to vote to get one...
http://forum.xda-developers.com/showthread.php?t=1416406
I dont have this device, but i would be more than happy to do some for this device.
But without the device the stuff would be pointless
May be some donations will take me and help me getting this device
Hi ,
Wanting to get rid of 3 uk junk and flash to normal UK RUU
Do we need super CID?
My bootloader is unlocked , can't download the RUU from from the Dev section as all the slots are gone , or when it seems to work it errors out .
Has anyone got the latest UK RUU file they can share with me and can someone confirm if I need Super CID to run RUU to unbrand
Thanks in Advance
Just flash Modaco or the Virtuous roms through recovery, these are unbranded and really good.
You will need to flash a Recovery image first though.
Hi and thanks
Yes , I understand this but I want to just unbrand through RUU then re-lock my bootloader.
Do we need Super CID ?
Ok can someone remind me if I need S-Off to change the CID , playing around with ADB at the moment
If Im honest mate, no idea what you mean by CID...
But if you want a new rom, all that needs to be done is unlock bootloader, flash recovery, flash rom.
Thats all anyone has done in the dev threads, and worked fine for me (coming from a retail, unbranded unit).
You can 'lock' the bootloader again, BUT it never goes back to its true original state. This is as HTC designed their unlocking/locking process to be (and is stated in their terms when you go to their site to unlock).
Edit: OK, just read up on it. Possibly then! Depends how annoying 3 are I suppose... Probably best to ask one of the devs
Edit 2: CHeck the following, may be of help (though its for the One X)
http://forum.xda-developers.com/showthread.php?t=1594262
http://android.modaco.com/topic/353106-debrand-one-x/
Edit 3: If you're applying a flashable zip, does the CID limitiation on RUUs even come into play?
Hi thanks ,
Yea what I want to achieve is this .
My CID is HG3____001 this will need to be changed to a CID that is HTC UK specific usually HTC_____001
To find out your CID in ADB
Fastboot Getvar CID
To get to a retail version from a branded version , what usually needed to happen was this .
Unlock bootloader , change CID to 11111111 via ADB
Run the specific UK RUU.exe
Change your CID to the HTC_____001 which is the usual default for UK unbranded devices .
re-lock your bootloader and then you should receive OTA updates from HTC instead of your network supplier which can take months
I can't remember if S-off was needed to do this. I have just checked revolution site and One s is not listed , will play around tonight though and see
Thanks for the help so far
Hi, I know what CID is - coming from the Sensation.
I dont think its possible to change CID without S-OFF, you cant use advanced ADB functions with S-ON
Until revolutionary or someone else makes tool for S-OFF, we will just have to stick with HTCDev, Its not the best, but it allows to flash recovery and ROMs so its better than nothing.
Im pretty sure there will be some progress in the next few weeks, Once the phone is available worldwide
Ahh ok , thanks , yea this phone is set S- on , so S-off will be needed sooner or later
yeah, as development develops and more rights are needed from the phone, S-0FF will eventually be a MUST.
I wish it was available already, I hate the fact that HTC know i have tampered with my HBOOT and voided my warranty.
Luckily enough, if i have a problem, my provider fixes / repairs the phone, Not HTC, So i might just get off lightly
I think HTC will know if you have tampered with the phone period if they wish to look that far into it .
Unless you fry your processor where you have set it too high etc then shouldn't be a problem. If you have a hardware problem such as your screen fails , battery etc then should be fine .
As you say though , if you brought it through a retail unit then that is where it is returned so in some respects is a bit easier as they will use a third party repairer acting for HTC .
well with the sensation it was possible to return everything back to stock, Including the bootloader and S-ON..
There was no way it could be diagnosed as being tampered with, If you did it properly..
But with HTCDev. youve already submitted a code (which i assume contains serial number) so all they have to do is check whether that device matches anything on their database of tampered devices. Thats why i dislike it so much..
But i need root for most of my apps so there was no workaround for me...
I see on the One X forum S-off is under way . Can't wait to get this baby to true stock.
Just did another Google search for S-Off on the S but nothing as yet .
Hi guys!
I hope it's not a problem I opened a new thread but I haven't really found a fully answered topic to my question. (I might be blind, anyway...)
So I own a Vodafone UK Branded HTC Sensation. I am thinking to root the device. I do not want to use any custom rom, I'm happy with the official one (at the moment...) and I would only like to have "ROOT Access". So, am I right that I do not need to "S-OFF"?
In this case as I understand:
1.) I have to unlock bootloader (HTCdev)
2.) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1632553 to root the device
Is that right?
After the root had been done, will I be able to remove all the applications, boot image... pre-installed by Vodafone? (Kind of "de-brand" the device) Or will I be able to install a "EU RUU" or only the "Vodafone RUU". I'm really sorry if I'm totally wrong but I have been reading the threads for couple of weeks now and I already got absolutely confused... I appreciate any help, explanation. Thank you very much in advance!
matekaneve said:
Hi guys!
I hope it's not a problem I opened a new thread but I haven't really found a fully answered topic to my question. (I might be blind, anyway...)
So I own a Vodafone UK Branded HTC Sensation. I am thinking to root the device. I do not want to use any custom rom, I'm happy with the official one (at the moment...) and I would only like to have "ROOT Access". So, am I right that I do not need to "S-OFF"?
In this case as I understand:
1.) I have to unlock bootloader (HTCdev)
2.) Follow this guide: http://forum.xda-developers.com/showthread.php?t=1632553 to root the device
Is that right?
After the root had been done, will I be able to remove all the applications, boot image... pre-installed by Vodafone? (Kind of "de-brand" the device) Or will I be able to install a "EU RUU" or only the "Vodafone RUU". I'm really sorry if I'm totally wrong but I have been reading the threads for couple of weeks now and I already got absolutely confused... I appreciate any help, explanation. Thank you very much in advance!
Click to expand...
Click to collapse
Hi,
From having a quick look at the guide in the link you don't even need to unlock the bootloader via HTCdev. Just follow the guide. I personally unlocked my bootloader and S-off'd via revolutionary.io who did a great job of beating HTCdev to the punch within months of the sensation coming out.
Here's a "Super noob guide to unlocking bootloader and s-off" which may ease your confusion. Although for the HTC Rezound , the concept for all HTC Bootloaders is the same, Just don't follow that guide verbatim otherwise bad things may happen. :laugh:
You should be able to de-bloat ( probably the search term you want to use ) your rom after root. There's also a guide for carrier unlocking knocking around somewhere which I also did, Unlocking it from 3UK grips
Good Luck
You could have probably asked your questions in the guide thread but meh, no one died and I don't think anyone's losing sleep over this post at least you've spent some time trying to figure it out on your own before calling for help
trevd said:
Hi,
From having a quick look at the guide in the link you don't even need to unlock the bootloader via HTCdev. Just follow the guide. I personally unlocked my bootloader and S-off'd via revolutionary.io who did a great job of beating HTCdev to the punch within months of the sensation coming out.
Here's a "Super noob guide to unlocking bootloader and s-off" which may ease your confusion. Although for the HTC Rezound , the concept for all HTC Bootloaders is the same, Just don't follow that guide verbatim otherwise bad things may happen. :laugh:
You should be able to de-bloat ( probably the search term you want to use ) your rom after root. There's also a guide for carrier unlocking knocking around somewhere which I also did, Unlocking it from 3UK grips
Good Luck
You could have probably asked your questions in the guide thread but meh, no one died and I don't think anyone's losing sleep over this post at least you've spent some time trying to figure it out on your own before calling for help
Click to expand...
Click to collapse
Thank you very much for your reply! My Hboot version is 1.27. As far as I know I am unable to use the "revolutionary" method to S-OFF and unlock the bootloader. Anyway I will go for the htcdev one once I'm back from work! Thank you for your help again!
matekaneve said:
Thank you very much for your reply! My Hboot version is 1.27. As far as I know I am unable to use the "revolutionary" method to S-OFF and unlock the bootloader. Anyway I will go for the htcdev one once I'm back from work! Thank you for your help again!
Click to expand...
Click to collapse
Hi,
Please check my signature (☺ A great starting point for all new Sensation owners ☺) for a good list of guides to s-off.
I would suggest ganesh or kgs methods.
You will also need to install a custom recovery.
Check out joaquinf's guide to installing 4EXT.
malybru said:
Hi,
Please check my signature (☺ A great starting point for all new Sensation owners ☺) for a good list of guides to s-off.
I would suggest ganesh or kgs methods.
You will also need to install a custom recovery.
Check out joaquinf's guide to installing 4EXT.
Click to expand...
Click to collapse
Just an update! I managed to root my device! Now I'm a happy chappy! :victory: Thank you guys for all the help and guides! I used this guide: http://forum.xda-developers.com/showthread.php?t=1497404
I have root access, unlocked bootloader and 4ext installed. :good: I might try S-OFF another time...
Thank you again!
My apologies if this has been repeated before but i would like to just clear some things i have in my mind?
it may have been repeated but i would sincerely appreciate if someone just elaborates!
My understanding at present is:- i know root gives you more access,bootloader is a script or a code to load up os and kernel,s off gives us extended rights to some partitions,supercid makes it possible to flash any ROM irrespective of carrier and region,the firmware essentially contains the bootloader (hboot) and radio and lastly RUU is a utitlity to upgrade rom which can be region and carrier specific.
PLS correct me if m wrong?
So RUU+Supercid+SOFF can cause bricks?
which implies if at all RUU is used we need to be be on SON and CID should be 0000000?
also if i have OTA updates for a ROM that is from some other Service Provider and I am on SOFF and SUPERCID it still will brick my phone?
and lastly i have S0FF SUPERCID and Unlocked Bootloader and obvioulsy rooted
so what all on earth i should avoid doing?
You've got it the wrong way around. It goes like this: SuperCID + s-on + jb RUU = brick. Having s-off means you can run any RUU (Evita) without bricking. Other things that can cause a brick are flashing software not intended for our device (ROM/kernel/radio etc), running an RUU not intended for our device, in some cases altering the hboot has caused bricks. In some other cases running an Evita RUU has caused bricks if something goes wrong during the process. You shouldn't take an OTA unless you have the correct preceding ROM/firmware already on the device, plus you need stock recovery and I believe (not 100% sure) the correct CID. Personally, I wouldn't take an OTA on a modified device.
Sent from my Evita
Given this background if something happens and I need to go back entirely to a factory configuration what can be done?
i have always wondered does EVITA have any Application Utility (with a user friendly GUI ,terminals and prompts scare me)?
i have the all in one tool kit!! besides that?
and can flashing ROMS cause brick cause in The OP's of various ROM release threads i have read something like "brick fixed"?
and is it appropriate to use Goo Manager and the ROMS listed there?
btw after my epic failure of flashing a kernel ( now u see m really a noob) i accidentally happened to wipe my entire phone through TWRP and by mounting it i was able to get it back again that time i observed that the phone still has the bootloader but not the OS so which led to another question that is the boot loader a part of the firmware?
I know m wrong but somehow i just cant connect the dots!
excuse me for my bad English!
I really wonder at times why people like me total newbies take the risk.. but then i realize when u just have that little more control of your device and it stands out in the crowd its worth the effort and the calculated risk!
Cheers to all the developers!! :good::laugh:
timmaaa said:
You've got it the wrong way around. It goes like this: SuperCID + s-on + jb RUU = brick. Having s-off means you can run any RUU (Evita) without bricking. Other things that can cause a brick are flashing software not intended for our device (ROM/kernel/radio etc), running an RUU not intended for our device, in some cases altering the hboot has caused bricks. In some other cases running an Evita RUU has caused bricks if something goes wrong during the process. You shouldn't take an OTA unless you have the correct preceding ROM/firmware already on the device, plus you need stock recovery and I believe (not 100% sure) the correct CID. Personally, I wouldn't take an OTA on a modified device.
Sent from my Evita
Click to expand...
Click to collapse
you know what.... you are a savior and a hope for many! :good:
thanks!
so Supercid + SOFF + JB Ruu is not bricking your device (exceptional failures and human error in the process not considered)
Absolutely correct, sir.
Sent from my Evita
---------- Post added at 10:45 AM ---------- Previous post was at 10:35 AM ----------
Sonone said:
Given this background if something happens and I need to go back entirely to a factory configuration what can be done?
i have always wondered does EVITA have any Application Utility (with a user friendly GUI ,terminals and prompts scare me)?
i have the all in one tool kit!! besides that?
and can flashing ROMS cause brick cause in The OP's of various ROM release threads i have read something like "brick fixed"?
and is it appropriate to use Goo Manager and the ROMS listed there?
btw after my epic failure of flashing a kernel ( now u see m really a noob) i accidently happened to wipe my entre phone through TWRP and by mounting it i was able to get it back again that time i observed that the phone still has the bootloader but not the OS so which led to anorther question that is the boot loader a part of the firmware?
I know m worng but somehow i just cant connect the dots!
excuse me for my bad english!
I really wonder at times why people like me total newbies tkae the risk.. nut i realize when u just have that liitle more control of your device and it satnd out in the crowd its worthe the effort and the calculated risk?
Cheers to all the developers!! :good::laugh:
Click to expand...
Click to collapse
If you want to go back to a factory configuration all you need to do is run an RUU.
I think the ROM threads with the "brick fixed" would be the cm threads. There were a few builds a couple of months ago which had caused bricks but they've been fixed now.
I personally don't like or encourage the use of any automated flashing tools like Goo Manager, I simply don't trust them. Many users do use it with success though.
The bootloader/hboot is part of the firmware, this partition is unable to be wiped through recovery. So even if you do accidentally wipe everything in recovery you can always get to your bootloader and recovery.
To be honest I think it's totally worth the calculated risk. You have so much more freedom with your device, the ability to flash pretty much any ROM you want is awesome, plus you're able to access features that a stock configuration can't provide. In saying that, there is obviously a certain level of knowledge required to do this. Without that level of knowledge the risk is far higher, this is why we see many people bricking their device, because they've rushed into modifying it without doing the appropriate research first. It takes some work to learn it all, but the information is freely available and easy to access. We have a great community here, some great people with a combined pool of knowledge that can be called upon if someone gets into trouble with their phone.
Sent from my Evita
Why s-on is brick friendly since it's a safety measure?
Sent from my HTC One XL using Tapatalk 4
For the "what exactly causes the brick" my theory goes like this:
AT&T yelled at HTC that devices were ending up unlocked.
In that yelling someone decided the best way forwards was to block AT&T users using supercid 11111111 to get unlocked on HTCDev. This meant that even if a new root method was found a user with supercid still could not unlock. As a side thing it looks like they attempted to block supercid users getting future updates also.
We saw on HTCDev that they blocked supercid 11111111 for AT&T devices. It looks like as a simple oversight either by HTC or because AT&T only requested 11111111 be blocked that all other supercid variations still work. The oversight is likely because whoever decided on the block did not realize that 11111111 is only one of many supercid strings.
So now back to the side effect of attempting to block supercid users getting updates causing bricks. This issue is maybe deliberate or more likely accidental, it appears the block was not well thought through or tested before being implemented as seen by the HTCDev oversight.
I believe somewhere in the update the software checks that it is being installed on a device with the correct CID and in this portion of code ALL supercids were removed from being allowed.
There is at least one check right at the start(the update-script) that still includes the supercids as being allowed, which is why the updates starts, but later on another check in a different piece of code has had the supercids removed as valid cids. Because of this the device gets half way through the update and stops, leaving the device in a brick state.
I think whoever "designed"/made the change to remove supercids may not have understood that they had not removed the supercids from all required places to prevent bricks as we have seen. But at least they understood that there is many supercid strings and managed to block/remove them all.
Having s-off is allowing the check half way through to pass successfully. Likely because the update code doesn't bother checking CIDs if you have s-off and s-off checks were not what HTC/AT&T were looking to block at the time(s-off came later).
Why they wanted to block supercid users updating might be related to AT&T saying users that had not purchased their device from AT&T were being able to use AT&T propriety code without paying them to do so.
Silly argument but something large corp execs would get insane and illogical about.
I doubt the bricks were intentionally designed by HTC or AT&T. It is a side effect of poorly thought out blocks requested by AT&T related to blocking unlocks and blocking non AT&T users using AT&T software..
twistedddx said:
For the "what exactly causes the brick" my theory goes like this:
AT&T yelled at HTC that devices were ending up unlocked.
In that yelling someone decided the best way forwards was to block AT&T users using supercid 11111111 to get unlocked on HTCDev. This meant that even if a new root method was found a user with supercid still could not unlock. As a side thing it looks like they attempted to block supercid users getting future updates also.
We saw on HTCDev that they blocked supercid 11111111 for AT&T devices. It looks like as a simple oversight either by HTC or because AT&T only requested 11111111 be blocked that all other supercid variations still work. The oversight is likely because whoever decided on the block did not realize that 11111111 is only one of many supercid strings.
So now back to the side effect of attempting to block supercid users getting updates causing bricks. This issue is maybe deliberate or more likely accidental, it appears the block was not well thought through or tested before being implemented as seen by the HTCDev oversight.
I believe somewhere in the update the software checks that it is being installed on a device with the correct CID and in this portion of code ALL supercids were removed from being allowed.
There is at least one check right at the start(the update-script) that still includes the supercids as being allowed, which is why the updates starts, but later on another check in a different piece of code has had the supercids removed as valid cids. Because of this the device gets half way through the update and stops, leaving the device in a brick state.
I think whoever "designed"/made the change to remove supercids may not have understood that they had not removed the supercids from all required places to prevent bricks as we have seen. But at least they understood that there is many supercid strings and managed to block/remove them all.
Having s-off is allowing the check half way through to pass successfully. Likely because the update code doesn't bother checking CIDs if you have s-off and s-off checks were not what HTC/AT&T were looking to block at the time(s-off came later).
Why they wanted to block supercid users updating might be related to AT&T saying users that had not purchased their device from AT&T were being able to use AT&T propriety code without paying them to do so.
Silly argument but something large corp execs would get insane and illogical about.
I doubt the bricks were intentionally designed by HTC or AT&T. It is a side effect of poorly thought out blocks requested by AT&T related to blocking unlocks and blocking non AT&T users using AT&T software..
Click to expand...
Click to collapse
So in a way they were trying to avoid HTC devices being used on the other carrier networks and hence resorted to block such devices getting official software updates but the check for supercid occurred at a later stage of the procedure and it abruptly discontinued the entire upgrade causing bricks!
it seems reasonable although but rendering the device completely useless seems a bit harsh!
so users with supercid should stay away from RUU?
and Soff doesn't have any effect on the procedure it seems?
and u also mentioned Sir that there are multiple CID thread would you please elaborate!:angel:
The unlocking process he's talking about is the bootloader unlock, which is entirely separate from a SIM unlock. A bootloader unlock doesn't allow a non at&t SIM to be used. Basically, at&t didn't and don't want their phones to be able to have their bootloader unlocked and have custom software installed.
Users with SuperCID are totally fine to use an RUU, but they MUST have s-off first. Having s-off makes the RUU process safe.
Sent from my Evita
Sonone said:
so users with supercid should stay away from RUU?
Click to expand...
Click to collapse
Supercid + s-off is fine.
Being s-off turns off the current check for CID that is bricking devices.
11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777. 88888888. 99999999 are all valid supercids. But shhhh don't tell AT&T, as I'm sure in the next update 22222222 will get blocked and we will all move to 33333333.
This isnt about a user that bought an AT&T phone and wants to use it on Sprint USA etc. It is about a user buying a phone from Canada(or Hong Kong, Singapore, Australia etc) and importing it to USA and then switching it over to AT&T software. Or pretend for a minute AT&T made some amazing image editing app that they dont want to give out for free, but Australians users are getting it for free because they have supercid. It all seems like a knee jerk reaction to understanding supercid, how it was allowing their devices to be unlocked and a realization that overseas users might have supercid also and have AT&T software(and therefore potentially access to servers) for free.
"You told us the bootloader was locked, why are users still unlocking?!!"
It appears AT&T have told HTC to block supercid(in particular 11111111) for their devices. Exactly where blocking supercid translated to only 11111111 on HTCDev is unclear, it is likely AT&T's fault for not understanding the technical details of what exactly they were requesting.
"Well if they will likely be able to find a root exploit just block supercid 11111111(that they keep using) from HTCDev for our devices, then the problem is fixed!!!!"
And in my fictional version of the story the programmer that was told to block supercid 11111111 from being able to receive updates managed to correctly translates that request back to any supercid, but stuffed up by blocking the update too late in the update process.
Things get very pedantic in these types of cases. AT&T might have said "our propriety software must not be installed on supercid devices", so the non AT&T code starts installing but at the moment AT&T code is about to be transferred the update stops or something.
twistedddx said:
Supercid + s-off is fine.
Being s-off turns off the current check for CID that is bricking devices.
11111111, 22222222, 33333333, 44444444, 55555555, 66666666, 77777777. 88888888. 99999999 are all valid supercids. But shhhh don't tell AT&T, as I'm sure in the next update 22222222 will get blocked and we will all move to 33333333.
Click to expand...
Click to collapse
LOL like that!!
twistedddx said:
This isnt about a user that bought an AT&T phone and wants to use it on Sprint USA etc. It is about a user buying a phone from Canada(or Hong Kong, Singapore, Australia etc) and importing it to USA and then switching it over to AT&T software. Or pretend for a minute AT&T made some amazing image editing app that they dont want to give out for free, but Australians users are getting it for free because they have supercid. It all seems like a knee jerk reaction to understanding supercid, how it was allowing their devices to be unlocked and a realization that overseas users might have supercid also and have AT&T software(and therefore potentially access to servers) for free.
Click to expand...
Click to collapse
Big corporations and their big plans!
but again we cant blame them!
so having S-OFF actually has given the users a lot of freedom!
it is an important thing!
(just realized it now)
explained really well btw!
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Darkpikasso said:
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Click to expand...
Click to collapse
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
It's an at&t phone, the at&t CID is blocked by htcdev so you need to get SuperCID before being able to unlock the bootloader. Click the Everything Evita link in my signature and bookmark that thread, it's a resource thread that contains everything you'll ever need. Once you're in that thread navigate to the root section and find the 3.18 root method, this is the only method that'll work with your current firmware. Follow the instructions in that thread and then you can unlock your bootloader.
Once you have an unlocked bootloader you can install TWRP recovery which will allow you to root your stock ROM or install custom ROMs. If you need instructions on this click the How-To Guide For Beginners link in my signature, it's a thread I put together detailing some basic operations. If you have any questions feel free to ask in my Noob Friendly Q&A + General Help thread.
Sent from my One X using Tapatalk
You need to use the correct root method that corresponds to your firmware version in order to change your CID. Trying other methods you randomly Google around for is not going to work.
Use my Index thread, look under "ROOT" and find the method that matches your firmware number (3.18).
http://forum.xda-developers.com/showthread.php?t=1671237
There is not one-click method that works for firmware 3.18. Trying methods that don't match your firmware number is a waste of time.
Also, when asking for help, you need to be absolutely specific as to what you have tried, and what you haven't (including the result such as error messages, etc). If you don't give us specifics, it makes it even harder for us to help you.
Hasoon2000's all-in-one toolkit should work on 3.18. But if this is the one you tried, you haven't told us what happens when you try to use it.
To make it easier, here's the link to the 3.18 root method:
http://forum.xda-developers.com/showthread.php?t=2285086
You'll still want to bookmark the Everything Evita thread linked in my signature.
Sent from my One X using Tapatalk
Thank you everybody
When I try the all in one kit gave the error of waiting for the device, updated the adv drivers and still dosent show the CID change
In htcdev give me the MID not allowed error
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Darkpikasso said:
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Click to expand...
Click to collapse
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
ruffain said:
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Come on, you of all people shouldn't be giving attitude to this guy telling him he hasn't searched enough. You've asked me multiple questions that could have been answered if you had searched for the answer, including how to unlock your bootloader, that's kinda like the pot calling the kettle black.
It's easy for you to say unlocking the bootloader is an easy process once you've done it. The fact is that it isn't that simple for someone who is unaware that there are different methods for different firmware versions.
Sent from my One X using Tapatalk
redpoint73 said:
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
Click to expand...
Click to collapse
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Darkpikasso said:
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
Click to expand...
Click to collapse
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Roadrunner? I don't think such a method exists for this device. You can't get s-off without root, you can't get root without an unlocked bootloader, you can get an unlocked bootloader without SuperCID, the only way to get SuperCID on his firmware is to use the 3.18 root method. Hence the reason that's been stated over and over again in this thread. It's the only solution. Carrier unlocking has absolutely nothing to do with the bootloader unlock / root process.
Sent from my Evita
timmaaa said:
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Click to expand...
Click to collapse
Got it, first root and then unlock
Keep you update and thanks a lot for the help
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
timmaaa said:
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
Click to expand...
Click to collapse
Thanks everybody for the help but I can't get superCID
The htc dosent let him write and all the exploits to change it ether dosent find the device or dosent allow to write the commands
I really don't know what is the problem
I already install new drivers uninstall the ones from Samsung that I had and nothing
Not even my phone has the option to put it in charge only it has various opcitions but none of them are charge only
What do you mean by "all the exploits"? Which exploits have you tried? Did you try the 3.18 root method I gave you the link to?
Sent from my Evita
lemonfugu said:
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Click to expand...
Click to collapse
I got it....
I uninstall the drivers and install again there's were got the connection and unlocked but it says TEMPERED
Is that ok? Later in the afternoon I'm going to install custom recovery s-off and root
Yeah that's totally normal. I'd suggest you have a look at my How-To Guide For Beginners thread (link in my signature), it has some good instructions on your next steps.
Sent from my Evita
timmaaa said:
Roadrunner? I don't think such a method exists for this device.
Click to expand...
Click to collapse
Probably is referring to the Rumrunner s-off method. And yes, carrier (SIM) unlock has nothing to do with bootloader unlock and/or s-off. Probably just a coincidence that that person was able to bootloader unlock after doing SIM unlock.
Thank you very much for the help now I have it everydone unlock, custom recovery, root and s-off.
I was having problems with faceoff to s-off but nothing big
I already have install viperxl with beastmode kernel
Sent from my HTC One X using xda app-developers app