First of all, I want to say hello to all of you. HTC One is my first HTC smartphone (I'm coming from Samsung devices). There is many significant differences between those two brands when it comes to rooting and moding the software. Still there are some things that are unclear for me and I would appreciate any answers from experienced users or developers.
Some facts about my phone:
Unlocked and S-OFF by revone
SuperCID
Android Revolution HD 12.2 custom rom
Now the main question is: In some cases it is important to update phone with firmware.zip (part of OTA update) file which contains updated drivers, hboot, radio, etc. before flashing newer base of the custom rom. Will my phone stay S-OFF'ed after the update (firmware.zip's contains newer hboots and that's what made me worried).
Thanks!
matee89 said:
First of all, I want to say hello to all of you. HTC One is my first HTC smartphone (I'm coming from Samsung devices). There is many significant differences between those two brands when it comes to rooting and moding the software. Still there are some things that are unclear for me and I would appreciate any answers from experienced users or developers.
Some facts about my phone:
Unlocked and S-OFF by revone
SuperCID
Android Revolution HD 12.2 custom rom
Now the main question is: In some cases it is important to update phone with firmware.zip (part of OTA update) file which contains updated drivers, hboot, radio, etc. before flashing newer base of the custom rom. Will my phone stay S-OFF'ed after the update (firmware.zip's contains newer hboots and that's what made me worried).
Thanks!
Click to expand...
Click to collapse
Your phone will always stay s-off unless you specifically command it to go s-on. (which imo is a pointless thing to do)
Sent from my HTC One using xda premium
matee89 said:
First of all, I want to say hello to all of you. HTC One is my first HTC smartphone (I'm coming from Samsung devices). There is many significant differences between those two brands when it comes to rooting and moding the software. Still there are some things that are unclear for me and I would appreciate any answers from experienced users or developers.
Some facts about my phone:
Unlocked and S-OFF by revone
SuperCID
Android Revolution HD 12.2 custom rom
Now the main question is: In some cases it is important to update phone with firmware.zip (part of OTA update) file which contains updated drivers, hboot, radio, etc. before flashing newer base of the custom rom. Will my phone stay S-OFF'ed after the update (firmware.zip's contains newer hboots and that's what made me worried).
Thanks!
Click to expand...
Click to collapse
You will stay S-off through a firmware upgrade. Once S-off, the only way to go S-on is to set the secure flag yourself
Thanks for clarifying this for me !
One more question. I need to relock the bootloader when flashing the firmware.zip, even if I'm S-OFF'ed right?
In case I'm relocked and S-OFF on hboot not supported by revone, can I still downgrade it to the 1.44 without any problems?
I just don't want to ever use htcdev for unlocking.
You shouldn't have yo lock to flash firmware, I didn't. As far as downgrading hboot, since you have s-off, you can downgrade as long as you don't go to s-on for any reason.
But there's not many reasons to downgrade, your phone will still be s-off, unlocked, and without tampered flag on the new hboot. If it does relock, I believe you can use revone to unlock it again, since you've already used the exploit to gain s-off.
Or you can skip all that BS and flash the GE hboot, which can be locked or unlocked by "fastboot OEM lock/unlock"
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3
Actually, I found a great topic with firmware flashing guide by Volmer http://forum.xda-developers.com/showthread.php?t=2365506.
So I didn't need to relock my bootloader or had to wipe anything. For couple of minutes ago, I've updated my firmware from 1.29.x to 2.24 (with updated touch drivers etc.). Worked like charm I've got the newest hboot 1.54 and still S-OFF and unlocked
Thanks for info guys!
matee89 said:
Will my phone stay S-OFF'ed after the update (firmware.zip's contains newer hboots and that's what made me worried).
Click to expand...
Click to collapse
There are only a couple of ways to go back to s-on, and they are almost impossible to do accidentally. For practical purposes, unless you were to accept an OTA that HTC specifically designed to reverse s-off (something they have never done and are unlikely to ever do), you are s-off until you decide otherwise.
iElvis said:
There are only a couple of ways to go back to s-on, and they are almost impossible to do accidentally. For practical purposes, unless you were to accept an OTA that HTC specifically designed to reverse s-off (something they have never done and are unlikely to ever do), you are s-off until you decide otherwise.
Click to expand...
Click to collapse
That is, unless you go around flashing zips that are labeled "for development purposes only". A few people on here have flashed things when they didn't know what they're doing (and some that know exactly what they're doing) and lost s-off. After that you're stuck with s-on and hboot 1.54.
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3
CoryTallman said:
That is, unless you go around flashing zips that are labeled "for development purposes only". A few people on here have flashed things when they didn't know what they're doing (and some that know exactly what they're doing) and lost s-off. After that you're stuck with s-on and hboot 1.54.
Click to expand...
Click to collapse
That is one of the ways, actually. If you flash an s-on package with the p3 partition, where the secureflag is stored, that will do it. While one cannot flash things accidentally, I suppose it is possible to accidentally reset your secureflag if you're dumb enough to flash any old firmware package you find.
If that's you, you're one of those people who has to learn things the hard way, and your phone will pay the price.
iElvis said:
That is one of the ways, actually. If you flash an s-on package with the p3 partition, where the secureflag is stored, that will do it. While one cannot flash things accidentally, I suppose it is possible to accidentally reset your secureflag if you're dumb enough to flash any old firmware package you find.
If that's you, you're one of those people who has to learn things the hard way, and your phone will pay the price.
Click to expand...
Click to collapse
As unlikely as all that is, I figured it would be worth noting. Since Murphys law says that if you tell someone its impossible to lose s-off through flashing firmware, they're going to go find the only old firmware package floating around that would break their s-off.
AT&T HTC One
Baadnewz's InsertCoin 3.0-14
Flar2's Bulletproof 4.3
Related
Hey, I recently bought my HTC One and have been reading up on how to root etc. I'm looking for advice on how best to proceed. Currently my HTC one is running 4.1.2 with HBOOT 1.44.
Things seemed to have changed a bit since I last had a HTC (wildfire), now theres CID's, MID's, supercid and no goldcards. Things also seem a bit complicated compared to my SE Arc S, where you had one customization number and sony's software pulled the respective software.
At the moment, I want to be able to use root only apps (eg Titanium Backup) and update to the stock version of 4.2
Reading around, I've seen that rooting by unlocking the bootloader will block the OTA update to 4.2. Also, upgrading to 4.2 will update the HBOOT meaning that I won't be able to s-off. Even though, I currently don't need this, I don't want to update to the new HBOOT just in case.
My question is what would be the best way to get a stock rooted version of 4.2 without losing the ability to s-off?
Just looking for a bit of guidence, Thanks!
mike
I rooted to get 4.2 update bunch of custom roms already have them and there great roms I'm on viperone now but also have had revolution,trickdroid,cleanrom,ext all are stable don't need s off to flash but give it time and there will be an s off for 4.2.2
kasper1977 said:
I rooted to get 4.2 update bunch of custom roms already have them and there great roms I'm on viperone now but also have had revolution,trickdroid,cleanrom,ext all are stable don't need s off to flash but give it time and there will be an s off for 4.2.2
Click to expand...
Click to collapse
My phone is on HBOOT 1.44, it can be s-off at the moment.
My question was how to get stock 4.2 with root access without upgrading to HBOOT 1.54?
S-off,
Unlock boot loader,
Change cid to HTC__001,
Lock boot loader,
Run RUU for European developers edition,
Update by OTA,
Unlock bootloader,
Flash custom recovery,
Root device.
You will be on stock 4.2.2, and rooted. You also won't have to worry about the hboot because once you have s off you don't lose it.
AT&T HTC One
GPe 4.3
CoryTallman said:
S-off,
Unlock boot loader,
Change cid to HTC__001,
Lock boot loader,
Run RUU for European developers edition,
Update by OTA,
Unlock bootloader,
Flash custom recovery,
Root device.
You will be on stock 4.2.2, and rooted. You also won't have to worry about the hboot because once you have s off you don't lose it.
AT&T HTC One
GPe 4.3
Click to expand...
Click to collapse
Thanks for the reply
My cid is already HTC__001 (I bought it and it came with WWE ). Does that mean I can skip steps 2,3,4 and 5 in your list?
What is European developers edition?
Yes I suppose you can. WWE is world wide English. Which is what I believe comes on the developers editions. So you have HTC__001 already and have not received the ota? Like I said, if you want s off, get it before you upgrade. But if you don't need it you can upgrade without it and still root.
AT&T HTC One
GPe 4.3
CoryTallman said:
Yes I suppose you can. WWE is world wide English. Which is what I believe comes on the developers editions. So you have HTC__001 already and have not received the ota? Like I said, if you want s off, get it before you upgrade. But if you don't need it you can upgrade without it and still root.
AT&T HTC One
GPe 4.3
Click to expand...
Click to collapse
What EU developer edition? I assume he has the UK version so his stock rom would be the "HTC_Europe" version. Need his CID and MID numbers to confirm. I agree that he should run the S-off process first thing if he wants it.
My CID is HTC__001, I don't know what the MID is. I don't think it's the developer edition, I bought it from a retailer not HTC directly and it's 32GB. My software version is .401 and the OTA to 4.2.2 is available to me, I haven't updated yet because I don't want to be stuck on HBOOT 1.54.
Then you can s-off, update, you will retain s-off on the new hboot, unlock boot loader, flash a custom recovery and root.
AT&T HTC One
GPe 4.3
CoryTallman said:
Then you can s-off, update, you will retain s-off on the new hboot, unlock boot loader, flash a custom recovery and root.
AT&T HTC One
GPe 4.3
Click to expand...
Click to collapse
Thanks, if I unlock my bootloader with revone after s-off, is that exactly the same as doing it through htcdev?
fireice7 said:
Thanks, if I unlock my bootloader with revone after s-off, is that exactly the same as doing it through htcdev?
Click to expand...
Click to collapse
Yes it is, with the added bonus of HTC not knowing you've done it!
EddyOS said:
Yes it is, with the added bonus of HTC not knowing you've done it!
Click to expand...
Click to collapse
I guess another advantage is that your device doesn't get wiped on unlocking.
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
From what I've read, having HBOOT 1.54 basically means that you can't S-off your device (as this is only available for 1.44). This means that you won't have access to deeper customisation for your phone (flashing different firmware and changing CID). CID determines what region your phone belongs to so this translates to how early you can get official OTA's as some regions get updates earlier than others. Also, if you want to fully transform your phone into a Google Edition HTC One, this is only open to units with a specific CID.
As for firmware, not really clear on what the differences between firmwares are but you can still flash different radios which are a component of firmwares (thus getting some of the benefits of newer firmware anyway).
That being said, you can flash the whole range of custom ROMs and kernels available on these forums provided that you've unlocked your boot loader. Directions for this can be found on the HTC website.
If you want an optimised stock ROM, try ARHD Sense which is basically your stock ROM with many performance improvements (especially when it comes to signal). For more customisation on Sense, you can try ViperOne.
Honestly there are so many excellent ROMs here that you can easily lose days trying every single one. The Google Edition ROMs are excellent too.
Hope this helps!
Sent from my HTC One using XDA Premium 4 mobile app
Thank you both for detailed replies! This helped me ease my mind on the HBOOT-thing. Thanks!
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Michiel0211 said:
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
Click to expand...
Click to collapse
All you have to do is unlock your bootloader via htcdev.com (note, this will wipe your data) and then flash a custom recovery. You can use this tool http://d-h.st/mas to simplify the process.
CoryTallman said:
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
sixty_oz said:
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
No matter what, you should stay s-off, it does not affect OTA's or RUU's in any way whatsoever. To flash any RUU, you need to be with a cid of 11111111
It's not possible for you to flash an ruu for something else and then flash the rogers ota I don't think
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
Hey, I have an AT&T HTC one m7 running 4.1.2 and hboot 1.44
I was wondering which steps should I take to convert to a GPE in order to get an updated version of stock android (as I am not feeling very comfortable with HTC Sense).
Someone told me that I should do S-Off now and be happy ever after lol. Is it worth it??? If I have problems with camera tint, could I get it fixed or am I gonna have problems claiming the warranty?
1) What procedure should I use to do S-Off ??? I've seen like 3 different ones.
2) Doing S-Off also implies getting the bootloader unlocked right?
If you guys could point me in the right direction I'd be very grateful. Which guides I should follow to get from where I am, to a fully updated GPE phone?
Piachnp said:
Hey, I have an AT&T HTC one m7 running 4.1.2 and hboot 1.44
I was wondering which steps should I take to convert to a GPE in order to get an updated version of stock android (as I am not feeling very comfortable with HTC Sense).
Someone told me that I should do S-Off now and be happy ever after lol. Is it worth it??? If I have problems with camera tint, could I get it fixed or am I gonna have problems claiming the warranty?
1) What procedure should I use to do S-Off ??? I've seen like 3 different ones.
2) Doing S-Off also implies getting the bootloader unlocked right?
If you guys could point me in the right direction I'd be very grateful. Which guides I should follow to get from where I am, to a fully updated GPE phone?
Click to expand...
Click to collapse
1) The camera tint cannot be corrected unless you're on stock Sense firmware. Prior to S-OFF and a GPE ROM/firmware, the bootloader needs to be unlocked and phone must be rooted. Bootloader unlock and root voids warranty
2) First, unlock the bootloader. Then, flash a custom recovery and then, root. Then use Revone to S-OFF. HBOOT 1.44 is the least problematic, S-OFF is quite straightforward.
3) Yes, bootloader unlock is the first step towards S-OFF. It'll wipe the phone completely. So, make a backup first
Also note: To get the latest stock android build on your One, you have 2 options:
1) Complete conversion using an RUU. Link here:
http://forum.xda-developers.com/showthread.php?t=2358781
2) Flash a GPE-based ROM in custom recovery (Eg, Skydragon, ARHD, SinLess, etc.)
A full conversion involves much more steps; a ROM is more straightforward. You'll the the exact same GPE experience on either
Thank you for clarifying the steps. Every phone is different, and I got very overwhelmed with the info on this forum.
I'll get started with the bootloader unlocking and rooting!
Hi all. I just unlocked my HTC m7 (GSM) with HTCdev.com and then installed TWRP and used that to install SuperSU. After that, I ran Sunshine to get S-OFF, and then I ran Guru Bootloader Reset in order to remove the "tampered" flag. Then I set SuperCID to 11111111, and I think I'm ready to flash a rom (I"m looking at ViperOne, since I used it on my Sensation and liked it).
I'm on hboot 1.61. Is it worth downgrading to 1.44 so that I can easily get s-on/s-off in the future? If so, should I flash the new hboot before or after the rom? Does it matter?
Thanks all. I spent quite a bit of time flashing and testing roms on my HTC Touch Pro and then my HTC Sensation. I've held off for a couple of years, but I'm looking forward to playing around with my M7 again!
MPenguin said:
(...), I ran Sunshine to get S-OFF
(...)
I'm on hboot 1.61. Is it worth downgrading to 1.44 so that I can easily get s-on/s-off in the future? If so, should I flash the new hboot before or after the rom? Does it matter?
Thanks all. I spent quite a bit of time flashing and testing roms on my HTC Touch Pro and then my HTC Sensation. I've held off for a couple of years, but I'm looking forward to playing around with my M7 again!
Click to expand...
Click to collapse
Your phone is already S-OFF why would you want to turn it back S-ON? Never go back S-ON, the only time it should be done is before sending the phone for repair under warranty. Going back S-ON is the same as intentionally locking your car with the keys left inside... And even if you go back S-ON why hboot 1.44 should make it easier to achieve S-OFF again? You just paid for Sunshine, you can use it as many time as you want on that phone + If you already have paid for Sunshine, its actually the easiest method to S-OFF your phone on any hboot version.
If I buy a SunShine license, can I use it on multiple phones?
No - one license is good for one device. You can reuse SunShine on that device, if necessary, we however NEVER recommending setting your device S-ON
Click to expand...
Click to collapse
ref: http://theroot.ninja/faq.html
Another thing to know is that hboot 1.44 is incompatible with windows 8 and 10, so say goodbye to fastboot connectivity (fastboot commands) after flashing it, unless you are using a Mac, Win7 or Linux.
For your last question, it doesn't matter when you flash the hboot, if you need to flash one. Would recommend to stay on 1.61