yashsingh1/xdaforums huggingface dataset:
[Sprint HTC EVO 4G LTE] stanglifemike:
Closeone is an amazing asset to the Android community, this isn't his first rodeo!!! I can't wait for the LiveCD!!! Totally sucks not being s-off as I'm used to with my Evo 4G and Evo 3D. Not a HUGE difference many will say, but not being able to flash radios and having to be precocious when flashing kernals really sucks!!! Thanks to everyone involved in making this a reality for the majority of us Evo LTE owners!!!!!!
[Sprint HTC EVO 4G LTE] evoforevo:
good for u man i will still wait for closeone, to bring it out prime time when he feels it's ready.
[Sprint HTC EVO 4G LTE] Ladicx:
Yars tool is very solid too. I used it a week ago via unbuntu live cd and have been enjoying S-off ever since. I know yar and close have worked together on this project so I'm sure closes live cd will be awesome.

Sounds silly but almost wish I could try it again.

Sent from my EVO using Xparent Blue Tapatalk 2
[Sprint HTC EVO 4G LTE] evoforevo:
i try it out on Saturday and I just couldn't get the ubuntu command to work for me. If someone can make a you tube video that will be Awesome.
[Sprint HTC EVO 4G LTE] LadyX:
S-OFF for HBOOT 1.15 & 1.19 COMING SOON!!

Deleted.
[Sprint HTC EVO 4G LTE] fltinstructor:
Linky not worky for me.
[Sprint HTC EVO 4G LTE] DisplacedMic:
just replace the thread number with 33471597

the link is condensed - hence the series of elipses in the middle of it

:o

actually, here's the link
[Sprint HTC EVO 4G LTE] yarrimapirate:
I think it's admirable that you guys are looking to further evolve the process, but perhaps you could expound on the "massive issues" presented? Sorry people somehow arrived in your IRC looking for help; I think we've done a fine job supporting people here. As far as I'm aware, we've had no unrecoverable phones here and the success rates for people who follow directions or use the existing tools are very high.

Since you apparently don't contribute to XDA (unless I'm reading the text of your post incorrectly) it falls on us to continue to support and evolve this method until such a time as it is no longer necessary.
[Sprint HTC EVO 4G LTE] fltinstructor:
I actually saw her original post. Just pointing out the broken link. Thanks for that.
[Sprint HTC EVO 4G LTE] LadyX:
I am posting this update to let people know that a tool is coming so these steps will no longer be necessary. We don't support our tools (which are directly linked to in the OP) via XDA because of the number of devices that we build our tools for. It's better to have a central place for our instructions and downloads - that is our website. Also we're not "evolving" the process posted in the OP - we're putting out a new version of our tools which this OP is using which directly renders the downgrade method unnecessary.

Thanks! I've fixed it. Hyperlink didn't like copy / paste apparently.
[Sprint HTC EVO 4G LTE] il Duce:
Sorry to sound like a dink, I appreciate your team's work (used to s off my evo 3d) but to imply there have been bricks in someone else's thread solely for the purpose of plugging your tool is kinda shady.

The ppl in this thread have s offed a load of phones and I believe without actually bricking anyone.

If you want to make a thread for your tool, great. I'm sure it will be used by the many.

But don't come on xda and say you're not on xda to advertise your tool. It's simply not true and it's uncalled for.
[Sprint HTC EVO 4G LTE] bigdee1974:
+1. I am a success story with no linux experience but accomplished s-off by simply following the great directions of Yar and Mac. And by the way, I did get hung up a couple of times but I never came close to worrying about bricking my phone. And furthermore, that is what insurance is for. ;)
[Sprint HTC EVO 4G LTE] globatron:
I think you are missing the point. The reason for the post was to avoid those who do not have the experience necessary to carry out the procedure given in the OP ( despite all of the warnings) from doing so and getting stuck in a situation from which they are unable to recover. The may have followed directions incorrectly and had this consequence, we do not know. What we do know is that there have been a considerable number of people coming to our support channel looking for help in such situations and we simply cannot help them this also takes time away from supporting our tools and from our development efforts.

Hopefully these have all found the support that they need from the people involved in writing and supporting this thread and have recovered from the situations they found themselves in, but certainly a number of the examples and descriptions I have seen that did not look at all promising.

The fact of the matter is that we have a newer tool being released in a few days that does not have the same inherent risk and we would prefer that our tools be used with something that we can stand over and have verified as safe and working.

