I never received the OTA so I downloaded the captured one and installed it. After I was finished my phone automatically downloaded another file "PG05IMG_MECHA_VERIZON_WWE_1.70.605.0_RADIO_1.39.00.0627r_NV_8K_141_9K_1.64_RELEASE_200422_SIGNED.ZIP" that is 35.27k (3,117 Bytes). Does anyone know what I need to do with this file? Any help will be appreciated.
Thanks
EDIT: I just received my first reboot. The phone came back up in 3G for a few minutes and then switched back to 4G.
Since I received a new phone due to the reboots, This is the first time it has done it. Now, with the latest update I'm starting to get them. I'm about ready to jump ship. I'm so sick of waiting and having issues.
Related
I'm downloading a new software update . I had already installed the last update.
edit
When I say last update I meant the one with the GPS fix.
What else could this be besides froyo ?
edit
Something funny happen, the update didnt install and now I cant check for another one.
edit
I changed the date on my phone so now I'm trying the update again.
edit
It keeps failing, so I dont know what this is .
wrong.........
i tried 4 times, wasted many of my limited data, never get updated. Att sucks.
pobinghun said:
i tried 4 times, wasted many of my limited data, never get updated. Att sucks.
Click to expand...
Click to collapse
AT&T doesn't charge you for anything that comes from the update server. You sir, suck. ;-)
i just got my brand new phone in the mail yesterday, im just gonna wait till it tells me there's an update before I download any updates..
link12245 said:
AT&T doesn't charge you for anything that comes from the update server. You sir, suck. ;-)
Click to expand...
Click to collapse
It sure does show up under data used, so I assume that it will be counted against you data plan.
Is your phone rooted? Showing symptoms associated with.
AGAIN
Yeah I have no idea what this update is ? This is like the 5th time it failed on me, so forget it.
I am rooted.
When I got the update, I had just gotten the phone. The update went through just fine, the day after I rooted my phone. So maybe rooting had something to do with it. I don't see how that could effect it but maybe.
I think it's time you detach the umbilical cord to the OTA update Update using Clockwork. (Just a suggestion).
Obviously, I've got an issue on my hands.
Let me start by saying my Captivate has been unlocked. I remember buying my captivate after it'd probably been out a week and had updated it on here with an update.zip that I downloaded. That had rooted the phone pretty early on. I had saved the old phone data/backed it up, but I can no longer find where I saved it
In any case, I need to update the phone one way or another to see if that will resolve the issue. What would be the best way to go about this?
Here's some info that I feel I should add that is relevant:
If I power cycle the phone, I get a message that says no update was applied to the phone.
Firmware: 2.1-update1
Baseband Version: i897UCJH7
You already has the latest update JH7, at least according to what your info indicates.
What issue do you have?
foxbat121 said:
You already has the latest update JH7, at least according to what your info indicates.
Click to expand...
Click to collapse
I think so too, but I keep getting the message that the update wasn't applied every so often. I'm not too concerned, since my phone's not downloaded it recently and tried installing it lol
kegobeer said:
What issue do you have?
Click to expand...
Click to collapse
not getting any MMS/SMS. The last time it did this, it eventually 'fixed' itself and I got a flood of texts all at once. However, it's again stopped.
I read awhile back that google's been having some messaging issues with Android, and I think this might be my case . All other service works fine (Data, voice, GPS)
Hi folks,
My Shield 32 GB just arrived and is charged up. I've signed on with a google account and done nothing else.
I will eventually root it but want to put it through its paces for a month or so first.
It arrived with KK 4.4.2 (wow! so old!) on it. It offers an OTA update from October 2014. Says it is OTA 1.21. I've seen LOTS of other OTA numbers much later around these forums. Do I have to take the 1.21 OTA before I can get to the more recent ones?
And, by taking the OTA, am I doing anything irreversible that I probably shouldn't do, since I'm eventually a rooting and maybe ROMing kind of guy?
Thanks. I've read up and it looks like I probably want to go all the way to the 5.1 release, once they sort out the speaker-killing bug. But for the moment I'd like to make sure I'm not missing anything before taking the OTA.
Thanks!
Marc
I decided to download the update after I successfully activated the device on AT&T's cellular network.
That was a bit of a hassle... couldn't do it from the device (the ATT app said something about incompatibility with the SIM card), the PC online web registration wouldn't accept it because NVidia Shield wasn't listed in the device types, and it took the efforts of 3 ATT folks to get me activated. First one passed me to the second one when he found out it was a device not purchased from ATT (but... dude... here's the SIM and IMEI number that's all you need...), the second one set me up and told me to call another number to accept terms and conditions. Did that, still no joy, found the default APN isn't set up right. Fixed that, still no joy, eventually talked to person 3 that found out they didn't attach a data plan to the device when they set it up... as part of my family shared data account. Duh.
Anyway, I applied the 1.21 and then it prompted me to download the 2.1 update to Android 5.01. It has downloaded. I think I want to copy it over to my PC before I let it apply.
Marc
Hmmm. Poked around and found the 1.21 update but not the 2.1 full LTE OTA. Perhaps I'd need root to get at the files. Oh well. I can always download it if I need it. Applying the 2.1 update now.
And I've made it all the way to the 2.2.1 hotfix. Seems stable enough for the moment.
I understand OTA 3.0 got pulled; so I guess I'll be staying on Lollipop 5.01 until they release the fix.
It's a bit surprising that I had to do all the updates sequentially and that there wasn't any direct-to-the-latest. But it didn't take long. I wonder if all these OTAs are clogging up my memory somewhere?
OK, on to exploration!
Marc
the update got pulled indeed, caused all kind of problems, including blown speakers
nvidia employee told us on nvidia forum they would release a new OTA 3.1, targeted end of june
lastest news: it's now targeted end of july....
So I'll try to keep this as short as I can. Basically, this is my gf's phone that she gave to me. Ever since it updated to 6.0.1, she's had nothing but problems with it. Constant freezing, lagging, restarts, SMS trouble, poor battery life, you name it. Recently AT&T rolled out an update and her phone upgraded automatically. After that it pretty much bricked. The update failed for some reason and the phone got stuck in Download Mode. And then it didn't turn on for almost a week. Since her phone is a couple months out of warranty, she was forced to upgrade to an S8, and she gave me this Note Edge.
Yesterday I spent a few hours trying to fix it. I finally managed to get it to power back on and flash a PIT file to it, then flashed a fresh install of 6.0.1 to it. It worked okay for maybe 10 minutes, but then it would reboot every time you tried to lock or unlock the screen, and was still super laggy. So I decided to to give it another try and I managed to downgrade it to 5.1.1. It seems to be working great at the moment (fingers crossed).
So after reading here in the forums, it seems that you can't root AT&T Note Edge's. Bummer. I was hoping I'd be able to disable updates on this phone, unlock it, and use it on a new carrier (I think Verizon is trying to kill my Note 4 now).
So my question is, is there any way that I can keep this phone on 5.1.1? I know this sounds stupid, but I'm not sure how AT&T updates work, if they're forced or you just get annoying pop-ups. Right now I'm reluctant to connect the phone to WiFi, and there's no SIM card in it. Either way I'd just like to disable updates.
I haven't messed with rooting since my S4, which was about 3.5 years ago, but if there's something I can do to keep this phone on 5.1.1, I want to try it. Thanks.
camismacho said:
So I'll try to keep this as short as I can. Basically, this is my gf's phone that she gave to me. Ever since it updated to 6.0.1, she's had nothing but problems with it. Constant freezing, lagging, restarts, SMS trouble, poor battery life, you name it. Recently AT&T rolled out an update and her phone upgraded automatically. After that it pretty much bricked. The update failed for some reason and the phone got stuck in Download Mode. And then it didn't turn on for almost a week. Since her phone is a couple months out of warranty, she was forced to upgrade to an S8, and she gave me this Note Edge.
Yesterday I spent a few hours trying to fix it. I finally managed to get it to power back on and flash a PIT file to it, then flashed a fresh install of 6.0.1 to it. It worked okay for maybe 10 minutes, but then it would reboot every time you tried to lock or unlock the screen, and was still super laggy. So I decided to to give it another try and I managed to downgrade it to 5.1.1. It seems to be working great at the moment (fingers crossed).
So after reading here in the forums, it seems that you can't root AT&T Note Edge's. Bummer. I was hoping I'd be able to disable updates on this phone, unlock it, and use it on a new carrier (I think Verizon is trying to kill my Note 4 now).
So my question is, is there any way that I can keep this phone on 5.1.1? I know this sounds stupid, but I'm not sure how AT&T updates work, if they're forced or you just get annoying pop-ups. Right now I'm reluctant to connect the phone to WiFi, and there's no SIM card in it. Either way I'd just like to disable updates.
I haven't messed with rooting since my S4, which was about 3.5 years ago, but if there's something I can do to keep this phone on 5.1.1, I want to try it. Thanks.
Click to expand...
Click to collapse
You should be able to turn off auto updates in the about phone area of the settings menu.
You might want to turn off the picture sync'ing in the settings area of gallery....three dots,top right corner.
**Solved posting update in thread.
Purchased S21+ from Samsung online for Verizon Network, every OTA update since purchase results in it failing to the downloading screen with "
partition super Reason SUPER: Build-id does not match with the reference" I have been able to resurrect it successfully by entering the recovery mode and performing a factory reset. But each OTA update push results in the same issue.
Samsung wants me to either send them the phone or take to a repair location for a software refresh as they called it. Problem is nearest repair center is 3+ hours away from me or 5-7 day turn around on the mailed device with no backup phone.
Has anyone else encountered this and does anyone here have a solution to fix this myself? I am comfortable using Odin and flashing roms but not sure if this will fix it.
have you talked to verizon?
Post Nine said:
have you talked to verizon?
Click to expand...
Click to collapse
Yes, Spoke with their Tier 2 support. Tier 2 discussed the issue and implied a change of information for the phone would fix it. They transferred me to Samsung due to the phone being purchased direct from Samsung.
Ok so the problem seems to have been resolved. Here's what I did to fix it.
Downloaded the current firmware I had before the update from Sammobile.com. Using Odin I installed the firmware I was currently on. I had done this before on the last update that failed. But this time I gave it the user data info and did use the Home CSC in an effort to reset everything.
Phone came back online functioning normally with everything wiped. I connected to WiFi and let the first of 2 updates download then run. Success . First OTA that's been successful on the phone. Then went for update #2. Failed, but rebooted this time and gave me an Error 402. Tried again a little later, same WiFi. It redownloaded the update and success again.
So it seems it needs a very very stable internet connection and the full wipe fixed the build id mismatch.
Also before attempting updates highly recommend having all your 2FA accounts either backed up, a second authenticator on another device or turned off. Its a real PITA to get back into all your accounts when your authenticator app gets wiped unexpectedly.
Hope this helps someone else!
CBH60 said:
Hope this helps someone else
Click to expand...
Click to collapse
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Ardera_Sempre said:
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Click to expand...
Click to collapse
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
AliRAS said:
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
Click to expand...
Click to collapse
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Ardera_Sempre said:
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Click to expand...
Click to collapse
Damn that sucks never heard of them needing the charger as well for tests, that is a bit odd. The reflash seems to have fixed the rebooting issue I had when I first got my S22+ not sure if I should gamble with trying to update again after the last one failed. Might just wait for One UI 5 and do a dirty flash through Odin and if it doesn't give any problems I'll just flash the security updates every so often I guess. Saves me the stress haha.