I've spent the last couple of days researching and getting quite confused, but all I want to do is install the 4.2.2 stock leak onto my unrooted, untouched new Htc One with S-ON etc.
I have now got 3-4 conflicting posts explaining how to do it but surely there is a way that I can do this using only adb/fastboot, without unlocking bootloader, etc?
Kinda swimming in confusion at the moment...
You need to unlock through HTCDev. Or wait for OTA.
Related
So, with 4.2.2 rolling out , I have a question regarding firmware/radios.
I have a T-Mobile One with the bootloader unlocked from HTC Dev and a custom recovery. I still haven't gone S-Off, but I did flash the 4.2.2 leak from a couple weeks ago. My question is, since there seems to be a firmware update - should I install it on my T-Mobile HTC one, and if so, how would I go about doing that (I assume I'd have to S-off/SuperCID since the Tmobo version of 4.2.2 is still a long way off).
Thanks in advance for any answers - I'm mostly concerned since while the S-OFF process looks fairly painless, I'm always a lot more cautious with radios and such than I am with ROMS since the radios have the potential to brick your phone in nasty ways...
Should you update? Why yes. How? Flashing a stock version through recovery. You won't have wifi calling if you rely on it. I'm on 4.2.2, however I am s off. I've yet to understand how people brick their phones by flashing the wrong files. I go to a tread with the file name. The download file gas the name, and before flashing, you have to read the file name. I still font get it. But anyways, happy updating. Enjoy the phone
Sent from my HTC One using Tapatalk 4 Beta
snowkfh said:
So, with 4.2.2 rolling out , I have a question regarding firmware/radios.
I have a T-Mobile One with the bootloader unlocked from HTC Dev and a custom recovery. I still haven't gone S-Off, but I did flash the 4.2.2 leak from a couple weeks ago. My question is, since there seems to be a firmware update - should I install it on my T-Mobile HTC one, and if so, how would I go about doing that (I assume I'd have to S-off/SuperCID since the Tmobo version of 4.2.2 is still a long way off).
Thanks in advance for any answers - I'm mostly concerned since while the S-OFF process looks fairly painless, I'm always a lot more cautious with radios and such than I am with ROMS since the radios have the potential to brick your phone in nasty ways...
Click to expand...
Click to collapse
There's a good guide here for flashing firmware etc. It also has a link to the firmware package from the 2.24.401.1 base.
Hi,
I have follow up question to this.....Since there is no RUU for T-Mobile USA, how would we revert our firmware back to stock T-mobile firmware? Currently all we have for T-mobile are some stock nandroid backups, but I don't believe firmware packages are contained in those.
Sent from my HTC One using Tapatalk 2
i want share my experience since going around the forum have found that other where having the same issues and since i am just little more than a newbie i think that if i made everyone can make.
Sometime ago i gained s-off through revone method, got my rooting permission installed custom rom and when i saw the latest update from HTC decided to go back to stock.
Started the procedure (there are several thread on the forum) to go back to stock and all was working pretty smooth, i have the first version of RUU so i had to go through all the software update, once completed, i still had the phone unlocked, s-off but was not able to gain rooting, so not able to clean all the garbage (at least for me) installed apps, been through different forum and tried different think, changed ROM, recovery, few times etc when at last i thought ok, i stay for awhile with a full stock and wait, but since i am not that patient, yesterday i tried again with TWRP 2.6.3.3. and latest SuperSU 1.80 and it worked perfectly.
Hope this help someonelse
Hey xda,
I kind of feel like needing help understanding my situation. Normally I read a lot and understand all this stuff around modding quite ok, but I'm at a point with too many grey zones of half-understanding, I guess.
So I have an HTC ONE, bought in germany half a year ago, with Sense and all that HTC-branding. When the google edition came out, it was easy installing a custom recovery and a vanilla JB google rom (I'm not quite sure today why I did it, but I also flashed HBOOT to 1.54). There was no need thinking about s-off (I'm still s-on) and RUUs. Even OTAs worked seamless.
Then came the OTA for 4.4, I hit update and got stuck in a bootloop. Finding out that it was cwmr took me a while.. I began reading and realized that I would need s-off to install the OTAs. Here's my first question: Why? What changed that I can't install it via custom recovery like before?
And is it just a matter of time, until there's a flashable version of vanilla kitkat?
Now I'm running OneDroid by ssrij, which doesn't requires s-off - why doesn't this one need s-off, but most of the others do?
Any words for clarification would be really appreciated!
apptum said:
Hey xda,
I kind of feel like needing help understanding my situation. Normally I read a lot and understand all this stuff around modding quite ok, but I'm at a point with too many grey zones of half-understanding, I guess.
So I have an HTC ONE, bought in germany half a year ago, with Sense and all that HTC-branding. When the google edition came out, it was easy installing a custom recovery and a vanilla JB google rom (I'm not quite sure today why I did it, but I also flashed HBOOT to 1.54). There was no need thinking about s-off (I'm still s-on) and RUUs. Even OTAs worked seamless.
Then came the OTA for 4.4, I hit update and got stuck in a bootloop. Finding out that it was cwmr took me a while.. I began reading and realized that I would need s-off to install the OTAs. Here's my first question: Why? What changed that I can't install it via custom recovery like before?
And is it just a matter of time, until there's a flashable version of vanilla kitkat?
Now I'm running OneDroid by ssrij, which doesn't requires s-off - why doesn't this one need s-off, but most of the others do?
Any words for clarification would be really appreciated!
Click to expand...
Click to collapse
I would forget about the why and just get busy getting rumrunner to work to get s-off. just flash a stock rooted 4.3 rom and use rumrunner.
also make sure your on TWRP 2.6.3.3 before flashing any of the kitkat roms
this is as close to pure android as I could find
HTC One Nexus Edition 2.0
clsA said:
I would forget about the why and just get busy getting rumrunner to work to get s-off. just flash a stock rooted 4.3 rom and use rumrunner.
also make sure your on TWRP 2.6.3.3 before flashing any of the kitkat roms
this is as close to pure android as I could find
HTC One Nexus Edition 2.0
Click to expand...
Click to collapse
luckily I'm still happy with onedroid rom, so no need for further experiments
but the why is bothering me nonetheless. especially: is it just a matter of time (like something official isn't published yet) till there's a s-on flashable vanilla kitkat?
I have a M7 with a unlocked Bootloader, but nothing else has been changed. The phone has not been rooted in any way so my question is can I still take the upcoming Lollipop 5.0 OTA update.
Short answer: I believe so as long as you don't have a custom recovery installed. You may have to relock first (I'm not sure).
Long answer: I am s-off with a custom recovery. I was running the stock ROM from the RUU rooted with TWRP. It kept nagging me about an OTA so, after researching it to make sure it wouldn't break my s-off, I took it. It tried to install, but failed in recovery (TWRP didn't recognize the file and wouldn't install it). So, my guess is ... well, see short answer.
Having said that though, I wouldn't take the OTA. Usually within a few days (hours even) of an OTA, the masterminds on here have released something flashable that will not break things. Although you're just unlocked so it wouldn't be too hard to unlock again.
Long story short, I received the Lollipop update today only for it to say "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone....etc."
When I first got the phone it was from AT&T and thus had all the standard bloatware, etc. After tinkering around with rooting/unlocking I decided to convert it to the unlocked edition. I believe it is S-Off, and the Boot loader is unlocked, HBOOT-1.57.0000 with everything else pretty much unchanged. I'm still on AT&T currently if it helps. I've read that the bootloader needs to be locked in order for OTA updates to work properly?
I haven't rooted or tinkered with anything for months and so I've pretty much forgotten everything about it although I can catch up again pretty quickly. Apologies if the fix is something simple. I'd basically just like to be able to update to official stock Lollipop and stick with it.
mch277 said:
Long story short, I received the Lollipop update today only for it to say "We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone....etc."
When I first got the phone it was from AT&T and thus had all the standard bloatware, etc. After tinkering around with rooting/unlocking I decided to convert it to the unlocked edition. I believe it is S-Off, and the Boot loader is unlocked, HBOOT-1.57.0000 with everything else pretty much unchanged. I'm still on AT&T currently if it helps. I've read that the bootloader needs to be locked in order for OTA updates to work properly?
I haven't rooted or tinkered with anything for months and so I've pretty much forgotten everything about it although I can catch up again pretty quickly. Apologies if the fix is something simple. I'd basically just like to be able to update to official stock Lollipop and stick with it.
Click to expand...
Click to collapse
Read this, I did this last night and got lollipop, as your s-off and on "unlocked" edition anyway, this will be4 easy for you: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311
Ah, thank you! That worked flawlessly.