yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] RuckusDecay:
Who are you? again, so they can answer to you. Are you paying them an hourly wage? Last time I check it's a free time of work exploit. Only smart people that understands android get to have s-off because they understand unlike some people. If you donate, it's a donation for past work not future work. I'm being polite as possible too.
[One (M7) Original Android Development] maarawoe:
I know they are doing it in their free time and I really appreciate their hard work same like I am not one of those asking them for any eta - I NEVER did so as I know it's unpredictable and it's only up to them if they will or will not work on it. My original post was meant more like "why the can't even tell if they are or are not working on to calm all the people asking them the same question on the irc". There was absolutely no offense or angryness from my side but a simple missunderstanding why there is absolutely no info (even it's bit clear due to 4.3 release)...- bad news are also news even when they are disappointing :)

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] lukode:
Hi

What about the golcard? Is really true for hboot 1.54? How many people did make this downgrade?

Thx

Enviado desde mi HTC One usando Tapatalk 4
[One (M7) Original Android Development] maarawoe:
Only the java card is working for unlocking the 1.54 hboot...

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] malachow:
Guys, one, I suppose quick, question. I want just unlock bootloader & root my One - is S-OFF needed in that case?
[One (M7) Original Android Development] psx2pal:
No, unlock your bootloader with htcdev and then install a custom rom. After this you have root without s-off.
[One (M7) Original Android Development] malachow:
Know that dude, but currently I don't want to flash any custom rom, just root the stock firmware. S-OFF needed in that case?
[One (M7) Original Android Development] drakeymcmb:
No but you will need a custom recovery like cwm or twrp
[One (M7) Original Android Development] malachow:
Yeah, also noticed that. I'm not so newbie in that kind of magic - half a year with modifying S3 makes difference. :D So, to sum up, all i need to do after getting new One is to:

1. unlock bootloader

2. flash custom recovery

3. flash root via CWM/TWRP

, right?

One more question to confirm - after that procedure I will not be able to update my One via OTA if any new software update appears?

Thank you guys for help, it clarifies me a lot. :victory:
[One (M7) Original Android Development] guyd:
Correct. The OTA update will not be able to install if you have a custom recovery.
[One (M7) Original Android Development] horsetastic:
If I were you I'd unlock bootloader, then fastboot boot custom recovery rather than flash it. Root phone then boom you're running stock rooted software :)

Though saying that if you wanted to update via OTA you also need to flash the data/preload whilst booted to recovery. Otherwise the OTA will fail when trying to patch the preloaded files that unlocking bootloader deletes. :)

sent by homing Dragon.....
[One (M7) Original Android Development] Theshawty:
[MENTION=4124985]The War Horse[/MENTION]

Aren't you gonna order a usb y cable already? ;)
[One (M7) Original Android Development] horsetastic:
Haha well actually I want to yes. But the job I do means that right now it's the end of the month money wise so I don't really have any spare cash right now lol. But as soon as I get paid I'll try to budget it in amongst all the other 'stuff' life, two daughters and a wife brings haha.

sent by homing Dragon.....
[One (M7) Original Android Development] runganwt:
I followed you guys for a while and really want to try goldcard experimental I have Y OTG cable (make myself, and it works :D) but sadly I do not have S-on phone to try :D:p:D
[One (M7) Original Android Development] horsetastic:
Haha. Yeh I wish there were more S-ON people to try more Y-Cable experiments......

sent by homing Dragon.....
[One (M7) Original Android Development] jeffjoker:
Hello,

Sorry if I ask something already there, I haven't scanned all 589 pages and the search was not really precise nor successful.

I have s-off htc one and root and all.

The only thing that I miss now is sim unlock.

How can I do that ?

(I ask this here cause this is the closest thread and where all my searches have taken me)

Does anyone know where the lock is ?

I have changed the main firmware and it s still there

Should I change the radio or something else ?

I also have a SGS3 on which I used Galaxim which worked quite well

Thanks in advance.
[One (M7) Original Android Development] Spartn:
hey guys,

i've been playing with y cable and still had one of these errors:

-checking with reboot result at the end (trying to apply encrypted RUUs)

-main version is older (fixed by editing misc partition)

-wrong model (applying developer ruu 4.3) //...this error occurs if goldcard is not really gold -mentioned for different htc models

-hboot version is older (so far no luck to bypass this checking) //.. for different HTC phones only way to bypass this step is to use exploit even with goldcard

