[Q] Tampered, Locked. Unable to RUU. - AT&T, Rogers HTC One X, Telstra One XL

I rooted my 1.85 device via the one click method.
I want to stay with a stock ROM, but need to get to 2.20 because the multi tasking on 1.85 is so bad. 2.20 update OTA fails. I tried to RUU to 2.20 but continually receive a low battery error (error 120 I believe) even with 100% battery level
My device currently shows Tampered & Locked.
Any advice?
**EDIT**
When I run Root Checker it shows that my device is rooted.

Trust me, you don't want to update to 2.20. Stay on 1.85, flashing roms is much easier on it. If you really do not like the multitasking I'm sure there are some roms that can fix/make it better

utkaar099 said:
Trust me, you don't want to update to 2.20. Stay on 1.85, flashing roms is much easier on it. If you really do not like the multitasking I'm sure there are some roms that can fix/make it better
Click to expand...
Click to collapse
I'm okay with installing a new ROM, but I'm concerned that the status of my phone (showing locked/tampered) will create issues when I go to unlock the bootloader.

When you unlock the bootloader you lose all your data, it sounds bad at first but in the end it's worth it

utkaar099 said:
When you unlock the bootloader you lose all your data, it sounds bad at first but in the end it's worth it
Click to expand...
Click to collapse
I'm comfortable losing all my data, as I'm a long time rooter of devices (since the G1 in fact). What I'm worried about is the state my phone is in (showing locked/tampered) and how that might impact my attempt to unlock the bootloader.
Thoughts?

pfaudere said:
What I'm worried about is the state my phone is in (showing locked/tampered) and how that might impact my attempt to unlock the bootloader.
Click to expand...
Click to collapse
Ignore it. "Tampered" just means you're rooted; "Locked" means your bootloader is locked. When you unlock it, it will read "Unlocked." It has no effect on anything; it's just a flag for the service people to know what they've got, not that they appear to care about it based on the number of people who have returned unlocked phones without any trouble.

Related

How do I prepare my phone for roms?

I need to root, unlock, and install CWM right? How exactly do I do this? I tried to locate a how to without any luck.
The dev section is filled with all the info you need to know.
Also, not trying to be a **** but saying you searched when it is obvious that you didn't will get you nowhere.
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
johnl199 said:
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
Click to expand...
Click to collapse
Some of the roms, prior to the unlock discovery, were executable as an RUU. All the updated versions require recovery which you need the bootloader unlocked to get in to. It's a painless process and there's even a 1-Click script method for those who dont want to take chances.
Will I be able to get the phone back to COMPLETELY stock should I decide to sell it in the future?
From what I know it will say relocked or tampered but maybe I'm wrong
Sent from my HTC One X using xda premium
After unlocking your phone, there will be no way to get back to 100% stock unless we can get S-OFF (which hopefully may be in the near future due to a few devices already being S-OFF).
However, you can root your device and not unlock it (1.82 and prior as of now) and still be able to revert to 100% stock as if it came right out of the box.
Most of the ROMs currently do not require an unlocked bootloader.
However, this will definitely change as we begin to see custom kernels (hopefully soon with the release of the source by HTC Dev) and more complex ROMs (such as those based on AOSP, such as CM9 and AOKP).
So in short, you can still use most of the ROMs in the dev section. Just be aware however that if you do not unlock then you cannot install CWM (limiting the number of ROM options) and also if you update past 1.82.502.3 then you cannot root (at this time, other root exploits are being explored).
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
lamenramen said:
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
Click to expand...
Click to collapse
Nope. You are thinking of SIM unlock.
Bootloader unlock lets you load custom ROMs and change recovery, that's all.

Manual Changing of CID back to AT&T & Relocking Bootloader

I did the SuperCID, then unlocked the bootloader to get the latest update 1.85 since I'm on 1.73. But I heard bad stories about worse battery life on 1.85. My battery life has been awesome on 1.73. I have no complaints about the phone.
Yet after using SuperCID and unlocking the bootloader the phone feels laggy. I'm not perceiving this either, it's clearly laggy. Particularly on start up (going into the phone after first boot).
I say hell if it ain't broke don't fix it. I'll keep my 1.73 good battery life, and hotspot mod that's good enough for me.
I'm not sure if SuperCID or unlocking the bootloader slowed my phone down but the only thing I care about is root at this point anyway.
I used a script to do SuperCID so can someone tell me the following
1. How can I change my CID back to AT&T
2. How can I relock my bootloader
3. Will relocking bootloader wipe phone again?
4. If I clockworkmod first, then change CID, then relock I should be able to restore my phone without also restoring CID and unlocked bootloader right?
Thank in advance.
EDIT: OOH Never mind: This guide was EXCELLENT: http://forum.xda-developers.com/showthread.php?t=1678308
People who answer their own questions, and also come back to their post to share the answer they found, deserve thanks.
derrickonline said:
I did the SuperCID, then unlocked the bootloader to get the latest update 1.85 since I'm on 1.73. But I heard bad stories about worse battery life on 1.85. My battery life has been awesome on 1.73. I have no complaints about the phone.
Yet after using SuperCID and unlocking the bootloader the phone feels laggy. I'm not perceiving this either, it's clearly laggy. Particularly on start up (going into the phone after first boot).
I say hell if it ain't broke don't fix it. I'll keep my 1.73 good battery life, and hotspot mod that's good enough for me.
I'm not sure if SuperCID or unlocking the bootloader slowed my phone down but the only thing I care about is root at this point anyway.
I used a script to do SuperCID so can someone tell me the following
1. How can I change my CID back to AT&T
2. How can I relock my bootloader
3. Will relocking bootloader wipe phone again?
4. If I clockworkmod first, then change CID, then relock I should be able to restore my phone without also restoring CID and unlocked bootloader right?
Thank in advance.
EDIT: OOH Never mind: This guide was EXCELLENT: http://forum.xda-developers.com/showthread.php?t=1678308
Click to expand...
Click to collapse
I get that you feel 1.73 is better and downgrading (whether I agree or not). But why bother relocking the bootloader and changing back the CID?

Avoid losing root if ATT forces 2.20 OTA update

