yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] PillowMetal:
Thank you, that thread answers my question. They are indeed flashing with the "adb shell dd" command. Although they are flashing mmcblk31 which on my phone is the "reserve" partition. The "radio" partition for me is mmcblk33, and the "radio_config" partition is mmcblk17. One should probably be careful which partition one is flashing ;)

But that is good to know that you can now flash these sacred partitions with S-ON.

---------- Post added at 01:15 AM ---------- Previous post was at 12:53 AM ----------

Could you tell me specifically what method you accidentally used to flash mmcblk0p3?

a) fasboot oem rebootRUU followed by a fastboot flash zip <something.zip> that contained a "pg1fs.img" file

b) adb shell dd if=<something.img> of=/dev/block/mmcblk0p3

c) fastboot flash <partition_name> <p3_image>.img

d) something else

This is important to know, because I am always on the lookout when new OTA firmware.zip files or RUUs arrive that may contain a "pg1fs.img" file and convert us from S-OFF to S-ON (which would fall under option a in an RUU or option b in an OTA updater_script).

I have documented previously why I think this would be very unwise for HTC to do (mainly because of the potential for people to brick their phones as they are converted to S-ON while having custom bootloaders, hboot, or recovery), but it is entirely possible then depending on your answer. Although, I have never seen or heard of this happening; except when someone intentionally, or admittingly drunkedly :eek:, flashes that partition.
[One (M7) Original Android Development] EtherealRemnant:
Maybe the developers are waiting on the Verizon version to be released so HTC can't plug up any new exploit and bone Verizon users. Verizon is traditionally the worst with locked phones. Last I checked they still don't have a SIM Unlock for the MAXX even... It will not utilize US networks besides Verizon.

