yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] EtherealRemnant:
Yes but you have a RUU. Its not so easy for T-Mobile...

Although I did successfully downgrade and S-OFF when the method was posted a few weeks ago. Still running stock right now but don't get cocky with the S-ON and S-OFF - one of these days you might just brick. There is so much that can go wrong with a RUU...... Mostly due to Windows...
[One (M7) Original Android Development] skulldreamz:
I was under the assumption that all gsm ones had the same partition layout? I switched to T-Mobile a few weeks back and the tmo ruu.zip I flashed worked perfect. Except for their coverage is terrible in my opinion and they were charging me $50 for unlimited everything which you can't beat but when my family, friends, job...whoever can't contact you then its not an option. IMHO their service was totally unbearable and I live in Baltimore so you would think it would be decent but hey, were talking about b-more so I understand so I went strait back to ATT and LTE just arrived on my neighborhood so I'm so happy to be back. But your right about always going s-on to s-off to s-on to s-off, but everyone says you can't boot into android os with a eng.hboot and I really found out that was the reason many things were working for me that would just not be feasible for people that were using the one that's floating around. I had mine custom made for me so I use it %100 of the time. Anyway sorry for rambling and being that your another guy that seems to have much wisdom that is telling me to stop what I'm trying to accomplish but I guess I could do that with my evo, one x, vivid, razr..and not chance screwing my baby up. If anyone wants to see a screenshot of me booted into android os with my custom eng.hboot just let me know and I'll be glad to post some because many have doubted me...
[One (M7) Original Android Development] EtherealRemnant:
The partition layout is the same but the CID is not. You can't flash an ATT RUU without SuperCID which requires S-OFF. Someone got ahold of an internal HTC RUU for the older version of the T-Mobile software and leaked it. That's the only reason I have S-OFF right now.

As for ENG HBOOT - why bother in the first place? It isn't necessary like it was on older phones.
[One (M7) Original Android Development] skulldreamz:
I beg to differ because I would rather have a hboot that has 300+ commands just in fastboot than run a hboot that offers none of these. Some of these commands are so powerful, it really humbled me when I saw what this baby can do for you and the sheer talent of individuals and this makes me wonder what else is out there.

I believe that my eng.hboot is the same one the HTC devs use and I believe they have a purpose to use them still so why wouldn't people like us who are just as into deving not need them anymore. I'm not being being rude, just truly curious but maybe you just haven't seen what this hboot can do and if you did you might have a change of opinion?

So in your opinion why are eng.hboots not at all necessary now & as you also say that they used to be necessary, why?

Again not being sarcastic, truly would like to know. I bought my first android phone exactly about a year ago (I'm new to this) so I would love to understand why you feel they are not necessary anymore and please use examples... Thanks
[One (M7) Original Android Development] EtherealRemnant:
What is the point in having all of those commands when you don't need them? I understand the development side of it, I just wouldn't be using it on my daily driver, that's for sure.
[One (M7) Original Android Development] Sloth:
Some of these commands are so powerful,

= VERY dangerous if you don't know what you are doing.
[One (M7) Original Android Development] skulldreamz:
Why not?

---------- Post added at 08:32 PM ---------- Previous post was at 08:23 PM ----------

Oh got ya, basically what I've been doing is just going down the list and look each one up, one at a time. But my hboot is sooooooo solid. Was made for me by someone that is very highly respected in the android community and his job speaks for itself so I'm fine with using it as my daily driver, love it soooooo much. If you guys want I'll post pictures of it, but if no one really cares then I won't bother.. But thanks for letting me know how dangerous it is. Your right, there is some really powerful commands... :)
[One (M7) Original Android Development] cschmitt:
Oh, I so want to see your hboot. Not.
[One (M7) Original Android Development] Ozonethegreat:
Finally got it working

Finally got this working after months of failure.

This is what I did:

Relocked bootloader.

Downgraded to 1.27.531.11 using RUU.

Followed Xboarder's guide on Rootwiki (Downgrade to 1.27.531.8).

Instead of choosing to unlock bootloader (again) and re-rooting the device, I opted to just do revone without root.

Sucess on the first run!

Thanks to all who provided to the information needed to accomplish this.
[One (M7) Original Android Development] MrKaon:
Any hope for HBoot 1.54?

Itching to change CID :angel:
[One (M7) Original Android Development] josteink:
For anyone wondering about if they can/should run revone and what to do when what error-codes pops up...

This thread should have you covered:

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

Edit: Dont forget to donate. There's a VERY SMALL donation link at the bottom of the FP post :)

https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=NQRTG2YL4FPXY
[One (M7) Original Android Development] horsetastic:
Which software version were you on prior to your downgrade to 1.27.531.11?

Just out of interest?

---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------

Thanks for linking my Guide.... OP has been updated with some new info on the -6 error code and Links to downgrade guides
[One (M7) Original Android Development] Ozonethegreat:
I was running InsertCoin 3.4 prior to that. Before I finally got the s-off, I just had an unlocked bootloader.
[One (M7) Original Android Development] shingers5:
just a quick note to say thanks for making this possible...................like others i tried and failed many time. left phone alone for a few hours nad tried again

- not sure if linked but while running command ./revone -P a call came through and it succeeded after 3 previous fails

next to run ./revone -s 0 -u i also failed 3x so i got my mrs to call me just after running command and it worked again!!!!!!!!!!!!!

not sure if the calls caused it but i am now s-off and cid-11111111......................amazing

trick is to keep trying and eventually for some unknown reason it succeeds!

device

HTC One - Orange Uk but factory unlocked

Hboot - 1.44

i wasnt rooted or dev unlocked just a virgin device when running commands

- used revone 0.2.1

thanks gain guys for this!
[One (M7) Original Android Development] horsetastic:
Haha man I need to try this now...... Perhaps this'll be what cracks 1.54 lol
[One (M7) Original Android Development] Theshawty:
try it and report back :D
[One (M7) Original Android Development] horsetastic:
Haha. I can't right now. You should :P
[One (M7) Original Android Development] Theshawty:
Can't right now either. :P
[One (M7) Original Android Development] tdnookhd:
Hi, I'm trying to get back to S-ON. When I try to run fastboot oem writesecureflag 3 it says /system/bin/sh: fastboot: not found

What should I do?
[One (M7) Original Android Development] DeSaint2:
Unless you absolutely have to go back to s-on, don't. Some phones never get security turned on after everything is initially set up. Unless your carrier checks the phone when it is given to you and they have proof it was s-on(or whoever you bought it from) they can't really do anything as long as everything is back to stock and the bootloader says locked with no tampered warning.
[One (M7) Original Android Development] maarawoe:
Lol... Please give me a phone call to crack my 1.54 :D

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] supendal:
It worked after, i don't know, maybe 50th try. This is my 3rd and hardest HTC phone i've s-off'ed. The point is i was not doing anything wrong and did the exactly same procedure when i succeeded. I think it's a matter of luck or timing of something we don't know.

And strangely, i didn't use -t option but however i didn't get "tampered" message in hboot, just "unlocked".

I'm on Hboot 1.44 (May 4 2013), HTC_A48, stock 4.1.2 rom (1.29.401.17)
[One (M7) Original Android Development] iconspiracy:
I got my htc one mini S-OFF but it was really tough! I kept getting the error code 2 but I finally just rebooted and ran s-off command and success! I had to relock my bootloader after though to get me out of the bootloop :P

Still can do everything I need though with s-off and relocked bootloader :)

HTC One Mini

S-OFF
[One (M7) Original Android Development] tdnookhd:
I have to set the phone back to stock in order to send it to HTC. I don't have a carrier, I have the unlocked edition of the phone though so I theoretically wont lose S-OFF capability.
[One (M7) Original Android Development] nkk71:
You will loose s-off capability if they update the firmware, which they probably will do.

But you can send it with s-off because some devices are shipped that way. So it is very hard to trace if you did the s-off or not.