I have an AT&T HOX. Came stock with 1.85.
I rooted it using the "redbend" method described here (http://forum.xda-developers.com/showthread.php?t=1709296)
(More or less, the pulling SIM card business wasn't part of the steps when I used it, but the root was successful).
I am using SuperSU to manage root access by apps.
I have not done anything beyond that.
Now, I understand, at some point, AT&T is going to force a 2.20 update on me.
My primary concern is to avoid losing root.
(I have enabled the "preserve root across OTA" in SuperSU, but not sure if its effective or not)
I've looked at the howto's for SuperCID, unlocking the bootloader, etc, and I'm not sure which I NEED, and which are optional, and/or what the pros/cons are of each...
I'd like to stay as close to "stock" as possible, but I want to ensure that I can keep root.
I'm still within my AT&T contract, and would really prefer to avoid bricking the phone.
I'm wondering what the recommendations are as to the minimum steps I should take to keep root in the event the OTA is forced on me?
Can I pre-empty the OTA by installing this? ( http://forum.xda-developers.com/showthread.php?t=1812459 )
If so, what is the safest method for installing it?
FWIW, I am a linux user, and I am comfortable with adb as well as the command line on the phone itself.
I have no windows systems, so any special tools I'd need other than adb I'd have to find a linux version.
I don't need "one click" methods, in fact I'd prefer to see/perform the individual steps and understand what they are doing.
unlock your bootloader using this method http://forum.xda-developers.com/showthread.php?t=1672284 if you don't you wont get root again afterwards.
Dont have to unlock to flash roms?
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
My ATT HOX is currently rooted, and I now have SuperCID. I assumed I would need to unlock my bootloader, but I havent done that yet.
Can I install this:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Megadave123 said:
This document,
http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/
Near the very bottom, suggests:
For AT&T HTC One XL and alike, if you want to install custom ROMs, you don’t have to unlock your bootloader but simply flash custom recovery in fastboot.
Is this accurate?
Click to expand...
Click to collapse
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Megadave123 said:
and then use it to install the "Stock Rooted AT&T 2.20.502.7" here?
http://forum.xda-developers.com/showthread.php?t=1812459
And if I do that, will this avoid AT&T OTA'ing me?
Click to expand...
Click to collapse
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Megadave123 said:
On a relatated note, would the SuperCID survive the OTA, allowing me to unlock the bootloader afterward, even if I hadnt done so already?
Click to expand...
Click to collapse
SuperCID survives OTA. But the 2.20 OTA has a new hboot, which fixes the hole by which kernels and radios can be flashed from recovery, so my recommendation would be not to install the OTA.
redpoint73 said:
Completely false. You cannot install custom recovery without unlocked bootloader. For the safety of your device, I'd suggest sticking with XDA, and not Googling random websites. That website obviously has incorrect information.
Click to expand...
Click to collapse
FWIW, I didnt google that site. It was linked to from an XDA post. I't didnt seem right to me, which is why I asked here
AT&T isn't going to "OTA" you by force. You have to accept the download, then accept the installation. Cancelling either of those will prevent the OTA from being installed.
If you want to update to the stock 2.20 firmware without running the OTA or RUU (and therefore keep the ability to flash kernels and radios), than yes, the ROM you linked is the method I would suggest. But you would need to unlock the bootloader, then install TWRP before you can flash the rooted 2.20. Also keep in mind there are newer (than 2.20) firmwares already posted in Development (2.23, 2.29, etc.) in similar pre-rooted form. Not to mention custom ROMs based on 2.20 or newer.
Click to expand...
Click to collapse
Ok, that is VERY good to hear.
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Megadave123 said:
BTW, thank you very much. I read somewhere that ATT could/might force the OTA, and I've been worried about losing root ever since, but not quite ready to (presumably) completely void my warranty with a bootloader unlock.
Click to expand...
Click to collapse
I think bypassing the user acceptance dialogues for the OTA install would be a violation of how Android fundamentally works. It would be a serious security issue, as it might allow rogue software to be installed on your device without your interaction. I seriously doubt AT&T would institute such a thing.
The user confirmation of the OTA might be a liability thing, too. If the performance of the device is adversely affected by the OTA (happens to some people) and the OTA was forced by AT&T without the owner having a choice, it would seem to me that AT&T has to accept the responsibility. People can claim its AT&T's fault, and demand a replacement device (since AT&T technically installed the software remotely). By making you confirm the OTA installation (and giving you the chance to opt out), you pretty much are volunteering to install the software and accept the consequences.
In theory, unlocking the bootloader voids you warranty. But more than a few folks on here have gotten warranty replacements from AT&T (after unlocking the bootloader), without issue. Sometimes in-store (within the first 30 days) without them even checking for the bootloader unlock. No guarantee that this will always be the case. But just throwing it out there. Its still up to you whether unlocking the BL is worth the risk in your own case.
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
18th.abn said:
I dont remember but isnt hoxl supported by goomanager? As long as your rooted you can install a recovery from it with a locked bootloader. I always reccomend unlocking but im pretty sure its not a total necessity to get twrp recovery
Click to expand...
Click to collapse
The hoxl is officially supported by twrp and can be downloaded from goomanager. I do not know if you can install a custom recovery without an unlocked bootloader. I would be interested to know if this can be done as well.
Sent from my Nocturnalized One XL using Forum Runner
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Is there any harm in trying it?
If I install "goo manager", and let it do its thing, and the locked bootloader prevents it from doing so, there wont be any other side effects, will there?
If I come off as a complete noob at this - its because I am..
This is my first Android phone, and I *really* want to avoid bricking it, so I want to make sure I understand as much as possible before I go
trying to do anything to it.
Also I'm still wary of unlocking, mainly because of the whole "will erase your phone" bit.
I'm not yet fully comfortable that I know how/what to fully backup all of "my" data on the phone so as to facilitate easily putting it all back.
I'll answer some q's here.
1.) you cannot flash a custom recovery from hboot with a locked bootloader
2.) you CAN dd a custom recovery with a locked bootloader. However your device will be soft-bricked.
3.) you CAN install custom ROM's via dd right from android. This is how we did it back "in the day".
4.) you "might" be able to get away with dd'ing a custom kernel with locked BL, not not sure. In fact, I'd bet it will softbrick now that I think about it.
Anyways, the SAFEST way to do it is via unlocking the bootloader and installing your roms from custom recovery.
gunnyman said:
when you try to push a recovery via fastboot with a locked bootloader it will fail due to invalid signature I don't see how goomanager would be any different.
Click to expand...
Click to collapse
Beaups pretty much already answered it. But this guy tried installing TWRP thru goomanager with a locked bootloader, and confirmed it doesn't work: http://forum.xda-developers.com/showthread.php?p=31220704#post31220704

