Database Develop

[Q] 4.2.2 Update error, help please

I got OTA 4.2.2 on my ONE, which i bought used, was Relocked & Tempered. But now after Revone, I made it S-ON. During the flashing of OTA, the phone restarts itself once, and second time when the OTA is being flashed, it stops midway with a RED exclamation mark.
I am not getting what could be the problem here
Any suggestions....I did not flash any recovery or anything...

I recommend you to root the phone and update the firmware manually and apply a custom rom... Or make sure to follow the exact steps to go back to stock.
I'm pretty sure there are some missing files hence the update doesn't find the right checksum to proceed with the update.

Have you relocked the bootloader? Worth giving that a try if not
Sent from my HTC One using xda premium

OTAs will usually fail if any system files are missing. If your phone was debloated at any point, even if it's s-on and relocked, that could be enough to stop the OTA from installing.
To flash an OTA, you typically have to be completely stock.

What do you suggest i should do... Right now doing revone method... I am S-on and bootloader is locked...... I want the official OTA... Amy kind suggestions plz
Sent from my HTC One using xda premium

mathrania said:
What do you suggest i should do... Right now doing revone method... I am S-on and bootloader is locked...... I want the official OTA... Amy kind suggestions plz
Click to expand...
Click to collapse
revone will not take you back to stock. You have to run a RUU for your carrier, or flash a fully stock rom if no RUU is available. For the latter, you need to be unlocked, but you can then relock and should be able to apply the OTA.
Edit: sorry, for the latter, you also have to flash the stock recovery in fastboot. You can find that in the firmware threads, though you'll need to pull recovery.img file out of the zip file.

Can some one help me find the correct RUU for me... I have posted the screen shot...
Sent from my HTC One using xda premium

mathrania said:
Can some one help me find the correct RUU for me... I have posted the screen shot...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
There's no RUU for your version.
The 1.28.401.7 is for the HTC One UL variant (or was it the U variant?). Anyway the 1.28.401.7 will have a different MID to yours so you can't use that RUU unless you change your MID.
EDIT:
I found the 1.29.401.16.zip from here http://forum.xda-developers.com/showpost.php?p=43316694&postcount=1157 and use this guide here http://forum.xda-developers.com/showpost.php?p=40734501&postcount=1 to flash it so you should be back to stock.

Rex2369 said:
There's no RUU for your version.
The 1.28.401.7 is for the HTC One UL variant (or was it the U variant?). Anyway the 1.28.401.7 will have a different MID to yours so you can't use that RUU unless you change your MID.
EDIT:
I found the 1.29.401.16.zip from here http://forum.xda-developers.com/showpost.php?p=43316694&postcount=1157 and use this guide here http://forum.xda-developers.com/showpost.php?p=40734501&postcount=1 to flash it so you should be back to stock.
Click to expand...
Click to collapse
I wilk download and try it tomorrow morning..... Thanks for the link...
Sent from my HTC One using xda premium

mathrania said:
I wilk download and try it tomorrow morning..... Thanks for the link...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Do you have TWRP or CWM recovery installed?
If yes that is the problem. To update you need to be on stock recovery.

x017in said:
Do you have TWRP or CWM recovery installed?
If yes that is the problem. To update you need to be on stock recovery.
Click to expand...
Click to collapse
It is a stock recovery what i have..... Because once i entered recovery via bootloader, it showed some stock recovery animations... Phone rebooted, and all was back to factory reset......
Sent from my HTC One using xda premium

Guide - Get s-off on 1.31 HTC One (Sprint) Update:

Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.

Indirect said:
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd if=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Click to expand...
Click to collapse
Flash an ruu.zip or can it be ruu.exe also? Should revone be done after the ruu?
Sent from my PG86100 using xda app-developers app

bleichtman said:
Flash an ruu.zip or can it be ruu.exe also? Should revone be done after the ruu?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
either or and yes. After you RUU.

Indirect said:
either or and yes. After you RUU.
Click to expand...
Click to collapse
Just to be sure cause I'm having issues. This will allow me to flash a 1.29 ruu after having the 1.31 update? This could save me!
Sent from my PG86100 using xda app-developers app

bleichtman said:
Just to be sure cause I'm having issues. This will allow me to flash a 1.29 ruu after having the 1.31 update? This could save me!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes...as it is said in the post.

Indirect said:
Yes...as it is said in the post.
Click to expand...
Click to collapse
Thank you...had a lot of aggravation lately. Sorry for the stupid question.
Sent from my PG86100 using xda app-developers app

So I didn't see this post but did something slightly different and it worked perfect.
Unlocked the bootloader via HTCdev
pushed TWRP for Sprint
Flashed SuperSu
Then followed the revone instructions particularly step 3 su (and going onto the device to grant access.) and everything worked perfect and never had to downgrade from 1.31.
MG

Nice work Indirect good lookin out

Win for Indirect!
Sent from my HTCONE using xda premium

THANK YOU!!!
I owe you!!!

Indirect... you saved many a phones. I have been searching for this and read many a post where people were scrambling (not necessarily for s-off, but the fact that they relocked the bootloader and could not run the 1.29 RUU. I encountered the same thing but just unlocked again and flashed my stock nandroid. Thanks!
If I run just...
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29
Does that leave me with a stock build and s-on? In the event I had to part with the One, etc.

Yes.
Sent from my hidden jewel

Indirect said:
Yes.
Click to expand...
Click to collapse
Kind of related thing happened to me, what do I make of this?
I was S-OFF, but with the newest firmware and custom ROM, TWRP installed.
I did the fastboot oem lock, then RUU'ed back to OMJ's straight up stock Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Once that got booted up I went ahead and did the system update to 1.31.
NOW, when I go into bootloader it says "relocked" up top, but says S-OFF. S-OFF?!? Didn't I relock it and RUU?
Also, when I try to enter recovery, all I get is a phone with a red triangle above it.

FlowingAway said:
Kind of related thing happened to me, what do I make of this?
I was S-OFF, but with the newest firmware and custom ROM, TWRP installed.
I did the fastboot oem lock, then RUU'ed back to OMJ's straight up stock Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Once that got booted up I went ahead and did the system update to 1.31.
NOW, when I go into bootloader it says "relocked" up top, but says S-OFF. S-OFF?!? Didn't I relock it and RUU?
Also, when I try to enter recovery, all I get is a phone with a red triangle above it.
Click to expand...
Click to collapse
When you RUU, it doesn't turn the security back on, hence the S-Off still. However, it does put the stock recovery back on, which is why it has the phone with the red triangle. If you want S-On, you can flash the Stock H-boot, or use Revone to make it say locked instead of relocked and say S-On (I believe it can do that, although I'm not entirely sure.) As for recovery, just re-flash twrp in fastboot.
Edit: "Fastboot OEM lock" doesn't mess with security at all. It just re-locks the bootloader.
Sent from my HTCONE using xda premium

If I am S-on and want a factory recovery, can a stock recovery be flashed in fastboot once back to 1.31?

enmriley said:
If I am S-on and want a factory recovery, can a stock recovery be flashed in fastboot once back to 1.31?
Click to expand...
Click to collapse
Yes.
Sent from my HTCONE using xda premium

plegrand said:
Yes.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Thanks. one more question on this topic. The recovery (or screen) with the red triangle will flag a problem with Sprint right? I assumed the RUU didn't flash the stock recovery when I saw this. I am trying to get around the screen with the red triangle. Will flashing a stock recovery replace this? If not can you provide guidance on doing so after the 1.29 RUU is flashed as described in the OP?

enmriley said:
Thanks. one more question on this topic. The recovery (or screen) with the red triangle will flag a problem with Sprint right? I assumed the RUU didn't flash the stock recovery when I saw this. I am trying to get around the screen with the red triangle. Will flashing a stock recovery replace this? If not can you provide guidance on doing so after the 1.29 RUU is flashed as described in the OP?
Click to expand...
Click to collapse
What? The red triangle means you booted into recovery but something went wrong, either there's no update to flash or something like that. Are you trying to now update to 1.31 after the 1.29 RUU?
Sent from my HTCONE using xda premium

