Database Develop

[Q] Removing **TAMPERED** and **UNLOCKED**

I was just wondering, I have the HTC ONE/ M7 and I was trying to root it but was never successful. I unlocked it with the HTCDev website and installed GOO on my phone but thats about as far as I got. Now my phone shows **TAMPERED** and **UNLOCKED** in the HBOOT menu, I was just curious as to how I would get those to go away.
THANKS!

I believe you have to wait for s-off so you can downgrade hboot to remove that message.
Flashing back the stock firmware (RUU) will remove the tampered but it will always say relocked if you locked the bootloader again.

What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
Sent from my HTC One using xda app-developers app

Tampered can be removed when you flash the official RUU.
Relocked cant be as of now. And I have no hopes for it to happen in device's life cycle as well.

So how would I flash it? Is there a general way or is it device specific?
Sent from my HTC One using xda app-developers app

Take a look through this:
http://forum.xda-developers.com/showthread.php?t=2265618

When you rooted your phone it added tampered and unlocked in bootloader menu.
If you want to take them out you will have to unroot your phone or wait for s-off (it will fully unlock the phone)
I didn't have the tampered message on my rooted OneX,it must be something new as well as the red warning in booting the phone that it's a dev phone that must not be sold

There is a thread with RUU archive for each device. Check for specific RUU for your specific carrier make or model.
But if you install RUU you will have phone that is as good as stock phone. You will lose root and will have to re-root it.
Dont bother with it unless you have to go back to factory condition.
There are also zipped versions of stock ROMs available so you can try those if you have CWM or TWRP installed successfully.
You dont really need to remove that tampered / unlocked status. It does not hinder your phone in any way. You have already lost your warranty and even if you relock your bootloader and remove Tampered message by flashing factory RUU, your phone will still show RELOCKED message. So point going back unless as I said you must have factory condition phone.

Hi~!
So does this mean the factory will always know that our phones are rooted with S ON?

TrueYears said:
Hi~!
So does this mean the factory will always know that our phones are rooted with S ON?
Click to expand...
Click to collapse
Yes HTC will know for sure the phone has been tampered with and unless s-off is achieved for the masses which does not involve taking the phone apart then it will always say tampered, unlocked, relocked.

Oh, okay, thank you, my phone has vibrating problems, with the intensity, in some hits, the vibrating just keeps going slowly fading in. I read somewhere that 1.29 fixes this but its isnt out around my region yet and I dont want to flash this 1.29 stock rom to find out its a hardware issue and lose my warranty

Spacky03 said:
What does S-off mean? Sorry I'm really new to this, I know it's probably a dumb question. Is going back to the factory firmware a long process?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Security-Off if what it officially means. Means you can write to the bootloader and mod things

[Q] need to downgrade hboot from 1.55 to get my s-off back

Can anyone point me in the right direction to either get s-off for HBOOT 1.55 or a tutorial or video on how to downgrade back to a version of HBOOT that I can run S-OFF on. I did the Sprint OTA 4.3 and need a little help.

I'm sorry to say it, but you can't s-off when on 1.55, nor can you downgrade. I found that out for myself.

I also did the OTA 4.3 upgrade with S-off on Hboot 1.44.
I now am on Hboot 1.55 and can unlock/lock my bootloader using the unlock code.bin I saved from HTCdev.
I cant believe I thought S-off was the same as unlocked bootloader....
Now im stuck with 4.3 BOO

How did you guys lose your s-off? I did the 4.3 OTA when I had s-off already, and I didn't lose mine
Sent from my HTCONE using XDA Premium 4 mobile app

I was downgrading and upgrading and some things went wrong. I was stuck in recovery. Through the process of getting back to stock I guess I messed up.
At least I heard that the Devs are working on 1.55 : )
I found this but, its For ATT, and I don't really know if it would work.
http://forum.xda-developers.com/showthread.php?t=2394155
So if anyone knows if a nandroid backup will restore everything, even hboot 1.55 to 1.44, I would love a link so I can download yours since I upgraded to windows 8.1 with a fresh install before backing up mine...
Also, if I have S-ON, which I cant tell except for the fact that I cant downgrade, why can I lock/unlock my bootloader?

