yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] me_rashad:
My HTC one is T-mobile branded, HBOOT: 1.44, android: 4.1.2, software number: 1.27.531.11

keep getting revone failed (error code = -6)

If there's no solution ( i tried a million times and many methods)

So revone does not support software number: 1.27.531.11 and HBOOT 1.44 from T-Mobile.
[One (M7) Original Android Development] RuckusDecay:
Have you try'd this Here maybe this works.:fingers-crossed:
[One (M7) Original Android Development] me_rashad:
Hello, i tried:

adb push revone /data/local/tmp

adb shell

cd /data/local/tmp

chmod 755 revone

power off the phone and back on

adb shell

cd /data/local/tmp

./revone -P

power off the phone and back on

./revone -s 0 -u

power off the phone and back on

./revone -t

it doesn't work.

and i put "su" also before "./revone -P"

it doesn't work also

i think there's a trick :confused:
[One (M7) Original Android Development] RuckusDecay:
Yeah it's called WaitingI know I am. :D
[One (M7) Original Android Development] wildstang83:
Guys, I have no problem updating the OP with a list of supported and unsupported HBOOTS. Just discuss it amongst yourselves and then one of you shoot me a pm when ready.
[One (M7) Original Android Development] Theshawty:
AFAIK, there are two unsupported ones. The 1.54 (obviously) and a 1.44 with a newer build date. IIRC, Tmob shipped an update for it that patched it so it no longer works with revone.
[One (M7) Original Android Development] WorldIRC:
Guys,

Long story short...

Was on 1.44, did Revone..success

Upgraded to 1.54, S-OFF remained.

Now, I had to restore to stock. So I downgraded back to stock 1.44 HBOOT dated back in April, went S-ON, and relocked bootloader (with stock recovery). Now for some reason I am showing Tampered.

I tried to reuse Revone but get either Error 2 or Error 6 -- what's going on!? I've tried everything.

http://xdaforums.com/showthread.php?p=44359831#post44359831
[One (M7) Original Android Development] zFayZz:
im sure revone will have 1.54 support soon
[One (M7) Original Android Development] DeSaint2:
The only known hboots known not to work with revone is 1.54, tmo latest 1.44 and I believe the latest update on AT&T(still 1.44) botched revone as well.
[One (M7) Original Android Development] WorldIRC:
Maybe to keep it more simple -- what causes Error 6?
[One (M7) Original Android Development] KaSaBiS:
I love you. worked great. thanks given
[One (M7) Original Android Development] leon sprouse:
I have a Sprint with 1.44 made in June that Revone wont work on . I get "segmentation fault (dumped core) every time so its not only the tmo 1.44 that doesn't work or att but it seems all the "new " phones made after May 2013.
[One (M7) Original Android Development] Kyral:
hboot 1.44, stock 1.31.651.2 - Successfully s-offed using revone-0.2.1

I needed to htcdev unlock and flash su. I then had to do the optional step 3 (su through adb and then subsequently grant root through superuser app on the phone). If I did not do step 3, I got the segmentation fault error at step 4.

I didn't see a post that had all of this together for this particular hboot and software version, hope it helps someone!

I got my phone mid June and kept it stock until I used revone yesterday, and it worked for me. If you're not unlocked with superuser, try that (if haven't already and don't mind unlocking through htcdev). If you are doing the optional step 3 and it still doesn't work, that's weird since we're on the same hboot and possibly same software version. If you're not unlocked and don't want to htcdev unlock, you might be out of luck for now (?).
[One (M7) Original Android Development] WorldIRC:
http://xdaforums.com/showthread.php?t=2395756

Another user wish same issue. S-ON triggered tampered, when try to re S-OFF, Error 6 occurs.
[One (M7) Original Android Development] shri_chanakya:
tried multiple times every time it just reboots without any error.

###############

root@android:/ # cd /data/local/tmp/

root@android:/data/local/tmp # ll

-rwxr-xr-x root root 648208 2013-08-06 23:45 revone

-rwxr-xr-x root root 648208 2013-08-07 01:19 revone-0.2.1

root@android:/data/local/tmp # ./revone-0.2.1 -P

revone v0.2.1

################

any idea what could be wrong?
[One (M7) Original Android Development] 1username4thisforum:
Bell HTC One

Took a bit of messing around.

