Related
I am waiting a version of revolutionary to support 1.27.0000. So........when we'll stop waiting ?
Sent from my HTC Sensation Z710e using xda premium
razvanwin95 said:
I am waiting a version of revolutionary to support 1.27.0000. So........when we'll stop waiting ?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Hi,
Check THIS
Good luck.
I'm waiting as well, as I don't want to use the HTCDev tool and loose the warranty
Edenprime said:
I'm waiting as well, as I don't want to use the HTCDev tool and loose the warranty
Click to expand...
Click to collapse
Hi, you could TRY this : http://www.xda-developers.com/android/unlock-virtually-any-htc-bootloader-without-voiding-warranty/ Don't know, if it works.
kHinsch said:
Hi, you could TRY this : http://www.xda-developers.com/android/unlock-virtually-any-htc-bootloader-without-voiding-warranty/ Don't know, if it works.
Click to expand...
Click to collapse
I just posted in that thread offering to test it on the HTC Sensation 4G eMMC and simonsimons34 ,which is the developer of the utility, posted back saying that it is not working for eMMC right now and that he will have to do some more work on it to get it to work wit eMMC.
Edenprime said:
I'm waiting as well, as I don't want to use the HTCDev tool and loose the warranty
Click to expand...
Click to collapse
I don't know where all the hype about losing warranty came from, but you do not lose the warranty if you do the HTCDev unlock. Only if you cause damage to the hardware (by overclocking or messing it up really badly) will they not repair it.
FnH84 said:
I don't know where all the hype about losing warranty came from, but you do not lose the warranty if you do the HTCDev unlock. Only if you cause damage to the hardware (by overclocking or messing it up really badly) will they not repair it.
Click to expand...
Click to collapse
I think the fear is that if a part died inside the phone and it was through no fault of your own then HTC could say you caused it through rooting and flashing custom roms and kernels. If your CPU packed in and you sent it back for warranty repair they could say you caused it through overclocking. How would you prove otherwise?
Sent from my Sensation using Tapatalk 2
cjm1979 said:
I think the fear is that if a part died inside the phone and it was through no fault of your own then HTC could say you caused it through rooting and flashing custom roms and kernels. If your CPU packed in and you sent it back for warranty repair they could say you caused it through overclocking. How would you prove otherwise?
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
Easily; I haven't flashed a custom rom, kernel nor have I overclocked. And even if you did do that, you can always go back to stock rom and claim all you've done is unlock and never touched it further. They can't prove you wrong either. My point, however, is that doing the unlock alone, will not void your warranty.
FnH84 said:
Easily; I haven't flashed a custom rom, kernel nor have I overclocked. And even if you did do that, you can always go back to stock rom and claim all you've done is unlock and never touched it further. They can't prove you wrong either. My point, however, is that doing the unlock alone, will not void your warranty.
Click to expand...
Click to collapse
The real point is that if you use the HTC Dev method to unlock your bootloader. HTC then has a record of you unlocking your device. They then have the option to play the "Well you unlocked your bootloader, so we are declining your service request as te unlocking could have caused your problem". Then they would point to the disclaimer posted on the HTC Dev website about this could void your warranty. So you see if you use the HTC Dev method to unlock your bootloader you have as 50/50 shot of HTC fixing or replacing your device under warranty.
But if you do not use HTC Dev unlock your bootloader, but another method like Revolutionary, Joupunubear S-off, or the Universal S-off HTC has no record off you unlockig your bootloader. So as long as you return your device to a locked state and have the stock ROM and stock recovery installed on your device when you send it in for repair or replacement, HTC cannot play that card.
T-Macgnolia said:
The real point is that if you use the HTC Dev method to unlock your bootloader. HTC then has a record of you unlocking your device. They then have the option to play the "Well you unlocked your bootloader, so we are declining your service request as te unlocking could have caused your problem". Then they would point to the disclaimer posted on the HTC Dev website about this could void your warranty. So you see if you use the HTC Dev method to unlock your bootloader you have as 50/50 shot of HTC fixing or replacing your device under warranty.
But if you do not use HTC Dev unlock your bootloader, but another method like Revolutionary, Joupunubear S-off, or the Universal S-off HTC has no record off you unlockig your bootloader. So as long as you return your device to a locked state and have the stock ROM and stock recovery installed on your device when you send it in for repair or replacement, HTC cannot play that card.
Click to expand...
Click to collapse
Yes, I know all this. But saying that the unlock will def void your warranty is completely wrong. That was my point. Also, you can find several members on this board confirming they got their hardware-related issues fixed under the warranty even after doing the unlock. Of course it's good that we now have an alternative (altho he jupunutbear's way will absolutely void the warranty), but just saying the whole "you'll lose the warranty for sure if you do that" is a lil insane.
You can always unroot. It only voids the warranty if you send back a rooted phone
Sent from my Sensation 4G using xda premium
hairplayer said:
You can always unroot. It only voids the warranty if you send back a rooted phone
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
And if the phone died before you could unroot? They could easily say that you have caused it and how would you prove you haven't
Sent From My HTC Sensation Using Tapatalk 2.
Any news about revolutionary and hboot 1.27?
T-Macgnolia said:
The real point is that if you use the HTC Dev method to unlock your bootloader. HTC then has a record of you unlocking your device
Click to expand...
Click to collapse
No, they don't. They have a record that an unlock token was generated. They have no way to prove that you used it.
Rin said:
Any news about revolutionary and hboot 1.27?
Click to expand...
Click to collapse
Nope. Use JPBear.
I'm afraid of losing the warranty by using htcdev
Then you'll have to wait.
Hi,
Would it be possible to unlock the bootloader without going thru HTCDev?
I found this thread regarding a universal HTC unlocker here: http://forum.xda-developers.com/showpost.php?p=24324567
Would this work for the One XL?
HTC Dev site does not show One X, Select “All other supported models” if you cannot find your phone in this list
Has anyone done this with the One X
Pumpiron579 said:
HTC Dev site does not show One X, Select “All other supported models” if you cannot find your phone in this list
Has anyone done this with the One X
Click to expand...
Click to collapse
This will likely work, but my question was about unlocking the bootloader without using HTCDev.
This is even more important now, as reports are that HTC is denying warranty if the bootloader is unlocked via their site.
GameGod72 said:
This will likely work, but my question was about unlocking the bootloader without using HTCDev.
This is even more important now, as reports are that HTC is denying warranty if the bootloader is unlocked via their site.
Click to expand...
Click to collapse
I know, I didn't want to start a thread asking that. was just wondering since it is not listed. I wouldn't use that yet, seems like within a week, we will have s-off and more
GameGod72 said:
Hi,
Would it be possible to unlock the bootloader without going thru HTCDev?
I found this thread regarding a universal HTC unlocker here: http://forum.xda-developers.com/showpost.php?p=24324567
Would this work for the One XL?
Click to expand...
Click to collapse
Tried the universal HTC unlocker and it didn't work. Nothing wrong with my phone either after it failed either.
danada said:
Tried the universal HTC unlocker and it didn't work. Nothing wrong with my phone either after it failed either.
Click to expand...
Click to collapse
Bummer. Thanks for trying though.
Hopefully the superb devs on board will figure out a way to do this.
I think it's very possible using the same method, it just needs to be adjusted for the new partition layout of the newer HTC devices.
everything i have read about HTCDev unlocker is that if you return the phone for warranty work with a custom ROM loaded, they will deny it.
BUT, if you have the bootloader unlocked and running the stock rom (return to stock before sending it in), they will process the warranty work as usual.
I still want to find a way around HTCDev, but, just letting you know what i have read
buddy17 said:
everything i have read about HTCDev unlocker is that if you return the phone for warranty work with a custom ROM loaded, they will deny it.
BUT, if you have the bootloader unlocked and running the stock rom (return to stock before sending it in), they will process the warranty work as usual.
Click to expand...
Click to collapse
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
On a previous device I'd owned, after S-OFF they found a way to get rid of the device specific "TAMPERED" logo in the bootloader. I suspect there would be a way to do so on this device as well.
I can't remember which device it was, though...
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
Its probably a combination of the device being registered for unlock on HTCDev and something on the device.
I'm pretty sure, sooner or later, the devs will figure out a way to return the device to a "clean" state. All the more reason I would love for a way to get this done without going thru official channels.
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
cause of illegal software,
Look,
We are contacting you concerning the HTC One X which you returned to us due to there being a yellow tint on the display. As you are aware we sent the handset to the HTC service centre as it was not possible to have it classed as a DOA (dead on arrival), due to the bootloader being unlocked and illegal software having been installed. The HTC service has confirmed that illegal software has been installed on the handset at some time by yourself resulting in the warranty being invalidated. Simply unlocking and relocking the bootloader would not have invalidated the warranty.
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
When you flash custom software it trips a switch that displays "Tampered" on the HBOOT screen, whether or not you flash stock back on and relock the bootloader.
redpoint73 said:
This person had warranty service denied, despite the fact that he flashed the stock ROM before sending it in:
http://forum.xda-developers.com/showthread.php?t=1631466
Apparently, they have some way of knowing a custom ROM was flashed, even if its not on there when you send it in. Makes me wonder, even if an alternate method to unlock the bootloader (without HTC Unlock) is developed, will they still know you loaded a custom ROM in the past, and refuse warranty service?
Click to expand...
Click to collapse
Actually read the posts though. The guy didn't send it to HTC.
HTC will still service the device, even after an unlock.
OK, on topic... I just looked through the HTCdev process for the first time. It seems that we should start by comparing device identifier tokens and unlock files, right?
Perhaps there is a pattern to them or we can figure out how to generate one from the other? Maybe the device identifier token has nothing to do with the unlock file apart from HTC wanting to record a unique identifier of the phone?
Has anybody tried using an unlock file from a different user's phone (of the same make/model)? That would be a huge break-through if it was that easy!
I would think somebody would have tried this, but up until now, nobody seemed to have a problem following HTC's process to get their bootloader unlocked.
Thanks,
Billy
Pumpiron579 said:
cause of illegal software,
Look,
We are contacting you concerning the HTC One X which you returned to us due to there being a yellow tint on the display. As you are aware we sent the handset to the HTC service centre as it was not possible to have it classed as a DOA (dead on arrival), due to the bootloader being unlocked and illegal software having been installed. The HTC service has confirmed that illegal software has been installed on the handset at some time by yourself resulting in the warranty being invalidated. Simply unlocking and relocking the bootloader would not have invalidated the warranty.
Click to expand...
Click to collapse
If you read the whole chat conversation, the tech was instructed to call it "illegal" software. Doesn't mean it was in fact illegal.
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
ughhh i cant believe htc is being gay
i guess im not going to buy one and wait for a gs3
Im sure someone will make a software hack or a hardware one like the SGSII.
JeepFreak said:
OK, on topic... I just looked through the HTCdev process for the first time. It seems that we should start by comparing device identifier tokens and unlock files, right?
Perhaps there is a pattern to them or we can figure out how to generate one from the other? Maybe the device identifier token has nothing to do with the unlock file apart from HTC wanting to record a unique identifier of the phone?
Has anybody tried using an unlock file from a different user's phone (of the same make/model)? That would be a huge break-through if it was that easy!
I would think somebody would have tried this, but up until now, nobody seemed to have a problem following HTC's process to get their bootloader unlocked.
Thanks,
Billy
Click to expand...
Click to collapse
Maybe nobody wants to be on topic? I guess I'll give this a try next week when I get my phone =\
Billy
Hi guys im new getting my one x from ma bell, in a few days. Im coming from an amaze, amaze forums.
You guys need to understand, htc WILL know if anything was "tampered" with.
Most software bares a timestamps, or something similar that will let them know when and what the phone was flashed with. So even if you reflash, its going to show a timestamp of sorts.
Htc put the disclaimer of warranty denial to give them an option im sure.
I returned several phones rooted, bricked to T-Mobile, and they never said anything. Its like a car, the manufacturer can void your warranty for any "mods" you do....
I hope every one here gets some patience, and not worry about rooting, bootloader unlock , bloatware.
For now it is what it is... and it's only been
... a day???
We will get this ***** unlocked, romed and kick some ass... just gonna take time... and from the looks of it we have some brilliant devs here! .
Be patient and give it some time guys, check out the amaze forums and see what happens when people start whining about stuff going to slow or not happening ( not calling any one a whiner, so chill)... the devs start disappearing.
Ok im done... probably not the right place for intros but ah well!!!
And remember
.its just a gdam phone!
.
Sent from my DROIDX using xda premium
Hey guys, I just got the awesome One S and looking to root it asap. Is there a root method that doesn't give you the TAMPERED notice in case I need to replace the phone?
Sent from my HTC VLE_U using xda premium
NO,
You need to flash stock image, bootloader will stay unlocked. That should not be an issue.
The stock images are floating around sub-forum, maybe just do a search/google. Or someone will give you a link
Hmm so basically what you're saying is that I can return/replace the phone as long as I flash back to stock even if the bootloader is unlocked? I want to be sure before I go flash happy on it.
Sent from my HTC VLE_U using xda premium
nothing is for sure
but htc allows bootloader unlock, would think if it is a hardware issue, it wouldn't be a problem
never count on it though
No doubt, I figured as much too. Thanks rugmankc, I'll wait a little longer then.
Sent from my HTC VLE_U using xda premium
What about the tampered message?
Sent from my One S.
xflatlinex said:
What about the tampered message?
Sent from my One S.
Click to expand...
Click to collapse
The tampering message comes up no matter what. No matter if your boot loader is unlocked. It's the unlock unlock bootloadet message parts that you need to worry about. If I'm not mistaken there a relock command code to relock it. Just fellow the unlock bootloader directions but at the end change the unlock command to the relock command.
cbetso said:
The tampering message comes up no matter what. No matter if your boot loader is unlocked. It's the unlock unlock bootloadet message parts that you need to worry about. If I'm not mistaken there a relock command code to relock it. Just fellow the unlock bootloader directions but at the end change the unlock command to the relock command.
Click to expand...
Click to collapse
But from what I've read, even if you relock it, it still says "Relocked" as opposed to "Locked". Is that correct?
Don't know
yeah i think i'll wait until there's a work around for this.
twosixths said:
But from what I've read, even if you relock it, it still says "Relocked" as opposed to "Locked". Is that correct?
Click to expand...
Click to collapse
yeah, i wanted to claim warrenty on mine but when i relocked it said "relocked"
still waiting for someone to come up with a solution though
Most insurance company cover water damage now so you could soak that bad boy and pay the deductibles lol.
Sent from the One.
Moved To Q&A
Please post questions in the Q&A section
You can get rid of the ***TAMPERED*** message if you need to return to HTC
I tried this myself yesterday...just for my own piece of mind
Flash your phone back to recovery.img
Relock your bootloader
Run the RUU for your phone
I'm waiting my self for a complete tool to fix the tampered and relocked sign
Sent from my HTC VLE_U using xda premium
I have a stock, rooted, bootloader locked One X. I want the new update due to all of the speed and bug improvements. However, I don't want to lose root, or the ability to flash roms if I ever wanted to. I also do not wish to void the warranty due to my bad luck with phones in the past. Now two questions:
Can I supercid and get an unlock token without HTC voiding my warranty? Possibly with http://forum.xda-developers.com/showthread.php?t=1732980 ?
Second, would that token be valid after RUU'ing to the 2.20 update if I ever chose to void my warranty and unlock the bootloader?
I would like to thank anyone who replies for their time, and although I have researched quite a bit, I would like to clarify with everyone before taking the plunge.
You're going to void the warranty if you unlock the bootloader. Their is no way around that, well except for sometimes you can relock the boot loader then they would still service it. Kinda like jail breaking and unjailbreaking iPhone except its harder
McMichael96 said:
You're going to void the warranty if you unlock the bootloader. Their is no way around that, well except for sometimes you can relock the boot loader then they would style service it. Kinda like jail breaking and unjailbreaking iPhone accept its harder
Click to expand...
Click to collapse
This is more about keeping my options open. I'm not planning on unlocking the bootloader unless I have to. I'm just trying to retain the method of doing so if I ever wanted/needed to while enjoying the latest update. Sorry for not stating my intentions clearly.
Lightfall said:
I have a stock, rooted, bootloader locked One X. I want the new update due to all of the speed and bug improvements. However, I don't want to lose root, or the ability to flash roms if I ever wanted to. I also do not wish to void the warranty due to my bad luck with phones in the past. Now two questions:
Can I supercid and get an unlock token without HTC voiding my warranty? Possibly with http://forum.xda-developers.com/showthread.php?t=1732980 ?
Second, would that token be valid after RUU'ing to the 2.20 update if I ever chose to void my warranty and unlock the bootloader?
I would like to thank anyone who replies for their time, and although I have researched quite a bit, I would like to clarify with everyone before taking the plunge.
Click to expand...
Click to collapse
Ok 1. If you have supercid you already have altered your stock settings. So even if you use a spoof cid method if you ever have to return it guess what... you have to enter your information lol. Unless you change it back to your original super cid before hand HTC could in theory void your warranty. RUUing does not remove supercid it must be changed back manually. In all reality they have to "legally" tell you that they "can" void your warranty. I havent seen them void a warranty just because one had an unlocked bootloader. As long as the phone can be recovered by them you should be ok.
The screen on my first HOX got cracked, I re-locked the bootloader and RUU'd back to stock ROM ( left supercid on it) filed my claim with asurion Got a replacement next day, sent old one back no issues. Remember when you re lock that is displayed you cant change it to say locked as we dont have s-off. However I tracked my old phones return HTC recieved it back roughly 4 days after I mailed it off and asurion did their thing. It has been over a month now and havent heard anything about them not honoring the return. See people dont understand that even if you have insurance, warranty etc HTC can at anytime still according to their legal statements not honor a returned phone or etc. So if HTC doesn't honor it asurion will be adding a hefty fee to the next months bill lol. But like I said before as long as they can recover it I havent heard of anyone having warranty, insurance issues.
2. Yes once you get your unlock token with supercid it is valid no matter what firmware you use. However you must always keep the supercid after unlocking because if you change back to your original CID the unlock token you received wit supercid will fail to flash!
3. My suggestion. Follow threads here to get supercid, Unlock your bootloader, then update, re unlock, flash super user.
U do or do not have superuser permission? U can get your unlockbincode from HTC. They have a disclaimer when doing this. "May void your warranty" it says. However ONLY if u have done this before update, u should be able to unlock after update. So Unlock bootloader from htc before upgrade, then use unlockbincode, root after. NO GUARANTEE ON WARRANTY regardless.
Sent from my One X using xda app-developers app
subarudroid said:
U do or do not have superuser permission? U can get your unlockbincode from HTC. They have a disclaimer when doing this. "May void your warranty" it says. However ONLY if u have done this before update, u should be able to unlock after update. So Unlock bootloader from htc before upgrade, then use unlockbincode, root after. NO GUARANTEE ON WARRANTY regardless.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I DO have superuser permission. If I were to use the unlock method that does not involve htcdev, http://forum.xda-developers.com/showthread.php?t=1732980 , they wouldn't have any idea and if I never unlocked then they would have no way of knowing I had an unlock code. This is just in case I decide to unlock later after the update.
Lightfall said:
I DO have superuser permission. If I were to use the unlock method that does not involve htcdev, http://forum.xda-developers.com/showthread.php?t=1732980 , they wouldn't have any idea and if I never unlocked then they would have no way of knowing I had an unlock code. This is just in case I decide to unlock later after the update.
Click to expand...
Click to collapse
but they would unless you manually went back in and removed supercid. This method will give you supercid which would then tell HTC you altered your phone lol.
eraste said:
Ok 1. If you have supercid you already have altered your stock settings. So even if you use a spoof cid method if you ever have to return it guess what... you have to enter your information lol. Unless you change it back to your original super cid before hand HTC could in theory void your warranty. RUUing does not remove supercid it must be changed back manually. In all reality they have to "legally" tell you that they "can" void your warranty. I havent seen them void a warranty just because one had an unlocked bootloader. As long as the phone can be recovered by them you should be ok.
The screen on my first HOX got cracked, I re-locked the bootloader and RUU'd back to stock ROM ( left supercid on it) filed my claim with asurion Got a replacement next day, sent old one back no issues. Remember when you re lock that is displayed you cant change it to say locked as we dont have s-off. However I tracked my old phones return HTC recieved it back roughly 4 days after I mailed it off and asurion did their thing. It has been over a month now and havent heard anything about them not honoring the return. See people dont understand that even if you have insurance, warranty etc HTC can at anytime still according to their legal statements not honor a returned phone or etc. So if HTC doesn't honor it asurion will be adding a hefty fee to the next months bill lol. But like I said before as long as they can recover it I havent heard of anyone having warranty, insurance issues.
2. Yes once you get your unlock token with supercid it is valid no matter what firmware you use. However you must always keep the supercid after unlocking because if you change back to your original CID the unlock token you received wit supercid will fail to flash!
3. My suggestion. Follow threads here to get supercid, Unlock your bootloader, then update, re unlock, flash super user.
Click to expand...
Click to collapse
So the modified supercid file will stick even after a full RUU? This is why I'm checking with you guys because I've heard otherwise so it's hard to tell what's right.
Lightfall said:
So the modified supercid file will stick even after a full RUU? This is why I'm checking with you guys because I've heard otherwise so it's hard to tell what's right.
Click to expand...
Click to collapse
yes once you have supercid the "current" firmware builds do not overwrite it. They may later release a build that does but 2.20 does not.
eraste said:
yes once you have supercid the "current" firmware builds do not overwrite it. They may later release a build that does but 2.20 does not.
Click to expand...
Click to collapse
So because supercid sticks after the update, and because I would need bootloader unlock to modify it to stock, my whole evil plan has been foiled then. Darn... And you're saying bootloader unlock would probably only cause issues on a software related warranty return?
Lightfall said:
So because supercid sticks after the update, and because I would need bootloader unlock to modify it to stock, my whole evil plan has been foiled then. Darn... And you're saying bootloader unlock would probably only cause issues on a software related warranty return?
Click to expand...
Click to collapse
Not necessarily. You can always relock and RUU back to stock, and as long as they can "recover" the phone they shouldn't have a problem with it. Even if the HOX gets official bootloader unlock support from HTC they still give this warning. Right now there is no official bootloader unlock support. All the exploits to unlock the bootloader are just that an exploit hack lol. We arent suppose to be able to unlock them right now. However thats ATT's fault not HTC's. I guess its a 50/50 deal if you get someone who wants to be a prick that day if you have to return it then probably voided warranty. If you get someone cool probably ok. Its hard to say as I havent seen them void a warranty just for a unlocked bootloader. But now if you have unlocked then screw the phone up so bad they cant even fix it thats a different story lol.
eraste said:
Not necessarily. You can always relock and RUU back to stock, and as long as they can "recover" the phone they shouldn't have a problem with it. Even if the HOX gets official bootloader unlock support from HTC they still give this warning. Right now there is no official bootloader unlock support. All the exploits to unlock the bootloader are just that an exploit hack lol. We arent suppose to be able to unlock them right now. However thats ATT's fault not HTC's. I guess its a 50/50 deal if you get someone who wants to be a prick that day if you have to return it then probably voided warranty. If you get someone cool probably ok. Its hard to say as I havent seen them void a warranty just for a unlocked bootloader. But now if you have unlocked then screw the phone up so bad they cant even fix it thats a different story lol.
Click to expand...
Click to collapse
I used to have a captivate before this phone and I'm used to flashing one ROM after another. You telling me to just unlock my One X is like telling a former heroine addict to shoot some up for their birthday. You're not making this easy for me lol.
Lightfall said:
I used to have a captivate before this phone and I'm used to flashing one ROM after another. You telling me to just unlock my One X is like telling a former heroine addict to shoot some up for their birthday. You're not making this easy for me lol.
Click to expand...
Click to collapse
lol
Before anyone sets the hounds on me, I ask this question with a massive grain of salt. I had to send my original HOXL back to ATT (warranty) and my new one is on JB. I'm assuming that they reset the CID and relocked the BL when they installed JB on this unit and then packaged it to be sent out as a refurb.
Since it is tampered and locked, would the only way to unlock this be to go on a wild goose hunt and find the person that owned this device last and get the unlock code bin file from them?
I would try to go onto HTCdev and type in my token identifier but I have the feeling that ATT would have reset the CID when they reflashed their official JB.
Thoughts? Should I give up hope? lol
nhshah7 said:
Before anyone sets the hounds on me, I ask this question with a massive grain of salt. I had to send my original HOXL back to ATT (warranty) and my new one is on JB. I'm assuming that they reset the CID and relocked the BL when they installed JB on this unit and then packaged it to be sent out as a refurb.
Since it is tampered and locked, would the only way to unlock this be to go on a wild goose hunt and find the person that owned this device last and get the unlock code bin file from them?
I would try to go onto HTCdev and type in my token identifier but I have the feeling that ATT would have reset the CID when they reflashed their official JB.
Thoughts? Should I give up hope? lol
Click to expand...
Click to collapse
If you can somehow get the unlock code bin then you should be OK. However, I doubt you will get that. It is weird that they sent you a phone that was void by warranty though.
Any who, good luck.
Sent from my Carbon-ize Evita using xda-developers app
nhshah7 said:
Before anyone sets the hounds on me, I ask this question with a massive grain of salt. I had to send my original HOXL back to ATT (warranty) and my new one is on JB. I'm assuming that they reset the CID and relocked the BL when they installed JB on this unit and then packaged it to be sent out as a refurb.
Since it is tampered and locked, would the only way to unlock this be to go on a wild goose hunt and find the person that owned this device last and get the unlock code bin file from them?
I would try to go onto HTCdev and type in my token identifier but I have the feeling that ATT would have reset the CID when they reflashed their official JB.
Thoughts? Should I give up hope? lol
Click to expand...
Click to collapse
Can't you just go to HTC dev and get another
Sent from my Elemental Venomized S-off HTC One XL
If they put write protection on your phone you will not be able to hex edit to unlock. Check to see if you can issue commands in adb first. I hate to see anyone brick.
Sent from my HTC One X using xda premium
What Rom exactactly and hboot are you on now. They either updated you to a non rootable version or you will still be able to get bootloader unlocked . Previous owners has no relevance to the process .
Sent from my HTC One X using xda premium
DESERT.TECH said:
What Rom exactactly and hboot are you on now. They either updated you to a non rootable version or you will still be able to get bootloader unlocked . Previous owners has no relevance to the process .
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
well if he had that unlock_code.bin, could he possibly still unlock the bootloader? it was tampered with, so SOMETHING happened
Ya he originally was rooted and unlocked so the tampered will stay there even if you ruu unless you change it with being s off. I'm thinking that if they would of pushed newest update to your phn it would have bricked it. Just check your version and as long as its not the lastest go about unlocking /rooting as you would normally. If its the newest version its write protected so it just won't work, it wouldn't brick phone
Sent from my HTC One X using xda premium
It's a phone I got from att as a warranty replacement that came loaded with jelly bean. I knew I couldn't unlock it but I was searching for a glimmer of hope lol. Thanks guys!
Sent from my HTC One X using xda premium