Related
AT&T just SMSed me that the update is coming soon and I should press OK when prompted.
Quote, "AT&T FREE MSG: AT&T is providing a free update for your phone. When asked to install the update, please select OK. Thank You."
FYI
Sent from my SAMSUNG-SGH-I897 using XDA App
nirvani said:
AT&T just SMSed me that the update is coming soon and I should press OK when prompted.
Quote, "AT&T FREE MSG: AT&T is providing a free update for your phone. When asked to install the update, please select OK. Thank You."
FYI
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Uhhh, you are about 1 week to late for this information. Thanks though.
I was rooted, no lagfix when I tried to update. It got to 100% then it said failed. My baseband says I897UCJH7. Kernel 2.6.29 [email protected] #2.
Did the update work or not?
Flashman, how did your OTA update go? Any issues us rooted/unlocked folks should be worried about?
My instinct is to delay the update until I stop seeing posts about hot it F'd up people's phones.
Sent from my SAMSUNG-SGH-I897 using XDA App
nirvani said:
Flashman, how did your OTA update go? Any issues us rooted/unlocked folks should be worried about?
My instinct is to delay the update until I stop seeing posts about hot it F'd up people's phones.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you rooted and removed anything from stock rom, you're pretty much guaranteed to fail on OTA update. In order to make the OTA download package as small as possible, Samsung uses a diff patch based on the bit differences between stock JF6 image and new JH7 image. So, if you touched the JF6 in any unauthorized way, the patch won't work.
Luckily, you can now use the newly released Kies Mini to do a full ROM update which should be more reliable as you have the entire ROM image downloaded to your desktop and then flash to your phone.
foxbat121 said:
If you rooted and removed anything from stock rom, you're pretty much guaranteed to fail on OTA update. In order to make the OTA download package as small as possible, Samsung uses a diff patch based on the bit differences between stock JF6 image and new JH7 image. So, if you touched the JF6 in any unauthorized way, the patch won't work.
Luckily, you can now use the newly released Kies Mini to do a full ROM update which should be more reliable as you have the entire ROM image downloaded to your desktop and then flash to your phone.
Click to expand...
Click to collapse
What does it mean if Kies mini says Firmware version: unregistered device?
rcm921 said:
What does it mean if Kies mini says Firmware version: unregistered device?
Click to expand...
Click to collapse
Quoted by Samsung "The program can report this message if it detects a software build other than the official launch software of JF6."
You need to FLASH STOCK JF6 using ODIN ONE CLICK, Follow this Guide:
http://forum.xda-developers.com/showthread.php?t=794363
Colton5419 said:
Quoted by Samsung "The program can report this message if it detects a software build other than the official launch software of JF6."
You need to FLASH STOCK JF6 using ODIN ONE CLICK, Follow this Guide:
Click to expand...
Click to collapse
If my settings say i'm at JH7, does that necessarily mean the OTA update was completely successful? It reached 100% then said failed.
foxbat121 said:
If you rooted and removed anything from stock rom, you're pretty much guaranteed to fail on OTA update.
Click to expand...
Click to collapse
What do you mean removed anything from stock rom? I rooted and removed a bunch of the bloatware and did an OTA update with no issues.
I failed along with most other rooted and flashed guys. Luckily I didn't brick my phone in the process. I will wait until some beret update comes along before trying anything ota again.
Sweet life
Nevermind, I guess it didn't update fully cause some of the implemented changes aren't there. I really didn't want to have to run a master clear and have to reinstall all my stuff.
rcm921 said:
Nevermind, I guess it didn't update fully cause some of the implemented changes aren't there. I really didn't want to have to run a master clear and have to reinstall all my stuff.
Click to expand...
Click to collapse
Did you try to update with mini kies?
Colton5419 said:
Did you try to update with mini kies?
Click to expand...
Click to collapse
Trying to figure out a way to do it without having to wipe everything right now. But no luck.
rcm921 said:
Trying to figure out a way to do it without having to wipe everything right now. But no luck.
Click to expand...
Click to collapse
Do you have TouchWiz as your default launcher? and make sure you're on your home screen when you connect your USB cable.
If that doesn't do it you need to get back to JF6 only way or another because Mini Kies will continue to tell you that you have an "unregistered" device until it is at JF6
The reason is because your update failed partially :/
are you guys talking about a new update or just JH7?
We're talking about JH7, some people are still having difficulties getting it on their phone as the OTA is still failing - and if you've failed the OTA you need to reflash to stock before mini kies will work.
when i did the update i was rooted an it didn't fail on install or bootup or anything.
but then again i'm just rooted and nothing else has been touched.
wade7919 said:
when i did the update i was rooted an it didn't fail on install or bootup or anything.
but then again i'm just rooted and nothing else has been touched.
Click to expand...
Click to collapse
Exactly, I don't think root causes any issues. I was able to check for update on a rooted ROM.
It's when you have a custom kernel etc.
flashman2002 said:
Uhhh, you are about 1 week to late for this information. Thanks though.
Click to expand...
Click to collapse
Not really. AT&T has said that the real update will be sent out via SMS text message link, not through the "update software" menu in android.
Engadget just had that yesterday.
derek4484 said:
Not really. AT&T has said that the real update will be sent out via SMS text message link, not through the "update software" menu in android.
Engadget just had that yesterday.
Click to expand...
Click to collapse
It's the same thing.
Hi,
I got the notification that a new update was available so clicked to install it and it rebooted then got the orange bar showing its progress. Now I just left the tablet for a couple of hours and have now just looked at it again and it had the screen asking me if I wanted to install the update?? So I clicked install and it said the update failed, so I was wondering if someone who has done the update could post their details in the About section so I can see if my wifi version, kernel version etc are the latest versions?
Thanks.
http://forum.xda-developers.com/showthread.php?t=1041502
I've posted a few screens there in the first post of the build revisions. One pic is the original device with no update, the other two are updates 1 and 2 respectively. They are named as such so you'll see which is which.
stuntdouble said:
http://forum.xda-developers.com/showthread.php?t=1041502
I've posted a few screens there in the first post of the build revisions. One pic is the original device with no update, the other two are updates 1 and 2 respectively. They are named as such so you'll see which is which.
Click to expand...
Click to collapse
That's odd. I just did the first update yet it matches the original screenshot you've posted. It says there's another update (the second I presume) but it's not downloading it. Weird.
case0 said:
That's odd. I just did the first update yet it matches the original screenshot you've posted. It says there's another update (the second I presume) but it's not downloading it. Weird.
Click to expand...
Click to collapse
Strange, I guess your tablet had a newer firmware to start off with then. When did you purchase yours? And was it in the UK you bought it? There have been 2 updates for me so far.
I'll reply in the other thread so as not to spam this one too much
From Asus developer
I'm sorry for this problem. Can you try to click Settings -> About -> Check System Update? If you are still not able to update successfully, we will provide you an SD update file later.
Eric Liu said:
I'm sorry for this problem. Can you try to click Settings -> About -> Check System Update? If you are still not able to update successfully, we will provide you an SD update file later.
Click to expand...
Click to collapse
Are you really an asus developer? A couple of us could SERIOUSLY use your help. Please please please check out this thread http://forum.xda-developers.com/showthread.php?t=1051776
I manually updated from ASUS website (using the 5/1 software) and am still receiving the OTA notification in the system bar. Is there an easy way to remove this? Is there a file on the device that I need to delete? I already deleted the ASUS folder from the micro SD card that contained the update.
Thanks
EDIT: I went ahead and tried to update and it told me that the update failed. It then told me it was going to revert to blah blah blah, which basically did nothing and then went back to the home screen. This may only work if you have the same exact version that the system is trying to update to. After accepting the failed update notice, the notification went away.
What I did was clear cache and tried to run the update. It failed and the notification went away. This was however after I rooted and installed clockworkmod.
Sent from my ADR6400L using Tapatalk
tineras said:
I manually updated from ASUS website (using the 5/1 software) and am still receiving the OTA notification in the system bar. Is there an easy way to remove this? Is there a file on the device that I need to delete? I already deleted the ASUS folder from the micro SD card that contained the update.
Thanks
Click to expand...
Click to collapse
+1 I have this as well.
if u run it it will more than liekely fail and the notif wil go away
JMQUINT00 said:
if u run it it will more than liekely fail and the notif wil go away
Click to expand...
Click to collapse
Normally I would, but I don't want to be the guinea pig when there is such a limited supply. If something get's screwed up, I may have to wait weeks to get a replacement.
EDIT: That is exactly what happened. I updated my first post and the title.
i have stock 4.0.3. I try to download the OTA 4.0.4 but I get the red triangle with the green android as it is trying to install. did these steps and it still won't update:
1. go to setting / apps then hit the all button at the top
2. scroll down to google services framework and then press it to open
3. hit the clear data button
4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )
5. hit the check now button
6. xoom should show you the 4.0.4 update avalaible
7. hit install and enjoy
any suggestions?? seems like I have to send it in to Motorola for them to manually flash this update
a bunch of users in the Official Motorola forum also have this issue: https://forums.motorola.com/posts/0212457c59
vinnyt225 said:
i have stock 4.0.3. I try to download the OTA 4.0.4 but I get the red triangle with the green android as it is trying to install. did these steps and it still won't update:
1. go to setting / apps then hit the all button at the top
2. scroll down to google services framework and then press it to open
3. hit the clear data button
4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )
5. hit the check now button
6. xoom should show you the 4.0.4 update avalaible
7. hit install and enjoy
any suggestions?? seems like I have to send it in to Motorola for them to manually flash this update
a bunch of users in the Official Motorola forum also have this issue: https://forums.motorola.com/posts/0212457c59
Click to expand...
Click to collapse
It's because you're not using a stock recovery. Go into your /cache folder, pull the file out of there and put it on your internal storage somewhere, then go into whatever recovery you use and flash the zip file.
You can only do the auto OTA installs if you're using stock recovery. Otherwise, you have to flash manually. Just the way it is.
thanks for the reply oldblue910. I don't have any zip files anywhere. Everything i am trying to do is over the internet. But if you could guide me your process maybe i'll try your way.
vinnyt225 said:
thanks for the reply oldblue910. I don't have any zip files anywhere. Everything i am trying to do is over the internet. But if you could guide me your process maybe i'll try your way.
Click to expand...
Click to collapse
OK first off, I assume you're rooted, yes?
i am not rooted...forgot to say that. completely stock. tablet came with 4.0.3 and was new out of the box.
vinnyt225 said:
i am not rooted...forgot to say that. completely stock. tablet came with 4.0.3 and was new out of the box.
Click to expand...
Click to collapse
Interesting...the OTA should apply fine then. OK here's the next thing. Go and flash the OTA as normal. Once it gets to the Android with the red triangle, press and hold the power button, then press volume up (while holding down the power button). Some text will appear on screen. Please post that text here.
oldblue910 said:
Once it gets to the Android with the red triangle, press and hold the power button, then press volume up (while holding down the power button). Some text will appear on screen. Please post that text here.
Click to expand...
Click to collapse
Same exact issue here!!!!
I did that, and it reads in yellow text:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
That means for some reason the downloaded file is corrupt...hmmm....not quite sure on that one...
Sent from my Xoom using Tapatalk 2
From what I can read, the only way to get 4.0.4 is to either root of send it in to Moto. Here is a link that I read that is about the same issue.
*** I tried to post the link but since I am a new member I can't post outside links. It is on the motorola xoom owner's forum
False. If you haven't dicked around with your tablet and wait for the OTA notification like a good boy, it installs fine.
Sent from my Xoom using Tapatalk 2
I'm having the exact same issue, and I'm two for two on brand new Xoom's that will not install the update right out of the box.
---------- Post added at 07:11 PM ---------- Previous post was at 06:21 PM ----------
MikeMBau said:
Same exact issue here!!!!
I did that, and it reads in yellow text:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I'm getting the same text(obviously), but at the top of the screen, are you guys seeing these 4 options:
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
?
I'm sure you are. The one I'm interested in is the "apply update from USB drive", because someone at Xoom Forums suggested doing the update from a USB drive, but with a USB host cable, and it was a different method than what I think this option is suggesting, but mu understanding is that using a USB host cable doesn't work with an unrooted Xoom.
This option makes me curious.......and I'm wondering if it would see the update on a USB drive attached to the Xoom, should you have it attached with the stock 4.0.4 zip file on the USB drive, and selected this option.
I'd never do it unless someone said it would work.
All that being said, it also seems that if you installed a recovery, and rooted it, that you could flash the stock 4.0.4, but I'm just assuming that's right.
You know guys, I totally forgot about this...
If you are on 4.0.3 and trying to update manually to 4.0.4 in stock recovery via OTG cable, you will not be able to. There is a bug in the stock recovery that only allows flashing OTAs when using the OTA notification software, and will fail if attempted manually.
This topic was beat to death when the 4.0.4 OTA for the WiFi Xoom came out back in April. The Nexus S had the same problem as well because of the same stock recovery bug. If you want to read up on it, just do some searching here on XDA. There was a ton of chatter about it.
Sent from my Xoom using Tapatalk 2
oldblue910 said:
If you are on 4.0.3 and trying to update manually to 4.0.4 in stock recovery via OTG cable, you will not be able to.
Click to expand...
Click to collapse
Nope, this is all in reference to OTA updates. None of us are attempting to install it manually. It is a known issue with this device.
I don't get why you think I "dicked around" with my tablet... I got it in the mail, saw it was on 4.0.3 and just went to settings>about tablet>system updates. I haven't "dicked around" at all.
Do you have any other ideas in order to get 4.0.4 on my Xoom? Is the USB host cable worth a shot?
This is what someone on the Motorola support forums had to say about this:
I agree with the possibility that the OTA package could be corrupt and there are theories out there that Google's process is causing the issue, but no confirmation. The problem with the storage of Android OTA images is that they reside in a system partition without user accessibility, so if they are corrupt, the system just keeps trying to install it.
Let me share your details with the Motorola Tech I have been working with and see what your upgrade status shows.
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that. If someone told me that the USB works, then I would rather do that instead.
MikeMBau said:
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that. If someone told me that the USB works, then I would rather do that instead.
Click to expand...
Click to collapse
Yeah, I haven't pulled the trigger on that decision yet. I have to sleep on it. I told the one guy I talked to, who was "level 2"......Motorola is doing nothing about this. He said "we are doing something........we'll send you a box". Great answer.
On the USB thing.....I feel the same way, but sounds like you have to root it to do that. If I root it, it will be because I want to, and right now I don't. I just bought it. I'm on my second one in 3 days that has the same issue. If I root it, I'm going to cut to the chase and just flash a custom ROM, and I won't have to worry about updates. Right now I just don't want to do that.
On a side note, make sure they're real clear on what the issue is with your Xoom. The reason I say that is that I saw one lady post on the Motorola support forums that she has two Xooms that she bought at the same time, with the same issue you and I have, and they simply put "repair" in the notes. She got them both back, and they still had 4.0.3 on them, and wouldn't update. Read the second post on this page, from "Sharon"
https://forums.motorola.com/posts/0bc09ed02d?commentId=613182#613182
Totally ridiculous.
I was just about to say "screw it" and send it in, and then read that. I'd go through the roof if that happened to me. I still might send it in, but I'm just really uncomfortable doing that with something that has an issue right out of the box, but I don't want to keep sending them back to Amazon, with the hope that the "next one" will update correctly.
Trust me.......any method that would work to resolve this, that didn't involve rooting the damn thing, I'd be all over, just like you.
Just read this post from a guy on the Motorola support forums that has been talking to a Motorola tech he knows:
"The Android OS always downloads an update first (to a system-only partition), does a basic validation (like total size) and then applies the update to your system. What I have heard from other developers is that if the update fails (for any reason), the OS does not download a new copy nor delete the current image, it just keeps trying to reinstall the same image. If that is true, then someone (like the service center) may have to unlock the Xoom and apply a new image to resolve the issue."
MikeMBau said:
I submitted a ticket online to send my Xoom in.
Click to expand...
Click to collapse
So did I.......not crazy about it either.
MikeMBau said:
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that.
Click to expand...
Click to collapse
Did you end up sending it in after all? I sent mine, they got it the next day, the repair status says closed, and hopefully it will ship back today, and be here tomorrow.
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.