Develop Bugs

Rooting an S-Off HOX

Hey XDA :
I kneel before you a broken and confused man. Here's my issue, I bought a One X not long ago, noticed it was S-Off but still went ahead n unlocked Bootloader, dunno if I should have given fact I got S-Off ... Started flashing tons of ROMs .... But from what I understand, with S-Off I do not need to flash boot.img every time I want to flash a ROM, yet, none work unless I do ... Thus confusion reigns ...
Am seriously considering going stock with latest 2.17 RUU, thus loosing my ROOT and EVERYTHING !!! Ok all SD is backed up to my HDD ... But still I have no idea ... This is annoying ... Living in total darkness .. Am a n00b coming from iOS the main Android competitor ...
Here's proof of my S-Off :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me !!!!

Read, read some more, take a break then read some more....
Eventually you'll figure it out.
I'd help you but jumping into threads pretending you're a hero for having s off, which you didn't even earn - was just lucky, Pissed me off so I won't.
---------- Post added at 05:35 PM ---------- Previous post was at 05:31 PM ----------
PsyChoses said:
This ROM is so good it has become my daily driver! Sadly I only use my HOX to test various ROMs n learn more about Android! Nothing else, like no Sim Card nothing!
I am an iOS/MacOS fan n forever will be....
Click to expand...
Click to collapse
*rolls eyes*

1. You didn't need to unlock the bootloader if you have S-OFF, you can just flash anything you want
2. If the ROMs ZIP is written correctly you don't have to flash the boot.img as it'll be flashed with the ROM. If not you'll have to do it manually
3. You can flash any RUU you want as you are S-OFF so you don't even need to root it unless you want to

Read, read some more, take a break then read some more....
Eventually you'll figure it out.
I'd help you but jumping into threads pretending you're a hero for having s off, which you didn't even earn - was just lucky, Pissed me off so I won't.
Click to expand...
Click to collapse
Oh c'mon, really ? You took that seriously ? Yes I am an iOS fan that don't mean I can't become an Android one too !!! And am not acting like no hero ... Was just showing that S-Off devices existed ... Am really sorry it came off the wrong way ...
1. You didn't need to unlock the bootloader if you have S-OFF, you can just flash anything you want
2. If the ROMs ZIP is written correctly you don't have to flash the boot.img as it'll be flashed with the ROM. If not you'll have to do it manually
3. You can flash any RUU you want as you are S-OFF so you don't even need to root it unless you want to
Click to expand...
Click to collapse
1. So what does unlocking Bootloader on S-Off cause ? Will it cause device to act weird ?
2. Hmm... Ok ?
3. I just thought I'd flash latest RUU to get HBoot updated n stuff, then Root again to get back to flashing ROMs
Thanks

PsyChoses said:
1. So what does unlocking Bootloader on S-Off cause ? Will it cause device to act weird ?
2. Hmm... Ok ?
3. I just thought I'd flash latest RUU to get HBoot updated n stuff, then Root again to get back to flashing ROMs
Thanks
Click to expand...
Click to collapse
1. It means HTC now know you've unlocked the bootloader. Before, as you had S-OFF, there was no reason for them to know. They could now refuse your warranty
2. ???
3. Yep you can do that, I did

1. It means HTC now know you've unlocked the bootloader. Before, as you had S-OFF, there was no reason for them to know. They could now refuse your warranty
2. ???
3. Yep you can do that, I did
Click to expand...
Click to collapse
1. So to Root I did not need to unlock bootloader ? And it's ok where I live there is no such thing as Warranty ... Just a 3 month shop warranty ...
2. That means that the ROMs were not built right that is why am having o flash boot.img ?
3. After flashing latest RUU my bootloader will re-lock ? no need to unlock it again to root ?
Again thanks

PsyChoses said:
1. So to Root I did not need to unlock bootloader ? And it's ok where I live there is no such thing as Warranty ... Just a 3 month shop warranty ...
2. That means that the ROMs were not built right that is why am having o flash boot.img ?
3. After flashing latest RUU my bootloader will re-lock ? no need to unlock it again to root ?
Again thanks
Click to expand...
Click to collapse
1. Fair enough!
2. It would appear so as the T3 One X flashes differently
3. You have to relock the bootloader to flash an RUU but once flashed you just reflash CWM without unlocking the bootloader

1. Fair enough!
2. It would appear so as the T3 One X flashes differently
3. You have to relock the bootloader to flash an RUU but once flashed you just reflash CWM without unlocking the bootloader
Click to expand...
Click to collapse
1. Cool
2. Seems so
3. Relock ? How ? Where to get the stock recovery ?
You are awesome for taking the time to help thanks

