When my G2x was stock unrooted it always failed authentication when checking for an OTA update. I had always assumed this was because I'd done a desktop install of the LG Gingerbread update. After I rooted my phone I tried installing the stock Froyo ROM to test my theory and it still failed.
No problem, I thought, because I'm gonna install CM7. Well now I'm running CM7 and when I go to the section to register the phone for push update notifications I get the message "Registration failed."
Are these two issues connected and what might the problem be?
Once you're rooted, I don't think you can get OTA... when I had my rooted Mytouch 3g I was told to not accept ota or phone might mess up. Plus CM7 is better than stock
kompheak said:
Once you're rooted, I don't think you can get OTA... when I had my rooted Mytouch 3g I was told to not accept ota or phone might mess up. Plus CM7 is better than stock
Click to expand...
Click to collapse
The failed authentication to connect to T-mo's servers was before I rooted. I'm not so concerned about that as I am about the phone failing to register for push notifications of CM updates. The only reason I mentioned the authentication error with T-mo is because I ws wondering if they might be related.
Related
i dont have the OTA on the TB i just got today, when i go to Updates it says looking, then it does nothing. i have only tried it on 3g, do i have ot check it under WIFI instead?
thanks
dvigue said:
i dont have the OTA on the TB i just got today, when i go to Updates it says looking, then it does nothing. i have only tried it on 3g, do i have ot check it under WIFI instead?
thanks
Click to expand...
Click to collapse
If you plan on rooting, then don't bother with the OTA. You'll have to wipe the phone while rooting, then update to the latest. If you don't plan on rooting, then the OTA should show up when tell it to check. What version does it currently say you are running?
Even if you don't plan on rooting, I still wouldn't update. Otherwise you may end up frustrated with reboots.
I got my TB back in May. Didn't have one issue until I did the update. Since I only had the phone for 11 days VZW told me to walk into a store and exchange for a new one. I have had no issues with the new phone and will stay clear of that update. Wait until GB comes out and hopefully that will fix what ever is wrong.
So from what I've been reading it seems that the only difference from the two updates is that the T-Mo update has the green signal bars in the notification area. Everything seems to be the same else where; baseband, kernel, etc. They only problem I've had with the LG update is that sometimes it does freeze up and I have to reboot the phone Otherwise everything else been pretty good.
Is there a way to go back to Froyo and get the T-Mo OTA update?
when I go to "Check for software updates" it warns me with "connection failed cuased by authentication error" Am I the only one getting this message when I try to update my g2x?
Why don't you upgrade through LG?
Sent from my LG-P999 using XDA Premium App
jlsolorio5746 said:
when I go to "Check for software updates" it warns me with "connection failed cuased by authentication error" Am I the only one getting this message when I try to update my g2x?
Click to expand...
Click to collapse
I'm getting the same thing. I was rooted so I could freeze crapware, but have unfrozen and unrooted. My phone is a replacement/refurb, which apparently can't be updated using the LG tool. Hopefully the same isn't true for the OTA update.
the reason I dont update using lg's tool is because of bricking issues, plus since the ota is out for tmobile id figure its safer to get it from them, does the ota come to you? or do you manually search for the update?
I tried today to OTA update my phone and it said I had the current version even though i DID NOT update to GB before. Does anyone know why? I restored the stock, but did not unroot nor nvflashed to stock. I wanted to check for update first and afterwards to unroot and revert nvflash...
krekabl said:
I tried today to OTA update my phone and it said I had the current version even though i DID NOT update to GB before. Does anyone know why? I restored the stock, but did not unroot nor nvflashed to stock. I wanted to check for update first and afterwards to unroot and revert nvflash...
Click to expand...
Click to collapse
I'm back on froyo ATM and I get the same message. They could be releasing it from coast to coast, from east to west. Pushing the update to all G2X users at once would slow the network down drastically.
Sent from my LG-P999 using XDA Premium App
I'm on the east, didn't get mine yet....
I get an authentication error with mine.
same here, "authentication failed".. does this mean we wont be able to get the update?
To me, it seems all so clumsy...
anyone that got an authentication error managed to get the ota gb update?!?!?!?!
Whenever I try to do the OTA update for Jelly Bean, I get an error message saying that Service is Unvailable, even if I have full reception or Wifi connection. While I realize I can easily update the software using open1your1eyes0 thread, http://forum.xda-developers.com/showthread.php?t=1974114, I'd rather just keep the phone stock for the time being.
Is there a way to overcome this error message? Additionally, for some reason Verizon thinks I'm still using my nexus device and won't reupdate my phone to S3, even though I switched Sims.
I have had the same problem on other phones when i was trying to update. The only solution that i have found to work is a Factory Reset. If you dont want to do that however you can always flash the STOCK update through ODIN and you DO NOT have to root your phone to install the STOCK image. The details are in the link that you posted. Just download #8 it has no root and the stock recovery image.
I activated a new sim and that seemed to do the trick. I'm tempted to root the phone eventually. I've just noticed I've had some GPS and 4G data connection issues after I root my device.
I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse
You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.
I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium
kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse