Database Develop

[Q] My HTC One recently unrooted, how do i return to stock RUU?

I'm S-OFF. My device is recently unrooted, and my version is 1.28.771.10 on the THREE 3 UK network. It seems there isn't an RUU for my phone released by three. Is there any way that I can return to stock so that my phone is as new? Step by step instructions would be appreciated as i'm very new to this. My bootloader is also locked.

I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app

paul_59 said:
I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?

tomquartey said:
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?
Click to expand...
Click to collapse
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.

alray said:
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.
Click to expand...
Click to collapse
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?

tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota

alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
Thank you buddy, will try this soon.

tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G

nkk71 said:
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G
Click to expand...
Click to collapse
I was told to change my RUU to a particular RUU from another user who is on the same network as me.

tomquartey said:
I was told to change my RUU to a particular RUU from another user who is on the same network as me.
Click to expand...
Click to collapse
well if you are on CID H3G_001 then this "change my RUU to a particular RUU" (there is no particular RUU) makes no sense at all, if you are S-Off:
1- you can change CID to unbranded and use an unbranded RUU
2- you can use one of the guides around here to go back to H3G stock

[Q] HTC One HK ROM change to Europian

Hi all,
A few I bought an HTC One model, and faced that it is a HK model, with HK ROM but I want to use it Hungary. My question is that, can I switch from HK ROM to European ROM to get official OTA updates? I have googled it, but cannot find anything useful on this topic
My device is S-On
M7_UL PVT
cid: HTC__622
mid: PN0714000
main version: 2.24.708.4
hboot: 1.54.0000
radio: 4A.18.3250.15
os: 2.24.708.4
Thank you
cactuska

S-OFF > Change CID & MID > Flash International RUU

Thank you,
What will be the impact on the device the changing of the cid and mid?
Exactly which RUU should I use, becuase I have found tons of these, and i really dont know which one to choose?
For example is RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed OK for me?
it has different version numbers compared to what i have now

cactuska said:
Thank you,
What will be the impact on the device the changing of the cid and mid?
Exactly which RUU should I use, becuase I have found tons of these, and i really dont know which one to choose?
For example is RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed OK for me?
it has different version numbers compared to what i have now
Click to expand...
Click to collapse
Use the 1.28.401.7 ruu this one here
changing mid and cid will allow you to run that ruu and receive ota, no others impact on the device.
unlock bootloader
install latest twrp recovery + root
s-off with rumrunner (might also require to flash a custom kernel like elementalx)
change cid
Code:
fastboot oem write cid HTC__001
fastboot reboot-bootloader
change mid using this tool to PN0710000
downgrade hboot to 1.44 version using this file provided by nkk71
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip [COLOR="Red"]<---- twice[/COLOR]
fastboot reboot-bootloader
run the ruu.exe
update phone via ota to latest version
flash custom recovery + root again if you need it (optional)
better to stay s-off
make sure you are not using windows 8.1 to do this. Also make sure you have latest android sdk installed on your computer and latest htc drivers.
if you are going to root again after the conversion, keep a copy of your stock recovery. You will need it to receive future ota

alray said:
...
Click to expand...
Click to collapse
Awesome guide. Hopefully enough to get OP going
sent from my mobile device

SaHiLzZ said:
Awesome guide. Hopefully enough to get OP going
sent from my mobile device
Click to expand...
Click to collapse
thanks,
I did it several times on my device. Got it new PN0711000 with that crappy Mexican .599 software. Converted to European .401 then converted to GPE .1700 then converted to dev .1540
much easier to do this now with the MID tool, was using eng hboot when I converted to European and gpe

