My coworker is not able to OTA update her completely stock (never rooted/modded) Facinate to 2.2, but when she goes to System Updates->Check New, there is a pop up that says "Please Wait" that stays on the screen for a while, then just goes away and nothing happens.
Also, if you go to System Updates->Status, it says "Server Unavailable" Code: 500.
The only thing I can think of is that Verizon is only letting particular regions update at a time to prevent the server from bogging down. Any ideas?
Verizon seems to be having network issues since 2am. Even if you have a data connection, they probably offlines the OTA servers until the problem is resolved.
http://community.vzw.com/t5/4G-Disc...TE-outage-ETA-for-repair-and-other/m-p/513354
She is on stock DI01, and we downloaded the Verizon official ED01, but it says that it cannot find EA28. So, we downloaded EA28 official zip, and now it says that it cannot install because it needs DL09. Sooooo, should we now look for DL09? There has got to be a more simple way...
I'd leave her at stock and just be patient. Verizon's system will come back.
still down
I am having the same issue, even tried the DL09 no luck
I've had the same issues since the day the update came out but I had ODIN'd EB01 and then ODIN'd back to Dl09 and tried everything but got the server unavailable issue. I gave up and just flashed the ED01 update.zip.
After a lot of trying different things and giving up, an awesome dude posted the solution here: http://forum.xda-developers.com/showpost.php?p=13313409&postcount=12 . I followed the steps and it worked like a charm.
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
artvandelay440 said:
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
Click to expand...
Click to collapse
This method is well known, but the OP was asking about OTA.
Related
I updated my vibrant today via kies to JI5. Immediately prior to that I did a nandroid backup. I was experiencing some buggy things after the update, and then I saw that Samsung pulled the update. So I decided to revert back to my previous build. I ran Clockwork recovery and did the nandroid restore. It all seemed to go well. Rebooted the phone and now, well, its stuck on the Vibrant Samsung screen. Nothing else happens.
Did I do something wrong? Is there a way to get back to my previous build, or even back to original stock condition??
PLS help...thanks.
BTW- I can manually get into recovery mode, so i guess I am not hardware locked. I just don't know what the best thing to do next. Thanks.
The new build has a different kernel that is not compatible with previous builds. You can download odin, the 512 pit file and the original JFD tar file and restore to stock that way. After that you can use your nandroid backup to get back to where you were.
doenloading files now
thanks so much...i will try that! fingers crossed.
WORKED! Thanks so much.
What "buggy" things and what did you have installed on your Vibrant before you did the update.
This? Which is 100% your fault?
http://forum.xda-developers.com/showthread.php?t=795390
heygrl said:
What "buggy" things and what did you have installed on your Vibrant before you did the update.
This? Which is 100% your fault?
http://forum.xda-developers.com/showthread.php?t=795390
Click to expand...
Click to collapse
You're right. The settings thing was my fault by installing the wrong MobileAP. But there were other strange things happening as well. A lot of force closes with widgets - particularly "word clock." Also, the phone would freeze and the display would stay on whenever I received a text message.
I guess it's possible that all of that was the result of the wrong MobileAP. But the fact is that the update was pulled due to "known issues" according to Tmo. So its safe to assume - at least for me - that this update is not ready for primetime.
EDIT: To be more accurate - the update was pulled by Samsung for reasons unknown. Tmo then tweeted that the update had "known issues." And now there appears to be a JI6 roaming around. So if JI5 were perfect, why the JI6?
pdefazio said:
You're right. The settings thing was my fault by installing the wrong MobileAP. But there were other strange things happening as well. A lot of force closes with widgets - particularly "word clock." Also, the phone would freeze and the display would stay on whenever I received a text message.
I guess it's possible that all of that was the result of the wrong MobileAP. But the fact is that the update was pulled due to "known issues" according to Tmo. So its safe to assume - at least for me - that this update is not ready for primetime.
EDIT: To be more accurate - the update was pulled by Samsung for reasons unknown. Tmo then tweeted that the update had "known issues." And now there appears to be a JI6 roaming around. So if JI5 were perfect, why the JI6?
Click to expand...
Click to collapse
I had little issues after I updated to JI5. Swype was very inaccurate, other keyboard were very buggy as well. GPS was not working very well, and there was more lag than before. So I did a reset and all of those bugs went away.
i just flashed bionix 1.3 from JI5 through clockwork with no issues.
Wierd that you had any...
adm1jtg said:
The new build has a different kernel that is not compatible with previous builds. You can download odin, the 512 pit file and the original JFD tar file and restore to stock that way. After that you can use your nandroid backup to get back to where you were.
Click to expand...
Click to collapse
Ok, I just flashed from JI5 to bionix 1.3 through clockwork with no issue. Or does JI5 and bionix have the same kernal? hmmmm
Ok so I followed the guide at http://forum.xda-developers.com/showthread.php?t=1057003&page=8 and in the end I picked GreyBlur.
Now I get asked if I want to OTA my cell and I think its due to my system version reading back "Version.4.1.57.MB860.ATT.en.US" and I'm sure thats due to installing GreyBlur, It really should read as a Telstra system version instead but it would appear GreyBlur changed it to ATT.
Anyway of resolving this ?
you should change the title to after installing grey blur (some people may think there is an telstra OTA to be had). this is because the build prop is for the AT&T version as grey blur is based off of that and the update was pushed out to the masses yesterday. you could change the build prop file I guess. which line exactly and to what Im not exactly sure. when greyblur gets updated with the current firmware like gingerblur was, it will cease.
Well I modified the build.prop file to display 1.83 as the system version and so far this has not worked to resolve my issue with the OTA update nag.
I have even gone as far as to rename the otacerts.zip file to otacerts.bak in hopes it would prevent OTA updates and that has not worked either.
I by no means a newbie when it comes to figuring things out or following instructions so my next attempt will be to copy the build.prop file from GingerBlur 3.1 over mine and see what happens.
Ok tried replacing the build.prop file with the one from Gingerblur 3.1 and still I get the OTA nag so not sure how to resolve this, any ideas would be wonderful ...
Interesting, then it appears its reading the info from somewhere else. Here's two things you can try.
check your about phone and make sure the changes were pass through.
Check on the motoblur site if it still reads your device at 4.1.57.
It doesn't look like a greyblur is coming for a couple of days since Ken is on exams.
Ok checked to make sure the changes took effect on the phone and they read back "4.1.83.MB860.ATT.en.US" just how I wanted it so then I checked the motoblur website and it as well reads back the same thing "4.1.83.MB860.ATT.en.US" so I'm stumped as to why it continues to tell me there is an available update for me.
Of course as of today I've been getting a different message which says "This update has been recalled. No action required." This message pops up every so often and is more bothersome then the last lol.
Anyways I guess I'll just wait to see what comes down the pipe on the new release of GreyBlur, One thing is for sure some people out there MAY by mistake take the ATT 1.83 update and I think it would soft brick there phone as I'm fairly sure OTA updates overwrite the bootloader as well as opposed to the SBF updates.
yeah I mentioned that in another forum as well. The other thing is that some people that are on the actual 1.83 are getting the notification as well for some reason.
i'm on the new update had it for a week now(did sbf), i've not had the problems that some have mentioned having, it seems to be running great, BUT I have noticed more wifi disconnects since the update, and not sure why because i'm close the the router and have perfect signal and not using bt either.
Ok so what I've done is froze updater 2.2.1 with Titanium Backup and so far so good no more OTA update nags, Will post back if this doesn't hold.
Search, nothing relating to CM 7.1.
Anyone kow if there is an issue when *228 or *22899 both fail for me.
Thanks in advance for any thoughts.
THey fail for me too :/
I had it glitch twice on my little brothers phone and my gf's.It would end up breaking my service until I rebooted the phone.
And I could not get my gmail accounts to sync because I didn't flash the google add-ons lol...( I haven't rooted or flashed for a long while now)
Yeah, *228 never worked for me on CM7 either. I even flashed a new modem with an EFS wipe
I have read somewhere on here before that it does work just reports on the phone it failed. I just did it to test and the system voice advised it was successful but phone advised failed and try again.
That's exactly what happened, sfobrien. Thanks again for the info. I thought it was funny that one said successful, and the other said not...
Either way, it works, and the ROM is rather nice. I flashed it for my wife who had previously been running a rooted stock. It had updates waiting, but I wasn't even about to let the OTA run.
So far, it's been perfect for her. I'm running the same on my incredible flawlessly.
Thanks!
sfobrien said:
I have read somewhere on here before that it does work just reports on the phone it failed. I just did it to test and the system voice advised it was successful but phone advised failed and try again.
Click to expand...
Click to collapse
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
Click to expand...
Click to collapse
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
startswithPendswithOOH said:
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
Click to expand...
Click to collapse
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
dbow32 said:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
Click to expand...
Click to collapse
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software.
Click to expand...
Click to collapse
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
BladeRunner said:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
Click to expand...
Click to collapse
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
startswithPendswithOOH said:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
Click to expand...
Click to collapse
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
dbow32 said:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
Click to expand...
Click to collapse
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
startswithPendswithOOH said:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
Click to expand...
Click to collapse
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
dbow32 said:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
Click to expand...
Click to collapse
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.
If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
So ive run out of ideas on this problem. I no longer can update my prl and profile. I was on freeza's not3 2.2/2.25b rom had some issues with slow data and other hiccups. Flashed stock debloated and got tired of its blandness so i moved back to freeza's hoping for a better experience now that it had some time. After flashing back to it ive run into these issues.
Poor network signal, unable to update prl or profile with error code 6602. Ive gone stock tar nh7 and reflashed the modem too with no solution. Ive regained network connection after losing it entirely for a bit but still cant update prl or profile. Everybody else is talking how theirs is working great....i havent done anything different. Hope to get some input. Thx ahead of time.
Reminder at this point everything is stock flashed on odin. Twrp recovery latest version. Odin 3.09
Jataadroid said:
So ive run out of ideas on this problem. I no longer can update my prl and profile...
Click to expand...
Click to collapse
I had similar PRL/Profile problems, 'tho I was getting error code 6500. Network connections remained strong and through-speeds were very good. But the failure to update Prl/Profile really pissed me off. I also tried return to stock, other ROMs, but same error 6500. I just lived with it and did the occasional battery pull to good effect.
Then I installed Sacs_Note4 _Ported_apps_Rom_V2.
As part of the installation instructions, I updated PRL & Profile and was shocked when they worked!
Then I set up the phone as I like it, and back to error code 6500.
I turned-off the various Wanam mods and presto, no 6500 error code.
I then added them one at a time, (stuck with a few less this time) and still no error code 6500.
Good luck!