Upgrading from older build to 10581? - Windows 10 Mobile

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.

Related

Attempting to update 1 week old 8525 to ATT WM6 - Probs...

Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
Are you following the directions at THIS GUIDE . What ROM are you trying to put on there? Did you CID unlock the device? Are you running Vista? Do you have .NET 2.0 or 3.0 version?
That should be enough questions to get us started.
Did you read my title? This is the stock ATT WM6 that came out yesterday. No need to unlock the phone, it is a 1 week old ATT 8525 with the stock ATT WM5 Rom on it.....
Windows XP SP2+ PC.
If it's the rom RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship maybe it had some problems because if you go to the official release site http://www.htcamerica.net/support/8525/software-downloads.html they are still showing the WM5 rom for download.
There may have been a problem with the release and they pulled it back for some reason. Just a thought and not much help I'm afraid.
Yes thats it. When it ID's my current Rom and what it will upgrade to, it is correct. (it shows it's 3.62 vs my current 2.xx) Many peeps have had no problem upgrading to it. (most find it a very good Rom from the varios sites I read)
And this page at HTC still has it up:
http://www.america.htc.com/support/8525/software-downloads.html
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
@brorex he can wait till christmas next year, if the updater cant communicate with the device , because it has closed AS then it will never update.
@JETninja
try doing what i said to this guy here,
http://forum.xda-developers.com/showthread.php?t=341282
yesterday he upgraded with the same rom and device and it worked
brorex said:
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
Click to expand...
Click to collapse
I thought that too, but after the color bar test when it want to set you up to actually install the ROM, the Upgrader whats you to make sure there is an active connection with AS. Well, there isn't. It shut down and the PPC is still showing the color bars. I can reset it, then re-sync to AS. (after having to re-launch AS from the Program Files - it no longer resides in the Tray when it shuts down during the process) I then get it going again, it attempts to start the ROM upgrade, AS quits again.....about a min later I get the Communication Error message....
I'm downloading a 2nd copy right now, will try it as soon as it completes...
*Edit...think I have an idea what I'm doing wrong, I have it connected and synced too early, the first part of the ROM updater is just a PC test, I'm thinking the PPC should not have been connected at that time. Re-trying it now.....
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Going to give it a shot here at work on this PC. If no go still, will try the above mentioned methods. PC at home kept getting communication errors...
i had the same problem
make the connection at AS then start the update process.... the 8525 will go into 3 bar mode and when the update gets to the upgrading rom screen... the installed rom wont show up.... hit upgrade... and then continue and it will work.... i was stuck there for a while too because if i waited for the istallation to load then made the as connection the right image would show up in the installer but then it would stop working after that.....
I just put this rom on my 8525 and it worked well for me. My 8525 is unlocked with supercid so I had to extract the OS and update using the methods described for working with SPL-140 Olipro with IPL-1.01 or the "How not to Brick thread".
That won't help you much as you don't want to do that mod to your New 8525 and void the warranty, but thought you might like to know the stock OS seems pretty stable at this point and I have had no problems yet.
Thanks everyone! It finally worked here on my Work PC. At home I could get to the Bootloader, but it would lose connection for some reason. Here I lost it the first time, but tried it again and it managed to stay connected and apply the update. Got it up and running, applied owner info, just now re-doing the AS relationship. (a good 500+ contacts! LOL! It'll take a little while as usual!)
Then it's back to all the tweaks I like so far...and some new ones I've held up on since I've been waiting for WM6.
Out of my 3 PDA's (2 ipaqs and this puppy) this one has certainly been the trickiest ROM update, but it seems to be more my device since most don't have this much trouble.
Thanks again!
So far- So good, but just one problem- BATTERY!!!
After I installed upgrade, my battery drains in few hours... I reset phone, I reloded upgrade- nothing helps! Warranty still in affect, but phone worked well and I'm positive- hardware is OK. What else can i do to fix this problem?
I have the same problem
ai6908 said:
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Click to expand...
Click to collapse
I have the same problem exactly. As soon as I start the upgrade the device immediately sleeps and the connection is lost. 1 minute later I get a Connection error message.
I am new to all this. How do i put the machine in 'boot loader' mode?
Thanks
Just did this rom update again on a 8525 the installation went extracting files active sync shut down wait a few minutes nothing happens the the upgrade screen no ACTIVESYNC connection while update is happening as soon as device is in bootloader mode activesync closes out

AT&T LG G4 Won't Update! Help!

I'm currently running Android 5.1 Build H81010e.
Since last week, my phone has alerted me that a software update is available. I start installation, the phone resets, and the notification comes right back after 2-3 minutes. It's been in an endless loop for at least the last week. Now my phone resets every 3-5 hours attempting to force the update, but it doesn't seem to ever install.
Anyone else having this problem on AT&T? Is my build the most recent? Any ideas on how to fix it?
If you want root, don't take the update.http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
If you don't care about root, go to Settings > Smart Cleaning and use the cleaner. It may remove the update file and let you download it again.
Since AT&T blocked recovery mode, there's no easy way for us to clear the cache, so you may need to factory reset to get the update to download again.
Apologies for resurrecting an old post however this is the closest forum topic I can find. I have a G4 and I have the same issue as above. I keep getting a notification of a software update and when I try to install the update it just restarts and then 2 minutes later I get the same notification of an update. It's an endless circle lol. I have tried smart cleaning twice and each time I check for a system update and I get the original notification and the endless loop begins again. Is there anything else I can do to update my device? I'm not keen on performing a factory reset or rooting my device if at all possible. Also I'm not with AT&T. I'm with an Australian carrier.
Many thanks

Optimizing apps 1 of 233 - and rising?!

Just recently my LG G4 H815, rooted, bootloader unlocked, v10b, has been acting strange.
I installed boot manager a couple of months ago and it has been running fine, but a couple of days ago I noticed pop up notifications saying a variety of apps were "added to boot manager"
I dont know where these apps are installing from and I cant find them in any folders.
Yesterday my phone crashed and after starting up again showed a "android is starting... optimizing apps 1 of 233" which seems a lot more than i have seen before. This made my boot time about 6 minutes
Today at work my battery died, (this is was because I fell asleep before charging my phone the night before) and when I charged my phone back up it showed "...apps 1 of 244". My phone was then on the "Starting apps..." Screen for 3 minuets. This made the boot time around 8-9 minutes.
I hadn't installed any apps between now and then and I did not see any pop up notifications.
At the moment I am scared to turn of my phone in fear of it taking even longer so I have 2 questions,
What is happening?
Do you need any further information to help me resolve this?
Thanks!
Best shot would be to factory reset your phone
roobns said:
Best shot would be to factory reset your phone
Click to expand...
Click to collapse
if only it were that easy.
more in this thread
Update: I seem to have gotten past the problems after updating to 10n. Now running stock debloated 10n rom with no reboot issues (so far)

Constantly crushing proces com.android.phone

So about 2 months ago I get BigRom. It was all good but from times to times, no more than few times per week I was getting force close dialogs popup
Unfortunately the process com.android.phone has stopped
Click to expand...
Click to collapse
After few seconds the process restart and everything was fine, except that I don't always get sms messages... Till last week. Phone process just started crushing few times per day. So I decided to change the rom to BigOS. Happens the same. I back to the stock and on .87 i got phone app crushed once, because I changed after that to ClearStock custom ROM.
But nothinngs change. Exact pattern in most case looks like that:
Unfortunately the process com.android.phone has stopped
Click to expand...
Click to collapse
It restarts after few moments, phone & internet work few minutes and again
Unfortunately the process com.android.phone has stopped
Click to expand...
Click to collapse
But this time it doesn't repair itself, few moments later my phone is restarting. And I got that issue few times per day, when I turn on my phone phone some times work, somtimes doesn't.
It seems that it's not depends on ROM, but smth deeper. Guys, I need solution, please. I can't use my phone properly.
I was trying to clear data, to clear cache, I deleted manualy from recovery data folders "com.android.providers.telephony" and "com.android.phone". It doesn't help at all
Ok, but wchich one?
It says
To figure out the right version of Google Play services for your Android device, download Play Services info or go to Settings -> Apps -> Google Play services, and look at the last 3 numbers in the parentheses. You'll see something like -XYZ where:
Click to expand...
Click to collapse
and I got 270, but there is no version like that to download
Edit: Ok there is one, but it is exactly the same build I have already installed. But ok, I will try and give here the result
Edit2: It changed nothing. Few seconds after I restart phone it crushed again. Problem is somewhere deeper, but how can I solve it?
I get back to the stock .60 but there is nothing change. I dont have any crushes now, but also i do not have any conectivity. What's the problem? I Still have warranty, but if I can fix this by myself I would like to do that. But I need any hint...
Downgrade? Could that help? I've never before problem which couldn't be solved by flashing the custom rom, it's pretty wierd to me

n910p started freezing since MM , why?

Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now ,
.......
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
This problem is a little confusing and beyond me, but I have to ask and suggest one thing.
Instead of doing OTA, Have you tried to just use odin to flash the Marshmallow firmware you want?
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
Odin MM like suggested.. Don't do any mods. If it persist, then you might be looking at faulty hardware ie main board.
i just flashed MM after reading your replay , and will test it out.
any tips on what to do with the phone if it's a hardware problem ?
so right at the first boot i had this error shown in the images (attachment)
i removed the battery and restart the phone and it booted correctly , the same problems began to show freezing random restart and it keeps booting to recovery and i had to add and remove the battery a couple of times to turn the phone on .
i returned to stock 5.1.1 apparently it's the most stable thing i can use right now , honestly i'm puzzled on this problem i'm quite sure it's hardware and software somehow and if i send it to a local shop they probably will say "i don't know what seem to be the
problem "
so i'm just going to keep using it until it becomes a replacement parts for his other brothers . :crying:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
akira6968 said:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
Click to expand...
Click to collapse
Here is the thing though (I have the same issue). If you remove the battery and put it back in, say 30 seconds later, it won't turn on. If you remove the battery for like 5 minutes and then put back in, it might turn on. I'm talking about the first little vibrate it does when holding the power button to turn on. It really acts like a hardware issue to me. The only work around that has worked for me is an app called wakelock. Using this app and selecting partial partial wake lock makes the phone run completely normal.
What REALLY sucks right now is that I have an OTA update waiting for me and the phone needs to reboot to install. The phone won't reboot. When it turns off, it won't turn back on without removing the battery for 5+ minutes.
IT is the MM Update
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
gbennett21 said:
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
Click to expand...
Click to collapse
Yes having the same issue as well but now even the wakelock app won't keep it. The phone wil stay for maybe an hour, then reboots and will continue to reboot until I take the battery and then start it again afterwards. The length of time the phone stays on varies really and it could be as long as 3 or 4 hours, but it will definitely reboots itself, I cannot got 1 day without this happening. At this point the phone is unusable. I am on another phone at the moment.
I did flash the MM updates (even went back 3 or 4 older versions) using ODIN and same issue. I am debating whether I flash an older Lollipop version and see if that makes a difference.

Categories

Resources