yashsingh1/xdaforums huggingface dataset:
[Wildfire General] waywardlistener:
Yeah, sorry, i was confused between alpharev 2 and alpharev x. Eagerly awaiting it :)
[Wildfire General] moutsa:
good news :)
[Wildfire General] StarF:
impresive, any hints on release day?
[Wildfire General] androidino95:
What's taking them so long to publish the process how to do it? I'm sure they are trying to make it simple. :D
[Wildfire General] bx19:
I think nothing is simple when it comes to 2.2 wildfire.

It will take time for the alpharev x. The release date will be said at the time of release as usual. But really a good hope at the moment.
[Wildfire General] MohamedYousri:
They are our only hope now , let's wish it will be out soon
[Wildfire General] mtnhan1996:
Usually products from AlphaRev are for rooted devices, they've announced that on their website. So basicly, we cannot S-OFF wildfire without rooting it. :o

http://alpharev.nl/ Read it and carefully read the REQUIREMENTS
[Wildfire General] bx19:
No lol. This one is alpharev x and it is confirmed that it won't need a prerooted device. This one is specially for hboot 1 + on all devices. So it roots + s-off the phone.
[Wildfire General] lokeshramesh:
I think AlphaRev are planning to release s-off for wildfire hboot 1.01 along with 0.80 also with other devices that's y they are taking so much time but its good they are doing for as much devices as possible.. All the best for Alpha Team...;)
[Wildfire General] mtnhan1996:
Has anyone S-OFF wildfire successfully with a close beta version of AlphaRev?
[Wildfire General] ccdreadcc:
july 2011 - sell ur phone ? xD

my sisters wildfire still with s-on crap :rolleyes:
[Wildfire General] anonimo95:
maybe someone...
[Wildfire General] Cosmo123:
is there anything we can do to help? i have the htc gratia and would love to help out in any testing phase.
[Wildfire General] sergey.sh:
I have HTC Wildfire and also would to help Alpharev developers on the testing phase on my own risk.
[Wildfire General] wesleyvdbrink:
Send them a pm bout a week ago, no replie. So they dont need testers.

Imo wildfire is done, they are testing other devices atm.
[Wildfire General] cspiliakos:
Wildfire should be done already, as they've published the youtube video. Also Incredible S should also be done, as both the update and the original version are hboot s-off by Alpharev X. Apparently, we have to wait for the other devices to finish in order to move on to the release of the fix.
[Wildfire General] ErwinP:
So you are in close contact to the developers, and they have told you that they do not test it anymore on the wildfire bcause everything works flawless?

If not, keep in mind that they have had only one wildfire to test on (cfr the cracked on the website). God knows what they have done to that poor little thing to come finaly to the ultimate procedure for replacing the hboot. But it could be that it only worked because of the combination of the previous (partialy failed) hacking attemps. The only way to know if the procedure realy works is to test it on as much as other devices (all with diferent history) as posible. And that is what they are doing now, so that they can come up with a solution that is safe for EVERYBODY.

Of cours they are testing an addapting it for the other devices as well. But I can imagine that they can run all the tests more or less in parallel, so no need to wait until one device is finialized before starting developing for the next.

Don't make any assumpions regarding what they are doing, what they will do and what they are thinking. The only ones that know those things are theyselfs. And personaly, I hate the fact that other people are making assumpions on what i will and should do. So I can imagine that they would as well.

Finaly: please just be patient. What does it help to whine about those things? Nothing. We can complain all the way about how they are keeping and keeping the ultimate solution for themselfs and we can feel real miserable about it and write some sad songs. Or, we can just be glad that there is light at the horizon, start dreaming about what we will do when it comes out and enjoy the device that even with s-on, is still a lovely one.

Stop making yourself depressed, if it would depend on htc, we wont get s-off untill the first people arive at mars.
[Wildfire General] rajiv_karai:
waiting.. my bad.. had bought the htc with 2.1.. out of curiosity and lack of knowledge i updated it to 2.2.. its been 5 months.. just hoping it comes sooner..
[Wildfire General] cspiliakos:
@ErwinP, I'm not in contact with the devs, but from what I can imagine from personal working experience with software development, once you get it fully done you release it. In addition, providing the public with a video of a wildfire working with the hboot changed, shows that it actually works and that they're changing other hboots in order to release a wider fix, not just a specific one. Also, there are other mentions from beta testers that they've been helped by the devs to s-off their wildfire and thus, we currently know that there have been more than one wildfire fixed.

