yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] abhishek_22:
I am getting the -6 error. Is there anyway to fix this?
[One (M7) Original Android Development] Theshawty:
Just wait..
[One (M7) Original Android Development] TechSavvy2:
Verizon could actually care less about the xda community. Unfortunately it makes up less than 1% of their users, and they have made it (basically) clear they would rather see all the xda crowd jump ship to other providers than have unlocked bootloaders......no joke..... Hence why you never see a response from them about it
[One (M7) Original Android Development] AirforcProductions:
You should look around T-Mous system see if you can get at that .7 RUU :) You would be a hero if you got it...statues of you etc etc
[One (M7) Original Android Development] Theshawty:
He'd be fired in a day.
[One (M7) Original Android Development] AirforcProductions:
Yeah I think that outbalances the statues and crap haha I can dream can't I?
[One (M7) Original Android Development] gacon1000:
Tampered message back again after battery run out of

I used Revone to lock bootloader and remove “Tampered” message, S-ON. Everything is successful and back to stock with hboot 1.44 and android 4.1.2 and S-on completely.

After that, my device ran out of battery and shutdown. When I’d plugged in to charge, suddenly my screen turn on and go to bootloader automatically. At this time my htc appear “Tampered” message again and “Security Warning “message. That’s weird.

After I unplug and reboot bootloader, Security Warning message disappear but “Tampered” message is still here.

I tried to remove “Tampered” message again by revone and everything is ok. Then I reboot and shutdown, and plug in to charge then “Tampered” message don’t appear. Still plug in to charge, I reboot and shutdown then Tampered” message and “Security Warning “message appear again.
[One (M7) Original Android Development] bonzai6:
S-Off Issues with OTA Update

I had installed the OTA update for .15 without thinking and was stuck with S-ON. I was planning on doing it but never did before the update. From what I was reading online I figured I was screwed. I still had the 1.44 HBOOT, but it was dated July 5. I started looking around some more found this Thread by INeFFeCTiVE ( http://xdaforums.com/showthread.php?t=2394155&highlight=downgrade ) and it ultimately helped me downgrade to .12 and run revone to S-OFF. I couldn't believe it worked, but it did. So props to INeFFeCTiVE and I hope it helps anyone else stuck here with the same issue as me. Now I'm off to convert my HTC One to a GPE One.
[One (M7) Original Android Development] Gerton:
Only for AT&T?
[One (M7) Original Android Development] DanielF50:
Yeah, looks like it only works on AT&T 1.44, so if you're on 1.54 - you're still stuck!
[One (M7) Original Android Development] beats4x:
Haha, you're not the only one dreaming. I've thought about it and like you guys said, not worth my job /: I wish though!

Sent from my Venom Infected One powered by ElementalX Kernel
[One (M7) Original Android Development] LTKred:
Going Back to S-ON

Can i safely go back to S-ON and Locked Bootloader if i have previously changed MID/CID to do the full GPE RUU conversion?

The reason I ask is that im not sure there's an RUU for my phone, I've searched everywhere. I only want to know in case i ever sell the phone.

Original Device Info (M7_UL):

CID - TELST001

HBOOT - 1.44.0000

Radio - 4A.14.3250.13

MID - PN0714000

Current Device Info:

CID - GOOGL001

HBOOT - 1.54.0000

Radio - 4A.18.3263.15

MID - PN0712000

any help with this would be greatly appreciated :)
[One (M7) Original Android Development] runganwt:
First thing you need to do is find that RUU. You can change CID and MID to whatever you want, but it will mean nothing if you can find that RUU for them.

Be careful on changing CID & MID too. It have to be the proper combination unless your phone will lost baseband. It's similar to when you have NIC card on your PC but you install wrong driver for it. It will stop working, then you will got yourselt an iPod.
[One (M7) Original Android Development] LTKred:
yeah i thought that would be the case. If there is no RUU, then are there any other options?

Cheers man =D
[One (M7) Original Android Development] GelullaBarr:
s-off on hboot 1.54 would be availble?
[One (M7) Original Android Development] russel5:
No
[One (M7) Original Android Development] Tetsumi06:
No. Granted, reading any of the preceeding 300 pages would have answered your question.

----------------------o('_')o----------------------

Sent from an HTC One with using xda app:

TrickDroid ROM 9.1.0

