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.
Related
.... or maybe download link from google?
Hello all,
Wondering if someone could try this since I already upgraded won't work but when i got the update on my phone I was able to go to the cache folder and extract from fumo file the following zip that is on mediafire.
Called OTApkg.zip like the mt3g update file.
Should be the current update.
Anyone on the original firmware should be able to flash this from recovery and be up and running with new firmware
Let us know if it worked.
Just rename update.zip and put to root of memory card
boot with vol down and power.
down and select recover
vol up and power to get options
select update from update.zip and should run.
Download:
http://www.mediafire.com/?jm90w7hr922bpd4
You didn't get a chance to test this at all? Can anyone test this and tell me if it works. Before even thinking about rooting I always like to have a set of file to recover with. G1, original mytouch, and slide i all have had way to undo before I rooted.
Didn't work for me. When I tried it I got an error that said
Code:
-- Invalid operation --
On a side note, when I reboot into recovery I get this
Code:
E:Can't open /cache/recovery/command
Anyone else? Is this correct?
Reviewing the code does look like the right file but may not be able to be flashed manually.
First line in update script is mount ( "MTD" , "system" , "/system" )
Looks like boots is a special "fota" mode that will allow modification and this update run like that won't initialize it.
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
travisjames said:
I tried to flash it also. I also got the same "Invalid Operation."
I pushed it to /cache/ as OTApkg.zip and ran *#*#CHECKIN#*#* and still nothing at all.
Great. I have no idea what I'm going to do. Ever since I wrote my downgrade tutorial to downgrade from the OTA to Stock, I figured I would have gotten the OTA notifications again, but nope. Never received anything and it seems I can't use this.
This is a problem.
Click to expand...
Click to collapse
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Beast84 said:
Very big problem! By chance, when you boot into recovery, do you see the same line as I have above?
Click to expand...
Click to collapse
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
travisjames said:
Yes, I also saw the same thing when I booted into recovery on my G2(before I returned it), so that line is not a problem.
Click to expand...
Click to collapse
Great that means theres no problem with my phone. I feel so much better now
Beast84 said:
Great that means theres no problem with my phone. I feel so much better now
Click to expand...
Click to collapse
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
travisjames said:
Yep, but we still have a problem with not being able to update to the OTA and perm-root.
Click to expand...
Click to collapse
Very true. In the Vibrant section, those guys were able to make update.zip's that were flashable through the stock recovery. Maybe someone can do that for us with this update. I have no dev experience at all but I am willing to test whatever comes up.
It was weird because when I looked at it
It was in the cache directory but not directly
in the cache directory was a file fumo which on browsing just looked like a file on the phone using sufbs.
But when I copied it to the device using the app that is when fumo turned into a folder and opened and saw that file.
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
bobsbbq said:
I wonder if there is anyway T-Mobile can push the OTA to you?
The rep I talked to told me there were 2 updates. I would be happy to see one. She said once I made a call I should get the OTA update notice. That hasn't happened.
Click to expand...
Click to collapse
No, there isn't a way for T-Mo to push the OTA to you.
Did the rep say anything about the other update?
If you bought the phone full price instead of on contract be sure to check online and change the phone Tmobile has for you to a Mytouch 4g I think that could have something to do with it. I had mine listed as a Mytouch 3G still and I went and changed it and hope it'll make a difference.
Pretty sure that just changing the phone on my tmo wont change. Only thing that i can think of minus something being changed since i got it off the device vs a direct download if someone can get the link or call tmo to check on thier plans if past thier time frame they may be able to do something
Just hopefully someone could get the google link for it instead.
Sent from my HTC Vision using XDA App
I called T-Mobile today about the OTA and they said that it did matter that my plan wasn't set a mytouch package. They told me the OTA should have gone out after my first phone call. Sounds like a bunch of bull**** to me, just figured I'd fill in anyone who was interested. They told me I should have it within 48 hours. *crosses fingers*
*edit* my friend works at T-mobile, she just received the phone herself and after your phone is set as a Mytouch4G, use *#*#checkin#*#* should help start the process, now were both waiting...
I've been waiting since Sunday. Hopefully has nothing to do with having debugging enabled.
Been leaving the phone connected most of the time running
Code:
adb logcat | findstr clients.google
to try and snag the link for the update.
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
johnowa636 said:
downloaded "aLogcat" from market. it allows a log filter, any one know what i can place in filter so it does not catch entire logs of phone activity. Thanks.
Click to expand...
Click to collapse
I've been messing with this. It seems you can put in a filter (I put clients.google) but it doesn't matter if you set it to save to your card periodically it saves the entire logs... but you can open those on a pc later and search them or if you're a linux type you can cat file | grep "clients.google"
Hello, today I've noticed that my phone (Samsung Galaxy S2 Skyrocket) had received the updated ATT ICS (US). It downloaded successfully without any issues. At the current point, my phone is rooted with the stock ATT Gingerbread OS, with clockwork touch 5.8.1.3-hercules.tar. I never bothered to install any 3rd party unofficial ROMS because I was waiting for the official ATT ICS which apparently released today. Anyway once the download completed, my phone restarted normally and went automatically in to CWM which was expected. From there, I chose "install from zip", apply /sdcard/update.zip. Right after that I get an error message "Can't mount /sdcard/update.zip", so I click "Go Back", I then select "Mounts and storage" > mount /sdcard, and get "Error mounting /sdcard!".
I've tried doing this also with a prior version of CWM (prior to 5.8.1.3), but I've got the same issue. I've also tried to plugin my phone to my PC and looking for the update.zip, so I can manually transfer it to the root of the phone's file system, but it was not there although it downloaded. I do not have any additional external SDCARD installed.
Could I possibly get the update.zip from an official ATT hyperlink for my phone so I can manually download it on my PC and transfer it to the phone's root file system?
Is there a Fix for "Can't mount / sdcard"? I looked around but could not find an answer.
Please advise.
wait...what? release today?!?
Are you sure it's ICS and not UCLA3 yet again??
Also, I'm pretty sure you need to be on stock recovery in order for the update to work.
jarus323 said:
Hello, today I've noticed that my phone (Samsung Galaxy S2 Skyrocket) had received the updated ATT ICS (US). It downloaded successfully without any issues. At the current point, my phone is rooted with the stock ATT Gingerbread OS, with clockwork touch 5.8.1.3-hercules.tar. I never bothered to install any 3rd party unofficial ROMS because I was waiting for the official ATT ICS which apparently released today. Anyway once the download completed, my phone restarted normally and went automatically in to CWM which was expected. From there, I chose "install from zip", apply /sdcard/update.zip. Right after that I get an error message "Can't mount /sdcard/update.zip", so I click "Go Back", I then select "Mounts and storage" > mount /sdcard, and get "Error mounting /sdcard!".
I've tried doing this also with a prior version of CWM (prior to 5.8.1.3), but I've got the same issue. I've also tried to plugin my phone to my PC and looking for the update.zip, so I can manually transfer it to the root of the phone's file system, but it was not there although it downloaded. I do not have any additional external SDCARD installed.
Could I possibly get the update.zip from an official ATT hyperlink for my phone so I can manually download it on my PC and transfer it to the phone's root file system?
Is there a Fix for "Can't mount / sdcard"? I looked around but could not find an answer.
Please advise.
Click to expand...
Click to collapse
O.K., your join date is May 2012, you only have 1 post and I'm to believe you have a rooted device, ready to upgrade to ICS, yet what really sticks out is that this is the only time you've posted.
Well, the file that downloaded file was way over 200megs, probably 250-280 and right after, the the download, my phone restarted going to CWM. I may just backup my data and restore everything to factory so see the update complete. Not sure if anyone had the download available. Not sure if the location matters, I'm located in South Florida.
Thanks for the prompt reply's btw.
Yea regardless, as skrambled said, nothing is going to work unless you're on the stock recovery. Think about it, its an official update and cwm is a custom (unofficial) recovery.
Sent from my SAMSUNG-SGH-I727 using XDA
I got a prompt for an update was well today, it took a while to download and same thing happened, it went to CW on restart, I am also just rooted, no custom rom installed.
upload the update.zip and post here? i'm sure someone can verify the build it is and would be good info to have.
I'm doubting soooo much right now. When a reliable source confirms, or u post a screen shot with a different build number, then ill believe
just checked....
i have no update on my skyrocket...Boston mass area....
dlpatter said:
O.K., your join date is May 2012, you only have 1 post and I'm to believe you have a rooted device, ready to upgrade to ICS, yet what really sticks out is that this is the only time you've posted.
Click to expand...
Click to collapse
I decided to join because of the issue I'm having. Most of the time I read what others had to say on this forum and others.. I'm not too big on phone "tweaking" etc..., but I would surly like to get this update to work which is why I have joined. There are plenty of threads and other sites that offer step by step instructions of how to root a phone etc...So I would not be surprised if a member of one post has a rooted phone. Just Google "Root ATT Skyrocket".
my brothers completely stock skyrocket (no root, no nothing) received a notification of an update today.. it was just 2.3.6
Decer said:
my brothers completely stock skyrocket (no root, no nothing) received a notification of an update today.. it was just 2.3.6
Click to expand...
Click to collapse
That would make sense.
Decer said:
my brothers completely stock skyrocket (no root, no nothing) received a notification of an update today.. it was just 2.3.6
Click to expand...
Click to collapse
Was it between 250-280megs?
If it was, maybe it'll be good to delete this entire posting to not cause too much confusion.
jarus323 said:
I decided to join because of the issue I'm having. Most of the time I read what others had to say on this forum and others.. I'm not too big on phone "tweaking" etc..., but I would surly like to get this update to work which is why I have joined. There are plenty of threads and other sites that offer step by step instructions of how to root a phone etc...So I would not be surprised if a member of one post has a rooted phone. Just Google "Root ATT Skyrocket".
Click to expand...
Click to collapse
2.3.6 verified, My most humble apologies to you sir....
---------- Post added at 01:20 PM ---------- Previous post was at 01:16 PM ----------
jarus323 said:
I decided to join because of the issue I'm having. Most of the time I read what others had to say on this forum and others.. I'm not too big on phone "tweaking" etc..., but I would surly like to get this update to work which is why I have joined. There are plenty of threads and other sites that offer step by step instructions of how to root a phone etc...So I would not be surprised if a member of one post has a rooted phone. Just Google "Root ATT Skyrocket".
Click to expand...
Click to collapse
There have been so many false sightings and ICS treads started that it makes one leery of any mention of a OTA update. I want it sooooooooooo bad, because I know that once it's released, the devs will take it and pimp it out for me.....
dlpatter said:
2.3.6 verified, My most humble apologies to you sir....
---------- Post added at 01:20 PM ---------- Previous post was at 01:16 PM ----------
There have been so many false sightings and ICS treads started that it makes one leery of any mention of a OTA update. I want it sooooooooooo bad, because I know that once it's released, the devs will take it and pimp it out for me.....
Click to expand...
Click to collapse
Same here man.
dlpatter said:
O.K., your join date is May 2012, you only have 1 post and I'm to believe you have a rooted device, ready to upgrade to ICS, yet what really sticks out is that this is the only time you've posted.
Click to expand...
Click to collapse
what does any of that have to do with him receiving the update notice? and I got one too.
jarus323 said:
Was it between 250-280megs?
If it was, maybe it'll be good to delete this entire posting to not cause too much confusion.
Click to expand...
Click to collapse
Was at 98% completed installation before i saw it, so my brother is probably the only person who could answer that question.. and i highly doubt he even cared enough to look.
InSaiyanone said:
what does any of that have to do with him receiving the update notice? and I got one too.
Click to expand...
Click to collapse
I did apologize for my rushed opinion, I now apologize to you my friend....
Originally, I got hyped up about this update because I knew that around this time, we all should be expecting the official ATT ICS, and since my friend T has a huuuuuuge hard-on for Android phones, he was sure that the updated that downloaded on my phone was ICS, so I blame HIM for giving me a false positive! If you are reading this T, it's ALL YOUR FAULT! See how many people had to click on this pointless thread!
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
darkuni said:
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
Click to expand...
Click to collapse
im in the same boat as you i would also like help
joeyman08 said:
im in the same boat as you i would also like help
Click to expand...
Click to collapse
I am also in the same boat as I have an unlocked bootloader and will no longer receive OTA's from ASUS. We just have to be patient for another day or 2 and ASUS will post the JB Firmware on their site here:
http://support.asus.com/download.as...er Pad TF300T&os=32&hashedid=8BmzkQ4yoz5WzBrW
---------- Post added at 10:17 AM ---------- Previous post was at 10:11 AM ----------
But who wants to be patient. THere is always the option of updating manually. Thank krabappel2548 for this one!
http://forum.xda-developers.com/showthread.php?t=1845377
I will give the manual update a go. Thanks!
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
darkuni said:
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
Click to expand...
Click to collapse
Don't do all that crap. Do this. I did. Others as well.
Reference: http://forum.xda-developers.com/showthread.php?t=1840540
1) Found the correct OTA file. Someone posted it here for my US MODEL. If your WW or JP or something else, you'll need a different file.
http://forum.xda-developers.com/show...840397&page=11
2) I downloaded that file, named it dlpkgfile and put it in /cache/ (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
3) I created a file called 'command' and put it in /cache/recovery with the contents of that file being as follows(without quotes): "--update_package=/cache/dlpkgfile". (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
4) Now just run the update. To do this, make sure you do all your prep work (Voodoo OTA root keeper, supersu binary installed and run at least once, all original system apps in place. yada yada yada. To run the update shut down your tf300. and then start it holding the POWER and VOLUME DOWN. Keep holding it until you see writing appear. when the writing appears release and press VOLUME UP within 5 seconds of those words appearing.
5) you'll see the normal asus upgrade spin up.... and either complete or fail. If it fails, check your log file in /cache/recovery and see WHY it failed. Fix why it failed, and restart from step 1.
We have a winner! I had the command and dlpkg file ... what I didn't have was the boot process to enact it.
WONDERFUL! I'm safe for one more update
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Hi. I don't suppose the end result would be different, whatever method you choose.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
AFAICT this seems true, you I could run a leak#2/soak based ROM as a second system (first system too?) with boot menu manager by following the guides:
http://forum.xda-developers.com/showthread.php?t=1779968
http://forum.xda-developers.com/showthread.php?t=1882335
jboxer said:
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
Click to expand...
Click to collapse
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
jboxer said:
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
Click to expand...
Click to collapse
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Also I do not think you can be rooted to update the check will prevent you from updating, also you have to be as close as stock as you can..... Meaning all bloat must be unfroze.....
One more note there is a Q&A section now so try to post questions there.....
jboxer said:
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Click to expand...
Click to collapse
Can you share the link of the update file?
Thanks
jboxer said:
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Click to expand...
Click to collapse
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
You can be rooted. The update asserts only check for the original system files to make sure they have not been modified or deleted. It does not check for extra files like superuser.apk or busybox. Rooting is not a problem. I set superuser to OTA protect and it worked. After the update my ICS was still rooted without me having to root it.
For the person that wants the leak the OTA is leak # 2. It is exactly the same. Just find thread with download link for leak # 2 and you are good to go.
Would installing beats audio drivers using the app be considered tampering with system files? And would it prevent me from receiving a ota?
Sent from my MB865 using xda premium
athani said:
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
Click to expand...
Click to collapse
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
ramosquera said:
Can you share the link of the update file?
Thanks
Click to expand...
Click to collapse
The devs have confirmed that the soak test OTA is identical to ICS leak #2.
jboxer said:
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
Click to expand...
Click to collapse
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
You have to be someone that was invited and filled out a survey about six weeks ago. If you are you need to go to the Motorola Private forum. Go see how others are requesting it (not allowed to really talk about it). FDR means Factory Data Reset and it is an option in Privacy in Settings. It erases all your user settings, app data and you are back to square one like when the phone came out of the box. For many people it was required to get what they wanted.
If you were not invited don't worry. Usually the official rollout of the OTA will come within a week of a soak test if no problems are found. It is the same as leak # 2 so just look on this forum and you can install that manually. The release is solid so I see no reason the OTA won't be going live to all AT&T Atrix 2 devices very soon.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
alteredlikeness said:
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
Click to expand...
Click to collapse
I hated doing it but it was necessary for some reason. Before it my phone was invisible to the update servers. After it was and I got a push notification to begin the download. Loving ICS.
About the time JB was released I checked for an update not realising that it would go ahead without confirmation. As I didn't want to update just then I cancelled the download by clearing data in CM & DMclient (seemed to be the only way after turning wifi off).
Recently I just rooted (locked) using the debugfs method, after which checking for updates comes back with a zilch.
I tried clearing DM/CMclient data again and removing the update files :
fw_update_progress & isp_fw_progress
These had java errors in them presumably because I had aborted. After trying again they hold "0" and "100" in text format.
Finally on someone's recommendation I did a full factory reset (which worked for him) but I'm still without OTAs.
I'm hoping someone can shed some light on what may be the problem. AFAIK just rooting doesn't kill OTAs yet something has. Does Asus perhaps keep a database record as to what has been downloaded? I somehow doubt it but with a full factory reset I fail to see what's stopping these updates.
Any help , suggestions appreciated.
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
junrider said:
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
Click to expand...
Click to collapse
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
louiscar said:
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
Click to expand...
Click to collapse
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
buhohitr said:
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
Click to expand...
Click to collapse
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
louiscar said:
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
Click to expand...
Click to collapse
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
buhohitr said:
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
Click to expand...
Click to collapse
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
louiscar said:
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
Click to expand...
Click to collapse
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
buhohitr said:
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
Click to expand...
Click to collapse
Ok I will report here if I get anywhere with them. I somehow suspect that their support may not even realise or understand the issue but I will persist and see if I can get some kind of acknowledgment about their servers.
Well my OTA resumed after updating to JB so I think that it's as you state, the datebase on their servers. I don't know what the update was but your post in another thread would probably confirm this was JB .18. I guess once they have pushed an OTA, regardless of whether it was successful or not they don't seem to do it again. Which means I need to collect the dlpkgfile for each JB update given that I need to go back to ICS to do a proper factory reset and retain root.