yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] EtherealRemnant:
I hope a new root exploit gets found soon... The US OTAs are 1.44 hboot still but undoubtedly replacements and new devices are going to ship with the OTA some time soon...

So... From what I understand, at this juncture, I have to use the token from HTC Dev then root, then revone *should* give me S-OFF again? Or is this broken entirely now with the new OTAs?

Some confirmation would be nice so I don't void my warranty for nothing. I know how to fully restore it back to stock if I need to return it (had to spend 6 hours with the broken One and learned the whole process) but without S-OFF, there's no way to hide it.
[One (M7) Original Android Development] broffy:
can someone help me with this

revone failed (error code = -2)

254|root@android:/data/local/tmp #
[One (M7) Original Android Development] Spartn:
It woud be simple, just unlock bootloader by using htcdev, then load different rom by using custom recovery and then load stock recovery of that rom, after that revon/moonshine might work :)

---------- Post added at 03:49 PM ---------- Previous post was at 03:45 PM ----------

It woud be simple, just unlock bootloader by using htcdev, then load different rom by using custom recovery and then load stock recovery of that rom, after that revon/moonshine might work :)[/QUOTE]

---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------

I woud recommend to all Tmous users to unlock bootloader, flash lower version of their rom or restore nandroid with lower version without that patch, then flash original recovery of the same version and ty revone moonshine :) not tested by me, but i would give it a try if i had tmob
[One (M7) Original Android Development] NTree45:
i was on CM10.1, CM 10.2, ARHD12 and TrickDroid 8 and 5.6.0, using TWRP recoverynone of that worked

or are you saying to do the 1.27.531.8 RUU?
[One (M7) Original Android Development] Mockingbird946:
I originally did S-OFF using revone, then flashed the hex-edited hboot. If I want my hboot to go back to saying S-OFF and UNLOCKED again, is it safe to run revone again, even though I've flashed the hex edited hboot?
[One (M7) Original Android Development] INeFFeCTiVE:
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------

I woud recommend to all Tmous users to unlock bootloader, flash lower version of their rom or restore nandroid with lower version without that patch, then flash original recovery of the same version and ty revone moonshine :) not tested by me, but i would give it a try if i had tmob[/QUOTE]

Tried that... not working for me...
[One (M7) Original Android Development] snowkfh:
So I unlocked my bootloader with HTCDev but never upgraded firmware. I'm on the 4.2.2 SWITCH Rom (2.24.401.1) but my Hboot is the original version (I haven't flashed any firmware, only radios).

Will Revone work for me without flashing the original 4.1 ROM? Or do I have to downgrade in order to get S-OFF?
[One (M7) Original Android Development] tiho5:
Try it with what you have current first.
[One (M7) Original Android Development] snowkfh:
Worked like a charm! Thanks much. I realized with the new firmwares coming with the GE I wanted to get S-OFF while I could :D.

TYVM again.
[One (M7) Original Android Development] roush97:
New firmware 1.27.531.11, s-on, re-locked, still hboot 1.44.0000

This seems weird to me... I updated firmware, unlocked bootloader, installed CWM recovery, rooted, tried s-off many times. Installed a 1.27.531.8 stock rom and kernel, tried revone. Revone gave me an error code 2. I bought this phone off eBay a week or two ago and T-Mobile blocked the IMEI yesterday. I was trying to get s-off so I could remove tampered and unlocked status in order to return to seller. I ended up re-locking bootloader and flashing newest (only 1 I could find) RUU. I now have a TMOUS HTC One with updated firmware 1.27.531.11, relocked bootloader, s-on, hboot 1.44.0000. Why is my hboot not updated?
[One (M7) Original Android Development] ThePhoneGeek:
Ok not sure if anyone cares but here's what I did to solve my Segmentation Fault error.

First off I had a brand new out of the box one from Sprint and (stupid me) let it do the OTA to 1.31 out of the box. I then tried to s-off with revone without doing anything else, bootloader, etc. As many others here I kept getting the Segmentation Fault.

So I attempted to run the ruu to 1.29 but it wouldn't load. Generated the error: Error [140]: Bootloader Version Error.

So after that I went ahead to HTCdev and proceeded with unlocking the bootloader which was successful.

I tried revone again, same error.

Next I pushed TWRP (for Sprint) and then flashed SuperSU.

After that I went back to the revone instructions and followed them paying particular attention to step 3. When you type su in ADB shell I had to go to my phone and grant the access.

Followed the rest of the revone steps and everything was successful.

Again not sure if it helps anyone but this is how I got there and it works fine.

