yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Sharky52:
You can install a RUU, after that you have Hboot 1.44 again and you can use revone.

I did that after a flash to Hboot 1.54.

Link to RUU : http://www.androidfiles.org/ruu/?developer=M7
[One (M7) Original Android Development] gee2012:
He has S-ON so a Hboot downgrade will probably not work.
[One (M7) Original Android Development] Sharky52:
My mistake, i was only locked, but he can try.
[One (M7) Original Android Development] crushalot:
I have used revone on 6 different phones now and I had the same issue with getting that error -1 no matter what I tried on one of them.

Then I tried to run the commands from a terminal session on my phone rather than an adb shell and it worked. Could you try that?

Also even with the 1.54 hboot I was able to get revone to work on one phone. Perhaps keep trying it?

Is there a RUU for your carrier? That would reset hboot back down to 1.44 and then perhaps better luck with revone.

Good luck

EDIT: My bad. I guess a RUU won't work with s-on if the firmware on the phone is newer than the one in the RUU
[One (M7) Original Android Development] Super-Veloce:
if you used htcdev before, they will have your imei and could do difficult ;)

I did revone method whitout htcdev.. so I can make it totally stock and when repair center looks up my imei, they won't find htcdev registration of my imei :)
[One (M7) Original Android Development] gee2012:
If you turn in the phone completely stock (S-On, locked, correct CID and stock firmware) they can`t deny warranty :) even if a user unlocked by htcdev.com.
[One (M7) Original Android Development] Super-Veloce:
maybe they can, because you used htcdev and agreed something on that page..and you're not going to unlock for nothing and relock again ;)

on the other hand, if you claim warranty, for something not custom rom related, they can refuse either ;)
[One (M7) Original Android Development] gee2012:
HTC has to prove and link the modification/unlock to be the cause of the malfunction. EU law.
[One (M7) Original Android Development] DeSaint2:
Just because you requested the token doesn't mean you used it. You could have changed your mind. Now if they put in the agreement "By requesting this token parts of your warrant will be voided. Examples include blah, bla, blah, etc" then you would have reason to worry.
[One (M7) Original Android Development] JHK1984:
Followed instructions carefully and now I am officially unlocked and S-off.

Thanks :good:

Some of the possible misunderstanding that a newer flashers could have:

- Don't include * in the cmd prompt

- Include all spaces in the command "cd(space)/data" and so on

- Check the directory for proper location of execution
[One (M7) Original Android Development] poondog:
Hmm no, my device is not rooted

I will try with screen on :)
[One (M7) Original Android Development] mrrogers1:
Works great, just did another one today bringing total up to 6 for me. :thumbup:

*I wanted to add, if you have not donated, at least $1 of your money for the solution these guys have given us, you should. I've donated more than that but I know times can be tough but a dollar, you can spare. No excuses... (*at least don't post them. Lol)

THANK YOU TEAM REVOLUTION!
[One (M7) Original Android Development] flamechamp:
I tried the revone using the terminal from my phone.

The ./revone -P command resulted in error code -6 while the ./revone -s 0 -u resulted in error code -1.
[One (M7) Original Android Development] joshjunior:
Tried from my phone as well and got this.. maybe bc I'm running the Google edition?
[One (M7) Original Android Development] gartner83:
The ones who do have the problem, are on HBOOT 1.54, that's the problem.
[One (M7) Original Android Development] grtmoby:
This is most probably due to your hboot version.
[One (M7) Original Android Development] joshjunior:
Well hell thats what I get for not getting the one through tmobile lol. Thanks guys. Should I just hang tight till a work around comes out or is there something I can do
[One (M7) Original Android Development] Derek0228:
Hey guys, got a quick question, if I S-OFF and Unlock using this method, will it still wipe my internal SD just like the HTC Unlock?

Sorry, new to the One, was keeping it stock because of how great it just is but it's time to unleash the power of this beast :)
[One (M7) Original Android Development] joshjunior:
It won't wipe anything from my understanding
[One (M7) Original Android Development] Sloth:
Nope :D
[One (M7) Original Android Development] gee2012:
No , you will not loose data.
[One (M7) Original Android Development] Sneakyghost:
Hello everyone,

I was bothered by the case of a sudden S-ON after the recent firmware update, so I wrote an email to a HTC guy I know. He contacted HTCdev department to inquire if HTC would force phones back to S-ON via update. They say they're not aware of such a thing but they asked for more info.

Could the ones who had that happen please detail:

-what did you do before your phone became S-ON? As exact as possible

-what would I need to do, to reproduce this?

-exact info on the phone and firmware used.

To gain that info you can run fastboot getvar all and check your software info page for the rest.

Please either PM info to me or drop it here and notify me via PM as I don't regularly check into this thread.

Thanks!

mobile post
[One (M7) Original Android Development] AlbertoSONIC:
Hey guys, i'd like to have s-off, now i'm on RenovateROM 4.2.2 with 1.44 hboot, so i can use revone without any problems?

And a little question: what's the gain avenued with s-off?
[One (M7) Original Android Development] gee2012:
Yup, just follow the instructions in the OP and disable fastboot option in settings/energy at the bottom.
[One (M7) Original Android Development] DeSaint2:
Being able to flash latest firmware without having to have matching cid is the big one. Or being able to downgrade firmware to return to true stock. There's a whole lot more but beyond that you get into the riskier stuff. S-off is a major thing for people on carrier contracts especially AT&T. They are just so stinking slow with updates.
[One (M7) Original Android Development] AlbertoSONIC:
Thank guys! And what about warranty? I need to flash ruu and return s-on or i can keep s-off?
[One (M7) Original Android Development] Keupie:
Just tried to s-off, Worked like a charm!! I am now s-off and unlocked! Big thanks to the revolutionary team!!
[One (M7) Original Android Development] DeSaint2:
That's the other major thing lol. Yes you want to Ruu back to carrier stock Rom to ensure everything is back to stock then use the commands in the second post to show locked (not relocked and also remove tampered from the bootloader which is a separate command) and then return to s-on.
[One (M7) Original Android Development] AlbertoSONIC:
How can i brick my phone using s-off?
[One (M7) Original Android Development] gee2012:
No, don`t go back to S-On. Hboot 1.54.000 is not yet supported for S-Off. If you need to downgrade to 1.44.000 for warranty you can`t!

---------- Post added at 10:00 AM ---------- Previous post was at 09:56 AM ----------

Why would you want that? S-Off itself doesn`t brick your phone.
[One (M7) Original Android Development] AlbertoSONIC:
I need to know what i can't do with my phone... To prevent brick!
[One (M7) Original Android Development] Keupie:
Ok 1 question, after every reboot i get the message that the systeem is recovered from an error and it asks me to send the report to HTC. I am s-off, unlocked and stock. Can someone tell me what this means and what i can do about it?

