Related
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
jaredkent said:
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
Click to expand...
Click to collapse
You can not update a rooted phone. Go to my post on updating 2.2 made easy and you canupdate to 2.2 and reroot the phone. This is the OTA update.
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Either take it to Verizon for them to push it onto the phone or use one of the methods here.
fygar66 said:
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/showthread.php?t=771178
Hi
I wake up and have an update-from-tmo message . The think is that I already have the OTA JI6. does anyone knows something about this?
Anyone?..................
I haven't heard of any other update since J16.
Did you update manually to J16 or use the OTA?
Yeah, how did you update to JI6?
Install it and let us know if your firmware/baseband are the same.
I had Bionix 1.9, which already had the official OTA JI6 version. Still got the message T-Mo about the update, so I just updated it and everything seems fine. Didn't have any problems.
I have a similar problem. I had the update message but didn't want to apply it since I read about all the horror stories. I manually updated to JI6 and baseband version, etc., all reflects this (as does media hub being unlocked, hd camcorder, GPS working, new sorted gallery and other fixes). However, I still have the damn notification that pops up constantly. How do I get rid of it??
I 1st tried OTA but it got stuck on the vibrant screen so I odin the JI5 but ended up with the JI6. Don't ask me how. The odin files I have in my comp are the JI5. Another thing is that I was rooted when I OTA the JI6. Ended up with JI6 rooted
I read some of the threads that they brick their phone after installing J16 OTA from Tmo. I dont know why they brick their phone. We already know that all vibrant user will receive OTA update, right, now this is what I did:
My vibrant, remove one click lag fix from OCLF-RYAN, unroot my vibrant and reboot and do a factory reset. I did all this and the next day I receive OTA update from Tmo, let it install and reboot by itself.
New Task Manager Icon, HD Camcorder and little bit smooth using TW launcher, but Facebook contact sync wont work but according to Tmo, this is a know issue which I agree. Phone is great with J16 update, i root again and install the lagfix V2.+. Did not birck my phone. Hope this helps for those who had not receive OTA and rooted vibrant.
I got a request for an ota just today also.
Can anyone else confirm that's all it is?
Me too.
I delayed it for a day around 1230pm when I woke up from my nap.
Its ji6 iiiiiiiiiii!
Sent from my SGH-T959 using XDA App
I think it bricks my vibrant, just sitting on Vibrant screen after the reboot...
yea. I updated my phone and it stuck on the vibrant screen once i rebooted. The only thing i did was root my phone. No lag fixes. Nothing else. Had to get a replacement phone from Tmobile and unfortunately, its on back order.
i believe you need to factory reset first. delay the update and unroot the phone first and then factory reset. that's what i did, remove lagfix, wifi tether, lcd changer and unroot the phone and factory reset. works with my vibrant.
finally upgraded from DI01 to ED01 and have discovered a problem. the 4 buttons on the bottom of the screen now act weird. they will light up, go out, or flicker depending on what im doing. never had this problem before and i havent seen anyone else post about it but i could have missed it. anyone have any idea?
Did you update stock di01 to stock ed01 or between custom roms?
Sent from my SCH-I500 using XDA Premium App
no, i tried the OTA update several times with the end result being the server IP error. unrooted and tried again several times with the same results. then i followed the link in another post and flashed with odin, the DL09. tried again several times to get the OTA update with no success. had to flash that several times and then finally got it to install. as it sits i am running ED01 stock but rooted. my wifes phone had had all the OTA updates and has always run stock, not even root and has some problems with the buttons as well.
try reflashing a kernel... i only dealt with that problem once a while back and i just reflashed everything and that seemed to fix it.
Also i used to restore system files from titanium backup and sometimes it didn't play nice with whatever i upgraded to and that would cause the backlights to bug out before i got force close messages.
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.