Database Develop

[Q] Revone pb cause of hboot upgrade anyway to downgrade?

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

[Q] Can I restore to stock?

When i bought my phone it had 1.31 on it. Its now unlocked and rooted running a 4.3 ROM. Can I use the 1.29 RUU to return to stock or do I need to wait for a 1.31 RUU? I tried searching but I'm still confused. I'd like to install 1.29 to gain s-off. Thanks in advance.

See here http://forum.xda-developers.com/showthread.php?t=2390821

S-Off using Revone and also use Revone to return bootloader to Locked and not Relocked or Tampered. Then you can run RUU to anything you want. Once you run RUU don't bother returning your device to S-On because in case you ever want to run a previous RUU again you can without issue until you return to S-On and at the same time you don't need root to return to S-On
Sent from my HTCONE using Tapatalk 4

EPayne123 said:
S-Off using Revone and also use Revone to return bootloader to Locked and not Relocked or Tampered. Then you can run RUU to anything you want. Once you run RUU don't bother returning your device to S-On because in case you ever want to run a previous RUU again you can without issue until you return to S-On and at the same time you don't need root to return to S-On
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the quick replies. So revone will work on 1.31? Or do i have to follow the instructions in the link posted above? I thought I had to relock my bootloader then flash the 1.29 RUU to be able to use revone. One of the posters in the link above said he didn't have to downgrade from 1.31 to get s-off. My main reason for wanting s-off it to flash radios and firmwares. If i can use revone on 1.31 it would be much easier.

No, you do not need to downgrade from 1.31 to get S-Off using Revone. Just use the instructions in the Revone thread to get S-Off then use Revone to utilize the -t -l command to remove tampered and lock the bootloader instead of relocked and then run RUU. Flawless.
Sent from my HTCONE using Tapatalk 4

Thanks everyone. I tried revone with my phone running a 4.3 rom and it didnt work. I kept getting error 1 so I flashed ViperRom and went throught the steps again. I'm now s-off. Now I just need to learn how to flash the firmware and radios included in the 4.3 update. I'm used to my evo lte where i could just flash through twrp.

[Q] How to go back S-ON with hboot 1.55?

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!

what to do? need complete stock to send back, currently at relocked s-on stock rom

i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters

You will need s-off to reset the bootloader back to locked instead of re-locked
Sent from my HTC One using xda app-developers app

adoboFosho said:
i was running custom rom but decided the blue haze on the camera wasn't doing it for me and turns out htc are able to repair it once i send in
I got to relocked s-on only showing no tampered or anything by flashing ruu
running latest sense rom and hboot 1.56 atm
need to get back to just [locked] showing s-on
this is frustrating me I need help
i unlocked this originally through htc if that matters
Click to expand...
Click to collapse
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF

raghav kapur said:
S-OFF the phone. Then, use the flash the Guru Bootloader Reset zip in TWRP/CWM. From there, you can set it to Locked. But, HBOOT 1.56 has a lot of problems when trying to S-OFF. Its a hit and miss chance. Try using Firewater to S-OFF
Click to expand...
Click to collapse
the instructions on firewater on their site probably doesn't work with what I have atm cant link to the site yet not enough posts..
what is the best course of action I take?
im running latest android not 4.3 with an m7 not m8 and unrooted

i tried temprooting using firewater just to get s-off didn't work since i have newest android
can someone tell me what to do from here? flash 4.3? root again?!

S-OFF Situation with last Firmware & H-BOOT 1.57

Hey guys,
i'm sending my One to htc at the moment and i think i'll get it back in a couple of days with new camera module and a firmware update .
At the moment my HBOOT is 1.4x, the phone was S-OFF via revone and i reversed it back to stock yesterday.
Are there any safe possiblities to S-OFF a 1.57 HBOOT device WITHOUT using htcdev?
From what i've read recently
- Revone isn't supported with HBOOT 1.57
- Firewater can maybe S-OFF but needs HTCDEV unlock and maybe the Bootloader is TAMPERED after that
- Sunshine costs 25 USD !?
So is the conclusion correct that an unlock via htcdev is absolutely necessary to S-OFF atm?
Is it also correct that i can't get rid of the TAMPERED flag when Firewater fails?
Thanks