To relock the bootloader:
fastboot oem lock
Then run the RUU when the phone is connected in fastboot mode and away you go! You shouldn't need the stock recovery as the RUU replaces that but I've always flashed it before using the RUU purely through habit

To relock the bootloader:
fastboot oem lock
Then run the RUU when the phone is connected in fastboot mode and away you go! You shouldn't need the stock recovery as the RUU replaces that but I've always flashed it before using the RUU purely through habit
Click to expand...
Click to collapse
Ok now one last question how do I find out what RUU to use for my device ? Like if it is ASIA, Middle East, India etc .. ?
Thanks

You can use ANY RUU you want as you're S-OFF

You can use ANY RUU you want as you're S-OFF
Click to expand...
Click to collapse
ok flashed RUU, now I try to flash CWR and all I get is stock recovery can't go to CWR no more xD
EDIT :
I HAD to unlock Bootloader else no CWR ...
No Unlocked Bootloader = No Root / CWR
Unlocked Bootloader = Root/ CWR
At least that is what happened in my case even with S-Off xD

EddyOS said:
You can use ANY RUU you want as you're S-OFF
Click to expand...
Click to collapse
Unless the CID is set, but you can also set it to all 1s as you have S-Off!

I have the solution...............................Maybe you should swap your HOX with mine. :laugh:

PsyChoses said:
ok flashed RUU, now I try to flash CWR and all I get is stock recovery can't go to CWR no more xD
EDIT :
I HAD to unlock Bootloader else no CWR ...
No Unlocked Bootloader = No Root / CWR
Unlocked Bootloader = Root/ CWR
At least that is what happened in my case even with S-Off xD
Click to expand...
Click to collapse
Now that's weird, in the past with S-OFF you just flashed CWM using fastboot without unlocking the bootloader

Unless the CID is set, but you can also set it to all 1s as you have S-Off!
Click to expand...
Click to collapse
Yeah all is good now but had to unlock bootloader in order to flash CWR even with S-Off n CID set to 111111
Now that's weird, in the past with S-OFF you just flashed CWM using fastboot without unlocking the bootloader
Click to expand...
Click to collapse
I guess not anymore .. Not on HOX anyway xD
I have the solution...............................Maybe you should swap your HOX with mine.
Click to expand...
Click to collapse
You want it ? How about $600

[Q] former Samsung/Motorola flash addict seeking assistance with HTC!!

So...I first started rooting and custom rom'ing back in the Samsung Fascinate days, flash forward...I sold my s3 because I was in love with what I heard about the HTC One!! Found one on Craigslist in great condition. Dude I had bought it from said it had been rooted and I thought GREAT, saves me the trouble!! Well, I'm confused. I am running a modified 4.3, locked with s-on, and rooted. I am able to boot into TWRP. I cannot figure out the tech of the HTC One and need to know 2 things...1. How is this phone rooted with locked bootloader/s-on? 2. Where can I go from here... Can I flash other rom's through TWRP even though bootloader is locked and s-on? I have read everything I can on xda and still can't make sense of this...

Sounds like they unlocked it, flashed a custom rom, and then relocked it. I would use firewatter to get unlocked again and s-off. http://firewater-soff.com/instructions/. Not sure if you could flash in that state or not, but im guessing no.

Hey thanks! I was sort of guessing that is what happened...but couldn't really find a reason to do that? Is it difficult to hard brick an HTC? I was never concerned with the Samsung or Motorola, I could always get my way back from any issue. So, use firewater to unlock/s-off and then I can return to full stock or whatever?

schilly said:
So...I first started rooting and custom rom'ing back in the Samsung Fascinate days, flash forward...I sold my s3 because I was in love with what I heard about the HTC One!! Found one on Craigslist in great condition. Dude I had bought it from said it had been rooted and I thought GREAT, saves me the trouble!! Well, I'm confused. I am running a modified 4.3, locked with s-on, and rooted. I am able to boot into TWRP. I cannot figure out the tech of the HTC One and need to know 2 things...1. How is this phone rooted with locked bootloader/s-on? 2. Where can I go from here... Can I flash other rom's through TWRP even though bootloader is locked and s-on? I have read everything I can on xda and still can't make sense of this...
Click to expand...
Click to collapse
Hey I remember you from the Fascinate forums from a while ago... nice to see a familiar face! I had the S4 for a while but just switched to the HTC One. This phone is a beast. I was lucky enough to get mine on 4.2.2 so I just used rumrunner... you got lucky because up until a few days ago 4.3 was locked down. From what I understand so far, once you get S-Off you're pretty safe on flashing anything just like the Fascinate. The danger is in actually getting S-Off but firewater seems to be a fairly safe and easy method. Happy flashing and let me know if you have any questions, although I'm still learning the HTC ropes but I'll do my best