No, I went through the process defined in the OP to return to stock executing a 1.29 RUU. This seemed to work fine. I then received the OTA update to 1.31. After refusing the update several times I accepted it. I didn't go into recovery before accepting the OTA update (not sure that would matter but it would have identified the red triangle apart from the 1.31 uodate) Now when I boot to recovery I get the red triangle where I was expecting to see the stock boot menu.

so i ran the echo command and get seek 1seek64 failed am i in the clear to flash the ruu or what should i do kind of scared to move away from recovery
it worked xD thanks dude

flashe international revolution ROM on my sprint htc one.

i was rooted with s-on on 4.1.2 when i tried flashing the 4.2.2 revolution ROM, im now stuck in bootloader and cant reboot, factory reset, go into recovery or even power off. My image version is now 1.31.651.2. please help. Big time NOOB here.

evoshift617 said:
i was rooted with s-on on 4.1.2 when i tried flashing the 4.2.2 revolution ROM, im now stuck in bootloader and cant reboot, factory reset, go into recovery or even power off. My image version is now 1.31.651.2. please help. Big time NOOB here.
Click to expand...
Click to collapse
Don't panic, search and download the HTC one tool and install one of sprints costum recoveries while in boot loader

spottarget said:
Don't panic, search and download the HTC one tool and install one of sprints costum recoveries while in boot loader
Click to expand...
Click to collapse
Not going to work. If you flash an international ROM you hose your storage partitions. Generally the only way to recover from this is via an RUU, but I'm guessing the user is S-ON so they'll have to wait for an updated RUU to turn up.

Need to try to get s-off, which will allow you to flash older ruu. Also I suggest in the future you read OP of any Rom you want to flash to make sure it's compatible with sprint
Sent from my HTCONE using Tapatalk 4

it works on mine
Rirere said:
Not going to work. If you flash an international ROM you hose your storage partitions. Generally the only way to recover from this is via an RUU, but I'm guessing the user is S-ON so they'll have to wait for an updated RUU to turn up.
Click to expand...
Click to collapse
i have flashe internatinal rom trying to fix my gsm signal on my unlocked sprint htc one with no luck and the same has happened so ive fixed it by flashing recovery with the one click too or by using adb. Im s-off and unlocked though

same thing
I did the exact same thing. Flashed the revolution rom and selected the international version of it because it said that one applies to all carriers not listed below. stupid thing to overlook on my part. at first after doing so I was unable to get into my recovery then i used fastboot erase cache and once i did that I was able to fastboot flash the recovery image and navigate into it from the bootloader. ive tried everything i could think of once in my recovery, which is a version of cwm btw. Ive formatted data, erased cache and delvik, after that i tried installing my cyanogen 10.1 zip which i was successfully running without any problems for a day before i got greedy and tried to flash that international rom :crying: i made a backup of that working one but regardless of what I try doing whether it be restoring the back up that was working properly or re installing the cyan zip, every time it starts booting for about 30 secs then crashes reboots and tries again. it continues this loop for eternity and theres nothing i can do.looks like somebody said i messed up my internal storage partitions and im sol until a new ruu update comes out. I would greatly appreciate if someone would elaborate on that or point me in the direction of a good place to do some research on it. my bootloader says tampered, unlocked, s-on. there was also somebody that said try to get s-off and flash and older ruu. is this a possible fix?? i dont care how hard it is ill figure it out but right now im hurting for some help or direction. i appreciate any help. thanks

Can i
Sent from my SPH-L710 using xda app-developers app

Can i get s off using Adb on my pc.
Sent from my SPH-L710 using xda app-developers app

evoshift617 said:
Can i get s off using Adb on my pc.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582

s-off
krazyflipj said:
http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
Just ruu back to stock rom then s-off

spottarget said:
Just ruu back to stock rom then s-off
Click to expand...
Click to collapse
S-off then ruu
Sent from my HTCONE using Tapatalk 4