How to restore status code to 0 from status code 2

Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.

I want to relock the boot loader. How?

I want to do this. Is there a way to do so and retain data?
gunnyman said:
I want to do this. Is there a way to do so and retain data?
Click to expand...
Click to collapse
via fastboot...
fastboot oem lock
I don't recall if it factory defaults, as I rarely lock
bootloader locked now won't boot
All I want to do is run the RUU to get it back to stock
gunnyman said:
bootloader locked now won't boot
All I want to do is run the RUU to get it back to stock
Click to expand...
Click to collapse
Download appropriate RUU from https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048 place it on SD card, rename to 2PZCIMG.zip, put SD card into phone, press & hold vol down and power button to boot into download mode and confirm RUU flashing (battery should be over 30 or something %)
[Edited for better description.]
I have twrp still installed recovery won't start and it doesn't boot
gunnyman said:
I have twrp still installed recovery won't start and it doesn't boot
Click to expand...
Click to collapse
I edited my post for better description. You should do what it says there (you need to boot to download mode).
Also relocking bootloader with twrp still installed is a no no
Ok. Thanks. I'm charging phone now I got running ruu exe sorted. Thanks for the push in the right direction
gunnyman said:
Ok. Thanks. I'm charging phone now I got running ruu exe sorted. Thanks for the push in the right direction
Click to expand...
Click to collapse
Np.. Hope you get it sorted.
(the steps I described I described are for sd card method, if there is ruu exe for your variant you should just follow instructions once you start ruu exe on your computer)
I was freaking out because I was getting USB error 170 running the RUU. Got it all sorted out and am back up and running.
gunnyman said:
I was freaking out because I was getting USB error 170 running the RUU. Got it all sorted out and am back up and running.
Click to expand...
Click to collapse
Good to hear :good:
Sorry to hijack the thread but is there any way to unlock bootloader without going through the htcdev method? I believe that the warranty is voided if i unlock my bootloader and the support will not entertain any hardware damage (not caused by me) which is why i wanted to unlock without using htcdev. Any info is appreciated, thanks!
tokenbest said:
Sorry to hijack the thread but is there any way to unlock bootloader without going through the htcdev method? I believe that the warranty is voided if i unlock my bootloader and the support will not entertain any hardware damage (not caused by me) which is why i wanted to unlock without using htcdev. Any info is appreciated, thanks!
Click to expand...
Click to collapse
There isn't at least for now. And in any case until there is s-off even if there was other way it will show as relocked and modified after you lock it again.
there's no sunshine in the sky for now, but warranty is not voided in most countries/cases anyway.
velimircek said:
There isn't at least for now. And in any case until there is s-off even if there was other way it will show as relocked and modified after you lock it again.
there's no sunshine in the sky for now, but warranty is not voided in most countries/cases anyway.
Click to expand...
Click to collapse
Thanks but sadly.. the customer support for HTC Singapore said warranty would be void after unlocking bootloader and any issues would not be covered, seriously though -_- sucks to hear that and making me hesitate on purchasing a U11 currently.
tokenbest said:
Thanks but sadly.. the customer support for HTC Singapore said warranty would be void after unlocking bootloader and any issues would not be covered, seriously though -_- sucks to hear that and making me hesitate on purchasing a U11 currently.
Click to expand...
Click to collapse
I got the same response from HTC Czech Republic: unlocking the bootloader would instantly void my warranty, plus they said that warranty-keeping bootloader unlock is possible only in that one special case for US customers, the rest of the world voids their warranty by doing so :/
Rant on the side: I truly despise not being allowed to get root privileges without voiding the warranty - it is MY device, yet I can't control the system. I want to do MY own backups, control (or inspect) the data apps save to MY phone, and control the configuration of MY system. I really hate being locked out from even such basic configurations as the hosts file is - I'm effectively barred from some aspects of web development so that advertisements can be shoved down my throat
gunnyman said:
bootloader locked now won't boot
All I want to do is run the RUU to get it back to stock
Click to expand...
Click to collapse
How did you get it to relock? i keep getting a failed messaged with the command above.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
tokenbest said:
Sorry to hijack the thread but is there any way to unlock bootloader without going through the htcdev method? I believe that the warranty is voided if i unlock my bootloader and the support will not entertain any hardware damage (not caused by me) which is why i wanted to unlock without using htcdev. Any info is appreciated, thanks!
Click to expand...
Click to collapse
Right now it's only with the 175 USD XTC2Clip with all the attachments including the power adapter - and as of my last look, it cannot factory lock the bootloader thanks to temporary S-OFF so it will show up as relocked which will void the warranty anyway. In other words, we are all out of luck for now.
And it remains to be seen if HTC actually lets us keep our warranty in the US... The warranty in the box says otherwise.
EtherealRemnant said:
Right now it's only with the 175 USD XTC2Clip with all the attachments including the power adapter - and as of my last look, it cannot factory lock the bootloader thanks to temporary S-OFF so it will show up as relocked which will void the warranty anyway. In other words, we are all out of luck for now.
And it remains to be seen if HTC actually lets us keep our warranty in the US... The warranty in the box says otherwise.
Click to expand...
Click to collapse
175.00, S-off is not that important. Like you said a relocked bootloader voids your warranty. Why are people bothering to relock bootloader especially the OP to run the RUU, it is not needed. You do mention XTC2Clip a lot in these threads. You holding stock in the company? lol
schmeggy929 said:
175.00, S-off is not that important. Like you said a relocked bootloader voids your warranty. Why are people bothering to relock bootloader especially the OP to run the RUU, it is not needed. You do mention XTC2Clip a lot in these threads. You holding stock in the company? lol
Click to expand...
Click to collapse
Hell no, I have no interest in dropping another 175 bucks, I think it's ridiculous but it is currently the only way to do a number of things with the device. I'd consider it if being able to unlock and relock the phone without HTC ever having a clue was a big deal or there was a Google edition and I needed to change the CID and MID or other things but honestly, I still have my 10 if I really need to get at something that was on that phone but not on this one (for example my Battle.net authenticator). I suppose I could always try Helium though with my desktop but I imagine that's a protected app like Google Authenticator which required root to backup and why I switched to Authy.
I mentioned the XTC2Clip because it is the only way to get S-OFF of any kind right now and to point out that even with its temp S-OFF, it still can't restore the bootloader to factory locked status. It's an important thing to point out, not everyone knows that HTC has two different locked statuses, one that proves the phone has been tampered with, and one that is factory locked. A lot of people ask to go back to stock so they can send it in for a warranty claim or a refund to go buy another device. The relocked bootloader obviously kills one or both options depending on the situation.
EtherealRemnant said:
Right now it's only with the 175 USD XTC2Clip with all the attachments including the power adapter - and as of my last look, it cannot factory lock the bootloader thanks to temporary S-OFF so it will show up as relocked which will void the warranty anyway. In other words, we are all out of luck for now.
And it remains to be seen if HTC actually lets us keep our warranty in the US... The warranty in the box says otherwise.
Click to expand...
Click to collapse
schmeggy929 said:
175.00, S-off is not that important. Like you said a relocked bootloader voids your warranty. Why are people bothering to relock bootloader especially the OP to run the RUU, it is not needed. You do mention XTC2Clip a lot in these threads. You holding stock in the company? lol
Click to expand...
Click to collapse
Does it void warranty? I returned my bootloader relocked U11 to HTC due to a scratch on the display. Was offered a refund or exchange. I had to go the refund route to swap colours ( I went from Black to Blue). Was accepted without any fuss.
Galactus said:
Does it void warranty? I returned my bootloader relocked U11 to HTC due to a scratch on the display. Was offered a refund or exchange. I had to go the refund route to swap colours ( I went from Black to Blue). Was accepted without any fuss.
Click to expand...
Click to collapse
Yeah, a lot of people are claiming unlocked bootloader voids warranty now, however US is more relaxed. Every single HTC phone I had was returned with Unlocked Bootloader and S-off, never had a problem. Other countries are more strict I guess. I can understand not knowing the return policy and people relock for that reason(for returns) but I see many relocking for flashing RUU or firmware. This is not needed or even should be done. I'm a RUU flasher with each update, so I know no problems arise. This has been the case for the last 8,9 or 10 phones lol.

Categories

Resources