alray said:
Use the 1.28.401.7 ruu this one here
changing mid and cid will allow you to run that ruu and receive ota, no others impact on the device.
unlock bootloader
install latest twrp recovery + root
s-off with rumrunner (might also require to flash a custom kernel like elementalx)
change cid
Code:
fastboot oem write cid HTC__001
fastboot reboot-bootloader
change mid using this tool to PN0710000
downgrade hboot to 1.44 version using this file provided by nkk71
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip [COLOR="Red"]<---- twice[/COLOR]
fastboot reboot-bootloader
run the ruu.exe
update phone via ota to latest version
flash custom recovery + root again if you need it (optional)
better to stay s-off
make sure you are not using windows 8.1 to do this. Also make sure you have latest android sdk installed on your computer and latest htc drivers.
if you are going to root again after the conversion, keep a copy of your stock recovery. You will need it to receive future ota
Click to expand...
Click to collapse
Thank you all, I have managed to do it with your help!
Now it is working like a charm!
Have a nice day
cactuska

Which CID gets the fastest OTA?

My CID is htc_001 and it sucks i allways get ota updates very slow compared to the other cids, so my question is to which cid should i change in order to get the fastest ota updates?
And another question, i flashed TWRP and rooted my phone, i still can get ota updates?
Again sorry for my noobish questions and my bad english.

You will need to be fully stock to get OTA's, recovery, no missing apps, stock rom etc.
and as for CID, well at a guess I would say super cid would get the updates first, however, recently ive heard its very dependant on your operator, country and whether you brought your phone or its on contract.
Im in the UK and on CID HTC__001 too, I read today that HTC are releasing the sense 6 update to UK customers somewhere around the 11th June, so Wednesday. im all ready for it, just got to flash stock recovery.

Seanie280672 said:
You will need to be fully stock to get OTA's, recovery, no missing apps, stock rom etc.
and as for CID, well at a guess I would say super cid would get the updates first, however, recently ive heard its very dependant on your operator, country and whether you brought your phone or its on contract.
Im in the UK and on CID HTC__001 too, I read today that HTC are releasing the sense 6 update to UK customers somewhere around the 11th June, so Wednesday. im all ready for it, just got to flash stock recovery.
Click to expand...
Click to collapse
So all i need to do to get updateds is to flash stock recovery? (i can keep the root, right?)
How can i flash the stock recovery?

Num_Lock said:
So all i need to do to get updateds is to flash stock recovery? (i can keep the root, right?)
How can i flash the stock recovery?
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img

alray said:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok... do I need a file or something? can you explain more detailed?
I'm sorry for being noob it's just I'm used to samsung phones development and the htc development is different with new stuff (s off unlocking ruu and whatever) so i need you to explain me more detailed.
Thank you.

Num_Lock said:
Ok... I need a file or something? can you explain in more details?
I'm sorry for being noob it's just I'm reguler to samsung phones development and the htc development is different with new stuff (s off unlocking ruu and whatever) so i need you to explain me more detailed.
Thank you.
Click to expand...
Click to collapse
you need the stock recovery file (recovery.img) from the same version firmware of your phone. i.e if you phone is on 4.19.401.1 and you want to update to 5.20.401.1, you need the recovery.img file from the 4.19.401.1 firmware.
also read this: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9

alray said:
you need the stock recovery file (recovery.img) from the same version firmware of your phone. i.e if you phone is on 4.19.401.1 and you want to update to 5.20.401.1, you need the recovery.img file from the 4.19.401.1 firmware.
also read this: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Click to expand...
Click to collapse
OK and one more thing, i need to s off to change my cid?

Num_Lock said:
OK and one more thing, i need to s off to change my cid?
Click to expand...
Click to collapse
yes you need s-off, and if you change your cid, it must match your sw version! some software version only have a unique compatible cid and other have many compatible cid. i.e .401 sw version can use many different cid: HTC__001, HTC__Y13, HTC__032, HTC__203 etc etc..... but .502 version can only use one cid: CWS__001
to change cid:
Code:
fastboot oem writecid YOUR_CID [COLOR="Green"]<---- in most cases, start with HTC in capital letter, 2 underscores and 3 digits, always 8 characters total.[/COLOR]
i.e:
Code:
fastboot oem writecid HTC__001
you can read your actual cid with this command:
Code:
fastboot oem readcid

