Hey all. I am currently an android user looking into trading for a focus.
Problem is, the phone had WP7 chevron run on it and now has the nodo update.
My question is; since MS said no more updating for phones with chevron run on them, can I remove or revert to a non chevron installed state? From what I have read here, nodo "breaks" chevron, does that mean I can install future updates?
I just want to make sure I dont trade for a crippled phone...
I got the Samsung update after the NODO. Mine was Chevron 7 updated for NODO.
Where did you get the Samsung update? How did you apply it?
Also, is there a way to flash the original OEM firmware to get a "stock" phone?
Waiting to see
I used Chevron on my Focus so I could debrand it and used the timing trick to get NoDo myself, so after the MS release, I spent a while poking around online. As near as I can tell, what MS was warning against was the use of the chevron updater tool, not the original unlocker. MS had already said NoDo would basically "fix" the original chevron hack, so, I think they had that covered. If it was just an unlocked phone that got the update naturally through Zune (even if by trickery), it should be within what they expected. But, the updater apparently forced the NoDo update using some other function on the phone, and that seems to be where the worry is coming from.
But, in the end, if you don;t have a Zune backup from before the update (mine didn't successfully keep them, so, no rolling back for me) the only thing any of us can do is wait for either the next release and see what happens, or for someone to figure out how to get a rom. So far, I'm expecting to see the update first, but, you never know.
I am new to WP7 and would hate to get a crippled phone. Thank you both for your info.
I used the chevron ulocker. It ran in a DOS command window. It did the pre NODO, then it did the NODO. A few days later, I connected it to ZUNE and it announced there was a Sansung update. It went fine.
1.Chevron actually will not affect ur update. What MS said was using Chevron Updater MIGHT prevent you from further update, but what actually happened is that people used Chevron Updater still got Samsung Firmware update.
2.Get rid of Chevron unlock, is easy, just do a factory reset.
amtrakcn said:
1.Chevron actually will not affect ur update. What MS said was using Chevron Updater MIGHT prevent you from further update, but what actually happened is that people used Chevron Updater still got Samsung Firmware update.
2.Get rid of Chevron unlock, is easy, just do a factory reset.
Click to expand...
Click to collapse
Pretty much what this guy said. I did the NODO timing update on my debranded Focus. Samsung update wouldn't show up in Zune until I did a Factory Reset.
So the Chevron team released their tool to allow phones that have been forcefully updated to start receiving updates the regular way again. Is there any chance this would put the HD2 into a state that would allow us to update to NoDo?
http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Hamburg said:
So the Chevron team released their tool to allow phones that have been forcefully updated to start receiving updates the regular way again. Is there any chance this would put the HD2 into a state that would allow us to update to NoDo?
http://blog.walshie.me/walshed-phone-support-tool-official-fix-to-get-you-back-on-track
Click to expand...
Click to collapse
ive not tried it but i seriously doubt it, the updating still needs to be done the usual way, and that way restarts the device to updating mode where the device is then identified as a LEO, at which point updating fails.
whats needed is us to stop it being identified as a LEO in the update mode and i believe we'll then be able to do normal updates.
for those who are still on nodo 7390, an update has been released for some time now -> build 7392 which addresses some issues with certs.
those with dev unlocked phones will not be able to check with zune update server for this update.
error code 8000FFFF <- dont worry, you're not locked out from update like the walshies.
you need to relock your phones using appmfg reboot and plug in the phone. only then will zune detect the new update.
do not install touchxperience, this will also prevent the update. once updated, just unlock your phones again using appmfg.
homebrews are working well with registered dev cert.
sorry if this has been posted. too lazy to check and just wanted to share.
you DON'T have to HARD RESET your phone and lose all the stuff synced.
Hello all, I have the HD2 running the Back to the Future ROM V2. After I flashed it (a few weeks ago) I updated to WP7 7392 via Zune with no problems. I didn't touch it after that and left it as is.
So now I hear that T-Mobile is starting the rollout, and read in that 300+ page thread that some TMOUS HD2 users have gotten the update message. I am not getting the update available message.
Is the update staggered and it's just not available for me yet? Or am I doing something wrong?
Go back, reread, and continue the install guide info starting at build 7403. You have to install the cab sender on your PC and then send the 'Device Provisioning.cab' after you complete the device provision plug back into Zune and update to 7720 =D
So, I was eagered to update my phone with the new SFR-FR update, got it all set.
It started all with the 8018001E error I got when trying to update to this update, so I thought I would just leave it, and I changed my carrier to 000-88.
Then I saw there was another method to update, with the WP7 Cab Sender and the update as a .cab file. Tried this one out when I was still being debranded (000-88), this time the installation failed with error 80180011.
Then (oh dear), I downloaded the Samsung Update Tool from the Omnia 7 support page, and installed a update (or something). Now I tried the official way again (changing carrier to SFR-FR, then Zune update), this time I got the 80180097 error! Yes its raining errors today.
After the Samsung Update Tool thingy, my phone couldn't connect to any network, or sometimes it's connecting to my KPN network for a few moments.
I am tired of this all, all I wanted was to install a few OEM updates, now I end up with this. Can anyone help me out? Really appreciated!