Database Develop

[Q] HELP!

bricked my htc one trying to flash an ruu and computer gliched. can get into fast boot and it displays *tampered* *relocked* and *security warning*.
tried to re-up the ruu and says 12 signatures failed or something. any help would be much apriciated. and i cannot connect with adb because i was trying to get rid of cm10 and for some reason i cannot connect to adb with cm10. now when i reboot phone just goes right into bootloader/fastboot. tried to flash a recovery did not work. PLEASE HELP!
thanks in advance.

bk73w said:
bricked my htc one trying to flash an ruu and computer gliched. can get into fast boot and it displays *tampered* *relocked* and *security warning*.
tried to re-up the ruu and says 12 signatures failed or something. any help would be much apriciated. and i cannot connect with adb because i was trying to get rid of cm10 and for some reason i cannot connect to adb with cm10. now when i reboot phone just goes right into bootloader/fastboot. tried to flash a recovery did not work. PLEASE HELP!
thanks in advance.
Click to expand...
Click to collapse
do you have s-off? you can only flash a RUU with s-off...

How exactly did the computer glitch? Calm down, if you can get into the bootloader which I assume you can (as you can see the tampered etc tags) then it's still salvageable. As the person above asked, do you have s-off?

postfatal said:
How exactly did the computer glitch? Calm down, if you can get into the bootloader which I assume you can (as you can see the tampered etc tags) then it's still salvageable. As the person above asked, do you have s-off?
Click to expand...
Click to collapse
nope still got it to work though. was very shocked. bootloader worked, was locked, and s-on. could not do ruu so i found a stock rom i ran it once got a security issue then manually typed it in something like fastboot flash image XXX.zip and got another thing 12 security signature or something other, ran it again imediatelly <did not close command prompt and left phone with the htc emblem on there> with the same command and surprisingly it worked!

Unlock then reflash a recovery
Sent from my HTC One using xda app-developers app

Yep, that should do it since you unlock and flash from the bootloader.

Bseagull said:
Yep, that should do it since you unlock and flash from the bootloader.
Click to expand...
Click to collapse
it's weird tho, because it was "relocked" and S-ON so I dont even know how it worked.

HTC VIVID bootloader will not unlock

Default HTC VIVID
Ok im new not sure where to post this question. Im new to androids and my htc vivid is giving me a headache have read countless threads and posts and still stumped.
***LOCKED***
HOLIDAY PVT SHIP S-ON RL
HBOOT - 1.85.0025
MICRO OP - 0360
openADSP - v 02.6.0.2226.00.0202
eMMc - boot
march 1 2012, 17:09:49
Thats what my hboot reads. I have followed directions to unlock bootloader and everything went smooth got file in email and everything then when phone asks me to unlock bootloader i press power on phone to select yes and phone turns off and have to take out battery and reinsert into phone to get back into bootloader and still says locked at top. My os is messed up so i tried doing ruu thing it just keeps saying booting into bootloader and stays like that for thirty minutes. Fastboot program recognizes phone so im not sure what im doing wrong or if phone is too messed up or what. Need some help wopuld be greatly appreciated.

My bootloader did not wanted to be unlocked too.
Until i gain S-OFF...

Prerequisites
- Must be on a stock ROM
- Must be HTCDev unlocked
- Must be rooted
Thats what says requires these things to do the s-off, with the hasoon allin one toolkit for s-off. I am not rooted and when i do the HTCDev unlock my phone wont reboot so i have to take out battery just to get into hboot. So my question is how am i supposed to go about that if I cannot even meet the prerequisites. Or is there another way to s-off. Also if I go ahead and try it anyways is it gonna make this phone totally not usable?

Well now its been two days and my phone wont boot into hboot or anything says its charging then go to boot into hboot and light keeps flashing like its dead. Even bought an oem cable and charger for it and same thing. Gonna buy new battery and go from there i guess.

Ok well got new battery can get into hboot now but that is it. All the same things going on!!! WILL SOMEBODY PLEASE HELP 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.

[Q] Cannot set phone back to S-ON

Hi There,
So I've been following this guide to get back to 100% stock ready to send my phone off for repair.
I'm so close! The rom is back to stock from running the RUU, my bootloader is set back to LOCKED, now all I need to to change S-OFF back to S-ON. The problem is that fastboot won't let me for some reason. I run the command fastboot oem writesecureflag 3 and this is the output I get
Code:
...
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.048s]
Any clues how to sort this out? They're supposed to be collecting my phone tomorrow!
Thanks