doragu said:
I was downgrading and upgrading and some things went wrong. I was stuck in recovery. Through the process of getting back to stock I guess I messed up.
At least I heard that the Devs are working on 1.55 : )
I found this but, its For ATT, and I don't really know if it would work.
http://forum.xda-developers.com/showthread.php?t=2394155
So if anyone knows if a nandroid backup will restore everything, even hboot 1.55 to 1.44, I would love a link so I can download yours since I upgraded to windows 8.1 with a fresh install before backing up mine...
Also, if I have S-ON, which I cant tell except for the fact that I cant downgrade, why can I lock/unlock my bootloader?
Click to expand...
Click to collapse
No a nandroid does not contain the hboot. Sorry but you'll have to wait till some dev manages to s-off the newest hboot. You don't seem to know what s-off really means so don't worry, I'm sure you'll never need it.
Anyway here's a quote for you to read
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Click to expand...
Click to collapse

Thank you for better explaining that to me.
But why am I still allowed to flash TWRP recovery, and OMJ's Deodexed 3.04...ROM if the security is suppose to block it?
Guess I should of read more. SGS2 was too simple

doragu said:
Thank you for better explaining that to me.
But why am I still allowed to flash TWRP recovery, and OMJ's Deodexed 3.04...ROM if the security is suppose to block it?
Guess I should of read more. SGS2 was too simple
Click to expand...
Click to collapse
Flashing recovery and ROM, doesn't need you to be s-off, but flashing a firmware does
Sent from my HTCONE using Tapatalk 4

elvisypi said:
Flashing recovery and ROM, doesn't need you to be s-off, but flashing a firmware does
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
Okay so as I understand it. When a developer says need to be s-off to flash a rom they do mean it ? or is it some special firmware you are talking about. I had s-off and lost it because I didn't do my research. I'm very disgusted with my self now i'm on H-Boot 1.55 and stuck... also I heard the devs are working on this h-boot to get s-off. Can anyone tell me if this is true?
I was able to flash the viperone rom with S-On without any issues. well may be couple at&t apps which i erased but other than that-Lokks okay for now.

intramorph said:
Okay so as I understand it. When a developer says need to be s-off to flash a rom they do mean it ? or is it some special firmware you are talking about. I had s-off and lost it because I didn't do my research. I'm very disgusted with my self now i'm on H-Boot 1.55 and stuck... also I heard the devs are working on this h-boot to get s-off. Can anyone tell me if this is true?
I was able to flash the viperone rom with S-On without any issues. well may be couple at&t apps which i erased but other than that-Lokks okay for now.
Click to expand...
Click to collapse
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.

tkoreaper said:
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
Click to expand...
Click to collapse
I appreciate that however I had s-off and now can't get it back due to my been n00b. So yeah it's a little disappointing
Does this mean I won't be able to get the 4.3 OTA?

tkoreaper said:
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
Click to expand...
Click to collapse
Worst pile of misinformation ever. You do not need s-off to flash a boot animation, however you do need it for important things like downgrading your hboot.
Sent from my HTCONE using xda app-developers app

tkoreaper said:
You're really not missing much by not being S-OFF. As far as ROMs are concerned, it's mainly for custom boot screens.
Click to expand...
Click to collapse
And the ability to S-Off to go back to stock unrooted the properly official way. That's all I use it for lol