Please, bear in mind that program development cycles usually go according to this: development of the program > alpha testing > beta testing > release candidates > shipment of the software in question. In some cases, there may be some minor glitches to fix and updates to do, so that everything works flawlessly, but that doesn't mean that the devs should release a program as soon as it's proved working. Providing a specific fix, does solve our issue, but that would probably make it even worse than it is for them, at the moment, as they would have to deal with multiple things at the same time and delay from a more widened fix.

I do agree that whining doesn't help, and that we should allow the devs the time to complete their program, in order to be fully functional as soon as possible.

Does speculating make me bad? I honestly doubt about that, as I'm not doing anything wrong. If the developers want to share some thoughts on the matter, they can surely do so and they're more than welcome to do so, but I don't see why we shouldn't be using common sense to answer to questions that are being asked.
[Wildfire General] rajiv_karai:
well guess what.. i gave it a really deep thought.. i feel that alpharev x will be realesed on the 4th of july.. :)
[Wildfire General] cspiliakos:
@rajiv_karai: 4th of July eh??? Interesting, to say the least :P Shall we ask them to put a US flag as a background??? :P
[Wildfire General] rajiv_karai:
hehe..:) i guess.. :) ;)
[Wildfire General] dannyjmcguinness:
Congrats

Well done to the people responsible for achieving this. You have my admiration and respect, I really can't wait for this I have 3 phones to do and you can guarantee a donation from me upon success.

I'm willing to chance bricking my phone if you need any more testers by the way.

Oh heres a link to 1.01.0002 if anyone wants it. Its a UK vodaphone update.

http://www.mediafire.com/?wt6ac5f82s5yi47

Anyone noticed how shipped roms has a severe lack of UK Roms?

Any reason for this?
[Wildfire General] rajiv_karai:
what is the above link???:confused:
[Wildfire General] cspiliakos:
Supposedly, the HBOOT 1.01.0002 version for carrier Wildfires... (it's S-ON)
[Wildfire General] rajiv_karai:
for a moment i got super excited.. :rolleyes: :D
[Wildfire General] :
With one exception i was surprised to notice.

The OTA_Buzz_Froyo_hTC_Asia_WWE has hboot 1.01.0002

maybe debranding is not just related to the hboot but also to the build number.
[Wildfire General] cspiliakos:
Yes, it could be the build number as well. It has been mentioned in the past, as far as I remember, that branded and region specific phones have different HBOOT versions. After all, didn't certain Asian Wildfires get Froyo faster, or were shipped with it before European ones?
[Wildfire General] ErwinP:
First of all, since you are active in the sector you have a knowledge advantage of me. So you prob. will know the thing better then I do.

BUT: I my opinion this differs from the normal development cycle because of the danger of "flashing" a new hboot. If something goes wrong during the process, you will have to knock on the doors of htc because your phone won't boot anymore, an all you can do is hope that they don't notice that you tried to change your hboot. So in my opinion it is justified that they skip the "release candidates > shipment > post market surveillance > develop fixes" because if there is a need for a fix, harm will have already been done.

In addition: there isn't something like a "bug report" that can be send for them to make fixes. If something goes wrong, all they can do is hear that it went wrong, but a dead device can't send any reports, so how do they know what to fix? By making a closed beta-testing, they are in close contact with the device and can monitor every parameter. So if something goes wrong, well for you nothing much changes, but they can possibly see what went wrong, and possibly fix it.

And I know that you and I know that that harm is only done by ourself, and that we don't have to blame AlphaRev for ruining our devices, because it was on our own risk. But we also both know that not all people will read the big "ON YOUR OWN RISK" warranties. And if then something goes wrong, they start to complain, giving the team not only headaches on how to help those people, but it gives them also a bad name as well.

So:

- I think it is justified that they don't follow the normal development cycle

- I do think it is better that they won't have to fix things afterwards

- I would like them to come up with something wildfire-specific if it is already fully developed, but it is there choice and there is not much for us to "will".

- I would like them to come up with a expected time of release, but I'm willing to think that it is due to my non-developer mind (just a simple scientist in spe :-p) that I don't understand the problems that they have to face between "Eureka, it worked once!" and "here to you all, our solution".

- I do not think that whining is bad, but everyone seems to do it. And oke, that is personally, it is getting on my nerves. But oke, I myself shouldn't whine about that ;-)

As the matter of fact, I should stop whining in total. So no hard feelings (although I might have come over a bit aggressive) and I hope you do not thake is personal, but that is just my opinion.

Erwin
[Wildfire General] androidino95:
Nice one ^^, probably :D
[Wildfire General] cspiliakos:
Erwin, the thing with software is that it always leaves traces behind that you can read and see what's going on. The difficult part, from what I can imagine, is actually reading the hboot logs/data/whatever whenever a failed brick occurs. Trust me, htc knows that and I'm pretty sure they have an unbricking device, in the same manner as the xtc clip, it's just a matter of who's going to pay for the damage, not who's fault it is.

In my mind, and pardon me for going a bit off topic, the whole bootloader situation is a wee-bit of legal shady ground, mostly due to the following facts:

in order to load a new OS you have to reverse engineer it, thus breaking multiple laws, and

since you actually paid for a device, you should control it the way you like it, thus the company is limiting your ability to control it the way you do, which actually breaks multiple consumer laws as well.

I'm pretty sure a lawyer will have a field day on that matter, especially due to the fact that all android smartphones are running linux (ie. a free OS, that can be configured according to the user's wishes and that google has already published its source code for most, if not all, android versions), but, from what I can imagine, and pardon me for any technical ignorance on how smartphones are built, the hboot is like the bios of a computer system, with the addition of a bootloader, so making things like this public, does have its concerns.

