Database Develop

[Q] Returning HTC one to HTC with tampered?

Hi Guys
I'm wondering if any one knows if HTC kick up a stink and tell me my warranty is void...etc and not repair/replace a phone for having the tampered sign on the bootloader? Everything else looks stock.
What's happened was my phone developed a sound problem(can't make calls any more, sound won't work, no microphone- I tried flashing numerous ROMs/ backups no effect) and I'm going to have to return it for either repair (if possible) or replacement.
I originally had s-off, rooted, unlocked bootloader, twrp. Unfortunately to get back to stock I had to use a nandroid back up and firmware from the latest Australian OTA as no RUU appears to exist for unbranded Australian HTC ones.
So with the help of some awesome people I was able to get my phone back to current firmware and software, but I needed to downgrade the Hboot back to 1.44. I then relocked the bootloader with revone and S-on.
Only thing left was to reflashed the firmware to bring this back to Hboot 1.54, so I left no traces, which work but now I've got a tampered sign...... bugger
So this leads me back to my initial question; will HTC knock my phone back on account of having a tampered sign on the bootloader?
Is there any things I can say I did that did trip the tampered sign without admitting to do things that void the warranty?
If not I guess I'm in for a wait till some awesome individual works out how to get S-off again.
Cheers

How to preserve S-OFF before sending to service

Hi.
My ONE has some camera focus issue. Macros and close objects can be focused fine, but can't focus farther objects.
I want to send my device to service,
Additionally, I've updated to hboot 1.54 and ARHD20.1, device has SuperCID and S-OFF.
I want to install stock 4.2.2 software before sending my device, but it's S-OFFed and I want it to stay that way
My questions:
1. Can I safely downgrade to hboot 1.44, relock bootloader and revert CID to HTC_001?
2. What are the chances, that service will update my hboot to newest version?
3. Is there any chance that they will not notice that device is S-OFFed ?
Thanks in advance

mat02 said:
Hi.
My ONE has some camera focus issue. Macros and close objects can be focused fine, but can't focus farther objects.
I want to send my device to service,
Additionally, I've updated to hboot 1.54 and ARHD20.1, device has SuperCID and S-OFF.
I want to install stock 4.2.2 software before sending my device, but it's S-OFFed and I want it to stay that way
My questions:
1. Can I safely downgrade to hboot 1.44, relock bootloader and revert CID to HTC_001?
2. What are the chances, that service will update my hboot to newest version?
3. Is there any chance that they will not notice that device is S-OFFed ?
Thanks in advance
Click to expand...
Click to collapse
1. yes, you can safely downgrade with s-off. a simple way to revert everything to stock would be to flash a RUU.
2. chances are very low in my opinion. there's a bigger risk that they'll maybe send you a new device with hboot already updatet to 1.54.
3. in my opinion they'll not notice this, and even if they do, they can't say for sure that the device was not delivered with s-off already before you got it.. so s-off should not decline your warranty of an hardware issue by necessity
cheers

mat02 said:
Hi.
My ONE has some camera focus issue. Macros and close objects can be focused fine, but can't focus farther objects.
I want to send my device to service,
Additionally, I've updated to hboot 1.54 and ARHD20.1, device has SuperCID and S-OFF.
I want to install stock 4.2.2 software before sending my device, but it's S-OFFed and I want it to stay that way
My questions:
1. Can I safely downgrade to hboot 1.44, relock bootloader and revert CID to HTC_001?
2. What are the chances, that service will update my hboot to newest version?
3. Is there any chance that they will not notice that device is S-OFFed ?
Thanks in advance
Click to expand...
Click to collapse
Unlocking the bootloader, rooting, s-off does not necessarily invalidate warranty. If the error is due to physical defect during manufacture it doesnt uner the sale of goods act 1979. You will probably have to remind HTC/your provider of this. I sent in my device and it has been repaired, with unlocked bootloader, custom rom etc and was, eventually, repaired under warranty. The HTC warning whilst unlocking the bootloader via their website uses the word MAY invalidate your warranty for this reason. My repair was due to physical defect. I would say there is no chance they wont notice S-OFF. I dont know if they will flash 1.44 bootloader. I requested this but have yet to receive my One back. It should be returned today and I will advise, however they may flash 1.44 for me as they decided to replace the motherboard, presumably because they damaged it whilst attempting numerous repair attempts. So they may refuse you a 1.44 flash, whilst allowing mine.

Thanks guys
Personally, I don't think that Regenersis (HTC's service in Poland) will be so generous to offer me a new device
I will revert everything to stock and then I will see what happens after it returns from service.

zaphodbeeb said:
Unlocking the bootloader, rooting, s-off does not necessarily invalidate warranty. If the error is due to physical defect during manufacture it doesnt uner the sale of goods act 1979. You will probably have to remind HTC/your provider of this. I sent in my device and it has been repaired, with unlocked bootloader, custom rom etc and was, eventually, repaired under warranty. The HTC warning whilst unlocking the bootloader via their website uses the word MAY invalidate your warranty for this reason. My repair was due to physical defect. I would say there is no chance they wont notice S-OFF. I dont know if they will flash 1.44 bootloader. I requested this but have yet to receive my One back. It should be returned today and I will advise, however they may flash 1.44 for me as they decided to replace the motherboard, presumably because they damaged it whilst attempting numerous repair attempts. So they may refuse you a 1.44 flash, whilst allowing mine.
Click to expand...
Click to collapse
Hi, as promised heres an update. The repaired phone had 1.54 flashed. I think this may only be due to the fact that it is an EE supplied phone and this is (I think) is their preference. There may be a different set of rules if you have a mobile from a different network, or you purchased a sim free (any network) mobile. HTC may have more flexibility then.

[Q] Do HTC know if your phone is shipped S-on or S-off?

Reason I ask is because everyone here recommends you leave your phone S-off when returning to stock. My phone is a carrier based phone (O2-UK)
I figured that all phones under 02-UK are shipped as s-on (from experience only, I worked with 02 and only had a few HTC phones where I checked and they were S-on)
My phone has to be sent back for repair. At present it is S-off with locked boot loader and completely stock Rom. I can easily go back to S-on if needed so this is out of curiosity

stovie_steve said:
Reason I ask is because everyone here recommends you leave your phone S-off when returning to stock. My phone is a carrier based phone (O2-UK)
I figured that all phones under 02-UK are shipped as s-on (from experience only, I worked with 02 and only had a few HTC phones where I checked and they were S-on)
My phone has to be sent back for repair. At present it is S-off with locked boot loader and completely stock Rom. I can easily go back to S-on if needed so this is out of curiosity
Click to expand...
Click to collapse
it's getting harder to get s-off (no phones ship with s-off)
that's why everyone recommends leaving it s-off until the last possible second

Yeah I know that as well
The issue is if I go s on for repairs now on hboot 1.56 I will get a **TAMPER DETECTED** message and need to unlock via HTC dev again
If I NEED s on I can downgrade the hboot to 1.44, install an earlier 1.29.xxx.x Rom and return to S-on and accept OTA's til latest version
So it's either send it off now as is and hope for the best or just suck it up and go back to s-on
Sent from my HTC One using xda app-developers app

T-MOUS S-Off on newest hboot 1.57.0000(what I did)

