[Q] False Alarm; Problem during Nodo update - Windows Phone 7 General

Tonight i saw the workaround to unlock Nodo, and i decided to do it, but now at the second update it freezed.
I flashed back to a 7004 build rom, then i installed the pre nodo with Zune like normal, with the Nodo it didn't come up by itself.
So i forced it with the Hungarian IP workaround thingie. It worked and i could see Nodo. Backup and so on worked out fine, but when it came to "Installing Updates" it stopped at the near end.
Now i have been looking at the Zune updater at that step for about an hour, and i dont think it will change.
I'll leave it in for now and the rest of the night, but what can i do?
Start over?
Update:
FALSE ALARM
It apparently just took an hour for Zune to install a little update.
The first time i update to Nodo, it took 20 minutes :S.
Was just about to unplug the phone, when it finished.

Related

MS security update reboots my PC!

New MS update first of all was giving me an error after backup - now two days later I tried again and now it REBOOTS my pc just after the backup! Or rather it crashes my pc which then reboots (almost like a power loss reboot!!).
I tried the Phone support tool - but that just says it cant update my phone and says to contact tech support! GRRRR
It's and HD7 - originally got NoDo via Chevron - then got NoDo notification again - updated fine - updated the HTC update OK, but this latest MS security update is being a right pain!
Has no one else had this?
first time i tried it my pc got rebooted, but it went ok in the 2nd try.
Thanks, glad i wasn't the only one!

Upgrading from older build to 10581?

I am on 10166, and I am stuck at 0% downloading. Anyone been able to upgrade to 10581 or is their 'upgrade bug' still there?
Will be 0% for few minutes, and then go to 100%. Patience
pawlakpl said:
Will be 0% for few minutes, and then go to 100%. Patience
Click to expand...
Click to collapse
Going on over an hour now.
Phone not updating to 10581
My phone has been 'updating' to 10581 for last two hours and is still on 0%
any ideas peeps?
kennygza said:
My phone has been 'updating' to 10581 for last two hours and is still on 0%
any ideas peeps?
Click to expand...
Click to collapse
same story. they really did a great job fixing the upgrade bug..
The update downloaded okay for me, but it's been at 0% Preparing to install updates for a bit.. Should be fine though. Seems all of the builds have been plagued in some way when it comes to updating. I'm updating from 10536.
Edit: Right as I was writing this post the install failed. It said it couldn't install updates at this time. I rebooted and now it started downloading again. Way to go Microsoft, just like all the rest! ?
build 10572
Hi guys, I'm having trouble updating to build 10581 from build 10572, it downloads the udate fine, it takes a while but gets to 100% eventually, but at around 50% on the preparing to install update part it stops and says the update can't be installed at this time we will try again later, error code (0x80070538), I've rebooted and soft reset and also stopped all my background apps and still it's stopping at 50%, I've tried this about 10 times, can someone give me some advice please.
riksye said:
Hi guys, I'm having trouble updating to build 10581 from build 10572, it downloads the udate fine, it takes a while but gets to 100% eventually, but at around 50% on the preparing to install update part it stops and says the update can't be installed at this time we will try again later, error code (0x80070538), I've rebooted and soft reset and also stopped all my background apps and still it's stopping at 50%, I've tried this about 10 times, can someone give me some advice please.
Click to expand...
Click to collapse
In other words, they havent fixed the bug. OS sucks.
MS say you need to use the Recovery Tool and go back to WP8. It is allegedly only occurring on phones originally released with WP8. HOWEVER numerous fellow Lumia 920 users report successful upgrade so I smell some BS in that story. My next step is back-up, hard reset, try to update. If that fails its borrow a PC and Recovery Tool time.
Connect ur device to charger it may help
The update was smooth for me download time-45mins spinning gears-1hrs(ya its too long) migrating data and all other things-45 to 50 mins and now m phn is ready to go...... No need to hard reset this build is quite stable
Finally got it installed on my 640. I must say that it is lightening quick compared to 10536. I haven't even reset it yet. As I'm trying to type this though I'm noticing the Swype recognition is not working right. Almost every word it ignores and puts nothing, or it's changing to the wrong words. Anyone else having this issue?
Edit: Swype seems to work fine in Messaging, but not In Edge or Facebook app..
My upgrade process was smooth! When I woke the phone was updated already.