Main key that got it working for me was holding the power button for 15 seconds to reboot.

Managed to S-OFF

remove tamper

relock

and then fastboot oem writesecureflag 3 to s-on again

back to stock.

thanks
[One (M7) Original Android Development] me_rashad:
try this

su (enter)

cd /data/local/tmp (enter)

chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)

./revone -P (enter)

http://www.youtube.com/watch?v=J4BWxtjaamM

---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------

There's no solution for error -6 yet, you have to wait.
[One (M7) Original Android Development] tommykwan222:
why I got error=-1?

how to solve it?
[One (M7) Original Android Development] Sloth:
From Post 2 a little reading does wonders :D

Stuck with error: -1?

When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.

To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
[One (M7) Original Android Development] tommykwan222:
but I still got this error for many times
[One (M7) Original Android Development] leon sprouse:
Sorry I forgot to say my phone is locked and I will not use htcdev to unlock it. I do not want a record somewhere saying I unlocked the phone. I am not the trusting type and I know HTC keeps a record of the phones it unlocks.
[One (M7) Original Android Development] Theshawty:
I take it there's absolutely not a chance in hell to downgrade the hboot without being S-OFF?
[One (M7) Original Android Development] sniperelited:
Not support 1.54 s-off:rolleyes:
[One (M7) Original Android Development] daleski75:
Absolutely no way sorry mate.

---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------

Question or statement?
[One (M7) Original Android Development] drizzit03:
I keep getting that pesty Error = -6. I am on hboot 1.44 and I have tried everything that I have read in this thread. Tried running the revone (along with revone-0.2 and revone-0.2.1) from my computer and directly on the phone. Both give me the same Error =-6. I guess I am going to have to cross my fingers and hope they come out with a new version for all of us error =-6 people! Haha.

Edit: I also tried running revone from a stock 4.1.2 and a 4.2.2 ROM. Always get the Error =-6.
[One (M7) Original Android Development] WorldIRC:
Is that the full story, or did something occur on your phone before you got Error 6 (e.g., was on higher HBOOT, was S-OFF previously, etc...)
[One (M7) Original Android Development] mchinand:
The revone download in the first post and revone-0.2.1 in the second post are the same. This is mentioned in the second post. I've seen others also say they tried both revone and revone-0.2.1. Unless they downloaded using the revone link very early on, they are the same.

[HTCOne]$ wget -q http://revolutionary.io/revone
[HTCOne]$ wget -q http://revolutionary.io/revone-0.2.1
[HTCOne]$ diff revone revone-0.2.1
[HTCOne]$

(no output from the diff command indicates that the files are identical)
[One (M7) Original Android Development] drizzit03:
I rooted my phone earlier in the day yesterday. It was never s-off and I can't say for 100% it was never hboot 1.54 before yesterday, but I would only assume it was not since it seems impossible to downgrade. And I am currently 1.44.
[One (M7) Original Android Development] WorldIRC:
Which carrier 1.44 are you on? What is the date?
[One (M7) Original Android Development] drizzit03:
AT&T

HBOOT-1.44.0000

Date: Jul 5 2013, 16:04:18:-1
[One (M7) Original Android Development] WorldIRC:
Do you did the AT&T ota update?

Sent from my HTC One
[One (M7) Original Android Development] drizzit03:
I did one a couple weeks back. I am not sure if that put me at hboot 1.54, that's why I was saying I am not 100% sure if before yesterday my hboot was at 1.44 or 1.54. However, from reading through this thread it seems like downgrading the hboot isn't possible. So I'm kind of assuming that I have always been at 1.44.
[One (M7) Original Android Development] WorldIRC:
ATT released an OTA a week or two ago that did a radio and firmware update. It maintained 1.44 HBOOT but the S-OFF hole was patched in this process.
[One (M7) Original Android Development] drizzit03:
Wow, alright. I am beating a dead horse over here then. I'm sorry for the confusion. I was under the impression that it also upgraded the HBOOT and that is where the issue was. I appreciate your help.
[One (M7) Original Android Development] cee43ja1:
Since you're an AT&T user, you can try this.

http://xdaforums.com/showthread.php?t=2394155

