Hi, imade le latest Ota update for my Htc one and now i'm s-on and relocked and tempered and my hboot is 1.54 revone doesn't work in this case.
Is there anyway to downgrade hboot 1.54 to 1.44 with s-on of course?
Thanks a lot.
Unlock, flash a custom ROM and see if that works
I've not heard of an OTA that patches the exploit
Or try moonshine
There is no way to downgrade without bricking your device
Sent from my One using Tapatalk 4 Beta
superchilpil said:
Unlock, flash a custom ROM and see if that works
I've not heard of an OTA that patches the exploit
Or try moonshine
There is no way to downgrade without bricking your device
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
The last ota 2.24.401.1 with hboot1.54 patch the revone exploit so i unlocked my one and flash 2 differents roms but it doesn't work.
an another idea or i must waiting until revolutionnary team fmade a new update.:crying:
Thanks anyway.
Mikeo83 said:
Hi, imade le latest Ota update for my Htc one and now i'm s-on and relocked and tempered and my hboot is 1.54 revone doesn't work in this case.
Is there anyway to downgrade hboot 1.54 to 1.44 with s-on of course?
Thanks a lot.
Click to expand...
Click to collapse
Hey,
TIME is the solution
Wait till revone team strikes back
If you cant, only one option is left, unlock by htcDEV(you may lose system apps)
Root and then with root,
Revone works perfect
prunzzz said:
Hey,
TIME is the solution
Wait till revone team strikes back
If you cant, only one option is left, unlock by htcDEV(you may lose system apps)
Root and then with root,
Revone works perfect
Click to expand...
Click to collapse
No it doesn't.
Not with 1.54 hboot.
prunzzz said:
Hey,
TIME is the solution
Wait till revone team strikes back
If you cant, only one option is left, unlock by htcDEV(you may lose system apps)
Root and then with root,
Revone works perfect
Click to expand...
Click to collapse
Revone does NOT work with root (SU) on Hboot 1.54.000 atm.Not with adb and not with a terminal emulator. Stop giving users false hope and you we`re not one of the lucky ones dude cause it just isn`t possible
Nope it doesn't, 4.2 update here and hboot 1.54... Trying for 3 days with revone everyway which way can and at the moment guys I will guarantee you..NO REVONE S-OFF WITH HBOOT 1.54 yet
Sent from my HTC One using xda premium
gee2012 said:
Revone does NOT work with root (SU) on Hboot 1.54.000 atm.Not with adb and not with a terminal emulator. Stop giving users false hope and you we`re not one of the lucky ones dude cause it just isn`t possible
Click to expand...
Click to collapse
Correct answer. It does not work at all, stop to try buddies. I am Hboot 1.54 as well with S-ON, waiting solution to S-off
andylow4421 said:
Correct answer. It does not work at all, stop to try buddies. I am Hboot 1.54 as well with S-ON, waiting solution to S-off
Click to expand...
Click to collapse
i also did the ota and the firmware is the same one you mentioned however my h-boot went to 1.55 at&t htc one m7
intramorph said:
i also did the ota and the firmware is the same one you mentioned however my h-boot went to 1.55 at&t htc one m7
Click to expand...
Click to collapse
As of yesterday there's an S-off exploit for 1.54. 1.55 the newest hboot, and it is still not possible on it...
Sent from my HTC One using XDA Premium 4 mobile app
Related
Does the S-OFF Moonshine method work with 1.54 HBOOT (As I see revone doesn't)? I'd like to change my CID as I really miss having the official English Google Keyboard in my Google Edition ROM however it keeps saying
ERROR: run distiller again and READ
Click to expand...
Click to collapse
connelhooley said:
Does the S-OFF Moonshine method work with 1.54 HBOOT (As I see revone doesn't)? I'd like to change my CID as I really miss having the official English Google Keyboard in my Google Edition ROM however it keeps saying
Click to expand...
Click to collapse
Moonshine does not work with hboot 1.54
connelhooley said:
Does the S-OFF Moonshine method work with 1.54 HBOOT (As I see revone doesn't)? I'd like to change my CID as I really miss having the official English Google Keyboard in my Google Edition ROM however it keeps saying
Click to expand...
Click to collapse
No it does not, I am sorry.
dgtiii said:
No it does not, I am sorry.
Click to expand...
Click to collapse
I assume there isn't a way to s-off that version of HBOOT then?
connelhooley said:
I assume there isn't a way to s-off that version of HBOOT then?
Click to expand...
Click to collapse
Not at the moment ... I believe they are working on it though.
s-off
Can you not s-off atall now?
nathlynn22 said:
Can you not s-off atall now?
Click to expand...
Click to collapse
You can if you've got hboot 1.44 but not with 1.54..... HTC closed the exploit with the updated firmware.
If you're s-off with 1.44 then upgrading the firmware won't lose you s-off.
rider5512 said:
You can if you've got hboot 1.44 but not with 1.54..... HTC closed the exploit with the updated firmware.
If you're s-off with 1.44 then upgrading the firmware won't lose you s-off.
Click to expand...
Click to collapse
Is it possible to downgrade your HBOOT? I'm guessing not but thought I'd ask! I also read everywhere that's its pretty risky and probably not worth it.
connelhooley said:
Is it possible to downgrade your HBOOT? I'm guessing not but thought I'd ask! I also read everywhere that's its pretty risky and probably not worth it.
Click to expand...
Click to collapse
Even if you managed to once you rebooted the phone it would essentially brick, and to boot the new hboot you need to reboot.
Just going to have to wait
Sent from my HTC One using Tapatalk 4
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!
Can someone please finally find a way to S-OFF the HTC ONE?
I've tried revone and moonshine and nothing is working.
I'm currently running Android revolution 40.3, TWRP 2.6.3.3, Hboot 1.54
saar17 said:
Can someone please finally find a way to S-OFF the HTC ONE?
I've tried revone and moonshine and nothing is working.
I'm currently running Android revolution 40.3, TWRP 2.6.3.3, Hboot 1.54
Click to expand...
Click to collapse
You may need to search VERY hard for something called rumrunner.
Sent from my HTC One using Tapatalk
nkk71 said:
You may need to search VERY hard for something called rumrunner.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
tried that, the last part doesnt work
saar17 said:
tried that, the last part doesnt work
Click to expand...
Click to collapse
hboot 1.54 = firmware 2.xx = ROM based on 4.2
40.3 is already 4.4 and 31.6 is 4.3, it MAY work and maybe it won't.
and "the last part doesn't work" isn't very specific, is it?
Not trying to be an a**, but saying things like "i'm on latest version" doesnt really say much.
Versions usually have numbers for a reason.
Sent from my HTC One using Tapatalk
saar17 said:
Can someone please finally find a way to S-OFF the HTC ONE?
I've tried revone and moonshine and nothing is working.
I'm currently running Android revolution 40.3, TWRP 2.6.3.3, Hboot 1.54
Click to expand...
Click to collapse
Ok, as far as i know not sure if you can s-off while on kitkat..so for the sake of s-offing, flash ARHD 31.6 (ive used this to s-off my device twice on hboot 1.55 and it works) it should work for you too. and for revone and moonshine won't do since you need to use rumrunner for hboots 1.54 and 1.55
Now, im assuming you already have adb set up and know how to use adb and fastboot commands, so go on n check out this thread and then go to www.rumrunner.us and download the universal version 0.5.0 and remember to follow all the directions (most importantly disabling all firewall/antivirus, as this is what plagues most people). and then you should have s-off
thank you, I've tried this again and this time it worked!
You can close this post
I had s-off hboot 1.44 I updated to 1.54 on gpe and keep s-off. If I run a RUU that's has hoot 1.56 will I retain my s-off? When I update my hoot version.
Yes, you'll stay s-off. I'm a living proof. I did update to 1.56 and I'm still s-off.
Sent from my HTC One using xda app-developers app
supendal said:
Yes, you'll stay s-off. I'm a living proof. I did update to 1.56 and I'm still s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Anyone else ? Don't want to end up stuck with no way back.
canadacanada said:
Anyone else ? Don't want to end up stuck with no way back.
Click to expand...
Click to collapse
I have 1.56, though via OTA, and am still S-Off.
canadacanada said:
Anyone else ? Don't want to end up stuck with no way back.
Click to expand...
Click to collapse
You will never loose S-OFF unless YOU manually go S-ON
Hi,
Here is the situation.. I have an HTC One..
the hboot is still on 1.44 with s-on.
I want to flash the latest firmware, which is only possible with s-off.. problem is that I'm running a 4.4.2 ROM and trying revone throws an error as the ROM doesn't match the hboot.
Is there anyway I can get s-off easily? or do I have to hunt down a 4.1.2 ROM and flash that before trying to update the firmware?
You can try firewater
I had the same situation, trying to S-OFF with HBOOT 1.44. I was able to get revone's method to work.
http://forum.xda-developers.com/showthread.php?t=2314582
The only issue I ran into is at step 4
4. Prepare to gain S-OFF by running the command: ./revone -P
Click to expand...
Click to collapse
It wouldn't work without root. I used firewater's temp root and it worked perfectly. I did not need my bootloader unlocked or my device rooted.
xJedix
BD619 said:
You can try firewater
Click to expand...
Click to collapse
firewater was the first one I tried cause I'm accustomed to using it with the 1.55 and 1.56 hboot..
didn't work on this run.. and revone keeps failing..
Thinking i'll relock the bootloader and flash the stock ruu with the latest firmware and see if that gets me up to hboot 1.56 and then unlock the bootloader and try firewater again..
any thoughts on this procedure before I try it?
Puff1911 said:
firewater was the first one I tried cause I'm accustomed to using it with the 1.55 and 1.56 hboot..
didn't work on this run.. and revone keeps failing..
Thinking i'll relock the bootloader and flash the stock ruu with the latest firmware and see if that gets me up to hboot 1.56 and then unlock the bootloader and try firewater again..
any thoughts on this procedure before I try it?
Click to expand...
Click to collapse
I would try a 4.1.2 rom before you wipe your device with the RUU.
BD619 said:
I would try a 4.1.2 rom before you wipe your device with the RUU.
Click to expand...
Click to collapse
catching a$$ to find a 4.1.2 rom though..
Puff1911 said:
catching a$$ to find a 4.1.2 rom though..
Click to expand...
Click to collapse
Stock rooted should be fine.
Thanks guys.. managed to find a copy of ARHD 9.4
gave a little trouble to flash.. but finally got through with it and revone s-off worked perfectly after that.
Thanks for the assistance.