[Q] Is there a new update?

Hi all. At 4:20 AM PDT (the notification sys 8:20AM for some reason) this morning (June 12) my Note 4 buzzed and woke up and let me know there was a software update available. Any idea what this is?
I didn't install the small security update last month yet, is this just that update trying to be more forceful (the notification will not go away)? Or is it a new update?
Try it, and let us know what it is !
I didn't install last month's security update myself for the fear of losing that slim chance of an unlocked bootloader and root..lol
I haven't received a notification about an update this month..would you happen to have a description of the update?
Well, the notification wasn't going away and I accidentally hit continue and it rebooted and installed whatever it was.
Took it's sweet time installing and then optimizing apps, and as far as I'm aware nothing changed. Same baseband, same kernel, same build number (LMY47X.N910AUCU2DOI3) according to About Device.
Also my phone is starting to show me the same annoying screen that started appearing when the security update came out saying to connect to wifi to download another update (whatever update was installed today, it downloaded itself via mobile, not wifi).
So I am rather confused as to what the 'update' I installed was.

Since Bootloop at M1D64T, i can't update to any Marshmallow Version...

As i've wrote in another Thread (Bootloop at M1D64T), my SWR50 has this behaviour since this Update.
So, i've manually rolled back to Lollipop - discribed in the Thread " How to Fix SWR50 with working Fastboot".
Now, everytime the Watch comes at the Point to Update from Lollipop to Marshmallow, it's endet in the Bootloop with the four Dots...all Updates to higher Lollipop-Versions works like a charm...
Another strange observation i've made when i tried to change to the chinese Fitware....all went fine, but i don't like these Software and rolled back to AW. The Fitware put my Watch back to LDZ22D.
The Watch seddle up, all was fine and after a while the Watch want performe an Update. At the the end from the Update, the Watch booting, but it don't show the circling Clock, no, the four Dots come up, but only for two seconds, then the Watch stays in Recovery...no warning about a failed Update...After i've booting manually from Recovery to System, all runs good and the Watch was on LDZ22D.
So at this point, it can't be the Update to LCA43 by OTA, the Watch says im at the actually system...
Now i will try an manually update to LCA43 and ignore the Update Message to MM....
I'll hope, Sony release an Update to correct this Issue...

OTA update to 9 on unlocked rooted phone

Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
specd_out said:
Cliff notes: rooted/unlocked xl on stock 8.1 ota. that I sideloaded. Phone installed 9 ota, requested restart, now im on 9. I honestly do not remember accepting update.
How can this happen? and will there be issues?
More Details:
So an odd thing happened to today. My phone, a rooted/unlocked running stock rom, got a notification for an update to 9. I have had my phone since 1/17, and I have been rooted unlocked since day one. This is the first time I have received a update notification. I ignored it figuring ill just get the ota and sideload it like i have done previously. Later today my battery was low and I get a message stating the update install is paused due to low battery. Once it charged enough it told me to restart phone which i did, then quickly realized it may have been a bad idea. Phone booted, told me i had an unlocked phone blah blah, then I noticed my custom loading screen was replaced by the standard google screen. 30 seconds later android 9 boots up. everything works fine, lost root though.
Click to expand...
Click to collapse
my phone is still on 8.1 and a check say's up to date, I have downloaded 9. ppr ota , would like to know before i side load, have you got root back ? I use magisk .
I have not attempted to get root back.
Did you have TWRP? Honestly, I'm in a situation where I'd like that to happen. Unfortunately I don't have access to my PC and would like to take the final OTA to Pie, but I'm rooted with Magisk, and.have TWRP installed, I'm worried about a bootloop.
I'm just trying to figure out if there is a way to force my phone to get the OTA update the normal way. My Pixel picked it up as soon as I manually checked for an OTA Update. My daily driver Pixel XL has been saying that I am up to date for the past 22 - 23 hours since the update went live, so I'm still stuck on 8.1.0. Does Google drip feed the update out in blocks based on IMEI to limit the impact on the download server?

Categories

Resources