Bulletproof 4.3
[One (M7) Original Android Development] GelullaBarr:
I was reffering on any news, I know from begining that was not possible, I was talking for future, don't be cruel
[One (M7) Original Android Development] beaups:
How can anyone know the future? Happen to know what next week's powerball numbers are?
[One (M7) Original Android Development] GelullaBarr:
35, 88, 67, 24, 2...I only could "see" those numbers...
[One (M7) Original Android Development] EtherealRemnant:
Dont you think people would be posting all over the forums and making being a moderator a nightmare for the next week or so? Seriously.
[One (M7) Original Android Development] GelullaBarr:
k, I understand the rule..."don't ask, just wait", I'm just frustrating that I can't s-off my device so I must wait for official update, relock bootloader, install stock recovery and hoping for OTA, then unlock bootloader, flash rom, kernel, etc...all with cost of format sd card..would be much simple s-off, but no luck there...
[One (M7) Original Android Development] EtherealRemnant:
Preaching to the choir. I don't have root because I don't want to mess with the bootloader. Not until S-OFF lets me hide what I did. So I understand completely.
[One (M7) Original Android Development] ZeRo2o9:
have tried for hours and searched in here alot I have HBOOT 1.44 and date says may 5th it seems like it should work but it doesnt just get error 1 everytime on step 4 can't even get past it. im on windows 8 btw :rolleyes:
[One (M7) Original Android Development] WWEpsp:
Maybe with the new hboot release (1.55) we can get S-OFF. Who knows, maybe HTC left a back door open :P

Cheers :good:
[One (M7) Original Android Development] c5satellite2:
There is no point in a new s-off method because it will just help HTC close the exploit as we have already seen. Probably will be waiting until HTC gets out all the 4.3 updates before any devs will want to expose any new methods.

I do not have any inside info, just basing this on what I have seen over the years.
[One (M7) Original Android Development] EtherealRemnant:
I think we will see a release when they have cracked Verizon.

And yeah, I know about HTC and plugging holes so I agree that exposing a new exploitation would give them ammo... But I've seen the cat and mouse game and I honestly think the HTC devs get off on making new holes for us to figure out. HTC knows how to program (even stock,my One is the most stable device I have ever had - in fact T-Mobile reminds me once I've passed 7 days to reboot - I had to reboot every other device at least every 3) - they could easily encrypt the bootloader like Samsung did for AT&T and Verizon... Verizon bounty is well over 3500...

The point is that they make us work for it. They always have. That's not going to change. They proved with HOX+ what they can do........
[One (M7) Original Android Development] DeSaint2:
That also had to do with tegra. There is security coding within the chip as well from the manufacturer so that was just a double whammy.
[One (M7) Original Android Development] runganwt:
If you can, just ask someone you know who use the same phone you have whether he/she make Nandroid backup of stock rom, firmware can be anything. You just need the same version as Stock (out of the box). With Super CID, flash them after you got everything back to stock then you edit your CID (and MID is needed) back to yours then S-On. Then get yourself STOCK Phone. :cowboy:
[One (M7) Original Android Development] angusc:
Read a few pages back there is a link to another thread on how to downgrade to and earlier HBOOT date which then allows revone to work on 1.44 HBOOTs.

Sent with desire from My One
[One (M7) Original Android Development] ZeRo2o9:
yea I saw that I wasnt sure if I should try it. I may give it a shot. thanks
[One (M7) Original Android Development] 1meanrex:
I was in your shoes for a few hours today, attempted numerous times to get s-off only to be met with an error code. There were times where it let me past a previous spot i hadn't past only to meet another dead end. It seems if you took the ota in the early part of august there it blocked s-off while leaving you with the original hboot of 1.44. I followed the link Angus was talking about and it cures all my issues and it should cure the issues you have. Here's the link again if you need it http://xdaforums.com/showthread.php?t=2394155
[One (M7) Original Android Development] biohazardta:
Hi all,

My device is running under HBoot 1.54 Unlocked S-On

Anyway to flash it back to "Locked"?