Konfuzion said:
Worst pile of misinformation ever. You do not need s-off to flash a boot animation, however you do need it for important things like downgrading your hboot.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Oh really? Are you sure about that? Explain to me how we never had custom boot animations until we achieved S-OFF and also explain to me why everything I've read on the topic has been wrong. There was no reason for you to be rude about it. A quick Google search tells you all that you need to know: http://android-revolution-hd.blogspot.com/2013/06/do-we-really-need-s-off.html
With S-OFF you can:
Flash in fastboot original parts of the firmware like: Trust Zone (tz.img), Resource Power Manager (rpm.img), Advanced Digital Signal Processor (adsp.img), bootloader (hboot.img), Radio Config Data (rcdata.img), Splash Screen and others, very often device specific firmware like Consumer IR (cir.img) for the television remote controller in HTC One.
Flash in fastboot custom parts of the firmware above, however I've never seen in my life anyone compiling custom rpm.img or tz.img. I've seen custom bootloaders and Splash Screens only. You can also flash modified radio.img but there is rarely anyone out there who does this.
Use more advanced fastboot commands, for example you can change the CID (Carrier ID) of your device or even MID (Model ID). And this one is the most important one in the context of this article.
Reset the Tampered flag, so your device does not show up as "Relocked" if you relock your bootloader.
Click to expand...
Click to collapse
You can also refer yourself to a thread that I started back when we got S-OFF... Take a look at one of the first things mentioned: http://forum.xda-developers.com/showthread.php?t=2314705

tkoreaper said:
Oh really? Are you sure about that? Explain to me how we never had custom boot animations until we achieved S-OFF and also explain to me why everything I've read on the topic has been wrong. There was no reason for you to be rude about it. A quick Google search tells you all that you need to know: http://android-revolution-hd.blogspot.com/2013/06/do-we-really-need-s-off.html
You can also refer yourself to a thread that I started back when we got S-OFF... Take a look at one of the first things mentioned: http://forum.xda-developers.com/showthread.php?t=2314705
Click to expand...
Click to collapse
Le sigh.....
Maybe I slightly misread your post. You said main thing is "boot screens" you mean splash screens maybe? If so yes you do need s-off, however you don't need s-off to flash custom boot animations. Most importantly flashing a splash screen is not the main reason someone would need s-off, and I am sure the many users of this forum who have flashed a 4.3 based GSM Rom on their CDMA device and don't have s-off would agree.
Last but not least I was in no shape or form rude, even if you did mean to flash splash screens it's still total misinformation that isn't the most important reason to have s-off, it's to save your butt when your in a pickle.
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Le sigh.....
Maybe I slightly misread your post. You said main thing is "boot screens" you mean splash screens maybe? If so yes you do need s-off, however you don't need s-off to flash custom boot animations. Most importantly flashing a splash screen is not the main reason someone would need s-off, and I am sure the many users of this forum who have flashed a 4.3 based GSM Rom on their CDMA device and don't have s-off would agree.
Last but not least I was in no shape or form rude, even if you did mean to flash splash screens it's still total misinformation that isn't the most important reason to have s-off, it's to save your butt when your in a pickle.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
And that's why I said "as far as ROMs are concerned..."
Of course S-OFF is used for more important things, but the person's question was about S-OFF in regards to ROMs. And what is a ROM going to do with S-OFF? I answered that question.

tkoreaper said:
And that's why I said "as far as ROMs are concerned..."
Of course S-OFF is used for more important things, but the person's question was about S-OFF in regards to ROMs. And what is a ROM going to do with S-OFF? I answered that question.
Click to expand...
Click to collapse
Ok, sounds fair. Just a misunderstanding
Sent from my HTCONE using xda app-developers app

Konfuzion said:
Ok, sounds fair. Just a misunderstanding
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Okay guys I didn't need to start a war. Is there anything I can do or anyone I can pay to get s-off If I'm on hboot 1.55 at&t?
I really need my s-off back ^^

intramorph said:
Okay guys I didn't need to start a war. Is there anything I can do or anyone I can pay to get s-off If I'm on hboot 1.55 at&t?
I really need my s-off back ^^
Click to expand...
Click to collapse
As of now there it's nothing you can do, this might change in the future.
Sent from my HTCONE using xda app-developers app

Kernel
Konfuzion said:
As of now there it's nothing you can do, this might change in the future.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
So with s-on can I still flash kernel and radio??? My biggest concern is that I won't be able to flash the kernel I want and the radio also when there's an official update how can I get that with custom rom I stalled? I rly miss having s-off rly does anyone know of a paid site who can do that for me?

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.

HTC__001 OTA Problem