MG
[One (M7) Original Android Development] leon sprouse:
Glad this worked for you. In my case I will NOT go to HTCDEV to unlock the phone.
[One (M7) Original Android Development] RuckusDecay:
Why not?
[One (M7) Original Android Development] DeSaint2:
Arouses suspicion when sent in for repair. There's a slim possibility they would actually check the log and maybe delve deeper than just the hboot. I would say they are to lazy to do that but there might be done over achievers working at repair centers.
[One (M7) Original Android Development] RuckusDecay:
Sounds reasonable enough then.
[One (M7) Original Android Development] Theshawty:
http://fsfe.org/freesoftware/legal/flashingdevices.en.html
[One (M7) Original Android Development] DeSaint2:
Good for the EU. Doesn't mean it works for the rest of the world.
[One (M7) Original Android Development] c5satellite2:
Yes it varies from country to country. In the US and EU it will not void your warranty. If you read the disclaimer from HTC when unlocking your bootloader it says "MAY void warranty". Check the laws in your country if you are worried. Over the past 7+ years, I have only heard of one that was denied for unlocking. Really not worth worrying about.
[One (M7) Original Android Development] broffy:
can u tell me if you every heard about revone failed (error code = -2)

and what does that mean any one >?

Hello, I am getting error code -2. Below is all my information. -t

CID : BS_us001

HBOOT : 1.44.0000

Software : 1.29.1540.17

Kernel :3.4.10-g64174d4 root@abm013 #1 smp prempt

The output after running the -t
[One (M7) Original Android Development] godutch:
I would gladly smash my One to smithereens if it would mean my country would leave the EUSSR...
[One (M7) Original Android Development] broffy:
same problem any luck to s-off as yet ?
[One (M7) Original Android Development] broffy:
have you heard about a error code 2 one removing tampered ?
[One (M7) Original Android Development] Theshawty:
One thing I've wondered for some time now (and failed to find an answer to). How can this tool give itself root access? (Gaining root access (thanks to Dan's motochopper))
[One (M7) Original Android Development] muddassar001:
Cant get s-off error code -6

Hi,

I have tried many times and cant get pass the stage 4

it says revone failed error code -6

is it because i have 4.2.2 and hboot 1.54?

can you get s-off on this hboot?

i have trying all night please need help

anyway of downgrading of reverting it?

Thanks
[One (M7) Original Android Development] Dark Fable:
Lol, I have the same problem and I cant downgrade without s-off. :( Tried it already. Really hope the revone team gets an update to fix this.
[One (M7) Original Android Development] daleski75:
Time to resurrect my little rant again (not that people will read it but hey!)

This is for all the people who come here and ignore the search function...

1. If you ALREADY have hboot 1.54 with S-ON then you CANNOT S-OFF so don't even bother asking if you can or if there is a magical fix.

2. If you already have S-OFF and either on 1.44 or 1.54 of hboot DO NOT S-ON or even better downgrade to hboot 1.44

3. If you are DESPERATE for the 4.22/4.3 OTA do a SEARCH and install the custom ZIP or flash a CUSTOM ROM yes XDA has these!!

4. There is NO WAY to downgrade by RUU with S-ON

5. I repeat DO NOT keep asking about s-off for 1.54 hboot IT DOES NOT WORK!!!!

This thread IS STILL getting cluttered up by people who are too lazy to research the answers to their questions before posting and this leads to people who keep asking the same questions over and over again.

So please read my post or even better search for let's say "hboot 1.54" and voila you get the answer so NO NEED to post the question unless it's a legitimate question which has not been asked before.

Oh and one last thing...

When a new version is released the dev's will update the OP so just keep an eye on that.... or when a solution/workaround is found it will be posted here and the thread will be flooded with people saying "wow thanks bro this solution works" so it won't be hard to spot even without searching.
[One (M7) Original Android Development] muddassar001:
Thanks mate... but i did search and cudnt find a proper answer to it. It dsnt means someone is lazy or anything .. you guys dont have a thing called patience.
[One (M7) Original Android Development] daleski75:
We/I have plenty of patience to help people but if you do a search and cannot find a proper answer it is because there is no answer and in 440+ pages if there was an answer we would all know about it ;)

I am in the same boat as everyone else due to my stupidity (hboot 1.54 and S-ON) and I am waiting patiently for an update from the dev's.

So as soon as there is an answer it WILL be plastered ALL OVER this thread and will be very hard to miss.
[One (M7) Original Android Development] Gandalf Greyhelm:
Me stupid too :silly:

Lesson learned - don't take OTAs! :eek:

I rest assured knowing that "what one man invents - one dev will circumvent" :fingers-crossed:
[One (M7) Original Android Development] leon sprouse:
If the very first page here is read you will see Revone wont work all the time , as much as this is a bummer , live with it I have. I have come to this forum almost every day hoping for a fix. I even , some time ago , sent messages to the dev , got no reply , but hope he read my post.
[One (M7) Original Android Development] xXXschokiXXx:
[ done ]

How long will it take until the HBOOT 1.54 support is ?
[One (M7) Original Android Development] gunnyman:
You're kidding, right?

*smh*
[One (M7) Original Android Development] xXXschokiXXx:
I'm sorry it had read up too late
[One (M7) Original Android Development] gunnyman:
Has anyone PM'ed the OP and suggested he edit the first post and put in big red flashing letters

1.54 HBOOT isn't SUPPORTED...
[One (M7) Original Android Development] craftycarper1:
I reckon you'll be posting this again in under a week!
[One (M7) Original Android Development] daleski75:
Lol I could keep posting this and people would still ask if it's working with hboot 1.54!!
[One (M7) Original Android Development] Brodad:
Looks like this question hasn't been asked before, will the OTA update return a phone to S-ON? I know the 4.3 update will unroot, but u wasn't sure about S-OFF
[One (M7) Original Android Development] gunnyman:
NOPE

Only you returning the phone to S-ON yourself returns a phone to S-on
[One (M7) Original Android Development] phekno:
Revone also doesn't work if you took the latest OTA on TMOUS. In that case HBOOT is still listed as 1.44, but the date is different (dated June 21, I think), and they patched the exploit. Again, as far as I know, that's a TMOUS only thing.

I'm pretty sure I've read this in at least two other places in this thread, but since we're re-iterating information that's already in this thread...
[One (M7) Original Android Development] cc999:
Gunnyman please advise

Is there any harm now that I am fully upgraded to 4.3 and S-off

to put back the 1.44 hboot. Is there any advantage of doing this

being I am S-off already?

Thanks

CC
[One (M7) Original Android Development] Theshawty:
Well, revone works with the older hboot so you could use the various commands.

I don't believe there's a single logic reason to update to the newer hboot at all, it doesn't in any way affect how the device performs in booted state.

I did the mistake of updating OTA, though, but I was unrooted, stock and thought why not. Now I know NOT to take OTA's.
[One (M7) Original Android Development] altimax98:
I can confirm this. My wife just bought a One and it was on the newest update and it wouldn't work.
[One (M7) Original Android Development] cc999:
question

I am already S-off. Turned my developer edition to the GE. Got the OTA to 4.3.

So right now it sits as S-OFF, GE recovery and hboot.

Question is is there any advantage for me to put the 1.44 hboot back or there is

no advantage since I am already S-off. With the current brand new GE hboot you

cannot issue ADB commands to the phone.

CC
[One (M7) Original Android Development] Theshawty:
I'm really not the one to ask for opinions regarding that. I still haven't gotten off my lazy arse to root yet.
[One (M7) Original Android Development] broffy:
can you tell me if you ever came across error code 2 i say it on page on and from then on nothing ? i have and error 2 ./revone -t
[One (M7) Original Android Development] runganwt:
I S-off mine since 1.29 with 1.44 hboot, now I am on 2.24 with hboot 1.54 my S still off. Never take OTA , never plan to S-On ever.
[One (M7) Original Android Development] daleski75:
Very good advice.
[One (M7) Original Android Development] Gerton:
Why dont u do it yourself?
[One (M7) Original Android Development] gunnyman:
because If someone already has, doing so again would be pestering a dev and I don't do that.
[One (M7) Original Android Development] RuckusDecay:
Seriously you guys s-off and then are talking about taking a OTA seriously. God plz help us all.
[One (M7) Original Android Development] mrrogers1:
S-Off...... They're
[One (M7) Original Android Development] RuckusDecay:
Actually it's.

Seriously, you guys s-off and then you guys are talking about taking a OTA seriously! seriously!. God plz help us all.

I have 99 problems and a ***** ain't one or my spelling. I'm just jelly cause now I have to wait till the guys at revone could find another exploit. Sucks balls now. I bought it late. The only thing about the OTA are the radios really.
[One (M7) Original Android Development] Nightf0x_007:
Just keep calm .... And wait fore revone
[One (M7) Original Android Development] RuckusDecay:
For sure will keep checking out OP for anything new that pops up.
[One (M7) Original Android Development] DeSaint2:
Only known benefit is being able to fastboot boot things. 1.54 doesn't allow it. It freezes hboot.
[One (M7) Original Android Development] broffy:
Originally Posted by Sneakyghost View Post

