yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4-2ndtwin:
Really ? :confused:

Look 1 post up from urs. :thumbup:

Not sure how ya missed that post. And even quoted ya in it. :what:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
Doesn't work without root just tried and I didn't miss the post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 94loranger:
Mine did the same thing. Just go to settings> Date and time and uncheck the Automatic date and time. Now set your time a full day or 2 ahead.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 4-2ndtwin:
Cool. No prob.

And yep as Ethere previously posted...if ya want to do it, ya gotta have Root. I was just postin the method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
I did the date and time thing it says update interrupted server will check again in the next 48 hours. Idk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ethere:
That just means that your phone didn't get the update yet. You used to be able to clear cache and data on the AT&T Software Update app, but they've restricted it. You can't do that anymore without root access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChesterJT:
I had the same issue and finally gave up on OTA in frustration. Assuming you can get a hold of a micro sd, use the link earlier in the thread and just install the update from the card. It worked perfectly, and fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tokuzumi:
Do I need to have an active AT&T sim in order to receive the update? I bought an SGH-I747 off of swappa, and it's currently only hooked up via wifi. I saw a response regarding someone who was in another country, on another carrier, but nothing about a non-activated phone, hooked up via wifi only.

I can always just go to this thread;

http://xdaforums.com/showthread.php?t=2387423

and flash the update if I need to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
The OTA update is 229M and is taking forever to download. 43% after 45 minutes on wifi. Maybe it will work but at this rate I bet it will die before it finishes. I find it interesting that Kies does not also have the update...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Can I get someone that's installed the OTA, has root, and is running the latest modem ("Baseband version: I747UCDMG2") to send me a PM? I can't get a good copy of the modem file through the ZIPs that have been posted so far and I'd appreciate if someone could help. (It's very simple and 100% risk free)

EDIT: No more PMs please! Got what I need. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
Still downloading...at 80%!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElKompaAndres:
Edit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
Download completed...UPDATE FAILED. No reason given but it might be because I am rooted. At 229M the package must be pretty complete so root should not matter unless the installer explicitly checks it....I am going to unroot and try again in 21 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
So I'm getting a failed update and don't quite understand why.

I've rooted via: http://xdaforums.com/showthread.php?t=1739426; however, I stopped after the second step, so I didn't install a custom recovery.

I rooted mainly for TiBu. I'm using OTA Rootkeeper to temporarily unroot and preserve root. That said, I get about 25-32% in the flash and then it fails.

From everything I've read, I should be good to go, unless I've missed something. Any thoughts?

GB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The update MD5s your modem, bootloader, and /system files to make sure they're still the AT&T official ones. For the most part, this update doesn't contain "complete" files, just patches for files that already exist. (Patches are like a diff file.) If any of those MD5 checks fail, the update will not install. This means if you've changed your modem, bootloader, or one of the /system files that are checked, you'll fail to update. Oddly enough, "su" is not on the list of checked files, so you shouldn't even lose root if you have it. If you've made use of your root powers to change anything in /system, it'll probably fail though.

Once someone's created and posted a non-patch version (it'll be over 1GB) from their working system, you'll be able to update with that.

DO NOT EDIT THE UPDATER TO REMOVE THESE MD5 CHECKS!!

The update will either still fail to install (just a bit later in the script) or will totally mess up everything it touches. The MD5 checks are there for a reason!

Also, I don't need any more PMs, thanks for the quick replies guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Ah okay, so the altered hosts file would cause that.

And as for why it doesn't check for su, it probably runs a MD5Sum check on the known files. Since su isn't part of the default install list, they can't check for it.

I've truncated my hosts file and started again. If that doesn't work, I'll have to figure out what the original system looks like. I really don't feel like wiping my phone.

GB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Good luck! If you're curious, you can open the OTA ZIP file and read the list of checked files in /META-INF/com/google/android/updater-script (open it in Notepad++ or Wordpad, Notepad doesn't like Unix line endings) but like I said before, don't modify this script unless you're willing to have a broken device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
care to share the new modem .zip ? Or post it in the modem thread: http://xdaforums.com/showthread.php?t=1831898
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Thanks for the link to my own thread, I'll post it when it's ready. ;) It takes time for uploads and downloads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Already there, I don't see the hosts file. I do see the progress which will give me an idea on which item is causing my problem.