It is not likley to hard brick it, but it does happen. Mostly to people who dont pay attention and dont follow instructions well. Just make sure what ever your flashing, is for your phone. There are several varations of the one, and flashing the wrong firmware is just asking for an expensive brick. As long as you can get into the bootloader, there is usually always a fix.
Yeah use firewater and then flash a rom of your choosing. If you just want to be complete stock, you can flash an ruu, and then use firewater to unlock and get s-off if so desired.

Crawshayi said:
Hey I remember you from the Fascinate forums from a while ago... nice to see a familiar face! I had the S4 for a while but just switched to the HTC One. This phone is a beast. I was lucky enough to get mine on 4.2.2 so I just used rumrunner... you got lucky because up until a few days ago 4.3 was locked down. From what I understand so far, once you get S-Off you're pretty safe on flashing anything just like the Fascinate. The danger is in actually getting S-Off but firewater seems to be a fairly safe and easy method. Happy flashing and let me know if you have any questions, although I'm still learning the HTC ropes but I'll do my best
Click to expand...
Click to collapse
Hey...HELLO!! I will be sure to ask, thanks!

cmlusco said:
It is not likley to hard brick it, but it does happen. Mostly to people who dont pay attention and dont follow instructions well. Just make sure what ever your flashing, is for your phone. There are several varations of the one, and flashing the wrong firmware is just asking for an expensive brick. As long as you can get into the bootloader, there is usually always a fix.
Yeah use firewater and then flash a rom of your choosing. If you just want to be complete stock, you can flash an ruu, and then use firewater to unlock and get s-off if so desired.
Click to expand...
Click to collapse
Thank you for your reply...I feel a bit more confident. I follow directions well, so as long as I find a great tutorial I don't see any issues.
so as my phone stands right now, I can just flash a RUU (I think I know what that is, is it hard to find correct one?) and be stock, unrooted? And then I can take the upcoming OTA?
Thanks to you both...I just don't quite get the HTC lingo yet, but I'm a fast learner!!

Well it depends what version your on. If your on if your on 4.2 yes you can, if your on 4.3 not at the moment, unless you can find a 2.10.605.1 ruu somewhere. I would use firewater to get s-off then you can flash an older ruu and take the otas. If you take the kk ota before you get s-off, you risk the chance of firewater not working, and then your stuck without root untill a new exploit is found.

schilly said:
Thank you for your reply...I feel a bit more confident. I follow directions well, so as long as I find a great tutorial I don't see any issues.
so as my phone stands right now, I can just flash a RUU (I think I know what that is, is it hard to find correct one?) and be stock, unrooted? And then I can take the upcoming OTA?
Thanks to you both...I just don't quite get the HTC lingo yet, but I'm a fast learner!!
Click to expand...
Click to collapse
As cmlusco said, I'd probably recommend getting s-off with firewater before an OTA. When 4.3 came out it prevented the existing bootloader unlock tool from working. It was a few weeks before firewater came out and while it works with 4.3 there's no guarantee that it will work with 4.4. Also, you can be S-OFF and take OTAs but flashing a ROM is the safer way to go as far as keeping the ability to run custom recoveries, etc.
EDIT: I didn't realize how much I repeated what cmlusco said. I'll go fade back into the woodwork now. Carry on, nothing to see here.

schilly said:
Thank you for your reply...I feel a bit more confident. I follow directions well, so as long as I find a great tutorial I don't see any issues.
so as my phone stands right now, I can just flash a RUU (I think I know what that is, is it hard to find correct one?) and be stock, unrooted? And then I can take the upcoming OTA?
Thanks to you both...I just don't quite get the HTC lingo yet, but I'm a fast learner!!
Click to expand...
Click to collapse
Don't even bother waiting for the OTA... I'm on NuSense 4.4.2 and it's awesome. I'm sure it'll be updated when the OTA hits too, but if you want KitKat early just jump right in, the water is fine.

EDIT: I didn't realize how much I repeated what cmlusco said. I'll go fade back into the woodwork now. Carry on, nothing to see here. [/QUOTE]
Ha! I didn't see nuthin lol...moving on!

I cannot get adb to work on my new laptop running windows 8...ugh! So frustrated.

A modified hboot with the indicators of s-off and unlocked changed to look like locked and s-on might have been flashed also. I would boot into fastboot and see if you can fast boot flash a different recovery before going through the hastle of using the firewater soff exploit
Sent from my HTC6500LVW using Tapatalk

Check out this thread and see if it provides any answers for your Windows 8 dilemma http://forum.xda-developers.com/showthread.php?t=2493458

