yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] iconspiracy:
I understand your frustration! Have you read this thread?

or have you tried the lower case p in the command ./revone -p ?
[One (M7) Original Android Development] Sloth:
lower case p always gives me an error.

Every time I got the error 1 I would just restart the process.
[One (M7) Original Android Development] iconspiracy:
When I tried the lower case p thingy I got a success message but wasn't able to get S-OFF after rebooting anyway. But I've seen some people getting it to work using the lower case p ;)
[One (M7) Original Android Development] zaphodbeeb:
did you try su, then ./revone -P?
[One (M7) Original Android Development] DeSaint2:
Run the command in succession without reboot until it goes through. If you do it like 20 times on a row and still getting it do a hard reset by holding down the power button until it restarts.
[One (M7) Original Android Development] Sloth:
I have gotten 17 Sprint phones S-OFF I was just saying those were some issues I have encountered for some.
[One (M7) Original Android Development] Golv:
Anybody with s-on and rooted trying to do backup and upload again block mmcblk0p4 (for super cid)? Or do the same with this method?

Blocks mmcblk0p3 ("pg1fs" with S-ON/OFF Switch) and mmcblk0p4 (here we find CID Data) are the same in these models ...
[One (M7) Original Android Development] andypig04:
HTC One Mini

S-OFF

Why you S-OFFed the One mini :eek:
[One (M7) Original Android Development] horsetastic:
Wont work... Those blocks are WP at very low level by HBoot.....
[One (M7) Original Android Development] iconspiracy:
I do have my mini s-offed :)

HTC One Mini

S-OFF

Kernel: 3.4.49 jmz stock

Rom: 1.22.401.1

OS: 4.2.2
[One (M7) Original Android Development] andypig04:
Uh...sorry for my English:eek:. I think I want to say "How" do you do to S-OFF your One mini ?
[One (M7) Original Android Development] iconspiracy:
Haha! It's ok! Check this thread http://xdaforums.com/showthread.php?t=2445670

HTC One Mini

S-OFF

Kernel: 3.4.49 jmz stock

Rom: 1.22.401.1

OS: 4.2.2

superCID

HTC Desire Z

S-OFF

Samsung Galaxy S3 4G

Rooted & stuff :)
[One (M7) Original Android Development] Theshawty:
[MENTION=2521652]Spartn[/MENTION] [MENTION=4124985]The War Horse[/MENTION]

Any news on either of your experiments?
[One (M7) Original Android Development] horsetastic:
I've tried almost everything you can imagine but no luck I'm afraid. Lets hope the real devs are having more luck.
[One (M7) Original Android Development] Theshawty:
I hope so too. After all, the topic read "early access preview edition" which leads me to believe they've got faaaaar more up their sleeves.
[One (M7) Original Android Development] krustypick:
I finally got it.

I did a nandroid restore to factory software.

Installed SU again

I did it on terminal on the phone and it worked, but ADB would not work from my Win 8 computer.

I am happy happy happy !!!
[One (M7) Original Android Development] horsetastic:
Tbh I don't think he changed the title after the initial release. The latest version isn't such a preview edition..... The new HBoot may never be cracked. As a few One X owners gave stated there's never been a crack for that phone and there's every chance that HTC have replicated the blocks in place on that HBoot on our phone.....

Imo I think our best hope is some way to downgrade hboot to then enable revone or moonshine again.....
[One (M7) Original Android Development] Theshawty:
Currently, my best hope is to either win a huge sum of money so I can either jump to another device, leaving HTC for good, or buy a java card with the HTC diag files on it and S-OFF the crap out of my phone, then flash a RUU, go S-ON and then S-OFF with revone just to be sure.

Either that, or hope someone in Sweden (and comfortably near me!!) buys a java card. Neither of which will of course happen. :)
[One (M7) Original Android Development] andypig04:
My device is HTC One mini 601e (HTC_621 Taiwan). Can it use this thread too?
[One (M7) Original Android Development] X46X:
If I have a S-Off, Can I flash kernel.zip in recovery (without flashing boot.img over adb)?
[One (M7) Original Android Development] sinosuke:
Look like you had some times with the HOX..yes with a S-ON HOX and no with this ONE,you don't need to do that,even with S-ON :fingers-crossed:
[One (M7) Original Android Development] X46X:
Yep, you'r right. So I don't need S-Off for flashing kernel without PC? So S-off is only for back to stock completly? Uderstand it correctly?
[One (M7) Original Android Development] sinosuke:
Yes,you don't need S-OFF . S-OFF is needed,really needed when you get boring with S-ON :p
[One (M7) Original Android Development] horsetastic:
Urm..... I wouldn't give that as advice to people wondering if they should S-OFF or not lol..... S-OFF is only really useful for people who wish to flash custom firmware, de-brand their device or even re-brand it by running an unsupported RUU as well as various other under the hood changes that it makes available. I certainly wouldn't advise anyone that was bored of their S-ON phone to S-OFF simply because of that lol....
[One (M7) Original Android Development] sinosuke:
Hehehe :cool: :cyclops:
[One (M7) Original Android Development] Spartn:
after disappointing of hex editing zip files i was playing a while trying to convince phone that it should install new ota file, no luck, then i come to an idea..install lower version stock one and try to change the official update.zip file as soon as it's downloaded to phone, but coudln't find the zip file on a phone :( but i think this is a way which could lead to downgrade of hboot

btw i think new exploit will not come for 1.54, it takes too long :( but devs could achieve radio s off, have seen that the way which is used for different htc phone
[One (M7) Original Android Development] horsetastic:
We can't radio S-OFF the One. It's mapped differently to the older devices.

I've had an idea that I think might work.... I'm going to try taking a 4.1.2 RUU, decrypting the rom.zip, replacing the HBoot with 1.54, encrypting it again then putting it back in the RUU and running it..... Perhaps if we can somehow downgrade all other partitions except HBoot revone/moonshine still might work.....

I'm not sure if it will work as I have a feeling that 1.54 HBoot will be looking for files that wont be there in the older rom.zip so it will most likely fall on its ass lol... Worth a shot though. Will let you know how it goes!
[One (M7) Original Android Development] Theshawty:
Once you download the OTA but not install it, it should be either in temp or cache.

>> Sent from the abyss <<
[One (M7) Original Android Development] Spartn:
checked, none of them had the file, created a thread for this question and some people advised to check download folder, but it was not visible this way: /download ...so it could be download folder on /sdcard/download, but did not check, if someone knows the right location of OTA file i would try something ;)

---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------

i can provide decrypted 1.20.401 or 1.28.401, if you are interested in

that was my idea, just install rom.zip (1.20 or 28) with 1.54 hboot inside, hex edit way... but was not able to pass verification after puting 1.54 inside.., but if we were able to create a rom(1.20 signed) with 1.54 hboot, then we are good to downgrade, OTA would do all for us, but problem here is that touchscreen does not work until you install rom.zip(1.20 RUU), so none of stock recovery are useable

EDIT: no need to put signed zip back to ruu, you can manually flash encrypted zip -i hope u know this :)
[One (M7) Original Android Development] horsetastic:
No worries man, I've decrypted a few myself so will mess and let you know...

Also I have an RUU utility that I've been using, does the same really as rebootRUU but for the sake of laziness I prefer it lol....
[One (M7) Original Android Development] Golv:
Touchscreen drivers are in firmware.zip in tp_SYN3202.img, we can change them from correct version...
[One (M7) Original Android Development] Theshawty:
I got my usb y cable now that I ordered last week :)

>> Sent from the abyss <<
[One (M7) Original Android Development] iconspiracy:
I think you should be able to just make sure to use the correct ROM (WWE version). Haven't seen anyone reporting using a phone from that region yet though. If you plan on keeping the bootloader unlocked i suggest not doing it yet cuz you will be stuck in a bootloop.
[One (M7) Original Android Development] horsetastic:
Just re-read the last bit you said here.... I don't think that keeping 1.54hboot inside a 1.20 RUU will allow to downgrade hboot via the OTA. At the end of the day the OTA update will still check hboot version and it wont be able to downgrade.

My hope is that if we can somehow get a modified ruu.zip/ruu.exe to flash all partitions (except hboot which it would skip) to lower version then something like moonshine might work again.... Or even revone maybe.....

I gave it a go but of course even using ruuveal, without the proper HTC encryption key it still failed.....

One thing I did think of and try was to decrypt an RUU from a different HTC device (with software supported by moonshine) edit the android-info.txt to show PN071000 etc then try to run that in the hope that, 1. being a higher HBoot version number it might let it flash and 2. even if it temporarily borked the phone the software on the phone would hopefully be able to be hacked by moonshine and S-OFF'd then I could run 1.20 RUU.exe, fix the borkedness as well as revert the hboot back to 1.44 then I could do whatever I wanted....

But of course so far I couldn't get it to work lol..... I got a success report one time but it had infact simply failed on signature so again without the right key to sign/encrypt the zip files it's not looking good.....

