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
Related
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
First i apologize if this is was already posted,
I just got the 1.84 ota update installed. And i just want to check the h boot . And its says Tampered and Locked.
My issue is i never unlocked the bootloader or tried to root this phone. Bought phone new from T-mobile.
Is this normal for stock phone to say tampered?
If it is not then i will want to root since its tampered, but is there a way to root for 1.84 .
blkfire50 said:
First i apologize if this is was already posted,
I just got the 1.84 ota update installed. And i just want to check the h boot . And its says Tampered and Locked.
My issue is i never unlocked the bootloader or tried to root this phone. Bought phone new from T-mobile.
Is this normal for stock phone to say tampered?
If it is not then i will want to root since its tampered, but is there a way to root for 1.84 .
Click to expand...
Click to collapse
Go exchange it if you're plan to use stock. If not go root it
Sent from my HTC VLE_U using Tapatalk 2
You could exchange it, but if you plan to root instead, there's 2 sticky threads in development specifically devoted to rooting and they work for the 1.84 update as well. However, there's also a "one click" rooting option in the One X (AT&T version) development section that was recently updated and MIGHT work on the 1.84 update without having to unlock the bootloader through HTC. The last one click for the AT&T X worked for the S as well before the 1.84 update.
Sent from my H1S using XDA Premium.
Thanks ,
Last thing is it normal to see tampered on a completely stock device thats never been rooted
Absolutely not.
Sent from my H1S using XDA Premium.
Mine was listed as "tampered". I didn't think much of it as I was planning on unlocking/rooting anyway.
blkfire50 said:
First i apologize if this is was already posted,
I just got the 1.84 ota update installed. And i just want to check the h boot . And its says Tampered and Locked.
My issue is i never unlocked the bootloader or tried to root this phone. Bought phone new from T-mobile.
Is this normal for stock phone to say tampered?
If it is not then i will want to root since its tampered, but is there a way to root for 1.84 .
Click to expand...
Click to collapse
I havent followed newest info for some time, but I noticed that at htcdev you can get HTC One S kernel code.
Have this made us anywhere closer to unlocking without htcdev to keep warranty?
I want to root, but I dont want to avoid any kind of warranty (technical service guys here are assholes)
Just do it with HTC dev say to them if anything does happen that I got my token id and everything to unlock bootloader but thought about it and in the end didn't do it they can't say u did then
Sent from my HTC One S using xda premium
k1llacanon said:
Just do it with HTC dev say to them if anything does happen that I got my token id and everything to unlock bootloader but thought about it and in the end didn't do it they can't say u did then
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
If you unlock the phone, it will be flagged AFAIK. Even if you don't do anything and relock it, it will be flagged as "relocked". If you flash anything, it will be flagged as "tampered" as well.
I am new to the whole android modding scene but from my understanding, you can NOT get rid of any of those flags without S-OFF which the community hasn't been able to achieve yet.
I've tried every bootloader unlock and I keep getting that error. Any thoughts? The supposed non htcdev bootloader unlocks still take me to htcdev and the same error. I'm rooted
Sent from my HTC One X using xda app-developers app
hodgie26 said:
I've tried every bootloader unlock and I keep getting that error. Any thoughts? The supposed non htcdev bootloader unlocks still take me to htcdev and the same error. I'm rooted
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
please read more before trying to unlock bootloader...
ethantarheels123 said:
please read more before trying to unlock bootloader...
Click to expand...
Click to collapse
Please read my post before telling me to read. I know that it won't work strictly through htcdev. I'm trying the bootloader unlocks in android development and am still getting that error. Do you have some information I need to know about?
Sent from my HTC One X using xda app-developers app
i had the same error. did you solve yours? if youdid, pls tell me...
Which carrier are you on?
Sent from my HTC One X using xda app-developers app
alpersami said:
i had the same error. did you solve yours? if youdid, pls tell me...
Click to expand...
Click to collapse
I managed to unlock the bootloader for my AT&T One X. These are the steps that I took.I think that the problem I had was that my root wasn't done completely. SuperSU was installed, but whenever I tried to use an app that required root, it would ask if I was rooted.
1. I factory reset my phone through the bootloader. (For me, this removed root).
2. I uninstalled the HTC drivers on my PC, then reinstalled.
3. Re-root, using this root.
3a. USB debugging enabled3b. Disable fastboot.3c. Make sure HTC sync isn't running.3d. If using desktop, plug USB into the back of the computer.4. Check and make sure root is working properly. You can go into SuperSU and it should update SU binaries.
5. Use this tool to unlock the bootloader.
That is what worked for me. I took every precaution I could think of and it worked. Good luck!
hodgie26 said:
I've tried every bootloader unlock and I keep getting that error. Any thoughts? The supposed non htcdev bootloader unlocks still take me to htcdev and the same error. I'm rooted
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sounds like a CID or MID error.
Sent from my Inspire 4G using Tapatalk 2
I'm running 3.18 on my att one x and having zero luck unlocking my phone via htcdev... keep getting error 160. I also cant find any one click roots for 3.18?? Any special steps I should know about?
That's because htcdev blocks AT&T phones. You need to get SuperCID first. You can't have looked very hard, because there is a 3.18 root method in the General section of our phone's forum. Also, you probably need to do some reading, because you should have known these facts before attempting to alter your phone.
Sent from my Evita
bugzeem6s said:
I'm running 3.18 on my att one x and having zero luck unlocking my phone via htcdev... keep getting error 160. I also cant find any one click roots for 3.18?? Any special steps I should know about?
Click to expand...
Click to collapse
You can't find any 1-click roots for 3.18, because there are none.
The "special steps" you should follow, are to first start looking at my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Find the root method for 3.18. Then you will need to SuperCID. Then, and only then, will you be able to unlock the bootlaoder. Read read read.
Has anybody had this issue with the HTC One M4
To anybody that knows about these forums,
I have been trying to unlock the bootloader for the new HTC One from Verizon, I went to the HTcdev website, and I follow all the instructions step by step, I paste the code into the box, then it tells me some code error 160 mid not allowed, so now I have no clue what that means, I check out the websites and they all have similar instructions on unlocking the bootloader, but they all worked and none of them got the error 160 mid not allowed, I check out the error forums, and they are just as frustrating because they get detailed into what the reason in the code is, but considering that the need for the code to be all 1111 doesn't help when the phone won't even unlock through the htcdev site.
Has anyone else come up against this particular error and if so how was it resolved? Any help is greatly appreciated:fingers-crossed:
You're I'm the wrong forum buddy, this is the HTC One XL forum.
Sent from my Evita
Hi,
I'm having issues trying to unlock the bootloader for my One S. I know that you have to go to htcdev to unlock it but even after going through all the steps my bootloader will stay locked.
Just to be clear, I've managed to go through all steps and get my phone to ask whether I want to unlock the bootloader, after clicking yes my phone just turns off. When I go into the bootloader it says locked.
I should also mention that I bought this phone off eBay from a seller who had rooted, s-off and unlocked the bootloader previously. The seller unrooted, s-on and locked the bootloader when they decided to sell the phone. They also mentioned that they installed an official HTC European Rom when rooted.
Any help would be appreciated as I would like to root my phone.
Thanks
Sent from my HTC One S using xda app-developers app
Can anyone help? I was hoping after a week or so that someone would be able to give some suggestions. I've searched through the forums and not found anyone that has the same issue as me. I'm gussing this is a rare problem that no-one has encountered or been able to solve.
Sent from my HTC One S using xda app-developers app
:laugh: