yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] SaHiLzZ:
Tried installing the firmware, didn't work.

fastboot output:

This is the fastboot from a working BELL HTC One:

The only difference in my device seems to be:

INFOversion-baseband: 4A.18.3263.15 vs a bell stock device INFOversion-baseband: 4A.14.3250.13

Searching on 4A.18.3263.15 shows that it is from Google Edition 4.3 RUU which has 1.54 Hboot. I am suspecting that someone just flashed the 1.44 HBOOT on top of it in attempt to revert back?

I am considering using Fonefunshop server for S-off using Javacard, http://www.fonefunshop.co.uk/cable_picker/97585_HTC_One_M7_S-OFF_Service.html, anyone used it?
[One (M7) Original Android Development] horsetastic:
Maybe but if it's a 1.44 hboot then it should be..... Oh god....

Did the moron that sent this borked phone back send it back with a hex edited 1.54 hboot..... if they has had s-off they could have....

that would explain the issues. And explain why bootloader doesn't work.
[One (M7) Original Android Development] SaHiLzZ:
so now there is a htc one 4.3 available for bell edition, which will update bootloader to 1.55 as well as probably update the baseband etc.

I have a choice of either sending it to fonrfunshop or doing the 4.3 update.. no guarentees in either.
[One (M7) Original Android Development] horsetastic:
I'd try to update....

Good luck!
[One (M7) Original Android Development] PillowMetal:
All that command does is set permission to allow the file to be executable after copying it, so I am surprised you were able to even run revone without it.
[One (M7) Original Android Development] SaHiLzZ:
4.3 Update fixed the phone screen!!

Touchscreen is usable now, however bootloader still can

NOT

be unlocked, the bootloader warning splash screen doesn't show up. On startup Google also gets displayed and then HTC, so there is still something weird with this. As you said TWH, it must be a hex modified hboot. I have now lost ability of S-Off, but a usable phone is better than an unusable one.

Thanks for all the support from everyone and thoughts and suggestions!
[One (M7) Original Android Development] horsetastic:
Hey, this is good news.... Can you boot to bootloader now then? Can't you use htcdev to unlock bootloader? I wouldn't worry about the google splash screen as I'm sure that's all it is.... At some point if we can get you unlocked and rooted you might be able to flash a stock HTC splash screen again though.

Oh and no worries man.... For the most part we are all here for the same reasons (or close to) so it's in our interests to help each other if we can. You got shafted by someone else and in my opinion that's not right so if I can help you in any way then I will.... Of course the other guys that helped probably feel the same. Glad you can start to enjoy your epic beast now though :)
[One (M7) Original Android Development] SaHiLzZ:
Yeah htcdev bootloader unlock doesn't bring up the Yea/no screen.

Good enough for now to be on stock. Thanks again!
[One (M7) Original Android Development] horsetastic:
hmmm... did you run through it fresh? Generate new unlock code etc? You'll need a new one with each software version as it changes. Sorry if I'm telling you stuff you already know or have tried.
[One (M7) Original Android Development] Swanseatom:
are these steps referring to using normal ADB through my PC?

2. Open an adb shell and:

* cd /data/local/tmp

* chmod 755 revone

or does it want me to use terminal emulator for example on my phone?
[One (M7) Original Android Development] horsetastic:
There are two methods you can use.... Or even maybe 3 with the last being a variant on the third...

1. Use adb connected to PC. Push revone to phone then adb shell etc etc

2. Copy revone to sdcard then use terminal emulator to dd it to data/local/tmp (you need root for this though) then use terminal emulator for rest of the commands etc

3. Copy revone to sdcard then move it manually using file explorer to data/local/tmp (need root again) then use terminal emulator for the rest....

All should work fine...

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

@SaHiLzZ Did you say the update to 4.3 was an OTA? Sorry I just want to test something that could help you :)
[One (M7) Original Android Development] :
Me too. Thanks for the clarification.
[One (M7) Original Android Development] stoned99:
I'm in the same boat as you, even though it says it was successfully flash missing shows up on my htc screen
[One (M7) Original Android Development] SaHiLzZ:
Hi,

Yes it was the 4.3 OTA update release to bell Canada OS.
[One (M7) Original Android Development] horsetastic:
OK, I'll have a think and get back to you :) fingers crossed...
[One (M7) Original Android Development] SaHiLzZ:
Awesome!
[One (M7) Original Android Development] iElvis:
That explains the splash screens. The OTA likely just patched this and that, and didn't replace your splash screen.

But you have a new bootloader, and you could not be running be running a modified hboot with s-on. You would be bricked in that case because it would fail the signature check at boot.

I would do as War Horse suggests and start the htcdev unlock all over and see what happens.
[One (M7) Original Android Development] ricebus:
This is what I'm getting on my T-Mobile HTC One when trying to do this... my hboot is 1.44 and i'm running on android 4.1.2
[One (M7) Original Android Development] EtherealRemnant:
You have the .11 software version. Back up everything on your phone you want to keep to your computer and follow this guide.

http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318/

Sent from my HTC One
[One (M7) Original Android Development] ricebus:
thanks, but aruwizard.exe won't run for some reason... you have any idea why? i'm runnning win8

i can't find any manual guide to do this with faseboot/adb
[One (M7) Original Android Development] EtherealRemnant:
It worked for me on Windows 8. Right click and run as administrator after making sure that you have disabled all security software on your computer.

It pulls right up to the RUU GUI for me on W8 Pro 64-bit. Are you getting an error or what?

You can use fastboot oem rebootRUU and try to flash Rom.zip with fastboot flash zip rom.zip - it will fail, just run the command again. Does the same thing the RUU exe does.

Sent from my HTC One
[One (M7) Original Android Development] ricebus:
it just fails twice...

btw i managed to open the rom upgrade utility but it still wont work

just stalls at "verifying information on your android phone. please wait..."

and the device doesnt even go to fastboot/bootloader mode
[One (M7) Original Android Development] EtherealRemnant:
Have you tried reinstalling the drivers and do you have HTC Sync installed because Sync can wreak havoc like no other.

Also, since fastboot is connecting, just try running the RUU when you are already in fastboot oem rebootRUU. It should work just fine from there.

Sent from my HTC One
[One (M7) Original Android Development] Swanseatom:
So i got my phone back from funfoneshope today s-off.

They had S-off > Super CID > run the earliest available open europe RUU.

But they HADN'T OTA'd back to 4.2.2/hboot 1.54.

So after much reading i decided best thing to do was S-ON whilst on Hboot 1.44 and then use revone to s-off etc.

All went perfect not one error.

However now i have update myself to 4.2.2 and Hboot 1.54. Revone seems to have disapeared?

As in i cannot execute any of its commands.

shell@android:/data/local/tmp $ ./revone -l

./revone -l

/system/bin/sh: ./revone: not found

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

Is this normal?

Am i missing something simple?

I was under the impression that revone stays after you OTA, or is it just S-OFF that stays and revone goes?

If so can i push revone back just for the lock function now i am S-off / hboot 1.54 or would i need to RUU back to 1.44 and lock it then.

Thinking ive missed something simple along the way.
[One (M7) Original Android Development] EtherealRemnant:
You're S-OFF until you S-ON again, which isn't recommended. revone itself is just a temporary executable on the phone and isn't needed. Just keep the binary on your computer in case you need it in the future.
[One (M7) Original Android Development] Swanseatom:
Ahh right so if i wanted to return to Locked in bootloader i would need to downgrade Hboot to 1.44 then use revone accordingly?
[One (M7) Original Android Development] EtherealRemnant:
I don't know why you would want to lock your bootloader since there isn't really any harm in having it unlocked but you can lock it on any hboot. The only thing you can't do with higher hboots is obtain S-OFF with revone. At least as far as I know - I wouldn't risk trying to lock it on a higher hboot personally. You never know - things go wrong.
[One (M7) Original Android Development] Swanseatom:
I understand all about being unlocked etc.

My question was purely for IF i ever need to return to HTC and want it to look like never unlocked.

Locking and unlocking on hboot1.54 is no issue atall whilst keeping s-off nothing would go wrong.

But it would show relocked.

Hence my question.

Either way my confusion was over revone only being temporary.

All clear now.
[One (M7) Original Android Development] EtherealRemnant:
It works for that purpose. And if it doesn't, you can just downgrade the hboot. S-OFF is grand ;)
[One (M7) Original Android Development] ricebus:
thanks for the advice, i uninstalled htc sync and reinstalled the latest htcdrive 4.2 but windows wont recognize my device... i'm using the same cable and hardware on my mac and fastboot works. any suggestions?

edit: my bootloader is htcdev unlocked, is this fine?

edit2: well, the fastboot problem appears to be something related to my computer drivers (win8 + usb3)

and the flashing problem with the mac appears to be related to the bootloader being unlocked.

when i locked it again it worked!

thanks alot man, appreciate it!

---------- Post added at 01:35 AM ---------- Previous post was at 12:49 AM ----------

this is the message i'm getting when running ./revone -P

---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------

this is the message i'm getting when running ./revone -P
[One (M7) Original Android Development] chevymusclecar:
Don't you need to use su command first....
[One (M7) Original Android Development] :
I too am having the exact same roblem. Not sure where to go from this point, does yours also not tell you to reboot either even though it says successful? I have the 32GB on sprint
[One (M7) Original Android Development] descenpet:
you can't proceed if ./revone -P failed. it will not work of course.

did you retry that step? some people had to retry multiple times.
[One (M7) Original Android Development] lumbu:
I see your signature says CM 10.1, I couldn't get it working on Rootbox, had to flash Revolution (though Im guessing any Sense based ROM will do) and then got it to work right away.
[One (M7) Original Android Development] chakra:
Correct, this is not the same. This will not wipe anything.
[One (M7) Original Android Development] gray10k:
worked perfect on at&t 64gb htc one with trickdroid rom...perfect on first try!
[One (M7) Original Android Development] Elin28:
follow the instruction, s-off under 5 minutes, thank you!!! (Rogers HTC ONE)
[One (M7) Original Android Development] Garmig:
I was having problems too after SUPERCID. I have missed calls on my T-Mobile US.

So I've rewrite the TMO CID:

fastboot oem writecid T-MOB010
[One (M7) Original Android Development] pauley:
I was curious which data icons I'd get on Trickdroid 7 / 2.17.401.1 / 4.2.2. It makes them the standard looking GSM ones in case anyone was wondering. I am going back to 11111111 now because that left them as the AT&T 4G style.

Next up is flashing the new 1.29.1540.16 Developer Edition RUU or can I just do the .zip instead? I want to make sure I have the newest touchscreen & wifi driver img's since those are typically uploaded for flashing.
[One (M7) Original Android Development] clsA:
Took 2 tries, but got it - AT&T 32gb

Huge Thanks to everyone involved
[One (M7) Original Android Development] wzu7:
pls what this mean acctually ?

uninstall htc syn also not working ! now my usb (one) only connect to the phone already, no other devices...

what is something relate to this ?...thanks
[One (M7) Original Android Development] Riyal:
[MENTION=1188543]Baste[/MENTION]

./revone -s 3 -l

being

-s 3 = Return to S-On

-l = Return your bootloader status to Locked.

Take not of the warning though...

Due to a few requests, this is how to reset your device to S-ON (completely not recommended/supported):-
[One (M7) Original Android Development] :
yeah my signature is old, that was the rom i was running when my phone mysteriously killed itself in the middle of the night last sunday. see here http://xdaforums.com/showthread.php?t=2310750 currently I am stock rooted/unlocked through the dev site.
[One (M7) Original Android Development] Riyal:
Hi! I may be familiar with alot of things but not with HTC's stuff.

So I would like to ask... If I S-Off my device do I still need to relock my bootloader to flash RUU or I can flash it even with unlocked status?
[One (M7) Original Android Development] baste07:
Thanks! Any risks going back to s-on? Keep unlocked

from my incredible mobile
[One (M7) Original Android Development] mistoffelees:
Success

Took several tries, kept reporting success but would when I went into bootloader again it still showed S-ON. Finally switched from the USB cable I was using to the cable it came with and to a different USB port. BAM everything worked on the first try, S-OFF and Tamper gone. 64GB Dev Edition. Great work devs, thanks for the tips.
[One (M7) Original Android Development] surge27:
Thanks to Rev team!

Very simple...

Note: I was on a 4.1.2 rom. TrickDroid 5.5
[One (M7) Original Android Development] Riyal:
Not sure if there's any risk... Probably the reason why it's not supported/recommended is because they haven't tested it yet. It's an alpha anyways so it's understandable.

---------- Post added at 10:49 AM ---------- Previous post was at 10:48 AM ----------

Hi guys! To reduce risks of failure make sure to check the md5 of revone..

MD5: 08EC1439ADE5DB3F46C5D225312D2025
[One (M7) Original Android Development] Star2dn:
Works perfectly

Great Job

Thanks a bunch!

Sprint HTC One

Sporting:

MacksRom "Dark Horse 3.0"

OC/w Badass Kernel oc2.1

Loving It..
[One (M7) Original Android Development] :
Yeah it was definitely the usb cable/port changed both out and voila.
[One (M7) Original Android Development] ~~Tito~~:
4th time's the charm! lol No more tampered flag either. Does anyone know how to remove the message on the splash screen?
[One (M7) Original Android Development] EtherealRemnant:
Something odd is going on. I downgraded to .8 and revone worked the first try. I was not rooted or anything. Maybe someone else has an idea as to what is happening.

Sent from my HTC One
[One (M7) Original Android Development] ricebus:
EDIT: okay... after a few dozen times... it worked.. i guess its based on luck :p

thanks for all the help! especially EtheralRemnant..
[One (M7) Original Android Development] horsetastic:
Luck does come in to it I think actually. I think almost every device must react slightly differently to the exploit for some reason. It's bazaar.
[One (M7) Original Android Development] BenPope:
Yeah, I tried quite a few times and it wouldn't work. Even worked with the dev to improve error messages, so at least one of us knew what we were doing!

As soon as I tried the restart by holding power it worked first time.
[One (M7) Original Android Development] athiskir:
Hi ieftm!

I used revone to S-Off my Dev Ed One about three months ago and it has been smooth sailing ever since. Now I'm looking to put it back on S-On and flash the 4.3 RUU.

I tried both the secureflag fastboot command and revone but I can't seem to return to S-On. Any idea how I can get this done?

Sent from my HTC One
[One (M7) Original Android Development] ParanormalBat:
NEVER GO BACK TO S-ON!

You should be able to find an unsigned 4.3 OTA for S-OFF devices
[One (M7) Original Android Development] athiskir:
Why wouldn't I want to go back to S-On? There's nothing wrong in returning to full stock without root when you're handing over the phone to someone else right?
[One (M7) Original Android Development] InfinitiGuy:
Just so I'm clear on the terminology. Does locking your bootloader mean going back to S-on or is it something different? How exactly do you lock your bootloader if you are unlocked?
[One (M7) Original Android Development] athiskir:
No, locking or unlocking your bootloader is not S-Off or S-On.

You relock your bootloader by running fastboot OEM lock. The 'unlock' lets you flash system and recovery files while S-Off lets you mess with everything, without restrictions.

Every HTC phone ships with S-On and a LOCKED bootloader, except the Dev Ed.

Thing is, S-Off and S-On are a HTC only pain.
[One (M7) Original Android Development] InfinitiGuy:
Thanks. I just wanted to make sure. After reading so many threads it seems some could be mixing up the 2 terms.
[One (M7) Original Android Development] athiskir:
Yeah, they're frequently confused.

Now does anyone know how to S-On?
[One (M7) Original Android Development] DeSaint2:
Just leave it s-off and run the Ruu to 4.1.2 Rom and use revone to lock(so bl slows locked not relocked). Some phones are shipped s-off from HTC. It is never a good idea to s-on if you are s-off. Even after running a Ruu.
[One (M7) Original Android Development] athiskir:
Alright, but I'm good. I reinstalled adb drivers and used fastboot to S-On. Bootloader is unlocked (as a developer edition phone should be) and now I'm just going to flash the RUU.
[One (M7) Original Android Development] Theshawty:
You should have run the RUU while being S-OFF.

>> Sent from the abyss <<
[One (M7) Original Android Development] horsetastic:
Why did you S-ON?
[One (M7) Original Android Development] athiskir:
Because I'm handing over the phone to someone else. Now I reconsidering, maybe I should run the RUU then try S-On.
[One (M7) Original Android Development] Theshawty:
Doesn't the dev edition come S-OFF anyways?

>> Sent from the abyss <<
[One (M7) Original Android Development] EtherealRemnant:
I hope whoever you hand it to doesn't want to have S-OFF or you're on the exploitable hboot (original 1.44). There is a reason we say to never S-ON a phone once it has been S-OFF'ed.

---------- Post added at 08:19 AM ---------- Previous post was at 08:16 AM ----------

Not that I'm aware of. There are a lot of people who have the Dev Edition who still have to S-OFF.
[One (M7) Original Android Development] guyd:
Correct. The Dev Edition comes SIM unlocked and Bootloader unlocked. You have to run the exploit to make it s-off.
[One (M7) Original Android Development] skulldreamz:
Official HTC 4.1.2 ruus were just posted ( 6 posted-2 Europe, 2 Asian, 1tawaneise n forgot the other ) :)
[One (M7) Original Android Development] athiskir:
But then again if a device with S-Off he would have issues with warranty right? That's why I wanted to S-On.
[One (M7) Original Android Development] skulldreamz:
No, you can make your bootloader say locked if your s-off and make your phone say s-on when its really not if you wanted to
[One (M7) Original Android Development] Theshawty:
Now they need to post 4.2.2 ones :p

Are these ruus posted at htcdev?

>> Sent from the abyss <<
[One (M7) Original Android Development] skulldreamz:
Not sure but there posted here on xda and it says their official (not ruu zip ) so I'm guessing on the guy got them from htcdev but not 100% :)
[One (M7) Original Android Development] DeSaint2:
Repair centers know that some phones are shipped s-off and if it is completely stock they can't know that you made it s-off. If they try to say otherwise you just play dumb to the matter. Plenty of people get repairs done under warranty with s-off
[One (M7) Original Android Development] Theshawty:
Do these differ from the ones we've had up for a good few months?

Maybe these will let us downgrade the hboot haha. Stupid idea I know but hey :p

>> Sent from the abyss <<
[One (M7) Original Android Development] skulldreamz:
No t hats why I posted :) if your cid & mid match you can downgrade. That's what a official ruu is for ;)

---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------

I don't want to give false hope. I'm already s-off. I'm just happy they released official ruus for everyone who is not s-off. :)
[One (M7) Original Android Development] Theshawty:
So what are those ruus we've had before? :eek:

Would be awesome if these ruus could downgrade the hboot for an s-on user but that seems farfetched haha

>> Sent from the abyss <<
[One (M7) Original Android Development] skulldreamz:
To be honest I'm not sure whats the difference but I hope it works for you...I'm confused to but wanted to let you guys know in case it helped :)

---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------

The post is under HTC one General
[One (M7) Original Android Development] Theshawty:
I can't actually find any of these supposed official RUU's on htcdev.
[One (M7) Original Android Development] skulldreamz:
How do I upload a screenshot from the xda phone app? I took a screenshot of the op so you can see...
[One (M7) Original Android Development] Theshawty:
Dunno, I use tapa. Try http://imgur.com/
[One (M7) Original Android Development] iElvis:
Because going back to s-on after you've modded your phone is potentially dangerous. I have seen many people lock their phones into an unstable configuration because they didn't go back to stock correctly or missed a step. You may have done it by going s-on before running the RUU. You needed to run the RUU first. If you must do it, going to s-on should be the last thing you do once the phone has been returned to out-of-the-box stock.

Even if you think you're back to bone stock, there can be potential problems if some software gremlin doesn't do what it's supposed to when you run the RUU.

S-off really should be a one-way trip.
[One (M7) Original Android Development] athiskir:
Then again I'm back on S-Off and RUU'd so I guess it's all fine now.
[One (M7) Original Android Development] lauri_ylonen:
thnaks

can i s_off desire v hboot 1.14.002 with this method??

thans
[One (M7) Original Android Development] Jump1ng:
This is for the HTC ONE so NO. Look in the appropriate forum if there is s-off for your phone.
[One (M7) Original Android Development] horsetastic:
edit ^^^^ what he said lol
[One (M7) Original Android Development] InfinitiGuy:
I'm in the process of resetting my phone to stock for warranty. I'm current'y on my original stock ROM and stock firmware (1.29 & Hboot 1.44). I have s-off and I'm trying to get to a 'Locked' state. I used revone with the '-r' and '-t' options but I can only get it to "Relocked" state. Is there another parameter to make it say "Locked"?
[One (M7) Original Android Development] Gerton:
U have to use -l

Here it is from OP:

6a. Other optional command arguments:-

* -u - Unlock the device

* -l - Lock the device (as if it was never unlocked)

* -r - Relock the device (mark the device as relocked)

* -t - Reset the device's tamper flag.
[One (M7) Original Android Development] InfinitiGuy:
Won't "-l" make the device s-on?
[One (M7) Original Android Development] Gerton:
No it doesn't. It only set device as locked but still s-off. S-on has to do by fastboot command something like:

fastboot write secureflag and then a number.
[One (M7) Original Android Development] InfinitiGuy:
Thanks. I just used "-l" and that did the trick and it now shows up as Locked. I was a bit paranoid to lose s-off so I wanted to be 100% sure.
[One (M7) Original Android Development] lauri_ylonen:
please help me

http://xdaforums.com/showthread.php?t=2468847
[One (M7) Original Android Development] InfinitiGuy:
Sorry but I have no experience with the HTC Desire in that thread.