I proposed a fake goldcard option and got shot down but a properly coded linux driver could theoretically simulate an SD card as long as HTC hasn't coded for the lack of one (which honestly is pretty likely that they have). Besides, goldcards still required keys.
[One (M7) Original Android Development] AirforcProductions:
Sad Face :(

Got my HTC One from XDA-DevCon and it already had the .11 build on it :(((( hopefully the revolutionary guys figure out a new exploit! I believe in them since I had my Sensation which they got me s-off!
[One (M7) Original Android Development] MICH_**:
Is it right that i cant remove the tampred flag without s-off? And cant change relocked to locked?

I am on hboot 1.54, so i am not able to achieve s-off now :/ Or is there any way to downgrade hboot?
[One (M7) Original Android Development] sp5it:
Must be s-off to downgrade.
[One (M7) Original Android Development] MICH_**:
perfect :rolleyes:

Will there ever be a s-off for 1.54 or is this not possible?
[One (M7) Original Android Development] Theshawty:
We can't say.
[One (M7) Original Android Development] sp5it:
You have to ask fairy.

Mike
[One (M7) Original Android Development] MICH_**:
Who is fairy? :eek:
[One (M7) Original Android Development] sp5it:
Ich schrieb über Fee

Mike
[One (M7) Original Android Development] Theshawty:
English please.
[One (M7) Original Android Development] sp5it:
http://xdaforums.com/showpost.php?p=44708437&postcount=4818
[One (M7) Original Android Development] schn1tt3r:
Hey guys HTC One Developer here (1.29 firmware latest), I am on ARHD 12.2 ROM. I didnt ROOT the phone because ARHD ROM gives you ROOT access (at least while the OS is up).

Should I restore back to stock RUU before doing this?

To get S-Off do I need to root through the conventional method or is it ok just with ARHD installed??
[One (M7) Original Android Development] tiho5:
As you're on 1.29 firmware your hboot must be 1.44 so try like this. It should work.

Even better you're rooted. You also must be on stock kernel, which is also a plus. ARHD is close to stock, so again a plus. Good luck!
[One (M7) Original Android Development] leohdz148:
Hey guys,

I had the stock locked rom and updated so it was updated to .11 then I unlocked bootloader and flashed viper rom 2.0 and am currently on 2.1.0...can I still s-off my hboot is 1.44.000 I checked it on bootloader... Or do you have to have a stock rom to achieve this...plus I saw a video on youtube that they used terminal on the phone and downloaded revone and they achieved s-off that way...can I do this while I'm on viperone or is there a stock rom that needs to be used? Just want to be sure about what might be needed to do something like this

Sent from my ViperOne
[One (M7) Original Android Development] Theshawty:
Not possible, methinks. The .11 update patched something.
[One (M7) Original Android Development] leohdz148:
Ok...gotcha... Thanks for the info, will wait whenever you guys find a way around this

Sent from my ViperOne
[One (M7) Original Android Development] spaboleo:
Hm :(

were my thoughts too far from reality? :angel:
[One (M7) Original Android Development] Theshawty:
I'm waiting as well but a little info on the current progress wouldn't hurt. I'd at least want to know if it's at all possible to S-OFF now.

---------- Post added at 01:19 AM ---------- Previous post was at 01:13 AM ----------

Thought 1-2: Maybe possible?

Thought 3: Wouldn't that require opening the device?

Thought 4: HTC can flash hboot and stuff with their private signing keys. They're more secured than fort Knox though.

Thought 5: Doesn't sound like that'd be of use.

I'm no developer though.
[One (M7) Original Android Development] EtherealRemnant:
As far as the T-Mobile .11 and AT&T .16 updates, has anyone pulled all of the partition blocks and done a comparison with the same .8 blocks? It could at least point out what changed, especially taking the results from .11/.8 and further comparing with at&t's update since it is pretty likely the change is the same on both of them. Same hardware, same exact phone.

It would be tedious but it could yield some promising results. I don't see HTC patching it with different code - that just gives away two patches for hackers to figure out.

It might be worth it to look at Sprint's too although the hardware isn't the same.

All three are on 1.44 hboot - just throwing it out there.
[One (M7) Original Android Development] Theshawty:
IIRC, the hboot version doesn't really matter in terms of gaining S-OFF. For example, the security flag data is stored in mmcblk0p3.
[One (M7) Original Android Development] AirforcProductions:
A wise developer once told me, "Anything that has been secured can then become unsecured"... Unfortunately I am not talented enough to do this :( but if history proves correct...the revolutionary guys will come through.
[One (M7) Original Android Development] EtherealRemnant:
Right but if the hboot hasn't changed in version then they patched something somewhere. It was mentioned that the hboot version number wasn't updated but is different - what about running a diff on the three hboots and seeing what was changed? It might be something that could be easy to work around to regain access to exploit for S-OFF. Like a byte moved somewhere else in the code that just needs to have the address fixed in revone.

I'm grasping at straws but there are devices that still don't have a working S-OFF like the HOX+ last I heard after an HTC patch so throwing out ideas and trying to think out of the box might lead to a combination of ideas that turn out a working solution.

Unless something changed, they still don't have S-OFF on a number of HTC devices and nobody has ever figured out how to fully bypass security on OMAP4 devices either. Eventually anything can be cracked but by the time some exploits are able to be found, everyone has moved on to another device. I'm hopeful that doesn't happen here - if it does though, I will trade in my non-tampered HTC One in 5 months through JUMP and never get another HTC device again. T-Mobile will be checking the bootloader for signs of tampering. If it says unlocked or relocked or tampered, you will have to pay your insurance deductible if you want a new phone. I confirmed this with 3 stores.

I can live without root - Carbon (i think it's called Helium now) allows me to backup and restore apps including app data, I don't need a tethering hack because I have 500MB of tethering included in my data plan, and I'm pretty happy with the performance out of the box. I really just would like to get much more timely updates and be able to have full control over my phone. I paid for it!
[One (M7) Original Android Development] AirforcProductions:
I have had multiple HTC devices. My third one being the Sensation which was one of the first devices to come with HTC's locked bootloader. Revolutionary created the first exploit that got the Sensation s-off in fact I believe they later found multiple new exploits as HTC/T-mobile patched the old ones. Also HTCDev unlocks does work although you can't mess with the radio firmware or the kernel.
[One (M7) Original Android Development] EtherealRemnant:
Yeah I had the Sensation on launch day. Yay S-OFF was fun on that one.

As for HTCDev - yes, of course it works - but without S-OFF you can't hide the fact it was unlocked.
[One (M7) Original Android Development] SaHiLzZ:
This is in relation to: http://xdaforums.com/showthread.php?t=2406407

Any help with this?
[One (M7) Original Android Development] grim489:
I get the -6 error on my tmobile HTC one that was updated to .11, maybe it has been patched whatever happened to it.
[One (M7) Original Android Development] hypocritelecteur:
So if I've moved from the stock TMO ROM there's no way to RUU? If thats not the case then I am missing something!
[One (M7) Original Android Development] EtherealRemnant:
T-Mobile US doesn't have a RUU unfortunately.
[One (M7) Original Android Development] hypocritelecteur:
What I don't understand is the incentive on T-MO and HTC's end to thwart customization? What's the margin? Seems like a waste of time, money, and talent, but I'm sure they have a very smart and well paid duder that has provided an objective and measurable savings in something. At least, I'd hope there's a reason like that, a reason other than a boot stamping on our face forever just for the hell of it.
[One (M7) Original Android Development] EtherealRemnant:
Probably because of how free HTC has actually made this device with S-ON as it is and to minimize stupid people bricking their phones and also so they can force you to unlock through HTCDev so they have a record. It is only possible to hide what you've done to the phone when you have S-OFF.

I think the large reason though is because HTC doesn't want people turning their Ones into Google Edition devices and T-Mobile doesn't want to cover phones that have been tampered with under warranty, especially with the launch of the JUMP program.

Or it could be that AT&T wanted it so HTC packaged it for T-Mobile's radio update while they were at it.

As for the lack of a RUU - that perplexes me. I had to use at&ts RUU on SuperCID and then replace the radio with the latest T-Mobile version when I relocked mine and sent it in for warranty exchange. It was a nightmare.
[One (M7) Original Android Development] theunknowner:
Because the carriers have an 'agreement' to push bloatware on the phones they sell.
[One (M7) Original Android Development] hypocritelecteur:
So wait--there is a way to force revert to stock via ATT RUU? Or am I misunderstanding? Apologies if this is basic stuff-I come from nexusland where the grass is green and the sun is always shining.
[One (M7) Original Android Development] EtherealRemnant:
Yeah but if that was the case, HTC wouldn't allow us to unlock and root to remove that bloatware.

It will be interesting to see what happens with the Verizon release though.

---------- Post added at 12:45 AM ---------- Previous post was at 12:42 AM ----------

If you have S-OFF and SuperCID, it's the easiest way to restore firmware changes. I had done the 1.54 firmware update and a number of things.

Then you have to flash either a nandroid of .7 or .8 or install a stock unrooted ROM in a custom recovery. Its a really stupid thing. I don't see why every other carrier has a damn RUU.
[One (M7) Original Android Development] gutbomb:
T-mobile has one now too for .11.
[One (M7) Original Android Development] Johnny424:
Not to get off topic but the juopunut bear s-off for the evo 3d I had was no where near as easy as the revone procedure..we had to preform the wire trick to gain s-off. And boy oh boy did a lot of people jack their phones up lol
[One (M7) Original Android Development] jgeorge15:
The .11 RUU patches the S-Off method. So its a bummer. They never released a RUU for the original stock .7 which would of been amazing for us but unfortunately they don't want us S-Off
[One (M7) Original Android Development] Theshawty:
Stupid that they think it's their decision. Our phones, we should be able to do what the hell we want with them. They're no iphones, lol.
[One (M7) Original Android Development] jgeorge15:
Yeah and the worst part is that the replacements that both T-Mobile and HTC give all come with the .11 update, I'm very disappointed with the both of them.
[One (M7) Original Android Development] DeSaint2:
The problem with that attitude is ,for example, you go buy a car and decide to chip it. Something goes wrong with it? Dealer won't honor warranty because you modified the engine and programming. You can't exactly revert that in a way that they can't tell. With smartphones, you can. Or at least it is a lot more difficult to tell. Nobody would make money if they let everyone do whatever they want to with their phones. They would be spending it all on warranty replacements. So measures are put into place to keep them from screwing the company over because of their idiocy and selfishness. Granted they should allow downgrading of firmware via Ruu that's the only thing left imo for them to allow us to do.
[One (M7) Original Android Development] Theshawty:
That is not what I'm saying. I mean we should be allowed to do whatever we want with our stuff on our own risk. If we break it and it broke because of what we did, it's on us.
[One (M7) Original Android Development] monkeypaws:
But it's not. How many times have you seen a thread about people lying to their carrier to get a warranty exchange or rma ?Even if it was their fault? Instead of going through their insurance people lie and get a replacement when they bricked their device.
[One (M7) Original Android Development] Theshawty:
Fair enough.

I'm glad I always buy my phones completely free of carrier interference then.
[One (M7) Original Android Development] hypocritelecteur:
They would definitely still make money in great big bales.

These are dystopian nightmare megacorps we're talking about. They are making obscene amounts of money. Obscene like firing a rifle in the air and whooping while balls deep in a bent-over patron.
[One (M7) Original Android Development] c5satellite2:
In the US they still must honor your warranty unless they can PROVE BEYOND A RESONABLE DOUBT that the modification directly caused the failure. Know your rights.
[One (M7) Original Android Development] sagarsamtani:
My htc one is S-OFF with Locked status,... Now to install TWRP ,should i unlock the bootloader or just S-off is enough?
[One (M7) Original Android Development] leohdz148:
You need to unlock your bootloader to install twrp, s-off is just to mess with partitions on your phone and flash firmware

Sent from my ViperOne
[One (M7) Original Android Development] DeSaint2:
I do know my rights and an aware of that but even still. There are plenty of con artists out there that can lie through their teeth and get away with doing stupid things. HTC already allows us to do more than Apple ever would even think of and still even more than some of the android oems. HTC has a right to try and prevent loss of profit by making it difficult for people to do stupid stuff. Should they make it impossible? No.
[One (M7) Original Android Development] sagarsamtani:
And to do that i have to run the command "./revone -u

Am i right?
[One (M7) Original Android Development] bkosh84:
Okay, I've been trying to get this to work last night and today and keep running into the same issues..

Here's what I have:

AT&T HTC One with CleanROM 5.0.0 with stock kernel

Firmware is updated to latest AT&T .15 firmware

HBOOT 1.44

TWRP (If that matter, which I don't think it does..)

When I boot into Fastboot it shows at the top **TAMPERED** and **UNLOCKED**

-Now when I go through the command line, after I type ./revone -P I get a Error -6

-When I go through the command line, after I type ./revone -p I get an error that says -p isn't a command then it tells me that it was successful?

-When I go to step 5 and perform ./revone -s 0 -u it gives me an Error -2

So I'm pretty much stumped on how to proceed because I don't know where to go from here.. I tried searching the thread but nothing seems to be helpful to me in this situation.. Any ideas? Is it because of my firmware version?
[One (M7) Original Android Development] DeSaint2:
The latest firmware(which I think is .15) patched the exploit. For the time being you're sol. Until someone finds a new exploit you won't be able to s-off. Sry man.
[One (M7) Original Android Development] monkeypaws:
Sorry. I wasn't directly or in any way attacking you. Just stating I've read it mention that people have admitted to doing this. I will only run thebwarranty exchange it it's a manufacting . I do agree with you that manufacturers should allow us freedoms . Android is open after all. I hate this bootloader abd s off crap. Prior to owning this phone I've used Samsung phones. I've mentioned this a few times before. Samsung makes it so it's easy to return to 100% stock. No one will know it was modified. In one simple step . No dealing with bootloaders or s off. There are Rom flash counters but there is a simple way around that . And no hboots to deal with ?
[One (M7) Original Android Development] leohdz148:
No to unlock your bootloader you need the all in one kit in the development thread to unlock it, this is for s-off I believe. But you will need the all in one kit.. follow the instructions and you will be fine

Sent from my ViperOne
[One (M7) Original Android Development] dborgo:
You need to look at the date of your hboot. If anything later than May I think it is, you have the updated hboot that has been patched and will not allow you to s-off (old and new hboot are both 1.44 but the date changed to July I believe). You can follow this procedure though to downgrade and then obtain s-off (http://xdaforums.com/showthread.php?t=2394155). It worked for me with some persistence after I had mistakenly taken the OTA AT&T update while running stock ROM.
[One (M7) Original Android Development] TabascoJoe:
How do you find the date of your hboot?
[One (M7) Original Android Development] Tabtoub:
On your bootloader screen, you have the date, the last line of the green text
[One (M7) Original Android Development] bkosh84:
Thanks guys.. That's what I figured after researching after posting.. Don't know if downgrading is worth getting S-Off ATM so we'll see.

When you boot into Fastboot/Recovery (Power+Volume Down Key) look at the date below eMMC-boot.. That's the date that will tell you if you can perform S-Off or not. See dborgo's post above for the date you need to have to be able to get S-Off...

My date is July 5th, 2013 so that means I need to unroot/downgrade via RUU back to .12 (I believe that one is dated sometime in May) to be able to get S-Off.. Now I just need to decide if it's worth it, lol.
[One (M7) Original Android Development] dborgo:
Unfortunately, there is no guarantee that s-off will be achieved again. That's what drove me to go ahead and exploit what avenue I did have to obtain s-off. Once you obtain it, your good for the life of your phone. It also allows you to return it to pure stock and remove all those tampered flags, if you ever need to. Just be sure to never take any additional upgrades from AT&T, because right now were lucky the hboot version matches so the hboot is written over when you downgrade with the RUU. If the next AT&T update forces an upgrade of the hboot version number, you could loose any chance to gain s-off. If all you want to do is run custom ROMs, though, you're fine with just having the phone unlocked.
[One (M7) Original Android Development] cubitusclaudius:
Not really, cause you'll not be able to update firmware...
[One (M7) Original Android Development] GalaxyUser50:
I used this to s-off my sprint HTC one, and hot reboot was broken as stated. However, I ruud to fix it like it was posted, and it's still broken. Any ideas?

Thanks
[One (M7) Original Android Development] donmarkoni:
What are you talking about? In what situation he will not be able to update firmware? If he is S-OFF, he can do what he likes, upgrade, downgrade. If he is S-ON he can only upgrade.

Anyway, I'm S-OFF and have never updated firmware, not a single partition, HBOOT and other important ones are from April 20th. Never had any problem.
[One (M7) Original Android Development] runganwt:
Anyone have ever heard about S-On after flash new firmware (Hboot 1.54) then Radio is gone. My phone now cannot find any phone signal (wifi and bluetooth work fine) It's look like baseband is gone...:confused::confused::confused:
[One (M7) Original Android Development] donmarkoni:
Which

specific

file did you flash, point us to it please, so it could be examined and avoided if necessary.
[One (M7) Original Android Development] zipsnet:
Can anyone who has S-off and has not upgraded hboot upload a copy of his hboot? You can use fastboot to dump a copy
[One (M7) Original Android Development] donmarkoni:
Check THIS out. But the question is: what do you want to do with it?
[One (M7) Original Android Development] runganwt:
This is from a friend of mine. He tried to S-on (bad decision) he also edit CID to CSW__001 after that he flash 4.3 firmware (after S-on). Then he try to flash many ROM but got bootloop almost every ROM except Stock Google Play Edition. Now basebands show unknow. Then there is no phone signal since.

Sent from my HTC One
[One (M7) Original Android Development] zipsnet:
Thanks, I don't know exactly what i'm gonna do, good thing tho is I still have my T-MO's 14 days to return phone ;)

-Z
[One (M7) Original Android Development] donmarkoni:
Why doesn't he flash just a radio?
[One (M7) Original Android Development] runganwt:
I have no idea what that silly wanted to do with his phone. :D

Now I try many known combination I knew. I still cannot get phone baseband (phone signal) to work. Wifi and Blurtooth work fine.

I think it have something to do with hboot and CID. What could cause baseband to stop working? :confused::confused:
[One (M7) Original Android Development] donmarkoni:
Have you tried selecting network type under Phone info inside HTC Function Test program *#*#3424#*#*?
[One (M7) Original Android Development] daleski75:
Pardon me if I am wrong but are you basically saying you played around with the phone, screwed it up and are now going to get a replacement through T-Mobile within 14 days if you cannot get it fixed??!!!
[One (M7) Original Android Development] Theshawty:
If that is the case, I will soon lose faith in humanity. I so hope T-Mo notices and refuses to let him switch (or make him pay to switch).
[One (M7) Original Android Development] daleski75:
I hope I got the wrong end of the stick in this instance but that's certainly how it looks from here.
[One (M7) Original Android Development] harlenm:
trying to get it to work on current device, have gotten it to work on other devices, but this just keeps throwing error -1.

No matter what I try, always the same error.

Any ideas? Att version, with 1.44 hboot.