Database Develop

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] Dead phone, RUU fails

The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!

Shu. said:
The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Click to expand...
Click to collapse
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.

nkk71 said:
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
Click to expand...
Click to collapse
Okay, then that seems to be the issue, i'll try to relock, thanks!

Shu. said:
Okay, then that seems to be the issue, i'll try to relock, thanks!
Click to expand...
Click to collapse
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.

nkk71 said:
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
Click to expand...
Click to collapse
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on

If you have S-off you don't have to lock your bootloader to run a ruu.

Shu. said:
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
Click to expand...
Click to collapse
No problem :good:
Post back with your results so we know

maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use

maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed

maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
I stand corrected
---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------
Shu. said:
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
Click to expand...
Click to collapse
with S-Off it's no problem to downgrade. where did you get the RUU, can you post link.
And what's the exact error you get?

EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!

Shu. said:
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Click to expand...
Click to collapse
For other RUUs check this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
I find HTCdev way too confusing, as it clutters everything together, you can easily download a RUU for "HTC One S" instead of "HTC One" (aka M7)
And since you're S-Off downgrading is no problem

[Q] Retain S-off and bootloader unlock after RUU?

Apologies if this is a noob question or has been answered before, but I just ran the RUU and I retained S-off and my bootloader was still unlocked afterwards. Is this suppose to happen?
I'll try and make this short: I had HBOOT 1.44 (S-off with revone and HTC Dev unlocked). I saw OMJ's thread with newer firmwares and a 4.06.651.4 RUU. I flashed the firmware, verified everything worked still, and ran the RUU (for peace of mind). RUU was successful but the fastboot screen still shows the pink ***UNLOCKED*** text and S-OFF message. Current HBOOT is 1.56.

MrLinky said:
Apologies if this is a noob question or has been answered before, but I just ran the RUU and I retained S-off and my bootloader was still unlocked afterwards. Is this suppose to happen?
I'll try and make this short: I had HBOOT 1.44 (S-off with revone and HTC Dev unlocked). I saw OMJ's thread with newer firmwares and a 4.06.651.4 RUU. I flashed the firmware, verified everything worked still, and ran the RUU (for peace of mind). RUU was successful but the fastboot screen still shows the pink ***UNLOCKED*** text and S-OFF message. Current HBOOT is 1.56.
Click to expand...
Click to collapse
Yes

hmm, i might have to try this later on...i was concerned it might relock or i might have to lock but i guess not?(ive been trying to search and find out but i think you answered my question lol)

Once S-OFF, always S-OFF, unless you write the secureflag to be S-ON again.

pinky059 said:
Once S-OFF, always S-OFF, unless you write the secureflag to be S-ON again.
Click to expand...
Click to collapse
Good to know, thanks. I was under the impression that an RUU totally resets a device but I guess not. It saved me having to s-off/unlock/root again :victory:

Hey I learned something new lol

mxx20 said:
Hey I learned something new lol
Click to expand...
Click to collapse
So did I, regarding RUUs that is.

v1ral said:
So did I, regarding RUUs that is.
Click to expand...
Click to collapse
Me too..lol, heyit's a learning game!

Yes you have to do a FASTBOOT RELOCK COMMAND to make the phone secure. You can also use root linux to disguise the bootloader/Hboot to make it appear S-ON if you choose. http://forum.xda-developers.com/showthread.php?t=2565201

back to stock

I am s-off and bootloader unlocked. stock rom and stock recovery.
Which command locks the bootloader? I want it to show "locked"
and which command makes the phone s-on again?

MICH_** said:
I am s-off and bootloader unlocked. stock rom and stock recovery.
Which command locks the bootloader? I want it to show "locked"
and which command makes the phone s-on again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2675535&page=2

alray said:
http://forum.xda-developers.com/showthread.php?t=2675535&page=2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51183962

MICH_** said:
I am s-off and bootloader unlocked. stock rom and stock recovery.
Which command locks the bootloader? I want it to show "locked"
and which command makes the phone s-on again?
Click to expand...
Click to collapse
what's the point of asking the same questions many times?
follow the advice you have already been given.

[Q] Can't use my HTC phone, no system

Hey, I was stupid and missed up my phone. I wanted to update my phone, but because It was rooded I wasn't able to do it. So I decided to begin from start. So I downgraded my Hboot to 1.44 and also stupid to set s-on again. But then I could not install the stock rom 1.29.651.10. So I decided to try a custom rom. So I would be able to set s-off again. But non of them worked. I think that the old Hboot 1.44 is why the roms didn't work. But I can't change my Hboot before my device is s-off.
I'm able to use adb sideload and twrp recovery
Bootloader information
Tampered
Unlocked
M7_WLS PTV SHIP S-ON RH
HBOOT-1.44.0000
OpenDSP-v32.120.274.0909
eMMC-boot
May 8 2013.16:30:08:-1
Does any one have any suggestions ?

If I remember right, the older s-off techniques like rumrunner should still work with that hboot. I'd look into those first.

coal686 said:
If I remember right, the older s-off techniques like rumrunner should still work with that hboot. I'd look into those first.
Click to expand...
Click to collapse
I've have already tried rumrunner, but it didn't work for me. I was able to get Viberone 8 to work, but it was very slow. Tried to get s-off but did't work with the Viberone rom. So now i'm trying another one to see if it will allow me to get the phone s-off. But thx for your respond

1.29.401.12. is not a Sprint rom.

BD619 said:
1.29.401.12. is not a Sprint rom.
Click to expand...
Click to collapse
Sorry ment 1.29.651.10

christian8220 said:
Sorry ment 1.29.651.10
Click to expand...
Click to collapse
While booted to fastbootusb open a cmd window (from your platform tools folder) and type:
Code:
fastboot getvar all
Then copy and paste the results here...make sure you remove your IMEI from the results.

BD619 said:
While booted to fastbootusb open a cmd window (from your platform tools folder) and type:
Code:
fastboot getvar all
Then copy and paste the results here...make sure you remove your IMEI from the results.
Click to expand...
Click to collapse
Here you go

christian8220 said:
Here you go
Click to expand...
Click to collapse
Re-lock your bootloader and use the 1.29.651.10 RUU then give revone a try it should work to get you s-off again

BD619 said:
Re-lock your bootloader and use the 1.29.651.10 RUU then give revone a try it should work to get you s-off again
Click to expand...
Click to collapse
Thx it worked for me. First I replaced the TWRP recovery with the stock recovery 1.29.651.10. After that I relocked my bootloader "fastboot oem lock" and the device rebooted. I used the 1.29.651.10 RUU exe. and it worked. So thank you, have a nice day