Hey guys,
I got my One back from repair today. Before I gave it to the shop it was S-ON and hboot 1.44. Now it's S-OFF and hboot 1.55!
I read that a few things are different for hboot 1.55. Can anybody tell me, what's different now regarded to flashing ROMs etc.
Is it possible to revert back to hboot 1.55? Is this necessary at all? Are there disadvantages with hboot 1.55?
I hope somebody can help me with some answers.
Thank you very much in advance!
Greets kally
kally said:
Hey guys,
I got my One back from repair today. Before I gave it to the shop it was S-ON and hboot 1.44. Now it's S-OFF and hboot 1.55!
I read that a few things are different for hboot 1.55. Can anybody tell me, what's different now regarded to flashing ROMs etc.
Is it possible to revert back to hboot 1.55? Is this necessary at all? Are there disadvantages with hboot 1.55?
I hope somebody can help me with some answers.
Thank you very much in advance!
Greets kally
Click to expand...
Click to collapse
Unless you want to reset your device to 100% stock with a lower version ruu.exe there is no reason to downgrade hboot back to 1.44. Yes its possible to downgrade hboot but it will require you to s-off the device first using rumrunner tool or firewater tool. nvm already s-off
kally said:
Hey guys,
I got my One back from repair today. Before I gave it to the shop it was S-ON and hboot 1.44. Now it's S-OFF and hboot 1.55!
I read that a few things are different for hboot 1.55. Can anybody tell me, what's different now regarded to flashing ROMs etc.
Is it possible to revert back to hboot 1.55? Is this necessary at all? Are there disadvantages with hboot 1.55?
I hope somebody can help me with some answers.
Thank you very much in advance!
Greets kally
Click to expand...
Click to collapse
does it says UNLOCKED?
wow it's great news that you got S-OFF after repair
and you should stay S-OFF; for flashing desired firmwares and vice versa
any hboot is fine (for Win8.1 you need to be on 1.55+ for fastboot to see your phone), other than that, just keep the hboot that comes with the firmware.
kally said:
Now it's S-OFF and hboot 1.55!
Click to expand...
Click to collapse
What's the obsession with hboot it get's updated with firmware updates that's all
Are there disadvantages with hboot 1.55?
Click to expand...
Click to collapse
-> Yes :silly:, it works with Win8.1 :silly:
(hboot 1.44 doesn't)
Thank for the answers!
kamilmirza said:
does it says UNLOCKED?
wow it's great news that you got S-OFF after repair
and you should stay S-OFF; for flashing desired firmwares and vice versa
any hboot is fine (for Win8.1 you need to be on 1.55+ for fastboot to see your phone), other than that, just keep the hboot that comes with the firmware.
Click to expand...
Click to collapse
No, it's locked
I tested my phone and realized, that the failure still exists!
Should I make it S-ON again or can I send it back to the shop with S-OFF because they gave it me with S-OFF?
kally
kally said:
Thank for the answers!
No, it's locked
I tested my phone and realized, that the failure still exists!
Should I make it S-ON again or can I send it back to the shop with S-OFF because they gave it me with S-OFF?
kally
Click to expand...
Click to collapse
What sort of failures are you experiencing, ( are they hardware or software failures ). Stay S-Off.. it's a 99% guarantee of getting out of trouble.
Sent from my HTC One using XDA Premium HD app
bored_stupid said:
What sort of failures are you experiencing, ( are they hardware or software failures ). Stay S-Off.. it's a 99% guarantee of getting out of trouble.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
It's hardware related (earphone issue).
kally said:
It's hardware related (earphone issue).
Click to expand...
Click to collapse
Then return it for repair, no need to s-on, but inform them the hardware problem still remains..
Sent from my HTC One using XDA Premium HD app
Related
Please help me, i really need to downgrade hboot 1.54 to 1.44 with s-on?
I would really approciate any idea
Not possible
and is there any way to install PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip ? i'm trying to install this rom by using fastboot, but when it's checking HBOOT, it says error wrong bootloader required 1.44.00..., but i've got 1.54 at this time
way how to install this RUU or different one for international device without error caused by wrong HBOOT version?
Spartn said:
and is there any way to install PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio _4A.14.3250.13_10.33.1150.01_release_318486_signed _2_4.zip ? i'm trying to install this rom by using fastboot, but when it's checking HBOOT, it says error wrong bootloader required 1.44.00..., but i've got 1.54 at this time
way how to install this RUU or different one for international device without error caused by wrong HBOOT version?
Click to expand...
Click to collapse
Nope, not possible unless you have S-Off.
i wish i had known that security is better to leave off
thanks guys i think i just have to wait for s off which will work on new hboot 1.54..
will flashing stock ruu work to downgrade hboot?
djcoolguyno1 said:
will flashing stock ruu work to downgrade hboot?
Click to expand...
Click to collapse
That has been answered here already - no
EddyOS said:
That has been answered here already - no
Click to expand...
Click to collapse
How did you get s-off on 1.54?
sopaj96 said:
How did you get s-off on 1.54?
Click to expand...
Click to collapse
He probably got while still on hboot 1.44 (pre June 2013), and then just upgraded the firmware (including hboot to 1.54), that would not change S-Off status.
nkk71 said:
He probably got while still on hboot 1.44 (pre June 2013), and then just upgraded the firmware (including hboot to 1.54), that would not change S-Off status.
Click to expand...
Click to collapse
Exactly that ^
bobs ur uncle, fanny's ur aunt etc..........................
I guess it would be a good idea to post some pointers regarding this issue.
If you're s-on and on fw 1.54, you can't use revone to s-off.
Since you can't s-off, you are limited to flashing only RUUs that are compatible with your CID AND same or higher fw than you currently have on your device.
So to sum it all up, if you are on a higher fw than 1.44 and s-on, you are stuck there. The only possible way to s-off might be using a java card but I personally wouldn't go that way, even if you found some place that can do it.
makbil said:
So to sum it all up, if you are on a higher fw than 1.44 and s-on, you are stuck there.
Click to expand...
Click to collapse
So if going from 1.55 back to 1.44 is not possible. And Getting S-OFF with 1.55 is not possible.
Would Sprint be able to reflash my phone with either a working 1.55 or 1.44?
Spartn said:
Please help me, i really need to downgrade hboot 1.54 to 1.44 with s-on?
I would really approciate any idea
Click to expand...
Click to collapse
Try to s-off your phone with hboot 1.54 using rumrunner.
Dears,
i am currently on firmware version 2.24.401.1 and would like to revert back to 1.29.401.16 (bootloader 1.44.0000).. can please someone help me to find where can i download this firmware ?
thanks a lot in advance
zeekabal said:
Dears,
i am currently on firmware version 2.24.401.1 and would like to revert back to 1.29.401.16 (bootloader 1.44.0000).. can please someone help me to find where can i download this firmware ?
thanks a lot in advance
Click to expand...
Click to collapse
You can`t downgrade the Hboot unless you are S-Off.
It is S-ON but bootloader is unlocked using www.htvdev.com
Shall i still S-Off ?
Sent from my LT26ii using xda app-developers app
zeekabal said:
It is S-ON but bootloader is unlocked using www.htvdev.com
Shall i still S-Off ?
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
If you have the 1.54 HBOOT already, then the consensus is that you can't S-OFF. 1.54 most likely blocked the current methods of getting S-OFF.
Even if you RUU back to 1.29.401.16, the HBOOT wouldn't change. It's a one way deal if you didn't S-OFF on 1.44 HBOOT.
cee43ja1 said:
If you have the 1.54 HBOOT already, then the consensus is that you can't S-OFF. 1.54 most likely blocked the current methods of getting S-OFF.
Even if you RUU back to 1.29.401.16, the HBOOT wouldn't change. It's a one way deal if you didn't S-OFF on 1.44 HBOOT.
Click to expand...
Click to collapse
then how can I make use of my phone again
how can i flash a .zip ROM if my phone is not mounting the sdcard
Hello everyone,
my phone statement is;
1.54 hboot, S-ON, HTC Unlocked, 2.24.401.x FW.
I just found local service in my city for s-off on 1.54 hboot via javacard. I will use that service. And i have questions:
after getting s-off on 1.54;
- How can i downgrade hboot to 1.44? RUU is enough for this?
- Is there a any other method?
- Is Nandroid backups contain hboot part?
- Can i write super CID on 1.54 S-OFF?
- Can i delete "Tempered" flag when i gain s-off on hboot 1.54?
Thank you,
ShdwFx said:
Hello everyone,
my phone statement is;
1.54 hboot, S-ON, HTC Unlocked, 2.24.401.x FW.
I just found local service in my city for s-off on 1.54 hboot via javacard. I will use that service. And i have questions:
after getting s-off on 1.54;
- How can i downgrade hboot to 1.44? RUU is enough for this?
- Is there a any other method?
- Is Nandroid backups contain hboot part?
- Can i write super CID on 1.54 S-OFF?
- Can i delete "Tempered" flag when i gain s-off on hboot 1.54?
Thank you,
Click to expand...
Click to collapse
- How can i downgrade hboot to 1.44? RUU is enough for this? (A 1.29.x or any RUU with hboot 1.44 will suffice)
- Is there a any other method? (You can flash a 1.44 hboot manually without any RUU)
- Is Nandroid backups contain hboot part? (No)
- Can i write super CID on 1.54 S-OFF? (Yes)
- Can i delete "Tempered" flag when i gain s-off on hboot 1.54? (Yes with revone if it works)
ShdwFx said:
Hello everyone,
my phone statement is;
1.54 hboot, S-ON, HTC Unlocked, 2.24.401.x FW.
I just found local service in my city for s-off on 1.54 hboot via javacard. I will use that service. And i have questions:
after getting s-off on 1.54;
- How can i downgrade hboot to 1.44? RUU is enough for this?
- Is there a any other method?
- Is Nandroid backups contain hboot part?
- Can i write super CID on 1.54 S-OFF?
- Can i delete "Tempered" flag when i gain s-off on hboot 1.54?
Thank you,
Click to expand...
Click to collapse
If you are getting s-off why would you want to go back to 1.44 hboot?
i want back to stock completly. i ll comeback 1.54 via OTA.
ShdwFx said:
Hello everyone,
my phone statement is;
1.54 hboot, S-ON, HTC Unlocked, 2.24.401.x FW.
I just found local service in my city for s-off on 1.54 hboot via javacard. I will use that service. And i have questions:
after getting s-off on 1.54;
- How can i downgrade hboot to 1.44? RUU is enough for this?
- Is there a any other method?
- Is Nandroid backups contain hboot part?
- Can i write super CID on 1.54 S-OFF?
- Can i delete "Tempered" flag when i gain s-off on hboot 1.54?
Thank you,
Click to expand...
Click to collapse
Well to start off at the moment you can't s-off on hboot 1.54 at the moment that is after it is available till would be able to flash any hboot so you would be able to go completely stock
Sent from inside the T.A.R.D.I.S
joselv456 said:
Well to start off at the moment you can't s-off on hboot 1.54 at the moment that is after it is available till would be able to flash any hboot so you would be able to go completely stock
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
You can with the java card method
ShdwFx said:
i want back to stock completly. i ll comeback 1.54 via OTA.
Click to expand...
Click to collapse
So you're going to pay for S-Off and then intentionally get rid of S-Off, and then upgrade, preventing you from gaining S-Off without paying again?
You know, it's probably best to leave it S-Off.
The OTA doesn't remove S-OFF, I went from 1.44 to 1.54 with no issues
EddyOS said:
The OTA doesn't remove S-OFF, I went from 1.44 to 1.54 with no issues
Click to expand...
Click to collapse
Whoops, I somehow read that he wanted to revert to S-On.
daleski75 said:
- Is there a any other method? (You can flash a 1.44 hboot manually without any RUU)
Click to expand...
Click to collapse
Please could you post a link showing where this is possible because for the life of me, I cannot find one.
Sent from my HTC One using XDA Premium 4 mobile app
Gavilaaar said:
Please could you post a link showing where this is possible because for the life of me, I cannot find one.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once the OP pays the shop to S-OFF the phone on 1.54 using the java card method he can use any RUU to go back
EddyOS said:
You can with the java card method
Click to expand...
Click to collapse
Hope he has a lot of money cause that is expensive ive hears
Sent from inside the T.A.R.D.I.S
Gavilaaar said:
Please could you post a link showing where this is possible because for the life of me, I cannot find one.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2316726
All firmwares available in this thread
Sent from my HTC One using xda app-developers app
Hello everyone,
I have several issues with my HTC One and so I've got to send it to HTC. But for this I have to reset it back to stock so I have the right to claim warranty. Now I proceeded every step from using a RUU and setting the locked state to installing every OTA update. But now the only thing that has to be removed is the S OFF. I heard that you can instantly brick your device if you "fastboot writesecureflag 3" and you have a custom hboot. So now I have the stock hboot 1.55 recieved OTA. Is it secure the turn my phone back S ON? Or do I have to downgrade the hboot 1.44?
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
really? It would just.. be ... f***ing awesome And if they say s off voided my warranty i'm gonna punch them... thanks..
And is it true that some devices are shipped s off by mistake?
LibertyMarine said:
really? It would just.. be ... f***ing awesome And if they say s off voided my warranty i'm gonna punch them... thanks..
And is it true that some devices are shipped s off by mistake?
Click to expand...
Click to collapse
Yeah its true.. keep in mind your warranty can still be voided by requesting an unlock token from HTCDev
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Yeah its true.. keep in mind your warranty can still be voided by requesting an unlock token from HTCDev
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I know but they don't have any evidences that I used the unlock_code.bin so I think i am on the safe side... At least I hope so...
altimax98 said:
Don't go S-On. S-Off won't void your warranty
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
why not go son？
Sent from my HTC One using Tapatalk 2
dingnangen said:
why not go son？
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
stovie_steve said:
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
Click to expand...
Click to collapse
hmm.. that's crappy... do you know a thread where this particular problem is mentioned? I searched for it.. but didn't find anything
LibertyMarine said:
hmm.. that's crappy... do you know a thread where this particular problem is mentioned? I searched for it.. but didn't find anything
Click to expand...
Click to collapse
It's happened with myself despite being completely stock and to someone else in an earlier thread today
Only way I could bypass this was by basically starting from hboot 1.44 and then installing an RUU before going s on, then taking the ota s right up to the latest hboot
stovie_steve said:
It's happened with myself despite being completely stock and to someone else in an earlier thread today
Only way I could bypass this was by basically starting from hboot 1.44 and then installing an RUU before going s on, then taking the ota s right up to the latest hboot
Click to expand...
Click to collapse
So this basically means you locked and untampered your phone after installing the RUU? And another question: Did you also flash this stock hboot before installing the RUU?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
But I decided not to go back s on because they won't void my warranty for that and if they say that will void it, I am gonna argue with them until they accept the only fair option: SOFWARE MODIFICATION CAN'T CAUSE ANY HARDWARE DAMAGE except overclocking can melt your phone^^
LibertyMarine said:
So this basically means you locked and untampered your phone after installing the RUU? And another question: Did you also flash this stock hboot before installing the RUU?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
But I decided not to go back s on because they won't void my warranty for that and if they say that will void it, I am gonna argue with them until they accept the only fair option: SOFWARE MODIFICATION CAN'T CAUSE ANY HARDWARE DAMAGE except overclocking can melt your phone^^
Click to expand...
Click to collapse
This is how I did it
http://forum.xda-developers.com/showthread.php?t=2519259
My method was for a carrier branded phone (o2 UK) but this guide can be changed to suit unbranded phones. The problem I had, as well as others, was getting back to s on and once writesecureflag 3 was performed on hboot 1.55 tamper was detected. Guess it may be a patch in latest hboot. I had to go s on with hboot 1.54 or earlier and then upgrade to hboot 1.55 via ota once I was happy everything was stock
stovie_steve said:
Don't go S-On with hboot 1.55 - A few users have reported the ***TAMPER*** returning to the bootloader screen even with the bootloader Locked
Don't know if they patched something in the latest hboot. Only way around it was to go S-ON in hboot 1.54 and then receive the OTA
Click to expand...
Click to collapse
my phone is son unlock with hb1.54 now,i want to go soff using RumRunner ,then flash 4.1 ruu and back to 100% stock(s-on) using revone for warranty,can i get soff Using revone again?
dingnangen said:
my phone is son unlock with hb1.54 now,i want to go soff using RumRunner ,then flash 4.1 ruu and back to 100% stock(s-on) using revone for warranty,can i get soff Using revone again?
Click to expand...
Click to collapse
As long as your using it on a downgraded hboot ie 1.44. Rumrunner will only work on hboot 1.5x
To run the 4.1 RUU you will have to downgrade the hboot or it will give error 155
stovie_steve said:
This is how I did it
http://forum.xda-developers.com/showthread.php?t=2519259
My method was for a carrier branded phone (o2 UK) but this guide can be changed to suit unbranded phones. The problem I had, as well as others, was getting back to s on and once writesecureflag 3 was performed on hboot 1.55 tamper was detected. Guess it may be a patch in latest hboot. I had to go s on with hboot 1.54 or earlier and then upgrade to hboot 1.55 via ota once I was happy everything was stock
Click to expand...
Click to collapse
Sorry that this question seams to be very simple.. but did you go s on with this version of bootloader?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Because I really don't want to risk anything by going s on again..
Or did you go s on again with the 1.54 hboot from the OTA?
LibertyMarine said:
Sorry that this question seams to be very simple.. but did you go s on with this version of bootloader?
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
Because I really don't want to risk anything by going s on again..
Or did you go s on again with the 1.54 hboot from the OTA?
Click to expand...
Click to collapse
When I ran the RUU after downgrading the hboot I was on android 4.1.2 and hboot 1.44
I restored a nandroid backup then for my o2 carrier. Although the recovery was stock, it wasn't 100% stock for my carrier. I knew this would be fixed with the OTA so that's why I went s on then with hboot 1.54 as EVERYTHING was stock
If you are going to an unbranded model, you can change the CID to run the RUU if you have to, then once completed change the CID back, push revone for locking bootloader, remove tampered etc then when satisfied you can s on again. Just don't s on with hboot 1.55!
Hello all.. my question is very basic..
I have an open bootloader, twrp recovery and S-ON
how do I return stock pleaassee!!
screamwork said:
Hello all.. my question is very basic..
I have an open bootloader, twrp recovery and S-ON
how do I return stock pleaassee!!
Click to expand...
Click to collapse
nkk71's guide linked in my signature should explain everything you need to know to return 100% stock.
alray said:
nkk71's guide linked in my signature should explain everything you need to know to return 100% stock.
Click to expand...
Click to collapse
I don't think so.. there has to be a more logical way as my security is on why do I even to turn it off for a stock recovery :/
screamwork said:
I don't think so.. there has to be a more logical way as my security is on why do I even to turn it off for a stock recovery :/
Click to expand...
Click to collapse
You need s-off for 100% stock and ***LOCKED*** Bootloader. The reason Is you can't downgrade firmware and remove tampered with s-on.
You need s-off to remove tampered and set bootloader to ***LOCKED*** . And because HTC patched newer firmware you must downgrade before you set ***LOCKED*** or you risk the tampered flag returning after your back to stock.
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
You need s-off for 100% stock and ***LOCKED*** Bootloader. The reason Is you can't downgrade firmware and remove tampered with s-on.
You need s-off to remove tampered and set bootloader to ***LOCKED*** . And because HTC patched newer firmware you must downgrade before you set ***LOCKED*** or you risk the tampered flag returning after your back to stock.
_)
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
This makes a lot of sense, Appreciate your help
alray said:
nkk71's guide linked in my signature should explain everything you need to know to return 100% stock.
Click to expand...
Click to collapse
S-off's free ways ((which are a major part)) do not work. Thank you.
screamwork said:
S-off's free ways ((which are a major part)) do not work. Thank you.
Click to expand...
Click to collapse
Hboot 1.54, 1.55 can still gain s-off with rumrunner
Hboot 1.44 can still gain s-off with revone.
If your on hboot 1.56 or above then unfortunately the only way to gain s-off is Sunshine App which cost $25. HTC patched newer firmware against other methods of s-off.
Sent from my SM-T230 using Tapatalk
Danny201281 said:
Hboot 1.54, 1.55 can still gain s-off with rumrunner
Hboot 1.44 can still gain s-off with revone.
If your on hboot 1.56 or above then unfortunately the only way to gain s-off is Sunshine App which cost $25. HTC patched newer firmware against other methods of s-off.
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Yep.. I tried flashing a different ROM/Kernel and it worked!!