yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stan.s:
I can not express how pleased I am with the install of your zip files. I did the no-bootloader version without a wipe of the cache/dalvik and my data, apps et all are all there. The ATT Device Managment started up when the phone finally rebooted. I'd postponed it the max # of times (3x8 hours), and after it did it's thing, the phone started running normally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdhommert:
Question.

I'm waiting until we get some solid aosp/aokp roms to begin the whole rooting/flashing stuff.

The damn phone will not stfu about the update and that is a huge pita. If I'm not rooted is there ANY negatives to just doing the OTA? Will I still be able to root with zero problems, or any other negative repercussions other than losing the search? I just want the damn update box to stop taking over my phone. The back button wont even let me out of it, I have to use the home/multitasking button and the icon is always in the notifcation bar.

halp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
At the moment, there's no way to root after you apply the OTA in a way that won't trip the flash counter. If you want to root, I suggest you do it with UCALEM (before the OTA). Once you've done that, you can either apply the OTA or use Titanium Backup to freeze AT&T Software Update and stop the OTA notifications.

If you do decide to apply the OTA after you've rooted, I suggest you use the method in the OP. :)

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Actually, I was successful. I applied the Stock Rom, per your suggestion, using ODIN 3.04 , back to UCALEM, then followed the rooting processes. My counter did not increment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rsf2:
After flashing, getting Android Is Upgrading after each boot.

First of thanks for putting this together!

I apologize if this is a noob question, this AT&T Galaxy S3 is my first every android device (long time iphone user who has seen the light).

I'm on the stock ROM rooted following this article androidauthority .com/galaxy-s3-sgh-i747-att-root-99789/. I followed the directions in the OP, nandroid backup, flashed the I747UCALG1_OTA.zip, cleared both caches, and restored just the data portion of the backup. Everything seems working fine with the exception that now every time I reboot, i get the "Android Is Upgrading" dialog.

While searching for a solution I've read that one can receive that when they clear there cache but this happens every standard reboot. I also read that this could be related to a fastboot setting being disabled? Does that apply for this phone/firmware? Lastly I have a few apps that have odex files in the /data/app/ directory and I ready that those being present can cause this? Odd thing is they were present before I flashed the OTA zip and didn't get the Upgrading dialog on boot.

Does the method I used to root have something to do with why I'm seeing it or is it simply because a non-standard rom was flashed? The general consensus from what I've read seems to be that this is nothing to be overly concerned about but it does increase the boot time.

Curious if others are getting this message after flashing and if there is any way to get rid of it? Perhaps a file tuck somewhere that's telling Android to perform this on each boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm not sure what's causing that. I only see that once after the process. One way to check if it's your apps in /data is to do a factory reset and then try to boot. If that gets rid of the message after the first boot, you have your answer. You can always restore the /data from your nandroid after the test.

Good luck! Please report back if you figure it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stan.s:
The android is upgrading is normal even for this zip if you install the kernel (I did without the boot loader). Mine said that it had to upgrade over 200 items, so just wait it out.

However, just before I went to the rooted stock to be able to run this zip the att tried to do its thing, and I shut down the phone. . Also fwiw if it tries on the rooted stock, it seems to get a failure message.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dave1977nj:
A few programs from the market I had already had on the phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
changelog

Anyone find a change log for this update? I can't find one anywere on xda or Google
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drwx:
That's normal for any ics rom that doesn't wipe. It is rebuilding the dalvik cache, i believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rsf2:
You are the man!

@drothenberger, you are the man!

I followed your advice by doing a fresh nandroid backup and reset data/factory. On reboot there was no "Android Is Upgrading" message so as you mentioned, I had my answer, something was amiss in my data directory. I restored back the data portion of the latest nandroid backup and on reboot I was once again presented with the "Android is Upgrading". I went into my /data/apps/ directory and deleted all the .odex files present and rebooted. Once again the "Android Is Upgrading" message appeared. On a whim I fired up the CWM ROM Manager app and ran fix permissions. I then rebooted and have not seen the "Android Is Upgrading" message since. I had run the fix permissions from the ROM manager before while troubleshooting, but maybe something with revertering/restoring the data directory and then running fix permissions was the trick.