I would boot into fastboot and see if you can fast boot flash a different recovery before going through the hastle of using the firewater soff exploit
Never did that before...will see what I can find on Google! Need to figure this out, making me mad.
Sent from my HTC6500LVW using Tapatalk[/QUOTE]

schilly said:
I would boot into fastboot and see if you can fast boot flash a different recovery before going through the hastle of using the firewater soff exploit
Never did that before...will see what I can find on Google! Need to figure this out, making me mad.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
[/QUOTE]
Its pretty easy. first obviously make sure you have debugging enabled then Install this package http://forum.xda-developers.com/showthread.php?t=2317790
Then download a recovery IMG from the original dev section and put it in the same folder as where the minimal adb and fastboot package extracted too. Run the batch for minimal that opens a command prompt to that directory.
Type: adb devices(to make sure it sees your phone)
Next: adb reboot bootloader
Next: you will see bootloader options type: fastboot oem rebootRUU (it is case sensitive)
Next: wait for HTC logo on black background to show up and then type: fastboot flash recovery (IMG filename with extension. IE: twrp.IMG)
Example: fastboot flash recovery twrp.img
Next: fastboot reboot
After it boots up reboot into recovery and see if it changed recoveries although you should know when you fastboot flash if it went. It should tell you successful or fail.
Sent from my One using Tapatalk

Its pretty easy. first obviously make sure you have debugging enabled then Install this package http://forum.xda-developers.com/showthread.php?t=2317790
Then download a recovery IMG from the original dev section and put it in the same folder as where the minimal adb and fastboot package extracted too. Run the batch for minimal that opens a command prompt to that directory.
Type: adb devices(to make sure it sees your phone)
Next: adb reboot bootloader
Next: you will see bootloader options type: fastboot oem rebootRUU (it is case sensitive)
Next: wait for HTC logo on black background to show up and then type: fastboot flash recovery (IMG filename with extension. IE: twrp.IMG)
Example: fastboot flash recovery twrp.img
Next: fastboot reboot
After it boots up reboot into recovery and see if it changed recoveries although you should know when you fastboot flash if it went. It should tell you successful or fail.
Sent from my One using Tapatalk[/QUOTE]
Thank you! You rock! Will report back...just annoyed at this point because I can't flash anything, but I can't take update. Sort of stuck. Thank you for the short how to!

Hmmm...was just thinking, why am I flashing a recovery img? It's already running twrp. Am I just seeing if I can flash anything, at this point?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is where I am right now...anyone care to decipher lol

schilly said:
View attachment 2567052
View attachment 2567053
Here is where I am right now...anyone care to decipher lol
Click to expand...
Click to collapse
Yes just trying to see if it will take. If it takes then you have a hex edited custom hboot otherwise you will need to run fire water. That looks like stock firmware.
Sent from my HTC6500LVW using Tapatalk

[SOLVED]Friend messed up his phone-gave it to me to fix-seems to be stuck in fastboot

Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.

eboy_gb said:
Hi guys,
My friend has given me his HTC One M8 Bell to fix.
It's seems to be stuck in fastboot with S-ON
As far as I know, he had cyanogenmod and twrp installed and was trying to return his phone to stock (not sure why) and installed the wrong RUU.
How can I repair his phone?
I'm researching as best as I can, but everything I'm finding requires S-OFF and I doubt he has the BIN file....
Thanks in advance.
Click to expand...
Click to collapse
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.

Kyuubi10 said:
You shouldn't need S-OFF if you are using the correct RUU... so that could be the first thing you could try.
Another would be to unlock the phone through fastboot, then re-flash custom recovery... through custom recovery flash a nandroid of stock HTC Sense. Then through fastboot again flash stock recovery. Then wait for all the OTA updates to arrive.
Once you have installed all OTA updates you have two choices....relock the device, or use it stock while keeping the bootloader unlocked for future flashing goodness.
Click to expand...
Click to collapse
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....

eboy_gb said:
UPDATE - I got S-OFF back on the phone and booted into recovery. From there, I decided to simply reboot the system, but now I'm stuck at the Cyanogenmod splashscreen. So back to TWRP....
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
If you can access TWRP the download a nandroid of stock, and follow the advice I already gave above.
Flash stock nandroid 4.25/4.20, from TWRP, then from fastboot flash stock recovery.
Reboot and wait for OTA updates.

All is well, got the running properly now - thanks everyone!

eboy_gb said:
All is well, got the running properly now - thanks everyone!
Click to expand...
Click to collapse
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems

Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.

