yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
In case you didn't notice you quoted venom and not me, which is why I didn't answer your question. Feel free to do whatever you want with the OTA. It's not my work.

But posting flashable zips without testing them yourself first is irresponsible. How do you know it works? How do you know the partitions didn't change? What happens if someone flashes the modem to DLK3? Get my point?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I'm not going to get into a debate with you, but I'll just point at the links in my signature as proof that I know what I'm talking about. I've been taking care of modem updates for a while now, and I've never had a user have flashing issues. If you're offering your device to test it on, I'll gladly accept the help, but all "creating" a modem ZIP requires is swapping out one .BIN with another inside the ZIP. It's completely trivial and I'm 100% confident that anything I post will not cause harm to devices.

Kinda like how I don't need to have a Ford to know that a Ford part from a Ford factory will fit in a Ford car. I'm just the guy putting it in a box.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevedrz:
Both of you clearly have a bunch of posts and are well respected. I would just say (and I'm sure you do) dstruct2k, to just mention that in your OP, that you dont have the phone.. But come on, I think we all know buyer beware when it comes to flashing! And if just one person bricks, you'll quickly see it in threads!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Just to reassure you (and anyone else reading) I went and read through the entire update script. It very simply MD5s your current modem to make sure you have the previous official AT&T modem, and then runs a patch against it to update you to the newest one. This also means that anyone running a different modem than expected will fail the assert and will not be able to install the OTA. No partitions are changed in any way by this update.

Running newer modems on older firmware has never been an issue in the past, and because I don't see any RIL-related changes on the Android side of the update (beyond the 4.1.2 changes) I expect that this modem will work fine on any AT&T device running any ROM. If this is not the case, users can simply flash an older modem from my repository. When a device is running an incompatible modem, it simply boots without modem access. The device is still fully functional on WiFi, so users aren't left with a brick, and they can just flash a working modem to fix it. (These are things that have been tested repeatedly.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
This conversation is not about knowledge, but ethics. Clearly we have different standards.

It is my fault this thread went OT, but let's end it right now.

Everyone (including myself) needs to stay on topic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrox00612:
Hi, a little note of what I do to update.

1. Using CWM recovery format system, data, cache and sdcard, also cache partition and dalvik cache.

2. Using Odin 3.07 flash DLK3 stock image.

3. Update from ext-sdcard using stock recovery to UMCG2 using update.zip from "upndwn4par" please thank him for a great job.

4. Download Samsung Galaxy S3 Toolkit 7.51, and in model selection proceed with TMobile SGH-T999, 4.1.2, just because TMobile and ATT use same insecure Kernel and custom Recovery Image, proceed to "All in One" root, custom recovery and busyboxed.

5. Wala, fresh new rooted installation of UMCG2 update.

Happy Flashing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ra4013:
I have the latest Clockwork. After downloading the update, it rebooted my phone into recovery. Clockwork opened and asked if I wanted to install the "untrusted zip". Don't know where the file was stored.

sent from my S3 Sammy Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tailgunner9:
Thanks got it back rooted and CWM going. Thanks again!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Well this definitely helped!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
Is this a typo or the wrong file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greysonofusa:
I'm updating on stock OTA right now. Should I root before I install or after? This is taking a long time with AT&T's servers. Might just do it this way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oldbbman:
If your questioning the size then that size is correct :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] booster944:
Worked great from stock... OP should state that it wipes data!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
No not the size. It says it's for Galaxy S4. Highlighted in yellow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oldbbman:
Haha

He has a S4 and develops for that phone as well. Likely a typo. :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
Step 4 Isn't happening for me

I'm on the ATT US network. I installed 4.1.2 fine then went to step 4 and it fails to load.

Is there a trick to it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DaLakersFan:
Just double checking before updating

Its my first time doing a bootloader update, so im kinda nervous.

just making sure if these are the steps i should follow:

Device: d2att (AT&T i747 Galaxy s3)

Currently running 4.1.1 (LK3) rooted with CWM Installed.

I Should Download the 4.1.2 zip ... and then install from sd card

then Download 4.3 zip and install from sd card..

Someone please tell me im good to go and that i wont brick my device if i do this. and if i would still have root access.

SEPERATE QUESTION: also is it ok to flash I747UCUEMJ2 booloader from a third party website. (I know downgrading boot loaders = brick)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hith1:
after doing PC103's method i'm currently running 4.3 with LK3 boot loader, MJB Baseband. How would I get to 4.4.2 from here???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
There are several threads dedicated to updating to 4.4.2. I suggest picking the one you are most comfortable with and follow the instructions exactly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] echelon64:
Well I have a galaxy S3 AT&T SGH-I747 on 4.1.1 and tried updating to 4.1.2 with using TWRP. Didn't work kept giving me something about unsighed hash or something or the other. I then tried using mobile odin and it flashed there but just got me a softbrick.