hopefully all htc one are updated to 4.3 soon and then someone might be able to find exploit for 1.55 hboot... 1.54 seems to be not crackable :(

htc 1 : 0 dev
[One (M7) Original Android Development] horsetastic:
Simlock is something else entirely. No hack so far I'm afraid.

Who knows 1.54 hasn't been around all that long yet. There could be an exploit still. The phone is still relatively new really...

sent by homing Dragon.....
[One (M7) Original Android Development] Spartn:
hmm, 1.44 was cracked after 3 months around if i'm not mistaken and 1.54 is here around 2 so far, but it looks like there is bigger chance to focus on 1.55
[One (M7) Original Android Development] horsetastic:
I wouldn't make any estimations based on time. 1.54 may take 6 months but I doubt the devs will skip it and move to 1.55. Chances are any patches and blocks that are on 1.54 will be in every new hboot for ever more

sent by homing Dragon.....
[One (M7) Original Android Development] Jwtiyar:
i tried again many times and still Give Error code -1

i don't know whats wrong?
[One (M7) Original Android Development] Sloth:
Reboot your phone and start from the beginning again
[One (M7) Original Android Development] Jwtiyar:
i did so many times.
[One (M7) Original Android Development] Sloth:
That has worked for me every time I get error 1
[One (M7) Original Android Development] horsetastic:
If I were you I'd read the guide in my signature. It will ensure you have the best chance of succeeding with this procedure.

sent by homing Dragon.....
[One (M7) Original Android Development] Jwtiyar:
i have elegancia ROM sense 5 , JB 4.3 , base 3.17
[One (M7) Original Android Development] Theshawty:
revone doesn't quite work (if at all) with the 4.3 bases. Go back to a 4.2.2 Sense based ROM.
[One (M7) Original Android Development] horsetastic:
You should follow the guide step for step to ensure best chance of success. Number 1 on the guide states 4.1 stock software.... Custom Roms and esspecially 4.3 software aren't advised

sent by homing Dragon.....
[One (M7) Original Android Development] Jwtiyar:
thank you i will get back to 4.2.2 .

thank you very much , its S-Off now .
[One (M7) Original Android Development] horsetastic:
No worries man. A lot of people think us old hats are only here to jeer and mock but most of us do just want to help.

Glad you got there mate.

sent by homing Dragon.....
[One (M7) Original Android Development] bjg222:
Ok, I've tried and retried this a bunch of times and must be missing something. I can't get revone to work, and after trying a variety of troubleshooting mentioned in previous posts in this thread (I'll admit I haven't read all 591 pages... But searching led to some things), I don't really know why. If anybody can help, I'd be very thankful!

HTC One Dev Edition

M7-UL PVT SHIP S-ON RH

HBOOT-1.44.0000

CID BS_US001

recovery TWRP (though tried with stock recovery, too)

Android 4.1.2 (1.29.1540.17)

rooted

Shell output:

C:\>adb push revone /data/local/tmp
3596 KB/s (648208 bytes in 0.176s)

C:\>adb shell
shell@android:/ $ cd /data/local/tmp
cd /data/local/tmp
shell@android:/data/local/tmp $ cd /data/local/tmp
cd /data/local/tmp
shell@android:/data/local/tmp $ ls
ls
revone
shell@android:/data/local/tmp $ su
su
root@android:/data/local/tmp # chmod 755 revone
chmod 755 revone
root@android:/data/local/tmp # ./revone -P
./revone -P
revone v0.2.1

revone successful - please reboot to continue.
root@android:/data/local/tmp # exit
exit
shell@android:/data/local/tmp $ exit
exit

C:\>adb shell
shell@android:/ $ su
su
root@android:/ # cd /data/local/tmp
cd /data/local/tmp
root@android:/data/local/tmp # ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1

revone failed (error code = -1)
255|root@android:/data/local/tmp # exit
exit
255|shell@android:/ $ exit
exit

I've tried a number reboots, full power down & wait 60 seconds before power on, rooted, unrooted, TWRP, stock recovery... I've read the Pre-S-Off guide... Am I missing something, or is my phone just one of those that it's not going to work on?

Thanks!
[One (M7) Original Android Development] iconspiracy:
Did you try running the commands from terminal emulator on your rooted phone? Somehow it worked for me after failure running the commands from my computer :P

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] horsetastic:
Hey. Check the date of your hboot when you reboot to bootloader. You could have a patched hboot.

sent by homing Dragon.....
[One (M7) Original Android Development] bjg222:
Hmm, didn't try that, I'll give it a try.

EDIT: no luck, but thanks for the suggestion

