I have been browsing through all the subforums within HTC One for the last few weeks. I've seen a number of threads and posts that talk about the topic in question, but, don't really answer what I am after. Hence, this thread.
I have the Dev Edition. Rooted. CWM 6.0.3.1. Stock ROM. On TMobile prepaid in the US. ROM version 1.29.1540.3.
On my previous phone (HTC Evo), I had CM7 and will probably ultimately end up with CM for this phone too. However, for the next few months I plan to stick with Sense. I know that there are custom Sense ROMs out there; however, I don't really have a pressing need to ditch the stock ROM. Another concern is that the various custom Sense ROMs are based on the international ROM/firmware (I see many threads that go back and forth on all GSM variants being identical or different... and the real vs perceived differences in radios). I intend to remain with TMobile for the near future and so, while I'd love to get the AWS band working, more importantly, I don't want to get any worse speed/performance than I already have. So, bottom line, current preference is to stick with the stock ROM.
That said, I see newer versions of the Stock ROM (here) and read about HTC releasing 4.2.2 based ROM in the near future and so on. I understand that with the CWM recovery installed, I will not get OTA updates from HTC (part of the draw of the Dev Edition was getting frequent updates from HTC - did not realize at that time that a custom recovery would nix OTA updates).
So, here's what I am unsure about - specifically for the Dev Edition...
Are these newer ROMs for the Dev Edition or have they been released for an international variant, but, found to work fine for the Dev Edition? From this list, it looks like the latter. If so, will I lose any functionality (such as performance on TMo) by flashing a 401.13 ROM?
If I did not have a custom recovery, would I have received this 401.13 ROM via an OTA update?
If I choose to flash the 401.13 or newer stock ROM, can I just flash the zip from CWM Recovery? I want to retain the CWM recovery and root. I see various threads that describe how to go back to stock, how to relock the bootloader, how to get back to stock recovery and get OTA updates. However, if all I want is this newer build of the stock ROM, what do I need to do (wipe what?, flash what?, root again?).
I've read about the differences between odexed and deodexed ROM. Mike's thread has links to both versions of the 401.13 build. Can I choose either of them or is there any dependency on anything else?
Thanks,
MediocreFred.
I am in the same boat with the exception that I am on AT&T. I also have CWM touch, rooted with RuperSU, and now wonder about the 4.2.2 update coming. I am reasonably sure that you'll need to un-root. I don't think youll need a stock recovery or to lock to boot loader since the dev version is gracefully unlocked. I would assume the dev OTA will cover those circumstances. As for the 401 rom, it will work, but why bother. It makes no changes to your current rom. 1503 is just dev of 1.29. same like 403 is international of 1.29. the version is 1.29. Please correct me if I am wrong as I also am pretty new to this. I can tell you that as of now AWS HSPA is a no go on the dev version for T-Mo. I am a bit pissed about the articles of perceived speed decreases on AT&T with the international or dev roms. It is not just a bar problem. The LTE speed IS SLOWER. I would go AT&T rom but um [email protected]#K that? I just hope HTC fixes it in the next Dev rom release or someone smarter than I does on this forum.
Anyone going to get the HTC One Google edition on the 26th next week? I already have Tmobile and I could just get it and pay 20 bucks a month to pay for it. Im just wondering if anyone is going to pick up the Google Edition?
Will it really have priority updates? or is that what people only say to make themselves feel better? Couldnt we just flash the ROM and Kernal from the Google Edition when Google updates it to android 4.3... 5.0 etc.. to the GSM varients? Since they all have the same components.
Its better to get the T-Mobile version and just flash the Google ROM on it. I forgot where I read that you can flash an AOSP ROM on a sense based variant but not vice versa.
Sent from my HTC One using xda premium
AttachedSilver said:
Its better to get the T-Mobile version and just flash the Google ROM on it. I forgot where I read that you can flash an AOSP ROM on a sense based variant but not vice versa.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Of course you can, why not? Just pick one - http://forum.xda-developers.com/forumdisplay.php?f=2120
SonicGD said:
Of course you can, why not? Just pick one - http://forum.xda-developers.com/forumdisplay.php?f=2120
Click to expand...
Click to collapse
hes talking about stock android to sense.
AttachedSilver said:
Its better to get the T-Mobile version and just flash the Google ROM on it. I forgot where I read that you can flash an AOSP ROM on a sense based variant but not vice versa.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
expertzero1 said:
hes talking about stock android to sense.
Click to expand...
Click to collapse
There would be no reason why the GE couldn't run sense. They are the same HW. I'd like to see the source of whoever made that claim.
You have two devices that have the same exact HW just running different SW. Why on earth would you be able to run AOSP on a Sense version and not run sense on the GE? It just doesn't make any sense whatsoever. Is it because the bootloader and partitions are different? if so with s-off that can certainly be changed.
GE will have the Nexus bootloader interface so it wont be a simple flash job to get Sense
@OP: better to get the T-Mobile version as it would be easy to switch between Stock and Sense
IINexusII said:
GE will have the Nexus bootloader interface so it wont be a simple flash job to get Sense
@OP: better to get the T-Mobile version as it would be easy to switch between Stock and Sense
Click to expand...
Click to collapse
As long as you have a custom recovery and the boot, system and data partitions are the same blocks you should be able to flash Sense just fine even with the GE bootloader. Even if the partitions aren't the same you can modify the update script for the sense rom to map to the proper boot/data/system partitions. The only thing I see being a problem is the partitions being different blocks. It doesn't make sense that you'll be able to flash the GE rom on the non GE device and not the other way around.
We have everything we need to convert to Google edition and back again. The key is fastboot mode. We should be able to install an ruu or push the images manually. The only question is will the RUU exe file recognize a converted phone. I'm assuming all we need to do is make sure the Cid matches or we use supercid
gunnyman said:
We have everything we need to convert to Google edition and back again. The key is fastboot mode. We should be able to install an ruu or push the images manually. The only question is will the RUU exe file recognize a converted phone. I'm assuming all we need to do is make sure the Cid matches or we use supercid
Click to expand...
Click to collapse
GE phones wont have any CID so i doubt the RUU would work in converted phones, unless Google gives us a way to flash to Sense version phones without changing the bootloader
IINexusII said:
GE phones wont have any CID so i doubt the RUU would work in converted phones, unless Google gives us a way to flash to Sense version phones without changing the bootloader
Click to expand...
Click to collapse
I've seen reports to the contrary regarding Cid on the Google edition.
gunnyman said:
I've seen reports to the contrary regarding Cid on the Google edition.
Click to expand...
Click to collapse
source?
http://www.gsmlover.com/htc-android-os/182358-htc-model-cid-list.html. Googl001
gunnyman said:
http://www.gsmlover.com/htc-android-os/182358-htc-model-cid-list.html. Googl001
Click to expand...
Click to collapse
well thats nothing official but if that is the case then it should be easy to switch back and forth
I've seen the CID in several locations and it's probably correct. I hope so anyway
I'm just ready for AOSP development to skyrocket.
-Sent from Marino's One-
IINexusII said:
GE phones wont have any CID so i doubt the RUU would work in converted phones, unless Google gives us a way to flash to Sense version phones without changing the bootloader
Click to expand...
Click to collapse
You will have fastboot commands with the GE bootloader just like you do on every nexus device (and HTC devices). The bootloader doesn't have to do with the rom.
If you have a system image or even a rom.zip you can flash in fastboot and it will be fine.
the way to flash a sense rom with the GE edition bootloader would be to flash it in recovery like any other rom or fastboot flash system system.img, fastboot flash boot boot.img. The bootloader doesn't care if it's sense or if it's senseless just as long as you're flashing to the correct partitions you should be fine.
And it will have a CID. It will most likely be a different CID than what's out there now. It might have a different model ID as well.
But hey.. what do I know? I'm just a noob and don't know what I'm talking about
The Google edition CID already exists in the hboot code. Just, well, 'Google' for it using a hex editor. Proof enough for me.
So it seems this was planned all along. Interesting.
So will we (those with the original One) be able to just SuperCID, flash the Google RUU, change CID to Google edition CID and effectively have a Google edition phone?
Or instead of that, will the excellent devs here just port the GE Rom and we can flash it that way, without getting OTAs of course...
Sent from my HTC One using xda premium
redbull123 said:
So will we (those with the original One) be able to just SuperCID, flash the Google RUU, change CID to Google edition CID and effectively have a Google edition phone?
Or instead of that, will the excellent devs here just port the GE Rom and we can flash it that way, without getting OTAs of course...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yup, pretty much. You should be able to just change the CID to the GE CID and then flash the RUU without using super cid but you'll be able to flash the ruu with super cid as well. I'm not sure if you need to hex edit one of the partitions to change change the CID to the GE CID to get OTA's or not(I think ther has been debate about this). The model ID might have to change as well if they use a different model number for the GE (Which I'm assuming they would)
First, sorry for this tread. I started to read across HTC ONE related treads, but then I give up on the end... just to many informations...
If i had time I'm sure that many if not all this questions are answered somewhere in HTC ONE forum.
I have only one day do decide if I'm going to buy HTC ONE, due to end of special promotion sale (with 24 months binding to my network provider), so I will really appreciate XDA and HTC community help, as I can't go trough all those 100+ treads in one day.
So here are my infos & questions:
I'm only interesting in HTC ONE for the reason that could be converted to Google Edition phone and that it's build quality and design is much better than Nexus 4. I own SE Xperia Ray and Nexus 7 both rooted and slightly modified, but mainly stock, and I love vanilla look and regular updates of Nexus from Gogole. I intend to run HTC ONE few weeks with STOCK and then go for GE.
I live in Slovenia/Europe, so HTC ONE will be bought here. It is SIM unlocked, not operator dependant, but may have some network operator/provider specific programs installed.
So I assume that this is International version of the phone (it's stated, that LTE is supported) and it comes with Android 4.1.2 version presumably not updated.
1.) If it is still on 4.1 Android will I be able to convert it to GE? What if is on 4.2.2 or 4.3? Is there already a correct stock GE rom for EUR version?
2.) Is S-OFF possible and needed also for EU version of ONE? (if yes, this is a must for changing CID, which is needed for a proper GE ROM installation? is my understanding correct?) On HTC site, One can be rooted officially, I assume this is also valid for EUR version. Even rooted phone needs S-OFF? meaning GE ROM cant be flashed? Sorry, S-OFF is something completely new for me (non-existing at Sony or Nexus 7)
3.) Will LTE work properly with GE (GE is for american phones this will be European/International) Are there any other restrictions, that I need to be aware if going for GE (radio versions...)?
4.) How is going back to stock HTC rom (in case of warranty claims)? Is it country specific and can be automatically done with HTC software (like Xperia and Sony PC Companion - Repair phone function) or is there generic ROM (like Google provides for Nexus 7, that can be flashed back. In this case should rom be country specific? Any simple way to dump and backup original stock rom that phone comes with?).
5.) OTA updates from Google. Some threads debating about working OTA, others have remarks that OTA won't work. So is it possible to convert to latest 4.3 GE with working OTA? (I love this feature on Nexus 7, but can be easily broken if some changes are done in root/system)
6.) ONE has 3 physical buttons (capacitive) below screen (not on screen like Nexus phones/tablets). Is GE version adapting those 3 buttons, or there are double buttons (on screen also visible). Is there a fix for that? I'm asking this as I have fully adopted to on "screen buttons" with Nexus 7
7.) Is it safe to assume that there will be also 4.4 KiteKat GE OTA/ROM for HTC ONE?
8.) Any other important stuff that i I'm not aware of it (some programs not working, DRM protection issues for some stock programs, etc)? So is GE convert a full convert or just partial and is better in this case to stick with Nexus phones?
Thank you all for answers in advance!
mirkuma said:
First, sorry for this tread. I started to read across HTC ONE related treads, but then I give up on the end... just to many informations...
If i had time I'm sure that many if not all this questions are answered somewhere in HTC ONE forum.
I have only one day do decide if I'm going to buy HTC ONE, due to end of special promotion sale (with 24 months binding to my network provider), so I will really appreciate XDA and HTC community help, as I can't go trough all those 100+ treads in one day.
So here are my infos & questions:
I'm only interesting in HTC ONE for the reason that could be converted to Google Edition phone and that it's build quality and design is much better than Nexus 4. I own SE Xperia Ray and Nexus 7 both rooted and slightly modified, but mainly stock, and I love vanilla look and regular updates of Nexus from Gogole. I intend to run HTC ONE few weeks with STOCK and then go for GE.
I live in Slovenia/Europe, so HTC ONE will be bought here. It is SIM unlocked, not operator dependant, but may have some network operator/provider specific programs installed.
So I assume that this is International version of the phone (it's stated, that LTE is supported) and it comes with Android 4.1.2 version presumably not updated.
1.) If it is still on 4.1 Android will I be able to convert it to GE? What if is on 4.2.2 or 4.3? Is there already a correct stock GE rom for EUR version?
2.) Is S-OFF possible and needed also for EU version of ONE? (if yes, this is a must for changing CID, which is needed for a proper GE ROM installation? is my understanding correct?) On HTC site, One can be rooted officially, I assume this is also valid for EUR version. Even rooted phone needs S-OFF? meaning GE ROM cant be flashed? Sorry, S-OFF is something completely new for me (non-existing at Sony or Nexus 7)
3.) Will LTE work properly with GE (GE is for american phones this will be European/International) Are there any other restrictions, that I need to be aware if going for GE (radio versions...)?
4.) How is going back to stock HTC rom (in case of warranty claims)? Is it country specific and can be automatically done with HTC software (like Xperia and Sony PC Companion - Repair phone function) or is there generic ROM (like Google provides for Nexus 7, that can be flashed back. In this case should rom be country specific? Any simple way to dump and backup original stock rom that phone comes with?).
5.) OTA updates from Google. Some threads debating about working OTA, others have remarks that OTA won't work. So is it possible to convert to latest 4.3 GE with working OTA? (I love this feature on Nexus 7, but can be easily broken if some changes are done in root/system)
6.) ONE has 3 physical buttons (capacitive) below screen (not on screen like Nexus phones/tablets). Is GE version adapting those 3 buttons, or there are double buttons (on screen also visible). Is there a fix for that? I'm asking this as I have fully adopted to on "screen buttons" with Nexus 7
7.) Is it safe to assume that there will be also 4.4 KiteKat GE OTA/ROM for HTC ONE?
8.) Any other important stuff that i I'm not aware of it (some programs not working, DRM protection issues for some stock programs, etc)? So is GE convert a full convert or just partial and is better in this case to stick with Nexus phones?
Thank you all for answers in advance!
Click to expand...
Click to collapse
With the new Rumrunner exploit, the version of HBOOT makes no difference UNLESS IT IS 1.55
S-OFF is definitely needed. It can be achieved with any HBOOT but 1.55 as of today.
Yes LTE will work properly.
If you can find a carrier-specific RUU for your modelid and cid, then you are as good as a stock device.
Can't help you with that one
The One has two active capacitative buttons (by default). Custom kernels enable the use of the HTC logo as a third button. You can always enable on-screen buttons if you prefer them.
I'd say it is safe to assume. Launching a "Google Edition" device and not supporting it for the first "major" update since release would be a disaster...
I'm no expert about the Google Edition but from what I understand it is pretty close to a Nexus device. I'm a big Sense 5 (and 5.5) sellout however and don't really understand why you'd want to do that but it's your choice. The updates still have to come through HTC and do NOT come directly from Google.
Thanks a lot!
attanasi0 said:
With the new Rumrunner exploit, the version of HBOOT makes no difference UNLESS IT IS 1.55
S-OFF is definitely needed. It can be achieved with any HBOOT but 1.55 as of today.
Yes LTE will work properly.
If you can find a carrier-specific RUU for your modelid and cid, then you are as good as a stock device.
Can't help you with that one
The One has two active capacitative buttons (by default). Custom kernels enable the use of the HTC logo as a third button. You can always enable on-screen buttons if you prefer them.
I'd say it is safe to assume. Launching a "Google Edition" device and not supporting it for the first "major" update since release would be a disaster...
I'm no expert about the Google Edition but from what I understand it is pretty close to a Nexus device. I'm a big Sense 5 (and 5.5) sellout however and don't really understand why you'd want to do that but it's your choice. The updates still have to come through HTC and do NOT come directly from Google.
Click to expand...
Click to collapse
Thanks a lot!
4.) Is there a way I can backup stock rom, that device comes with (I doubt that i will be able to find my carrier specific RUU)?
8.) I was thinking that HTC only update its own Sense ROM, and Google takes care about Google Edition ROM (so GE will be updated before Sense). But I might try Sense for a while and see if I can accept it.
In case of S-OFF, can new official HTC update or OTA, toggle it to S-ON again?
Most recommended tweaked Sense ROMS, that are smooth as GE?
Thank you.
mirkuma said:
Thanks a lot!
4.) Is there a way I can backup stock rom, that device comes with (I doubt that i will be able to find my carrier specific RUU)?
8.) I was thinking that HTC only update its own Sense ROM, and Google takes care about Google Edition ROM (so GE will be updated before Sense). But I might try Sense for a while and see if I can accept it.
In case of S-OFF, can new official HTC update or OTA, toggle it to S-ON again?
Most recommended tweaked Sense ROMS, that are smooth as GE?
Thank you.
Click to expand...
Click to collapse
4) A nandroid backup or RUU is pretty much essential once you start messing around with your phone. In my case, the RUU is not available but I do have a stock nandroid backup
8) Google updates Android and HTC brings it to the one skin-free. There is delay between Nexus releases and Google Edition releases, but it is WAY shorter than with most phones.
For the ROM, I really recommend Android Revolution HD by mike1986. It is smooth, adds cool customization options with the Sense 5 toolbox and simply adds to the HTC experience. F
You won't really need offical HTC updates or OTA if you decide to go with S-OFF. You could always S-ON back to stock but if you update the bootloader in a firmware update and it doesn't allow you to go back to S-OFF, you won't be able to live with yourself
attanasi0 said:
4) A nandroid backup or RUU is pretty much essential once you start messing around with your phone. In my case, the RUU is not available but I do have a stock nandroid backup
8) Google updates Android and HTC brings it to the one skin-free. There is delay between Nexus releases and Google Edition releases, but it is WAY shorter than with most phones.
For the ROM, I really recommend Android Revolution HD by mike1986. It is smooth, adds cool customization options with the Sense 5 toolbox and simply adds to the HTC experience. F
You won't really need offical HTC updates or OTA if you decide to go with S-OFF. You could always S-ON back to stock but if you update the bootloader in a firmware update and it doesn't allow you to go back to S-OFF, you won't be able to live with yourself
Click to expand...
Click to collapse
Thank you. I decide to go with HTC One despite, special S-OFF issue, that makes things little more complicated in comparison with other manufacturers (Sony or ASUS Nexus). Xperia Z1f (Honami mini) was my first choice, but unfortunately if will be only available in Asia/Japan, so I will switch to HTC.
Looking forward to playing with the One
Thanks for your help again!
attanasi0 said:
4) A nandroid backup or RUU is pretty much essential once you start messing around with your phone. In my case, the RUU is not available but I do have a stock nandroid backup
8) Google updates Android and HTC brings it to the one skin-free. There is delay between Nexus releases and Google Edition releases, but it is WAY shorter than with most phones.
For the ROM, I really recommend Android Revolution HD by mike1986. It is smooth, adds cool customization options with the Sense 5 toolbox and simply adds to the HTC experience. F
You won't really need offical HTC updates or OTA if you decide to go with S-OFF. You could always S-ON back to stock but if you update the bootloader in a firmware update and it doesn't allow you to go back to S-OFF, you won't be able to live with yourself
Click to expand...
Click to collapse
Finally i receive my HTC One (had to exchange the first unit because of the gap in housing).
My HTC One out of the box is:
Android 4.2.2,
Software ver. 2.24.401.8
Kernel: 3.4.10-g28df0d6
Baseband: 4A.17.3250.14:10.39.1150.04L
CID: [HTC__032]
S-ON
HBoot 1.54
I have on question tough:
can I update to 1.3.670597 (small 614 kb update fundamental for a bigger update) and from here to 3.62.401.1 update (678,48 MB, Android 4.3 and Sense 5.5) without S-OFF from the current version?
New update does make HBoot 1.55, but is seems that it is supported by Rumrunner (http://forum.xda-developers.com/showthread.php?t=2496687)
Should I bother with S-OFF now and then take OTA update (will I lose S-OFF after update?) or can I update to 4.3 & Sense 5.5 and then made S-OFF i i decide to go with custom fw?
P.S.
At the moment I'm actually satisfied with stock (very quick and stable, no delays in UI) and will probably not go for custom rom for a while (maybe just with root, to remove some of the bloat-ware).
Thank you for replay in advance.
mirkuma said:
Finally i receive my HTC One (had to exchange the first unit because of the gap in housing).
My HTC One out of the box is:
Android 4.2.2,
Software ver. 2.24.401.8
Kernel: 3.4.10-g28df0d6
Baseband: 4A.17.3250.14:10.39.1150.04L
CID: [HTC__032]
S-ON
HBoot 1.54
I have on question tough:
can I update to 1.3.670597 (small 614 kb update fundamental for a bigger update) and from here to 3.62.401.1 update (678,48 MB, Android 4.3 and Sense 5.5) without S-OFF from the current version?
New update does make HBoot 1.55, but is seems that it is supported by Rumrunner (http://forum.xda-developers.com/showthread.php?t=2496687)
Should I bother with S-OFF now and then take OTA update (will I lose S-OFF after update?) or can I update to 4.3 & Sense 5.5 and then made S-OFF i i decide to go with custom fw?
P.S.
At the moment I'm actually satisfied with stock (very quick and stable, no delays in UI) and will probably not go for custom rom for a while (maybe just with root, to remove some of the bloat-ware).
Thank you for replay in advance.
Click to expand...
Click to collapse
Sorry for the late reply,
I would S-OFF right now using revone as it is much simpler to use. Worst case scenario you relock bootloader and re-enable S-ON.
You will not lose S-OFF. Once you have it, it is yours to keep.
attanasi0 said:
Sorry for the late reply,
I would S-OFF right now using revone as it is much simpler to use. Worst case scenario you relock bootloader and re-enable S-ON.
You will not lose S-OFF. Once you have it, it is yours to keep.
Click to expand...
Click to collapse
To the topic: My current hboot is 1.54, I was thinking that revone only works until hdboot 1.44.
What about options for removing TEMPERED, UNLOCKED messages from boot -loader (I’m little confused here, there are so many treads and options which may work, or may not, including flashing parts of firmware..etc..Seems dangerous to me)?
If my understanding is correct, I need to unlock boot-loader, root, and then S-OFF....but after that to be able to update trough OTA (to Android 4.3/Sense 5.5 stock), I must revert all the changes made (excluding S-OFF), if I wish that OTA will be successful (again I’m not sure if there actually is RUU.exe for my current version of software and using nandroid online or CWM /TWRP recovery for backup again involves a lot of work after for going back to stock).
At the moment seems too much work for me, that’s why I was asking if updating to 4.3/5.5 hdboot 1.55 makes more sense, and only if I decide to try some custom rom, going towards S-OFF direction...
But still, I'm not completely sure, if I understand correctly how to remove red messages in boot loader (unlocked, tempered...etc) and how hard or dangerous is it.
What I’m thinking at the moment is:
Go to 4.3/5.5 wia OTA, and use it for a while, than make unlock, root, s-off and install TWRP, and make backup. Then remove some not needed apps (Facebook, Tweeter, Stocks...). In case of need returning back to stock (warranty repair in case of hardware failure, new OTA for stock, etc), use TWRP to restore back and then somehow revert all the changes after (unlock, unroot, factory recovery…). So what are my available options with my current / updated version? Is this easier to achieve if I do all this on hboot 1.54 and 4.22 android or can be also done under hdboot 1.55 and 4.3?
P.S.
But you were correct with your comments about Sense, it's not bad at all. I starting to like Sense UI, so maybe going towards Google Edition will not be needed at all.
mirkuma said:
To the topic: My current hboot is 1.54, I was thinking that revone only works until hdboot 1.44.
What about options for removing TEMPERED, UNLOCKED messages from boot -loader (I’m little confused here, there are so many treads and options which may work, or may not, including flashing parts of firmware..etc..Seems dangerous to me)?
If my understanding is correct, I need to unlock boot-loader, root, and then S-OFF....but after that to be able to update trough OTA (to Android 4.3/Sense 5.5 stock), I must revert all the changes made (excluding S-OFF), if I wish that OTA will be successful (again I’m not sure if there actually is RUU.exe for my current version of software and using nandroid online or CWM /TWRP recovery for backup again involves a lot of work after for going back to stock).
At the moment seems too much work for me, that’s why I was asking if updating to 4.3/5.5 hdboot 1.55 makes more sense, and only if I decide to try some custom rom, going towards S-OFF direction...
But still, I'm not completely sure, if I understand correctly how to remove red messages in boot loader (unlocked, tempered...etc) and how hard or dangerous is it.
What I’m thinking at the moment is:
Go to 4.3/5.5 wia OTA, and use it for a while, than make unlock, root, s-off and install TWRP, and make backup. Then remove some not needed apps (Facebook, Tweeter, Stocks...). In case of need returning back to stock (warranty repair in case of hardware failure, new OTA for stock, etc), use TWRP to restore back and then somehow revert all the changes after (unlock, unroot, factory recovery…). So what are my available options with my current / updated version? Is this easier to achieve if I do all this on hboot 1.54 and 4.22 android or can be also done under hdboot 1.55 and 4.3?
P.S.
But you were correct with your comments about Sense, it's not bad at all. I starting to like Sense UI, so maybe going towards Google Edition will not be needed at all.
Click to expand...
Click to collapse
It's up to you really. HBOOT 1.55 is now compatible with Rumrunner so upgrade away. Once you have S-OFF, you also get SuperCID, which gives access to all ROMs and firmwares (included stock ones, that are usually available here before the carriers even start testing). The Tampered flag is in fastboot, it is not linked to the red writing. To remove the red writing you must flash a custom firmware.
The easiness of going back to stock after having unlocked the bootloader and etc depends on the availability of RUUs and/or S-OFF.
attanasi0 said:
The easiness of going back to stock after having unlocked the bootloader and etc depends on the availability of RUUs and/or S-OFF.
Click to expand...
Click to collapse
Looking this:
http://www.htc1guru.com/downloads/ruu-file-downloads/ -> RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
It seems that my RUU.exe path is open? This seems to be 4.1.2 version of RUU with older radio, but it should give me OTA option to 2.24.401.8 (Android 4.2.2/Sense 5.0) and then OTA again to 3.62.401.1 (Android 4.3/Sense 5.5).
Can you please confirm this? Do I have a valid "easy" RUU.exe backup/downgrade path?
Thanks?
P.S.
There are some notes about touch not working properly going downgrade path to old firmware...will I be able to accept OTA anyway?
mirkuma said:
Looking this:
http://www.htc1guru.com/downloads/ruu-file-downloads/ -> RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
It seems that my RUU.exe path is open? This seems to be 4.1.2 version of RUU with older radio, but it should give me OTA option to 2.24.401.8 (Android 4.2.2/Sense 5.0) and then OTA again to 3.62.401.1 (Android 4.3/Sense 5.5).
Can you please confirm this? Do I have a valid "easy" RUU.exe backup/downgrade path?
Thanks?
P.S.
There are some notes about touch not working properly going downgrade path to old firmware...will I be able to accept OTA anyway?
Click to expand...
Click to collapse
Once you are S-OFF, you can downgrade using an RUU (since you should have SuperCID as well); meaning you can't be "stuck" S-OFF. S-OFF allows you to "factory lock" the bootloader (instead of "relock"), remove the "tampered" sign and flash the latest firmwares.
The RUU you found, while valid, would only work if you were S-OFF as it's older than the software on you HTC One right now. HTC1Guru has stock ROMs that include recovery for pretty much any firmware if for some reason you don't like RUUs or don't wanna go S-OFF but still want to flash ROMs.
Touch works starting at 2.24 and it simply doesn't work in Recovery, meaning you have to use the volume keys.
I've had my htc one for a while, and it has been flashed quite a bit, sense roms, aosp roms, and a google edition conversion. I went to flash cm on her the other day and downloaded cm for the m7tmo, and it didn't flash until i modified the updater-script. So I was looking through all of the RUU files and almost all of them say m7ul. My first question is, is this designation part of the hboot? Secondly I bought mine from a T-mobile (U.S.) If I would have paid attention to the bootloader would it have originally said m7tmo? and if not what phones are the m7att, m7tmo etc etc roms referring to? If it was originally m7tmo, how do I get it back to that state?
Thanks in advance.
n1gh7m4r3 said:
I've had my htc one for a while, and it has been flashed quite a bit, sense roms, aosp roms, and a google edition conversion. I went to flash cm on her the other day and downloaded cm for the m7tmo, and it didn't flash until i modified the updater-script. So I was looking through all of the RUU files and almost all of them say m7ul. My first question is, is this designation part of the hboot? Secondly I bought mine from a T-mobile (U.S.) If I would have paid attention to the bootloader would it have originally said m7tmo? and if not what phones are the m7att, m7tmo etc etc roms referring to? If it was originally m7tmo, how do I get it back to that state?
Thanks in advance.
Click to expand...
Click to collapse
The hboot has nothing to do with if its tmo/att etc...
Now, regardless if its att/tmo it'll say m7_ul (ul being its LTE capable) otherwise im pretty sure international phones will just show an m7_l on the bootloader instead
Specifically, since i too have a tmob one, the cid should be t-mob010 (it'll say this in the bootloader, unless you had changed to supercid before).
So your phone is still "tmobile", I believe the 'm7tmo' naming by cm is just a way for the rom makers to label the rom for whatever phone its for.
Excellent Smithers. Thank you.
Sent from my One using Tapatalk