For Those who have the Unoffial Froyo will the New Update still Pushdown

[mvaughn12]

Just Curious , and forgive me if i didn't see an answer to this, i did look, but for those of us that have the manual install Froyo 2.2 will the automatic update still work on the release date? It would seem to be a different version when it comes down am i correct on this? Since the realease now was not the final version.

 

[Stepintothedark]

Yes because "TECHNICALLY" the phone wouldn't be up to date...

 

[zombdroid]

I am wondering the same. I downloaded the update but did not install just in case. I can certainly wait a few extra days to get the final release.

 

[dzar]

We will know on or after August 3rd... anything else is speculation.

Here's my speculation; If the official release has the same versions/identifiers/whatever-is-being-checked, then no update is necessary and I wouldn't expect it. If something is newer, I would expect it to take.

 

[laredo7mm]

For what ever was "released" yesterday, the update on the third will probably have a different build number even if the software number is the same. So yes, I think it will update.

 

[RiverOfIce]

For what ever was "released" yesterday, the update on the third will probably have a different build number even if the software number is the same. So yes, I think it will update.

To be honest, you could not change the build number that quickly.

To change the build, you are looking at 1000 hours of testing. You can not have a different build this close to launch. It has to be finished before Friday, to be pushed out Tuesday. If they are still testing a build on Monday, then to load it into channels, they would have to take about 3 days which means they could not launch before Wednesday.

To be honest, they would have not pushed it out to reviewers and outside testers, if it was not the final release. If you think they are going to add anything between that build and the current build, it would require 1000 hours to do that.

 

[shadiguy1]

Worse case download to home computer and do it yourself im sure it will be available.

 

[laredo7mm]

To be honest, you could not change the build number that quickly.

To change the build, you are looking at 1000 hours of testing. You can not have a different build this close to launch. It has to be finished before Friday, to be pushed out Tuesday. If they are still testing a build on Monday, then to load it into channels, they would have to take about 3 days which means they could not launch before Wednesday.

To be honest, they would have not pushed it out to reviewers and outside testers, if it was not the final release. If you think they are going to add anything between that build and the current build, it would require 1000 hours to do that.

Well, I disagree. I work for a software company and we have a hundred build submissions a day. We release builds the day before we are going to release the final version of the software. The amount of testing needed depends on the risk of the change and what areas it affects.

I by no means implied in my original post that there would definitely be a change, just that if there was a change from what was released there would be a differenciating factor (build number) that would allow those that had done the early update to be able to update to the final release.

 

[EarlyMon]

To change the build, you are looking at 1000 hours of testing.

No one can make a statement with that sort of number attached.

A decent process-driven QA program will take however hours to qualify a build as may be required.

The better the product revision maps are, the better things are compartmentalized, the more surety any system test manager will have in his regression test plan.

If they were to clear out whatever cache they missed clearing out and to reset the radio _correctly_ to CDMA auto PRL then based on the feedback for the real root issues people have suffered so far - they'd be done, in my opinion.[*]

Besides - this was A release candidate. They could easily have had others in the barn they were shaking out while looking for feedback on this one.

For all we know, we've already validated whatever they were looking for by NOT having the problem with whatever it was.

None of us were read into the program. (And if the mystically-postulated HTC lurkers are here, they're certainly not talking.)

We had no criteria.

We winged this mother, and all else is speculation.



[*]Yeah, and where unicorns live the final should also have H.264 everywhere, no fps cap, the input sensitivity timing upgraded, everything out on HDMI, H.264/MPEG4 browser support, auto-CPU-overclocking, free tethering.... and that calendar event editing changed back.

 

[heavychevy]

I saw something in the root section that said you could undo the manual update. If need be we could all do that.

 

[VGPOP]

Well, logically speaking, if the build is different than what we have, we will get a notification that a new update is available.

 

[brushrop03]

I saw something in the root section that said you could undo the manual update. If need be we could all do that.

Could you link that? I might wanna keep that in my back pocket....just in case.

 

[EarlyMon]

Could you link that? I might wanna keep that in my back pocket....just in case.

It will essentially just simply be the same process with the previous rom.

Here's the 1.32.651.6 installer.

[ROM]RUU_Supersonic_1.32.651.6 - xda-developers

Can probably track down the 1.47 update for you - or just use google.

 

[brushrop03]

Ah ok. If that's all then I have the 1.47. Thanks. Still new to this android flashing process.

I flashed the 2.2 directly from HTC's website. Now i can go back and root it.

 

[brushrop03]

Hmm actually I tried this but it says I dont have the correct bootloader

 

[skunkd]

connect the phone to the PC, start the bootloader (hold power on and vol down until white screen) then go to fastboot and press power. After that, use the RUU (the .exe) from your PC and it will find the device and flash everything

thats how you tried to do it correct?


i'm trying to go back as well let me know if you have any luck. I'm on 2.2 (unrooted) and want to go back to 2.1 so i can root and upgrade to one of the rooted froyo roms.

 

[skunkd]

looks like we are out of luck til some dev finds a way to root froyo

 

[brushrop03]

Actually I just ran the exe file to go back to 1.47. It got to the bootloader but said it wasn't the correct version.

No biggie for me. i'm sure it will be rooted soon after the official release. and honestly I didn't do anything that required the phone to be rooted