Jun 7 2013 22:07:59:-1

I'll try to downgrade it, see if that works... Couple questions first: I have the dev ed, and all the downgrade guides talk about ATT or TMo versions (which is why I thought I was safe initially). Do I still need to go through the steps of relocking & RUUing? Can I simply sub the appropriate DE RUU/nandroid files?
[One (M7) Original Android Development] Theshawty:
[MENTION=4124985]The War Horse[/MENTION] Do you think it would be possible to S-OFF with one of these? If yes, I might just order one because I'm desperate.. lol.

http://www.fonefunshop.co.uk/cable_picker/97595_IR-Key_Suite.html
[One (M7) Original Android Development] haenraets:
I read somewhere it was not possible. I also thought about ordering one until I read that.
[One (M7) Original Android Development] Theshawty:
Hmm, hopefully it's not true :( Btw, my One isn't an 801e, it's an 801n if it makes any difference. :p
[One (M7) Original Android Development] horsetastic:
June will be patched so yes you should try to downgrade somehow..... modifying the tmo version might be the best bet.

These absolutely work though they're not cheap. it basically contains HTC's private keys in order to completely modify your phone I think....
[One (M7) Original Android Development] Theshawty:
So they actually work? Hmm.... :D

I need to ask around a bit tomorrow because if it does work I'll buy one. I am that desperate.

EDIT: I see it works for the 801e, but does it work with the LTE variant, the 801n?
[One (M7) Original Android Development] csetera:
I'm stuck trying to get past the -1 error running revone. I've tried 4 or 5 times with various combinations of reboot attempts. I'm on HBOOT 1.44 from March 2013, so I should be able to get it to go and the "-P" option works fine for me. Any hints or tips? It seems like I'm close, but I'm clearly doing something wrong.

NOTE: After the failed attempt with the "-s 0 -u" command, if I reboot I get strange permission denied errors when trying to do anything with /data/local/tmp folder (even after su). I'm not sure if that helps anyone give me further direction?

Thanks,

Craig
[One (M7) Original Android Development] AnumEndzeit:
I dont think it matters. The variants are different hardware wise but software wise i don't think hboots come with anything extra just to add LTE.
[One (M7) Original Android Development] Theshawty:
Great. Looks like I'll be ordering one later :)

>> Sent from the abyss <<
[One (M7) Original Android Development] gartner83:
delete
[One (M7) Original Android Development] horsetastic:
Read my guide in my signature. That is my advice :)

Go for it man. Cheapest I could find was £50 though....

sent by homing Dragon.....
[One (M7) Original Android Development] maarawoe:
The comment on the product page says that they tested it on 1.54 with no luck.... :(
[One (M7) Original Android Development] Theshawty:
Crap!! :(

>> Sent from the abyss <<
[One (M7) Original Android Development] maarawoe:
Yes... :(

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] Theshawty:
I also confirmed with fonefunshop that the IR key method doesn't work.
[One (M7) Original Android Development] horsetastic:
Ahh really? Man they really should state more clearly on their site that it doesn't work with newer hboot versions. Simply says it works with HTC One M7. Bastards lol

sent by homing Dragon.....
[One (M7) Original Android Development] prunzzz:
Hey,

Actually from past month i was not able to keep track on posts in this thread due to my studies.

I just wanted to know that, is there anyway found out by now, by smart people from XDA to s-OFF htc one running HBOOT 1.55???

Pls reply kindly(dont ask me to read past months post)

:o
[One (M7) Original Android Development] Theshawty:
Agreed. I was this close to buying one until I read the comments and decided to ask them myself..

Only known method is java card.
[One (M7) Original Android Development] skulldreamz:
Unfortunately not yet; still rooting for you guys :)
[One (M7) Original Android Development] prunzzz:
Hey can u pls explain wats that?

I know the rules of this forum

I used to be here regularly

But now i want to get back fast so pls kindly help and tell me, what exactly is java card?
[One (M7) Original Android Development] Theshawty:
A java card is basically an sd card with a microprocessor. It contains HTC's private diag files. Repair shops use these to gain S-OFF so they can fully restore a device.
[One (M7) Original Android Development] prunzzz:
Thanks a lot man!!!:thumbup:
[One (M7) Original Android Development] Ciebiada:
You don't have to be Sherlock Holmes to figure out, by looking at 2-3 latest pages, if there is s-off method already or not.
[One (M7) Original Android Development] csetera:
I'm happy to report that I was able to gain S-Off after a bit of fighting. I was attempting to follow your directions, but holding the power off for 15 seconds did not work at all. It would just sit on the dialog until I released, but not actually reboot. On a whim, I uninstalled https://play.google.com/store/apps/details?id=me.timos.htconerw and restarted. Without that module installed, I was able to follow your instructions and get beyond the -1 error I was getting consistently.

I'm not sure if others may run into this as well, but it may be worth adding to your instructions to uninstall anything that is enabling write access to the system partition.

Thanks!

Craig
[One (M7) Original Android Development] AnumEndzeit:
Huh, maybe it would be a good idea for people to put their devices into safe mode before doing anything.
[One (M7) Original Android Development] whiper:
Is it possible to use revone from recovery?

I'm on 1.54 s-on with unlocked bootloader.

I'm able to write hboot from recovery via dd

dd if=/dev/block/mmcblk0p12 of=/sdcard/p12_bak.img

4161+0 records in

4161+0 records out

2130432 bytes (2.0MB) copied, 0.204151 seconds, 10.0MB/s

dd if=/sdcard/p12_bak.img of=/dev/block/mmcblk0p12

4161+0 records in

4161+0 records out

2130432 bytes (2.0MB) copied, 0.204456 seconds, 9.9MB/s

- I wanted to downgrade hboot to 1.44

- boot into recovery

- use revone to s-off

- flash 4.3 gpe firmware

and be lucky. Will this work? Or can i modify any other partition data to get s-off?
[One (M7) Original Android Development] russel5:
Try to downgrade and tell us.
[One (M7) Original Android Development] Theshawty:
I think it would work. Revone requires adb and you have adb access in the recovery. I don't think the downgrade will work though.
[One (M7) Original Android Development] horsetastic:
Nope. Won't work. Have tried this as well as many other things myself. P12 is wp beyond the power of busybox or recovery.

sent by homing Dragon.....
[One (M7) Original Android Development] whiper:
Why it shouldn't work?

Writing my own backup works

dd if=/sdcard/p12_bak.img of=/dev/block/mmcblk0p12

4161+0 records in

4161+0 records out

2130432 bytes (2.0MB) copied, 0.204456 seconds, 9.9MB/s

I'm not sure if writing only older hboot version will work or if i have to flash sbl too
[One (M7) Original Android Development] Theshawty:
So, in the bootloader it states you're 1.44? IIRC, the hboot flash is two steps where the second flash occurs when you reboot the phone.
[One (M7) Original Android Development] whiper:
No, i did not flash 1.44 yet. I flashed my own 1.54 backup to test if i can flash hboot.

I flashed via dd from recovery, directly, not with fastboot. Fastboot does not work because with s-on i cannot flash unsigned zips
[One (M7) Original Android Development] EtherealRemnant:
It will fail if you try to flash 1.44 but you're more than welcome to try.
[One (M7) Original Android Development] Theshawty:
Well of course you can flash 1.54 if you're on 1.54, if it's unmodified. It's thew downgrading bit that isn't possible because the hboot doesn't allow it. We haven't yet found a way to somehow trick the process.
[One (M7) Original Android Development] maarawoe:
Why dd'ed backup of 1.44 can't be dd'ed same like the 1.54 backup of the partition above?

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] Theshawty:
Because 1.54 doesn't allow downgrading.
[One (M7) Original Android Development] maarawoe:
I know it doesn't bud dd also goes through some check? dd is a blind write and if you are able to wriite backup of 1.54 image of the partition, there shouldn't be much difference in writing 1.44 image or there is?
[One (M7) Original Android Development] whiper:
Maybe I try to flash 1.44, read it out and reflash my backup.

After that I can compare if it was possible to flash 1.44.

If it works i'm not sure if i should try to reboot.

Knows anyone if it's possible to exchange hboot partition only?
[One (M7) Original Android Development] Theshawty:
There is no known way of downgrading the hboot without S-OFF. We have tried all known ways such as dd flashing..
[One (M7) Original Android Development] maarawoe:
Thats what I am asking above :))
[One (M7) Original Android Development] zaphodbeeb:
bingo, the penny has dropped. Mission accomplished. Message sent.
[One (M7) Original Android Development] whiper:
I never read this. I always read about flashing from fastboot. I found no example where someone with unlocked bootloader and s-on tried to write to mmcblk0p12. I tried to write my own backup, this worked without getting an error. If dd fails i would expect an error like permission denied. Can you show me an example?
[One (M7) Original Android Development] Theshawty:
You said you flashed your own backup, which was 1.54, right on top of 1.54. This I don't deny because it works. What I say don't work is downgrading the hboot, from say 1.54 to 1.44 because the security checks will notice it's older and simply won't flash it. S-OFF disables these checks completely.