alray said:
yes you need s-off, and if you change your cid, it must match your sw version! some software version only have a unique compatible cid and other have many compatible cid. i.e .401 sw version can use many different cid: HTC__001, HTC__Y13, HTC__032, HTC__203 etc etc..... but .502 version can only use one cid: CWS__001
to change cid:
Code:
fastboot oem writecid YOUR_CID [COLOR="Green"]<---- in most cases, start with HTC in capital letter, 2 underscores and 3 digits, always 8 characters total.[/COLOR]
i.e:
Code:
fastboot oem writecid HTC__001
you can read your actual cid with this command:
Code:
fastboot oem readcid
Click to expand...
Click to collapse
I want to change to supercid, it supports my version? and with s off i can still get ota right?

Num_Lock said:
I want to change to supercid, it supports my version? and with s off i can still get ota right?
Click to expand...
Click to collapse
on some sw version, you will not receive ota update with supercid. supercid is used to bypass cid check when installing some rom/ruu.
for s-off question, read the link i have posted at post #6

alray said:
on some sw version, you will not receive ota update with supercid. supercid is used to bypass cid check when installing some rom/ruu.
for s-off question, read the link i have posted at post #6
Click to expand...
Click to collapse
In my version i will get ota updates with supercid?
Thanks for your help i really appreciate it.

Num_Lock said:
In my version i will get ota updates with supercid?
Thanks for your help i really appreciate it.
Click to expand...
Click to collapse
idk, refer to the android-info.txt of the ota.zip and you'll see all supported cid.

USA developers edition get ota first every time
from HTC One

[Q] Can I downgrade 6.06 to 1.29 with S-OFF

Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 1.29.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?

uhm, what? this is nonsense , the lastest available RUU is "4.19.401.9" which must be flashed under hboot 1.56 ... there is no need to go to initial release of android 4.1!
WARNING!!! YOU MUST FLASH HBOOT 1.56 BEFORE APPLYING 4.19.401.9 RUU
RUU: http://d-h.st/KmT
+There is no need to LOCK your bootloader to get an OTA update... Mine is always unlocked and never had a problem with OTA's
+RUU's work only under S-OFF

Androidian10 said:
Hi all, I was just wondering if I should run the RUU ZIP or EXE if I am on S-OFF.
I currently have the 6.06.401.1 firmware along with the stock 6.06.401.1 rom. I need to return to the stock 1.29.707.1 for my HTC__044 before taking the latest OTA to Android Lollipop.
So far, I have used my S-OFF to change my bootloader to *LOCKED* and flashed stock recovery and stock rom for the 6.06.401.1.
I currently have both the 4.20.707.1 RUU EXE and ZIP. Which one should I use? I read that I need to have the 1.44 Hboot but I currently have the 1.54 Hboot.
Halp?
Click to expand...
Click to collapse
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.

Seanie280672 said:
you can use the RUU you have fine 4.20.707.1, you'll just have to make sure your cid and mid match first, and also just flash the 4.20.707.1 firmware first, this will put you on the correct HBOOT and system files for the RUU, no need to lock your bootloader with s-off.
or you can skip all of that and just flash the 7.19.401.2 RUU right now as your phone is as your already on the 6.xx.401.x firmware.
you don't really have any reason to back flash.
Click to expand...
Click to collapse
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.

Androidian10 said:
But I can't seem to find a 4.20.707.1 RUU. I only have the 1.29.707.3 firmware. I need a region specific one because I need to trade my phone in.
Edit: Crap I made a typo in my OP, I mean that I have the 1.29 RUU EXE and ZIP right now.
Could you point me in the direction of a 4.20.707.1 RUU zip?
Also, is it safe to OTA update if I flash back to 1.29 with S-OFF?
Click to expand...
Click to collapse
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.

Seanie280672 said:
I thought you said you had the 4.20.707.1 RUU
if not then you'll have to use the 1.29.707 one that you have, you'll just have to flash the 1.44 hboot first or the firmware that matches the RUU.
Click to expand...
Click to collapse
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?

