yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] George_Mn:
Yeah I used the first revone to s-off which lead to reboots. I tried everything to fix it. Took me 3 days to find out it was bc of revone. As I already updated the hboot in order to fix my issue (before I went s-on), there is currently no way for me to get s-off.
[One (M7) Original Android Development] gartner83:
What exactly did you find out about revone that lead to reboots?
[One (M7) Original Android Development] murtezahu:
is anybody else getting random reboots after doing s-off using revone?

i have had a couple today, and im trying to figure out if its cm10.1 or it has something to do with the modified hboot.

thanks in advance!
[One (M7) Original Android Development] donmarkoni:
It is not related for sure. Revone doesn't use modified hboot, like Moonshine does. If your bootloader does it's thing and pass control to kernel/ROM, then that's it, blame those two. ;)

Sent from my HTC One
[One (M7) Original Android Development] cangia:
well .. i'm going to became CRAZY :silly: i try to relock and make stock /( for future assistance ) , from s-off , bootloader unlock and hboot 1.54 .. well .. setup RUU RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed , relock bootloader and s-on .. then now i'm TAMPERED , Locked , s-on and hboot 1.44 .. very well .. but .. now revone don't work ( try and retry for 2/3 hours , in many way ) .. and most important thing ... unlock bootloader via HTCdev and One Toolkit DON'T work !! .. can someone help me ?

log for revone :

shell@android:/ $ cd /data/local/tmp/

cd /data/local/tmp/

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

./revone -P

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Success.

revone successful - no need to reboot.

10|shell@android:/data/local/tmp $ ./revone -s 0 -u

./revone -s 0 -u

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Success.

revone failed (error code = -1)

and unlock bootloader say that work .. but in fastboot it's always LOCKED ..
[One (M7) Original Android Development] donmarkoni:
I would say you must reboot where you don't. Did you tried that too?
[One (M7) Original Android Development] cangia:
after " ./revone -P " i always reboot .. but don't work ..
[One (M7) Original Android Development] godutch:
Indeed, the only thing is stock rom's (and maybe some custom roms) do a check for s-off and turn on extra logging, so maybe that extra logging is causing the reboots
[One (M7) Original Android Development] George_Mn:
check 2nd post:

"UPDATED revone binary (v0.2)

* Remove the random reboot feature."

Took me days (and a lot unnecessary efford like trying other roms/going back to stock/flashing ruu/updating to stupid 1.54) to find out my reboots were related to the first release of revone.
[One (M7) Original Android Development] godutch:
Are you serious :confused:
[One (M7) Original Android Development] cangia:
and if i try to install software update via OTA , download it, install .. but stuck on Fastboot screen ( with "Security Warning " in red ) .. please someone .. :(
[One (M7) Original Android Development] mugetsu666:
Only thing I can say is rerun the ruu for your phone, but U should have never s-on. Once u s-off, u should never s-on again unless u are returning it or getting rid of it and then I still wouldn't s-on again.

androidtechy.com/Team-nocturnal/droidnow.com Sign up for [MENTION=310414]Copya[/MENTION]pp with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=DrfOMd
[One (M7) Original Android Development] cangia:
S-off wont work, i dont know why..
[One (M7) Original Android Development] iElvis:
I don't understand why people keep doing this to themselves. S-off is serious business. You should not do it unless you're prepared to stay that way. Some people seem to think that s-on is "safer" or "more stable" but this is only the case on an unmodified phone. Once you go s-off, going back to s-on can be very dangerous unless you know what you're doing.

Going back to s-on after you've modded your phone is a lot like peeling off a bandage, rubbing a lot of crap under it, then putting it back on. You're running the risk of locking your phone into an unstable configuration, with no way to correct it. Too many people have learned this the hard way. :rolleyes:
[One (M7) Original Android Development] mugetsu666:
I couldn't have said it better myself man. :banghead:

androidtechy.com/Team-nocturnal/droidnow.com
[One (M7) Original Android Development] EtherealRemnant:
[MENTION=4282187]mugetsu666[/MENTION]

I did a warranty swap on T-Mobile and stupidly took the .11 OTA. You say you have had 3 out of 3 success on getting S-OFF, can you please PM me the steps? I am not a newbie, I have goldcarded the Sensation and so I can follow step by step instructions - I need the info and the links to the material I need to use.

I signed up for JUMP and I need S-OFF so that I can reset everything to stock before I hand them a phone that shows I have messed with it. Thanks for your help. I'll get rejected from JUMP if I bring in my phone with a bootloader that shows unlocked or tampered. T-Mobile makes you do it in store so they can inspect physical damage and bootloader tampering. If they see the tampering, you have to pay the Asurion deductible

Thank you.

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

By the way I only took the OTA because I was annoyed with dropping LTE all the time and how long it took to handshake... I'm assuming that somehow the radio can be patched to increase polling time because my S4 immediately went back to LTE while it takes about 45 seconds with the One.
[One (M7) Original Android Development] cangia:
I don't joke with s-off :( only try to relock for go to bring back to assistance.. I know that im doing.. But now i dont know what happen..

Before s-on i install RUU, stock recovery and stock hboot 1.44..
[One (M7) Original Android Development] mugetsu666:
My 3 of 3 is by ppl who haven't taken the ota & still on the .8 ota and couldn't get revone to work. They were always getting the error 6, so they used .7 version my team has and downgraded that way and was able to gain s-off on usual the first attempt. Right for those who have taken the ota I have only had 1 success out of 3 and that's by flashing Behold_this firmware package for .8 and then our .7 and then attempting s-off, but the most recent attempt failed and that was yesterday. If u took the ota u applied the patch & only if ur Very lucky will it work. Sorry about

androidtechy.com/Team-nocturnal/droidnow.com
[One (M7) Original Android Development] pandaball:
Thread cleaned. Personal attacks are not how disagreements should be solved. Please stay on topic and be nice to each other :)
[One (M7) Original Android Development] mugetsu666:
If ur on tmobile and on .8 it's actually easier to flash or restore a .7 rom and u can usually achieve s-off on the first or second attempt.