Not totally sure what the issue was, but right now I'm a very happy camper! My baby is patched with the lastest OTA sans the bs google search downgrade and, having also patched your "Tether, Cell Standby Fix, Increase Autobrightness" patch, I'm rocking free tethering and the annoying cell standby issue fixed!

Thanks so much for your help and effort putting these patches together!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
just flashed the G1 zip, the one without the bootloader, everything went great, root preserved, universal google search still on, everything seem working fine,took about 3 mins to flash it

first time android and samsung phone user, so still reading and learning before I flash some custom roms or mods :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
I let the ota flash automatically and now cwm recovery disappears after applying it. I apply it boot in to recovery and it's cwm recovery. Reboot and boot back into recovery and it's stock. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tenkie:
Any benefits with flashing the G1 kernel and/or modem?

(I'm hoping it addresses the overwhelming standby drain on weak reception LTE networks)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The OTA installed a file /etc/install-recovery.sh:

#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p18:6404352:0a4fd7e91ff85eadbd0fba72485ca5a9ec50d671; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p7:5712128:fb95a5d43d651be3972f96e8d6d2eb181a9fc66b EMMC:/dev/block/mmcblk0p18 0a4fd7e91ff85eadbd0fba72485ca5a9ec50d671 6404352 fb95a5d43d651be3972f96e8d6d2eb181a9fc66b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi

I honestly don't understand exactly what this is doing, but I didn't include it in the OTA zip I put together because I'm pretty sure it's trying to mess with recovery and I didn't want that. Maybe if you remove this file (and also /system/recovery-from-boot.p) it will fix your problem. If you have a /system/recovery.img file, try removing that, too.

Let me know if that works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I don't have LTE in my area, but you can always try the new modem and report back with your results. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Full list of files changed by the OTA attached to OP

I attached a full list of the files and partitions the OTA changed to the OP, in case people are interested.

I've heard said "the OTA just removed universal search", but I don't think that's completely true from the list of changed files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tenkie:
I'll flash the updated modem (and the updated kernel) and report my results. Thanks for stripping them out of the new ROM for us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vinuneuro:
Please do. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyan~:
I thought the update was 10MB. what can they change with 10MB. hm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
It worked! It worked! Deleted /etc/install-recovery.sh and /system/recovery-from-boot.p. Booted into cwm recovery 4 straight times. You are the man! A million thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
It's mostly binary patches and not full copies of the changed files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stan.s:
The emmc mmblk is the same location that cwm is installld in mrrobbinson's adb bypass odin install. The bootloader was IMHO intended to overwrite it or parts of it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drwx:
Anyone else getting wifi that won't connect?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shep FC3:
Tried flashing the no bootloader version and failed with a long "assert failed: apply_patch_check("EMMC:...)" message. Updated CWM to the recommeded version and still will not flash. Anyone else have that issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
It's working fine for me. Maybe try to reflash the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
That means either your modem or your kernel are not what the OTA is expecting. Are you running a custom kernel? Or even the rooted stock UCALEM kernel? If so, try flashing the no bootloader / no kernel version. If you're running the UCALEM rooted kernel, flash the LG1 kernel after. If you're running something else like KT747, don't bother.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shep FC3:
Stock kernel rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Then flash the no bootloader/no kernel zip and then the UCALG1 kernel if you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpazevedo:
Did you flash Ktoonsez Kernel? If so you need to remove the updated WIFI and Bluetooth drivers.

Flash http://xdaforums.com/attachment.php?attachmentid=1184198&d=1341720006

And it will flash the old drivers.

I had to do that after I found out I had no wifi. Hand to nandroid back and flash it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
anyone have any results worth reporting with the new modem only?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tenkie:
So far, pretty good. Connection seems fairly consistent. I'll update more as i'll be in a LTE area tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
That attachment will get you the UCALEM kernel. If you want the UCALG1 kernel (this is a thread about that :)) then flash the kernel in the OP. That one also includes the kernel modules and should also fix your problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Would I still need to flash to the stock rooted odexed LEM before flashing the modem update only?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
No. The modems and the kernel are self-contained, complete flash files. You can flash them regardless of which ROM you're on. (Well, the kernel will only work with LEM or LG1-based kernels and not CM9 or AOSP, but you get the idea.)