This is what led to the post, not any need to promote the our tools which we believe stand on their own merit.
[Sprint HTC EVO 4G LTE] bigdee1974:
Release your tools but don't make it sound like your tool is the greatest thing since slice bread. Before this thread there was no mention of this in the works. I, personally, would greatly appreciate your tool but people brick there phones all the time just because they don't follow directions for the simplest tasks. It is their own fault and risk. We all know that there is a possibility to brick your phone or even boot loop (mild case scenario) when flashing or mod(ing) your phone. It just sounds like you are saying "mines is better than yours" and don't use this one. This development serves a great purpose and should be respected for such.
[Sprint HTC EVO 4G LTE] globatron:
I am not going to enter into a flaming contest, I was simply explaining why we posted in the thread in the first place. If people think what was posted was inappropriate by all means request that it be deleted from the thread.
[Sprint HTC EVO 4G LTE] yarrimapirate:
This is totally understandable, I do hope that you've been referring them back here for support, as up until now this project has really been a separate entity from your team's endeavors.

My understanding is that so far, we haven't left anyone on the table with a nonrecoverable phone. The process we use is VERY forgiving for mistakes. If you have anyone with problems visit your IRC channel, PLEASE refer them back here. Despite what your impressions may be, this process is mature and reasonably safe. There is a Linux based tool that automates it as well, and that tool is still under active development. Fuses has already merged one of my pull requests to the main trunk of emmc_recover, and I have another fork I plan to submit as well.

I think perhaps there was a PR failure in the initial posts, coupled with the fact that people have asked your team for support in a process/tool that you haven't developed. I for one, don't have any ego tied up in this and fully support any attempt to make S-OFF doable for everyone, so long as the efforts of everyone involved are acknowledged, including all of the XDA users who bravely bricked their phones using this method and reported back to this thread. Cutting the HBoot downgrade out of the process will certainly streamline matters; but I suspect I know how you plan to achieve this and that most definitely builds on knowledge acquired through this community's efforts.

In the end, we're all aiming for the same goal here. So I ask, how can I/we help you?
[Sprint HTC EVO 4G LTE] bigdee1974:
Not flaming just letting you know what your words suggest. I think it would of been better said, "we have a tool that will also work" rather than suggesting that this method of obtaing s-off is bricking peoples phones. Like I said in the previous post, I look forward to one day possibly utilizing your tool - if you will allow me to. :fingers-crossed:
[Sprint HTC EVO 4G LTE] LadyX:
I also just want to point out that it is OUR TOOLS linked in the OP - that is why I responded. I also PM'd the OP as well letting him know about the new release AND the problems we're seeing. Flame all you want kids, we're just trying to help people be informed and have all the options at their disposal. We took this method instead of asking the OP to remove references to our tools they used in a way that we have not tested and without our permission.
[Sprint HTC EVO 4G LTE] LadyX:
My post has been deleted. It's clear the intent was taken incorrectly. All people we see with downgrade issues will be directed to contact you or the OP directly and we will not support their devices for any S-OFF procedure in the future.
[Sprint HTC EVO 4G LTE] yarrimapirate:
I just checked the OP, last edited on the 23rd. It has no link to anything of yours as far as I can see.

Mac is around I think, but hasn't been active in this thread for awhile. I have taken over stewardship of this thread for the most part, along with other users who have successfully performed the downgrade. Would you be so kind as to forward the PM you sent Mac to me? I'd like to know if you are seeing issues that we have not yet tackled here.

Thanks.

EDIT: Our posts crossed. I just read your above post. Thanks for referring support to me. I'm sorry if any bad blood has been created, as this was not my intention.
[Sprint HTC EVO 4G LTE] bigdee1974:
Understood and once again, I am not flaming, just trying to make clear that this method does work if you follow directions and read through the countless threads to help you get the results you are looking for. I humbly bow out and appreciate your developments. And thank you in advance for your works and Yar and Mac for their hard work.
[Sprint HTC EVO 4G LTE] il Duce:
I hear you, but you've handled it wrong. I agree your team stands on it's own merits, you're development is well known. Release your tools when you wish, but do so as it should be, in your own thread.

I'm not a flaming kid, I'm a forum moderator. Your tools are gpl licensed I assume? I'm sure that means it's ok to build upon them. The emmc recover used here has been modified and submitted upstream to you. I also imagine your tools are like any great software, built upon the work of many.