People have claimed that it restored the older HBOOT after taking the OTA, therefore making revone work. I still don't get how it downgraded the HBOOT to a older version without S-OFF.
[One (M7) Original Android Development] drizzit03:
I'll give that a shot. Thanks.
[One (M7) Original Android Development] drizzit03:
It worked! I was shocked to be honest. I followed the steps and it worked flawlessly on the first try. It downgraded my HBOOT to 1.39 and i was able to run revone no problem.
[One (M7) Original Android Development] bilek06:
We look forward with enthusiasm and:angel:
[One (M7) Original Android Development] maddie01:
Once you do S- Off with revone, you stay S-Off no matter what you do with updates, correct. ?
[One (M7) Original Android Development] Sloth:
Correct the only way to go back to s-on is to do it yourself

VERY BAD IDEA IMHO
[One (M7) Original Android Development] runganwt:
Since you decided to go to the dark side, don't even think about going back. :D

:D Even Anakin still have to die to get back from dark side at the end :D
[One (M7) Original Android Development] maddie01:
Thanks. No way would I go back to s On now...why would anyone do that.
[One (M7) Original Android Development] broffy:
did you get this fixed
[One (M7) Original Android Development] Sloth:
EXACTLY ^^^^^
[One (M7) Original Android Development] mugetsu666:
Ok tmobile users I have a bit of good news for u s-on individuals who have not taken the latest update to .11. If u want revone to work correctly u will need to flash the .7 version which I will link here for everyone. I have had 2 out of 2 report back to me with s-off after doing this. All u'll need to do is flash this and then do everything as the op here states for revone. Good luck

http://xdaforums.com/showthread.php?p=44362060

[ROM] M7 Stock Rooted 1.27.531.7 GSM Odex & DeOdex

androidtechy.com/Team-nocturnal/droidnow.com Sign up for [MENTION=310414]Copya[/MENTION]pp with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=DrfOMd
[One (M7) Original Android Development] beats4x:
How do we verify which we are on?

Sent from my Venom injected One powered by ElementalXKernel
[One (M7) Original Android Development] gampt:
Can I flash .7 if I already have .11?
[One (M7) Original Android Development] Sloth:
With your phone in Fastboot USB type the following:

fastboot getvar mainver

or

fastboot getvar all
[One (M7) Original Android Development] Sneakyghost:
Guys, I suspect that not only the hboot update is responsible for the failing of revone but - maybe - also the SBL updates.

If you are planning to go back S-ON for some reason and later back S-OFF again I would like you to try flash the full older firmware packages which are available through Mike1986 posts or my own thread.

It will downgrade not only hboot but also every other available partition.

Essentially, every partition that got updated by any OTA, RUU or firmware package will be downgraded again. Nothing will stay updated.

If you then also flash a corresponding old ROM, you should be back to old system 99%.

If I'm not totally mistaken, that should also enable revone again.

I believe the reason for people not being able to run revone again after they had updated before is solely the fact that they then only downgrade their hboot but leave the other partitions as is.

There are more than one partition related to security. It would most definitely be the SBL images, possibly pg2fs, possibly even radio.

Anyone wanting to go back down and then S-ON and later S-OFF again give that a shot.

The previously linked method via an older RUU does essentially that...

Just saying....

Mobile post
[One (M7) Original Android Development] RuckusDecay:
Have you done this already
[One (M7) Original Android Development] gampt:
Nope.
[One (M7) Original Android Development] kenl:
anyone know why i cant run su on mine?

revone successful - please reboot to continue.

shell@android:/data/local/tmp $ su

su

/system/bin/sh: su: not found

127|shell@android:/data/local/tmp $

i've installed the rooting tool from

http://xdaforums.com/showthread.php?t=2265618

i think it had only installed busybox? how do i even tell if su and busybox is now installed?
[One (M7) Original Android Development] me_rashad:
same question here?
[One (M7) Original Android Development] crazy_kamal:
Android Version : Protected

Can Anyone tell me

what is this??

it shows this is test version!!! is it DEVELOPER Edition phone???
[One (M7) Original Android Development] daleski75:
Want to run something past everyone to see if they think this would be possible.

As the official OTA update can update all partitions with s-on (sbl, hboot) couldn't we take advantage of that to see if a hboot which is s-off could be flashed onto our phones using the HTC OTA method.

My thought process is below and feel free to correct me or say it's not possible.

1. Extract hboot.img from a phone with hboot 1.54 and s-off using DD