Actually thinking about it the hboot will be checking the device so would have to be edited also....
[One (M7) Original Android Development] Golv:
Is this USB Y cable suitable?
[One (M7) Original Android Development] Theshawty:
Mine looks exactly like that so I bet it'd work.

>> Sent from the abyss <<
[One (M7) Original Android Development] DarkAngel00:
my htco one:

m7_UL PVT SHIP S-ON RH

Hboot: 1.44.0000

radio: 4a.14.3250.13

rom android revolution hd 21.0

kernel elementalx 5.2

moved revone to data/local/tmp

on terminal emulator:

su

cd /data/local/tmp

chmod 755 revone

./revone .P

revone v0.2.1

revone failed (error code - 1)

rebooted and do from 1st step and again same error (fasboot is disabled, usb debug enabled)
[One (M7) Original Android Development] nkk71:
ARHD 21 is a 4.3 based ROM so it won't work. You need a 4.1 based ROM (possibly 4.2 COULD work) but 4.3 definitely not.
[One (M7) Original Android Development] X46X:
Hmm thank you. I still flashing kernel via adb (boot.img) and after that kernel.zip in recovery until now..F****** HOX, bad habits :eek:
[One (M7) Original Android Development] horsetastic:
For best chance of success read the Pre-S-OFF Guide in my signature.
[One (M7) Original Android Development] ky3bmu4:
I see a lot of people who are getting "Segmentation fault (core dumped)" after ./revone -s 0 -u struggling without answers

YOU SHOULD KEEP TRYING

Mine worked only from the 4th attempt. BUT IT WORKED (I am stock de-odexed 4.22. (2.24) rooted and with TWRP recovery, hboot 1.44)

I beleive it worked because I typed "su" adter the step "Now that revone has successfully prepared your device for S-OFF please open another adb shell (as per step 2) and change to the /data/local/tmp directory" as follows:

adb shell

cd /data/local/tmp

su

./revone -s 0 -u

MAYBE it was not the reason, but still I am s-off now.

Good luck to you all!
[One (M7) Original Android Development] Golv:
Yes, my new Y usb cable works fine.

Data are loaded in bootloader from GoldCard.

I propose to continue theme of downgrading HBOOT here - 1.54 Hboot S-off now possible!!!!
[One (M7) Original Android Development] horsetastic:
using a goldcard? are you saying you managed to take an sdcard, goldcard it and then using y-cable run PN07IMG.zip from that sdcard?

Or by goldcard do you mean javacard?
[One (M7) Original Android Development] Golv:
I mean GOLDCARD!