krazyflipj said:
S-off then ruu
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
I cant, it only stays on bootloeader and pc won't read the phone. Am I hard bricked?
Sent from my HTCONE using Tapatalk 2

Rirere said:
Not going to work. If you flash an international ROM you hose your storage partitions. Generally the only way to recover from this is via an RUU, but I'm guessing the user is S-ON so they'll have to wait for an updated RUU to turn up.
Click to expand...
Click to collapse
Any updated RUUs that u know of yet in order to fix my phone?
Sent from my HTCONE using Tapatalk 2

evoshift617 said:
I cant, it only stays on bootloeader and pc won't read the phone. Am I hard bricked?
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Are you trying this in fastboot? If you are just in the bootloader then the computer won't detect anything, but if you're in fastboot mode your computer should at least register an unknown device. And I don't think there are any 4.3 RUU's yet either...

You need to RUU, try this and see if it works. http://forum.xda-developers.com/showthread.php?p=44243635
You might be screwed in till there is an updated RUU.
Sent from my HTCONE using xda app-developers app

[Q] How to downgrade HTC One Developer Edition (US) from firmware 1.29.1540.17 to 1.2

Hello,
I have been researching here to find a way to downgrade to a previous version of a firmware so that I can S-Off, and to no avail unsure how to do it myself using either use Moonshine or revone.
The reason I wish to do this is that I want to install Google Play edition and of course the necessary info to install it.
Sent from my HTC One using xda premium

EvilSpants said:
Hello,
I have been researching here to find a way to downgrade to a previous version of a firmware so that I can S-Off, and to no avail unsure how to do it myself using either use Moonshine or revone.
The reason I wish to do this is that I want to install Google Play edition and of course the necessary info to install it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
If I'm not mistaken the ROM firmware is irrelevant as to if you can root or not, or get-S-OFF. The most important factor for S-OFF is the bootloader version. I haven't seen any threads about getting S-OFF on bootloader 1.54.
Reboot to your bootloader (turn device off, hold volume down and turn device on). Check your HBOOT version there. If it says 1.54, then the only possible solution is to search for an official HTC RUU with a lower HBOOT version. However I do not know if this will actually work.

RadiatorRXD said:
If I'm not mistaken the ROM firmware is irrelevant as to if you can root or not, or get-S-OFF. The most important factor for S-OFF is the bootloader version. I haven't seen any threads about getting S-OFF on bootloader 1.54.
Reboot to your bootloader (turn device off, hold volume down and turn device on). Check your HBOOT version there. If it says 1.54, then the only possible solution is to search for an official HTC RUU with a lower HBOOT version. However I do not know if this will actually work.
Click to expand...
Click to collapse
Alright. Assuming that works, is there a way to reflash?
[Edit] Just checked my bootloader it says that I have 1.44. However I have tried both Revone and S-off with no success
Sent from my HTC One using xda premium

EvilSpants said:
Alright. Assuming that works, is there a way to reflash?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Don't really know what you mean by reflash? Returning to the newer HBOOT (1.54)?
If that's the case, once you're S-OFF you can update the HBOOT to 1.54 and S-OFF will still be there. There are some threads in the development section about upgrading the HBOOT. I used these myself without issues.
As for the official RUU, this will probably be a Google search. I haven't seen a thread around with these files.
Keep in mind that flashing an original RUU will result in loss of root and custom recovery. You will need to re-root after flashing the RUU and reflash a custom recovery.

RadiatorRXD said:
Don't really know what you mean by reflash? Returning to the newer HBOOT (1.54)?
If that's the case, once you're S-OFF you can update the HBOOT to 1.54 and S-OFF will still be there. There are some threads in the development section about upgrading the HBOOT. I used these myself without issues.
As for the official RUU, this will probably be a Google search. I haven't seen a thread around with these files.
Keep in mind that flashing an original RUU will result in loss of root and custom recovery. You will need to re-root after flashing the RUU and reflash a custom recovery.
Click to expand...
Click to collapse
A little bit off topic here but ..if I am s- off already and I were to use a stock ruu on my phone all that I will I loose is the recovery and root?... So after I run ruu my device will still be s-off ?
Sent from my HTC One using xda premium

