Database Info

S-off with HTC Dev tool?

Just got my Sensation back from repair, so now it's already on 4.03 ICS. I remember from before there was some discussion of the new HBOOT version not being about to S-off. However, HTC offers the unlock tool. Just wondering if it's a bad thing to do using their unlock tool or does it matter?

Look at the S-OFF guides for 1.2x.xxxx HBOOTs.
The wire trick is a pain but does work.
EDIT: meant to say that I believe you don't need the HTC unlock thing now. I used it but......

newr said:
Just got my Sensation back from repair, so now it's already on 4.03 ICS. I remember from before there was some discussion of the new HBOOT version not being about to S-off. However, HTC offers the unlock tool. Just wondering if it's a bad thing to do using their unlock tool or does it matter?
Click to expand...
Click to collapse
S-OFF and htcdev tool are two different things
htcdev tool only disables write protection on recovery partition - allowing you to flash custom recovery.
S-OFF unlocks all partitions including boot partition which means you can flash ROMs without flashing boot.img manually or needing to have 4EXT SmartSync on.
In short the htcdev tool is misnamed because it does not unlock the bootloader - only unlocks recovery

Jonny said:
In short the htcdev tool is misnamed because it does not unlock the bootloader - only unlocks recovery
Click to expand...
Click to collapse
only recovery ? isn't it recovery,system,boot and data partitions ?

ganeshp said:
only recovery ? isn't it recovery,system,boot and data partitions ?
Click to expand...
Click to collapse
Boot partition? no because you have to manually flash a boot.img with htcdev
system partition write protection is controlled by the OS and disabled by rooting - rooting allows the end user to give certain programs write permission. As to whether the recovery can access system and data partitions without unlocking the bootloader, I believe it can because stock recovery can overwrite system and data using OTA files controlled by a similar updater-script that we use in custom ROMs

Jonny said:
Boot partition? no because you have to manually flash a boot.img with htcdev
system partition write protection is controlled by the OS and disabled by rooting - rooting allows the end user to give certain programs write permission. As to whether the recovery can access system and data partitions without unlocking the bootloader, I believe it can because stock recovery can overwrite system and data using OTA files controlled by a similar updater-script that we use in custom ROMs
Click to expand...
Click to collapse
If boot partition is locked then you can't even flash boot.img via bootloader using fastboot flash command.. I think it has some issue getting flashed from recovery.. That's all
First to get root itself you require write permission on system partition.. That means at the end you require system partition unlocked.
The stock recovery can only flash signed stuff.. Thus a signature check is made.. (at the end unlocking of partitions is nothing but removing sign checking of whatever we flash)
Iirc the FAQ of htc-dev mentioned about what partitions are unlocked.... And those are what I mentioned
Sent from my HTC Sensation 4G using xda premium

[Q] Need info about bootloader mode and other stuff

Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!

LSGio said:
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
Click to expand...
Click to collapse
1. No, if you have S-ON you can't create a NAND backup as you don't have a custom recovery.
2. ***TAMPERED*** means that an app or apps have gone into your /system/ partition, thereby triggering the tampered flag. You can remove this message by running a HTC RUU.
3. No, you first flash the zip file with the boot.img inside, then flash the boot.img in the bootloader. fastboot flash boot boot.img

1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?

LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
Then yes you can make a backup and restore later. Just always full wipe, cache and dalvik cache wipe.
As far as flashing kernels/boot.img, if you are < hboot 1.13 then just flash via recovery. If your hboot is > or = to hboot 1.13tjen flash via fastboot or flash img GUI (available in the play store and in various threads).
And as of right now there is no s-off for the one s.
Sent from a baked One S
If I've helped hit the thanks button

LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.

KACE321 said:
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
Click to expand...
Click to collapse
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?

LSGio said:
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
Click to expand...
Click to collapse
fastboot oem writecid 11111111

usaff22 said:
fastboot oem writecid 11111111
i have 2 questions:
1.how many 1's do i have to write
2.can i get back to my cid and how?
Click to expand...
Click to collapse

Yes, you can make nand backups and restore them if you have a custom recovery. You don't need to have s-off for that but you do need to have your bootloader unlocked. Depending on your hboot version, restoring a nand backup will not restore your boot image. (1.09 and below will, 1.13 and up won't.) We do now have the means to downgrade hboot tho.
You get the *tampered* line if your recovery is unsigned. When you use a custom rom, you will most likely also get a red warning text over your boot splash. It's normal.
You have to extract the boot image from the rom zip and flash it in fastboot before you boot the new rom. This may even be before you flash the new rom. You can leave the rom zip unchanged and flash it in recovery.
-Jobo

if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Sent from my HTC One S using xda app-developers app

LSGio said:
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Click to expand...
Click to collapse
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
LSGio said:
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Click to expand...
Click to collapse
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.