---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------

I am on Hboot 1.44.000 So everything should be allright.
[One (M7) Original Android Development] gee2012:
The only way to brick it is to flash a non HTC One rom on it. I wouldn`t go S-On if i were you. There aren`t any stock 4.2.2 RUU`s available. So incase you need warranty you can downgrade to a 4.1.2 RUU, update it and turn it in.
[One (M7) Original Android Development] nikolaus2007:
Wanna test this, but where can I get ARHD 9.4 for the One again?

Thanks
[One (M7) Original Android Development] gee2012:
Look in the ARHD thread and post a request, maybe a user stil got it. Its off the ARHD servers. Let us know if it worked please :)
[One (M7) Original Android Development] daleski75:
I tried downgrading to an older rom from maximus7 and after doing so the touchscreen refused to function whatsoever and revone -P etc still gives an error code -6 or -2 but I did not see any segmentation faults
[One (M7) Original Android Development] gee2012:
Yes, kinda expected that. If that would have worked S-On wouldn`t serve a purpouse :D
[One (M7) Original Android Development] daleski75:
It looks like that guy who downgraded to arhd 9.4 was simply very lucky, had a look around and could not see any links for it either.. also did this guy recover from a nandroid backup or install a fresh copy of arhd 9.4 with full wipe etc?
[One (M7) Original Android Development] gee2012:
To be honset i doubt that the procedure he discribed worked at all.
[One (M7) Original Android Development] daleski75:
I suspect that too but worth a shot if someone has arhd 9.4 zip handy
[One (M7) Original Android Development] Keupie:
Heey guys, Just read that the OTA update to 4.2.2 is available in Holland. This morning i achieved s-off. I am now on stock rom and recovery, hboot says unlocked s-off with cid HTC__001. Is it safe to update to 4.2.2 or would this brick my device due to unlocked bootloader and s-off? Thanks in advance!
[One (M7) Original Android Development] daleski75:
Its safe :)