I don't know, I might have not updated one of the Samsung apps off of Play and maybe that's causing the mismatch.

I guess I'll see soon enough.

GB

EDIT:

FYI - they are sha-1 hashes, via sha1sum, not md5sums.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Updates to /system apps don't actually get installed to /system/app, they reside in /data/app and the original is left in /system. (That's why you can always "Uninstall Updates" and restore the factory version of system apps) When Android sees the same package in both folders, it uses the one with the highest version number. Missing app updates shouldn't stop the OTA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
Didn't see it was your thread until after I posted...my fault. But thank you anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Okay, so I ran sha1sum in check mode, all the checksums matched with the exception of the emmc ones (which I don't know how to verify yet).

That's not good.

Additionally the update.zip I got from another thread here doesn't seem to have the same messages, which is odd. AT&T may be blocking those messages via their own UI, I'm not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
In recovery, backup everything, then Odin to stock (but remove the recovery from your Odin image first) and install the ota. After, restore just /data from your recovery backup. You'll have to re-root, but that's easy with a custom recovery already installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Um you might have missed it, I'm not using a custom recovery.

I found the install log. The log is in /cache/recovery/last_log if anyone is interested.

The mismatch appears to be in the boot image. That's very weird, as I shouldn't have modified the boot image while rooting.

GB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Have you ever updated your bootloader? This OTA expects you to have DLK3. You can install the update from my sig, use the Odin one if you want the modem to be as-expected as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
I should have DLK3, and I don't believe I've ever updated the bootloader. In fact it is my belief that my bootloader is still locked.

Edit:

I'll have to continue this tomorrow.

Also I don't think I made it clear, the boot.img is incorrect, not the bootloader portion. (NON-HLOS.bin is verifying for me, so I have the correct bootloader.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
NON-HLOS.bin is the modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Thanks for the clarification. I found the issue, when I rooted (LG1, before the 4.1.1 update) the boot.img was not stock. I upgraded to 4.1.1 OTA without an issue. As a result, the boot.img I have now is not stock. Which means I get the play the game of back everything up, and reflash.

I may even need to do a full scorched earth wipe and start over. Fun times. I've never tried just flashing the boot.img, I'm not sure that'll have a happy ending. Any advice would be greatly appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
The boot.img is your kernel. Go ahead and replace just that, leave the rest of your system untouched. Wipe cache after flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
I've never done that through Odin (or if I did I've forgotten in the last year) are there any instructions? (I'd RTFM, but Odin doesn't have a manual.)

GB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
I was hoping you knew lol, I don't have the files on hand to put together anything for you. Try making a copy of the .tar.md5 file, renaming it to just .tar, and removing everything but the boot.img from it and flashing that new tar through Odin. (Don't rename it back to .tar.md5)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
My update is still failing but I can't find this log file. I am rooted and using Astro to view files. I have the cache folder but it is empty. The OTA update starts, works for awhile then fails. I did have a non-stock boot image but I have replaced that with stock already. I need to see the log to find the point of failure...what am I doing wrong? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
I certainly have the files, but given this isn't something I normally do I'm concerned that I don't understand the ramifications. For example when swapping kernels is a full wipe needed? What should be backed up in case of failure? Oh and which box should I load the kernel in? PDA?

GB

---------- Post added at 08:13 AM ---------- Previous post was at 08:11 AM ----------

Install terminal emulator and then run:

cat /cache/recovery/last_log

It should be in that log file. I don't think you need root rights to see it. EDIT: You do need root rights.

GB

EDIT:

Sorry just read the fact that you can't see anything using Astro. Try Terminal Emulator anyways, but it might not work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Everything you flash in Odin is through the PDA slot. When switching kernels, you should wipe cache/dalvik, but a full wipe isn't needed. If you'd like to do a backup first, you can use ADB or Terminal Emulator to run dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.bin. Then you can restore it by reversing the input file and output file parameters.

When you say "stock", you mean DLK3, right? That's the only version this patch is valid against.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
Thanks GB. I realized that Astro was not getting root like I thought but ES File Explorer does so I am using that now to see the file. I do not have terminal editor so I may look into getting it to make these tasks easier... Doing this with a file explorer on the phone requires root to see the file and more importantly, the app has to get root permission...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Yeah, I just found that out and edited my post appropriately. What's going wrong? You should see something that says failed assert.

---------- Post added at 08:54 AM ---------- Previous post was at 08:27 AM ----------

So would dd work on the img file directly? Or would I have a problem if the rest of the space isn't cleared out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
You could just DD the img file directly on the device if you wanted. dd if=/path/to/new.bin of=/dev/block/mmcblk0p7

Do a backup first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Of course.

It didn't blow up, so I guess that's good. I'm downloading the update yet again, so we'll see if this time it'll take.

Edit:

So that appears to have fixed things. The update didn't stop. \o/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
Yes...DLK3.

Now that I have been able to look at the log file it appears the install died when it went looking for books.apk and could not find it. I did fairly aggressive debloating and removed lots of apps that I did not want including Books, Music etc...

I am wondering if it is worth it to reload Books only to have the update install on the next missing program or if possibly Books is the only one it looks for....

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rkant18:
I installed the update and then re rooted and from what I see so far I am enjoying the update a lot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
If you open up the update.zip, the list of what is checked for is in the updater-script under meta-inf/com/google/android/ I think. Remember, it's looking for things in /system/app, and reinstalling something from the Play Store will not put it in /system. You'll need to have the exact same versions in /system that were there from AT&T or it'll still fail on the hash check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
In the future, for debloating, use TiBu's freeze. You can defrost when another update comes along. Otherwise you're probably stuck wiping and flashing stock if you want this update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Yep. I thought about this when I had originally rooted the stock ROM and this update confirmed it. I had a debloated phone as well. But figured WTH. I have learned from past experience the extra 15 minutes or so is not a big deal to revert. I prefer to have a phone that is clean without all the BS...especially apps that are fully available on the Play Store. I figure if I want them later I will just install them.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Silenthunder:
I'm stock (DLK3) 4.1.1 and rooted using Samsung galaxy s3 toolkit. I want to update and I know I have to unroot to do so. How do I reroot after updating to 4.1.2 being that I used the Samsung toolkit? I'm still a noob.. All I did was follow what the screen said and I have no idea how to root outside that program.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scottmcm:
Indeed. I used TiBu to remove, not freeze, because I had no intention of ever wanting those programs again. Little did I think that a future update would require them. I have tried restoring them from the TiBu backup but that version was older so it is still failing even after I updated it through Play. Oh well, I guess it is back to stock then update then root then reinstall! My GPS has been a little flakey lately anyway so maybe a god cleanup will help it. :fingers-crossed:

Thanks again for all the tips!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Frrrrrrunkis:
Seems I am getting an ota update from att as I type. 229 mb. Could this the vaunted 4.2 update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danvee:
Nope. It's the semi vaunted 4.1.2 update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Frrrrrrunkis:
So I've noticed. Lol.

Will this update affect foxfi in anyway?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
Continues to work just fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Frrrrrrunkis:
Cool beans. I would hate to give more money to att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Decided to give the new update a whirl. Love the extra features such as multiview. It definitely adds that little something extra. However, AT&T has managed to fubar the toggle bar yet again. I have not found anywhere that lets me edit the toggles so I am assuming once again it is disabled and we are without the data toggle again. I guess the only way around it is toggle mod or a widget on the screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vanisleryan:
HD Widgets has some great toggle widgets.....that's what I use for my data toggle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
How about the tab on the side. Can someone tell me how to disable this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
You just hold the back button and it should go away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
+1. If you want Multiview disabled you can swipe down for the notification toggles and it will the second from the last.

---------- Post added at 11:42 PM ---------- Previous post was at 11:37 PM ----------

