Microsoft insists ChevronWP7.Updater devices will not be able to update past NoDo.

April 20, 2011 | By Surur

nopastdo

With NoDo arriving on the AT&T, many users who have updated their phones using the ChevronWP7.Updater method noticed they were in fact also notified of the update and were able to apply NoDo and the AT&T-specific tweaks it contained without any issue.

This has led many to believe Microsoft’s warnings that the hacked update will prevent future updates, placing phones in a “non-serviceable state” was nothing more than FUD.

On Twitter however Microsoft’s Brandon Watson has maintained the issue is real, and while the update to build 7390 went well, phones will not be able to update any further.

While only actual issues at the next update will confirm the problem for most users, an update is in fact expected in the next few weeks to patch a certificate issue, so the claim will be tested very soon.

Via WPSauce.com

About Surur

Site Admin and Windows Phone enthusiast, he has been using Windows Mobile devices since before they were called PocketPC’s. He is currently sporting a HTC 7 Trophy.

Tagged hack, microsoft, nodo, update, windows phone 7

jilbo

This is a disaster. And this is why iphones are "magical". Not because of pixie dust or because they are any good. But precisely this kind of crap would never happen regarding updates. Any two year old can update the iphone. IT JUST WORKS. This nonsense will only further the impression that is not user friendly (to the masses anyway).

ghosh9691

Bullshit! If your iPhone is jailbroken (just like the WinPhone7 is using Chevron), then you will have a hard time updating it. Try it….
chrislynchhp

Seriously? iPhone updates "just work?" Boy, are you misinformed. There are plenty of issues with iOS updates. This discussion is directed at those that chose an UNSUPPORTED manor of obtaining an update to their phones. Everyone who has a Windows Phone right now is classified as an "Early Adopter" and will have to suffer through some pain. One of those pains was the initial release of updates to WIndows Phone. It was released later than expected, and even promissed. Some folks couldn't wait, and thus chose to take a different avenue, and one that I would like to point out again is an UNSUPPORTED METHOD. There are risks to going down that path. I hope Microsoft helps folks out that chose to do this, but I wouldn't hold my breath.

GP007

At most they might redo the support tool to reflash your phone to a clean build of 7390 though that'd be like resetting it so people will have that problem to put up with (probably). I dunno what else can be done IF there is a problem, MS hasn't given details at to what might have changed that would block future OS updates at this point.

Only time will tell though, we'll see how the next SSL security update goes.
james p

Microsoft should just shut up and give us a windows 7 desk top ui intead of that tile crap

chrislynchhp

Yeah, that's the ticket! Where is the Troll Stopper 5000 when you need it!?!?
Disco Stew

Is this when I start the slow clap or should I continue to look around and notice nobody else agrees with your sorry remark.
Airanp

Yep, that will happen right after Black Ops is released for the phone. Why did you buy the phone then?

http://twitter.com/SirCatalyst @SirCatalyst

MS said they were going to emphatically prove that you couldn't update past NoDo with hard evidence. They still haven't done that so I'm still standing behind the FUD explanation and that MS was embarrassed at how easy Chris bypassed their system.
TheManFromEarth

These bastards better allow me to get those updates or I will have those three family members go back to iOS (Which I hate) and I will go Android (it will be easer for them to bo back to iOS that it was for me to bring them to WP7)
all in all I believe that my money is quite a powerfull thing to big corporation and I will add to that my influence to those around me and that will hurt.

I am the best and most loyal friend, but a friend scorned is an enemy you don't want.
You have until july to make me happy.
zzz

Those blaming MS for not supporting unauthorized updates created by a 3rd party developer are some of the biggest idiots I've seen in my life.

jplayer01

Well, a Microsoft tool was used to install a Microsoft update which was hopelessly delayed. I'd say yes, Microsoft does have a lot to account for. They haven't exactly endeared themselves to their customers as of late. If they tell off their customers in this case, they're simply shooting themselves in the foot because the customers were only trying to fix a problem Microsoft caused. Add in to the mix the complete lack of transparency and the siding with carriers … eh, they had better make things right or they'll have quite a few unhappy customers.

chrislynchhp

No, they haven't endeared customers with the delays by both Microsoft and Carriers. However, there are risks involved with taking an unsupported method or process. Brandon Watson isn't one to go about lying. I will believe him until it is proven otherwise.

Haven't you heard of the expression "you lie in the bed you made"? Folks that chose to use Walshe's "tool" made that bed, and have to suffer the consequences of that action.

Yes, I know a lot of folks were upset that it took MS and carriers longer than expected to get NoDo out. However, they have, and are trying to repair/fix this process for future updates. This was the FIRST rollout of an update. If this was your reboot attempt, don't you think you want to make sure updating code (wether it be software or firmware) is solid, and delivered in a controlled manner?
Joe05

That Microsoft tool was not used in the manner that it was designed for, a 3rd party used it in a unsupported manner and that's the chance one takes for these kind of things.

I don't know if what Microsoft say is true or not, but I certainly wouldn't blame Microsoft for something that I made the conscious decision to do.
jimski

Microsoft has provided a potential solution. You will have to send your phone to your carrier and have it reflashed to stock. At your own cost most likely.

http://twitter.com/airanp @airanp

Everyone knew the risk when they did this, including myself. I call shenanigans for the simple fact that why is it the next update that wont be able to install, why not the one I just installed today, several weeks after I used the tool Chris put out. I just think they are trying to cover thier ass and save themselves embarrassment like SirCatalyst said before.