androidtechy.com/Team-nocturnal/droidnow.com
[One (M7) Original Android Development] Gandroid:
Thanks mugetsu666. I got the s-off with the .8 :D

I just realized that this method gets the s-off but doesn't root the phone?. To root, should I need to register at the htc dev site?
[One (M7) Original Android Development] iElvis:
People forget that revone is a hack, not an official HTC tool. It seems to work most of the time, but other times things go haywire, especially after mods have been made. That's the risk in going s-off, even if you're an advanced user. You would think restoring all the stock elements via RUU would solve the issue, but it seems there may be other things going on.

Since you got revone to work, you may as well use it to unlock. Then you can flash recovery and a rooted rom or superuser.
[One (M7) Original Android Development] Theshawty:
What exactly would happen if we opened up a RUU, switched whatever hboot is inside for a 1.44 one (S-OFF'able) and the repacked it and flashed it?

Or is this wishful thinking?
[One (M7) Original Android Development] iElvis:
It would be fine if you were s-off, with s-on, it will fail the signature check.
[One (M7) Original Android Development] PillowMetal:
Another option is to leave it locked... you can flash recovery using

fastboot oem rebootRUU

fastboot flash zip recovery.zip

fastboot reboot

You can then flash SuperSU, busybox and whatever mods, ROMs, etc. you want from custom recovery.

The advantage to staying locked is you don't have to use HTCDev, and you don't have to rely on revone unlock working on future versions of hboot. Once you are S-Off there is no need to unlock.

EDIT: the recovery zip is simply a zip file you create with the recovery.img file in it, along with a file called "android_info.txt" that usually contains information pertaining to your phone, but truthfully can even be empty because when S-Off that file is not checked.
[One (M7) Original Android Development] Theshawty:
Crap. I need to downgrade so I can S-OFF. I mistakenly accepted the 4.2.2. OTA. :D
[One (M7) Original Android Development] Gandroid:
Just flash the recovery from fastboot?. Sorry I am new to htc one.
[One (M7) Original Android Development] iElvis:
Yes, from fastboot.
[One (M7) Original Android Development] Gandroid:
Thanks.

got the TWRP flashed and working....flashed su as well but titanium still says no root. I will flash the rooted .11 from mugetsu666's other thread and will see how it goes.
[One (M7) Original Android Development] mugetsu666:
No use revone to unlock if u want to unlock ur bootlaoder. Matter of fact pm me and I'll lend u a hand.

androidtechy.com/Team-nocturnal/droidnow.com
[One (M7) Original Android Development] gampt:
Did you use custom or expanded custom Behold_this firmware?
[One (M7) Original Android Development] lainemac:
Worked perfectly on my Sprint One!

Note: Prior to this, my bootloader was unlocked and I was rooted.
[One (M7) Original Android Development] mimin0:
+1
[One (M7) Original Android Development] spaboleo:
that sounds like a feasible method! thanks!

but how can i backup the stock recovery?

Or is it already available somewhere?

So you flashed TWRP from fastboot, as described by PillowMetal?

Were you on 1.54.0000 and S-ON HR? (What does that "HR" stand for anyways...?)

Does the "recovery option" appear in the boot-select menu of the bootloader?

Thanks :good:
[One (M7) Original Android Development] PillowMetal:
You can get a pristine copy of your stock recovery (if you are still stock or have run an RUU) by running

adb shell dd if=/dev/block/mmcblk0p36 of=/sdcard/recovery.img

mmcblk0p36 is the recovery partition on the Sprint HTC One, which may be different for other variants, I'm not sure. But you can verify for yourself by running

adb shell cat /proc/emmc

and looking at the output which will list all your partitions, one of which is labelled "recovery" - that's the one you want for the "if=" parameter.

You can also get a copy of recovery.img from inside the "firmware.zip" of an OTA file or inside the decrypted "rom.zip" from an RUU. But the only time I've needed to flash a stock recovery is if I want to accept a new OTA; it requires and uses stock recovery to perform its functions.

BTW, I misspoke when saying the android_info.txt can be empty, that was the case with my old EVO 4G LTE, but it seems for the new Sprint HTC One it needs the following three lines at a minimum.

modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10

Again this may vary with your variant, so change them for your version of the phone. You can get this information by running

adb reboot bootloader
fastboot getvar cid
fastboot getvar mid
fastboot getvar version-main
fastboot reboot

Yes, it is in the root level of the bootloader, not in the fastboot level of the bootloader. If you are in the fastboot menu, just select "bootloader" and it will bring you back to the root.
[One (M7) Original Android Development] zyon92:
Hi all,

concretely, there is a chance that revone be updated? The team's trying to find a exploit ?
[One (M7) Original Android Development] Theshawty:
I'm sure they're hard at work.
[One (M7) Original Android Development] rfryar:
The lowercase p worked for me. I am s-off now. Rebooting again to get tampered removed. Been struggling for days using the upper case P. Thanks for the post!!

Rick
[One (M7) Original Android Development] spaboleo:
Thanks a lot PillowMetal :good:

Just to clarify: This method should work with S-ON devices (hboot 1.54, OS-Version 2.24.401), right?

If so then I am wondering why this isn't done by everyone, who is stuck on the 1.54 bootloader, who wants to avoid using htcdev?

I mean it doesn't unlock the bootloader, but you don't really need to if you can get a custom recovery/root with this method.

Or are there any (potential) disadvantages that I can't foresee?

Maybe like when something goes wrong really badly that you can't flash the update.zip via fastboot?

If I can remember correctly this was the scheme we all followed with the HTC Desire, as well. Disguising the Custom Recovery as an RUU Update...until other methods popped up.

:good:
[One (M7) Original Android Development] grasshands:
Rogers ONE - Android 4.1.2 , Software 1.29.631.17 - S-OFF Possible?

Hi

Just picked up the Rogers HTC One, and it's running stock android 4.1.2 with Software 1.29.631.17. I see mention of other users having problems acquiring the S-OFF state on 4.1.2. Can anyone confirm/deny if this should work with the standard revone script, or is there a modified version of revone for this?

Thanks very much

J
[One (M7) Original Android Development] maddie01:
This is the software version I had when I did S Off with revone and it worked great. Maybe Rogers is different but don't accept any OTA updates to 4.2.2 until you S Off...once you update to the next version revone won't work...do it while you can
[One (M7) Original Android Development] grasshands:
Exactly my plan, avoid the OTA update until I was sure what I was doing with this new phone...coming from an SGS1! hahaha

I'm going to give this a shot now, front page instructions good to follow using the latest revone0.2.1?

Thanks

J
[One (M7) Original Android Development] maddie01:
I did not have my laptop so I used Rom ToolBox Lite with it's Terminal Emulator and downloaded revone file directly to my phone and went that route. Worked great..
[One (M7) Original Android Development] grasshands:
Just finished and it worked perfectly! S-OFF, done!

Now to start reviewing ROMS with sense as I dont want to lose all the cool features of the phone, remote control, etc. :)