Legally, and correct me if I'm wrong, they do have the obligation to fix your phone free of charge, if it's a hardware failure and on its warranty period, regardless of the rom you've installed, with the exception of the parts damaged due to an overclocked device. If it's damaged outside of its warranty period, I'm pretty sure they'll offer you alternatives. htc and any other company, doesn't have the right to refuse to fix a phone if it's bricked, as long as someone pays for it, in the same manner as one would pay for a technician to format his computer, the only question here, is IF they're willing to do it, and under what price.

Now, since I've probably said enough off topic, true, it's not a normal development cycle, but I'm pretty sure the devs already know what to do and have done it, so we only have to wait for them to finalize everything, pack them nicely and release it to the public.

Costas

P.S. from what I've seen in ieftm's youtube account, they've probably finished a Desire hboot fix as well, so it's only a matter of time before releasing it to the public, and we should all be patient and thankful to the devs for actually doing something free of charge for all of us who want to actually own our smartphones.
[Wildfire General] :
Maybe ur predictions are correct. But even u r not sure about eta. So, of course it might be annoying to the devs. And moreover these predictions may be considered by other people visiting the thread. So, suppose if the delay is more, these other people will finally show the impatience towards devs again. I think that's what erwin was trying to say.

And of course I will be happy to hear the release date. And I too have my predictions just in my mind. But I think I can ask nothing because I was waiting for a free thing.

And u said that wildfire should have completed just because of that YouTube video which was false.

And HTC may do the unbricking in a day. But mostly they will take a lot of time. Even people had 1month experiences with service center. And I support that because of my previous experiences with other phones.
[Wildfire General] fergusstrachan:
"htc and any other company, doesn't have the right to refuse to fix a phone if it's bricked"

Hehe, I think that's a VERY debatable point. You think because somebody owns a shop, you have the right to buy something there? No, they can tell you where to go. That's fair enough.
[Wildfire General] cspiliakos:
Actually fergusstrachan, it's not a debatable point because the buying has already been done. They can refuse the fix of a rooted phone IF and only IF it's software related. The same applies to all computer manufacturers, who are bound by warranty. The software comes in the form of a license agreement, the hardware is what the manufacturers usually sell. In the same reason, if hboot is just a bootloader, they are bound to unlock any and all phones that are requested to do so, due to the fact that a smartphone these days IS in fact a computer.

True, the last part is debatable and if you do go to a decent court, you can probably win such an argument, but that would cost money and companies do know that.

According to HTC's Limited Warranty statement:

meaning that htc does have the right to refuse the fix of a bricked phone for free as the bootloader is, as far as I know, still considered to be software. Asking for such advice in your country's consumer rights groups may give you more hints on what a company is and isn't allowed to do. If that doesn't help, try talking to a law firm specializing in IT and consumer rights.

However, this discussion is completely off topic and we can continue it on a PM.
[Wildfire General] wesleyvdbrink:
BETA TIME, SEE ALPHAREV.NL/X/BETA ONLY LINUX!

