.... 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"
Related
Can&How to force SNS check for OTA 2.3.2 update.
Thankyou
You can't. You either get the .zip posted on the thread in General and update manually or you wait.
You can go into settings, about phone, firmware update.
Sent from my Nexus S
kenvan19 said:
You can go into settings, about phone, firmware update.
Sent from my Nexus S
Click to expand...
Click to collapse
that doesnt really force the update, that just installs it if the phone was already presented with the OTA
slowz3r said:
that doesnt really force the update, that just installs it if the phone was already presented with the OTA
Click to expand...
Click to collapse
I thought it forced a check for the update, or at least it did on my Epic.
kenvan19 said:
I thought it forced a check for the update, or at least it did on my Epic.
Click to expand...
Click to collapse
nope, the closest thing you can get to "forcing the phone to get the update" is the
*#*#CHECKIN#*#* method. and even then all the CHECKIN command does is gets the phone to call home to the mothership and say "hi im here"
kenvan19 said:
I thought it forced a check for the update, or at least it did on my Epic.
Click to expand...
Click to collapse
Hard to say. Maybe the difference with your Epic is that the update comes from Samsung and on the Nexus S it comes from Google.
With the NS on both updates so far, I was not able to magically make it appear on my device by using the Settings or the checkin dial code. I think that for those it showed up after checkin, it was just coincidence...
distortedloop said:
Hard to say. Maybe the difference with your Epic is that the update comes from Samsung and on the Nexus S it comes from Google.
With the NS on both updates so far, I was not able to magically make it appear on my device by using the Settings or the checkin dial code. I think that for those it showed up after checkin, it was just coincidence...
Click to expand...
Click to collapse
Perhaps it is the difference in where the update is coming from, I've been running 2.3.1 with CM7rc8 for a few days now don't really plan to update
The way to force the NS to get the update is to download the zip and go into recovery and update it. No root, changing recovery to apply.
1) Download it (Search forums for it.. its in General)
2) Rename to update.zip if it isnt already
3) Put it on root of sd card
4) Boot into recovery (search forums, if you dont know how)
5) Apply update.zip
6) Reboot... you're on 2.3.2
NOTE: The file you are downloading is exactly identical to what you would get from the OTA. So you're doing the same thing. When you get the OTA, you're downloading it from the same source. The URL was received from aLogCat.
I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.
You can get the update in the "Just got an OTA update" thread.
Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk
...................
martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...
for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.
TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk
Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...
Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.
None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116
Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.
Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.
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.
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.
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
beelow319 said:
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
Click to expand...
Click to collapse
Can you offer up the steps to do that? I know how to do a factory reset, but that will wipe the data. Thanks.
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
newtoncd said:
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Click to expand...
Click to collapse
Are you, or have you been rooted in the past?
rmjones2006 said:
Are you, or have you been rooted in the past?
Click to expand...
Click to collapse
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
beelow319 said:
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
Click to expand...
Click to collapse
May I just say, thank you very much.
That worked ... I am now running v4.4.4 .... and you are right, that was very easy.
Too bad I had already wiped my phone twice ... ugh ... again, thank you!
newtoncd said:
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
Click to expand...
Click to collapse
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
distortedloop said:
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
Click to expand...
Click to collapse
I had replaced the radios with stock before trying to update to v4.4.4 .... when that didn't work, I thought the reset to factory specs would take care of that; no joy.
In the end, I love the HouseofMoto program .... that was really easy.