Database Develop

Is it possible to go back to Stock - Completely - To sell the phone?

I have a Mint Condition HTC One phone I am trying to sell - Mostly just because I also own a Nexus 4 and love it - and decided I'd rather keep it and use the money on the HTC One on something else.
I'm having a hard time selling it because the "everything is unlocked" is making people scared to buy it.
It's S-OFF, SuperCID, TWRP 2.6.0.1, Bootloader Unlocked, Running 2.24 Firmware and Android Revolution 12.1, Sim Unlocked too.
It's originally a Rogers Canada HTC One
Is there any way (or guide) to completely make it stock again to help sell it? Any help would be appreciated.

Yep, just flash the Rogers RUU (if available) and then you're good to go! If there isn't one then use one of the Nandroids provided and then get the stock recovery and relock the bootloader

don't forget to go back to S-ON after flashing the RUU

herwegan said:
don't forget to go back to S-ON after flashing the RUU
Click to expand...
Click to collapse
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.

bigystyle84 said:
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.
Click to expand...
Click to collapse
just download the RUU (sorry, don't know if there is one for your carrier), be sure to be s-off, and then run the RUU.exe or flash the RUU.zip.
the RUU will flash stock recovery, stock rom and i think it will even relock your bootloader. and then you'll be able to download OTA-updates again.
last step is to put it back to s-on and you should be done..

Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app

EnIXmA said:
Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thanks
I'm S-OFF using the Revone Method
I'm on firmware 2.24 and HBoot 1.54 (Still S-Off though)
If anyone has time, can somebody give me a real quick overview on what I need to do? I'll buy ya a beer!
I'm not real familiar with HTC Devices - This was my first experience and to be honest, Right now I'm wishing I didn't do this if I knew before hand I was going to flip it so fast.

Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers

herwegan said:
Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers
Click to expand...
Click to collapse
You cant run the RUU with Super CID. You will have to change it to one that matches the RUU you choose before running it, but keep s-off. Then you should be able to use the tool as mentioned above or do all the things manually. You can use my guide if you like:
http://forum.xda-developers.com/showthread.php?p=43458497

Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)

Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!

bigystyle84 said:
Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Click to expand...
Click to collapse
you could take the latest open europe RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7), or take an AT&T one.. don't really know which one would be better for your situation you'll know it better
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Click to expand...
Click to collapse
this is also an option. you can flash this nandroid backup through cwm recovery. but then you'd have to manually install stock recovery and lock the bootloader/go back to s-on. why not :good:
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Click to expand...
Click to collapse
you can stay on 1.54 if everything works fine after flashing the older firmware. the "warning text" is related to this thread: http://forum.xda-developers.com/showthread.php?t=2316726
but if you've never installed a custom HBoot you don't have to worry about this when going back to s-on. just check once if the red warning text in the bootscreen is there.
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)
Click to expand...
Click to collapse
hope it works :fingers-crossed:

crushalot said:
Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!
Click to expand...
Click to collapse
Hey, I'm trying to do the same thing as OP, and this thread has been the closest thing to my issue. I'm trying to return everything on my phone to stock, however my Canadian carrier is Bell. Currently my HTC One has the bootloader unlocked, is rooted, TWRP recovery, and TrickDroid installed.
If I understand your instructions correctly, what I should do (given I want to restore using a nandroid backup) is:
1) S-Off my phone
2) Change the CID to CWS___001 and run the ATT RUU
3) Change the CID back to my original (BM_001 is what I think it is, do you know how I can make sure? What command to run for ADB?)
4) The Nandroid backup from http://forum.xda-developers.com/showthread.php?t=2207874&highlight=bell+update for my phone is for CWM (it's this one: M7 CWM Nandroid Backup / CID BM___001 / 1.29.666.5), does that mean I have to change my recovery from TWRP to CWM at this point?
5) Use fastboot to boot the recovery --> two questions regarding this, 1) why would I not install the .zip I downloaded from step 4? 2) where do I get the recovery.img? Just the one that is in the zip? In which case, shouldn't I also has to boot the boot.img or anything else?
6) I also want to upgrade the radio, should that be done last?
Thanks for all your help!
Lastly, I'm looking for a ROM to flash afterwards, I was wondering if you had any suggestions/know of a ROM that can allow me to use the swipe2sleep features, as well as hold the back touch button to force kill an app.

Just sell it on swappa. They love rooted unlocked modded phones.

S-OFF Necessary?

Is it necessary to s-off for installing custom roms? is it more safe to install the roms and kernels like we do in one-x?
thx

kami2k said:
Is it necessary to s-off for installing custom roms? is it more safe to install the roms and kernels like we do in one-x?
thx
Click to expand...
Click to collapse
no its not necessary to S-OFF for installing custom ROMs, all you need is unlocked bootloader and custom recovery (TWRP/CWM):good:
and yes its totally safe to install roms and kernels without PC unlike on One X :laugh:
just flash 'em from recovery

The only benefit to S-OFF is you have a get out to get back to stock if you need to as you can flash one of the early RUUs that leaked. If HTC released RUUs to the public there would be no need to have S-OFF unless changing the splash screen is important to you

EddyOS said:
The only benefit to S-OFF is you have a get out to get back to stock if you need to as you can flash one of the early RUUs that leaked. If HTC released RUUs to the public there would be no need to have S-OFF unless changing the splash screen is important to you
Click to expand...
Click to collapse
S-OFF is needed I think if you want to change HBOOT or downgrade OS versions for ex from 4.2.2 to 4.2.1, but how about correct CID and S-ON again?

EddyOS said:
The only benefit to S-OFF is you have a get out to get back to stock if you need to as you can flash one of the early RUUs that leaked. If HTC released RUUs to the public there would be no need to have S-OFF unless changing the splash screen is important to you
Click to expand...
Click to collapse
So without S-OFF, I can't go back to stock ROM after installing custom ROM, right?
What about before installing a custom ROM, I create a backup with TWRP, can I use this backup to return to stock?

htcm7 said:
So without S-OFF, I can't go back to stock ROM after installing custom ROM, right?
What about before installing a custom ROM, I create a backup with TWRP, can I use this backup to return to stock?
Click to expand...
Click to collapse
Yes. You would only need s-off if an ruu isn't available for your cid.
Sent from my HTC One using XDA Premium 4 mobile app

If you have to ask then no....
S-OFF often introduces more problems then it's worth, especially when your not very experienced. It is a great tool to fix stuff when you really screw up, but it also allows a lot more control then most people can handle. If you so S-OFF then just remember to never S-ON unless you are already back 100% stock.
Sent from my HTC One using Tapatalk 4

Anyway if you are on the HBOOT 1.54 you wont be able to S-OFF...

htcm7 said:
So without S-OFF, I can't go back to stock ROM after installing custom ROM, right?
What about before installing a custom ROM, I create a backup with TWRP, can I use this backup to return to stock?
Click to expand...
Click to collapse
You will be able to go back to stock if you can get hold of the original recovery as well as using your backup (for the love of God make a backup!!!). S-OFF means you can use one of the rare publicly-leaked RUUs to get back to stock

EddyOS said:
You will be able to go back to stock if you can get hold of the original recovery as well as using your backup (for the love of God make a backup!!!). S-OFF means you can use one of the rare publicly-leaked RUUs to get back to stock
Click to expand...
Click to collapse
Sorry, not sure if i understand your information correctly.
What do you mean by 'get hold of the original recovery'?
If I backup stock ROM using TWRP and when I want to go back to stock, can I just restore my backup without a use of RUU?

htcm7 said:
Sorry, not sure if i understand your information correctly.
What do you mean by 'get hold of the original recovery'?
If I backup stock ROM using TWRP and when I want to go back to stock, can I just restore my backup without a use of RUU?
Click to expand...
Click to collapse
Yes but you wouldn't be able to install OTA updates without the original recovery image

so only if u want ruu u do s-off otherwise no reason......

S-OFF allows you to flash an RUU earlier than your current build, e.g. I can flash the 1.28.401.7 on top of my current 2.24.401.8 whereas without S-OFF I wouldn't be able to

but if a new rom came with new built u can install that, who needs s-off then?

As I originally said, you don't need S-OFF if you have no need to go back to stock. If you need to send the phone to HTC for repair, having S-OFF means you can get the phone back to 100% stock and showing 'locked' as opposed to 'relocked' so they won't know you've ever done anything to the phone.
Otherwise you're taking a chance on HTC refusing the repair

[Q] Developer Edition flashed to GPE, back to Stock?

I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)

docdoc518 said:
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
Click to expand...
Click to collapse
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk

n1234d said:
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!

docdoc518 said:
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
Click to expand...
Click to collapse
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk

so as long as the you are s-off, you can ruu to any version even if you are at 1.54 hboot?
n1234d said:
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse

You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first

EddyOS said:
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
Click to expand...
Click to collapse
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information

docdoc518 said:
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
Click to expand...
Click to collapse
Follow what eddy says, he's the man @eddy, how does the hboot version make a difference??
Sent from my iPod touch using Tapatalk

I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me

EddyOS said:
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
Click to expand...
Click to collapse
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.

You should be fine on that HBOOT, just try it and if it works it works! If not, you'll get an error and then you just following the second post in the GPe conversion thread

docdoc518 said:
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
Click to expand...
Click to collapse
Yep, go ahead and try, if it gives you an error, post back.
AFAIK, the dev edition BS_US001 gets OTAs the quickest, so you could keep it at that. SuperCID will allow you to flash any RUU/OTA, even of a different region/MID/CID
Nope, you're not being a pain We're all trying to learn and help here

Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:

docdoc518 said:
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
Click to expand...
Click to collapse
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result

EddyOS said:
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
Click to expand...
Click to collapse
Newbie move I suppose :angel: haha
I've been rooting and flashing ROMs on my Androids since the G1/Dream believe it or not, but with every new phone/manufacturer there's always new terminology and steps to be taken so I feel like I start over every single time, which honestly isn't much of a bad thing, keeps things exciting (even though HTC made the G1 but that was what feels like ages ago now)
Thanks again guys, it's hard not to feel intimidated but it's been an extremely pleasant experience learning from you. This is why xda is by far the best site you can find for these things.
Cheers

[Q] GPE to Sense

I was originally on Sense 6 with Hboot 1.57, however I made a switch to GPE and flashed the ruu. Prior to this I changed my cid to supercid 1111111 so that I could do so. My Hboot has dropped to 1.54.
If I wish to return to Sense do I need to find my regional ruu, or as I have changed my cid I can pretty much wwe release? Also, do I need to change my Hboot to a lower version or leave as is?
While I'm on GPE, can I flash aosp roms such as cm, aokp etc?
Thank you.

maritimesbob said:
I was originally on Sense 6 with Hboot 1.57, however I made a switch to GPE and flashed the ruu. Prior to this I changed my cid to supercid 1111111 so that I could do so. My Hboot has dropped to 1.54.
If I wish to return to Sense do I need to find my regional ruu, or as I have changed my cid I can pretty much wwe release? Also, do I need to change my Hboot to a lower version or leave as is?
While I'm on GPE, can I flash aosp roms such as cm, aokp etc?
Thank you.
Click to expand...
Click to collapse
1. The best way to get back your warranty (I think you want it) is to change CID to your stock CID and flash RUU for your CID.
2. Yoou don;t have to change Hboot coz RUU will do it for you so leave it as is.
3. Yes you can flash all Custom ROMS not only AOSP but it's good to have SuperCID.

No I'm not after keeping my warranty, just asking in case I wanted to switch back to Sense. I can flash a Sense rom over GPE? I wasn't aware that was possible. Figured I would need to go back to a Sense base via ruu.

maritimesbob said:
No I'm not after keeping my warranty, just asking in case I wanted to switch back to Sense. I can flash a Sense rom over GPE? I wasn't aware that was possible. Figured I would need to go back to a Sense base via ruu.
Click to expand...
Click to collapse
Yes to go back to Sense you should flash a Sense RUU. And to be on the safe side you should use the earliest ruu you can downgrading to hboot 1.4.4. Then update the phone to the latest sense.
If you don't use an ruu to revert you risk running into problems later. And as your obviously s-off do not under any circumstance 're-lock your bootloader or go back to s-on. you will be stuck with a brick.

Ok, any tips to avoid accidently relocking the bootloader?
I was checking the GPE conversion thread, it simply states flashing the hboot 1.44 ruu, flash a stock ruu, pretty much it? Is there anything that could cause the bootloader to lock or for me to lose s-off? I paid sunshine for that, don't fancy losing it again!!
Assume, I'll have to root and flash custom recovery again? Yeah don't fancy going through the unlocking bootloader procedure again.
I simply want to go back to Sense, retain s-off and my unlocked bootloader so I can continue flashing custom roms and all that fun.
I have supercid 1111111 which means I can use a Euro ruu or any other? I was on Vodafone UK.
Thanks,