Sorry for caps :)
[Wildfire General] :
Thanks for sharing. nice
[Wildfire General] Rimidal:
S-OFF'ed sucsessfully. Alpharev are the best!
[Wildfire General] djdevine2:
Beta is closed, I hear it was fully successful with the wildfire! 10/10 Hope we see it soon again!
[Wildfire General] hoho20022222:
open only for few hours... :(

anyway, hopefully :)
[Wildfire General] sergey.sh:
I've downloaded file, what shall I do with it?
[Wildfire General] Cosmo123:
I got the Gratia with the HBOOT 1.00.0000 and that version is not supported.....i hope it will be added. thanks for all the help tho, you guys have been really nice, kmdm and attn1
[Wildfire General] BarclayTech:
Beta is closed. U cannot use the hack anymore due to them stopping the beta key release.
[Wildfire General] sergey.sh:
I've got also the key. What shall I do with downloaded file? I'm new at Linux (right now installed Ubuntu)
[Wildfire General] asz18:
Connect your phone to USB, then:

Go to Terminal and run:

sudo su

./alpharevx

There you go!
[Wildfire General] wesleyvdbrink:
Thanks mate!

New to the world of Linux. Used Ubuntu with above commands and it worked.

Hboot 6.01.1002 :cool:

For people that got a key and file, extra the file and use copy to "home folder" after that press "ctrl alt T" for the terminal and type above command.