Thank you very much!
[One (M7) Original Android Development] runganwt:
The most you can get is "Re-locked" You can't run revone -l with S-ON. and you can't S-OFF Hboot 1.54 :(
[One (M7) Original Android Development] biohazardta:
How can I get Re-locked under Hboot 1.54? I cannot relock or lock it.:crying:Thank you.
[One (M7) Original Android Development] Sloth:
fastboot oem lock
[One (M7) Original Android Development] biohazardta:
Hi,

Could you please explain more detail? Thank you very much!
[One (M7) Original Android Development] RuckusDecay:
Same procedure dude as when you unlock it.
[One (M7) Original Android Development] runganwt:
How do you get it unlock? :confused:

If you unlock you phone yourself you should know what he talking about. Unless you have a lot to read...:D
[One (M7) Original Android Development] biohazardta:
Oh I see.:o

Thank you very much!!

Hope can "Locked" very soon.
[One (M7) Original Android Development] RuckusDecay:
Put ur phone on fastboot mode bust out with cmd then bust the code.
[One (M7) Original Android Development] biohazardta:
Yes I know:o

I mean it would be better to change to "Locked" Instead of "Relocked" if possible.:o
[One (M7) Original Android Development] RuckusDecay:
If ifs and buts were candy and nuts, we’d all have a Merry Christmas.
[One (M7) Original Android Development] TechSavvy2:
$3,500? .... Try $5,200 last I saw before the thread was locked. Regardless.....
[One (M7) Original Android Development] jZanetti:
Hi S-OFF not work on

HBOOT-1.54

OS-2.24.161.1 ????????????
[One (M7) Original Android Development] Sloth:
Your answer is in post 1 the first line :D
[One (M7) Original Android Development] RuckusDecay:
U beat me to it
[One (M7) Original Android Development] chemita:
Reading the first post least
[One (M7) Original Android Development] runganwt:
Hi Guy, Just want to confirm one thing. Can we flash recovery without unlock just S-off (I mean Phone is S-off but still Locked) :confused:

Thanks
[One (M7) Original Android Development] cz4r3n:
No
[One (M7) Original Android Development] runganwt:
Thanks :good:
[One (M7) Original Android Development] Sim-X:
Confirmed working on the new Red Sprint HTC One. I did have to HTC Dev unlock first in order to gain root. revone failed to root 1.31.651.2 but it wasn't that big of deal. Once root was gained, S-OFF was no problem. Thanks :good:
[One (M7) Original Android Development] Gerton:
I presume this is hboot 1.44?
[One (M7) Original Android Development] skulldreamz:
Boot to bootloader and you are on 1.44 if you haven't flashed the 1.54 hboot and I'm sure the the date of the 1.44 when u got it was before may 3 probably even april...
[One (M7) Original Android Development] Golv:
YES!

If you have S-OFF, but the bootloader is locked, you can flash RECOVERY!

In this case, the recovery (can be stock or сustom) flashed as firmware.

In the zip file should be only 2 files: recovery (called recovery.img) and android-info.txt

The content of android-info.txt about this (just to be your data cid, mid, ver):

modelid: PN0710000

cidnum: 11111111

cidnum: HTC__001

cidnum: HTC__E11

cidnum: HTC__102

cidnum: HTC__203

cidnum: HTC__405

cidnum: HTC__Y13

cidnum: HTC__304

cidnum: HTC__032

cidnum: HTC__A07

cidnum: HTC__J15

cidnum: HTC__016

mainver: 2.24.401.1

btype: 1

aareport: 1

DelCache: 1

hbootpreupdate: 3

Run in the command line:

adb reboot bootloader

fastboot oem rebootRUU

fastboot flash zip recovery_named_something.zip

fastboot reboot-bootloader

For more information, see Step-by-step (items 1-6) - HERE. :good:
[One (M7) Original Android Development] TabascoJoe:
I was able to revone -P once, rebooted and now I keep getting the "Failed to map memory." error

What am I doing wrong? On 1.44 att

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

./revone -P

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.

[-] Failed to map memory.
[One (M7) Original Android Development] Squirrel1620:
Jeeze at this rate everyone will have s off before you guys get to release finalized software lmao

Sent from my Tricked out HTC One
[One (M7) Original Android Development] dronepro:
you are a life saver, i forgot my notes at work.. i am about to post something important....
[One (M7) Original Android Development] chakra:
No this will not wipe anything.
[One (M7) Original Android Development] Garmig:
Try adding .bin after revone

example: chmod 755 revone.bin
[One (M7) Original Android Development] dronepro:
Attention ALL (especially US HTC DEV phone holders)

i did all that needed to be done and wrote a small tutorial (more simplistic for people like me :eek:) however i went above and beyond and changed CID to 11111111 once i did this after 1 hour my phone would not allow me to make calls or receive and asked that i wipe data partition, did and reinstalled rom however then told me HTC Dialer won't work. did everything i found online to fix dialer but did not work.

here is the FIX.

CHANGE BACK CID to BS_US001 and you will be OK. DO NOT FREAK OUT, i did,

Follow these instruction as per PAGE 1 but if you have issue CHANGE CID back to BS_US001 if you have issue, otherwise S-OFF works GREAT.

again thanks to all devs who did this, you are amazing.

here are my simplistic steps for getting S-OFF

1. Download revone (above and place in the forlder where you have the ADB files)

2. Open Command prompt and CD to where you have ADB files and just placed revone.(i.e. for me= cd android {this is my folder for adb}

the following are commands you will type word for word.

3. adb push revone /data/local/tmp/

4. adb shell

5. cd /data/local/tmp

6. chmod 755 revone

(optional) If your device is unlocked and rooted please type

7. su

8. ./revone -P

If revone reports success reboot the device

after rebooting open another Command Prompt and go to your ADB folder files like in step 2.

9. adb shell

10. cd /data/local/tmp

11. ./revone -s 0 -u

Presuming revone reported success please reboot the device again, this time to the bootloader this was.

12. adb reboot bootloader (or power+Vol down)

You should now observe your device is S-OFF --- if so, note your CID and change to this CID doing this when in Bootloader

go back to command prompt where adb files are

13. fastboot oem writecid 11111111

if you want you can remove the TAMPERED by booting your phone and going to command promt and

14.adb shell

15. cd /data/locaL/tmp

16. ./revone -t

Go to bootloader and see if TAMPERED is gone.
[One (M7) Original Android Development] deeevan:
Some obvious questions:

How did you push the revone file to your phone? Was that successful, and was it to /data/local/tmp?

Is the file name revone?
[One (M7) Original Android Development] philbaines:
It went over fine,even checked in /data/local/tmp with root browser on the phone and the file is there.and yes file name is revone.
[One (M7) Original Android Development] Fidelio_o:
S-off and cid 111111. You guys rock. Quick question now that I am S-off that means I can flash any RUU right? with my 111111 CID?
[One (M7) Original Android Development] ThePhoneGeek:
One suggestion. I always like to do a full reboot before I start anything like this. In my case my device may be days or weeks from the last reboot so it always made sense to me to start fresh.

I then followed these directions and it worked perfectly the first time...

I am now s-off, I left my CID as BS_US001 as I know I can go change it if I need to but right now all is good!!!

Kudos to the Revolutionary team - 3HM98298X60219031

Thanks to other smart folks in this thread who contributed to the success and yes it is important to read the entire thread!!!

MG
[One (M7) Original Android Development] nenebear:
Thanks very much for the hard work, it's fully working. :good::good::good:

View attachment 2025527
[One (M7) Original Android Development] Riyal:
You need to modify HTCDialer to support CID 1111111. HTC Dialer utilizes CID to distinguish the network connection it uses. I know because I already tried decompiling the dialer to enable additional options in the Mobile data.
[One (M7) Original Android Development] 1wayjonny:
After all the 4.1.2 talk I decided to flash the ARHD, took like 10x because of aroma installer issues. Then I ran the command once and it worked first try. After all the wasted time it was ASOP / 4.2.2 causing all the issues. I was able to unlock under 4.2.2 but I could not get SOFF or tampered removed until I switch to 4.1.2.

Hope this helps and great work guys!
[One (M7) Original Android Development] Rydah:
Mine works on sprint

Sent Via My HTC One, On The Now Network By Sprint!
[One (M7) Original Android Development] slyevo:
Amazing

This was simple & effective... You guys are amazing Thx...
[One (M7) Original Android Development] GitAlongLilDoggies:
Hi All,

I'm running completely stock and haven't unlocked through htcdev because I didn't want to loose the ability to play DRM protected content. Does anyone know if the DRM keys will remain intact after using revone to unlock and root?

Thanks,

Ken
[One (M7) Original Android Development] philbaines:
HAHAHAHA,that was it.

all it needed was a reboot! cheers
[One (M7) Original Android Development] drewtang:
Well. That probably explains why the hell mine's not working. Guess I'll head back to 4.1.2 and try again.
[One (M7) Original Android Development] goodman_east:
C:\Users\admin\Desktop\apktool>adb push revone /data/local/tmp/
2698 KB/s (646704 bytes in 0.234s)

C:\Users\admin\Desktop\apktool>adb shell chmod 755 /data/local/tmp/revone

C:\Users\admin\Desktop\apktool>adb shell
root@android:/ # su
su
root@android:/ # cd /data/local/tmp
cd /data/local/tmp
root@android:/data/local/tmp # ./revone -P
./revone -P
revone failed (error code = 1

what is the matter with this?

my phone is htc m7cdtu/802t for China Mobile with os 2.09.1403.1
[One (M7) Original Android Development] lance989:
Worked for me the first time around.. thanks for all the hard work guys!
[One (M7) Original Android Development] Glenn.Bre:
Worked perfectly for me :) thanks also everyone :)
[One (M7) Original Android Development] Golv:
Didn't get root rights!

You can unlock the bootloader on htcdev.com, install ROOT and try again.

Open an adb shell and enter the first:

su

(get icon # instead of $) and continue instructions...

cd /data/local/tmp

and etc...
[One (M7) Original Android Development] runganwt:
Yes, I knew that. Just want to know the normal flash not on RUU mode.
[One (M7) Original Android Development] TabascoJoe:
I thought you don't need a rooted phone to use revone. Step 1 is a temp root "Gaining root access (thanks to Dan's motochopper)"

I know how to unlock my bootloader, but I don't want to to this if I don't have to. What else can cause this message.
[One (M7) Original Android Development] Golv:
Yes, but not always manages to get a temporary root access on the first attempt ... Then try again. You can try to do the same, only through the terminal from phone.
[One (M7) Original Android Development] TabascoJoe:
Try, Try again

I'll keep trying

---------- Post added at 09:14 AM ---------- Previous post was at 09:04 AM ----------

That worked! It took 6 attempts to revone, but it worked.

So nice to have S-off and not use HTCDEV.
[One (M7) Original Android Development] LTKred:
thanks!

Awesome, so basically, as long as i put original HBOOT 1.44 and CID/MID back to what they were and flash a stock rom, then im good to go back to S-ON yeah? doesnt matter about all the other partitions that the GPE RUU flashes? :)
[One (M7) Original Android Development] donmarkoni:
No. It does matter. [highlight]You should not leave combined partitions when going S-ON.[/highlight] There are few guys that got stuck with half working/broken phones doing that. IIRC one has no radio at all, so he has very expensive e-book reader, or mp3/mp4 player. :rolleyes:
[One (M7) Original Android Development] LTKred:
oh ok. so is there any way I can fix this without an RUU? because there is no Telstra RUU for the HTC One.
[One (M7) Original Android Development] iElvis:
+1000