2. Repackage the 4.2.2 OTA update zip with the modified hboot (Not sure it's possible due to the signature)

3. Flash the odexed 2.17 firmware to prepare the phone for flashing the modified 4.2.2 zip

4. Lock the bootloader

5. Fastboot oem rebootRUU

6. Fastboot flash zip (name of zip with new hboot and 4.2.2)

---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------

No idea is this a phone you brought or did you do the s-off yourself or flash a engineering hboot from another thread?
[One (M7) Original Android Development] cc999:
hmm

If this is a n phone then you did not get what you paid for. Its S-off on 1.54 so this

has seen a few firmwares.

CC
[One (M7) Original Android Development] Theshawty:
Don't you mean 1.44?
[One (M7) Original Android Development] horsetastic:
No I think he means 1.54 hboot from an already s-off'd phone....Not sure if it would be any different to an s-on 1.54 hboot though....
[One (M7) Original Android Development] daleski75:
Either or really just wanted to know if it would be feasible?

---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------

That is what I meant and is there more to it than just the hboot image then I take it when you s-off?
[One (M7) Original Android Development] horsetastic:
I have a feeling that it's perhaps not necessarily the hboot that the security lives within but more the hboot that sets it on low boot. But I could be totally off here. So I'm thinking that if this is the case the hboot probably isn't any different from an s-on to s-off phone. I mean the next update could well have the hboot set s-off devices back to s-on for all we know.....

Having said that it might be better to try and take a 1.44 hboot and rename it to think it's a 1.54 hboot then attempt your method. As long as the hboot was correctly edited I would think it would be a safer way of installing it rather than just trying to write the edited hboot alone.....
[One (M7) Original Android Development] daleski75:
Best bet then would be to get a dd copy of the 1.54 hboot both with s-on and s-off and then do a binary compare to see if indeed there are any differences?
[One (M7) Original Android Development] godutch:
back in the desire days [MENTION=939673]ieftm[/MENTION] said the security flag is inside the radio and hboot boots the device with security on or off depending on this flag
[One (M7) Original Android Development] horsetastic:
might as well. not like it's going to harm anyone to see :)
[One (M7) Original Android Development] crazy_kamal:
Well..Nop...

from the very beginning it was as it is...

i just dont wanna use the version i have on it...

so i decided to use custom ROM..

i can get unlock boot loader but while flashing recovery m getting error

"

fastboot flash recovery recovery.img

sending 'recovery' (7916 KB)...

FAILED (remote: data length is too large [RAMDUMP2USB MODE])

finished. total time: 0.016s

"
[One (M7) Original Android Development] daleski75:
Reading up on this I get the feeling if this was possible then sneakyghost would of already done it so there must be a lot more to it than just flashing a hboot within an ota package.

---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------

This looks like you are in some custom mode on hboot maybe worthwhile speaking to some dev's to see what they think.
[One (M7) Original Android Development] crushalot:
I was thinking the same thing, but there has to be more too it than that. I have helped several users returning to stock and they have flashed the older firmware packages in full from Mike's thread. Tried several versions, but even after back down to hboot 1.44 and sbl, still no working revone to s-off again.

The lowest firmware package of 1.29.401.12 does include sb1 blocks but is missing some blocks that are in the decrypted RUU's. So if there is no RUU for a device then simply flashing back the older firmware even with the sbl updates doesn't seem to work.

However shouldn't we be able to make a custom firmware zip that can be flashed if s-off to return to stock by pulling the extra blocks included in the RUU?

Like basically make a return_to_stock_firmware.zip by pulling everything except the system.img and data.img from a decrypted RUU?

That would certainly return all blocks to stock level and should allow revone to work again if needed. After flashing that and then restoring a stock nandroid, should be exactly like a factory RUU correct?

What do you think Sneakyghost?
[One (M7) Original Android Development] horsetastic:
It'll be interesting to see how the s-off guys end up getting around the block, if they do that is....Or if a hboot downgrade can be made possible. I've been rooting through the hboot files to see if I can find the bit that refers to checking the actual hboot version itself but am pretty much way out of my depth lol
[One (M7) Original Android Development] Chezbel:
You should take a look at the HTC One X forums. Still no S-OFF after a year plus. I'm not trying to discourage people from thinking, but you you will find 100s of pages of "ideas" like this.

Sent from my one and only One
[One (M7) Original Android Development] ayk07:
i don't know what is wrong with the revolutionary irc moderator but he banned me for trying to double check if downgrading would work to get s-off, and asked if htc made .11 impossible for getting s-off. never asked for eta or future plans. few people said downgrading to .7 would work for getting s-off so i wanted to make sure, instead of giving a simple yes or no answer he went into rage mode.
[One (M7) Original Android Development] Theshawty:
Maybe, maybe not. Don't think S-OFF is within the bootloader, though. If one's already S-OFF it's better to just flash back to the 1.44 bootloader and revone will work completely.
[One (M7) Original Android Development] Sneakyghost:
Security flag is stored in partition 3, with little else. It's easy to identify and not even hidden.

Problem: p3 is also under the protection of that very security toggle in it. So, if you're S-OFF already, you could write a copy of that partition with security toggled ON back to the chip, reboot and be S-ON.

Unfortunately, it doesn't ever work the other way around as it cannot ever be written to while security is ON, unless you have HTC's private signing keys. Those are guarded like golden eggs and you won't ever get them.

BUT: there is a certain situation where the chip is unprotected. I know from the HTC OneS that it was possible to reset the chip into this temporary insecure mode with an exploit were the phone would be rebooted into it.

While in that mode, an S-OFF copy of partition 3 could be written and thus security permanently disabled.

Revone seems to be slightly different in how it does it but I'm rather sure it utilizes the same flaw in the chip design to reach this temporary insecure mode. It is essentially the same on all past snapdragon generations. The difficulty lies in getting the phone into that state. That is what the revone exploit did on the older firmware. Now, it seems patched.

Revolutionary team is certainly feverishly trying to find a new trick to get the phone into that state, while HTC does the same, just with the intention to be faster and plug that hole before it is discovered :D

Mobile post
[One (M7) Original Android Development] daleski75:
That is a very helpful post and nice to know that the revolutionary team are still hard at work.
[One (M7) Original Android Development] Sneakyghost:
I was only guessing. Maybe they're sitting in their lazy armchairs, watching the drama and having a laugh.

Mobile post
[One (M7) Original Android Development] mugetsu666:
U can but if u took the update or updated ur firmware already, it's pointless as u have already applied the patch.

androidtechy.com/Team-nocturnal/droidnow.com Sign up for [MENTION=310414]Copya[/MENTION]pp with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=DrfOMd
[One (M7) Original Android Development] rakesh595160:
Running on stock 4.2.2 with the hboot 1.54...

I want to install custom roms and mods but don't wanna void my warrenty so is this anyway to get s off without using HTC dev
[One (M7) Original Android Development] godutch:
No, you will have to wait or risk voiding your waranty...
[One (M7) Original Android Development] mugetsu666:
If u look at ur phone information and if u took otas u'd know

androidtechy.com/Team-nocturnal/droidnow.com Sign up for [MENTION=310414]Copya[/MENTION]pp with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=DrfOMd
[One (M7) Original Android Development] horsetastic:
Ok just a simple, perhaps very noob question from me lol. But what would simply running the command below do?

su

./revone

Without the -p....does it even do anything?
[One (M7) Original Android Development] daleski75:
You can run revone and without any switches it reports success because it's done nothing at all, you can even run it with -xyz and it has the exact same output.
[One (M7) Original Android Development] RuckusDecay:
Damn you learn something new everyday. Nice read. I understand a little more.

---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------

Just maybe caused its just fun to watch people go rage mode saying it doesn't support hboot 1.54
[One (M7) Original Android Development] ChongoDroid:
*Runs into thread in slow motion*

Weeee are the chammmpiooons!!!!!!

Haha.. thanks Team Revolutionary. First try success, on Rogers HTC One. :D

S-OFF ... hello old friend.
[One (M7) Original Android Development] sokoko:
Allo out. Nickelodeon
[One (M7) Original Android Development] daleski75:
What?
[One (M7) Original Android Development] brendans13:
Tried many times using different combinations/sequence of commands and both versions of revone without success.

This is on a Telstra HTC One with hboot ver 1.44, running stock rooted android 4.1.2 rom.

Not sure if this is a coincidence either but ever since trying unsucessfully to S-Off with both revone and Moonshine method my MMS is now broken.. :confused:
[One (M7) Original Android Development] horsetastic:
haha thought as much, cheers for clearing that up :)