Develop Bugs

I cracked my screen, ok to send it in rooted?

So the phone is currently rooted and running a GPE rom, would it be ok if i sent it in like that for repair?? or should i return it to stock?

Well i hope you had the logic thought yourself that completely stock is the best. It's about your screen so it shouldn't matter.....but on the other hand, why take the risk ?

Mr Hofs said:
Well i hope you had the logic thought yourself that completely stock is the best. It's about your screen so it shouldn't matter.....but on the other hand, why take the risk ?
Click to expand...
Click to collapse
yup, thats what i was thinking its just getting repaired nothing else, im just gonna return it back just in case.

Are you trying to use the free replacement? In that case definitely go back to stock and locked bootloader and remove tampered banner
Sent from my HTC One_M8 using XDA Free mobile app

otariq said:
Are you trying to use the free replacement? In that case definitely go back to stock and locked bootloader and remove tampered banner
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
hey thanks for the reply man, i read back on the shattered screen thread, a guy mailing it in rooted running a custom rom, please read and tell me what your think, im really considering just doing that.
iNiREALiZED said:
Just thought I'd share my experience for anyone else wondering. I originally sent my phone in a week ago. Did the express option. After shipping the phone back received an email about two days later with the title" Your HTC quotation is ready". After clicking the link I see a that the quote is for $290, and the reason is illegal software.
Before sending my phone off all I did was a wipe. My phone was sent unlocked and rooted with ARHD 8.0 Rom and TWRP still intact. I called HTC the next day and filed a "quotation dispute ticket". They asked my reason and I said basically the screen was cracked due to physical damage and clearly no software installed on the phone had any impact on that. Got a call last Thursday (July 3rd) from an HTC repair manager. He apologized for the inconvenience and stated that after reviewing the phone he could see that it was unlocked but was still running HTC Sense rom, and was not overclocked or altered in other ways. Due to this they would honor the screen replacement. Got an email this morning saying the phone was sent out next day air, and should receive tomorrow afternoon.
Thanks HTC! I think the main issue they see is people installing GPE based roms or overclocking. It seems pretty standard that any unlocking will automatically red flag the phone and shoot out an automated quotation email for the $290. I think simply opening the dispute has someone take a deeper look into your issue and more times and none HTC will honor the replacement.
Hope this helps!:fingers-crossed:
Click to expand...
Click to collapse

HRodMusic said:
hey thanks for the reply man, i read back on the shattered screen thread, a guy mailing it in rooted running a custom rom, please read and tell me what your think, im really considering just doing that.
Click to expand...
Click to collapse
up to you mate - but why take the risk for a quick return to stock?
you'll see other people in that same thread have had huge problems trying to get repair under warranty.

cr1960 said:
up to you mate - but why take the risk for a quick return to stock?
you'll see other people in that same thread have had huge problems trying to get repair under warranty.
Click to expand...
Click to collapse
I want to return it back to stock, but im not 100% on the steps i should take, and I currently dont have a Windows machine to work on, i could borrow one later today.

First remove the tempered flag then return bootloader to LOCKED not relocked and finally run the ruu to get full stock unrooted
Sent from my HTC One_M8 using XDA Free mobile app

otariq said:
First remove the tempered flag then return bootloader to LOCKED not relocked and finally run the ruu to get full stock unrooted
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Same old same old....now i ask you which ruu !? Do you know if its there. Do you have a 2.22.401 international ruu (if he is on that official main) ? No because its not there. All available ruu's are for sprint/Verizon/tmobile....so stop referring to ruu's in the international forum !
For the OP
Check my nandroid backup thread

Mr Hofs said:
Same old same old....now i ask you which ruu !? Do you know if its there. Do you have a 2.22.401 international ruu (if he is on that official main) ? No because its not there. All available ruu's are for sprint/Verizon/tmobile....so stop referring to ruu's in the international forum !
For the OP
Check my nandroid backup thread
Click to expand...
Click to collapse
Oh that's my fault I didn't know there wasn't one for international version.
Sent from my HTC One_M8 using XDA Free mobile app

Mr Hofs said:
Same old same old....now i ask you which ruu !? Do you know if its there. Do you have a 2.22.401 international ruu (if he is on that official main) ? No because its not there. All available ruu's are for sprint/Verizon/tmobile....so stop referring to ruu's in the international forum !
For the OP
Check my nandroid backup thread
Click to expand...
Click to collapse
So i should remove the tempered flag then return bootloader to locked, after all that flash one of your nandroid backups? i have an ATT device btw.