Your team can stop posting here now, this thread is about the methods explained in the op, and it's partially about the script offshoot in another thread. It is not about your tool. Thank you for your work, the community will benefit greatly when this new tool is released.
[Sprint HTC EVO 4G LTE] baknblack:
I have no stake in any of this and if you consider someone 53 years old a kid, then thanks I guess. I highly respect what your team has accomplished. I used your tool to get soff when it was 1st released. My only question for your team. Since you come to xda to promote your tool. Would it have killed one of you to drop in and tell the hundreds of users stuck without soff that it was being worked on?
[Sprint HTC EVO 4G LTE] yarrimapirate:
Just for fun... Here's a proof of concept.
[Sprint HTC EVO 4G LTE] SouL Shadow:
Wow, I get sidetracked by a hurricane and miss all the fun!

Ok, first off, I believe the item in the op being linked to is the lteUnbricker. Although it links to the page, not the file directly.

Second, this thread is all about sharing knowledge with the community. Someone made a discovery and shared. It then turned in to a few projects (the downgrade tool, the live cd). And in the process there have been many successful people who in turn have helped many other people.

Third, while I can't speak for anyone else, I see great potential in the methods discovered here, beyond a means to s-off. I can see creating a powerful diagnostic and recovery tool for soft bricked evo lte's. Also, because this works on such a low level with snapdragon s4 based phones, it should easily be expanded to help fix many other devices. (****AFTER proper testing****)

Finally, it should be noted that this process to facilitate s-off will likely continue to work, even if newer hboot exploits are found and subsequently patched by HTC. (While the method used here to soft brick can be patched easily, it's unlikely they would bother given that there are many other ways to force a soft brick)

Of course, the best approach might be to skip the downgrade altogether and just use the dl mode to directly flash the location that holds the security bits... anyone care to point me to that location?

-SLS-
[Sprint HTC EVO 4G LTE] wwjoshdew:
You could NOT have worded that any better... BRAVO!!
[Sprint HTC EVO 4G LTE] cgrimm9:
I got into a little hickup on closeonex alpha of the live cd he is working on both yar and close got me back up and running in no time I stand behind them and this thread. I believe you fallow directions this is really not hard at all. this is coming out of a guy who is inexperienced at this. just know how to fallow directions.
[Sprint HTC EVO 4G LTE] yarrimapirate:
This where I see things heading as well. I'm already in touch with a few of the OneX guys about using some of what we've worked on to help those folks with unbricking improperly flashed devices.

I've used donation money people have sent to pick up a bricked OneX and I'm looking for a bricked Evo as well.
[Sprint HTC EVO 4G LTE] benny3:
Pirate Look here http://xdaforums.com/showpost.php?p=33216491&postcount=10
[Sprint HTC EVO 4G LTE] SouL Shadow:
Is it a OneX or OneXL? Only reason i ask is because the partition layout is different between the two.
[Sprint HTC EVO 4G LTE] yarrimapirate:
OneXL
[Sprint HTC EVO 4G LTE] Mac_Gyver:
Agreed on many points. This could potentially work on most HTC phones, for for that matter, Qualcomm devices in a similar CPU generation.

I am not sure if you can access the @secu_flag from QC DOWNLOAD MODE. The trick to this is through what Team Unlimited does in LazyPanda and their subsequent tool. It might be really easy, who knows. Haven't had much time to wireshark USB traffic and analyze it ;) It's a bit chatty.
[Sprint HTC EVO 4G LTE] SouL Shadow:
i guess the first question is where is the secu_flag, or whatever they modify, stored. knowing that an RUU does NOT reset s-on eliminates over half the partitions. a few others can also be eliminated because they are either blank or known to be used for another purpose. this leaves only about 10 partitions (maybe less, don't have my list in front of me right now). I think the easiest way would be to pull images of each partition, one while s-on and one while s-off, then compare to see what is different.

as to other qualcomm devices, the SGS3 uses the same Snapdragon S4 SoC (msm8690). Everything prior to the apps-pbl (hboot on htc devices, aboot on samsung) is basicly the same, including dl mode. however samsung and htc might have made slight changes, beyond simply adding their own crypo certs to the binaries.

so far i think the htc oneXL would be the only other viable device to apply these methods and tools.
[Sprint HTC EVO 4G LTE] Mac_Gyver:
I know people have done diffs on all of the eMMC partitions but my understanding is that secu_flag is stored in 'radio memory' which is not necessarily part of eMMC partitions (mmcblkXpX). I believe there are 3 types of storage total on EVO LTE. But writing this post and thinking about going S-ON/OFF makes me wonder... The easiest place to check would be the source code for fastboot. Fastboot can write 'secure on' so it can access that area. Of course unless it just writes to a temp memory which gets written elsewhere :) My understanding, and anyone can correct me if I'm wrong, is that radio sits nearly at the top of the security chain and hboot (newer versions) protect simlock and secu_flag data.

<http://xdaforums.com/showpost.php?p=26958455&postcount=2495> actually has some good ways to get shell to talk to radio (there's an even better one online about talking to the radio) echoing rtask C should not work anymore but I think there are a couple of ways to get it to work. But you do need a lower HBOOT or some other sneaky way :) I've played around with QPST and QxDM but nothing too promising. You can query a lot but can't write secuflag.

Yeah, I hear that HTC could do a lot more to leverage the crypto craziness that msm8960 can do. :)

