Database Develop

[Q]Reverting to stock firmware (three) and stock ROM (s-off)

Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.

Ardmanz said:
Hey guys,
Right, I have a hardware issue with my phone so need to return it to Three UK.
Currently I have Android Revolution HD 11 on my phone and have updated to 2.17 firmware, s-off.
So I need stock, firmware to be reverted to 1.28.771 and to change my CID to H3G__001 (currently HTC__001). There doesn't appear to be an RUU for three.
First off I'm assuming the H3G nandroid backup in the "[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads" thread doesn't actually touch the firmware so it would remain at 2.17?
So my thinking is this:
Flash the generic europe RUU (do I need to lock my bootloader before doing this)? (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe)
Change CID to H3G__001
Nandroid restore of H3G ROM. (M7 CWM Nandroid Backup / CID H3G__001 / 1.28.771.x )
s-off to lock and remove tamper.
s-on.
OTA update?
Will this work?
Or does anyone have a link to the 1.28.771 firmware?
Thanks for the help.
Click to expand...
Click to collapse
Any ideas?

You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck

prodizo said:
You don't have to lock the bootloader and you need s-off to downgrade.
http://forum.xda-developers.com/showpost.php?p=42396455&postcount=20
Rest of the steps...well sounds good but unfortunatelly i'm not expert so dunno
I'm really interested if it works this way for you as i have a VF-uk one, and once i have to go back to stock this info would be really helpful.
Please let we know your progress
Good luck
Click to expand...
Click to collapse
Hey,
Yup this worked perfectly (almost). Reset your CID to your originally carriers before running the nandroid backup or it will be missing your carriers boot screen.
The only thing is the recovery seems to be missing. I'd expect the HTC recovery to load when selecting it from the bootloader but all I get is a red triangle. I obviously need to sort this before sending it back (Monday).
Any ideas?
I haven't s-on'd yet because I want to sort out recovery first. That should be pretty simple though.

I guess I just need a link to stock recovery.img.

Just tried and mine does same. I have stock recovery so thats fine.
Hope you get a nice new one:laugh:
Cheers

Stock recovery will display a red triangle..your all set
Sent from my HTC One using xda app-developers app

Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.

Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Ardmanz said:
Yup. I just realised. Completely 100% back to stock now with s-on.
It's been quite a journey. Hopefully they can repair it quickly so I can get ARHD 11 back on.
Click to expand...
Click to collapse
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?

Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.

Grand_Goblin said:
Would you make the step by step?
It would really helpful
If I ain't wrong,
1. Get the RUU's
2. Change CID to HTC_001 before flashing RUU
3. Flash RUU
4. Write original CID
5. Nandroid Restore
6. Re S-ON with Revone
Is that right?
Click to expand...
Click to collapse
Ardmanz said:
Yup, those are the exact steps that I took.
Note* make sure you just boot into custom recovery and don't actually flash it when restoring your nandroid backup. Having custom recovery on your device is a dead give away.
Click to expand...
Click to collapse
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up

Grand_Goblin said:
sorry man, but "flash it" refers to?
I don't get it and I don't wanna mess up
Click to expand...
Click to collapse
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.

Ardmanz said:
Normally you would use the following command to install custom recovery:
Code:
fastboot flash recovery recovery.img
Use this command instead:
Code:
fastboot boot recovery.img
That allows you to boot into custom recovery without actually installing it onto your phone.
Click to expand...
Click to collapse
matursuwun - Thank You so much! (in Javanese)

[Q] Htc ruu 1.28 not overwriting orange 1.28.61.7 even after s-off. Please Help