NORCALkID said:
A little bit off topic here but ..if I am s- off already and I were to use a stock ruu on my phone all that I will I loose is the recovery and root?... So after I run ruu my device will still be s-off ?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I think so yes, but I'm not 100% sure. You may find the answer, or ask the question in the hboot update threads or s-off threads. I haven't flashed a RUU myself in years.
Sent from my Viper One

RadiatorRXD said:
Don't really know what you mean by reflash? Returning to the newer HBOOT (1.54)?
If that's the case, once you're S-OFF you can update the HBOOT to 1.54 and S-OFF will still be there. There are some threads in the development section about upgrading the HBOOT. I used these myself without issues.
As for the official RUU, this will probably be a Google search. I haven't seen a thread around with these files.
Keep in mind that flashing an original RUU will result in loss of root and custom recovery. You will need to re-root after flashing the RUU and reflash a custom recovery.
Click to expand...
Click to collapse
What I mean to say is that once I have found one with an older HBoot, how do I go about flashing that so that I can do one of the two S-Off procedures?
Sent from my HTC One using xda premium

EvilSpants said:
What I mean to say is that once I have found one with an older HBoot, how do I go about flashing that so that I can do one of the two S-Off procedures?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Ah ok. The RUU should be a windows executable. Just hook up the phone to computer, start the RUU and follow the on-screen instructions.
Sent from my Viper One

RadiatorRXD said:
Ah ok. The RUU should be a windows executable. Just hook up the phone to computer, start the RUU and follow the on-screen instructions.
Sent from my Viper One
Click to expand...
Click to collapse
I assume the RUUs can be pulled from HTCdev?
Sent from my HTC One using xda premium

EvilSpants said:
I assume the RUUs can be pulled from HTCdev?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Here's an article about flashing a RUU: Flash RUU
It has a link to a website which contains several RUU files to download: HERE