So I'm no stranger to running RUU's on my device as the amount of times I have changed from Sense to GPE is ridiculous. However I have been thinking about getting the M8 so went back to stock sense, locked everything back up and put S-On. When I turn the phone on everything is fine as normal, and it starts receiving ota's, however it wont update past 4.3. Does anyone know if there are any issues with the HTC ota's for HTC__001? It also won't go past with super cid, yet when I unlock and S-Off again I can convert it to H3G__001(not what it should be but I am with the 3 network) it updates absolutely fine to sense 6, 4.4.2.
If anyone knows anything that might shed some light it would be most appreciated.
Thanks.

v28 said:
So I'm no stranger to running RUU's on my device as the amount of times I have changed from Sense to GPE is ridiculous. However I have been thinking about getting the M8 so went back to stock sense, locked everything back up and put S-On. When I turn the phone on everything is fine as normal, and it starts receiving ota's, however it wont update past 4.3. Does anyone know if there are any issues with the HTC ota's for HTC__001? It also won't go past with super cid, yet when I unlock and S-Off again I can convert it to H3G__001(not what it should be but I am with the 3 network) it updates absolutely fine to sense 6, 4.4.2.
If anyone knows anything that might shed some light it would be most appreciated.
Thanks.
Click to expand...
Click to collapse
That is very strange, got to be something to do with the HTC Servers, however, are you trying to update with super cid or with HTC__001 ? I ask as I e noticed that super cid isn't in any of the android info txt files for the 401 updates, I've returned to stock a few times, and never had any problems, but I always start from the 401 kitkat ruu which is 4.19.401.9

Thanks for the reply, I've used both Cid's in the past and both have updated to sense 6 no problem. The only reason I go back to such an early RUU is to S-On as after 1.28 if you try and S-On your phone becomes a paperweight.
Possibly a server thing I guess, but thanks again.
Sent from my Nexus 7 using XDA Free mobile app

Has anyone else in the UK on HTC__001 had this problem recently?

v28 said:
Thanks for the reply, I've used both Cid's in the past and both have updated to sense 6 no problem. The only reason I go back to such an early RUU is to S-On as after 1.28 if you try and S-On your phone becomes a paperweight.
Possibly a server thing I guess, but thanks again.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
no it doesn't become a brick, unless your using a modified firmware and then you should never s-on, what happens is after HBOOT 1.55 I think it is which will be 3.62.401.XX, if you s-on past that then you get the ***TAMPERED*** flag back.

Ahh ok thanks for that, always good to learn something new.

[Q] M8: S-On, Unlocked and want to get back to Stock

Hello, I seem to have got myself into a fix and need to reach out to the M8 community for assistance. I purchased a lightly used HTC One M8 that appeared to be in near mint condition. The phone was unrooted, locked and S-On. Although, it did have the Harmen Kardon rom installed and it is not the HK model, which I found odd but nothing more. I verified that the phone could be added to the Sprint Network so all seemed good.
I immediately set about rooting it. I have owned a number of Galaxy phones and considered myself rather adept at rooting, loading new ROMs, updating firmware and troubleshooting in general. I would occasionally soft brick but I'd always fine a way out.
Rooting the HTC was just different enough that I skipped one critical step without realizing it an now I am stuck for the first time ever.
I used the HTC Dev site and the HTC All-In-One tool to unlock, root and install TWRP 2.8. Two things that I did not do, S-OFF and back-up my stock system image just in case. Now, while I have Viper 4.3.0 installed and running fine, and I can switch to at least one other ROM (Bare Bones 2.1), I seem to have no path to get back to a pure stock ROM if I need to do so. And that bothers me. =)
It seems from what I have read that using an RUU would be the easiest route however, that seems to be impossible from the S-ON position. I have tried Sunshine, but it refuses to work; giving errors something along the lines of it does not like my ROM load stock or something closer to stock. Which is why I tried Bare Bones. I looked at Firewater but it seems to have issues and is not really supported anymore. I have tried various command line scripts via miniADB but still nothing.
My understanding is that if I could get S-OFF, I could install the RUU and return to stock. I even tried flashing a stock nandroid BU but that did not work either.
I suppose I should not complain, it's not bricked and it has a cool ROM installed and I can activate it but I just hate that I made such a blunder and that I can't figure out how to fix it.
Any thoughts out there? Let me know if you need additional info. This is what my bootloader is showing.
Thanks in advance!
Software status: Modified
Unlocked
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
Radio-1.08.20.8916
OpenDSP-v46.2.2-00564-M8974_FP.0811
OS-
eMMC-boot 2048MB
Dec 2 2014,14:00:10.0
Running
ViperOneM8 4.3.0
Updated 1st March 2015