Check your software number and cid. That's first to know ! Then compare and check if there is a matching nandroid or ruu (for AT&T) gather your information first. And NEVER relock/lock your bootloader before you know what you are doing. In regarding of restoring a nandroid backup relocking/locking the bootloader is the very LAST step you take in the process.

Mr Hofs said:
Check your software number and cid. That's first to know ! Then compare and check if there is a matching nandroid or ruu (for AT&T) gather your information first. And NEVER relock/lock your bootloader before you know what you are doing. In regarding of restoring a nandroid backup relocking/locking the bootloader is the very LAST step you take in the process.
Click to expand...
Click to collapse
Thanks, i know how to get the CID but where do i find the software number?
It has to be one of this two.
{
"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"
}

You can check in the settings menu - about - software the version you are running now. If the 502 is the same you can take any of those 2 with the matching stock recovery and even perform ota again. You can also check in the AT&T threads if there is a ruu available. But without s-off you can't downgrade the hboot. With a nandroid backup you can, because the hboot will be untouched and you "just" run a lower software.

Mr Hofs said:
You can check in the settings menu - about - software the version you are running now. If the 502 is the same you can take any of those 2 with the matching stock recovery and even perform ota again. You can also check in the AT&T threads if there is a ruu available. But without s-off you can't downgrade the hboot. With a nandroid backup you can, because the hboot will be untouched and you "just" run a lower software.
Click to expand...
Click to collapse
I dont see that, im guessing its because im running GPE, so just picking the correct one will flash back to 100% stock even recovery?

Check your main and cid via fastboot commands. Described in the OP of my backup thread.

Recently sent my phone in for an exchange. Set to complete stock, locked bootloader, and unrooted. Happy to say I got my phone back in a week.

BlackAlien92 said:
Recently sent my phone in for an exchange. Set to complete stock, locked bootloader, and unrooted. Happy to say I got my phone back in a week.
Click to expand...
Click to collapse
Hey there ! Did you get a brand new one or a refurbished one or the same one you sent ?

Tej XFire said:
Hey there ! Did you get a brand new one or a refurbished one or the same one you sent ?
Click to expand...
Click to collapse
From what I can tell it looks brand new. Completely flawless. [emoji4]

Can't install ROM or update

I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.

kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks

The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.

Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"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"
}

grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.

kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work

Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.

kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?

Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks

grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU

Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.

Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11

kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:

Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.

I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?

kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier

[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.

[HTC M8] Unable to update firmware :(

Hello, guys!
I write here for help as HTC's customer support can't help me!
As title tell you I am unable to update firmware.
Everytime I receive notification that an update is available and that I should update my firmware.
Unfortunely, I get error
Screenshot:
{
"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"
}
To be honest, I am using original version and didn't even tried another version on my HTC
Practically, I don't understand why currently version which I never changed can tell me that I am using a modified version
In order to solve this problem I tried to factory reset, but without any success
Would be very glad if someone could help me!
Thank you!
EDIT: I am sorry for my worst English! I hope you understand what I wrote here. Thanks!

Winserity said:
To be honest, I am using original version and didn't even tried another version on my HTC
Practically, I don't understand why currently version which I never changed can tell me that I am using a modified version
Click to expand...
Click to collapse
The phone's software has almost certainly been modified, if not by you then a previous owner or seller. What was the condition of the phone when you bought it (from another user, 3rd party vendor, etc.)?
We'll need a lot more info, in order to help you. Do you know how to use fastboot?
Do you know how to get to the bootloader screen? If so, does it say UNLOCKED, LOCKED or RELOCKED near the top?
Does it say s-on or s-off?
What number does it say for OS number? If nothing, what does it say for hboot number and radio baseband number?
Winserity said:
In order to solve this problem I tried to factory reset, but without any success
Click to expand...
Click to collapse
Factory reset won't do anything in this case. Factory reset just wipes user data, and doesn't touch the OS/system.
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
Winserity said:
I am sorry for my worst English! I hope you understand what I wrote here. Thanks!
Click to expand...
Click to collapse
Your English is fine so far! :good:

redpoint73 said:
The phone's software has almost certainly been modified, if not by you then a previous owner or seller. What was the condition of the phone when you bought it (from another user, 3rd party vendor, etc.)?
We'll need a lot more info, in order to help you. Do you know how to use fastboot?
Do you know how to get to the bootloader screen? If so, does it say UNLOCKED, LOCKED or RELOCKED near the top?
Does it say s-on or s-off?
What number does it say for OS number? If nothing, what does it say for hboot number and radio baseband number?
Factory reset won't do anything in this case. Factory reset just wipes user data, and doesn't touch the OS/system.
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
Your English is fine so far! :good:
Click to expand...
Click to collapse
My sister bought it as a gift new HTC M8 from Amazon Store United States.
Bootloader screen give me this information:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015,22:51:08.1

Winserity said:
My sister bought it as a gift new HTC M8 from Amazon Store United States.
Bootloader screen give me this information:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OS-4.16.401.10
Click to expand...
Click to collapse
The phone is definitely not in factory stock condition. It's highly modified, having had it's bootloader unlocked, s-off, and made SuperCID. Possibly (probably?) modified by the seller, in order to remove any region or carrier branding.
You can probably use the Euro RUU to update the OS software/firmware. Use the instructions and files from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I'd have to see more info to be sure. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
The phone is definitely not in factory stock condition. It's highly modified, having had it's bootloader unlocked, s-off, and made SuperCID. Possibly (probably?) modified by the seller, in order to remove any region or carrier branding.
You can probably use the Euro RUU to update the OS software/firmware. Use the instructions and files from here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
I'd have to see more info to be sure. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
Is this step required if I have S-OFF and UNLOCKED?
I am sorry for asking such dumb asks! I just want to be sure at all!
EDIT:
Look there

Winserity said:
Is this step required if I have S-OFF and UNLOCKED?
I am sorry for asking such dumb asks! I just want to be sure at all!
Click to expand...
Click to collapse
It's not a dumb question. Others have been confused by the wording in the guide regarding relocking the bootloader.
You do not need to relock the bootloader. S-off bypasses the requirement for bootloader to be locked/relocked when running RUU. In other words, with s-off the RUU will run fine regardless of whether the bootloader is unlocked or locked.
I recommend you leave the bootloader unlocked, as it gives you more options if anything goes wrong.
Thanks for posting the getvar data. Either you knew how to do that already, or you are learning quickly! The info confirms that you should be able to use the RUU. It also appears to have been the US T-Mobile version (model ID 0P6B13000) that was modified to remove the carrier branding, and "convert" it to Euro version.

Unfortunately, I am unable to extract from RUU zip
I receive this kind of error
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: The archive is corrupt
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: Checksum error in C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed\dzdata_32g.img. The file is corrupt
EDIT:
Used function "Repair archive" and I am able to extract.
If there will be new information regarding my issue I will post there
EDIT 2:
After "FAILED" it automatically restart the same procedure
Still waiting for about 25-30 minutes
Is this ok?
EDIT 3:
To be honest, I am feeling scared x(
Can someone confirm that my phone isn't broke?
It's still showing "send `zip` ... (1687274KB)" more than a hour
Why is it taking too long?

Update:
Used OS Windows 7 and I flushed this RUU, but after fastboot reboot my HTC doesn't seems to switch on Android
Screenshot:
Right now, my HTC stucks at a white screen where is shown HTC One logo
Maybe it sounds dumb, but I can't even switch off phone.
I am able only to restart phone using Power + Volume UP
No any setup started after fastboot reboot

Winserity said:
Unfortunately, I am unable to extract from RUU zip
I receive this kind of error
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: The archive is corrupt
C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip: Checksum error in C:\Users\xxevi\Desktop\0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed\dzdata_32g.img. The file is corrupt
EDIT:
Used function "Repair archive" and I am able to extract.
Click to expand...
Click to collapse
It doesn't say anywhere in the instructions to extract anything! Follow the instructions exactly, and don't make up steps!
The zip is an encrypted archive. It's encrypted with HTC's encryptions keys, and there is no way for you to decrypt it (and there isn't any reason to!). That is why Windows thinks it is "corrupt" - but don't worry it isn't. You just flash the RUU, as is, and it will do the rest. Extracting anything will break the signature, and cause it to fail signature check (will not install).
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
Error 90 is normal. It needs to be run twice as indicated. The message "flush again immediately" is a strange typo which HTC has maintained over numerous RUUs on different devices - it should say "flash again immediately. You need to run the command again to flash the RUU zip.
It's not completely clear for your description, if you extracted anything from the RUU zip and tried to flash it. Hopefully you didn't. Please describe in full detail, all the steps you performed, with the exact file names, commands, etc.

In the final I didn't extracted archive ZIP. But as you said I tried to repair archive cause I saw "The file is corrupt."
Anyway, I gave my HTC to one of my friend working right now on my HTC.
Tomorrow I will let you know if my problem is solved
Until that time I have to tell you thank you very much!
I really appreciate your attention to my issue

Winserity said:
Anyway, I gave my HTC to one of my friend working right now on my HTC.
Tomorrow I will let you know if my problem is solved
Click to expand...
Click to collapse
Do you have reason to believe your friend has more knowledge of this specific device than we do (or you doing the steps, with our guidance)?
Because HTC devices can be very nuanced (lots of differences from other Android devices). If he doesn't have specific experience with HTC devices (and even better, the M8 specifically) he might not be able to help, or even make the problem worse.

My friend solved problem by installing firmware version 6.12.1540.4
He used a ROM utility to solve this problem.
Wasn't easy for him at all, but in final I am glad
Now, I have last version installed for my HTC M8
Thanks for your help, redpoint73!
Wish everyone to avoid HTC phone problems =)

Hi all please I do need help on this same issue. I cannot install updates. I get the msg I am using a modified version of the software. Even though I never modified it myself but bought it that way, I tried to unroot it with an app I installed, but it says it's not even rooted. My phone is HTC Desire Eye and it's presently running on 4.4.4 Kitkat. Your assistance will be appreciated. Also I am less of a technical guy, so pls guide me on every step I may need to solve this like a newbie.
Thanks guys!

Temp S-OFF for HTC U12+

S-OFF is out now for HTC U12+ with Sunshine
{
"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"
}
https://twitter.com/TheRootNinja/status/1017891591531343872
https://twitter.com/firewaterdevs/status/1017152637433761795
https://forum.xda-developers.com/showpost.php?p=77066052&postcount=249

That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!

MNoisy said:
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
Click to expand...
Click to collapse
Starting from the HTC U11, you can't permanently S-OFF the device (SunShine never achieved it for the U11). You can find a complete explanation here:
https://forum.xda-developers.com/u11/how-to/s-off-word-t3662712/post73543715

MNoisy said:
That is great! Thank you!
Could you explain a bit more about the "temp" nature at this point and why someone would need the temp solution right now before you guys figure out the permanent way?
Great work!
Click to expand...
Click to collapse
Razorbacktrack5535 said:
Starting from the HTC U11, you can't permanently S-OFF the device (SunShine never achieved it for the U11). You can find a complete explanation here:
https://forum.xda-developers.com/u11/how-to/s-off-word-t3662712/post73543715
Click to expand...
Click to collapse
In addition: it has all the same features as permanent S-OFF, with exception of the ability to use custom hboot/aboot. Once you reboot into Android or Recovery, the device will reset back S-ON, so be careful what you do, once you achieved S-OFF.
Permanent S-OFF is to dangerous - and much more risky - on those new devices as the U11 and all more recent ones.

5m4r7ph0n36uru said:
In addition: it has all the same features as permanent S-OFF, with exception of the ability to use custom hboot/aboot. Once you reboot into Android or Recovery, the device will reset back S-ON, so be careful what you do, once you achieved S-OFF.
Permanent S-OFF is to dangerous - and much more risky - on those new devices as the U11 and all more recent ones.
Click to expand...
Click to collapse
Thank you for that information!
So for the basic essential customizers like me, I would start using this when we start getting some custom ROM's if they are unsigned, to change my model, install TWRP, or if I need supercid?

MNoisy said:
Thank you for that information!
So for the basic essential customizers like me, I would start using this when we start getting some custom ROM's if they are unsigned, to change my model, install TWRP, or if I need supercid?
Click to expand...
Click to collapse
Wouldn't recommend SuperCID anymore, as you won't be able to receive OTAs any longer - yes they changed that as well. S-OFF is only needed to change CID and thus the specific software you're running, or to flash unsigned firmware. No more no less to it actually.
And there's no actual recovery partition anymore, due to treble. Instead stock recovery shares its partition with the respective boot.img. Thus I guess TWRP might be flashed as recovery_ramdisk, or as a TWRP patched boot image - we'll see when it's out and available though.
Sent from my HTC U11 using XDA Labs

S-off gives you complete control over YOUR device. You don't necessarily need to receive OTA's if you're S-off. You can flash your firmware on your schedule, not when the carrier or manufacturer says it's ready. Flash it when you're ready. Flash what you want, when you want. If the option is there, I'm getting S-off every time.
Do your homework, research and learn. If you're too lazy to do your due diligence, don't S-off. You can truly brick your phone if you're not 100% sure of what you're doing.
If you're going to just flash ROMs or just get root access but stay stock otherwise, no need to S-off. If you want complete control over flashing everything , go S-off.
But remember with great power comes great responsibility.

Beyond flashing random firmwares willy-nilly, what's the actual point of this when all U12+ ships unlocked (at least here, in the US)...? I really don't see any reason now.

szlevi said:
Beyond flashing random firmwares willy-nilly, what's the actual point of this when all U12+ ships unlocked (at least here, in the US)...? I really don't see any reason now.
Click to expand...
Click to collapse
if there is a temp root solution u can have a completely bootloader locked saftey net passing rooted device, also the us unlocked devices just mean the sim card is unlocked for whatever carrier you want to use not bootloader unlocked

Hi! I can't to obtain s-off.I bought license via app Sunshine, but when the process begins (Sunshine will now set your device S-OFF) my phone no reboot and no to obtain s-off.
I have 1.15.401.4,unlocked,rooted.
May this need to make with LOCKED status?
Help me pls.
Sorry my english

JR 2007 said:
Hi! I can't to obtain s-off.I bought license via app Sunshine, but when the process begins (Sunshine will now set your device S-OFF) my phone no reboot and no to obtain s-off.
I have 1.15.401.4,unlocked,rooted.
May this need to make with LOCKED status?
Help me pls.
Sorry my english
Click to expand...
Click to collapse
You need to be sure you went to HTC Dev and unlocked your bootloader first. After that you need to be rooted.
If you have both of those steps done and you're getting errors, go to: https://therootninja.zendesk.com/hc/en-us and check out how to troubleshoot, and send in a support ticket.
These guys are awesome, jcase and beaups are super legit and are always willing to help with their software. Good luck

Granite1 said:
You need to be sure you went to HTC Dev and unlocked your bootloader first. After that you need to be rooted.
If you have both of those steps done and you're getting errors, go to: https://therootninja.zendesk.com/hc/en-us and check out how to troubleshoot, and send in a support ticket.
These guys are awesome, jcase and beaups are super legit and are always willing to help with their software. Good luck
Click to expand...
Click to collapse
Thank you)

also make sure you are on the stock kernel it doesnt like freak07's

kickyoace said:
also make sure you are on the stock kernel it doesnt like freak07's
Click to expand...
Click to collapse
Sunshine S-Off isn't working for me either, the orange progress bar completes multiple times until it finally reboots but it just boots back up into the ROM. I am on cleanslate kernel, maybe that is the issue?

LibertyMonger said:
Sunshine S-Off isn't working for me either, the orange progress bar completes multiple times until it finally reboots but it just boots back up into the ROM. I am on cleanslate kernel, maybe that is the issue?
Click to expand...
Click to collapse
Seems like I needs to have the stock kernel

mammothjojo88 said:
Seems like I needs to have the stock kernel
Click to expand...
Click to collapse
Yes, this was exactly the problem. I restored stock kernel and it worked first try. Thanks.
---------- Post added at 01:22 PM ---------- Previous post was at 12:32 PM ----------
Temp. S-Off helped me to fix my Slot b, it seemed slot b was corrupt, it wouldn't boot as if there wasn't a ROM on it so reverting back to the old 1.15 ROM and taking the 1.21 OTA seemed to fix it. Seemless updates worked and i am currently back on slot b finally. I tried everything beforehand and nothing would work except this.

Thanks, used sunshine to convert u12+ china to emea ROM

answer from the support:
HTC designed the u12+ to only support temp s-off, all phones after and including the 11 have been this way

I tried to achieve S-Off with 1.30.401.2 but it takes more than 10 minutes and afterwards the phone boots into the system and not bootloader/download mode. Any thoughts?

mdxdave said:
I tried to achieve S-Off with 1.30.401.2 but it takes more than 10 minutes and afterwards the phone boots into the system and not bootloader/download mode. Any thoughts?
Click to expand...
Click to collapse
I just tried it on 1.30 and it is working for me. I have no advice other than that, sorry.