---------- Post added at 12:03 PM ---------- Previous post was at 11:29 AM ----------

Tried loads of combinations to get revone working with hboot and nothing has worked always end up with an error code -6.

1. Nandroid restore of maximus7 1.29.401.7

2. Restore and full wipe of odexed 1.29.401.7

3. Restore and full wipe of odexed 2.17.401.1

4. Restore and full wipe of cyanogenmod

Also tried moonshine with the 1.29.x and the closest I got was it said moonshining 1 of 2 of 3 of 4..... to 10 of and got no further.

Looks like it simply does not work any more under 1.54 hboot so that other guy who downgraded was very lucky.
[One (M7) Original Android Development] fongnd:
phone require decrypt code

OK! I managed to get S-OFF

but upon rebooting phone, it require decrypt code to gain access to phone. only emergency call is allow.

Does anyone experience the above situation?

thanks,
[One (M7) Original Android Development] steljwaxd:
I need some serious help.....

I did the firmware.zip thing, so I needed to relock again for that.

Now the unlocking procedure with revone is failing with a core dumped error, and I noticed I'm on hboot 1.54.0000 now.

Is there any way I can get the unlocked status again? Im still S-OFF......
[One (M7) Original Android Development] gartner83:
With HTCdev token? But I guess you already knew that:cool:.
[One (M7) Original Android Development] steljwaxd:
;)