If you were able to change your cid, you are most definitely S-OFF. Can you show us the output of fastboot getvar all please?

Mobile post

version: 0.5

version-bootloader: 1.44.0000

version-baseband: 4A.14.3250.13

version-cpld: None

version-microp: None

version-main: 1.29.1540.17

version-misc: PVT SHIP S-ON

serialno: XXXXXXXXXXXXX

imei: 3XXXXXXXXXXXXXX

meid: 00000000000000

product: m7_ul

platform: HBOOT-8064

modelid: PN0712000

cidnum: BS_US001

battery-status: good

battery-voltage: 3994mV

partition-layout: Generic

security: on

build-mode: SHIP

boot-mode: FASTBOOT

ILED (status read failed (Too many links))

I WAS 11111111 BEFORE

AND I CHANGE IT BACK TO BS

---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------

Quote:

Originally Posted by broffy View Post

version: 0.5

version-bootloader: 1.44.0000

version-baseband: 4A.14.3250.13

version-cpld: None

version-microp: None

version-main: 1.29.1540.17

version-misc: PVT SHIP S-ON

serialno: XXXXXXXXXXXXX

imei: 3XXXXXXXXXXXXXX

meid: 00000000000000

product: m7_ul

platform: HBOOT-8064

modelid: PN0712000

cidnum: BS_US001

battery-status: good

battery-voltage: 3994mV

partition-layout: Generic

security: on

build-mode: SHIP

boot-mode: FASTBOOT

ILED (status read failed (Too many links))

I WAS 11111111 BEFORE

AND I CHANGE IT BACK TO BS

version: 0.5

version-bootloader: 1.44.0000

version-baseband: 4A.14.3250.13

version-cpld: None

version-microp: None

version-main: 1.29.1540.17

version-misc: PVT SHIP S-ON

serialno: .............

imei: 3XXXXXXXXXX

meid: 00000000000000

product: m7_ul

platform: HBOOT-8064

modelid: PN0712000

cidnum: 11111111

battery-status: good

battery-voltage: 4005mV

partition-layout: Generic

security: on

build-mode: SHIP

boot-mode: FASTBOOT

ILED (status read failed (Too many links))

al time: 0.076s I AM ABLE TO CHANGE IT TO WHAT I WANT I CHANGED IT BACK TO 111111111 AND SO ON

IS THE WEIRD ?
[One (M7) Original Android Development] cc999:
Agree

Agree, Will I have trouble because I am on the pure stock GE 4.3 rom?

If not I am going to do it.

CC
[One (M7) Original Android Development] daleski75:
Sorry I haven't before.
[One (M7) Original Android Development] broffy:
i think this problem is bigger than i thought any direction to look in ?
[One (M7) Original Android Development] Nightf0x_007:
But you know bro i really dont need s-off as my phone is international unlocked and i dont rely on OTA and dont need supercid i am a custom rom user all the way :good: but will wait for revone s-off;)
[One (M7) Original Android Development] cc999:
fastboot

Fastboot does work with the 4.3 GE Hboot version. ADB shell does not.

Just converted to the Hboot 1.44. So I have:

64 gb Developer Edition

S-off

unlocked

Hboot ver 1.44

GE pure stock including the 4.3 update

Perfection, If the 4.3 lands for Sence I now can revert easily back to stock and goto the

4.3 Sense rom if wanted.

CC
[One (M7) Original Android Development] daleski75:
Are you already s-off and just trying to remove the tampered flag?
[One (M7) Original Android Development] broffy:
i was s-off but i locked back i dont know how i ran a oem flag 3 thing and it lock now i cant get tampered to move i have a dev version 64 gb i would like to get s-of again but i can settle for the tampered
[One (M7) Original Android Development] daleski75:
What version of hboot?
[One (M7) Original Android Development] broffy:
1.44
[One (M7) Original Android Development] daleski75:
If you are on 4.2.2 you can try downgrading with a 1.29.x odexed stock zip and see if you can then s-off and get rid of the tampered flag and then upgrade back to 4.2.2
[One (M7) Original Android Development] broffy:
i am on stock with 4.1 should i upgrade to 4.2.2 custom rom ? and then try this ?
[One (M7) Original Android Development] Theshawty:
How come the hboot can't be downgraded without S-OFF? What if you flash it through the Ruu mode? OTA's seem to be perfectly able to upgrade the hboot, but why isn't a downgrade possible without S-OFF?
[One (M7) Original Android Development] gunnyman:
Because HTC says so.

It's their way of plugging up exploits.
[One (M7) Original Android Development] daleski75:
As you are on stock 4.1 with hboot 1.44 there is no reason why it should not work.