The only thing that would be a giveaway, is if u had unlocked/relocked/tampered in your bootloader.
[One (M7) Original Android Development] BenPope:
Tampered is for S-On with unsigned software.
[One (M7) Original Android Development] DeSaint2:
Tampered is for recovery tampering mostly. There are other things that cause it to appear but mostly only when s-off
[One (M7) Original Android Development] bongie1:
Hey there guys. I already unlocked one HTC One with revone and it worked like a charm. This one has HBOOT 1.54 though so it doesn't work. Is there a way to downgrade the HBOOT version or I just have to wait?
[One (M7) Original Android Development] DeSaint2:
Unfortunately you'll just have to wait. There's no downgrade hack just yet and no released s-off exploit for 1.54.
[One (M7) Original Android Development] maarawoe:
Yeah this sucks... :((

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] rasta312:
I wonder if come out s-off on hboot 1.54 if only for hboot 1.55 with android 4.3

HTC One - Tapatalk 4
[One (M7) Original Android Development] Entry Wounds:
S-Off no longer working.

Hello everyone, I am trying to regain S-Off after having my phone repaired and for some reason its not working like it did the first time which worked like a charm the very first go. I have included pics of my getvar all and the error message I am getting which seems to be pretty common. I have searched XDA and the interwebs high and low and have tried just abut everything with no luck. If anyone has any ideas they would be much appreciated.

Now the phone currently has stock, rooted Sense OS on it. Also the bootloader is unlocked, and have stock 1.44 HBoot.
[One (M7) Original Android Development] Theshawty:
Are you on AT&T by any chance? If so, you cannot S-OFF anymore due to a patch they sent out in various updates. You're gonna have to revert to .7 or similar.
[One (M7) Original Android Development] EtherealRemnant:
Your phone is a UK model, yes?

Strange that it doesn't work with that software version...

Try the old revone 0.2.0 - it seems to work for some people better than 0.2.1 does.

If your carrier has a RUU available that is of a lower version, run that and see if that fixes the revone issue.
[One (M7) Original Android Development] Entry Wounds:
Dang! Turns out all I needed to do was flash an old rom from when the phone came out and use the original rev one file and it worked like a charm. Didn't know that roms had anything to do with it. Thanks for the help guys.
[One (M7) Original Android Development] chong67:
All I did is watch this video and follow the instruction:

http://qbking77.com/development/how-to-gain-s-off-on-the-htc-one-with-revone/

It was so easy. Easier than any HTC device that I have get s-off before.
[One (M7) Original Android Development] Theshawty:
[MENTION=2521652]Spartn[/MENTION] What is the goldcard.img actually used for? I generated one but then what? :p
[One (M7) Original Android Development] Spartn:
"-Go to the the goldcard.img tab and select 'Edit' then 'Select All' then 'Edit' and 'Copy'.

-Now go the you SD card tab and highlight offset 00000000 to 000000170 , and then 'Edit' and 'Paste'

-Lastly goto 'File' and select 'Save'"

for more info, please check this: http://androidforums.com/desire-s-all-things-root/500543-guide-how-create-goldcard.html

btw i thought goldcard does skip checking on phone while flashing IMG.ZIP, seems gold doesn't have such as that feature ;)
[One (M7) Original Android Development] Theshawty:
Thanks. Any luck in your experiments?

>> Sent from the abyss <<
[One (M7) Original Android Development] Spartn:
During the weekend i tried to copy in hex editor lines from signed zip to decrypted one with modified hboot version(but original 1.44, just changed number at the beginning of hboot ), the file passed verification, but got same error hboot old version -no luck

then i put 1.54 original hboot to the decrypted zip and copied lines in hex editor again, but again no luck had error message while verification of zip file....had not enough time to play more, will try again ;)
[One (M7) Original Android Development] horsetastic:
You need to hex modify the other check points and such too i recon....

look for this bit

PN07100008€Þ

h''œT'l>'¸>'TB'$E' V'ŒT'(P'˜S'LW'¬V'*W'TW'\'l\'D$'Ðboard_m7_um7_u

Or something similar.... Use search for PN07, then copy the segments from the 1.54 hboot over to the 1.44 hboot..... There are probably other version checks too.... In android-info.txt there's those numbers in there, they are probably in hboot somewhere too, look for those and copy them across.... I'm excited about the fact you got past the verification.....

---------- Post added at 03:52 PM ---------- Previous post was at 03:20 PM ----------

I've hex edited a 1.44 hboot to show 1.54 at top and updated header/board check stuff...

1.44 hexed

Only thing is I think the text after the hboot version at the top may also need to be copied from 1.54 hboot. Could be a check point....

Let me know if this was useful at all anyways
[One (M7) Original Android Development] exocetdj:
Keep up the good work guys!!! :)
[One (M7) Original Android Development] Theshawty:
This is really awesome. Hopefully this is possible! The fact that you managed to pass verification is amazing.

>> Sent from the abyss <<
[One (M7) Original Android Development] maarawoe:
Fingers crossed.... :)

Btw how about some checksum checks? - is there something like this? it sounds very cheap that it could be possibly tricked by flashing lower version masked like 1.54...

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] horsetastic:
Yeh right.... Hex edited hboot passing verification is a pretty big step. If we could get an enghboot to get through somehow we'd be on to a real winner then. Then we could flash that. Then run a stock RUU then s-off and be free to do whatever we wish really.
[One (M7) Original Android Development] Spartn:
really sorry for giving you hope, all other files same error on verification, seems i had to mix up files and that's why passed verification :(
[One (M7) Original Android Development] Maichel:
Very good news!

Looks like a breakthrough is coming soon! First we had the goldcard stuff and now this. Thumbs up for you guys!

Ofcourse I do not know all details of this changed hboot test but IF this will work than the HTC security is quite easy to "hack" :)

Good luck guys, if I need to test anything please ask!
[One (M7) Original Android Development] Spartn:
sorry guys, please forget of breaking news with signing custom rom...had to mix up files :(
[One (M7) Original Android Development] Theshawty:
But you managed to pass the verification?

>> Sent from the abyss <<
[One (M7) Original Android Development] Spartn:
thought so :( just tried the same and no way, still getting error on verification

edit: it had to be one of original files, no other explanation
[One (M7) Original Android Development] Theshawty:
Aw shucks. :/

>> Sent from the abyss <<
[One (M7) Original Android Development] maarawoe:
Fok.... :(

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] Spartn:
it doesn't mean no way to downgrade for ever, sooner or later someone will come with a way
[One (M7) Original Android Development] dastylee:
there is a way to downgrade i can only tell u the name of the tool but i cant post any like google RUU_Downgrader_1.27.531.11-1.27.531.8 it works like magic...this is all i can say.:cowboy:
[One (M7) Original Android Development] horsetastic:
Only works for T-Mobile and only on patched 1.44 hboot. Please don't just randomly post things that people might think they can use.
[One (M7) Original Android Development] Theshawty:
Yeah, hopefully. I hope I've learned my lesson now.
[One (M7) Original Android Development] AnumEndzeit:
How odd... im on 4.1/ Sense 5.0 stock. Version 1.29.1500.21, model id PN0713000, HBOOT 1.44 and GLOBA001 as cid. Yet i keep getting error code -6 but im not on tmobile. My firmware doesnt even match that of it. My model id matches an international version but the cid doesn't. What am i missing?
[One (M7) Original Android Development] DeSaint2:
What does the date say in bootloader? Should be the last line.
[One (M7) Original Android Development] AnumEndzeit:
It says... Jul 23 2013, 23:01:49:-1
[One (M7) Original Android Development] Theshawty:
The hboot might have been patched. May is the last known good date.

>> Sent from the abyss <<
[One (M7) Original Android Development] horsetastic:
Nice bit of info.... I've updated point No.2 on my guide to add this CLICK HERE AND READ ALL BEFORE S-OFFING (NEWBS ESSPECIALLY!!)
[One (M7) Original Android Development] sinosuke:
You have saved a noob...ME :p

Sent from my HTC One
[One (M7) Original Android Development] AnumEndzeit:
Ah, thank you. How unfortunate, off by a month...
[One (M7) Original Android Development] MrKaon:
Guys I need help.

I was on HB1.54 and got s-off with paid java card service.

Then I've downgraded to HB 1.44

now if I want to flash RUU or recovery it fails all the time:

Writhing 'zip' ... FAILED (remote: not allowed)

Any help please?
[One (M7) Original Android Development] Chezbel:
Is it because your boot loader is locked?
[One (M7) Original Android Development] nkk71:
Sounds like you're using fastboot :confused:

Download and run a full RUU from your PC.
[One (M7) Original Android Development] MrKaon:
Yes I was running fastboot command from my PC trying to flash RUU zip file.

Could you please be more specific how else I can flash RUU?

Thx
[One (M7) Original Android Development] Golv:
How you downgraded to HBOOT 1.44?

You must to use fastboot flash zip <name_zip> twice

without

rebooting. The first time is preloading hboot, the second full load and load other modules ... Attach the log updates here.

Info...
[One (M7) Original Android Development] nkk71:
Download a full RUU in exe format to your PC, then run it as a normal application on Windows.

The RUUs can be found in the stickies, or androidruu.com.

I'm on my phone so don't have the links right now, sorry. But they're easy to find.
[One (M7) Original Android Development] Theshawty:
Aren't RUU zips flashed in the "RebootRUU" mode :p

>> Sent from the abyss <<
[One (M7) Original Android Development] nkk71:
Full RUU (Rom Update Utility) are an executable file from a PC that do contain a zip file amongst other things.

If you're s-off, and SuperCID, it's easier to just run the exe from your PC, and you'll be sure the whole package/phone was updated.

---------- Post added at 07:00 PM ---------- Previous post was at 06:56 PM ----------

You're just teasing me aren't you :rolleyes:
[One (M7) Original Android Development] Golv:
Has anyone tried to downgrade hboot method as for Desire S (edit the firmware version in misc (in HTC One - in block 19), and flashed firmware 1.28.401.7 or RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed? Or is there is a check on the version of HBOOT?
[One (M7) Original Android Development] MrKaon:
It was failing to flash RUU zip even before downgrading HB to 1.44 from 1.54 with same error massage. while I'm at moment on TWRP tried to flash stock recovery but again failed. :mad:

Then I decided to downgrade HB: flashed it once and it said finished while phone was showing 75% then I returned the phone to boot loader mode with command line and it was already showering HB 1.44

I'm not at home now so can't put any log but I will do it tonight.

I haven't tried RUN exe file will try that one as well.

Edit:

Ok while I'm outside and cannot do anything with my PC I've download revone and run two commands -t and -u .

Now bootloader showing unlocked sign.

Will try to flash RUU soon.
[One (M7) Original Android Development] Spartn:
i have tried to..but it failed on hboot version check, tried different ways, nothing worked
[One (M7) Original Android Development] Theshawty:
I'm actually not teasing you. I'm not talking about the executable. In fact, screw the .exe to begin with. What I'm talking about is the "rom.zip" that is inside the RUU executable, that contains EVERYTHING rom related. Rom + firmware etc. That zip can directly be flashed within the RebootRUU mode, just like the .exe does. Only the .exe contains rom.zip plus adb and fastboot files and some other junk like dll's and images and whatnot.
[One (M7) Original Android Development] chuckado:
I used revone several months ago, is there any point in me upgrading to the newest version? Will it gain me anything, how do I perform the upgrade. I am currently running hboot 1.55 on the 3.17.40.12 firmware base. Thank you for your help.
[One (M7) Original Android Development] nkk71:
Fair enough :thumbup:, but wouldnt the RUU (exe) also get past a locked bootloader etc.

Or am I missing something?
[One (M7) Original Android Development] Theshawty:
Since you're not in the fastboot mode, I don't think the state of the bootloader matters.
[One (M7) Original Android Development] tiho5:
Yes it will flash with locked or unlocked bootloader in RUU mode. That's how I do it as I don't like using the exe RUUs
[One (M7) Original Android Development] Theshawty:
I think we'll see revone S-OFF again after 4.3 is out. :p
[One (M7) Original Android Development] Swanseatom:
Why do you think that Theshawty?
[One (M7) Original Android Development] zaphodbeeb:
downgrade to 1.44 boot from 1.54 to use revone?

Hi,

Im s-off, and currently on 1.54 stock. Can I just flash the 1.44 boot and then use revone to lock, or do I have to downgrade to another rom also.
[One (M7) Original Android Development] Theshawty:
I dunno. A lot of it is wishful thinking. :D

Well, revone might work on 4.2.2, but it'll definitely work best on a 4.1 rom.
[One (M7) Original Android Development] krustypick:
Telus in Canada

The first command will not work.

Have done the ./revone -P a thousand times and no luck.

Rebooted 50 times at least and no luck.

Anyone have any ideas?

Richard
[One (M7) Original Android Development] zaphodbeeb:
ruu worked for me after jcard s-off. I had to root and do su before .revone -P, but after that all other functions worked fine.
[One (M7) Original Android Development] sweetrobot:
this did it- went to an aokp 4.2.2 - not one error. thank you. superCID and s-off enabled.
[One (M7) Original Android Development] horsetastic:
Agreed... for maximum success people should read the guide in my signature!
[One (M7) Original Android Development] iconspiracy:
What error code/message do you get when running ./revone -P ?
[One (M7) Original Android Development] horsetastic:
My advice is to read the guide in my signature of what to do/know before trying to S-Off
[One (M7) Original Android Development] krustypick:
revone

I have.

I am tampered and unlocked .

rooted

The phone is in developer mode

moonshine will not work either.

I just keep getting error 1 with the ./revone -P command.

I have tried all 3 versions of revone.

FRUSTRATED