Of course yes! Though I don't think you'll be denied OTAs if you at least have a stock ROM and stock recovery with S-OFF
Don't quote me on it though lol 
[GUIDE] Return your European M8 to 100% Stock - S-OFF REQUIRED
- Thread starter EddyOS
- Start date
Of course yes! Though I don't think you'll be denied OTAs if you at least have a stock ROM and stock recovery with S-OFF
Don't quote me on it though lol Of course yes! Though I don't think you'll be denied OTAs if you at least have a stock ROM and stock recovery with S-OFF
Ok. So stock recovery is required for OTA as well?
As I understand it yes, perhaps @EddyOS could help more on that or correct me if I'm wrong on it. Though that's how I understand it
Then perform a nandroid backup, this will backup also the stock HTC recovery that is needed in combination with the stock nandroid backup to be able to recieve official HTC OTA's
http://xdaforums.com/showthread.php?t=2701376
Mr Hofs Collection of stock backups etc It's stated as above in the first post.
You will need to have the stock recovery for OTA updates, but flashing the FW package restores the stock recovery so you're good to go
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Hey there.
I want to return my M8 to warranty repairs and therefore have to return to stock.
I have CID H3G_001, root, unlocked, and S-OFF.
I have found the stock H3G__001 nandroid backup and I understand that I have to flash that and so on.
What I do not understand is related to the S-OFF flag. Do I HAVE to make the phone S_ON to get warranty repair?
What happens if I make the phone S-ON? Am I not able to make it S-OFF again?
Thanks!
ok, but if they were to check and it would be S-OFF, would it mean that the warranty would be void?
Also, what happens if I S-ON before sending? Does it mean that I cannot S-OFF again?
1. Some phones go out S-OFF so they shouldn't care
2. If you got S-OFF once you should be able to get it again. As you don't have an unbranded phone this guide doesn't fully apply as the firmware isn't for your device. I'd use the backup available and then flash the stock recovery, lock the bootloader and remove tampered if you need to but otherwise leave it S-OFF
I have some first hand knowledge on this. You should most certainly go back to s-on. I had some dead pixels and called HTC. They offered to replace my phone. I had to pay $19 for shipping both ways through HTC. I had to send my phone to them, then they would inspect it and send me a new phone. I returned to stock except I left it s-off. Well.... After they received my phone, I got an email saying in order for them to go on I would have to pay $140. To make a long story short, it was because of s-off. I did get them to replace it for free, but it took much lying and arguing.
Now... The problem is, getting s-on is not the easy. Well, it's easy to do... But it doesn't work every time from what I'm getting. So, try to go back to s-on if you can.
Sent from my One using Tapatalk
Can you please elaborate (or link some topics) why it doesn't always work? This is the first time I hear this.
Thanks. :good:
Thanks. :good:
Well I read it somewhere that the fastboot oem writesecureflag 3 is hit or miss. It may or may not work. I haven't tried and I haven't gotten my m8 back yet to test it. It's just not guaranteed to work. That's all I know. I don't remember where I read it. Might have been m7 forums.
Sent from my One using Tapatalk
It's not that it's hit and miss, it's that if you're not 100% stock it can brick the phone. As for going back to S-ON, I didn't when I sent my Sensation and Desire to HTC for repair, both were fixed and sent back FOC under the warranty. Might be different elsewhere but a hardware fault isn't caused by S-OFF
No a hardware fault is not caused by s-off but it does void the warranty. I had to plead and beg them to replace my phone without charging me. S-off cannot cause dead pixels, but they didn't care. The person that inspected my phone took pictures of the bootloader with s-off. I think it depends on who inspects the phone. This happened just this week.
Sent from my OnePlus 7a
Must be different in the US to the UK, our Laws protect the buyer and a software change that cannot cause a hardware fault cannot be used to void warranty. HTC have never had an issue with repairing my past phones and even if they did, the retailer has a duty to replace a device not working correctly. If you can set back to S-ON confidently then by all means do so, but you then take the risk of bricking the phone (and HTC would then probably replace it as it no longer turns on!)
Yes I've read that before. Must be nice! Your government cares about you more than ours for sure!
If your sending for repkaxment through a carrier no issues. I've sent phones back to AT&T with custom Rom still on and custom recovery and no issues. Now if ur sending back to HTC themselves, well that could be different as some users have pointed out. Luck of the draw I guess with HTC. With phone carriers though or third party warranty companies, I think they hardly check that stuff or care. Then again this was about 2 years ago, don't know if things have changed since?
If carrier then I'd try to at least have stock Rom and no root and stock recovery before sending.
Worst comes to worst throw phone in microwave for 30sec and its literally dead. Dead phones tell no tales!
If carrier then I'd try to at least have stock Rom and no root and stock recovery before sending.
Worst comes to worst throw phone in microwave for 30sec and its literally dead. Dead phones tell no tales
!
That's strange, it was removed after a reboot for me. I'm afraid I don't know what to do in that case
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
108*** I HAVE SOLD MY M8 BUT I WILL TRY AND KEEP THIS UP-TO-DATE WHEN NEW RUUs COME OUT ***
*** NEW GUIDE AS WE NOW HAVE AN RUU!!! ***
This guide is for Windows-only. The reason for this is because the htc_fastboot file used is a Windows binary and there doesn't appear to be a version for Mac/Linux
This guide will allow you to return your EU, unbranded M8_UL device to 100% stock (inc. locking the bootloader and removing the tampered flag) for resale purposes or to return to HTC. It does not cover carrier-branded handsets and does require you to be S-OFF but Step 3 can be done on an S-ON EU M8 so long as your bootloader is relocked and you match one of the CIDs listed below. A lot of this can be used to restore a US carrier M8 as the RUUs are available, though, but you'd have to get the relevant RUU.zip from the EXE (which is very easy)
This process applies to the following CIDs:
HTC__001
HTC__102
HTC__203
HTC__E11
HTC__405
HTC__Y13
HTC__304
HTC__A07
HTC__032
HTC__J15
HTC__016
HTC__M27
HTC__K18
HTC__A48
HTC__002
You need the following files stored in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (renamed to ruu.zip - not ruu.zip.zip!)
md5:4e03845aeab375746b4553e610047680
htc_fastboot.exe - *** REMOVED DUE TO HUGE AMMOUNTS OF SPAM REQUESTS ***
md5: 7343C5BCEC64373F83D69BD074954759
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (renamed to recovery.img) md5:
e51c6ce8db0b7318ef31e1e7bd03c96e
And you'll also need HTC Sync Manager - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it for the drivers and then uninstall it but leave the drivers on your PC)
All commands in bold are to be done in a command prompt window in your fastboot folder
1. 'Lock' the bootloader and reset the tamper flag
We know we can relock the bootloader by using the command 'fastboot oem lock', but it will show 'RELOCKED' on the bootloader and still show the phone has been unlocked in the past. With S-OFF we can set it back to 'LOCKED'. To do this, we need to use TWRP and adb shell
Flash TWRP in the usual manner by connecting the phone to the PC whilst in the bootloader and flash by using the command fastboot flash recovery recovery.img. Once flashed, boot the phone into TWRP and connect to your PC and make sure the drivers are successfully installed. To confirm it's working type adb devices and it should be listed with your devices serial number. Assuming you can see the device, we can now use adb shell to change the flag from 'UNLOCKED' to 'LOCKED' by using the following commands:
adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Once the command has finished, we can continue using adb shell to reset the tamper flag by using the following command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
Once this has finished, we can exit out of adb shell by simply typing exit. Then reboot the phone into the bootloader through the menu in TWRP so we can confirm the flags are set back to stock.
2. Change the CID (if required)
Now we're in the bootloader and are 'LOCKED' and not listed as modified (but still S-OFF) it's best we reset the CID so moving forward things are easy. To do this, you just need to use fastboot oem writecid HTC__001, or whichever CID your device originally came with from the list at the beginning of this guide. Once you've reset the CID, reboot the bootloader to confirm the changes using fastboot reboot-bootloader
3. Flash the RUU
We are now at the point where we can flash the RUU and restore the phone to 100% stock. To do this, we first need to boot the phone into RUU mode using the command fastboot oem rebootRUU. Once in RUU mode, you'll see a silver HTC logo on the phone and that's it. At this point, we now use the HTC fastboot package to flash their RUU.zip file using the command htc_fastboot flash zip ruu.zip. This process will take a few minutes, and the phone will reboot a few times but once done it'll say complete. At this point, reboot the phone back to the bootloader using fastboot reboot-bootloader
4. Factory reset the device *** OPTIONAL ***
Having flashed the RUU, I always prefer to do a factory reset to make sure everything is in order. To do this, boot into the stock recovery and once at the black screen hold volume up and press power to get into the menu and then select 'wipe data/factory reset' using the volume buttons and use power to select the option.
5. Reboot the phone
Pretty obvious this - just select 'reboot system now' and you should be good to go!33
That's the stock recovery, press vol up and power to get into the menu
And yes, you'll get the OTA
