Nvidia and Robotics w/ Barrett Williams – XDA:DevCon 2014

Robotics continues to dominate our videos from this years XDA:DevCon 2014 in … more

Speed Up Deodexing with JoelDroid Batch Deodexer

Android 5.0 Lollipop brings many under-the-hood changes like changing the default compiler … more

Top 5 Apps for 2014 + Top Xposed Mod of 2014 – XDA TV

Its that time of year where you look back and remember the things that happened … more

NVIDIA SHIELD Tablet Gets Android 5.0.1, OTA Available

The NVIDIA SHIELD Tablet is the latest Android-powered device released by famed GPU … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Cannot set phone back to S-ON

OP HapticThreek

20th July 2014, 11:34 AM   |  #1  
OP Junior Member
Flag Cambridge, UK
Thanks Meter: 1
 
25 posts
Join Date:Joined: Aug 2012
More
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
20th July 2014, 12:53 PM   |  #2  
Seanie280672's Avatar
Senior Member
Flag Halesowen
Thanks Meter: 349
 
1,180 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by HapticThreek

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

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.
20th July 2014, 12:57 PM   |  #3  
OP Junior Member
Flag Cambridge, UK
Thanks Meter: 1
 
25 posts
Join Date:Joined: Aug 2012
More
Quote:
Originally Posted by Seanie280672

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.

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.
20th July 2014, 04:05 PM   |  #4  
Seanie280672's Avatar
Senior Member
Flag Halesowen
Thanks Meter: 349
 
1,180 posts
Join Date:Joined: Feb 2012
Donate to Me
More
Quote:
Originally Posted by HapticThreek

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.

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.
20th July 2014, 04:14 PM   |  #5  
nkk71's Avatar
Recognized Contributor
Flag Beirut
Thanks Meter: 3,127
 
6,298 posts
Join Date:Joined: May 2010
More
@HapticThreek you have a modded hboot in there!! be careful!!
20th July 2014, 09:30 PM   |  #6  
OP Junior Member
Flag Cambridge, UK
Thanks Meter: 1
 
25 posts
Join Date:Joined: Aug 2012
More
Quote:
Originally Posted by Seanie280672

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.

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.

Quote:
Originally Posted by nkk71

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

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)!
21st July 2014, 05:52 AM   |  #7  
Member
Flag St Louis MO
Thanks Meter: 4
 
40 posts
Join Date:Joined: Sep 2013
More
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.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes