Database Develop

[Q] Firmware on carrier models??

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

[Q] Going back to 4.2.2 Sense from 4.3 Google Edition firmware?

Hello all, first time posting on this site. Apologies if I seem like a leecher because my first post happens to be asking for help
I want to make sure I have the right information handy before I attempt anything as I'm afraid of bricking my phone. I've done much research on downgrading from 4.3 GE firmware to 4.2.2. Sense firmware and I've run into a bit of a wall. I'm getting conflicting advice from the various sources. Some say to downgrade hboot to 1.44 and flash 1.29 firmware. Some say relock the bootloader before doing so. I am not entirely sure on how to progress. I also have read things about the 1.54 GE hboot not working with S-OFF. All in all this makes for a very confusing read. Could someone point me in the right direction or be generous enough to post directions of their attempt?
Thanks again.
I am running 3.06.1700.10 firmware with 4.3 GPe. SuperCID and S-OFF. Model ID is PN0172000

b00f13 said:
Hello all, first time posting on this site. Apologies if I seem like a leecher because my first post happens to be asking for help
I want to make sure I have the right information handy before I attempt anything as I'm afraid of bricking my phone. I've done much research on downgrading from 4.3 GE firmware to 4.2.2. Sense firmware and I've run into a bit of a wall. I'm getting conflicting advice from the various sources. Some say to downgrade hboot to 1.44 and flash 1.29 firmware. Some say relock the bootloader before doing so. I am not entirely sure on how to progress. I also have read things about the 1.54 GE hboot not working with S-OFF. All in all this makes for a very confusing read. Could someone point me in the right direction or be generous enough to post directions of their attempt?
Thanks again.
I am running 3.06.1700.10 firmware with 4.3 GPe. SuperCID and S-OFF. Model ID is PN0172000
Click to expand...
Click to collapse
I am assuming here that your device was originally running Sense and that you flashed the 3.06.1700.10 firmware and a GE 4.3 rom.
If you want to flash a 4.2.2 Sense custom rom then you can do that without reflashing the firmware..... I am running ARHD 12.2 (4.2.2) with the firmware and radio from 3.06.1700.10 and everything is good.
If you wish to reflash a 4.2.2 firmware then you can do this also as you are s-off and supercid..... this is done by exactly the same method used to flash the 3.06.1700.10 firmware.
If your intention is to completely return to stock (firmware and rom) then you will need to find the correct RUU for your device and run that.... search and you will find that there are several threads available explaining how to do that.

rider5512 said:
I am assuming here that your device was originally running Sense and that you flashed the 3.06.1700.10 firmware and a GE 4.3 rom.
If you want to flash a 4.2.2 Sense custom rom then you can do that without reflashing the firmware..... I am running ARHD 12.2 (4.2.2) with the firmware and radio from 3.06.1700.10 and everything is good.
If you wish to reflash a 4.2.2 firmware then you can do this also as you are s-off and supercid..... this is done by exactly the same method used to flash the 3.06.1700.10 firmware.
If your intention is to completely return to stock (firmware and rom) then you will need to find the correct RUU for your device and run that.... search and you will find that there are several threads available explaining how to do that.
Click to expand...
Click to collapse
If I flashed a Sense ROM on top would I still be able to use all the features and apps that are included? My intention was to really just be rid of all that comes with Google Play. I don't mind the radios or firmware.
Another reason is for some reason when I turn my phone off while charging, the charging screen (battery with voltage icon) come on but then stays on. The screen won't turn off like on Nexus devices. Is this a normal feature or a bug? Do you have this too? That's mostly my reason for going back to 4.2.2 firmware.

b00f13 said:
If I flashed a Sense ROM on top would I still be able to use all the features and apps that are included? My intention was to really just be rid of all that comes with Google Play. I don't mind the radios or firmware.
Another reason is for some reason when I turn my phone off while charging, the charging screen (battery with voltage icon) come on but then stays on. The screen won't turn off like on Nexus devices. Is this a normal feature or a bug? Do you have this too? That's mostly my reason for going back to 4.2.2 firmware.
Click to expand...
Click to collapse
You will have to wipe the data on your device before flashing a 4.2.2 rom so you will have to install and setup your apps again but you will have all the included apps in the rom.
The charging icon is a feature of 4.3 but I'm not sure if it should stay on.... I didn't run a 4.3 rom long enough before returning to a sense rom.

rider5512 said:
You will have to wipe the data on your device before flashing a 4.2.2 rom so you will have to install and setup your apps again but you will have all the included apps in the rom.
The charging icon is a feature of 4.3 but I'm not sure if it should stay on.... I didn't run a 4.3 rom long enough before returning to a sense rom.
Click to expand...
Click to collapse
Wasn't sure if that was part of the ROM but I'll try it out. Wouldn't putting a 4.2.2 ROM on top of 4.3 cause some sort of instability? I mean the kernel included is usually meant for 4.2.2.

b00f13 said:
Wasn't sure if that was part of the ROM but I'll try it out. Wouldn't putting a 4.2.2 ROM on top of 4.3 cause some sort of instability? I mean the kernel included is usually meant for 4.2.2.
Click to expand...
Click to collapse
Not if you wipe data..... flashing a 4.2.2 rom will include the kernel