Androidian10 said:
Yeah I had a typo.
So yeah, I have both the EXE and ZIP RUU.
I'm thinking that the ZIP RUU has the 1.44 hboot no?
Also, most importantly, can I take official OTA updates while I am S-OFFed?
Click to expand...
Click to collapse
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.

Seanie280672 said:
yes you can take OTA's whilst s-off, do not go s-on at any point.
I would also say try the RUU.zip first.
Click to expand...
Click to collapse
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.

Androidian10 said:
Righto. Will report back again.
I hope the guy at the store doesn't go into the bootloader when I trade my m7 in. Even then I already set the flag to locked so I think he'll miss that S-OFF portion.
Click to expand...
Click to collapse
cid and mid need to match the ruu your flashing first.

Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Already checked with fastboot getvar all.

Seanie280672 said:
cid and mid need to match the ruu your flashing first.
Click to expand...
Click to collapse
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?

Androidian10 said:
Actually, problem. :/
I have a matching CID which is HTC__044 but the modelid is PN0714000.
The RUU's android-info has a matching CID of HTC__044 but a modelid of PN0711000.
What now?
Click to expand...
Click to collapse
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
here you go, do this instead, this is going to be a bit backwards and forwards.
Unlock your bootloader, and flash TWRP recovery, then use the mid change tool to change your mid to the correct one.
https://www.androidfilehost.com/?fid=23622183712469376
next copy this guru reset file to your internal storage and flash it, select no to stock radio and no to stock recovery: http://www.htc1guru.com/2013/11/guru-reset-3-63-707-4-stock-rom/
now lock your bootloader
and finally flash the matching firmwqare from here: http://d-h.st/BWu this will put stock recovery and stock radio on your phone.

Seanie280672 said:
unlock your bootloader, flash twrp recovery and change your mid, are you sure your using the RUU for the M7_UL as that looks a lot like the M7_U mid too me, can you give me a link for the RUU's you downloaded please.
Click to expand...
Click to collapse
I actually ran the RUU. It's now stuck on waiting for device after the usual flush after 90 hboot pre-update.
I changed the modelid in the android-info.txt since it was decrypted.

Anyone help me?
My computer can't see the device anymore after flashing the hboot!

Androidian10 said:
Anyone help me?
My computer can't see the device anymore after flashing the hboot!
Click to expand...
Click to collapse
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.

Seanie280672 said:
if your using windows 8 or higher then that's the problem, HBOOT 1.44 doesn't work with it, there is a fix around here somewhere by @clsA but ive never had to use it myself.
trouble with changing the android-info text file is all of the OTA's will fail due to you having the wrong mid on your phone, you'll have to change your phones mid as soon as possible.
Click to expand...
Click to collapse
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?

Androidian10 said:
Ok, I have changed to an old Windows 7 laptop and tried doing the fastboot flash zip again. After I press enter, nothing happens at all. Not a single code at all. Just a blinker.
Edit: Started moving again. Phew. I almost had a heart attack.
So now do I do the fastboot writemid command?
Click to expand...
Click to collapse
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.

Seanie280672 said:
to change the mid you need to use the mid change tool I posted a link to it earlier, install it inside twrp recovery then select the mid you require from the list it gives you.
Click to expand...
Click to collapse
It's okay now. I found a matching mid RUU for my phone.
But my question now is should I go S-ON to remove the red "This is a test device. Accordingly, to collect critical information about the device, Tell HTC is enabled and cannot be turned off regardless of device settings" warning? Or just leave it S-OFF and hope that the techies at the store doesn't notice it?

More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?

Androidian10 said:
More questions
I have done all the OTAs now so should I do the fastboot oem writesecureflag 3 as the final step before putting the phone aside to trade it in?
Click to expand...
Click to collapse
no, leave it s-off, if you turn it back s-on now you will get the tampered flag back.

Htc One AT&T trying to upgrade to lollipop using official RUU - get error 155

Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,

BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...

alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!

alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!

BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)

alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!

BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.

alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!