Try after each step powering off the phone and back on and see how you get on from there.
[One (M7) Original Android Development] Theshawty:
So they "come up with" new exploits to be able to flash a new hboot version, then plug it shut?
[One (M7) Original Android Development] broffy:
so should i like cd /data/local/tmp

restart phone

chmod 755 revone ?
[One (M7) Original Android Development] daleski75:
cd /data/local/tmp

chmod 755 revone

power off the phone and back on

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
[One (M7) Original Android Development] broffy:
ok i will give this a try should i use TE are adb shell

---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------

ok i seriously think something wrong with my phone i went to 4.2.2 using a nand rom i had use a odex unmodified original file now it just stock at the htc beat logo sign
[One (M7) Original Android Development] daleski75:
First time flashing a rom it will take a good 2 or 3 minutes to boot up be patient it will boot.
[One (M7) Original Android Development] broffy:
yeah i know but i didnt i flash the nand it booted i flash the odex and then it stock on the boot
[One (M7) Original Android Development] daleski75:
You will have a much better chance getting s-off to work properly on 4.1.2 rather than 4.2.2 specially if it's 2.24.x firmware.
[One (M7) Original Android Development] broffy:
firmware meaning main software ? it say 1.29.
[One (M7) Original Android Development] daleski75:
You are confusing me you said you upgraded to 4.2.2???
[One (M7) Original Android Development] broffy:
yes i am running android hd 12.1 4.22

version: 0.5

version-bootloader: 1.44.0000

version-baseband: 4A.14.3250.13

version-cpld: None

version-microp: None

version-main: 1.29.1540.17

version-misc: PVT SHIP S-ON

serialno: F

imei: 3

meid: 00000000000000

product: m7_ul

platform: HBOOT-8064

modelid: PN0712000

cidnum: BS_US001

battery-status: good

battery-voltage: 4054mV

partition-layout: Generic

security: on

build-mode: SHIP

boot-mode: FASTBOOT

ILED (status read failed (Too many links))

al time: 0.080s

at the moment

i did what u said and still nothing

only getting error 2 on ./revone -t everything else successful ask to reboot sometime and other times no need to reboot comes up
[One (M7) Original Android Development] DeSaint2:
Edit your post to remove imei and s/n. Don't want bad people getting a hold of that.
[One (M7) Original Android Development] lucario73:
-6 error why...

EDIT: I downloaded the old version: 0.2 and it worked! 0.2.1 didn't work for me.
[One (M7) Original Android Development] gunnyman:
each new Hboot I would assume plugs an exploit so they could I assume, force you to take an update, thus closing an exploit.
[One (M7) Original Android Development] Darealshht:
i have searched the forum and i cant seem to find the problem i have. i keep getting revone failed (error code = 1) when i enter ./revone -P im on att hboot 1.44
[One (M7) Original Android Development] blackangst:
Thank you rev team! T-Mobile One unlocked and tampered flag removed first time. Instructions are clear and concise.

Thank you!

---------- Post added at 02:14 AM ---------- Previous post was at 02:12 AM ----------

Did you get the successful message on step 4? And if you did, did you reboot before attempting the ./revone -P command?
[One (M7) Original Android Development] jgeorge15:
Hey, I seemed to have been having this problem also. I happened to be on the GE 4.3 when I tried and that is when i got that error. I flashed a 4.2.2 rom ARHD to be more specific and tried again it worked with no problems, also I've had problems with windows 8 and vista, not sure if it was just me but I guess your best bet is use windows 7 and be on a rom thats 4.2 or 4.1. and be sure to reboot after chmod 755 revone step.
[One (M7) Original Android Development] looneylu:
I keep getting the following

shell@android:/ $ cd /data/local/tmp
shell@android:/data/local/tmp $ ls
revone
revone-0.2.1
shell@android:/data/local/tmp $ chmod 755 revone-0.2.1
shell@android:/data/local/tmp $ su
root@android:/data/local/tmp # ./revone-0.2.1 -P
revone v0.2.1

revone failed (error code = -6)

I'm on hboot 1.44

Can someone please help me out?
[One (M7) Original Android Development] Slim Shady:
is revone working for hboot version 1.5 ???
[One (M7) Original Android Development] Sloth:
Look HERE for the answer :D
[One (M7) Original Android Development] wildstang83:
Ok guys, sorry for the long down time of this thread. I have updated the op of this thread with a note that should help prevent further undue questions and off-topic.

Basically revone does not support HBOOT 1.54 at this time.
[One (M7) Original Android Development] zFayZz:
i wish i read that hboot 1.54 is not supported... now what do we do....
[One (M7) Original Android Development] :
Wait.