IgnatzMaus said:
Hello, I seem to have got myself into a fix and need to reach out to the M8 community for assistance. I purchased a lightly used HTC One M8 that appeared to be in near mint condition. The phone was unrooted, locked and S-On. Although, it did have the Harmen Kardon rom installed and it is not the HK model, which I found odd but nothing more. I verified that the phone could be added to the Sprint Network so all seemed good.
I immediately set about rooting it. I have owned a number of Galaxy phones and considered myself rather adept at rooting, loading new ROMs, updating firmware and troubleshooting in general. I would occasionally soft brick but I'd always fine a way out.
Rooting the HTC was just different enough that I skipped one critical step without realizing it an now I am stuck for the first time ever.
I used the HTC Dev site and the HTC All-In-One tool to unlock, root and install TWRP 2.8. Two things that I did not do, S-OFF and back-up my stock system image just in case. Now, while I have Viper 4.3.0 installed and running fine, and I can switch to at least one other ROM (Bare Bones 2.1), I seem to have no path to get back to a pure stock ROM if I need to do so. And that bothers me. =)
It seems from what I have read that using an RUU would be the easiest route however, that seems to be impossible from the S-ON position. I have tried Sunshine, but it refuses to work; giving errors something along the lines of it does not like my ROM load stock or something closer to stock. Which is why I tried Bare Bones. I looked at Firewater but it seems to have issues and is not really supported anymore. I have tried various command line scripts via miniADB but still nothing.
My understanding is that if I could get S-OFF, I could install the RUU and return to stock. I even tried flashing a stock nandroid BU but that did not work either.
I suppose I should not complain, it's not bricked and it has a cool ROM installed and I can activate it but I just hate that I made such a blunder and that I can't figure out how to fix it.
Any thoughts out there? Let me know if you need additional info. This is what my bootloader is showing.
Thanks in advance!
Software status: Modified
Unlocked
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
Radio-1.08.20.8916
OpenDSP-v46.2.2-00564-M8974_FP.0811
OS-
eMMC-boot 2048MB
Dec 2 2014,14:00:10.0
Running
ViperOneM8 4.3.0
Updated 1st March 2015
Click to expand...
Click to collapse
Relock bootloader then run ruu will restore back to stock or just flash a stock rooted rom prolly easier
Sent from 27.5244° N, 99.4906° W

joshuadub said:
Relock bootloader then run ruu will restore back to stock or just flash a stock rooted rom prolly easier
Sent from 27.5244° N, 99.4906° W
Click to expand...
Click to collapse
From what I have read, relocking the bootloader with custom recovery, ROM or kernel will result in the phone not booting. Is that true? I am nervous about doing that and still not being able to successfully restore stock with an RUU. Though, again from what I have read, I should be able to re-unlock and put things back.
Every guide I am seeing says that getting back to stock is really only possible with S-Off and that there is no way to get to S-Off from Unlocked. So, I am feeling that I am out of luck.

IgnatzMaus said:
From what I have read, relocking the bootloader with custom recovery, ROM or kernel will result in the phone not booting. Is that true? I am nervous about doing that and still not being able to successfully restore stock with an RUU. Though, again from what I have read, I should be able to re-unlock and put things back.
Every guide I am seeing says that getting back to stock is really only possible with S-Off and that there is no way to get to S-Off from Unlocked. So, I am feeling that I am out of luck.
Click to expand...
Click to collapse
The phone will still boot. Also, S-off is not necessary to get your phone back to stock. The entire point of a RUU would be lost if it only worked when S-off.