maritimesbob said:
Ok, any tips to avoid accidently relocking the bootloader?
I was checking the GPE conversion thread, it simply states flashing the hboot 1.44 ruu, flash a stock ruu, pretty much it? Is there anything that could cause the bootloader to lock or for me to lose s-off? I paid sunshine for that, don't fancy losing it again!!
Assume, I'll have to root and flash custom recovery again? Yeah don't fancy going through the unlocking bootloader procedure again.
I simply want to go back to Sense, retain s-off and my unlocked bootloader so I can continue flashing custom roms and all that fun.
I have supercid 1111111 which means I can use a Euro ruu or any other? I was on Vodafone UK.
Thanks,
Click to expand...
Click to collapse
Well you'll be pleased to know that if you used Sunshine to s-off. Should you need it again you won't have to pay. You only pay once per device.
Locking the bootloader and switching s-on can only be done manually using specific fastboot commands. Or Very specific dd commands in recovery. It's not likely to happen accidentally.
I only warned you of it because some users made the mistake of thinking it was necessary. But if the phone ends up locked or s-on without a proper conversion they can become impossible to recover.

All done, quite painless really. Thanks for the help.

[Q] Problems with SunShine: what stock kernel to flash?

Hello,
I wanted to S-OFF my HTC One M7 and it looks like my last hope is use SunShine in the end.
Since I receive the following message when SunShine runs on my phone, I would like to receive some help to figure out what is the stock kernel I have to flash in order to run SunShine.
At the moment I use Elemental X kernel, as shown in the signature below, but I have not been able to find a kernel to meet the requirements. By the way, I have a rooted and unlocked phone, and I wouldn't like to come back to stock if possible.
Thanks

fbcyborg said:
Hello,
I wanted to S-OFF my HTC One M7 and it looks like my last hope is use SunShine in the end.
Since I receive the following message when SunShine runs on my phone, I would like to receive some help to figure out what is the stock kernel I have to flash in order to run SunShine.
At the moment I use Elemental X kernel, as shown in the signature below, but I have not been able to find a kernel to meet the requirements. By the way, I have a rooted and unlocked phone, and I wouldn't like to come back to stock if possible.
Thanks
Click to expand...
Click to collapse
1) do a nandroid backup in TWRP
2) install maximusHD, this one: http://llabtoofer.com/2014/12/02/htc-one-maximushd-46-0-0/
3) sunshine s-off
4) restore you nandroid backup

Hi!
Thanks a lot for your hint!
And what about doing as explained here instead? I mean where it says about "Step-by-step procedure before attempting to S-OFF (with the universal Rumrunner version for international variants)".
It doen't say anything about the hboot version. That should work I guess, without wiping anything by the way.

fbcyborg said:
Hi!
Thanks a lot for your hint!
And what about doing as explained here instead? I mean where it says about "Step-by-step procedure before attempting to S-OFF (with the universal Rumrunner version for international variants)".
It doen't say anything about the hboot version. That should work I guess, without wiping anything by the way.
Click to expand...
Click to collapse
rumrunner only works on hboot 1.54 and lower

clsA said:
rumrunner only works on hboot 1.54 and lower
Click to expand...
Click to collapse
OK, thank you.
So, I could flash a ROM having such hboot and then try rumrunner. If yes, can you suggest me some rom to flash? There's lot of stuff here in the forum, I get confused to be honest.

fbcyborg said:
OK, thank you.
So, I could flash a ROM having such hboot and then try rumrunner. If yes, can you suggest me some rom to flash? There's lot of stuff here in the forum, I get confused to be honest.
Click to expand...
Click to collapse
nope, you cant back flash your HBOOT at all unless you are already s-off, I see in your signature your on 1.57, sunshine is the only way to s-off your device, really the only way - (people still ask after saying this if there is another way), you also need as close to stock as possible to use sunshine.

I succeeded using Sunshine in the end, flashing a stock kernel (boot.img) extacted by a stock ROM.