Hi, i am new here and after some help. Have just had my htc one repaired for the 2nd time (blown top speaker ee didn't repair properly so had to go to htc) so now want to go to stock htc_001.
I am on orange and been waiting for the 1.29 update (never going to come) so i carried out s-off on my phone this morning and changed the cid to htc_001. That all went okay and i relocked the phone and put it back to s-on. When i check the cid on the phone and with revone it says htc_001, so that all worked okay.
I downloaded the htc ruu 1.28 from xda and installed it, it when through the checking and installed it all (took about 15mins), i got no error messages it said update successful. The phone rebooted and was wiped clean and had to go through all the settings when you first get your phone. When i go to software version its still running 1.28.61.7 (the orange software) and when i check for updates it says none available. I have tried twice to install the ruu and both times it says successful but won't write over the orange software.
I am not sure what i have done wrong but some help to get my phone onto stock htc so i get timely updates and not having to wait for rubbish orange.
Any help would be greatly appriciated
Thanks Ashley

CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho

EddyOS said:
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
Click to expand...
Click to collapse
Thanks for the quick reply, I have just double checked it is HTC-001 the only thing i can think of is its because the orange version is a higher number to the htc. Would i have to install a ruu for a different area (asia maybe) and then put it back to HTC_001 and try to update to the 1.28 htc version? I wouldnt want it to be stuck on the wrong country version if it still wont update to the europe version.

HTC__001, not HTC_001 - you HAVE to use TWO underscores...

EddyOS said:
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
Click to expand...
Click to collapse
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley

I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?

saquib said:
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
Click to expand...
Click to collapse
Looks like I'm having the same issue - did either of you find a solution?

I ended up applying a nandriod backup to get 1.28.

Change cid to super cid 11111111.

saquib said:
I ended up applying a nandriod backup to get 1.28.
Click to expand...
Click to collapse
Cheers - guess I'll go that way too - don't suppose you have a link to the backup - unfortunately the BugsyLawson site is down

Sorry don't have a copy to hand, I also downloaded it from that site.

Ashes20vt said:
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
Click to expand...
Click to collapse
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.

Rex2369 said:
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Click to expand...
Click to collapse
I managed to sort it out, not sure how I did it really. I tried to flash it manually which it didn't do as it was playing games with me. I tried the ruu with supercid which it didn't work. I put it back to HTC__001 and relocked it then tried flashing manually again, it didn't work so tried afew times but no luck. So I tried the ruu one more time and it worked, I got the 1.29.401.12 ota straight away too. I think trying to manually flash it corrupted something so the ruu was able to overwrite orange. The phone nearly broke me and was about to give in but glad I kept at it though as orange updates are ridiculous.
Thanks to all that helped me with my error of not putting 2 underscores in the cid.
I am just hoping the 4.2.2 updates on my phone okay when it's released soon.

[Q] HELP!! Need Stock UK T-Mobile RUU

Hi,
I have been looking for the Stock Ruu for T-Mobile UK but cant find it.
I have rooted my phone and s-off and super cid. but unfortunately i need to return my phone for warranty.
Can anybody help.
Regards

Skynet2Mainframe said:
Hi,
I have been looking for the Stock Ruu for T-Mobile UK but cant find it.
I have rooted my phone and s-off and super cid. but unfortunately i need to return my phone for warranty.
Can anybody help.
Regards
Click to expand...
Click to collapse
There isn't an RUU for x.xx.61.x available. I should know I searched for one for long enough. All I can suggest is change your cid to supercid (fastboot oem writecid 11111111) Then Run the RUU 1.28.401.7 found here http://forum.xda-developers.com/showpost.php?p=39588860&postcount=1
After this has completed, install CWM recovery, and flash the CWM nandroid backup 1.28.61.7 found at the same link.
Next find the stock recovery (have to search several here somewhere), remove root completely, install the stock recovery and s-on.
If all goes well you might even get the 2.24.61.1 update. :good:
OOOPS forgot, change cid back to ORANG001 before changing back to s-on.

bobsie41 said:
There isn't an RUU for x.xx.61.x available. I should know I searched for one for long enough. All I can suggest is change your cid to supercid (fastboot oem writecid 11111111) Then Run the RUU 1.28.401.7 found here http://forum.xda-developers.com/showpost.php?p=39588860&postcount=1
After this has completed, install CWM recovery, and flash the CWM nandroid backup 1.28.61.7 found at the same link.
Next find the stock recovery (have to search several here somewhere), remove root completely, install the stock recovery and s-on.
If all goes well you might even get the 2.24.61.1 update. :good:
OOOPS forgot, change cid back to ORANG001 before changing back to s-on.
Click to expand...
Click to collapse
Thanks for your reply.
im on t-mobile so i think my CID should be T-MOB001.
also i see the CWM Orange nandroid is avalible but not the T-mobile uk. ill have to do some digging.
Thanks again.

Skynet2Mainframe said:
Thanks for your reply.
im on t-mobile so i think my CID should be T-MOB001.
also i see the CWM Orange nandroid is avalible but not the T-mobile uk. ill have to do some digging.
Thanks again.
Click to expand...
Click to collapse
I am on T-Mobile too. This is the correct cid which is used by EE/T-Mobile/Orange.

bobsie41 said:
I am on T-Mobile too. This is the correct cid which is used by EE/T-Mobile/Orange.
Click to expand...
Click to collapse
Sorry to be a pain which cid did you use orange or T-mob?
Cheers

Skynet2Mainframe said:
Sorry to be a pain which cid did you use orange or T-mob?
Cheers
Click to expand...
Click to collapse
ORANG001 which is used for all EE/T-Mobile/Orange HTC ones.

Skynet2Mainframe said:
Hi,
I have been looking for the Stock Ruu for T-Mobile UK but cant find it.
I have rooted my phone and s-off and super cid. but unfortunately i need to return my phone for warranty.
Can anybody help.
Regards
Click to expand...
Click to collapse
I have the same problem. Did you find a T-Mobile UK CWM Nandroid in the end? I'm probably just going to try the Orange one seeing as they are both EE now.

first post need help returning to stock

hello every one this is my first post i need some help please.
i bought a htc one preowned and i have since been in settings and its running a custom rom
android revolution hd 12.1 by mike 1986
my phone cid is htc_001
how do i return it to stock htc os
i have read a few posts before posting here i no i have to re lock bootloader then flash the ruu
i was wondering is there an easier way to relock bootloader and flash the ruu could some one also point me in the right direction
to which ruu to download with a link if possible to download.
thanks in advance for any help u may give with some simple instructions that i can understand as this is new to me and do not want to
make a mistake.
thankyou.

Is it S-OFF at the moment?

EddyOS said:
Is it S-OFF at the moment?
Click to expand...
Click to collapse
says m7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.44.0000
RADIO-4a.18.3263.15
openDSP-v26.120.274.0202
eMMC-boot
so im guessing so

You don't need to relock, if you're s-off you can run whatever RUU you like.

iElvis said:
You don't need to relock, if you're s-off you can run whatever RUU you like.
Click to expand...
Click to collapse
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.

Infamouslimey said:
thnks for your help can u link me to the correct ruu if u dont mind been looking not sure which one to download
thanks very much for your help to all.
Click to expand...
Click to collapse
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Note that running a RUU will fully wipe the phone. So back up anything on it you want to keep.

iElvis said:
Where was the phone purchased and what was the carrier? It's possible your CID was changed.
Assuming htc__001 is correct, the RUU collection is here:
http://forum.xda-developers.com/showthread.php?p=39588860
There are no RUUs for 4.2, so this would mean downgrading. But you should then start getting OTAs.
Click to expand...
Click to collapse
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111

Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
You have superCID, which means any RUU will run. You have the generic European model. CIDGetter is pulling the original cid from some system file, but it doesn't reflect the actual cid.

Infamouslimey said:
will i ran cid getter and it tells me the cid is htc_001
but in above post its cid_11111111
Click to expand...
Click to collapse
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe

Infamouslimey said:
will this ruu work
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Click to expand...
Click to collapse
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.

iElvis said:
Yes, that's the one you want. You don't need to relock or anything being s-off. Just plug into your computer and run the ruu.
Click to expand...
Click to collapse
thank you very much for all your help great site with such helpful members.

will this method re-lock bootloader and put s-off back to s-on or whatever its called ?

Infamouslimey said:
will this method re-lock bootloader and put s-off back to s-on or whatever its called ?
Click to expand...
Click to collapse
No and no. You have to do those manually, and there is no need to here.

if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?

Infamouslimey said:
if i wanted to re lock bootloader and put s back on how would i do it trying to learn so i dont have to keep asking for help ?
Click to expand...
Click to collapse
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.

iElvis said:
That is a bit trickier and riskier since you don't know what was done to your phone before you bought it. I don't recommend going back to s-on because of this. However, running the correct RUU should put you back to safe stock.
Once the RUU has run and you've confirmed that the phone boots and is back to a stable stock configuration, you need to reboot and run a series of commands in fastboot:
fastboot oem writecid HTC__001
This will restore your stock CID. Note that there are two underscores there.
fastboot reboot-bootloader
Confirm on your bootloader screen that the CID is correct.
fastboot oem lock
This will relock your bootloader. Reboot again and confirm that it says "LOCKED" on your bootloader (Not "RELOCKED"). Boot up your phone and confirm that everything seems to be running correctly. You may want to give this a few days. Then reboot to bootloader when you're comfortable with it.
fastboot oem writesecureflag 3
This will put you back to s-on. When you reboot from here, your bootloader should say LOCKED and S-ON as if it was out of the box.
Click to expand...
Click to collapse
thanks very much for all your help ill install the fastboot files anyway so if need them there there.
many thanks

I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?

N0wy0ud1e said:
I too need to put my T-mobile HTC One back to stock somehow, but don't even know where to start, I saw this thread so I didn't want to clutter up the subforum, and thought that maybe I should ask here. I'm at 1.27.531.11, S-ON, rooted w/ unlocked bootloader, and would like to make it look like nothing happened to it when I return it to the store tomorrow. Could you please give me some pointers?
Click to expand...
Click to collapse
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.

iElvis said:
You need to s-off first or it will say "RELOCKED" on the bootloader. Problem is you may or may not be able to s-off right now. There is a new T-Mo exploit that supposedly works but I know nothing about it.
Once you do that, you can run an older RUU, which will remove the TAMPERED from the bootloader, then relock and s-on as described above.
Click to expand...
Click to collapse
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.

N0wy0ud1e said:
Crap. Well I know they're not going to check the bootloader lol, just that when you turn on the phone, you'll see the red text at the bottom saying "Developmental purposes" and I can't remember the rest of the message. Can I make that disappear so it just shows nothing on the white background but the green HTC logo? Btw thanks for the reply.
Click to expand...
Click to collapse
That goes away when you relock.

[SOLVED] Stock O2 UK Nandroid or Zip?

Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.

fade2black101 said:
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
Click to expand...
Click to collapse
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware

nkk71 said:
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
Click to expand...
Click to collapse
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.

fade2black101 said:
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
Click to expand...
Click to collapse
so quick and dirty? (and hope for the best)... did you use sunshine to s-off? before i post the steps.

haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time

fade2black101 said:
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
Click to expand...
Click to collapse
okay cool, i only asked because sunshine will work again (without needing to pay again), in case that infamous "tamper detected - rebooting" happens (shouldnt in your case but just in case it does)
gimme a few minutes, and i'll post instructions with links....

Thanks
I will check this out tomorrow when I have some time

fade2black101 said:
Thanks
I will check this out tomorrow when I have some time
Click to expand...
Click to collapse
okay, should be easy enough:
1) download Guru_Bootloader_Reset_1.0.zip and put it on your virtual storage
2) download 4.19.401.9-TWRP2633_combined_nowipe.zip
if need be change cid to a compatible one:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
flash firmware
Code:
fastboot oem rebootRUU
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot reboot-bootloader
set back O2 UK cid:
Code:
fastboot oem writecid O2___001
fastboot reboot-bootloader
3) go to RECOVERY (it should be TWRP 2.6.3.3 from the file above) and run the Bootloader Reset
--> remove TAMPERED
--> set LOCKED
4) go back to bootloader, and check it says LOCKED, and no more TAMPERED
5) download RUU_4.20.206.16.EXE
and run it
(if it "exits" for some unknown reason, make sure you have this installed vcredist)
6) reboot the phone to make sure it boots up fine, do not take OTA updates
7) if you really insist, go s-on
Code:
fastboot oem writesecureflag 3
8) reboot three times (do not take any OTAs, especially above 6.xx), and make sure no TAMPERED is triggered

nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!

fade2black101 said:
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
Click to expand...
Click to collapse
there's no risk in bricking using that "fastboot oem writesecureflag 3" command to set s-on; the RUU would have set everything back to stock; if in the unlikely event the "TAMPERED" comes back, you'll need to s-off again, and use my guide with the 1.xx RUU + nandroid method
as for sending it in S-OFF, it's really country/carrier/service centre/person specific.... from what i've seen UK is one of the most tolerant countries (some people have even sent the phone in with tamperd and running a custom rom, and still got the camera fixed)
but it's your call, i cant really say for sure how they would react.
and if all is good now, could you also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks and good luck