I have been trying to update to the 3.29.651.5 update since its release on September 22 and it just continually says, "Checking..." It never stops. I've left it there for thirty minutes before. It never tells me there isn't an available update nor that 3.29.651.5 is available.
I took the phone into a Sprint store and they said to come back in forty-five minutes for the upgrade (a bit of a wait!). I came back after fifty and they told me they would have to wipe the phone to install the software update.
Is there an easier way to fix this? Sprint support gave me a link to a download for the update, but said it is a risk. Is there a way to just fix what is making it continually check so that it finally just finds the software update by the normal means?
Thank you for any help.
idealisticrealism said:
I have been trying to update to the 3.29.651.5 update since its release on September 22 and it just continually says, "Checking..." It never stops. I've left it there for thirty minutes before. It never tells me there isn't an available update nor that 3.29.651.5 is available.
I took the phone into a Sprint store and they said to come back in forty-five minutes for the upgrade (a bit of a wait!). I came back after fifty and they told me they would have to wipe the phone to install the software update.
Is there an easier way to fix this? Sprint support gave me a link to a download for the update, but said it is a risk. Is there a way to just fix what is making it continually check so that it finally just finds the software update by the normal means?
Thank you for any help.
Click to expand...
Click to collapse
just download the ota from here in the 4g developement area and connect to your pc and update, be sure to sync your contacts first, and back your apps up to just incase, i know when i updated the wife's hero her contacts were ok, and did not get deleted from the phone, the apps i cant remember if i had to add them back in or not.
I ended up doing a factory reset and then the update was able to found normally. Thank you for your help, though.
Related
Well i just got the, as Carlsberg says, probably the best phone out there , i love it, but i have a small little problem. I don't know what happened but when i made the 2.1 update 1 it didn't applied it . u can see the picture where it says 2.1 update 1 BUT the other numbers are like before, and i checked and the changes and they where NOT applied, no HQ youtube, still the problem with the keyboard when long press menu in home screen. I alse checked bootloader, still the 0.75. Now when i check for updates OTA it says : "No new updates available". My phone is not rooted, just got it. And yes, i rebooted phone, several times. No hard reset yet.
First of all, the line with "2.1-update1" is not changed by the update, so that is no indication
With that out of the way, maybe this can help:
http://blog.gamermatrix.co.uk/?p=194
I have not tried it, as my phone updated fine by itself.
Be sure you have the version that it mentions ("unbranded EU"), and even then it is all at your own risk...
You might want to try it first from step 3: if the update is already somewhere on your sd-card, maybe hidden or disguised, then it would be best to use that of course.
For my phone the update lasted about 7 minutes and took about 3 reboots to finish.
Good luck with it!
tx
Oh, tx about the info, i thought it tried to update and failed, i am not eager to do it, i'll just wait for froyo update. I have one more question: i will receive an unlock key to remove my vodafone only limitation, then will i have an unbranded phone or it will still be branded but unlocked?
Hi all,
I tried the search function and could not find anything. So I hope someone can help me. And I hope I am in the right section.
First off, my phone is not rooted. I looked at my phone, and found that the update was available. I was going to wait until I got home and update, so I hit cancel.
I got home, and when doing an HTC update check, it says "No Update available"
I have tried several time, I have used the original rom that the phone came with and it did find the update to 1.32. But now it still won't find the update for the one released today.
Any help on this would be appreciated
Thanks in advance, and that you to all the developers!
Goku
Update was pulled. Damage control team has been pulled in to asses and rectify the current issue. More details as they become available.
Sent from my PC36100 using XDA App
htc pulled the update because for a small number of users after applying the update they would not get the "update sucessfully installed" message and they would either search for the update and see it a second time or would get another message saying it was available again. Downloading and applying it a second time sometimes bricked the phone and it would not startup again. I had this happen to me today but thankfully after I installed it a second time it worked after a longer period with the bricking. HTC software engineers are looking into it. I don't know what this guy is talking about with the damage control devs looking into it because they have nothing to do with the release of official OTA updates they just cook roms
Let me clarify by stating that my previous post does not in any way imply that the "dev" team is working on the OTA issue. Obviously they are not the ones to address the issue.
My apologies Faus if this was not clear enough for you.
Sent from my PC36100 using XDA App
Hello,
I've just started using this phone as my old one died on me and someone gave me this one secondhand.
It seems to have an update available but I can't get it!
If I'm on mobile data only it keeps telling me I have to use Wifi to download it which is annoying as I have unlimited data but there you go.
I've tried on 3 different peoples Wifi and every time it will get to somewhere between 5% and 30% and then error with a message that it can't update and a code of 801881d0.
Very frustrating!
I don't suppose there's any way round this ? If only I oculd download it on my PC and apply it or something but I've read that's not possible.....
Any ideas ?
Thanks,
Dan
Hi, how much storage space do you have on your phone?
Well after 5 days of it failing to download on any WIFI connection I tried, suddenly the other night it said it had downloaded it. Hooray!
So I told it to install it, to which it told me I hadn't got enough space so I removed eveything I'd installed..... still not enough so I ended up uninstalling everything that it would let me on the phone till I was down to the bare minimum of apps and finally it decided to work.
After the update it decided it fancied going into a boot loop just to finish off the joy. After 20 minutes of fiddling with power and volume down combinations I eventually managed to get it to boot up and now, after another 2 updates, it finally says "Your software is up to date"
Phew!!!!
That was a lot more painful than it needed to be but we got there in the end!
Glad you got it fixed.
I believe the GDR3 update (which I think you were doing) is something like 800mb or so.
So basically you need to uninstall most of your apps to download and install it (I had to).
So WP8.1 should be fun to install! (Assuming it is released for the HTC 8S)
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
pbrady5 said:
I've tried searching around here for an answer, but I haven't really been able to find anything solid regarding the issue that I'm experiencing. The other day I popped my sim card into my sgh-i467, as I do from time to time, to check for any OTA updates. This device is usually mounted in my vehicle, so I don't regularly check for updates. Sure enough, an OTA update was available. Tablet was at maximum charge, so I went ahead and chose to do the update. Unfortunately, the update failed at around 93% and went into a boot loop. There was nothing crucial on the device, so I figured it'd be no big deal to just re-flash the firmware if need be. However, I can only seem to find a KIES image for 4.1.2, and while I didn't think to verify exactly what version I was on before the bootloop/brick, I'm fairly certain I was on 4.2.xx.
From what I understand, the bootloader updates with 4.4, correct? With the bootloader getting updated, downgrading to 4.1.2 isn't possible or feasible, right? I didn't think to confirm this before I attempted to flash the KIES image for 4.1.2 via odin (kies never seems to actually see my device), which fails every attempt. I was originally able to get into recovery, but I kept seeing that /system wasn't found. I'm assuming that the OTA update partially installed, before failing, and either corrupted the partition scheme or updated the bootloader but not the system?
I'm dead in the water at this point, and AT&T is obviously no help. Plus, I don't the device on contract with them anyway, so I'm starting to think that my only option is to contact Samsung. However, I really don't want to have to send the unit in, and given it's age, I don't think it's worth investing anything in it if the repair isn't covered somehow. Plus I enjoy tinkering, I'm not new to the scene, and I'd really like to come up with a solution that doesn't require Samsung.
I don't suppose any kind people out there have any suggestions, similar experiences, etc. do they? I'd really like to hear from anyone who's got something to offer! Thanks in advance for your help!
Click to expand...
Click to collapse
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
gooberdude said:
You need to upgrade to keis 3.0 and reboot, then start kies, then boot note into download mode and have kies detect and reload the update.
Too bad you let the Note update to Kit Kat, Jellybean is better, on the LTE Note.
Click to expand...
Click to collapse
Thank you very much for the information! Unfortunately, I've tried Kies 3.0. It notifies me that my device isn't compatible with Kies 3.0. With the other version of Kies, 2.6 maybe(?), it never ends up being able to connect. I've tried manual initialization, but when after I enter my model number, it won't accept my serial.
Take it to a BEST BUY with a Samsung Experience Center (Kiosk (Most all of them in larger cities have them) and they will fix your SGH-i467 for free. I did almost the same exact thing as you (trying to solve a EFS problem) and was stuck. I have posted about it on here before. They will not charge you BUT you may run into a clueless rep now and then. If you do, ask them to call for help and they will get you fixed up in a hurry. Hope this helps.