Let me start off with I think I got lucky. Try this at your own risk. I locked my bootloader and turned my security back on for a TMOUS warranty exchange for the dreaded purple tint in camera. I received my replacement only to find out that in fluorescent lighting the replacement HTC ONE M7 had a greenish tint but only under fluorescent lighting. So I am getting another replacement sent for free. This is where my troubles begin. I decided to unlock my bootloader for my original phone again and root it so I can set everything up again for daily use. I got through all those steps fairly easy. FYI: original phone is on newest TMOUS OTA_M7_UL_K44_SENSE60_MR_TMOUS_5.14.531.1_R-4.19.531.10_release_373019xng22l97gj5szmwv. I then relocked the phone and tried to flash RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.zip in order to achieve s-off again but to no success. Hboot 1.57.000 with S-ON wasn't having any of it I guess.
I unlocked bootloader and relocked bootloader several times trying several different methods to no success. Oh, my recovery was TWRP 2.7.0.0. At some point I realized that if I was going to return this phone I needed to get s-off again to remove tampered flag and actually lock phone instead of relock. I happened to come across a stock rom that I decided to install in hopes of accomplishing S-off. Stock 3.24.531.3 T-Mobile.zip was the rom. Long story. I know. So here is what I did;
Unlocked bootloader
Flashed TWRP and gained root using WinDroid Universal HTC Toolkit
Installed Stock 3.24.531.3 T-Mobile.zip ROM via TWRP
Phone would not fully boot past HTC ONE Animation screen
powered down and powered back on into bootloader
relocked bootloader and rebooted bootloader
unlocked bootloader again
Phone now booted completely into the stock rom I flashed
Proceeded to use firewater for S-off
Didn't work first time
Powered down phone by holding power button and rebooted normally
Tried firewater again and to my luck the SOB worked and I am S-Off again on newest HTC One TMOUS with an older Stock 3.24.531.3 T-Mobile rom
I'm sorry if I have no links to anything I mentioned but I am new to this so I don't really know how to link to other stuff I found on the site. Thanks to all the great people whose tools and rom I used to achieve S-off again.

Prior to doing those steps firewater would not get past the first chugging stage.

If you got the chugging message you were always going to be able to s off it. Firewater isn't worried about the hboot so much as the version of your cpu as to whether the exploit will work on it
Sent from my HTC One using XDA Premium 4 mobile app

It would get to the chugging and sit there for bit then kick the phone back to root command. It didn't matter how many times I tried it would always do the same thing at the same spot. I would then have to reboot the phone and try again but no success. I'm just sharing what I did and worked for me. Clearly the exploit didn't want to work before I did the steps I took. I wouldn't have spent almost 30 hours of reading and trying to fix the problem I caused otherwise. Maybe it was a fluke or dumb luck. I don't know.

Where can I find this stock rom?

Nevermind this did not work.

[Q] Sending M7 back to repair (Purple Camera)

Hi All
I am currently in a bit of a predicament, i bought a second hand one m7 and i foolishly unlocked the bootloader and proceeded to install TWRP on the phone
After spending hours trying to S-OFF my HBOOT 1.57 with nearly every method that was posted on the internet i decided to give up. It was only then i realised that my M7 has the purple camera problem and now seeing that it still has warranty, i want to return it to get it fixed.
Except it has the tampered and unlocked flags and im concerned that they might refuse my warranty claim. Can anyone with past experience provide some insight on what will happen
The phone is running a carrier branded firmware and has no RUU.

Some times they refuse to repair it. Sometimes they accept it. Depends on your location and the service you are sending it in.
As for my opinion I tell you that you are safe if you are sending it locked and s-on and tampered flag gone. If you have some money you can s-off it with sunshine http://theroot.ninja/

I´ve send HTC One M7 to official HTC Service center for my region (Czech Republic) with the same problem- Purple photos.
The phone was Unlocked and S-On.
They changed me my One M7 for new HTC One M8,becasue they haven´t got substitute parts for One M7.

cyrusct82 said:
Some times they refuse to repair it. Sometimes they accept it. Depends on your location and the service you are sending it in.
As for my opinion I tell you that you are safe if you are sending it locked and s-on and tampered flag gone. If you have some money you can s-off it with sunshine http://theroot.ninja/
Click to expand...
Click to collapse
So i decided to send it back today in its current state. Relocking the bootloader would just make things even more suss since it would say "relocked" and would imply that i tried to cover things up
When i sent it in i turned on fast boot within the power menu and i set a pattern lock so it will force my carrier's service team to wipe the device. Speaking with one of the devs of SunShine he told me that flashing a RUU removes the tampered flag
Hoping for the best