I have HD Widgets. However I like having the data toggle in the notification area because it is easier to access that when working in apps. I tend to turn data on selectively at work due to policies in place regarding personal electronic devices. Besides that, I get a very poor signal while in the building I work at and the syncing of certain apps helps drain the battery faster. When I do want data on I am typically already working with an app so exiting just tot turn data on/off is a pain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheStrokerace:
I found the new update useless. Nothing good or important in it. I had to use a debloater to get rid of all the new crap that they installed. Now I am thinking of getting rid of this phone after 8 months as its not good for much. I think its time to try a windows phone before I go back to a blackberry again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hoke88:
I applied I747_UCDMG2_Firmware_Modem.zip update to detmobilized rom and camera stops working. The issue was I had was kinetic pulse kernel. When I applied default kernel camera works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathdread:
I also lost my "blocking mode" toggle, and any way to change the order of the toggles up there.

Wonder how long it will be before a new toggle mod comes along?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tecknowboi:
Update 4.1.2

Ok... Noob here.. I have a at&t S3 rooted. I am on t-mobile service. I am not getting any updates from at&t.. Questions are.. Do I have to be on at&t network to get update? I have done all to unroot with voodoo yet still no updates when checking.. I am also in Wisconsin so if that helps..

Thanks Guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
You are never going to get any AT&T updates on a T-Mobile network.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tecknowboi:
Even if I pull my t-mobile sim card out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
How can you communicate to the AT&T network without an AT&T sim card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tecknowboi:
Guess not... Makes sense... Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Guardian_Bob:
It fixes a lock screen bypass bug, so that's good.

---------- Post added at 03:57 PM ---------- Previous post was at 03:45 PM ----------

There is some kind of check for the AT&T network even if you just use wifi; however, the update is posted here:

http://xdaforums.com/showthread.php?t=2387423

I believe there's a way to use the stock recovery to install it, but I'm not sure how.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
You follow the instructions in the link you provided.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
And backup your internal sd. It will get wiped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
Is there a flashable zip to renable tethering on the 4.1.2. I tried using one for 4.1.1 but that didn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
I personally like a few of the changes such as the new gallery and the folders auto closing after launching an app. There are a few other features that seem cool but don't see myself using. Like you, I can't stand all of the bloat. I thought it was bad before but this is ridiculous. I debloated so I can honestly give this a true test run. If it does not grow on me back to AOSP for me.

EDIT: Thus far I'm impressed. Had issues with the alarm clock before and it is fixed for me now. While not as "clean"or lean as AOSP the little improvements on usability have added up. There are definitely no mind blowing additions but I don't expect it with such a minor update.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheStrokerace:
What do you mean tethering? I know that Iphone has tethering as they can't unlock the phone like they did in the old days. Is that what you are talking about, or is it for 2 different providers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
There is a way to change the order. In fact you can even add data toggle and a few others that are missing. It requires you to deodex the system ui file and do a little bit of minor editing and recreate the apk. Then you replace your current system ui and corresponding .odex file with the new apk. It is a little time consuming though.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
There is a way to enable tethering in the FrameworkRes.apk file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Fyi, if you go back to aosp you will need to downgrade your bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheStrokerace:
ok, but what are you tethering? what does it do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Thinks for the heads up. I just installed this update so I will give myself at least a full week to test out and see what I think.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
It allows you to turn your phone into a wifi hotspot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
back to 4.1.1?

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] TheStrokerace:
Well, that isn't really tethering. And All I have to do is going into my setting, more setting and turn it on. And tethering would be hooking it up to your computer and using your phone for the internet connection.

Plus why would you want to use it? It will just waste your data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dratsablive:
Because sometimes I am in need of a wifi connection where there are none available.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nelimungous:
This method also worked perfectly for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aryeh86:
Stock I747UCDMG2 Rom

Where can I download the rom to flash because every time I try to update OTA it fails even afterI unrooted the phone. I found the Modem in another thread but I cant find a stock rom to flash.

---------- Post added at 06:44 PM ---------- Previous post was at 06:18 PM ----------

Also can the stock 4.1.2 be rooted yet?

Any links to these things will be really helpful..... maybe if someone mayde a stock 4.1.2 udate thread with links to the Rom MOdem etc and root instructions and then sticky it it would help every one flooding here that wants the new update but is having a hard time updating OTA..... Heck if you link me to the Rom and Instructions I ll take the time to write up that thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
A true stock Odin package is not available yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheStrokerace:
There is a stock 4.1.2 rom that is rooted already. I have it on my phone now.