I took firmware3.09.zip renamed it PN07IMG.zip, copied into microSD (of which made ​​GoldCard), reboot into bootloader, then hboot. Phone began to scan internal memory and then it found data on microSD (now unfortunately I can't make the screen) and wrote:

HBOOT

[1] TP

[2] TRUST_ZONE

[3] CIR

[4] BOOTLOADER

[5] PG2FS_SPCUSTOM

[6] RPM

[7] SBL1

[8] SBL1

[9] SBL1

[10] SBL2

[11] SBL3

[12] ADSP

[13] RADIO_V2

Do you want to start update?

<VOL UP> Yes

<VOL DOWN> No
[One (M7) Original Android Development] horsetastic:
I'm confused what do you mean by can't make the screen? You mean you can't select an option?

and by hboot do you mean you fastboot oem rebootRUU? cuz you should just need to be in bootloader....

Could this not be simpler and work with usb-otg?

---------- Post added at 02:00 PM ---------- Previous post was at 01:53 PM ----------

Just noticed your signature says you're S-OFF..... why haven't you just flashed PN07IMG.zip using fastboot flash zip? You'll be able to do this.....
[One (M7) Original Android Development] AnumEndzeit:
No, he cant make a screenshot thats what he means. And what happens is when you boot from phone, it always checks for some kind of specifically named file incase it needs to load it. If it finds it, it IMMEDIATELY loads it. Thing is, it doesnt do any check it just loads it and runs because this was intended as HTC's fail safe for soft bricked devices. There is no RUU.exe being run, its a Goldcard (old school HTC workaround for downgrading firmware). Now, i never thought they still used that on these phones. Gotta make me one.
[One (M7) Original Android Development] deboopi2:
going back to stock / properly locked

I visited vollowing threads for going back to stock and I'm going the righ direction but I'm not yet at the finish.

http://xdaforums.com/showthread.php?p=45918866#post45918866

http://xdaforums.com/showthread.php?p=45902482#post45902482

http://xdaforums.com/showthread.php?p=45890348#post45890348

The readon why I want to back to stock is bacause I have signal problems, so when back on stock I want to return it to the shop

So at this moment I am

back at OS 4.2.2, based on firmware 2.24.401.8

relocked state

s-off

Some people say they will say no warranty because of relocked state, others say they don't mind, so I still do not know the correct answer.

Then I've heard about relocking with revone makes it locked instead of relocked, but this seems to work up to hboot 1.44.

http://xdaforums.com/showthread.php?p=43424690&highlight=relock+warranty#post43424690

http://xdaforums.com/showthread.php?p=43290421&highlight=relock+warranty#post43290421

If I look at the original page revone does not seem to work with hboot 1.54, is this still the case?

And in detail if it works and you lock the bootloader again will it then be locked or relocked.

How to lock after revons s-off; fastboot oem lock or something else.

So what should I do before returning my phone.

Leave it in s-off state or go back s-on on hboot 1.44 and s-off with revone on hboot .44, and then update uo to rom 4.2.2?

Then I will have locked system but s-off.

Or start from s-off hboot 1.54 and make it s-on but still have th relocked state.

Can someone tell me which steps to take and in what order so I can take it back to shop and get it fixed under warranty?
[One (M7) Original Android Development] horsetastic:
I thought goldcard only bypassed CID check on older phones, least it did on Desire HD when I had that...... If it bypasses all checks and it does actually work then why hasn't it been done before? It also doesn't work on HOX to downgrade I don't think....

Also this chap is S-OFF already (according to his sig) so I should assume if it has worked to downgrade his hboot then it's because he's already able to do that being S-OFF.

Not wanting to discount that this could work. Just seems unlikely that literally no-one would have tried this method yet since the One has been out, which surely if it worked must be the case if it's not posted anywhere at all. I'm thinking it was probably one of the first things tried by devs but didn't work so they moved on....

I hope I'm wrong though.

---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------

leave it S-OFF. Flash any RUU or whatever to return to stock, LEAVE IT S-OFF!!! Return phone, get it back, still S-OFF and be happy.... (they wont S-ON your phone)
[One (M7) Original Android Development] AnumEndzeit:
Yea it worked for me on my Incredible S and my Desire/HD. I could be wrong but thats my understanding. Maybe it was overlooked due to how complicated it was? Who knows. Ill see what i can get out of it.
[One (M7) Original Android Development] horsetastic:
Honestly if it does work it'll be epic.... But I'm sure it was for older phones literally to bypass CID check to allow flashing RUU's for different carriers etc. It was also part of the rooting process on the older phones.

EDIT. Looks like it used to work on the Desire to allow hboot downgrade... assuming HTC haven't totally changed things now (which they may have seeing as this method failed on the HOX to downgrade) we might be in with a shout.!
[One (M7) Original Android Development] Golv:
Yeah, I just couldn't make screenshot.

I have s-off and I can flash through fastboot oem rebootRUU, but I wanted to try this method. I am very closely following this topic and for your debate about downgrading hboot.
[One (M7) Original Android Development] horsetastic:
That's cool man. Appreciate the interest..... I've got a goldcard, I've got a phone.... I just don't have usb y or otg lol.....

Just out of interest, did you use the reverse CID generated from the phone or from the card you used? I'm thinking using a goldcard created using the phone's reverse CID would have more chance of success?
[One (M7) Original Android Development] Theshawty:
how exactly do I make a gokd card? I have a gold card IMG generated from my phones reverse CID, but what do I do then?

[MENTION=4124985]The War Horse[/MENTION]

>> Sent from the abyss <<
[One (M7) Original Android Development] horsetastic:
Get an SD card. Format it to fat 32, then open it in HexEditor on computer. But you have to open it using Open Special or similar, Open it as Physical Disk, it'll open the SD Card's img, then copy the goldcard.img and paste it over the 000 to 170 lines at the start of the SD card img.

then save it (ignor the error) then remove SD and replace, if it opens fine then you're goldcard is good to go.
[One (M7) Original Android Development] AnumEndzeit:
Edit: Ignore this.
[One (M7) Original Android Development] deboopi2:
Ok I got the message leave it s-off.

But how to proceed.

restore rom based on firware hboot 1.44

unlock

lock and see if it is locked instead of relocked

start upgrading to rom 2.24

if it does not work

restore to jboot 1.44

unlock

make if s-on (with revone)?

s-off with revone

lock

sttart upgrading

or do it in another way and whch way then?
[One (M7) Original Android Development] Theshawty:
When creating the goldcard IMG, do I use the phone's reversed CID or the sdcard's?

I have an old 2 GB sdcard and some usb reader, but I hope those will work for this.

>> Sent from the abyss <<
[One (M7) Original Android Development] horsetastic:
If I were you I would take the latest RUU I could find either unbranded or for your carrier, run it and then send the phone off. Nothing will reset the phone back to S-ON so as long as you dont it'll be fine.

well I'd try the phones CID first. use this tool then you can use reverse or normal.
[One (M7) Original Android Development] Golv:
We need CID of card, not the phone. I used DesireHD for that.

I generated CID of mmc, generated goldcard.img and patched card through SimpleGoldCard.exe (I can manually, I have enough knowledge and experience).
[One (M7) Original Android Development] horsetastic:
i dont literally mean the phones CID, I mean the mmc0 CID of the phone...... It is formatted as fat.....
[One (M7) Original Android Development] Theshawty:
Uh? Mind breaking that down in easier parts? Would HxD work as a hex editor?
[One (M7) Original Android Development] Golv:
Yes, I agree.
[One (M7) Original Android Development] jirkab:
Great, simple and absolutely functional.

Deodexed ROM 2.17.401.1 with HBOOT 1.44.0000.
[One (M7) Original Android Development] Paleryder:
Great job
[One (M7) Original Android Development] scotty1223:
awsome sauce! :cool:

after reading the first 12ish pages,i expected to have some trouble with my t mobile us phone,but it worked like a charm first shot. now all we need is a t mobile RUU so i can start trying out some others :D

the following is what worked fine for me,if it helps. im stock rooted,1.27.531.7 with supersu.

c:\miniadb_m7>[COLOR="Red"]adb push revone /data/local/tmp/[/COLOR]
3272 KB/s (646704 bytes in 0.193s)

c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
shell@android:/ $ [COLOR="red"]cd /data/local/tmp[/COLOR]
cd /data/local/tmp
shell@android:/data/local/tmp $ [COLOR="red"]chmod 755 revone[/COLOR]
chmod 755 revone
shell@android:/data/local/tmp $ [COLOR="red"]su[/COLOR]
su
root@android:/data/local/tmp # [COLOR="red"]./revone -P[/COLOR]
./revone -P
revone successful - please reboot to continue.
root@android:/data/local/tmp #

[COLOR="Blue"]*physically reboot phone(dont use adb reboot)[/COLOR]

c:\miniadb_m7>[COLOR="Red"]adb shell[/COLOR]
shell@android:/ $ [COLOR="red"]cd /data/local/tmp[/COLOR]
cd /data/local/tmp
shell@android:/data/local/tmp $ [COLOR="red"]su[/COLOR]
su
root@android:/data/local/tmp # [COLOR="red"]./revone -s 0 -u[/COLOR]
./revone -s 0 -u
revone successful.
root@android:/data/local/tmp # [COLOR="red"]exit[/COLOR]
exit
shell@android:/data/local/tmp $ [COLOR="red"]exit[/COLOR]
exit

c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(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.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off [COLOR="Blue"]<-hooray![/COLOR]
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-60fafa5b0be2807a0ad050f62f94e0010
getvar:all FAILED (unknown status code)
finished. total time: 0.087s
[One (M7) Original Android Development] groo:
Took about 10 tries, but it finally worked!
[One (M7) Original Android Development] erto90:
Do I need to be unlocked and rooted?

Inviato dal mio HTC One con Tapatalk 2
[One (M7) Original Android Development] ethan.r.besbris:
Me too! Used ADB of wifi and it worked great!
[One (M7) Original Android Development] Huey85:
All good here. Was simpler than I thought and great that it's working on ALL OS's and not just Linux. Great to see the *** TAMPERED *** status can also be removed. Might hold off on SuperCID though, seeing as some people are reporting issues with the HTC Dialer.
[One (M7) Original Android Development] x017in:
Awesome Guys, Thanks for the S-off.

however when i try to remove "tampered" sign i get the following error:

/system/bin/sh: ./revone: can't execute: Permission denied

Any help on this? I'm on ARHD 10.1, ATT HTC One with S-off & Super CID
[One (M7) Original Android Development] daddioj:
thats the way i did mine. booted in android with usb debugging on
[One (M7) Original Android Development] 215Aphillyated:
Got it to work...im also on sprint too..thanks for the info