You're free to try to flash 1.44 through dd over 1.54, but it won't work.
[One (M7) Original Android Development] iElvis:
This thread is almost 600 pages long. It's safe to assume the obvious stuff has all been tried many, many times. Let's keep the wheel reinventing to a minimum,
[One (M7) Original Android Development] russel5:
Please anyone who have S-ON try flash this file via dd commands on mmcblk0p12

And post results. Thanks.
[One (M7) Original Android Development] Theshawty:
Won't render a brick, will it? What does it do and what partition should it be flashed to?

(also, it's dd of if to flash, right, and not dd if of?)
[One (M7) Original Android Development] russel5:
just flash. with your S-ON you not brick your phone.

this is hboot and flash it on mmcblk0p12

put this file in sdcard then enter command in terminal or from your comp (need su)

dd if=/sdcard/test1.img of=/dev/block/mmcblk0p12
[One (M7) Original Android Development] Theshawty:
D:\Nedladdat\Chrome Downloads\HTC One>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
InsertCoin@/# su
su
InsertCoin@/# dd if=/sdcard/test1.img of=/dev/block/mmcblk0p12
dd if=/sdcard/test1.img of=/dev/block/mmcblk0p12
4161+0 records in
4161+0 records out
2130432 bytes transferred in 0.238 secs (8951394 bytes/sec)

What was it supposed to do? Nothing seemed to happen.
[One (M7) Original Android Development] ParanormalBat:
I think hboot version is supposed to change...
[One (M7) Original Android Development] russel5:
holy sh*t you are not joking

this file flashed?????????

no errors????????
[One (M7) Original Android Development] horsetastic:
I'm not being funny here, but am I the only one that's thinking well he flashed 1.54 hboot (dd'd) over a write protected 1.54 hboot..... It blatently didn't even write, he just insanely thinks that it did even though he was already on 1.54 so can't actually check at all in any way lol....

I can tell everyone right now that mmcblk0p12, hboot partition is WP unless you're S-OFF. That means that regardless of what you try to do to the binary image it WILL NOT ALTER IT AT ALL!!!

I'm pretty certain that every partition from mmcblk0 to mmcblk0p14 or something are completely untouchable regardless of what you try to do (unless you're S-OFF of course!)

---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------

No it didn't flash, it didn't do anything.

p12 is WP.....
[One (M7) Original Android Development] Theshawty:
No errors. What did it do? I don't think it changed becaused my hboot is still 1.54.
[One (M7) Original Android Development] russel5:
yes but no errors. in log you see that file was flashed
[One (M7) Original Android Development] horsetastic:
It didn't do anything man. Trust me!

I can tell everyone now 100% that you cannot dd, flash to, delete or anything else you might think to mmcblk0p12.

I personally tried ages ago even chmoding mmcblk0p12, chowning it, deleting it, editing it..... It's WP! YOU CAN'T CHANGE IT!!!!
[One (M7) Original Android Development] Theshawty:
What was it supposed to do? I don't recognize any changes whatsoever.

I suspected as much. And you if anyone know this is how it is. I remember when you tried literally every flash method under the sun :P
[One (M7) Original Android Development] horsetastic:
No it wasn't.... TRUST ME!

but just for a laugh as everyone here seems to be ignoring me get him to dd if=dev/block/mmcblk0p12 of=sdcard/hboot..... and see what he says the hboot number is......

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

Exactly man. I have personally tried pretty much every single thinkable method of gaining either SuperCID or S-OFF on 1.54 HBoot.... NOTHING WORKS!
[One (M7) Original Android Development] russel5:
ok. how i make this file.

first i make a realy hboot1.54 backup, save this file in comp

second i make a backup of hboot 1.44, save in comp

Then i open 1.54 in HeX editor and copy a few code

Then i open 1.44 in HeX and paste code and change version on 1.54

You flashed hboot 1.44 but it shows 1.54

How you try revone or download nandroid backup of 1.29.401.12 version flash and try.

If hboot sector have WP this is wont work even in log success flashing

Try and cross your fingers!
[One (M7) Original Android Development] horsetastic:
Look just stop please. This has been tried and tried. Just listen to me!! I'm not being a **** head. I'm telling you it's a waste of time. It DID NOT CHANGE ANYTHING! Nothing you can think of hasn't been thought of or tried already.