Should I use CWM instead?

Attempting to install the 4.1.2 zip just gives me a status 6 error in CWM. ;_;
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] playergab:
Question sir. Please. Badly needed. Thank you !

I want to upgrade my phone to android 4.3. I am not sure if im in the correct path. I already downloaded the files that you posted. I just want to know if I am in stock odin. My device specs is posted below. Thank you in advance ! Sorry just a newbie.

Model Number : SAMSUNG-SGH-I747

Android Version: 4.1.1

Baseband Version: I747UCUEMJB

Kernel Version:

3.0.31-294793

ziggy@tardis #011513

SMP PREEMPT Tue Jan 15 06:40:00 EST

Build Number: JRO03L.I747UCDLK3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
The file is correct. I put it in the wrong folder.

No trick. Check the MD5 and use the USB cable that came with the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
In the DL instructions what do you mean by check md5?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
MD5 is 60CCC961AB45B24351507B3AE9441BE4

Is the CF autoroot supposed to be the same #?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
Where do I check that number at?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
You have to use an MD5 checker. They're free just google one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
So the one I found is a md5.zip is that correct? Just flash it like I would a ROM correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
Hash Calculator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beaverslayer:
You can use ES file explorer from the play store to check the md5. Just select the file and look under properties.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhanamjay:
After re-root with 4.1.2, does carbon ROM back up can be restored?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
You don't need to check md5 numbers on a tar.md5 when you flash with Odin. It auto checks it for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
I can't get the thing rooted. I tried flashing loserskater's stock rom with root and then it just wiped all my data (still 4.1.2) and had to start over again.

The CF auto roots don't work for me. Every time I get a fail on Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
How do i update via stock recovery?

I copied it to my internal storage?

I don't have an SD-Card BTW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
I copied mine to my external so I couldn't tell you about internal. Smooth update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Help, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pre4speed:
[MENTION=5301683]Sajoeee[/MENTION] The stock recovery only has an option to install update.zip from external so you'd need an external sd for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Works great on SGH-I747. Odin'd back to stock, couldn't download the update OTA kept failing so I downloaded this and flashed in stock recovery, worked fine. Phone is back up running 4.1.2 stock w/ root not. Thanks very much :) :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
I was on 4..1.1 rooted and was able to use losekater's update.zip file. Put it on my external card, rebooted int TWR and ran the update. No problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
It has to be on the external. When I ran it, it formatted the entire data partition, which includes your internal sd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superman2112ms:
I see 2 basic threads discussing the 4.1.2 ota. Is there a complete flashable zip yet? One that includes modem and bootlaoder or just a multi part zip. I am confused
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Linked in the OP is the entire OTA. I got tired of waiting for my update notification so I came up with this alternate method.

___________

Sorry about the data getting wiped guys. I didn't know. I always do a factory reset before I Odin back to stock to prevent any problems.

I updated the OP yesterday to warn everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
No worries. I used adb to pull the entire internal before I started.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] negrowil:
My phone softbricked after doing that. I am trying to go back to stock and flash it again... Be careful!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tokuzumi:
Does this only occur if flashing the update.zip manually? If you receive the update via OTA, does it leave your data partition intact?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I believe it only occurs flashing the update,zip manually. Don't hold me to that. Usually, a message will come up to tell you if you need to back anything by doing an ota.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajsedlacek:
I was rooted with unlocked bootloader and was unable to install the downloaded OTA with CWM, TWRP and stock recovery. Kept receiving error messages.

I tried flashing with ODIN, no luck.

Tried to sideload with nexus 7 toolkit, error.

Wiped and flashed back to stock, downloaded OTA and receive an error message and on reboot it says the installation/update was interrupted.

I downloaded the .zip in the OP to my External SD Card, and receive the following error when trying to install from recovery error in /tmp/sideload/package.zip

Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
What do you mean by "flashed back to stock"?

Stock ROM zip or Odin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajsedlacek:
I Flashed the stock ROM via Odin and also did a wipe/reset through the stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajsedlacek:
The other message that comes up when trying to update through stock recovery is

assert failed: apply_patch_check("/system/app/Facelock.apk", :c0c83a8c5d02786abed70758022dce17e1fb3a6f", "1bel1a17f8063aba12220a38a38caa7b3382ec96bbeb")

E:Error in /tmp/sideload/package.zip

(Status 7)

Installation aborted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Ate trying to use the sideload option in recovery, or the apply update from external option?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajsedlacek:
Both and the same error comes up for both methods.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Anyone flashed this on a Rogers SGS3?

Never mind... apparently this is for AT&T i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danvee:
Sounds like the facelock.apk is either missing or changed, or the update is corrupted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] negrowil:
SOLVED!!!

Must flash a custom rom again. Thanks to mskip.

http://xdaforums.com/showpost.php?p=39300520&postcount=62

Wil
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajsedlacek:
If that is the case, does anyone have a download for the galaxy s3 face unlock apk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
It would be much easier to just dl the entire zip again. Why? Let's say you replace that apk with a good. Then other apk is bad. Fix it, then another. See where I'm goingwith this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danvee:
Should also try re downloading the update just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ra4013:
I have the latest Clockwork recovery 6 installed with Rom Manager. Worked fine and still no problems. After installing, CW returned to the reboot phone screen. After reboot AT&T updater said the update failed. Then the phone rebooted and got the Android is updating apps. Didn't know CM would install it, but did.

sent from my S3 Sammy Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :


---------- Post added at 12:21 AM ---------- Previous post was at 12:18 AM ----------

Mine just aborts the installation when i select "install untrusted.zip" :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ajsedlacek:
Finally on 4.1.2. I ended up loading 4.1.1 through Kies and was then able to load the update in the op from my ext sdcard. Rooted through Odin. All is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdl2mtl90:
I have tried many times to update without success. I am on stock rooted 4.1.1. I have tried to flash with stock recovery and TWRP. Both say 'Zip signature verification failed".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danvee:
Bad download? Did the md5 sum match?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Unroot, then run the update by the directions in the op.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdl2mtl90:
The last time I tried, it did say something about no md5 or something.

What is the best way to unroot and maybe try again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danvee:
That's because there was no MD5 file to compare with.

You need to manually compare it against the MD5 on the download site using an MD5 checker app or program.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
I used SuperSU to unroot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdl2mtl90:
Going thru TWRP it says there is no md5...downloaded Hash Droid but not real sure what to do. Might be over my head!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
i wanted to try latest cm10.1 nightly,I have read in the op tht 4.1.2 updates the bootloader, can i use Odin to go back to 4.1.1 using full rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
You can. But if you need to just downgrade the bootloader, look here

http://xdaforums.com/showthread.php?t=2321310
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
is it necessary to downgrade bootloader to flash 4.1.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdl2mtl90:
Ran it thru a program on my computer as well as an app on the phone. Get the same number both times but when I try to update, I get "no MD5 file found" and "Zip signature verification failed".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Does it match the MD5 supplied from Android File Host?

Are you using stock or a custom recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdl2mtl90:
Not sure how to do that!

TWRP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
There's the md5 from Android File Host. Compare that number to the one you generated with your computer. And you need to be on stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdl2mtl90:
Ahhh, thanks! Will try it again later!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
Any chance to get this without doing a full wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Not this version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lfaulkner29:
i followed the directions (or think i did) and i get E:Error in /tmp/sideload/package.zip (status 7)..... anyone have any idea why this is or how to fix it???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Are you still rooted before trying this? If so, unroot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lfaulkner29:
I FINALLY SCREWED UP MY PHONE..... hahaha. I knew the day would come. ok, so i was not un-rooted I guess. so again I think I un-rooted with odin and then tried to flash the update again. it went through the whole process and said the update was install correctly and then as it was doing a data and cache wipe it flashed two errors and went immediately into re-boot. it happened so quick that I couldn't see what the errors said. but anyways now I am softbricked. it's stuck at the "Samsung" boot screen. I can get into download and into stock recovery but I don't know what to do from there...... PLEASE HELP!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Dl and flash a stock Rom. Lg1 would be best, but it will wipe your internal sd (but you backed it up, right?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lfaulkner29:
thanks. that is what I was thinking too. all back to stock now. and yes I did back up before I started playing around :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stealthj:
wish there was a flashable zip to update stock rooted 4.1.1 to 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
Well I found the issue with Odin. I had Kies open at the same time and that was somehow interfering with Odin.