xunholyx said:
Incorrect. OS being empty was caused by a bug in some earlier versions of TWRP. Nothing to be too concerned about at all.
Click to expand...
Click to collapse
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Sent from my htc_m8 using XDA Labs

Kyuubi10 said:
Uhm....never knew it was an actual bug, i run across it once when i corrupted my system quite a few months.
Do u know the process to recreate the bug... Trying to see if it was the same bug which i experienced, or a variation thereof.
Click to expand...
Click to collapse
Corrupting system won't affect the OS number on the bootloader screen. "OS" is a bit misleading, it actually indicates the firmware number, not the ROM version.
The bug is easily reproduced by flashing certain TWRP versions (not sure exactly which ones). Its very common. We see this pop up by folks almost on a daily basis (OS number blank) especially folks using older TWRP versions.
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Kyuubi10 said:
Great!! Remember to add [SOLVED] in the title, so others know that here they can find solutions to common problems
Click to expand...
Click to collapse
Additionally, its not clear whether your suggestion is what actually worked for him (and exactly what nandroid build, etc.). OP should post the solution that worked, 1) for benefit of "helpers" like you, to confirm your fix is what worked; and 2) for the benefit of others that may run into the same issue.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
Kyuubi10 said:
Well...from what the image you pasted in the OP showed you had no system to reboot into. So that was definitely a wrong move.
Notice the OS - "empty space".....well that is not a good sign.
Click to expand...
Click to collapse
The phone would not boot since the bootloader was relocked. This is what happens when you relock by definition, as relocking expects RUU to be run.
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
eboy_gb said:
I don't really understand what RUU's are. The last HTC I had was Desire-Z....
Click to expand...
Click to collapse
RUU existing for the Desire Z (I had the same phone); and in fact for as long as HTC has been making Android devices.
RUU = ROM Update Utility
Its usually a Windows executable (although the zip format can be extracted to work with fastboot flash, or put right on an SD card) that will completely re-image the phone to stock firmware and software. You need to run the RUU that matches the phones carrier version (CID) and model (MID), and not all versions have RUU. Otherwise, the RUU will fail and not install anything.
RUU also requires a locked or relocked bootloader (although this requirement is bypassed with s-off).
RUU will also wipe any user data on the phone (including internal storage "media").

HTC M9- Can't Boot After Trying To Go Back To Stock

Hi everyone,
First of all thank you for taking the time to read my problem, and maybe trying to help.
I will try to describe with as many data and images what I have done, that led me to my problem, I hope it's not the end of my M9.
My original goal was to revert my M9 back to stock.
The M9 state before trying to achieve this was:
Root
S-OFF
TWRP Recovery installed
Unlocked Bootloader
cid 11111111
Custom Rom- Viperone M9 version 4.3.0
To revert to stock, I first tried RUU.EXE method.
This procedure always resulted in ERROR 155. After searching the forums, I understood that this sometimes happens because of the unlocked bootloader.
So using the Fastboot I relocked the bootloader. Unfortunately, that didn't help.
After that, I tried flashing RUU.ZIP via Fastboot.
I did several Fastboot commands after searching all forums. Everytime Fastboot command resulted in another error.
Unfortunately, during this process I did S-ON, and I this that because of that, I am currently stuck.
At the moment, the device doesn't manage to execute any command I try.
Also, it doesn't boot into the firmware, so I can't S-OFF again.
I'm afraid already (hope it's not too late) to continue other actions without assistance.
At the end of OP, you will find screenshots of
The current Bootloader Screen
The current Download screen
Result info of Fastboot command: "fastboot getvar all"
A link to the RUU.EXE I tried using
A link to the RUU.ZIP I tried using
To keep thing clear, any other image of actions will be uploaded to OP.
I would very very much appreciate help and advice.
I hope it's not too late, even if this whole thing doesn't succeed, I look forward learning more to prevent this from happening in the future.
Thank you.
Bootloader Screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Screen:
Fastboot getvar all:
RUU.EXE: https://www.dropbox.com/s/9kjf0u8h5iy8rdc/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe?dl=0
RUU.ZIP: https://www.dropbox.com/s/edzwftny23ldsiq/0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip?dl=0

Actions done according to information from this thread:

You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Sent from my HTC One M9 using Tapatalk

You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Click to expand...
Click to collapse
Hi, and thank you for your reply.
Can you please past a link to the thread so that I can be sure I'm following the correct one?
I tried flashing recovery, locking bootloader and flashing stock RUU, all resulting in error.
If you could be more specific about what exactly I should do, I would give you the respected result.
I'm not looking for someone to do the searching or work for me. I just want to be accurate about the actions I need to do and their results so that you I and other helpers would now the exact actions made and their results.
Thank you