Once S-Off you can revert the BL back to locked and remove the tampered flag anyway.

That's right but from what i heard some devices can't be S-OFFed with Firewater. Then the device is TAMPERED and you can't get rid of that because S-OFF doesn't work!?

Dacoco said:
That's right but from what i heard some devices can't be S-OFFed with Firewater. Then the device is TAMPERED and you can't get rid of that because S-OFF doesn't work!?
Click to expand...
Click to collapse
you cant get rid of the tampered flag full stop without s-off
sunshine does not require the bootloader to be unlocked, it does everything for you but like you said costs $25 however, it is a one off payment, after that you don't need to pay again to s-off the same device again.
all other s-off tools require the bootloader to be unlocked via HTC Dev.
if you are on HBOOT 1.56 or 1.57 and firewater fails then sunshine is the only way.

Seanie280672 said:
you cant get rid of the tampered flag full stop without s-off
sunshine does not require the bootloader to be unlocked, it does everything for you but like you said costs $25 however, it is a one off payment, after that you don't need to pay again to s-off the same device again.
all other s-off tools require the bootloader to be unlocked via HTC Dev.
if you are on HBOOT 1.56 or 1.57 and firewater fails then sunshine is the only way.
Click to expand...
Click to collapse
Okay, thank you very much for that!
Sorry for the question but can i install TWRP and flash ROMs via Recovery when just htcdev unlocked and S-ON? On the One X it was necessary to flash the boot.img from a pc. On the One this isn't necessary right?

Dacoco said:
Okay, thank you very much for that!
Sorry for the question but can i install TWRP and flash ROMs via Recovery when just htcdev unlocked and S-ON? On the One X it was necessary to flash the boot.img from a pc. On the One this isn't necessary right?
Click to expand...
Click to collapse
yes you can flash custom rom's whilst s-on as long as the bootloader is unlocked and also correct, no need to flash the boot.img separately.

Does someone know what devices will fail with firewater? Is it a change in the hardware maybe? My One is from May 2013 so i hope it may work.
There has to be a change between the devices with 1.57 that fail and the devices that work!?

Dacoco said:
Does someone know what devices will fail with firewater? Is it a change in the hardware maybe? My One is from May 2013 so i hope it may work.
There has to be a change between the devices with 1.57 that fail and the devices that work!?
Click to expand...
Click to collapse
download emmc check from playstore onto your phone, if the number starts with 9001 it will fail.

Seanie280672 said:
download emmc check from playstore onto your phone, if the number starts with 9001 it will fail.
Click to expand...
Click to collapse
Great! I will do that if i have my phone back. Thanks man
EDIT: What is the emmc id?

Dacoco said:
Great! I will do that if i have my phone back. Thanks man
EDIT: What is the emmc id?
Click to expand...
Click to collapse
if you sent your phone back to HTC to get the camera repaired, they will probably replace the motherboard, if they do then firewater probably wont work, all you can do is try.

Okay, i'll wait and report

Dunno if it's different but when I s-offed and unlocked and rooted my HTC one max I used firewater and used temp root method which in turn s-offed and unlocked bootloader which can be done on our highest hboot. I don't no if it's different for you guys but it might not be such a major problem but when I sent my HTC one m7 back for repair when I had it I reverted back to stock and left s-off present they said nothing about it.

Dacoco said:
Okay, i'll wait and report
Click to expand...
Click to collapse
if you request them to don't update software they don't do that
If it's camera problem they don't tends to update they don't waste their time if your phone motherboard s off once it can be easily again

Seanie280672 said:
if you sent your phone back to HTC to get the camera repaired, they will probably replace the motherboard, if they do then firewater probably wont work, all you can do is try.
Click to expand...
Click to collapse
they just change camera module
---------- Post added at 02:21 AM ---------- Previous post was at 02:18 AM ----------
Seanie280672 said:
download emmc check from playstore onto your phone, if the number starts with 9001 it will fail.
Click to expand...
Click to collapse
Link please

yatindroid said:
they just change camera module
---------- Post added at 02:21 AM ---------- Previous post was at 02:18 AM ----------
Link please
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Mine:

Seanie280672 said:
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Mine:
Click to expand...
Click to collapse
Mine