Yeah, I do think that since One X is nearly a clone of this guy that it's a great contender! reading about One X is what got me going on the downgrade in the first place.
[Sprint HTC EVO 4G LTE] Mac_Gyver:
I think the best tool for all of this would be something that uses parts of relevant adb code and fastboot code to leverage the USB modules. This way we can cut out adb/fastboot and just have 1 binary OR just a shell script that does what we need :)
[Sprint HTC EVO 4G LTE] RHall1340:
This is my biggest gripe. Anyone inquiring to the Lazy Panda folks about a new s-off method were often kicked from their channels and told to not ask about it. If they truly have a risk free way of doing this in the works, it really sucks that they couldn't have given people a heads up. I understand the flood of people asking about it if you do, but honestly those of us who WERE s-on and are now s-off felt like we had no other choice but to take this risk if we wanted to be s-off. By being so secretive the LP folks forced a lot of people to go through this method. I would have certainly waited, but not knowing if anything was even being worked on made me come here.

The whining about people coming to their IRC and asking about it seems a bit odd. Copy and paste a standard reply.. 'We aren't involved, go here: "... how difficult is that? To say it takes away from development time is absurd. They had no idea the LP folks were working on anything anyway. If the folks involved here were made aware at the very least of the LP folks working on a solution they may not have wasted their time and effort on this (I am glad they did though!).

That being said I appreciate the efforts of both groups. One group has given us a way of s-off when we had no other options, the other might provide a risk free way of doing it. Lets keep things respectful between the groups, this isn't a contest.
[Sprint HTC EVO 4G LTE] globatron:
Ok, this is the one and only time I will say this although it is off topic for this thread.

Exploit finding is not an exact science, which literally means that I don't have anything to offer you unless we find something and it is viable.

People were kicked off #juopunutbear because #juopunutbear is a support channel, and one of the primary rules is that we do not talk about future plans, so as not to give people false hope.

Working on a device mean absolutely nothing in terms of whether or not anything will be forthcoming it simply means that we are looking at a device, we do not give false promises of providing something when we simply do not know what may or may not work. It is as simple as that. In this instance we have decided to say that we have something viable because as of a few days ago we do.

Asking for release dates or information about new releases has always been and will continue to be off topic and a kicking offence in our support channels as people would see if they read the topic on joining. We will release when our tools have beed sufficiently tested and are ready.
[Sprint HTC EVO 4G LTE] Zodiac13:
ok so i did the script version and it was doing it's thing and then got stuck on cannot reset device timed out.

so I searched and found that people would then go to step 11 of the manual version. so I downloaded all the files on that thread and started at step 11.