Good luck and btw way I LOVE YOU ALPHAREV!
[Wildfire General] jbeans05:
Why they are closed beta release. I want to try it. I always waiting for this information T_T.
[Wildfire General] BarclayTech:
So people dont brick their phones. and if people do. then they wont have 100 people moaning at them.
[Wildfire General] TheIntruder:
Err because it's a beta maybe :S
[Wildfire General] BarclayTech:
Beta can be open. Minecraft was open at alpha.
[Wildfire General] hani93:
i can upload beta somewhere, but can we request key `?
[Wildfire General] Rimidal:
No. Until it's at least in open beta stage.
[Wildfire General] magico1988:
so you can not... :(
[Wildfire General] hani93:
damn, i've missed that....i have 4 wildfire-s waiting here for root with 1.01.0001 and 0002

i hope that open beta will be released soon.
[Wildfire General] Rimidal:
Devs told that it will be "very soon"
[Wildfire General] hani93:
thanks for your help.
[Wildfire General] Rimidal:
Meanwhile you can follow their twitter not to miss any news from them.
[Wildfire General] TheIntruder:
This is not minecraft lol I doubt there is any risk of bricking you phone with that, silly comparison...
[Wildfire General] dud3me:
Will the open beta be for windows too and is it safe to use?
[Wildfire General] drlard:
Out of 15 wildfires that i saw getting soff yesterday (me being one of the ones taking the chance) none got bricked. Was quick and easy.
[Wildfire General] kmdm:
It flashes a CRITICAL part of your phone, there is no such thing as "safe" since there is inherent risk in that process.
[Wildfire General] BarclayTech:
I'm comparing in the fact their both currently beta. It's not silly at all
[Wildfire General] kmdm:
No, really, it is silly.

For the reason already stated.
[Wildfire General] luxandroid:
for some time I am stucked to the screen of my laptop and waiting alpharev....one day I was off and missed beta realese :( :( dmn,but happy for those who did it,means the rest of us will get there "soon" indead
[Wildfire General] :
But I think that soon is even earlier than what u expect.

I think so because of the fact that no wildfire is bricked yet.
[Wildfire General] luxandroid:
I realy mean and bealive it will bee real soon because the fact that no wildfire is bricked as U say :) :) Waiting was worth I can say that much
[Wildfire General] JohnDorian1:
Yeay, im one od the luky guy who saw the post on Twitter :)

After 6 Moth i have finaly a rooted phone!

I rooted it immediately after the HBOOT was s-off and installed CM 7

Chin up, guys! You gonna get your WF rooted soon ;)
[Wildfire General] rajiv_karai:
the whole day i was following up with twitter and xda.. but just before they released the closed beta i fall asleep.. thats my luck.. :D :D:D:D;););):p:p:p:p
[Wildfire General] xallrons:
I can't wait for this! :D
[Wildfire General] luxandroid:
You are not alone in that bad luck ;)
[Wildfire General] maxjack193:
keep it up

nice topic

keep it up
[Wildfire General] IvanDeadWolf:
and what about HBOOT 0.80?

Whether I can to make S-OFF with AlphaRevX ?

sorry for my poor english.
[Wildfire General] cspiliakos:
HBOOT 0.80 can be S-OFFed by Unrevoked
[Wildfire General] Arachne86:
I think today is the day... the X day :)

(at least I HOPE so)
[Wildfire General] IvanDeadWolf:
really!? unrevoked for the CWM recovery and root only! secure flag is S-ON!!!
[Wildfire General] knoxious:
the suspense is really killing us haha!

you don't know how much i clicked refresh :P
[Wildfire General] cspiliakos:
Unrevoked, is HBOOT 0.80 compatible for the Wildfire, as far as I know. I've used it in at least 2 Wildfires for friends already. Did you follow the instructions on the Unrevoked website?
[Wildfire General] IvanDeadWolf:
As at us speak:

Hope springs eternal!:D
[Wildfire General] IvanDeadWolf:
Yes! But i already have a root by Unrevoked. I need S-OFF.

Sorry for my poor english:)
[Wildfire General] cspiliakos:
The Unrevoked gives S-OFF, check the settings on the Unrevoked program and do it again, if necessary.
[Wildfire General] 3xeno:
No. It exploits an exploit (lol) and pushes a custom recovery and superuser to the phone. Thus, giving root only. Not S-OFF.

Unrevoked Forever gives S-OFF, but it was not released for the Wildfire. The only way till date to get S-OFF (irrespective of HBoot version) is by using an XTC Clip, and AlphaRev X (When it is released).
[Wildfire General] cspiliakos:
3xeno, then how could we easily install any other ROM if S-ON was on? Didn't the same mechanisms apply? Or has the bootloader changed so much?
[Wildfire General] Cyda:
Erm, no. Unrevoked doesn't give S-OFF.

Edit: to answer the question above; unrevoked used a exploit to bypass the S-OFF and push a custom recovery, and once you have this in place you can install custom ROMS but this exploit no longer works so can't be used on the 1.x HBOOT.
[Wildfire General] poeken:
Because The recovery helps You install custom Roms , and installing a custom recovery on hboot 0.8 was possible with unrevoked. but on 1.x you need soff to install The custom recovery
[Wildfire General] IvanDeadWolf:
unrevoked only crack hboot 0.80 and install custom recovery.

/system - is not RW
[Wildfire General] hascimal:
Wildfire S A510E? A root will be possible with this release?
[Wildfire General] :
A custom recovery like "clockworkmod" has the ability to install custom roms. S-ON or S-OFF doesn't matter really. In general, recovery partition can make changes to all the other partitions when they are not in use.

Installing of custom recovery is made possible on wildfire hboot 0.80 (even with S-ON) with an exploit from unrevoked. This kind of exploit to install custom recovery is not yet possible on wildfire hboot 1.01. On hboot 0.80 , using that exploit unrevoked not only flashes the custom recovery but also pushes the su binary into system folders to make that current rom rootable.

A custom rom with su binary in the system/bin or system/xbin when flashed through custom recovery gives root permissions.

And all custom roms will have su binary in system folder AFAIK.

Suppose if u remove the su binary in a custom rom and then flash it through custom recovery, it is equal to the stock unrooted rom.

And s-off is not necessary for root permissions/custom roms. Pushing of that su binary is necessary for root permissions. That's what wildfires with hboot 0.80 has now (custom roms with s-on).

And once nand is bypassed even psneuter / gingerbreak can give permaroot to the wildfire. This kind of thing is needed if u want to use the same stock rom with root permissions just after s-off. Hope it helped......
[Wildfire General] ryan1mcq:
Aww man, awesome stuff Alpharev. Glad i found this thread, i salute the team. I have been spamming refresh all day hoping for more info and will continue probably all night lol :D
[Wildfire General] nms247:
Can be rooted with unrevoked, but it'll still be S=ON
[Wildfire General] :
Why having that doubt.

After alpharevX is released, u can even update to hboot 1.01 and use alpharevX to S-OFF it. NO worries dude.......
[Wildfire General] IvanDeadWolf:
I don't want to risk) It is terrible to increase HBOOT.

Устал уже по английски писать))
[Wildfire General] :
Hey, i said after alpharevX was released. If u once get S-OFF, root and custom roms are not at all a matter.