HapticThreek said:
Hi There,
So I've been following this guide to get back to 100% stock ready to send my phone off for repair.
I'm so close! The rom is back to stock from running the RUU, my bootloader is set back to LOCKED, now all I need to to change S-OFF back to S-ON. The problem is that fastboot won't let me for some reason. I run the command fastboot oem writesecureflag 3 and this is the output I get
Code:
...
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.048s]
Any clues how to sort this out? They're supposed to be collecting my phone tomorrow!
Thanks
Click to expand...
Click to collapse
If you set back to s-on with your current firmware version after the RUU you flashed in your last thread, you will get the tampered flag back, just lock your bootloader and send it back s-off, they probably wont even notice.

Seanie280672 said:
If you set back to s-on with your current firmware version after the RUU you flashed in your last thread, you will get the tampered flag back, just lock your bootloader and send it back s-off, they probably wont even notice.
Click to expand...
Click to collapse
I thought they might not notice but would rather not run the risk. If s-on will add a tampered flag I'll just follow your advice and hope they don't notice! Its an issue with the bluetooth they need to look at so hopefully they won't even bother looking at the bootloader. Especially seeing as they had the phone a week ago anyway.

HapticThreek said:
I thought they might not notice but would rather not run the risk. If s-on will add a tampered flag I'll just follow your advice and hope they don't notice! Its an issue with the bluetooth they need to look at so hopefully they won't even bother looking at the bootloader. Especially seeing as they had the phone a week ago anyway.
Click to expand...
Click to collapse
First time, most of the time, they just do what they call a software update on it to try and fix the problems, "like any of use cant do that ourselves lol", some people receive their phones already s-off and they will just think one slipped though, better to send it s-off than with the tampered flag, chance are they will just replace the device this time if its still under warranty.

@HapticThreek you have a modded hboot in there!! be careful!!

Seanie280672 said:
First time, most of the time, they just do what they call a software update on it to try and fix the problems, "like any of use cant do that ourselves lol", some people receive their phones already s-off and they will just think one slipped though, better to send it s-off than with the tampered flag, chance are they will just replace the device this time if its still under warranty.
Click to expand...
Click to collapse
This is what I'm hoping for! It's still under warranty so hopefully they just think I had an S-OFF originally (its still locked!) and fix or replace.
nkk71 said:
@HapticThreek you have a modded hboot in there!! be careful!!
Click to expand...
Click to collapse
Don't know how I would have gotten a modded hboot, I flashed from an RUU. Maybe something got corrupted along the way. I'm just gonna follow Seanie's advice and leave it and hope they don't notice (better yet, hope they don't look)!

I didn't look super closely at your link but I did see some stuff on there about hboot mods. If it is a custom hboot that was in the RUU (possibly unsigned?) that you flashed while s-off , "writesecureflag3 " will not work because it checks for such things. This is not a bad thing! If you used a hack to circumvent this security check, your next s-on boot up would result in the security check you just forced on finding the rouge hboot and a bricked device only repairable through a j-tag service is what you would be left with!! If you run an RUU for your device from the Dev thread with a fully stock everything (including hboot as a fully stock carrier specific would) "writesecureflag3" should definitely execute successfully and uneventfully. I have returned to stock with s-on for warranty work on the camera and the phone was returned with the same revone exploitable version on it that I sent it in with.

[Q] How to get back S-ON without fastboot usb :)

Hello,
First of all sorry in advance for my bad english
It's first time i post in xda for asking help.
Actual state of my phone :
- charge only when is power off
- when power on, no usb connectivity at all
This issue for usb connectivity appears one day without a logical reason, after some messages like "your phone is running in usb host mode and can't charge etc.." , "your phone charger is not original .." (despite he is)
Of course i have already test in furthers pc and usb cables, already clean the usb connector, already test the stuff like push power + vol up + vol down during 2 mins in front of bright light for reset the battery... My other phone an HOX is running well in usb with the same cable and pc (mtp, adb, fastboot..) so this not the way to solve my issue. I think it's a material issue on the mainboard or the usb connector.
So i've decided to get back my HTC One to repair center but for warranty i manage to get it back to completely stock of course.
So, i set it S-OFF with revone (initial hboot 1.44 inside, very good tool for this hboot works like a charm), for delete "tampered" and set "locked" instead of "relocked" in bootloader.
After that, i have make all the updates and now i am on stock branded rom SFR (vodafone in France) up to date with original recovery and 1.57 hboot.
But i am still S-OFF and can't return the phone for warranty like that
So, somebody here have a great idea to get S-ON without fastboot usb who isn't working anymore on my device ??
I have one idea but really complicated : make an update.zip for downgrade the hboot to 1.44 with the original recovery + root (SU+binaries) with that i could try to use an old version of revone (0.2) which permit to use ./revone -s 3 as fastboot oem wirtesecureflag 3
And i don't know if i can do that with original recovery... but my S-OFF could perhaps help me in my bad situation i hope
Thansk in advance for all your ideas to help me to get back S-ON

poggus said:
Hello,
First of all sorry in advance for my bad english
It's first time i post in xda for asking help.
Actual state of my phone :
- charge only when is power off
- when power on, no usb connectivity at all
This issue for usb connectivity appears one day without a logical reason, after some messages like "your phone is running in usb host mode and can't charge etc.." , "your phone charger is not original .." (despite he is)
Of course i have already test in furthers pc and usb cables, already clean the usb connector, already test the stuff like push power + vol up + vol down during 2 mins in front of bright light for reset the battery... My other phone an HOX is running well in usb with the same cable and pc (mtp, adb, fastboot..) so this not the way to solve my issue. I think it's a material issue on the mainboard or the usb connector.
So i've decided to get back my HTC One to repair center but for warranty i manage to get it back to completely stock of course.
So, i set it S-OFF with revone (initial hboot 1.44 inside, very good tool for this hboot works like a charm), for delete "tampered" and set "locked" instead of "relocked" in bootloader.
After that, i have make all the updates and now i am on stock branded rom SFR (vodafone in France) up to date with original recovery and 1.57 hboot.
But i am still S-OFF and can't return the phone for warranty like that
So, somebody here have a great idea to get S-ON without fastboot usb who isn't working anymore on my device ??
I have one idea but really complicated : make an update.zip for downgrade the hboot to 1.44 with the original recovery + root (SU+binaries) with that i could try to use an old version of revone (0.2) which permit to use ./revone -s 3 as fastboot oem wirtesecureflag 3
And i don't know if i can do that with original recovery... but my S-OFF could perhaps help me in my bad situation i hope
Thansk in advance for all your ideas to help me to get back S-ON
Click to expand...
Click to collapse
I could not find a way to go S-ON without fastboot except revone. You could just take the chance that with it "Locked" and no "Tampered" banner they may not care if it is S-OFF. IMO, it would be the safer route than attempting something that might brick the phone in the wrong configuration.

poggus said:
Hello,
First of all sorry in advance for my bad english
It's first time i post in xda for asking help.
Actual state of my phone :
- charge only when is power off
- when power on, no usb connectivity at all
This issue for usb connectivity appears one day without a logical reason, after some messages like "your phone is running in usb host mode and can't charge etc.." , "your phone charger is not original .." (despite he is)
Of course i have already test in furthers pc and usb cables, already clean the usb connector, already test the stuff like push power + vol up + vol down during 2 mins in front of bright light for reset the battery... My other phone an HOX is running well in usb with the same cable and pc (mtp, adb, fastboot..) so this not the way to solve my issue. I think it's a material issue on the mainboard or the usb connector.
So i've decided to get back my HTC One to repair center but for warranty i manage to get it back to completely stock of course.
So, i set it S-OFF with revone (initial hboot 1.44 inside, very good tool for this hboot works like a charm), for delete "tampered" and set "locked" instead of "relocked" in bootloader.
After that, i have make all the updates and now i am on stock branded rom SFR (vodafone in France) up to date with original recovery and 1.57 hboot.
But i am still S-OFF and can't return the phone for warranty like that
So, somebody here have a great idea to get S-ON without fastboot usb who isn't working anymore on my device ??
I have one idea but really complicated : make an update.zip for downgrade the hboot to 1.44 with the original recovery + root (SU+binaries) with that i could try to use an old version of revone (0.2) which permit to use ./revone -s 3 as fastboot oem wirtesecureflag 3
And i don't know if i can do that with original recovery... but my S-OFF could perhaps help me in my bad situation i hope
Thansk in advance for all your ideas to help me to get back S-ON
Click to expand...
Click to collapse
You should have gone back to s-on before updating the software. If you go back to s-on now you risk the tampered flag returning. You need to set back to s-on before hboot 1.55 to avoid this.
I think your best option as @majmoz suggests is to send it as is with s-off. There more likely to ignore the fact that it's a-off than if its s-on with tampered. :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Thank you majmoz and danny201281 for your advices.
I know that i should use revone when i was under 1.44 hboot.. but now it's too late
I think i will try to send to warranty like that, i share your opinion it's less risky like that than with tampered and relocked ! So i will no more try to get S-ON with fastboot, if it's for have the tampered flag that will be worst
And HTC must have furthers returns for HTC ONE with the same issue like mine (i google it and many peoples have the no usb connectivity issue in average 1 year after purchase it's strange..)
Next one will be a Samsung phone, sorryt HTC
I will comme back for getting news about warranty and S-OFF of course, if it can help some others.