Related
-why i can not Unlock bootreader Command fastboot oem get_identifier_token error it not up code for unlock
hamit66 said:
-why i can not Unlock bootreader Command fastboot oem get_identifier_token error it not up code for unlock
Click to expand...
Click to collapse
OK, when you boot into your bootloader screen, can you post a screen shot of it?
What version of the bootloader do you have?
The unlock token is only available on the official HTC bootloaders versions 1.16.0000 and above.
If you have version 1.13.0000, then you can just run Revolutionary to gain S-OFF.
hamit66 said:
-why i can not Unlock bootreader Command fastboot oem get_identifier_token error it not up code for unlock
Click to expand...
Click to collapse
Ok seriously, you really have to stop using google translate.
As to your problem, did you follow HTC's instructions exactly as they say on the website? If you did, there shouldn't be a problem. That's my first guess.
hamit66 said:
-why i can not Unlock bootreader Command fastboot oem get_identifier_token error it not up code for unlock
Click to expand...
Click to collapse
To answer your question that you posted in the Development section, you can download the last and final HTC ICS ROM for the IncS at the HTCDEV.com site.
i'm do follow web HTCDEV.com but it is not success
Phone me
BlackRose
Hboot 2.03.0000 S-OFF
ON CMD
D:\android>fastboot oem get_identifier_token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
hamit66 said:
i'm do follow web HTCDEV.com but it is not success
Phone me
BlackRose
Hboot 2.03.0000 S-OFF
ON CMD
D:\android>fastboot oem get_identifier_token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
OK, you have BlackRose HBOOT and you have S-OFF, so there is no need to unlock this bootloader.
Now if you want to go back to a full stock HTC RUU, then you will have to remove the BlackRose HBOOT before you can flash the HTC RUU.
hamit66 said:
i'm do follow web HTCDEV.com but it is not success
Phone me
BlackRose
Hboot 2.03.0000 S-OFF
ON CMD
D:\android>fastboot oem get_identifier_token
< waiting for device >
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
OK I hve no idea what Phone me means so I'll assum that's what it says in your bootloader.
Since you already have Blackrose, just flash a recovery and you are good to go for installing custom ROMs. If you need assistance, please look at the guides stickied in the general forum.
tpbklake said:
OK, you have BlackRose HBOOT and you have S-OFF, so there is no need to unlock this bootloader.
Now if you want to go back to a full stock HTC RUU, then you will have to remove the BlackRose HBOOT before you can flash the HTC RUU.
Click to expand...
Click to collapse
yeah i want to go back to a full stock HTC RUU offical rom
before Revolutionary Hboot 6.0..
Now i Suspect why is not up code on CMD
****** Thank you so much for Answer questions******** :good::good::good::good:
072665995 said:
OK I hve no idea what Phone me means so I'll assum that's what it says in your bootloader.
Since you already have Blackrose, just flash a recovery and you are good to go for installing custom ROMs. If you need assistance, please look at the guides stickied in the general forum.
Click to expand...
Click to collapse
Thank you so much
i Suspect why is not up code on CMD for unlock
I got the 4.2.2 Ruu installed and in order to downgrade on dev edition i flashed the 1.44 stock Hboot.
When i try to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3 it allways shows me the error 158 while tries to flash the RUU.
So i relocked my bootloader, as some states that could solve my prob. But i got the same error 158 again.
So i wanted to reunlock the bootloader again.(Still 4.2.2 GE and the Hboot 1.44)
Normally on GE roms(1.54 hboot) u just hit "fastboot oem unlock" but on 1.44 this is impossible. So i managed to get a token id key from htc dev
for my hboot 1.44.
The token works but theres no " are u really want to unlock bl" request, like it is on stock sense roms at the end of the bl-unlock procedure.
So bl stays relocked! I
Am i stucked now on a relocked bl with no way to get it unlocked again????
Code:
fastboot oem unlock
won't every work on an HTC device, by the way what does the terminal returns?
matt95 said:
Code:
fastboot oem unlock
won't every work on an HTC device, by the way what does the terminal returns?
Click to expand...
Click to collapse
C:\Android\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot flash
unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.162s
The terminal returns this after flashing the token. So this should be right! but bl stays relocked.
fastboot oem unlock :
C:\Android\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot oem un
lock
...
FAILED (remote: loading custom splash failed)
finished. total time: 0.002s
C:\Android\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>
That's strange, try to download again your unlockcode.bin, If it does not work then you're pretty much stucked there
matt95 said:
That's strange, try to download again your unlockcode.bin, If it does not work then you're pretty much stucked there
Click to expand...
Click to collapse
No ,new token didnt helped. Is there any chance to get the RUU.exe to work? heres the intresting part of the log of it:
Im on the right cid and mid!
<T235448><DEBUG><CMD>htc_fastboot -s SH362W900689 -d flash zip C:\Users\Bruno\AppData\Local\Temp\{164DC584-095D-4AE4-A69C-6DECA925F94E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T235448>
<T235545><DEBUG><OUT>sending 'zip'... (1004418 KB) OKAY</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>writing 'zip'... (bootloader) rom parsing start ...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>(bootloader) rom parsing finish ...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>(bootloader) zip header checking...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>(bootloader) zip info parsing...</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>FAIL22 loading zip info fail</OUT>
</DEBUG></T235545>
<T235545><DEBUG><OUT>FAILED (remote: 22 loading zip info fail)</OUT>
SOLVED !
Yeah man I got it finally! Somehow i was able to enter RUU mode with locked bl! Flashed a RUU and i was back in the game! I hit the token command first, which maybe caused a temp bypass,cause on the first try i rebooted bl before hiting the Ruu command, which didnt worked !
GN8 and Thanks
Yeah, with an official GPe HTC One you only unlock it using 'fastboot oem unlock' - you do NOT have to use HTCDev at all...
Taken from this HTC Blog post - http://blog.htc.com/2013/05/htc-one-google-nexus-experience/:
"***The HTC One special edition bootloader can be unlocked by standard method for “Nexus experience” devices"
Meaning you use the standard Nexus unlock procedure
EDIT: Re-read the OP, seems you have converted it to Sense so in that case, normal HTC unlock rules apply
EddyOS said:
Yeah, with an official GPe HTC One you only unlock it using 'fastboot oem unlock' - you do NOT have to use HTCDev at all...
Taken from this HTC Blog post - http://blog.htc.com/2013/05/htc-one-google-nexus-experience/:
"***The HTC One special edition bootloader can be unlocked by standard method for “Nexus experience” devices"
Meaning you use the standard Nexus unlock procedure
EDIT: Re-read the OP, seems you have converted it to Sense so in that case, normal HTC unlock rules apply
Click to expand...
Click to collapse
Yeah i know thats the way to do this on GE Roms! I solved it allready . No u cant open a sense bootloader under GE.(The request "are u really want to unlock the bl" wont appear(cause of wrong rom) and after u hit the token nothing happens and bl stays relocked .
As i described the post before i somehow "bypassed" the bl with the htc dev token to get into RUU mode.
My bl was still on relocked after i installed the new 4.3 GE RUU. For sure i could it unlock with "fastboot oem unlock" after new RUU was on!
So what ive learned?
DONT RELOCK A Hboot 1.44 BL on a GE ROM CAUSE U WILL STAY RELOCKED!
Hi Guys
Just wondering if anyone has any suggestions. I have an Australian unbranded HTC one (for which no known RUU seem to be floating around). I'm S-on with Hboot 1.54. And was hoping to use the Rumrunner exploit to S-off
I've previously had the bootloader unlocked and relocked it again. However since I've taken an OTA I've been unable to unlock the bootloader again using the method on HTC dev.
The unlock_code.bin is pushed (although says 0kB) and it is checked successfully. However then nothing happens. No screen to ask if you want to unlock the bootloader.
I'm wondering if anyone has any suggestions?
Cheers
What's the command you're typing in to unlock it? It should be:
fastboot flash unlocktoken Unlock_code.bin
EddyOS said:
What's the command you're typing in to unlock it? It should be:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Yep thats the command I've used. As I said that command pushes the unlock_code.bin. The check is successful.
Its just that nothing happens after that. No do you want to continue unlocking the bootloader screen. The phone sits there in fastboot doing nothing....
You have to type it exactly as I posted it as it's case sensitive. Copy and paste the command and try again (make sure you've not changed the name of the token either)
EddyOS said:
You have to type it exactly as I posted it as it's case sensitive. Copy and paste the command and try again (make sure you've not changed the name of the token either)
Click to expand...
Click to collapse
Yep I have copied and pasted. I have not renamed the .bin. I have also tried using Hasoon2000's all in one tool kit as well. As I said the unlock_bin is pushed. It passes the check but nothing happens after that.
Ali Baba 84 said:
Yep I have copied and pasted. I have not renamed the .bin. I have also tried using Hasoon2000's all in one tool kit as well. As I said the unlock_bin is pushed. It passes the check but nothing happens after that.
Click to expand...
Click to collapse
try getting a new unlocktoken from htcdev
[email protected] said:
try getting a new unlocktoken from htcdev
Click to expand...
Click to collapse
I have tried that as well. Same things occurs.
Ali Baba 84 said:
I have tried that as well. Same things occurs.
Click to expand...
Click to collapse
can you copy/paste the lines in the command prompt, so we can take a look at the details
Ali Baba 84 said:
I have tried that as well. Same things occurs.
Click to expand...
Click to collapse
try doing it from a new folder with a new set of adb/fastboot from a different folder location.
works for some
nkk71 said:
can you copy/paste the lines in the command prompt, so we can take a look at the details
Click to expand...
Click to collapse
c:\SDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.154s
c:\SDK\platform-tools>
[email protected] said:
try doing it from a new folder with a new set of adb/fastboot from a different folder location.
works for some
Click to expand...
Click to collapse
Just gave that a go... still no luck
Ali Baba 84 said:
c:\SDK\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.145s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.154s
c:\SDK\platform-tools>
Click to expand...
Click to collapse
Try doing a factory reset, and then try the unlock again.
You could also try what fadimanansala said about a different folder, it worked for this guy: http://forum.xda-developers.com/showthread.php?t=2491013
nkk71 said:
Try doing a factory reset, and then try the unlock again.
You could also try what fadimanansala said about a different folder, it worked for this guy: http://forum.xda-developers.com/showthread.php?t=2491013
Click to expand...
Click to collapse
Just gave that a go too. Still no luck
Ali Baba 84 said:
Just gave that a go too. Still no luck
Click to expand...
Click to collapse
try using Hasoon's or Squabbi's toolkit
but download the unlocktoken sent to your email again and use the new downloaded token
[email protected] said:
try using Hasoon's or Squabbi's toolkit
but download the unlocktoken sent to your email again and use the new downloaded token
Click to expand...
Click to collapse
I had tried that previously, but even still with the new token still nothing.
I appreciate the suggestions but still no luck
Ali Baba 84 said:
I had tried that previously, but even still with the new token still nothing.
I appreciate the suggestions but still no luck
Click to expand...
Click to collapse
What's your setup?
ROM,
firmware,
recovery,
CID
nkk71 said:
What's your setup?
ROM,
firmware,
recovery,
CID
Click to expand...
Click to collapse
Stock Sense
2.24.980.2
Stock recovery
HTC_039
Ali Baba 84 said:
Stock Sense
2.24.980.2
Stock recovery
HTC_039
Click to expand...
Click to collapse
that really doesn't make any sense why it's not working.
I'm pretty sure you are, but are you sure you're copy/pasting the entire identifier code including the top and bottom line (the ones that start and end with <<<<< and >>>>>)
Also check SETTINGS->POWER->Fast boot should be disabled
and SETTINGS->DEVELOPER OPTIONS->USB Debugging should be enabled.
I would try (yet again) factory reset, get identifier, submit to HTCdev for Unlock code, and finally try it.
If that doesn't work, I really don't know what could be causing it.
EDIT: just out of curiosity, have you tried "fastboot oem unlock"
Ali Baba 84 said:
Stock Sense
2.24.980.2
Stock recovery
HTC_039
Click to expand...
Click to collapse
One last thing I thought about, if the above doesn't work is try locking it again; maybe it's stuck somewhere half way in between. maybe locking it again "fastboot oem lock" and then trying again could release whatever is hanging.
Good luck
nkk71 said:
One last thing I thought about, if the above doesn't work is try locking it again; maybe it's stuck somewhere half way in between. maybe locking it again "fastboot oem lock" and then trying again could release whatever is hanging.
Good luck
Click to expand...
Click to collapse
Gave those both a try.
I got a command error when running fastboot oem unlock, and I got a message saying device is already locked when running fastboot oem lock.
Any other ideas, its a bit of a mystery to me
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
hjjfffaa said:
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
Click to expand...
Click to collapse
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
fenstre said:
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
Click to expand...
Click to collapse
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
hjjfffaa said:
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
Click to expand...
Click to collapse
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
fenstre said:
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
Click to expand...
Click to collapse
But I can downgrade to 1.44 and that would allow me to S-On and get OTA updates right? Or am I totally wrong?
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
hjjfffaa said:
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
Click to expand...
Click to collapse
You have S-off which is good. I'm going to ask you to use the BS_US001 CID. Try downloading the 1.29.1540.17 zip from HTC Dev. Do a fastboot oem rebootRUU and flash the zip from there. It should prompt you to do this twice.
Sent from my HTC One using XDA Premium 4 mobile app
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
hjjfffaa said:
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2497712
You can follow that thread if you want to set the phone to locked.
I'm sorry I forgot about the 4.3 zip, use that one if you want to go straight to 4.3. Again, my apologies
Sent from my HTC One
I don't care if it says re-locked (so long as it functions how it should), I just want my Sense ROM. I already have the 4.3 Dev Edition zip, should I try flashing it with fastboot?
I tried flashing the 3.22.1540.1 zip and got this problem, which doesn't seem consistent with the one guide I've seen for this process.
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.663s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.625s
Click to expand...
Click to collapse
Try 'fastboot erase cache' and 'fastboot reboot-bootloader' before you 'fastboot oem rebootruu' and then run the fastboot flash zip filename.zip'
Sent from my HTC One
The results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.359s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.318s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
Could this be a result of the 1.54 bootloader?
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
Can you take an image of your bootloader for me real quick
gusto5 said:
Can you take an image of your bootloader for me real quick
Click to expand...
Click to collapse
Here you go.
hjjfffaa said:
Here you go.
Click to expand...
Click to collapse
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
gusto5 said:
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
Click to expand...
Click to collapse
Thanks for all your help. Trying a different USB port.
You were right, it did nothing.
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
You may be right. Let's have you downgrade the Bootloader to 1.44 and then try running the RUU again.
Just remember that you already have the right MID and CID. CID you changed yourself, MID already matches as the Google Play Edition shares the same MID as the Developer edition (and a few other North American HTC Ones).
Here are the (real) results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip hbootRUU.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.516s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
hjjfffaa said:
Here are the results:
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
Click to expand...
Click to collapse
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
gusto5 said:
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All right, should I add it to the android-text file though?
Hey guys so I have a lot of problems with my phone like the purple camera and my volume down broke. Ive been trying to fix it for ages and im finally up to the last step and its not working.
I'm trying to get S-ON and used the cmd "fastboot oem writesecureflag 3" but it gives me an error fail thing
C:\Users\Ivan\Desktop\ROOT>adb devices
List of devices attached
HT35DW923150 device
C:\Users\Ivan\Desktop\ROOT>adb reboot boatloader
C:\Users\Ivan\Desktop\ROOT>fastboot devices
HT35DW923150 fastboot
C:\Users\Ivan\Desktop\ROOT>fastboot erase chache
erasing 'chache'...
FAILED (remote: not allowed)
finished. total time: 0.014s
C:\Users\Ivan\Desktop\ROOT>fastboot erase cache
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.372s
C:\Users\Ivan\Desktop\ROOT>fastboot oem writesecureflag 3
...
(bootloader) partition sbl2 signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 0.086s]
finished. total time: 0.090s
C:\Users\Ivan\Desktop\ROOT>
So I dont know what to do from here, I hope you guys can help me out.
Send your phone without S On HTC check for unlocked relocked locked only
If Locked is there without tampered they will avail warranty
To remove Tempered and set Locked use Guru bootloader reset tool in TWRP
yatindroid said:
Send your phone without S On HTC check for unlocked relocked locked only
If Locked is there without tampered they will avail warranty
To remove Tempered and set Locked use Guru bootloader reset tool in TWRP
Click to expand...
Click to collapse
Are you sure that i can send my One with S-Off??
Raschild6 said:
Are you sure that i can send my One with S-Off??
Click to expand...
Click to collapse
in my country they check tempered and unlocked bootloader not for S Off or On
ask your friends in your country
yatindroid said:
in my country they check tempered and unlocked bootloader not for S Off or On
ask your friends in your country
Click to expand...
Click to collapse
no problem i have set S On, now my One is in the other hands i hope it comes back soon!!
Any luck on this front? I am getting the same message when trying to writesecureflag 3. Any ideas?
i had a mis-matching hboot version between my ROM and firmware. downgraded the firmware back to the version matching the ROM and i was able to get S-ON
you guys have a modded hboot in there (who knows what else is non-100%-stock),
consider yourself lucky that command does signature checks, otherwise you'd have an insta-brick paperweight on your hands.