Thanks for the help!!!

J
[One (M7) Original Android Development] maddie01:
That is awesome! Great being S-Off....
[One (M7) Original Android Development] grasshands:
Hrmm, now to figure out which firmware I need for RevolutionHD on Rogers... ;)
[One (M7) Original Android Development] Sneakyghost:
Secureflag is in partition 3 which is not part of hboot or radio.

I posted this already.

This partition can be flashed as an image, containing a switched-on security flag, and after a reboot you'd be S-ON.

Unsure about the encrypted part of that partition though. If it's some unique key, it can't be flashed as a factory image, hence no S-ON possible via image flash unless restoring a dump of the individual phone.

I just wanted to say that S-OFF hasn't gotten much to do with radios or hboots these days anymore. It's a small extra partition which is itself protected by the security mechanism and can't be hacked if not already S-OFF.

mobile post

---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------

Are you sure you can't flash p3 as image? I'm genuinely interested. Can you provide further information? Because my info is different?

Thanks!

mobile post
[One (M7) Original Android Development] PillowMetal:
My original reply outlining the method of keeping the bootloader locked, was in response to a post where the guy was S-Off but wanted root, was asking if he needed HTCDev, and someone was recommending revone unlock. If you read near the bottom, I state that "Once you are S-Off there is no need to unlock." So I assumed you were S-Off already.