chinch

Microsoft is seriously inept if chevron devices running build 7390 (officially updated via carrier pushed update) cannot be upgraded without a total reset. I mean, this would require utter, gross incompetence

Joe05

If the problem with the update was because of something Microsoft did, the Chevron tool update was done with out the support or consent of Microsoft.

There are always risks when these things, I'm not surprised , but lets see what happens.

chinch

again, in designing WP7 updates…. if MS allowed a 3rd party to install the latest OFFICIAL update AND also not be upgradable further… THEY ARE INEPT. They completely and utterly failed and to a crucial base of vocal, early adopters.

It's not like chevron rooted, reimaged and wiped phones using a hacked ROM. If it did that then of course NoDo would not be expected to be updated.

Microsoft gets a lot of bad press that is unwarranted – including from lame bloggers like Paul T. who cried about "blocking updates", ignoring business realities.

This is a technical FIASCO, if true. I'm still doubting Brandon is 100% correct though.

http://twitter.com/airanp @airanp

Seriously, if within twelve hours of release of that tool, someone has figured out how to update directly from MS then MS should be embarrassed. Good possibility they will use this as an excuse in the future when the next update is grossly overdue from the promised date.

efjay

Someone please explain how using an unauthorised tool to update your phone that breaks update functionality in said phone is Microsoft's fault. I didnt see any links to Chris Walshie's tool on any MS knowledge base article, now any MS guidance to use the tool, or did I miss it?
HD7_owner

Stop pointing finger and blame one another! I'm sure will be a solution or a lesson learned for some of us(ChevronWP7 users) or NOT.
aprice

As someone who used the Chevron tool, this is not Microsoft's responsibility or Chris'. We all knew the risks. If MS or Chris can help that would be great. I would also be happy to reflash an official ROM if they would make one available.

EIther way, the responsibiltiy lies soley with us, the users, for using an unauthorized method. To state otherwise is foolish.

chrislynchhp

Finally, someone with some common sense!

KennyB1234

I can't believe they officially called them "Walshed Phones", thus causing his last name to be a sort of swear word. That's pretty rude.

Don't worry guys – Chris and the rest of the Chevron team are seriously talented. You'll get your security update and Mango through their evolving update tool, if that's the only way.
http://www.facebook.com/people/Brian-Selman/215900876 Brian Selman

Im sure the Chevron team will fix up something for future updates the same way they did for nodo so i wouldn't worry to much.
Deji Olajire

Just reset ur phone and everything would be alright..

http://www.facebook.com/danmaxis Danilo Heroso

Some phones can't be set in download mode, making them not updatable. ..

http://twitter.com/IGXNick @IGXNick

Well if all the updates so far are any indication we won't miss much took over 6 months to get NoDo which was promised forever ago and Mango will probably out December if we are lucky and then to the actual devices by this time next year.
HG23

I just don't buy it. I used the Chevron method and I don't see how this is an issue if it still updated and added all the little AT&T stuff. Time will tell
Rich Adair

Lol..I will worry about future updates when they are actually released. By that time I will probably have a Nokia running wp8
Jonathan

Craig,

Those that used the "Walsh" method have no restore point in the zune software. When performing a hard reset, the phone will only go back to the post-Walsh/nodo update.

There is no way to get the firmware back to the 'native' AT&T/pre-nodo version.
Bill

On my Samsung Focus, the "Walsh" method did not make any changes to the firmware version. The firmware version was not updated until the "official" push from AT&T/Microsoft.

jimski

How do you know that? Do you think the "Walsh" method would have changed the number?

Airanp

Huh?

Joe05

That's why I wouldn't do the unsupported update, If I bricked or Fraked up the ability to update the phone, it would be my little $500 dollar mistake .

Hopefully Microsoft will help out, But if I were the Chevron Guys I'd be careful, when you start doing things like this you put yourself in a position of being held accountable for someone else screwing up their phones.
nam

So you're blaming Microsoft on your impatience? I waited like a normal person for the update, and I didn't self implode or anything because I got it two weeks later.

Airanp

Well Golly, aren't you special all on your high horse.

http://twitter.com/airanp @airanp

Has anyone considered the possibility that MS released their tool with the knowledge that Chris and his team could, or would do what they did to skirt the carrier delays. They had it so you could update almost any WP7 on almost any carrier within twelve hours, then MS asked them to take it down after it was spread all over the internet. Now they are scolding everybody who did it so they look like they are in control.

I have no hard basis for this, it's just a thought. Yes, I "Chevron.Forced" my update and strangely enough, I updated mine through Zune and it works almost perfectly now.

Once again, I call shenanigans, but I will see down the road, if they ever really get the Mango update out on time. I still love my phone and will support the community unless I am give a good reason not too. And that doesn't include my own ignorance by updating through a "unsupported" method. I am a big boy, I make my own decisions and will live with what happens.
WP7Fan

It's the Chevron team that hacked the phone and incorrectly applied an undocumented API, and it's the user that updated trough an unofficial source.

It's a risk they took, and lost. You don't know how much damage the incorrect API usage has caused, so it could easily be impossible to fix (especially if something like the "download mode" (to receive firmware over USB) got corrupted)
HG23

I remember MS saying the HD2 would not be up-datable…yet here we are.
buzz

I got my official update through ATT and now I regret doing it. The official update will interfere with our ability to update on our own.

buzz

probably interfere.