The OTA zip itself is not a complete ROM, it's just a bunch of binary patches to various files. This is why you have to be on stock (non-rooted) LEM first. If you're not, the binary patches would do the wrong thing. The OTA zip checks the checksums (SHA1) of the files it's going to patch first, so it will just abort if you're not on the right ROM instead of doing damage.

Sorry for the lengthy explanation for your simple question...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greenstrat67:
Sorry about continuing on in that thread. It appears I was editing at the same time you were posting and backed out before getting the info about why v5.4.8.5 and already updated through ROM Manager to Touch which gave me v5.4.8.7 which it looks like I don't want so I'll need to redo that. It just seemed easier that way. Is that why in ROM Manager it says my "ROM is not set up to receive OTA updates. Please contact the ROM developer"?

What is the reason for discontinuing being able to access the SD card in subsequent versions of the recovery? It would seem like you'd want to get the latest which I can at least easily get now if there's a reason.

Anyway I got v5.8.4.5 on have backups from both versions and I'm ready to flash / would I747UCALG1_OTA.zip be the file I want to flash with?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
how do you update CWM to 5.8.45 if I'm on 5.5.04?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
I'm running the latest modem on the 7-15 build of AOKP. I was getting ~.50 download speed where I work and now I am getting ~3.00. It could be that there are less people around today, for whatever reason, so I will do more tests throughout the day and also throughout the week. Also, I do not have LTE, HSPA+ only.

edit: Doing 1 speed test yields very low results. My download speed is low but my upload speed is consistent. Doing more tests gives me a better download speed, capping out ~3.00. Regardless this modem is giving me much better results than stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stan.s:
turn it off/on or reboot. I find that once it connects it stays connected but that it negotiates a bit too long at times....

---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------

use the adb method either in a terminal on the phone or your PC as described here: http://xdaforums.com/showthread.php?t=1739426
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Nvm got it to update now my issue is that it won't install due to me deleting stock bloatware that I did not backup what should I do now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
You could flash a stock ROM, update to this one, then do an advanced data restore from CWM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Will reveerting back to stock like his method work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
I can't really say, I haven't done it. I just know that reverting to stock will reinstall all of the stock apps as well, so then you can update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I don't know.

Yup, that will work. Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
First flash back to stock UCALEM following mrRobinson's directions here. Be sure you apply the clockworkmod.com recovery (the ones he mentions are specifically for AT&T) and not the one from Team Epic. Then, make a nandroid backup, just to be safe. Then go ahead and apply the OTA.

None of that will mess with your /data partition, so your applications and settings should remain. You will have to debloat again, though.

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
OK I read through the whole thread but I'm not exactly clear on some things:

-Is it thought/known that flashing full ota with bootloader will Bork recovery? It seems everyone's avoiding the bootloader edition.

-I have nandroid with stock rooted so I will restore to that but would like to go back to my custom rom of choice right after installing ota zip? Is it advised to boot rom once after the ota and then reinstall custom rom? Or us it OK to just flash the custom rom right after ota zip while still in recovery?

-To go along with above has anyone nandroid restored back to custom rom after ota or just went with a fresh install.

Sorry for all the ? 'S this imei issue has got me all paranoid about everything I do now lol!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I personally flashed the bootloader version and haven't had any problems with IMEI or flashing custom kernels.

I'm not running a custom ROM, but if you're going back to one, maybe you should just flash the new modem (and maybe the kernel) and leave the rest. The custom ROM will replace all of /system, so you will just be missing the updates to sbl2, sbl3, rpm, and the partitions. I don't know what they do. You can find some more information in Adam's thread about the Verizon bootloader in VZ Original Development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] magn2o:
I flashed the "full" update (w/ bootloader). Recovery still works fine, still have root, my IMEI is intact.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
Thanks for the advice guys. Think I'll just role with the modem for now it'll be easier to compare apples to apples, then I'll probably comeback and do the full ota anyways just cause. ;) thanks for the great work/thread op truly an excellent contribution!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bracketologist:
I flashed the "full" version (w/bootloader) and everything worked like a charm. Root and recovery works as usual. Thanks for making the OTA into a flashable zip. Also thanks for redoing the mods as well. The no increasing ring mod was something I didn't want to lose. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greenstrat67:
I747ucalg1_ota

I'll let you know how it goes.I really appreciate all the help and especially patience. I noticed a SMs reference to member's lack of using the Thanks Button but have been using it regularly I hope it helps. -gs67
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Say there drothenberger...I applied the Sammy Kernel after getting this stuff on. Its running fine, but I find myself in the same camp as several others on that thread with MAX CPU speed not holding at 1512...drops to 1350.

I've been reading the thread, which I think I've seen you in, about the IMEI problems. At this point, I have no problems.

I installed the AT&T CWM: recovery-clockwork-5.8.4.5-d2att.zip, from the ones on your list form item 3.

I"m thinking about applying the UCALG1 Kernel from your Other Pieces links above. I want to use Voltage Control on it and see what speeds it shows. I'm not sure why SAMMY would be running below the default MAX, which I expect to be 1512.

Have you heard of anyone applying that Kernel and losing IMEI?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I also had problems with the Sammy KT747 kernel and SetCPU. I froze SetCPU, installed Voltage Control, and that worked fine for me.

I have personally flashed a lot of kernels, bouncing between rooted LEM, LG1, Sammy KT747, and the faux123 kernel, and my IMEI is just fine. But I don't think anyone really understands what's causing the IMEI issues, despite the advice in the OP of the IMEI thread.

Personally, I have made a dd clone of all my partitions. If I ever do lose my IMEI, I'll try restoring those. If that doesn't work, I'll either return it to AT&T (if within my 30 days) or try mobiletechvideos.com's repair service.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I'm having an issue trying to remove the bloat after flashing LG1(no bootloader zip)

When I try to uninstall some bloat apps with titanium back up, it says..

"cannot remove system app

failed to locate the apk file"

Any workaround to remove the bloat, or maybe should I come back to LEM, when I did remove the bloatware without any issues, it seem the OTA renamed/changed location so titanium cant find/delete them :eek:

the apps that I couldn remove show in titanium as "(updated)"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
That's pretty weird. Did you clear your cache and dalvik cache? If not, try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I clear them TWICE( to make sure) both cache and dalvik cache BEFORE flashing the zip, not after, should I clear them after too? sorry for the boob question

I used the cwm 5.8.4.5-d2att with mrRobinson not tripping counter method

what should I do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm really not sure what to suggest. I've never had that problem. I know in TB you can click on an app to open your backup history for it. If you tap on the top entry (the only labeled current) it will tell you the APK path. I would try looking at that for one of the troublesome apps and then checking to see if it is really there or not. I can't figure out from your description if TB has stale data or if there's some other problem.

You could also doing a Wipe Data on TB itself. I'm not sure what information you'd lose, so if I were you, I'd make a nandroid backup first.

Good luck and please report back if you figure this out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
Ill try the TB route, btw I installed the other 2 mods you had in the op (tether/ring volume) they are working fine, but being unable to remove the bloat is kinda annoying. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Yeah...I've tried the uninstall of the CPU apps, then install of Voltage Control, which they say fixed the problem. I appeared to fix it, but after a couple hours it reverted back.

I guess I'll plug skin at 1350. Still performs well.

[EDIT]

While we don;t know that we can restore from am clone and get IMEI, what you are doing sounds like a good idea. I need to do some searching and fine info on how to do that, and what the 'partitions' are in the phone.

I wonder if a Nandroid wouldn't server that purpose?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dirtyballoonot:
no luck

I can't seem to get anything to flash. I tried restoring to stock after it failed verifying. Now it doesn't even get that far. I'm stock rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I wrote a script that does it through adb. It will work with Cygwin or under Linux. (Sorry, I can't write Windows scripts very well.)

You can get the list of partitions from the phone itself:

# cd /dev/block/platform/msm_sdcc.1/by-name
/dev/block/platform/msm_sdcc.1/by-name # ls -l
lrwxrwxrwx 1 root root 20 Jan 9 01:42 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Jan 9 01:42 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 9 01:42 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 9 01:42 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 9 01:42 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 9 01:42 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 9 01:42 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 9 01:42 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 9 01:42 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 9 01:42 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 9 01:42 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Jan 9 01:42 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 9 01:42 param -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 9 01:42 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 9 01:42 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Jan 9 01:42 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 9 01:42 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 9 01:42 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 9 01:42 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 9 01:42 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 9 01:42 system -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 Jan 9 01:42 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 9 01:42 userdata -> /dev/block/mmcblk0p15

No, it doesn't backup everything.