RadiatorRXD said:
If I'm not mistaken the ROM firmware is irrelevant as to if you can root or not, or get-S-OFF. The most important factor for S-OFF is the bootloader version. I haven't seen any threads about getting S-OFF on bootloader 1.54.
Reboot to your bootloader (turn device off, hold volume down and turn device on). Check your HBOOT version there. If it says 1.54, then the only possible solution is to search for an official HTC RUU with a lower HBOOT version. However I do not know if this will actually work.
Click to expand...
Click to collapse
I was s-off with stock unrooted locked 2.24.401.1 firmware (ruu'ed by repair center)and tried to use revone to unlock again but it would fail, then I downgraded to hboot 1.44 (I could still do this because I was s-off already) but revone would still fail, then I decided to properly downgrade to 1.28(or was that 29).401.?? with an ruu and was able to use revone again to unlock my bootloader, so hboot is not the only factor for revone to be succesful...
downgrading hboot and other system partitions, except kernel rom radio and recovery, is not possible if you are not s-off already....

RadiatorRXD said:
Ah ok. The RUU should be a windows executable. Just hook up the phone to computer, start the RUU and follow the on-screen instructions.
Sent from my Viper One
Click to expand...
Click to collapse
My downgrade attempt failed with one of the executables. I am not sure what to try next.

EvilSpants said:
My downgrade attempt failed with one of the executables. I am not sure what to try next.
Click to expand...
Click to collapse
I'm at a loss here, sorry.
Sent from my Viper One

RadiatorRXD said:
I'm at a loss here, sorry.
Sent from my Viper One
Click to expand...
Click to collapse
I should note that I did not retry, however I figure that if it fails the first time, then it wouldn't succeed a second?
Sent from my HTC One using xda premium

EvilSpants said:
I should note that I did not retry, however I figure that if it fails the first time, then it wouldn't succeed a second?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
You could always try a second time. Maybe also post a screenshot of the failure.
Sent from my Viper One

RadiatorRXD said:
You could always try a second time. Maybe also post a screenshot of the failure.
Sent from my Viper One
Click to expand...
Click to collapse
At this point I am looking at installing a custom recovery, though from what I am reading I may not be able to do that without S-OFF, so I am stuck if this is true.
Sent from my HTC One using xda premium

EvilSpants said:
At this point I am looking at installing a custom recovery, though from what I am reading I may not be able to do that without S-OFF, so I am stuck if this is true.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
S-OFF is not needed for root or custom recovery. You do need an unlocked bootloader though. On other devices S-OFF was needed to flash radio's or kernels through recovery, but from what I have read the One can flash kernels in recovery without S-OFF
Sent from my Viper One

RadiatorRXD said:
S-OFF is not needed for root or custom recovery. You do need an unlocked bootloader though. On other devices S-OFF was needed to flash radio's or kernels through recovery, but from what I have read the One can flash kernels in recovery without S-OFF
Sent from my Viper One
Click to expand...
Click to collapse
So I have gotten TWRP on there, however I have been unable to flash a previous firmware, to downgrade, getting the error message, Unable to open zip. My guess is that S-On is stopping this process even in a custom recovery. Is there a recommendation as to how I can achieve S-Off?
Also There is something I have been thinking about it, and if I were to follow the steps here, with execption of the flashing the RUU through fasboot, could I flash the RUU through TWRP instead?
[Edit] Could I install a custom ROM, S-Off through the ROM, then follow the steps in the link to flash the RUU?

[Q] Downgrade hboot prior to sending phone for service?

I have read on various threads that when you send your phone for service, it typically comes back with latest firmware, and as a result, latest hboot 1.56. Would the device be considered for repair under warrenty if it is completely stock, s-on, latest firmware, but older hboot? This way the device firmware might not be upgraded during service and being on a lower hboot might make it easier to obtain s-off post service. Thoughts?

b99721 said:
I have read on various threads that when you send your phone for service, it typically comes back with latest firmware, and as a result, latest hboot 1.56. Would the device be considered for repair under warrenty if it is completely stock, s-on, latest firmware, but older hboot? This way the device firmware might not be upgraded during service and being on a lower hboot might make it easier to obtain s-off post service. Thoughts?
Click to expand...
Click to collapse
if everything is up to date except the hboot, they will know you have tampered the phone and your warranty will not be valid.

Ok get it. Thanks.
Now can someone please point me to the source for hboot 1.56 (I am on 4.19.1540.9, but had flashed hboot 1.44 and need to revert to original hboot version). I am looking for only hboot and not complete ruu (dont hv bandwidth to download ruu). Quick response would really really help.
Sent from my HTC One using Tapatalk

https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
You need the original unmodified.. these are GSM Only. By the way, does your bootloader say tampered, locked/relocked or does it just say locked.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
You need the original unmodified.. these are GSM Only. By the way, does your bootloader say tampered, locked/relocked or does it just say locked.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks!
My bootloader says unlocked - I had locked it day before yesterday (at that time it said Locked) but I have unlocked it again now so it says Unlocked. And am s-off. Mine is single sim gsm only phone and firmware is 4.19.1540.9. So which hboot to download? Will hboot for version 4.19.401.9 work on my device and be considered stock for it by service center?
Sent from my HTC One using Tapatalk

That will work ok, But... That's not the answer.. in order to return for warranty.. You phone has to be locked not relocked. Have tampered removed. Stock recovery. In other words out of the box software..
Take a look here
http://forum.xda-developers.com/showthread.php?t=2541082
Do not under any circumstances go S-On yet..
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
That will work ok, But... That's not the answer.. in order to return for warranty.. You phone has to be locked not relocked. Have tampered removed. Stock recovery. In other words out of the box software..
Take a look here
http://forum.xda-developers.com/showthread.php?t=2541082
Do not under any circumstances go S-On yet..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure I will install stock recovery and do Lock (not relock). Thanks again!
I can unroot after Locked? From the super user app itself?
I plan to follow steps:
1) flash hboot 1.56
2) flash stock recovery
3) get Locked
4) unroot from app
5) factory reset
6) get s-on
Sent from my HTC One using Tapatalk

b99721 said:
Sure I will install stock recovery and do Lock (not relock). Thanks again!
I can unroot after Locked? From the super user app itself?
I plan to follow steps:
1) flash hboot 1.56
2) flash stock recovery
3) get Locked
4) unroot from app
5) factory reset
6) get s-on
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Be careful with hboot 1 56.
If you go S-On. You may not be able to go S-Off again. Also make sure if you go S-On to do so before Ota 3.**.***.*.
Quote" Step 3: if YOU decide to go S-On*(Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55" End Quote. Thank you @nkk71
Though I see no reason to take OTA updates all the way to hboot1.55/1.56.
Not everyone I imagine wants to be on the latest firmware.
Has long as it's fully stock , HTC will honour the Warranty.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Be careful with hboot 1 56.
If you go S-On. You may not be able to go S-Off again. Also make sure if you go S-On to do so before Ota 3.**.***.*.
Quote" Step 3: if YOU decide to go S-On*(Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55" End Quote. Thank you @nkk71
Though I see no reason to take OTA updates all the way to hboot1.55/1.56.
Not everyone I imagine wants to be on the latest firmware.
Has long as it's fully stock , HTC will honour the Warranty.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you are suggesting I first downgrade and then achieve s-on? I am ok with no s-off. Getting warranty is more important for me at this point. I want to be on the latest firmware. So if I go s-on with hboot 1.56, I will be in a fix? In that case can I s-on with present hboot 1.44 and then flash hboot 1.56? Or it will not be possible since i would be s-on?
Sent from my HTC One using Tapatalk

bored_stupid said:
That will work ok, But... That's not the answer.. in order to return for warranty.. You phone has to be locked not relocked. Have tampered removed. Stock recovery. In other words out of the box software..
Take a look here
http://forum.xda-developers.com/showthread.php?t=2541082
Do not under any circumstances go S-On yet..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The hboot file didn't work. So I extracted it from the OTA file I had with me for 4.19.1540.9 and replaced the hboot img file in the zip I had for hboot 1.44. Worked!
But it was scary - I executed fasboot flash zip command and the progress bar n the phone was stuck around 75% but cmd returned OK. So as per instructions on htc1guru, I executed the command again and the status bar didn't move but again cmd said OK. Finally turned off the phone by holding down power button and prayed and turned it on. Phone booted with hboot 1.56!
PS: Exactly same thing had happened when I had downgraded to hboot 1.44
Sent from my HTC One using Tapatalk

Sorry should have mentioned that. It goes like this..
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip hboot.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:
fastboot flash zip hboot.zip
The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:
fastboot reboot
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Sorry should have mentioned that. It goes like this..
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip hboot.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:
fastboot flash zip hboot.zip
The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:
fastboot reboot
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the instructions! My phone has left country now! Will save one way courier money and hopefully get in warranty service - sent with s-off, but Locked.

b99721 said:
Thanks for the instructions! My phone has left country now! Will save one way courier money and hopefully get in warranty service - sent with s-off, but Locked.
Click to expand...
Click to collapse
Hope all goes well.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Hope all goes well.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got my One back! Camera is awesome now. Low light, normal light, sunlight... every situation the camera excels.
Sensor is ov6488, no date.
Only thing that that is bugging me, but I can live with it - using flash results in a very light green hue on the entire photograph. But I rarely use flash.
And the camera lens (and the flash module) are a little off-center from glass at the back, but it seems to have no effect on the photos, so I am fine (but just a little annoyed) with it.
At the same time, I want to confirm a couple of things -
1) Does this sensor have OIS - had read somewhere it is same sensor as the one used in M8, which doesn't have OIS
2) The photos appear distorted towards the ends/edges - a characteristic of the wide angle lense I understand - but with the prior sensor, when I use to set Crop as Regular, the photos use to get straight at ends/edges; but that is not the case anymore - no matter what Crop I select - Wide, Regular, and Square, photos are distorted/wide at ends/edges. Hope this is the way it is suppose to be.
Sent from my HTC One using Tapatalk