touch of jobo said:
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
Click to expand...
Click to collapse
can you please tell me how can i download an ruu that matches my stock rom. cause when i get to the filefactory server it tells me that i need to buy premium because the file is larger than 500MB.
and the link to the ruu downloads is from this thread:
http://forum.xda-developers.com/showthread.php?t=1543588
if youll go to the first page and click the (ville S4) link you will see a list of ruu's but i can't download them because the size of them is larger han 500mb and i need premium.

Bootloader detail differences?

Im on at&t one x with hboot 1.14, considering to downgrade the BL so that i dont need to flash boot.img separately.
Before that, i was wondering what could be the detail differences between each BL versions?
Anyone??
Sent from my HTC One XL

Ill take a stab at it, but im probably wrong The way I understand the difference is how HB 1.14 is partitioned in a way that is blocked and only accessible through bootloader and fastboot adb for 1.14 and older versions are not. Some one chime in with the wrong buzzer for me maybe?
Sent from my One X using xda premium

subarudroid said:
Ill take a stab at it, but im probably wrong The way I understand the difference is how HB 1.14 is partitioned in a way that is blocked and only accessible through bootloader and fastboot adb for 1.14 and older versions are not. Some one chime in with the wrong buzzer for me maybe?
Sent from my One X using xda premium
Click to expand...
Click to collapse
I do believe you are correct, if not fully correct, partly.

1.14 versus prior:
It at least blocks write access to some partition under some circumstances.
Eg:
-boot partition(includes kernel) is only writable from the bootloader, not from recovery.
-radio partition is only writable by RUU.
It may include other changes that have not been noticed. The below is only suggestions of things that may have been improved but may not
Eg:
-improvements in resilience to some faults that could end in bricked phones.
-improvements to tests to verify only signed code is being written to critical partitions
PS. the locking of the boot partition is not a new concept to HTC.
TWRP has previously released workarounds for other phones which involved flashing TWRP to boot instead of recovery to overcome the lock.
http://www.teamw.in/project/htcdumlock

twistedddx said:
1.14 versus prior:
It at least blocks write access to some partition under some circumstances.
Eg:
-boot partition(includes kernel) is only writable from the bootloader, not from recovery.
-radio partition is only writable by RUU.
It may include other changes that have not been noticed. The below is only suggestions of things that may have been improved but may not
Eg:
-improvements in resilience to some faults that could end in bricked phones.
-improvements to tests to verify only signed code is being written to critical partitions
PS. the locking of the boot partition is not a new concept to HTC.
TWRP has previously released workarounds for other phones which involved flashing TWRP to boot instead of recovery to overcome the lock.
http://www.teamw.in/project/htcdumlock
Click to expand...
Click to collapse
Boot partition is writeable while booted into system as well, this is how dumlock works
I do believe the radio partition can be wrote while booted into system as well. And probably other partitions.
Its just the recovery partition that is locked down
But you're right this isn't a new concept, this was just a fluke being able to flash kernels in recovery. Usually its locked down
Sent from my One X using Tapatalk 2

twistedddx said:
1.14 versus prior:
It at least blocks write access to some partition under some circumstances.
Eg:
-boot partition(includes kernel) is only writable from the bootloader, not from recovery.
-radio partition is only writable by RUU.
It may include other changes that have not been noticed. The below is only suggestions of things that may have been improved but may not
Eg:
-improvements in resilience to some faults that could end in bricked phones.
-improvements to tests to verify only signed code is being written to critical partitions
PS. the locking of the boot partition is not a new concept to HTC.
TWRP has previously released workarounds for other phones which involved flashing TWRP to boot instead of recovery to overcome the lock.
http://www.teamw.in/project/htcdumlock
Click to expand...
Click to collapse
Great explanation! Thaaanks! I am more informed now

subarudroid said:
Ill take a stab at it, but im probably wrong The way I understand the difference is how HB 1.14 is partitioned in a way that is blocked and only accessible through bootloader and fastboot adb for 1.14 and older versions are not. Some one chime in with the wrong buzzer for me maybe?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Appreciated the explanation, Thanks

Restoring CID after unlocked bootloader?

Im currently at the process of unlocking bootloader i ran a exploit and it is 1111 what ever cid.
After i do this htcdev and flash update.zip of super user for root.
How do i change my cid back to my original?
And i hope i didnt have to memorize what my cid what otherwise im crewed.
Thanks, Reason for this is i read around and people had issues with the side being 11111 like for updating the rom or omething like that i dont want to run into that problem afterwards. But if its not really needed please tell me that.

I believe, as long as you never take a OTA an stick with rooted Xda roms you'll be golden.
WR
Injected from My ViperXL

So this seems to be the closest existing thread to ask my question:
Is it possible to change the CID of a Rogers One X to Super CID after having the phone wiped? (No OS installed)
Long stupid story short: I have a Rogers One X, bootloader unlocked, TWRP, regular CID, (which I understand is my grand mistake stopping me from mounting /data, /cache, and /system in order to flash any roms), and no OS to run any of the posted exploits to change CID.
EVITA PVT SHIP S-On RL
HBoot-2.14.0000
Any help, advice, or cold-hard truth is greatly appreciated so I can get this shiny paper weight active again.

if you have twrp installed you should be able to mount the sdcard from recovery transfer the rom.zip over unmount and install a rom

jerrycoffman45 said:
if you have twrp installed you should be able to mount the sdcard from recovery transfer the rom.zip over unmount and install a rom
Click to expand...
Click to collapse
I can mount the sdcard, but every time I try to install a rom (Viper, Nocturnal, CM) it errors out trying to format /cache, /data and /system directories for the install. The terminal in TWRP says that it can't mount any of these volumes (even though I go into aroma file manager and ensure the read/write permissions are checked). The only remaining problem I can find is that I don't have Super CID which would give me access to those directories.

if you are on the most current version of twrp that is your problem there are a lot of problems with it go back to 2.3.3.0 http://techerrata.com/browse/twrp2/evita

Thanks for the quick responses! I've tried a bunch of those recovery versions (some the screen would't work), but they all come up with the same problem: rom installation gets hung up at the part where it wants to format the specific drives. And terminal still says it can't mount the same 3 directories

might need to ruu and start over

Just go S-off and that will stop any problems you may have with updating with a CID 11111111. No need to change the CID back to original.

I'd love to just S-off, but the problem is I don't have SuperCID and no OS to utilize any of the exploits to get it. Looks like starting over is my only option, now to just find the correct RUU as every one I've tried comes back with wrong carrier or ID errors. Thanks for the help!

sixalive said:
I'd love to just S-off, but the problem is I don't have SuperCID and no OS to utilize any of the exploits to get it. Looks like starting over is my only option, now to just find the correct RUU as every one I've tried comes back with wrong carrier or ID errors. Thanks for the help!
Click to expand...
Click to collapse
What is your CID now?

My CID is still the stock ROGER001 (HTCdev unlocked bootloader without changing it (boneheaded move I know now)), but last night while searching for that RUU I came across a ROM that worked for my build So now it's up and running.

Converting AT&T carrier unlocked HTC One A9 from stock 1.27.502.5 to Nougat

Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz

bbsmitz said:
Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz
Click to expand...
Click to collapse
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4

alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update? I'm guessing it will void my warranty, but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back.) I guess my question is, warranty aside, is there really any negative to turning S-off?
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Thanks again for your time.
Best,
Bbsmitz

bbsmitz said:
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update?
Click to expand...
Click to collapse
No, after converting to another version, you'll receive ota updates for that version.
I'm guessing it will void my warranty,
Click to expand...
Click to collapse
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back
Click to expand...
Click to collapse
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
I guess my question is, warranty aside, is there really any negative to turning S-off?
Click to expand...
Click to collapse
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Click to expand...
Click to collapse
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.

alray said:
No, after converting to another version, you'll receive ota updates for that version.
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.
Click to expand...
Click to collapse
Edit2: I figured out the problem. I had to boot into the bootloader and then run
Code:
htc_fastboot oem rebootRUU
before I could run the RUU sucessfully. Am leaving the rest of this post up just so that other people googling this have a touch point.
Okay so I've used Sunshine to turn s-off and unlock my bootloader. I then changed my CID to BS_US001.
I then tried to install the HTC version of Marshmallow (maybe silly, but heard people having issues with Nougat and the battery) using the RUU.exe file. It started successfully, but then halfway though, after it had transferred the ROM over, it threw an ERROR155 and aborted, leaving my phone with an empty progress bar, and that circular green arrow icon in the middle. I used the command line to restart my device and had to factory wipe it, but otherwise not the worse for wear.
I tried googling it; do I need to relock my bootloader for the RUU.exe files to work? I think the Sunshine FAQ recommended against doing that. Is this a risky step?
Edit: Here are some instructions I found from the HTC One M8 firmware flashing thread. My error says "unknown" but I imagine its similar.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
Click to expand...
Click to collapse

help
Is this guide convert AT&T bindings factory unlocked htc? I cant access wifi hotspot. also cant run RRU.

hiii i have htc one a9300 by mistak i wipe every thing including internal memory now my fon sows that no "os install are you sure wanto reboot " please tell me wat to do now

AT&T conversion
alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
How do I get started to do this. How do I find out my mid Cid and if I need to change? How do I flash firmware first? I have android 6.0 software 1.27.502.5. I have done a run before but never changed from a carrier. I went to the link above but I don't know what some if this means and where to start and what steps to take in order.