I'm running 2.3.3 on build .270. I'd like to update to build .285 over the air. I've read updating ofa will retain the root. I get an error that it cannot connect. The phone is unlocked and I'm using a tmobile sim. Is that what's causing the problem? Any solutions?
Anyone?
Related
I have tried the links posted in the forum to update my Nexus S but I always get some kind of error.
I own a Nexus S from T-mobile 9020t. I have previously upgraded manually from build GRH78C to GRI40. Currently my phone info states it is on GRI40 baseband JK8. I tried the GRI40 to GRJ22 update file but i get "status 7" error message while updating. I have never rooted my phone and I want to leave my phone unrooted and have the update.
If you know about any such issues and how to resolve it, please let me know.
Thanks.
Just got notification of a new firmware update which im in the process of pulling down its 80mb, will update once I get it and install, anyone know where the change log for this might be located?
logichoops said:
Just got notification of a new firmware update which im in the process of pulling down its 80mb, will update once I get it and install, anyone know where the change log for this might be located?
Click to expand...
Click to collapse
no idea on the changelog but it's MJ6 with baseband MJ4 - got the update OTA yesterday. Guess that blows rooting the phone tho as it'll have updated the bootloader from what I've read elsewhere here.
Dave
not too fussed about root as i don't really need it ATM, just glad we got an update as i normally get unbranded phones, this is the first EE phone and previously when with TMobile they took ages to update..
So as you know 3 days ago a small OTA update came out for Verizon which is pretty much the same one AT&T received last month. On wifi I tried to download the update via OTA on the phone, my phone is not rooted and when I tried to download it it just failed in the middle of downloading and I got the error code 503. The wifi I'm using is very fast and steady and nothing else on the phone is having an issue at the moment. So I tried to download it again and it told me that the software currently installed on the phone(original phone release date software) is the newest up to date software. So I called Samsung and told them the situation along with the new build number "VRU1AOD5"(from the new OTA not installed on my phone yet) and software version number currently installed on the phone(5.0.2) and they told me that I'm up to date 5.0.2 and that to their knowledge they never heard of the update or build number I gave them and there was no update for Verizon. So how I can redownload the OTA? because for 3 days now I'm unable to download the OTA due to the 503 error from the very first time I tried to download the update.
What is mind boggling to me is how Samsung the creator of the device has no idea of this update so they can't even help me out. Then they're basically telling me how the hell am I getting the 503 error when I have the latest build(according to them) and software update which is not the case here and I told them that.
Use the Odin file in the return to stock thread
Hello,
I have an H60-L12 with EMUI 3.1 which was receiving OTA updates till 6.1.1 without any problem.
Whenever I was getting an OTA update I was restoring the stock recovery, un-rooting, updating, installing custom recovery and rooting again. Business as usual.
Since that update I have not received any other OTA update. If I go to the Updater app it does not find any.
I have even restored stock recovery and un-rooted now, just to see if that was blocking the notifications, but no luck.
How can I troubleshoot that? Is there any log file anywhere that I can look?
Thanks in advance!!!
Same thing happened to me on the L02 version and i need to check for updates through VPN connected to Singapore. For example i use tapvpn and i downloaded the developer editions from 16.1 and 1.2 You can try...
Sent from my H60-L02 using Tapatalk
Thanks!!! That did the trick!!
Anyone here experiencing the same thing? I'm on DP4 w build number OPP4.
Enrolled in beta and got a 38+ mb ota.
Whenever I try to update it gets stuck on installing then fails.
Tried to unenroll to go back to 7.1.2 but after the 700+ mb download it fails too. I believe there's a signing issue. Or a google server problem. Im on a Verizon pixel. Locked bootloader. Anyone has an OTA link? Or any suggestions to fix this? This is kinda frustrating lol
edt: manually downloaded the OTA zip and sideloaded it but kept getting this error "kDownloadstateinitializationError". I even tried the rollback 7.1.2 zip and it does the same.
anyone knows what it is? PS. I can't unlock my bootload because Ive got a verizon pixel and can't rma it
Not in a vz pixel but I had the same issue and eventually just went the factory image route
Sent from my Pixel using Tapatalk
I can't flash factory images because my bootloader is locked and can't unlock it =/