My device is Super CID. I have a CWN nandroid thats got loads of CIDs so was going to just use CID HTC__102 once I have flashed the OS. Then removed tampered, Lock bootloader then S-on.. Will this work or does it have to go back to the vodaphone CID? regards
anarchyuk said:
My device is Super CID. I have a CWN nandroid thats got loads of CIDs so was going to just use CID HTC__102 once I have flashed the OS. Then removed tampered, Lock bootloader then S-on.. Will this work or does it have to go back to the vodaphone CID? regards
Click to expand...
Click to collapse
Your CID will remain SuperCID only. If you want to go back to the Vodafone CID, you will have to use the 'writecid' command. If you're giving the phone for repair, then you'll have to change to the HTC_102. If not, stay on SuperCID. The RUU will work perfectly on SuperCID
Next, i would never recommend you to go back S-ON. Stay S-OFF. However, if you insist on going S-ON, S-ON ONLY AFTER YOU'RE SUCCESSFULLY ON STOCK FIRMWARE AND HBOOT VERSION IS 1.44/1.54.
Do not S-ON before the RUU is flashed. Do not S-ON if HBOOT is 1.55/1.56. Otherwise, the TAMPERED flag will re-appear
raghav kapur said:
Your CID will remain SuperCID only. If you want to go back to the Vodafone CID, you will have to use the 'writecid' command. If you're giving the phone for repair, then you'll have to change to the HTC_102. If not, stay on SuperCID. The RUU will work perfectly on SuperCID
Next, i would never recommend you to go back S-ON. Stay S-OFF. However, if you insist on going S-ON, S-ON ONLY AFTER YOU'RE SUCCESSFULLY ON STOCK FIRMWARE AND HBOOT VERSION IS 1.44/1.54.
Do not S-ON before the RUU is flashed. Do not S-ON if HBOOT is 1.55/1.56. Otherwise, the TAMPERED flag will re-appear
Click to expand...
Click to collapse
thanks for the reply. Its hboot 1.44.. I am selling it and its supposed to be getting sold as stock... I have just pushed a nandroid for the euro over but had a md5 check error. think this may be because i opened one of the rars to make sure it was for my model id so im re pushing it.. My main concern is.. Can i flash say a ruu exe. leave super cid. lock bootloader and then s-on without a brick?
anarchyuk said:
thanks for the reply. Its hboot 1.44.. I am selling it and its supposed to be getting sold as stock... I have just pushed a nandroid for the euro over but had a md5 check error. think this may be because i opened one of the rars to make sure it was for my model id so im re pushing it.. My main concern is.. Can i flash say a ruu exe. leave super cid. lock bootloader and then s-on without a brick?
Click to expand...
Click to collapse
Look, if you're gonna sell the phone as stock, don't sell it as SuperCID. Sell it with the HTC__102 CID
If for some reason, you still want to sell it as SuperCID, then ignore the first step. Follow these steps in order
1. Change your CID to the stock Vodafone CID (HTC__102)
2. Flash this in TWRP 2.6.3.3 (ive had personal experience, none with CWM):
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
Choose "Lock Bootloader" and "remove TAMPERED"
3. Once you choose these 2 options and flash the zip, go back to the bootloader and check that the bootloader is now LOCKED and no TAMPERED
4. Now, flash this RUU.exe:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
5. Once the phone boots up successfully, the last thing left is to S-ON. Remember, S-ON the phone before you install any OTA's. Technically, as soon as the phone boots. To S-ON:
Get the phone to fastboot mode, open command prompt on ur PC in the fastboot folder and type:
fastboot oem writesecureflag 3
Then, reboot the phone thrice. It will be S-ON again
raghav kapur said:
Look, if you're gonna sell the phone as stock, don't sell it as SuperCID. Sell it with the HTC__102 CID
If for some reason, you still want to sell it as SuperCID, then ignore the first step. Follow these steps in order
1. Change your CID to the stock Vodafone CID (HTC__102)
2. Flash this in TWRP 2.6.3.3 (ive had personal experience, none with CWM):
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
Choose "Lock Bootloader" and "remove TAMPERED"
3. Once you choose these 2 options and flash the zip, go back to the bootloader and check that the bootloader is now LOCKED and no TAMPERED
4. Now, flash this RUU.exe:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
5. Once the phone boots up successfully, the last thing left is to S-ON. Remember, S-ON the phone before you install any OTA's. Technically, as soon as the phone boots. To S-ON:
Get the phone to fastboot mode, open command prompt on ur PC in the fastboot folder and type:
fastboot oem writesecureflag 3
Then, reboot the phone thrice. It will be S-ON again
Click to expand...
Click to collapse
I think I have already done most of it, i got the md5 check error to go away, and installed a standard HTC that had the CID HTC_002 available in the build prop. I then flashed stock recovery. Fastboot booted in to CWM and ran the remove tampered. Lock bootloader.. I have just changed the CID From 111111 to HTC__002 and its booted fine. So The bootloader shows locked, no tampered or HTC red developer message under the logo but still hs S-OFF on bootloader screen? what would happen If i s-on now?
edit: Not to worry I done the secuirty flag 3 command and its now s-on and still boots, ty to you both.. really appreciate it
edit: 2 the tampered has came back
edit: 3 back to s-off and bootloader unlocked, tamp flag back too
Related
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.
I have a T-MOB101 (Germany device HTC One), and i would like to revert it back to stock and sell it.
Read all the guides here at XDA, but couldn't achieve it.
My device now is:
HBOOT 1.54.00
S-Off with SuperCID 11111111
Unlocked bootloader
ARHD 13.4 rom
There isn't any RUU for T-MOB101. I found a CWM stock Nandroid backup but for some reason CWM can't install it.
I've installed the odexed 2.24.401.1 stock rom, reverted the CID back to T-MOB101, locked the Bootloader but now it says RELOCKED instead of LOCKED. And couldn't make it S-On maybe because of the HBOOT 1.54.00?
Please, help me, i would like to sell the device and the future owner don't have any issues with the warranty.
So, unlock your bootloader, go here, download the 1.44 hboot and flash it with the guide.
After, use the revone tool to go locked and s-on
Guich said:
So, unlock your bootloader, go here, download the 1.44 hboot and flash it with the guide.
After, use the revone tool to go locked and s-on
Click to expand...
Click to collapse
Thanks for the reply Guich.
I'm kinda lost in the above thread.
1) Which Base Firmware should i download for T-MOB101 German device? I would like for it to have automatic updates for the future.
2) After that i will have to download the HBOOT 1.44.0000 Original unmodified, right?
3) In which order should i flash them? It's the same method for both Base Firmware and HBOOT?
4) Lastly, my bootloader now is unlocked with the HTC's method. How i can use the Revone to go Locked and S-On? Also, when should i change the CID to T-MOB101 from SuperCID 11111111?
Excuse me for all these questions, after almost 8 hours in front of the PC with no luck my head's gonna explode..
Thanks a bunch,
Bill
bill_viper said:
Thanks for the reply Guich.
I'm kinda lost in the above thread.
1) Which Base Firmware should i download for T-MOB101 German device? I would like for it to have automatic updates for the future.
2) After that i will have to download the HBOOT 1.44.0000 Original unmodified, right?
3) In which order should i flash them? It's the same method for both Base Firmware and HBOOT?
4) Lastly, my bootloader now is unlocked with the HTC's method. How i can use the Revone to go Locked and S-On? Also, when should i change the CID to T-MOB101 from SuperCID 11111111?
Excuse me for all these questions, after almost 8 hours in front of the PC with no luck my head's gonna explode..
Thanks a bunch,
Bill
Click to expand...
Click to collapse
1) I will advise you to transform your T-MOB phone into an unbranded phone.
So, donwload the 1.29 firmware umodified and flash this.
2) Yupp, 1.44 hboot and go s-on and locked
3) Use the guide, i will advice firmware and after hboot.
4) Yup, with 1.44 hboot you can use the revone tool for go to LOCKED and not RELOCKED and s-on
But, before go to s-on, change the cid into HTC__001.
5) If you're tired do this tomoz
p.s. If you need more help, you can contact me in pm
Hoping you guys can help me
I s offed my phone using rumrunner, downgraded my hboot to 1.44 and restored my 1.29.206.7 O2 stock nandroid backup. I ran revone, locked the bootloader, removed tampered and updated to the latest 3.62.206.1 firmware. I need to send the phone back for repair so I did fastboot oem writesecureflag 3. I rebooted the phone and on first reboot the phone boot to the lock screen, froze and then reboot. This kept happening until a factory reset, after which the bootloader read as tampered and locked
My bootloader was 1.55 and not a modified hboot as I had come from hboot 1.44, although I don't think this hboot was for my model id or cid (I changed the android.info file to flash it)
How do I safely go to s-on for repairs? Or should I leave it as s off and locked bootloader. I'm sending it to o2 rather than HTC
I received an O2 HTC One that had had some messing.
Device was S-ON, Tampered, Relocked with FW 3.62.401.1, custom ROM and HBOOT 1.55.
I unlocked the bootloader using HTVDev and ran rumrunner over it to get it S-OFF.
Plan was to return it to stock. I followed a guide on here to return it which entailed:
S-OFF
Downgrade to HBOOT 1.44
Change CID to HTC__032
Run RUU for FW 1.28.401.1
Change CID to O2___001
Restore Nandroid 1.28.206.1
Lock bootloader
Remove tampered
OTA updates to 3.62.206.1
S-ON
Because I am a fool I forgot to Lock the bootloader and remove tampered before I went S-ON. I am now on 3.62.206.1 and rumrunner does not seem to work. I get to the same point every time...
Code:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (35/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
and then I get the FATAL error.
Things I have tried so far, all get to the same point:
1. Windows 7 w/ HTC Drivers provided with phone
2. Windows 7 w/ HTC Drivers downloaded
3. Windows 7 w/ CWM Drivers
4. Windows 8.0 w/ HTC Drivers provided from phone
5. Windows 8.0 w/ HTC Drivers downloaded
6. Windows 8.0 w/ CWM Drivers
7. Windows 8.1 w/ HTC Drivers provided with phone
8. Ubuntu 13.10
I am absolutely stumped. I can only assume that after the OTA update to 1.55 my phone is no longer vulnerable to whatever exploit Rumrunner uses.
Unless anyone else knows any reason for it to fail at this point?
Oh, and each OS was a clean install. I have spent a lot of time today on this!
Comedy- said:
Plan was to return it to stock. I followed a guide on here to return it which entailed:
S-OFF
Downgrade to HBOOT 1.44
Change CID to HTC__032
Run RUU for FW 1.28.401.1
Change CID to O2___001
Restore Nandroid 1.28.206.1
Lock bootloader
Remove tampered
OTA updates to 3.62.206.1
S-ON
Click to expand...
Click to collapse
That sound's awfully familiar, do I have anything to do with that?
If yes, then I said to S-On after 1st OTA ... not after OTA to 3.62
is you bootloader unlocked, or can you unlock bootloader using HTCdev?
nkk71 said:
That sound's awfully familiar, do I have anything to do with that?
If yes, then I said to S-On after 1st OTA ... not after OTA to 3.62
is you bootloader unlocked, or can you unlock bootloader using HTCdev?
Click to expand...
Click to collapse
The boot loader is unlocked. I can flash custom recovery and roms and also have the current rom rooted. It just appears that my HBOOT doesn't want to play ball.
It did indeed say to S-On after 1st OTA but also had a note that it may not be necessary. I read through and figured I would skip it as I was
, ironically, worried if I would successfully be able to S-OFF the next time around. I guess it was a kind of trial run and I was trying to play it safe.
Comedy- said:
The boot loader is unlocked. I can flash custom recovery and roms and also have the current rom rooted. It just appears that my HBOOT doesn't want to play ball.
It did indeed say to S-On after 1st OTA but also had a note that it may not be necessary. I read through and figured I would skip it as I was
, ironically, worried if I would successfully be able to S-OFF the next time around. I guess it was a kind of trial run and I was trying to play it safe.
Click to expand...
Click to collapse
Have you tried http://firewater-soff.com/
I didn't even know about that one. Thanks very much. It did the job!
Comedy- said:
I didn't even know about that one. Thanks very much. It did the job!
Click to expand...
Click to collapse
:laugh::laugh::victory::victory::victory:
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.
Vonrottes said:
I've got the new 5.14.531.1 RUU straight from the HTC website.
Click to expand...
Click to collapse
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??)
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??)
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
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://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
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://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
and remember to stay S-Off
Click to expand...
Click to collapse
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?
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?
Click to expand...
Click to collapse
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://forum.xda-developers.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?
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://forum.xda-developers.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?
Click to expand...
Click to collapse
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?
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?
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
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?
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?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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
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***
Click to expand...
Click to collapse
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?
Click to expand...
Click to collapse
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?
Click to expand...
Click to collapse
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.