took some time but managed to step 18. it flashed the 1k file but i never got a charge light to come on :(

my proper disk was dev/sdc so i did the dev/sdc12 for the hboot1.12 and dev/sdc4 for restoring block 4 but no light no booting up nothing.

i tried running sudo ./dg112.sh -r, sudo ./dg112.sh --r, sudo ./dg112.sh -unbrick, sudo ./dg112.sh --unbrick, -r, --r, -unbrick, and --unbrick but they all give me the same thing "command not found"

oh also the bakp4 file i used the one made from the original script version first, and after that didnt work I used the one found on the manual version thread.

need help please :/
[Sprint HTC EVO 4G LTE] yarrimapirate:
Try holding the power button down for longer than 30 seconds if you haven't already.
[Sprint HTC EVO 4G LTE] Zodiac13:
tried it and still no go

if i restart at step 11 this is what i'm getting when i push the 1.12

ubuntu@ubuntu:~/Desktop/evo/lte$ sudo modprobe -r qcserialubuntu@ubuntu:~/Desktop/evo/lte$ sudo mknod /dev/ttyUSB0 c 188 0ubuntu@ubuntu:~/Desktop/evo/lte$ sudo ./emmc_recover_new -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576

================= emmc_recover 0.3 alpha 2 ==========================

Using chunksize 24576

Messing up with device /dev/sdc12, ARE YOU SURE?

CTRL+C if not, ENTER to continue

Ok, ready to flash

Filesize:	1047808

Chunksize is:	24576

Cycle count is: 43.135417

Press ENTER if everything is correct, CTRL+C if not

Ready to write 24576 bytes

Resetting device

Cannot reset device

Reset command sent

Waiting device /dev/sdc12.......

Found device!

Writing 24576 bytes to offset 0x00000000

Waiting mode-switch

Device changed mode

Detected mode-switch

Ready to write 24576 bytes

Resetting device

Reset command sent

Waiting device /dev/sdc12.......

Found device!

Writing 24576 bytes to offset 0x00006000

Waiting mode-switch

Device changed mode

Detected mode-switch

Ready to write 24576 bytes

Resetting device

Reset command sent

Waiting device /dev/sdc12.......

Found device!

Writing 24576 bytes to offset 0x0000C000

Waiting mode-switch

Device changed mode

Detected mode-switch

Ready to write 24576 bytes

Resetting device

Reset command sent

Waiting device /dev/sdc12.......

Found device!

Writing 24576 bytes to offset 0x00012000

Waiting mode-switch

Device changed mode

Detected mode-switch

Ready to write 24576 bytes

Resetting device

Cannot reset device

Reset command sent

Waiting device /dev/sdc12.......

Found device!

Writing 24576 bytes to offset 0x00018000

Waiting mode-switch

Device changed mode

Detected mode-switch

Ready to write 24576 bytes

Resetting device

Reset command sent

Waiting device /dev/sdc12.......

Found device!

Writing 24576 bytes to offset 0x0001E000

Waiting mode-switch

Device changed mode

Failed to detect device in dload-mode

ubuntu@ubuntu:~/Desktop/evo/lte$ sudo modprobe -r qcserial

ubuntu@ubuntu:~/Desktop/evo/lte$ sudo mknod /dev/ttyUSB0 c 188 0

ubuntu@ubuntu:~/Desktop/evo/lte$ sudo ./emmc_recover_new -f ./bakp4 -d /dev/sdc4 -c 24576

================= emmc_recover 0.3 alpha 2 ==========================

Using chunksize 24576

Messing up with device /dev/sdc4, ARE YOU SURE?

CTRL+C if not, ENTER to continue

Ok, ready to flash

Filesize:	1024

Chunksize is:	24576

Cycle count is: 0.541667

Press ENTER if everything is correct, CTRL+C if not

Ready to write 1024 bytes

Resetting device

Cannot reset device

Reset command sent

Waiting device /dev/sdc4.......

Found device!

Writing 1024 bytes to offset 0x00000000

Waiting mode-switch

Device changed mode

Detected mode-switch

ubuntu@ubuntu:~/Desktop/evo/lte$
[Sprint HTC EVO 4G LTE] Zodiac13:
ok so i rebooted the comp and was able to get the command "./dg112.sh -r" to work. I had to go to work though so I left it doing its thing. I'll give an update when I get home.
[Sprint HTC EVO 4G LTE] yarrimapirate:
Look like the bootloader didn't load all the way (you'll get around 43 cycles of the previous output you posted when it does). The -r option should get you going.
[Sprint HTC EVO 4G LTE] Zodiac13:
awesome it's back and working now phew haha. cool now to get lazy panda to get s-off and upgrade my radio finally. wish me luck :P
[Sprint HTC EVO 4G LTE] baknblack:
Power phone completely off. Hold volume down and push power while continuing to hold the volume down. Don't release volume till you see the bootloader menu come up.
[Sprint HTC EVO 4G LTE] somdave2005:
Been waiting for the DirtyRacun S-off to come out , and now find out I have Windows 7 64 bit on both my computers, which is not compatible with the DirtyRacun software...grrrrr... Now I need to find a windows 7 23 bit computer somewhere to use.
[Sprint HTC EVO 4G LTE] evoforevo:
been waiting for it myself have same desktop as you were did you here the news. When in to there website just says coming soon.