Yes, I it safe to downgrade the hboot to 144.0000 ?
[One (M7) Original Android Development] gartner83:
It should be. I RUU-ed back to 1.28.401.something from 2.24 with RUU and it downgraded my HBOOT. I did it with RUU exe.
[One (M7) Original Android Development] daleski75:
Yes it is safe to downgrade as the RUU will flash everything including the hboot.
[One (M7) Original Android Development] steljwaxd:
Which RUU did you use? (I mean, I don't want a RUU with HBOOT 1.54.0000 included....)

This really sucks, I wanted to do a quick firmware upgrade and now I'm changing underwear..
[One (M7) Original Android Development] daleski75:
Also just a quick test before you downgrade can you type su before running revone and let me know if you can unlock it or if it still core dumps?
[One (M7) Original Android Development] gartner83:
http://www.androidfiles.org/ruu/get...31.27_10.31.1131.05_release_310878_signed.exe

I ruued this one but I don't know if it's the right for your model. Is it European?
[One (M7) Original Android Development] steljwaxd:
shell@android:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1

revone successful.
shell@android:/data/local/tmp #

Done, no need for downgrading with RUU's, I'm a happy man again, unlocked with 1.54.0000

Thanks everybody, also for pointing out to the RUU's
[One (M7) Original Android Development] gartner83:
Great. You were smart enough you didn't SON after the update. Well, I wasn't and there is no way I can successfully do the -P command now.
[One (M7) Original Android Development] daleski75:
You and me both I also did s-on and after a reboot of the phone it's reverted back to tampered and relocked.

---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------

Just a thought if we get hold of a nandroid backup of a phone which has hboot 1.54 and CAN be unlocked still would flashing that to our phones resolve our issue with revone -P??
[One (M7) Original Android Development] gartner83:
Yeah, I read your posts, we just have to play around, do we?:laugh:

Yeas,that's an interesting idead but who did unlock it from 1.54?
[One (M7) Original Android Development] daleski75:
It's bugging me because I am normally so careful, going to try restoring some of my older cwm backups when I also had s-off just to see what happens really, not holding up much hope but hey who knows.

---------- Post added at 04:09 PM ---------- Previous post was at 03:42 PM ----------

No luck at all looks like it's missing the preperation of doing the s-off which is already there for other people who have downgraded etc.
[One (M7) Original Android Development] gee2012:
Yup , after ./revone -P the -6 error apppears. I tried it in every possible way both with adb and terminal emulator both in adb shell and su. Aah well, we`ll just to wait for a succesfull exploit and currently running Android Revolution which runs very well.
[One (M7) Original Android Development] raptir:
I'm sorry for the noob questions, but I have been on Nexus devices for a while and this is my first device in a long time that is not "open."

I just bought a T-Mobile HTC One. I was going to hold off on unlocking and rooting in case of any defects, but I saw this and it seems like this should resolve my concerns. If I have S-OFF and then set the bootloader to "LOCKED" and remove the "TAMPER" flag, it should pass a warranty check?

I've also seen a lot of posts about issues since the update... the T-Mobile One is still on H-BOOT 1.44. If I get myself S-OFF now, will I be able to unlock/lock my bootloader even after my phone is ultimately updated? Or do I need to be careful about accepting the updates even if I have S-OFF?
[One (M7) Original Android Development] Sneakyghost:
That's not exactly right - there are many ways to brick the phone.

The most dangerous for people here would be to flash a modified hboot (e.g. have a moonshine S-OFF or flash my modified hboots) and then go back S-ON. The next reboot after that will instantly brick the phone as the security won't allow an unsigned hboot to execute - read: no boatloader, no boot. Dead phone.

mobile post
[One (M7) Original Android Development] gee2012:
If i were you i would unlock the phone right now bro. If you update to 4.2.2 you might not be able to atm. Commands: adb shell ; cd /data/local/temp/ ; ./revone -l.
[One (M7) Original Android Development] Sneakyghost:
If you updated your firmware you got the new touch driver which does not work with the old 4.1.2 system. Since there is no old touch image available, you can now only run newer ROM's. As far as I know, the old RUU's come without the touch driver image so we don't have an old one.

mobile post

---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------

It might though as he said he used an engineering hboot (which is available with moonshine S-OFF I believe)

mobile post
[One (M7) Original Android Development] gee2012:
What kind of log could we produce to record the failure to prepare S-Off for the Revone devs?
[One (M7) Original Android Development] Sneakyghost:
Dunno mate. Ask them.

mobile post
[One (M7) Original Android Development] raptir:
Well, that's my plan. But I was hoping that I could get a response for the second question in particular. If I have S-OFF, can I safely accept any OTA updates and always be able to do the lock process, even if HBOOT is updated?
[One (M7) Original Android Development] gartner83:
Isn't that the lock command? Should be ./revone -u.
[One (M7) Original Android Development] gee2012:
No, thats the problem. The updated Hboot 1.54.000 cannot be unlocked atm, the one you are on now can. So you have to do it now if you want to that is.
[One (M7) Original Android Development] raptir:
Ah, even if I have S-OFF before I updated it cannot be unlocked? And I assume that means it cannot be relocked (with the LOCKED status)?
[One (M7) Original Android Development] gee2012:
You can unlock and lock the current bootloader 1.44.000, but the new bootloader 1.54.000 cannot be locked or unlocked atm.
[One (M7) Original Android Development] raptir:
Alright, thank you for the clarification. Looking through the thread it seems like there were a couple posts saying that if you have S-OFF on HBOOT 1.54 you can downgrade to unlock/lock the bootloader, but the only links I saw were for RUUs for the European version. Is there any way I can do a full (not just nandroid) backup of my system once I S-OFF/unlock that would include recovery/HBOOT that could then be used like an RUU for my T-Mobile version to get the old HBOOT back?

EDIT: Then again this is probably moot since I'm sure it will be a while until the T-Mobile version gets updated.
[One (M7) Original Android Development] Sneakyghost:
wtf?!?

Confusing much here?

You mix up locking/unlocking and security on/off by the looks of it.

HTCdev unlock works fine no matter what hboot, security on works fine on all hboots, security off seems to be having issues on latest hboot.

mobile post
[One (M7) Original Android Development] raptir:
Well, keep in mind I'm talking about relocking with a LOCKED status, not RELOCKED. In case of a defect or something where I need to exchange the phone under warranty.
[One (M7) Original Android Development] Sneakyghost:
You can still manually achieve that by editing the appropriate partition and then relocking the normal way as long as you're S-OFF.

mobile post
[One (M7) Original Android Development] raptir:
I'm sorry, I don't quite follow what you mean by "the appropriate partition" or "the normal way." Would you be able to provide more detail on that?
[One (M7) Original Android Development] gee2012:
I meant with revone (what we talk about on this thread), not through htcdev off course.
[One (M7) Original Android Development] Sneakyghost:
Yeah I think I can. I just haven't checked what partition it is on the ONE but there is one partition that holds a few bytes only and is empty otherwise, and if you dump that partition, zero out those bytes and then push it back, using the dd method, and then relock afterwards, the phone will think it was never unlocked. It basically is a flag that gets created when you unlock the first time and if you remove it you fool the phone into thinking it was never messed with.

Probably this is what revone does anyway.

mobile post
[One (M7) Original Android Development] raptir:
Alright, so it sounds like I may be able to restore LOCKED status after updating (with S-OFF) but there is no easy tool for it yet so I should still be cautious about accepting an OTA.

Maybe I'll just keep this H-BOOT version and stick to custom ROMs if I want to update.
[One (M7) Original Android Development] carlos67:
Confused?

I thought that the latest hboot 1.54 could allow going s-off through revone as long as you still had root access when running revone. Is this not correct?

I also thought that, as long as you had root, you could unlock the latest hboot with revone without having to go through HTCDev?

Am I wrong about both of these?
[One (M7) Original Android Development] gee2012:
- S-Off not possible atm (for me and probably all users), faillure after ./revone -P showing error -6 with revone 0.2.1/0.2.1-wlj

- Unlock BL don`t know since not getting past ./revone -P

Tried with root on pc with adb and on the phone with terminal emulator since i was allready unlocked.
[One (M7) Original Android Development] jake460:
Sent phone to htc to day to get new digitizer fitted after i dropped it and couldn't get it back to stock, i had 1.44 hboot and went s-on again by mistake before i flashed old firmware back, and revone didnt work for me, cos i updated firmware with the new touch screen drivers, and i can only run 4.2.2, i did flash back to 4.1.2 but no touch screen, so i think revone dosent work on 4.2.2 with updated firmware and not just 1.54 hboot.

Any one else have this problem.
[One (M7) Original Android Development] steljwaxd:
As stated earlier, I did a successful unlock on a s-off 1.54 hboot. I think I can relock and unlock it as long it stays s-off and I must have SU access.
[One (M7) Original Android Development] russel5:
How you do S-OFF on HBOOT 1.54? Please tell us. Ever steps.
[One (M7) Original Android Development] daleski75:
True the issue is with going back to s-on after that it refuses to work no matter what you try and do with it
[One (M7) Original Android Development] tiho5:
Which FW? 2.17 or 2.24?
[One (M7) Original Android Development] jake460:
Think he is on about bootloader unlock
[One (M7) Original Android Development] gee2012:
Could you try wether or not you can get past ./revone -P just to test that and maybe further if you want? That would clarify the issue somehow. And if possible once with and without root.
[One (M7) Original Android Development] steljwaxd:
I can do that this weekend, at this moment I'm not available to a computer. Do you guys think it can be executed without any risks for my hboot ?
[One (M7) Original Android Development] gee2012:
You don`t have to do the whole sequence if you don`t feel comfortable, just past ./revone -P and see what happens and then abort or do ./revone -t.
[One (M7) Original Android Development] LorD ClockaN:
A friend of mine gave me his One to get CID unlocked but it already had 1.54 hboot and I'm getting -6 error..

Can I just downgrade the hboot and do the unlocking with revone??
[One (M7) Original Android Development] gee2012:
If the phone is S-Off you can downgrade Hboot by flashing a 4.1.2 RUU i guess, other wise not i`am afraid.
[One (M7) Original Android Development] LorD ClockaN:
no, it's not...

UFFFFF.. and he bought it so I can unlock it hahahaha

anyone knows if revone team is working on an update??
[One (M7) Original Android Development] gee2012:
Lets hope so, haven`t heard anything yet so far :)
[One (M7) Original Android Development] LorD ClockaN:
well did anyone reported to them?

I doubt they are following all topics on xda...
[One (M7) Original Android Development] gee2012:
No idea, i guess they follow the threads and see the issues reported.
[One (M7) Original Android Development] LorD ClockaN:
I've sent the PM to the OP.. I hope they are on to it
[One (M7) Original Android Development] TubeShaped:
guys I'm afraid I screwed up...

I wanted to return my one because my battery always dies at 50 percent.

I thought it might be a good idea to return everything to its original state before i go to the store.

Mine was S-OFF, SuperCID latest 2.24 firmware with 1.54 hboot.

- I flashed a Stock Rom in CWM. then flash Stock recovery via fast boot

- Then I tried to lock the device with ./revone -l but I learned that I needed SU because of new hboot.

- I flashed CWM again then root tools onto Stock rom.

- I was able to lock with su revone

- I returned to S-ON with fastboot oem writesecureflag 3

- Then it showed locked and S-ON but TAMPERED.

- Also I remembered I forgot to revert from SuperCID to original CID.

- Now I cant seem to S-OFF again, probably because of hboot 1.54

- I can't downgrade via RUU, probably because I'm still SuperCID.

I almost smashed my phone because I went nuts, which would have somehow solved the problem, but I didn't.

Now I really need your help!