http://xdaforums.com/showpost.php?p=44623360&postcount=4716

The rebootRUU method of flashing will only work with S-On if you are using HTC signed rom.zip files, like the kind that come from RUUs. These contain all partitions like hboot, boot, recovery, system, data, radios, etc. When S-Off you are taking advantage of not having to flash signed files and therefore can include only the items you want; like stock or even custom recovery.

So I was just saying that you can use revone to get S-Off only (revone -s 0 <-- no -u parameter) and leave the bootloader locked just fine. If your on an hboot that can't use revone, you will have to wait until they crack it, or will have to unlock from HTCDev.

Even if something goes very badly, as long as you can get to the bootloader, this method will still work fine, and in fact will restore your phone to factory if you use and RUU rom.zip. As long as you don't flash an hboot.img that is not compatible with your phone (which you can't do unless you are S-Off anyway), then you will be fine.
[One (M7) Original Android Development] prank1:
Yes you are right, the partition containing secureflag is a different to that containing the HBOOT or Radio, hence flashing HBOOT or Radio doesn't affect the Secureflag (S-OFF/ON) status.

You could flash that partition with an image containing an S-ON flag but I doubt people here would be experimenting on that level unless they knew what they were doing.

Then again I assume if you did happen to S-ON via this way you could use RevOne and gain S-OFF again provided you were on a 1.44 HBOOT?

As you said the secureflag status doesn't play much of a role in HBOOTs and Radios but as part of the boot process; if it is S-ON and sees that the HBOOT is unsigned then it will self-brick. This does not occur with S-OFF.
[One (M7) Original Android Development] PillowMetal:
No, I am not absolutely sure, but I have yet to see a pg1fs.img file in any firmware or OTA update, nor have I heard of anyone getting turned S-On once they were S-Off. There's even a thread that tracks this for people who want to be sure:

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

I also outline my reasons why I think this would be stupid or even impossible of HTC to convert people to S-On in this post:

http://xdaforums.com/showpost.php?p=44504181&postcount=4620

Indirect feels the same way:

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

Your suspicions could be be entirely correct that one could use "adb shell dd if=pg1fs.img of=/dev/mmcblk0p3" if you are S-Off, to take someone's S-On partition and write that over top yours, but I had the impression that since it is NV_RAM, it can't be touched by the normal recovery process.