http://forum.xda-developers.com/showthread.php?t=3132698
Sent from my HTC One M9 using Tapatalk

shivadow said:
You have to be "official" to go to stock or the ruu fails.
I dont think supercid helps either.. S-off shouldn't make a difference.
I think it's flash a stock backup, flash stock recovery,?? lock bootloader?? Flash stock ruu.
There are a few threads. I recommend flippy's thread.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
shivadow said:
http://forum.xda-developers.com/showthread.php?t=3132698
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
There are no instructions there. Only all sorts of files.
I have already been to that thread. The files are tried to flash are also from there.
Maybe I flashed the wrong files, or maybe I didn't do the steps properly, but in any case, I can't know from that thread since it is not described there.
Again, please be more specific about what are the steps, or anything else that I need to do.
Thank you

Did you even bother reading the OP of my thread? If you had you would have known where to find the instructions.
Sent from my HTC One S using XDA Labs

Flippy498 said:
Did you even bother reading the OP of my thread? If you had you would have known where to find the instructions.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Lol, I read every letter in the first post.
post 1: Opening post (no instructions)
post 2: TWRP backups (not relevant to me because I can't flash the recovery, again no instructions. Only files)
post 3: OTA Updates (again no instructions. Only files)
post 4: Stock Recoveries (again no instructions. Only files)
post 5: General Info (again no instructions. Only links to other threads regarding the info)
post 6: Useful links to downloads
Did I miss something?:laugh:

henengel said:
Did I miss something?:laugh:
Click to expand...
Click to collapse
Well, obviously you did.
From the OP:
Flippy498 said:
Please take a look at my google sheet if you want to get back to stock and don't know how to flash a RUU or how to correctly restore a TWRP backup. Although the sheet doesn't contain files for every existing firmware version the instructions can be used for every other RUU and TWRP backups that contain at least a Boot Image, the Stock Recovery and a System Image, too.
[...]
RUUs and useful links (e.g. instructions) can be found in the 6th Post.​
Click to expand...
Click to collapse
From Post #6:
Flippy498 said:
Flippy498's Google Sheet
Contains download links for all Back-to-Stock files he collected/created (RUUs, OTAs, official Firmware Packs, Stock Recoveries, Boot Images and TWRP Backups) and some instructions how to flash RUUs or how to Restore a TWRP Backup correctly, too​
Click to expand...
Click to collapse
Edit: Btw, if you don't want others to use your IMEI for scam you should remove it from your OP.

Flippy498 said:
Well, obviously you did.
From the OP:
From Post #6:
Click to expand...
Click to collapse
First of all thank you for pointing out the instructions.
Obviously, I did...
Just a suggestion, it would be very helpful if you could make the section stand out more, and be clearer that all steps and instructions are placed there.
I personally didn't understand that all of that is located there... again only my opinion.
I'll start right away and be back with all results and images...:good:

I actually prefer it the way it is now. That wasn't my thread from the beginning and I don't want to change too much of the original OP. Besides I don't like the tl;dr attitude (aka "OP? I see no reason why I should waste my time and read it!"-attitude) more and more user seem to have here on xda. You can do a lot of mistakes and ruin your phone in so many ways if you don't know what you're doing (this especially applies to S-OFF users) and this way people are forced to read the OP if they need help. (And maybe one or another user starts reading the basic information in post #5.)
Oh and for your own safety: Please take a look at the edit of my last post.

Flippy498 said:
I actually prefer it the way it is now. That wasn't my thread from the beginning and I don't want to change too much of the original OP. Besides I don't like the tl;dr attitude (aka "OP? I see no reason why I should waste my time and read it!"-attitude) more and more user seem to have here on xda. You can do a lot of mistakes and ruin your phone in so many ways if you don't know what you're doing (this especially applies to S-OFF users) and this way people are forced to read the OP if they need help. (And maybe one or another user starts reading the basic information in post #5.)
Oh and for your own safety: Please take a look at the edit of my last post.
Click to expand...
Click to collapse
I totally understand you...
That is indeed the common attitude...but if it doesn't stand out a bit, it is really easy to miss like I did.
There is a lot of information here, and it's very easy to miss 1 sentence, as I did.
But you are the creator, or in this situation the of the maintainer of the post, so obviously your opinion is what counts.
As far as one is concerned, I'm just appreciate very much and thank you for your help.:good:

Well after doing as the guide said (very easy), my M9 is up and running as normal.
Thank you so very much for your help and guidance.

[GUIDE] Safely set your bootloader back to "LOCKED" from "UNLOCKED" or "RELOCKED"

[GUIDE] Safely set your bootloader back to "LOCKED" from "UNLOCKED" or "RELOCKED"
*EDIT*
A percent of those that went S-OFF/LOCKED with SunShine 3.3.8 will have kernel flashing issues. We addressed this in 3.3.9 (released May 28th 2016 5PM PST).
Either go back s-on/unlocked and redo sunshine (may throw an error, if it does lmk and i can fix on server) or go s-off unlocked. This was one of those errors that only occurs on other people's phones, so it was a PITA to track down.
*EDIT*
HTC has made some changes into how the lock status are handled. The old methods are no longer safe, and can/will revert on you, or damage your device.
To deal with this we added a feature to SunShine to allow you to pick your bootloader status.
On the HTC 10 S-OFF LOCKED will behave the same as S-OFF UNLOCKED in addition to having all the S-OFF perks.
To get back LOCKED, make sure your phone is UNLOCKED and S-ON. Run SunShine, pick the "S-OFF LOCKED" Status, and let it complete.
At this point, if you want to go s-on, then you can flash your stock RUU and run "fastboot oem writesecureflag 3" in download mode.
We currently recommend the S-OFF LOCKED status, as S-OFF will force the device to behave unlocked anyways.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If I debranded from tmobile germany to wwe (....401..), did I have to go back to tmob or is it ok to set it s-on in wwe?
that I can go back to s-off with my license, I know

Does this work if one's already S-OFF/Unlocked?
First step would then be to set the secure flag to S-ON and run SunShine again, as I'd assume!? Am I right?
Thanks for taking your time and for your hard work on this great app.
Sent from my HTC 10 using XDA Labs

@jcase with S-off & locked option, will I still have to format data in TWRP after I s-off like with previous version?

Damn, I just bought a license and set S-Off with version 3.3.6 8 hours ago

Awesome, just what I've been waiting for on my 10!
Sent from my 2PS64 using XDA-Developers mobile app

Nice, for If and when I decide to go unlocked.

What would we do without some sunshine in our life? Thanks guys, sooo glad you are around. It's worth every penny and more. Thank you !

I have a German t-mob101. Is it currently possible to go s-off debranded and then back to s-on locked t-mob101? Considering that there is no RUU for it, I would only have a nandroid backup.

So when we have already "SunShined" the 10 to S-Off and unlocked we should simply lock the Bootloader with fastboot oem writesecureflag 3 and let SunShine do its job again?

wiQbold said:
If I debranded from tmobile germany to wwe (....401..), did I have to go back to tmob or is it ok to set it s-on in wwe?
that I can go back to s-off with my license, I know
Click to expand...
Click to collapse
Long as you are stock, it shouldnt matter
HTCNerdYoda said:
Does this work if one's already S-OFF/Unlocked?
First step would then be to set the secure flag to S-ON and run SunShine again, as I'd assume!? Am I right?
Thanks for taking your time and for your hard work on this great app.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
You have to go s-on before doing this. If you have no reason to go LOCKED, no reason to go through the hassle until you do.
mjh1978 said:
@jcase with S-off & locked option, will I still have to format data in TWRP after I s-off like with previous version?
Click to expand...
Click to collapse
Yes
bmwbasti said:
Damn, I just bought a license and set S-Off with version 3.3.6 8 hours ago
Click to expand...
Click to collapse
Doesnt matter, if you need LOCKED in the future, go s-on, and re-run sunshine, but wait until you need it.
amq said:
I have a German t-mob101. Is it currently possible to go s-off debranded and then back to s-on locked t-mob101? Considering that there is no RUU for it, I would only have a nandroid backup.
Click to expand...
Click to collapse
Yes, go stock first.
bmwbasti said:
So when we have already "SunShined" the 10 to S-Off and unlocked we should simply lock the Bootloader with fastboot oem writesecureflag 3 and let SunShine do its job again?
Click to expand...
Click to collapse
Yes but dont bother unless you need LOCKED, no point in going through the hassle at this point.

Wow, thx for your reply jcase.
I've just read that the license ist bound to the hardware (think motherboard) and can be reused.
So "until you need it" apparently means in terms of warranty?
Or is there another reason where locked is really needed?

jcase said:
Yes but don't bother unless you need LOCKED, no point in going through the hassle at this point.
Click to expand...
Click to collapse
Well, I got S-Off but haven't really done much with the phone yet, so RUU'ing, going back to S-On and re-running SunShine to set bootloader to LOCKED right now seems less of a hassle than doing it in the future when things need to be backed up.
However, I'm somewhat paranoid about going back to S-On. I remember than on M7 / M8 / M9 it was generally not recommended as there was at least a theoretical possibility that an RUU would not return the phone to a completely stock state and you'd get a hard brick on first boot. Is this no longer a concern?
Also, I seem to have a vague recollection that flashing an RUU zip from external was preferred to just running an executable RUU from a PC, as the latter might still skip some partitions under certain conditions. True / false?
Lastly, does this thread basically mean that the good old way of changing the LOCKED and TAMPERED / Software Status: Modified flags (M7 LOCKED, M8 LOCKED, M8 TAMPERED, M9 LOCKED, M9 SS:Modified) isn't safe on HTC 10? Also, does the SS:Modified flag even get triggered on HTC 10 when S-Off?

It is still not recommended to go s-on.
I would just stay s-off/unlocked for now no point
Kisakuku said:
Well, I got S-Off but haven't really done much with the phone yet, so RUU'ing, going back to S-On and re-running SunShine to set bootloader to LOCKED right now seems less of a hassle than doing it in the future when things need to be backed up.
However, I'm somewhat paranoid about going back to S-On. I remember than on M7 / M8 / M9 it was generally not recommended as there was at least a theoretical possibility that an RUU would not return the phone to a completely stock state and you'd get a hard brick on first boot. Is this no longer a concern?
Also, I seem to have a vague recollection that flashing an RUU zip from external was preferred to just running an executable RUU from a PC, as the latter might still skip some partitions under certain conditions. True / false?
Lastly, does this thread basically mean that the good old way of changing the LOCKED and TAMPERED / Software Status: Modified flags (M7 LOCKED, M8 LOCKED, M8 TAMPERED, M9 LOCKED, M9 SS:Modified) isn't safe on HTC 10? Also, does the SS:Modified flag even get triggered on HTC 10 when S-Off?
Click to expand...
Click to collapse

jcase said:
It is still not recommended to go s-on.
I would just stay s-off/unlocked for now no point
Click to expand...
Click to collapse
Gotcha. Well, I'm still within the return period, so if I were ever to go back to LOCKED, now seems to be the time.
Any comment on the preferred way to RUU (zip vs exe), the old way of flag resetting with adb echo and triggering of the Modified flag on HTC 10?

Kisakuku said:
Gotcha. Well, I'm still within the return period, so if I were ever to go back to LOCKED, now seems to be the time.
Any comment on the preferred way to RUU (zip vs exe), the old way of flag resetting with adb echo and triggering of the Modified flag on HTC 10?
Click to expand...
Click to collapse
RUU will clear tamper flag. HIGHLY HIGHLY recommended to not try to do that manually.
--beaups

beaups said:
RUU will clear tamper flag. HIGHLY HIGHLY recommended to not try to do that manually.
--beaups
Click to expand...
Click to collapse
Right, but are you advising against writing the tamper flag value as a general recommendation for all HTC One iterations or is that a new thing unique to HTC 10? Couple posts above I linked the M8 / M9 threads for doing exactly that, didn't seem to have any negative side effects.
My other question was regarding what actually triggers the tamper flag on the 10. I remember couple of weeks ago @Captain_Throwback was saying that it doesn't even get tripped when S-Off, again unlike the way it worked on M8 / M9.

Kisakuku said:
Right, but are you advising against writing the tamper flag value as a general recommendation for all HTC One iterations or is that a new thing unique to HTC 10? Couple posts above I linked the M8 / M9 threads for doing exactly that, didn't seem to have any negative side effects.
My other question was regarding what actually triggers the tamper flag on the 10. I remember couple of weeks ago @Captain_Throwback was saying that it doesn't even get tripped when S-Off, again unlike the way it worked on M8 / M9.
Click to expand...
Click to collapse
S-OFF isn't what tripped that flag on those other devices either....it never has been. Which is why running an RUU clears it.

Captain_Throwback said:
S-OFF isn't what tripped that flag on those other devices either....it never has been. Which is why running an RUU clears it.
Click to expand...
Click to collapse
Guess I didn't word my interpretation of your statement unambiguously. I meant that I think you said that on the 10, after gaining S-OFF, nothing trips the tampered flag. This is unlike having S-OFF on M8 / M9, where the tampered flag could still be tripped after gaining S-OFF.

Kisakuku said:
Guess I didn't word my interpretation of your statement unambiguously. I meant that I think you said that on the 10, after gaining S-OFF, nothing trips the tampered flag. This is unlike having S-OFF on M8 / M9, where the tampered flag could still be tripped after gaining S-OFF.
Click to expand...
Click to collapse
I couldn't trip that flag after S-OFF on those devices. You sure about that?
If it was tripped prior to S-OFF, I don't think S-OFF would clear it (though I'm not sure about that), but if it was official prior to S-OFF, it wouldn't get tripped afterwards, at least not in my experience.