rider5512 said:
Not if you wipe data..... flashing a 4.2.2 rom will include the kernel
Click to expand...
Click to collapse
Final question. Thank you for your help by the way. I could really just flash over the 2.24.401.1 firmware over my current firmware and I wouldn't have to worry about downgrading hboot etc? I could just flash it in fastboot?

[Q] Sort some things out (HTC One)

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?

[Q] Touch Screen Doesn't Work For Some Reason

I root my phone in order to downgrade my HTC One back to Android 4.1.2 Sense 5. I found the perfect ROM which was Guru_Reset_M7_1.26.502.15 from htc1guru. So I installed it but after it booting I couldn't use the touch screen anymore for some reason! I could use the touch screen when I'm in TWRP recovery but not on the ROM itself so I know it's not a hardware issue.
If this helps at all, my phone is running:
TAMPERED
UNLOCKED
S-ON
H-BOOT 1.56.0000
ROOTED (I know because the notifications tell me that it's there, unfortunately I can't access it due to the touch screen problem in the way)
If there's any more information needed just tell me
I REALLY NEED HELP SOMEBODY'S HELP!
I have searched countless forums but most of the time I have no idea what half of them they are talking about. Is it a kernel thing? An S-OFF thing? What could it be?? (I'm still new to this rooting thing)

AndroidHTC2013 said:
I root my phone in order to downgrade my HTC One back to Android 4.1.2 Sense 5. I found the perfect ROM which was Guru_Reset_M7_1.26.502.15 from htc1guru. So I installed it but after it booting I couldn't use the touch screen anymore for some reason! I could use the touch screen when I'm in TWRP recovery but not on the ROM itself so I know it's not a hardware issue.
If this helps at all, my phone is running:
TAMPERED
UNLOCKED
S-ON
H-BOOT 1.56.0000
ROOTED (I know because the notifications tell me that it's there, unfortunately I can't access it due to the touch screen problem in the way)
If there's any more information needed just tell me
I REALLY NEED HELP SOMEBODY'S HELP!
I have searched countless forums but most of the time I have no idea what half of them they are talking about. Is it a kernel thing? An S-OFF thing? What could it be?? (I'm still new to this rooting thing)
Click to expand...
Click to collapse
Read the instructions at the top of the page....
http://www.htc1guru.com/downloads/stock-rom-downloads/

So I would need to re-lock the bootloader and upload the Adnroid 4.1.2 OTA (or is it the current?) onto my phone and it should work?
Is this correct?
Would I really need an OTG cable for this or can I use CMD prompts to do so? ...
And is there anything else I would need to do?
Sorry in advance if I sound like I'm over-thinking it I don't want to screw up my phone

It sounds you loaded a bad touchscreen driver onto your phone with that RUU. TWRP works because it has its own driver. It's possible you've got a later model phone that isn't compatible with the firmware in the RUU.
Why do you want to roll it back so far?

iElvis said:
It sounds you loaded a bad touchscreen driver onto your phone with that RUU. TWRP works because it has its own driver. It's possible you've got a later model phone that isn't compatible with the firmware in the RUU.
Why do you want to roll it back so far?
Click to expand...
Click to collapse
Honestly, I don't like the look of the update/change within the phone. There's nothing great about it except the improved emojis.
A stupid reason? Probably.... but if there's no way to go back without having these big ass problems in the way, then I'll just go back to the current official stock firmware for my phone and learn to live with it

[Q] Finally got round to S-OFF but would like help with next steps please..

Hey all,
I am happy with all things rooting/flashing etc... been doing it for years. Problem is when i change my phone i usually go for a different make thus need to learn all new procedures. I rooted my HTC ONE with no issues, and i have been upgrading my TWRP with flashable zips.... Alas now i need to do more to get phone uptodate with firmwares etc...
Today i finally got round to S-OFF my phone (i am on 1.54 HBOOT) and all is good. I would like to upgrade the firmware and HBOOT to newer ones simply because i feel i need to now. Reason being - i am so many firmwares behind now the new ones have got to improve my phone (Some areas my reception is rubbish if not non existant!!). I need to update my TWRP to 2.7.1.x too as the new Viperone ROM wont install on 2.6.3.3...
So i was going to install https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml the latest file from here - 18.08.2014 6.09.401.5 http://www.androidfilehost.com/?fid=23622183712458599
c650f37bde1ef869ed1218c23047fafb m7_ul TWRP 2.7.1.1 but i wanted to double check that im ok to do so and its the right file??? This i presume from what i have read will update the firmware/radio and latest TWRP with stock HBOOT of 1.57??
Can anyone just clarify if this is right please before i go ahead... If i should do the HBOOT/firmware/twrp all seperate thats fine... just wanted the advice first from more knowledgeable people!!! :good::good::good:
And... if it is right - should i reflash the ROM i am on after or as its a no-wipe it should boot ok??
Im really sorry if its a simple answer. but i just cant get a definitive one from all the threads i have read - plus some mention MID and CID which i was hoping i wouldnt have to touch really if i can help it...
Really do appreciate any help here... sorry for the long post...
ps i am currently running ViperONE 6.2.1 if that makes a difference..