Database Info

Issues Updating to Official ATT ICS (US)

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!

Xoom Wi-Fi OTA 4.0.4 not installing!

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.

"Failed to unlock your device, Please try again later"....ugh

OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.

its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.

Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.

EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?

turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.

OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably

ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)

Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.

Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.

I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.

EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.

mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!

Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now

OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?

still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?

turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).

bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.

Did you manage to get this working?

Question about installing OTA

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.

[Q] Error 402 with 4.1.2 Update?

Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.

buckoman said:
Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.
Click to expand...
Click to collapse
Maybe just root(; lol and flash clean Rom stock 4.1.2
Sent from my SCH-I535 using Tapatalk 4 Beta

I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?

buckoman said:
I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?
Click to expand...
Click to collapse
Not unless you can remove the update and try again. Verizon soft bricked you. Don't know if you can remove the update file from memory and try to download again without root. Get a file explorer and look for the file. Not sure of name as I have only taken one OTA over all the years and it worked. If want to Odin the full MB1 update image is on SamMobile. If Odin that don't have to worry about OTA and will have same thing.

prdog1 said:
Not unless you can remove the update and try again. Verizon soft bricked you.
Click to expand...
Click to collapse
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?

buckoman said:
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?
Click to expand...
Click to collapse
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe

prdog1 said:
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe
Click to expand...
Click to collapse
And just making sure, using Odin will completely wipe the phone, yes?