[Q] Unrooting?

Vonrottes · Jun 17, 2014

Alright, I've been through thread after thread and plenty of pages found on google.
Some say to Lock the bootloader BEFORE using the RUU and some say to lock it AFTER or you'll brick the phone?

I've got a T-mobile Variant of the HTC one M7 It's rooted, SuperCID and obviously the bootloader is unlocked.... I think it's on 1.55, not exactly sure, I'm currently backing up all my data.

I've got the new 5.14.531.1 RUU straight from the HTC website.
Since it's a Tmobile rom, I'm guessing resetting the CID to T-MOB010 before installing would be a good idea?
And what of the bootloader? running the RUU should install the new Hboot correct? from there I would just need to relock it or am I not understanding this?

~Out of all my phones I've NEVER returned one to stock, so this is all kinda new to me.

nkk71 · Jun 17, 2014

Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.

SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)

Vonrottes · Jun 17, 2014

nkk71 said:
SuperCID means you're S-Off, so no need to lock/relock bootloader, but where did you get that RUU from? link please, cause I don't think it's an RUU (how big is the file??)

Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.

Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe

it's a whooping 1.49GB

nkk71 · Jun 17, 2014

Vonrottes said:
Doesn't exactly answer the question... I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.

Also the link, right from HTC
http://dl3.htc.com/application/RUU_M7UL_TMOUS_5.14.531.1_With Partial.exe

it's a whooping 1.49GB

ah ok, 1.49GB sounds good for an RUU

and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader

refer to "Not so FAQ #2": http://xdaforums.com/showpost.php?p=52135024&postcount=2

and remember to stay S-Off

Vonrottes · Jun 17, 2014

nkk71 said:
ah ok, 1.49GB sounds good for an RUU

and to answer your question differently, if you are S-Off, then you do not need to lock/relock bootloader; the RUU should work fine with unlocked bootloader

refer to "Not so FAQ #2": http://xdaforums.com/showpost.php?p=52135024&postcount=2

and remember to stay S-Off

Jolly good, I didn't even see that Not so FAQ.

So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?

nkk71 · Jun 17, 2014

Vonrottes said:
Jolly good, I didn't even see that Not so FAQ.

So basically I just run the RUU according to the instructions on the HTC page ( http://www.htc.com/us/support/news.aspx?p_id=630&p_name=htc-one-t-mobile ) and I should be good?

hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.

Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://xdaforums.com/showthread.php?t=2527194
(though I don't see any reason to do it

)

as long as you stay S-Off, you can easily get it unlocked again anytime

out of curiosity, any particular reason you're doing this?

Vonrottes · Jun 17, 2014

nkk71 said:
hmm, i can't seem to be able open that web page, but if the file is a full RUU (I'm downloading it, but with my connection it's gonna take quite a while), then hook up the phone, and run the RUU and all should be good.

Remember an RUU will fully wipe your phone (including sdcard/internal storage), and if for whatever reason you want to change bootloader to the original LOCKED (not relocked),
you can use this tool: http://xdaforums.com/showthread.php?t=2527194
(though I don't see any reason to do it )

as long as you stay S-Off, you can easily get it unlocked again anytime

out of curiosity, any particular reason you're doing this?

I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.

and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.

So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?

nkk71 · Jun 17, 2014

Vonrottes said:
I know, that's why I'm currently backing up everything important on Google Drive.
I was just looking at Scotty1223's threads with the ADB commands to remove tampered flag and reset locked.

and like I said in my second post
I'm going back to stock to upgrade my phone...
So, I do need to relock the bootloader & reset the CID at some point.

So to go back stock with no need to ever unlock or root again,
I'll be fine LOCKING the bootloader and resetting the CID to T-MOB010 Before running the RUU?

I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading

Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF

Vonrottes · Jun 17, 2014

nkk71 said:
I understood the part about upgrading your phone, but seeing your signature, you're running a custom ROM and kernel, so i'm not clear what you mean by upgrading

Anyway, if you are going back to stock, here's what I personally would do:
1- stay S-OFF
2- change CID back to original
3- remove TAMPERED and set LOCKED (using scotty1223's commands, or the Guru Bootloader Reset tool) not because it's necessary, just aesthetically more stock
4- run the RUU
5- stay S-OFF

Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html

To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?

nkk71 · Jun 17, 2014

Vonrottes said:
Upgrading as in:
http://www.t-mobile.com/phone-upgrade.html

To get an HTC One M8 I have turn in my Current M7... Which has to be stock...as far as the T-mobile store tech needs to know.... I guess?

gotcha :good:

that's a completely different kind of upgrade, i thought you meant software

Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.

Vonrottes · Jun 17, 2014

nkk71 said:
gotcha :good:

that's a completely different kind of upgrade, i thought you meant software

Do they care about S-OFF?? because if you intend on going S-ON, then I would highly recommend a 1.xx ruu, nothing higher.
because going from S-Off to S-On on hboot 1.55+, has been known to trigger "tamper detected - rebooting" and TAMPERED is back in bootloader screen.

Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***

Is it just the 1.55+ Hboot that throws the tampered when locked?
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?

Can't do the 1.44, My PC is running 8.1 and I've not played with Linux since 2009

nkk71 · Jun 17, 2014

Vonrottes said:
Yeah, it's gonna need to be S-on when I take it into the store...
Pretty sure they check the bootloader for S-ON, ***TAMPERED*** and ***LOCKED***

In that case, I recommend you use a 1.xx RUU
(check my guide in my signature)

Vonrottes said:
Is it just the 1.55+ Hboot that throws the tampered when locked?

Unknown when/what exactly triggers the "tamper detected" or some people have been able to S-On and not get that, others have not, so I can't say if it will happen or not. but if you wanna play it safe, go for 1.xx ruu.

Vonrottes said:
If so Can I flash the 1.54.401.5 Hboot from Firewater and proceed like that?

brick alert: Definitely NOT, that is a custom HBOOT, if you actually manage to S-On it with an unsigned hboot, you'll have an paperweight on your hands!! stay away from that.

Topics

Topics

[Q] Unrooting?

Vonrottes

Senior Member

nkk71

Inactive Recognized Developer / Contributor

Vonrottes

Senior Member

nkk71

Inactive Recognized Developer / Contributor

Vonrottes

Senior Member

nkk71

Inactive Recognized Developer / Contributor

Vonrottes

Senior Member

nkk71

Inactive Recognized Developer / Contributor

Vonrottes

Senior Member

nkk71

Inactive Recognized Developer / Contributor

Vonrottes

Senior Member

nkk71

Inactive Recognized Developer / Contributor

Similar threads

New posts