I welcome any information you have as well!
[One (M7) Original Android Development] godutch:
For what it's worth I sent in my device s-off/locked and got my phone fixed under warranty. I sent in my device running 1.29.401.12 (with hboot 1.44) and got it back with 2.24.401.1 (with hboot 1.54), they fixed the device under warranty (eventhough the defect could potentially have been caused by unlocking, I actually noticed it first right after installing a 2.17 test rom...)

I don't think the repair center checks for s-off, just for unlocked/relocked status. It had been known some devices ship s-off, so even if they make trouble you could claim you have no idea what rooting/unlocking/s-off/hboot is
[One (M7) Original Android Development] iElvis:
It's been done. As I think I mentioned earlier in this thread, the guys who created the GE conversation did it by accident when they tried flashing the entire stock GE package from an s-on GE phone onto a generic One. Bam, it was s-on (as well as stuck with the wrong IMEI).

You can most definitely write to p3 on this phone if you're s-off, just not in recovery.
[One (M7) Original Android Development] spaboleo:
Ah...damn :(

Thanks anyways for all your detailed explanation!

I bet it will be helpful for others anyways :)

So I'll just wait patiently...and hope for the best.

Or is there any way I can proactively contribute to finding an exploit?

I'm on an international HTC One, without any simlock.

Thanks :good:
[One (M7) Original Android Development] PillowMetal:
Agreed, that was really my point... that you would have to use something like "adb shell dd if=pg1fs.img of=/dev/mmcblk0p3" or maybe "fastboot flash <partition_name?> pg1fs.img" to do it, not through the normal recovery, RUU, or OTA, so I'm still not worried about HTC turning me S-On on in an update, since I have no intention of intentionally flashing partition 3.

Although that will not stop me from using catlog to find the OTA location, download the OTA file, open the firmware.zip, and take a look for myself before accepting! :eek:
[One (M7) Original Android Development] grasshands:
Sorry as this is sort of off topic, but I really dont want to lose my S-OFF...

researching the firmware upgrade procedure for my Rogers HTC One, necessary prior to installing Revolution HD, and I've got my CID set to 11111111 via Hasoon2000s toolkit and the firmware zip 2.24.401.1.zip downloaded. I had seen a post about opening the zip and removing some files that would overwrite the hboot or something, thus undoing my S-OFF...can anyone help point me back towards that info on how to edit the firmware zip to not lose my S-OFF?

Thanks :)
[One (M7) Original Android Development] zipsnet:
Help would be greatly appreciate

this is for HTC ONE T-mobile USA

fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.15

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.27.531.8

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT35PW912867

(bootloader) imei: xxxxxxxxxxxxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4304mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

shee$> for i in {1..500}; do adb shell su -c /data/local/tmp/revone -P; done

revone v0.2.1

revone failed (error code = 2)

revone v0.2.1

revone failed (error code = 2)

revone v0.2.1

revone failed (error code = 2)

....

Any idea ??

Thanks ..
[One (M7) Original Android Development] grasshands:
Found that once you've got S-OFF simply updating h-boot wont cause you to lose S-OFF...so I jumped in and upgraded my firmware and all went well! I was able to re-apply recovery after the upgrade and it still shows S-OFF! Next step, sexy rom time!!!!

Thanks again!

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

OOuch, spoke too soon...lost my camera :(
[One (M7) Original Android Development] jgeorge15:
If you haven't taken the .11 update then downgrade to .7 via nandroid or twrp backup and try again it will work, if you've taken the .11 update previously then you're out of luck and revone will not work.
[One (M7) Original Android Development] justin11141:
Does this work with at&t .15?
[One (M7) Original Android Development] maddie01:
Try Viper 2.0...best custom Rom and awesome support.
[One (M7) Original Android Development] jonas2295:
Nah it has some lags here and there.

And you know there is no best rom.
[One (M7) Original Android Development] grasshands:
Fixed my broken camera...turns out the firmware upgrade wasn't suppored by the stock 4.1.2 android...once upgraded to 4.2.2 all was well again in droidsville!!!

Cheers again!!
[One (M7) Original Android Development] jonas2295:
Glad you sorted it out :)
[One (M7) Original Android Development] mimin0:
That's strange. How could somebody flash Behold_this firmware .8 if a) there is no official .8 b) all custom fw require S-Off?

Either whoever reported this to work was already S-Off and didn't realize it, or just misinformed you.