The quoted post above is exactly what you should not do. I helped another guy with this issue, and his phone simply can't stay booted. He'll get about 20 seconds of use before it reboots. He's stuck until a new s-off exploit or a RUU for his device is posted.

You have to be 100% back to stock before going to s-on. And unfortunately, that can be difficult for some people due to the lack of RUUs. This is another illustration that going s-off carries risks, and not just possible brickage. It can be effectively a one-way trip.
[One (M7) Original Android Development] LTKred:
great help!

yeah totally. Thanks for the heads up. I'm just gonna forget about going back to S-ON if/when i sell the phone, just to be safe.

Any idea if its HTC or Telstra i need to bug to get the RUU? lol
[One (M7) Original Android Development] TabascoJoe:
I'm trying to get rid of "tampered". I have 1.55. My bootloader is from the Google edition (black background) but my system and boot are from the stock ATT edition. I am sending back the phone to ATT today, and would like to get rid of "tampered". From my understanding the "tampered" comes from a different recovery loaded.

I'm my situation (GE bootloader, ATT system) what recovery should I use to get rid of "tampered"

Thanks
[One (M7) Original Android Development] iElvis:
HTC posts the RUUs, but the carriers develop some of it. You'd probably get more response talking to HTC; Telstra CSRs may have no idea what you're talking about.
[One (M7) Original Android Development] donmarkoni:
As I read few pages back, I see that you already flashed your phone without backing your partitions first, right?

Only option is to find nandriod backup for your phone and use it to go 100% stock. You can use this [GUIDE] Easily go back to 100% stock

P.S. I searched a bit, is this for your phone: M7 CWM Nandroid Backup / CID TELST001 / 1.29.841.2?

EDIT: ...but, as you said it yourself, it would be better to stay S-OFF, even if you sell it.
[One (M7) Original Android Development] iElvis:
Tampered should go away once you flash a new hboot, because the system check that triggers it isn't run once you're s-off. There are stickied guides on going back to stock. Be sure you follow all the instructions carefully.
[One (M7) Original Android Development] TabascoJoe:
Since I'm s-on and have the wrong hboot for my phone I guess I'm SOL with getting "tampered" off. Oh well, from what it sound like ATT doesn't put up much of a fight on a modded phone. And good news is they sent me a replacement phone already.

Cross fingers that a 1.54 s-off comes out in the next 10 minutes. :)