BUT, after running CF Root it now took my 4.1.2 update back to Stock 4.1.1

View attachment 2173345
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Might try this out just to see what its like, thanks for the link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcorchary:
4.1.2 OTA failing?

In my Galaxy S3 starting from 4.1.1 rooted, I have wiped the phone back to factory and I'm now trying to let the AT&T OTA install, but it keeps failing. Any insight as to where to start looking, or how to investigate what might be causing this? Thanks for any insight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
Looks like I need to explain a few things to some of you.

You have no idea how fortunate you are that the S3 is a VERY forgiving device with a factory unlocked bootloader. With most devices, OTAs are out of the question because updating an exploit unlocked bootloader will brick your device. With most devices, if you are not 100% stock the OTA will brick your device.

I am not sure why some of you are having trouble following the very simple instructions in the OP.

That does not mean stock rooted.

That does not mean stock with a custom recovery.

That does not mean anything other than 100% stock that can only be achieved by flashing stock firmware through Odin.

If you don't want to follow the instructions or prefer another method that is fine, just don't post about it on this thread.

I really hope that some of you change your very bad habit of "flash first, ask later, read never" before moving on to another device or you will find yourselves frequently seeking JTAG repair.

Get it?

Got it?

Good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
There is, as long as you have a recover bootloader installed, you can flash this update.zip on a rooted 4.1.1. I had no problems updating my stock rooted phone.

http://xdaforums.com/showthread.php?t=2388065
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hat Trick:
When I do follow the instructions and they don't work I come here for answers. Know what I mean Vern?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] upndwn4par:
That is exactly what the threads are for. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shep FC3:
One slight change to the instructions that I had to do coming from a custom rom

Boot into recovery

Format system and clear dalvik

Odin to stock

Boot into recovery again

Format system and clear dalvik

Update!

I had to do the second format and clear due to getting FC's on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knightblaze:
Thanks for providing this. Adb sideloaded without issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Voicebox:
Just a quick note. First, thanks for this method.

Second, this method did not wipe my data. I just used Odin to go back to stock 4.1.1 without wiping cache or anything, then updated to this without wiping anything. All my apps and data carried over both times and I have had no problems in about a week of running this.

Note however that I was using rooted, stock 4.1.1 before so I think all that happened was it re-installed 4.1.1 including putting stock recovery back on, then the OTA update is designed not to wipe. Otherwise users just doing it OTA would be flooding AT&T customer service complaining about the loss of their data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
If you used this method, it should have wiped data and internal sd. It formats the entire /data partition, which includes /data/media (the storage location for sdcard0, aka your internal sd). It did in mine, all 3 times I used it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
It wiped my wife's S3 also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Voicebox:
Well, /data is a new folder with some new folders and some old folders inside. /data/media has a date of Aug. 1, but the folders inside are of various dates from this year and last and the files seem to all be there.

My sdcard0 is at /storage/sdcard0.

At any rate, there are some generic steps in this process, so here's what I did. I think Odin to stock is where the data would be wiped, and again, I started from rooted stock 4.1.1 with TWRP recovery, so it wasn't much of a change.

I used the DLK3 stock rom from here:

http://xdaforums.com/showthread.php?p=33570269#post33570269

Used Odin 3.07, which I had from before, to install the stock file. Everything was still there when it rebooted, including a SU icon in app drawer which didn't work. But all my data, the screen background, icons, same unlock pattern, and even face unlock worked. Recovery had gone back to stock recovery.

Then I installed the update to 4.1.2 using recovery and again, everything stayed. I then rooted and did triangle away, reinstalled TWRP, and that's it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
While I don't doubt,I am confused. You are,I believe, the first person to claim that their data wasn't wiped with this update.