yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmirrow:
Thanks for your help. Perhaps when I rooted it a different kernel was loaded.

Which solution would you recommend in my situation? I currently use Rom Manager, and have CWM 5.8.4.5 installed. I have OTA rootkeeper running also. Also, what would be the benefits/drawbacks to loading the LG1 bootloader or the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I would flash the "no kernel no bootloader" package followed by the bootloader package. Then flash the LG1 kernel unless you plan to use a custom one like ktoonez's Sammy kernel or faux123 kernel. (I'm currently using the ktoonez kernel and loving it.) You can download all the packages and flash them all in order in recovery without rebooting in between. I suggest wiping the cache and Dalvik cache after flashing before you reboot.

I can't really comment about the advantages and disadvantages of flashing the bootloader because I have no idea what changes they made. I'm personally using it and haven't noticed any issues. Flashing the bootloader is a little dangerous because a failed flash can brick your phone, but it was included in the OTA from AT&T so it can't be that dangerous.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmirrow:
Okay thank you for your help. Your bootloader file doesnt seem to exist on media fire anymore though, trying to download it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Thanks for the heads up. I've fixed the link in the OP. Here it is for quick reference: http://www.mediafire.com/?o025gk9q9847q90
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmirrow:
Awesome thanks for your help once again. Last and final questions (I hope). The order that I should flash things is

the No Bootloader no Kernel zip file you have, then the Bootloader zip file, and then the file called UCALG1-Kernel.zip on the front page?

Is that all of the components to make this a UCALG1? Basically i want to make my phone a stock rooted UCALG1 via CWM, with all of my existing data on it. You said I wouldnt lose any data/settings and is that still the case? Wouldnt want to have to reload everything with titaniumbackup, just a pain

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The order shouldn't matter much, but the order you mentioned is fine.

Yup. The only thing that won't be stock LG1 is you'll still have the Google search widget from LEM with the Universal Search intact.

That's right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tigerdonz:
New scripts for the latest OTA from AT&T

I just installed the latest OTA from AT&T. My build number is "IMM76D.I747UCALH9". Could I ask for an updated script for this?

Many thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'm not sure what you mean by scripts, but I did a thread similar to this one for LH9, which you can find here: http://xdaforums.com/showthread.php?t=1896773
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tigerdonz:
Thanks a LOT for your prompt reply.

I have installed the OTA on my phone so my current build number is "IMM76D.I747UCALH9". What I am looking for is the Mod/Hack for "native tethering" - that's what I meant "scripts". I followed you link but am not sure which one I should use, e.g. full OTA with (or without) kernel/bootloader. Could you explain please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
If you're already on LH9, then you just want to install the "Tether and Cell Standby Fix" mod from the MODS section at the bottom of the post. You'll need to have a custom recovery (CWM or TWRP) installed to do that. Do you already have a custom recovery installed? If not and you are rooted, you can use ROM Manager (for CWM) or GooManager (for TWRP) from the Play Store to install the custom recovery. If you're not already rooted, use the instructions here: http://xdaforums.com/showpost.php?p=32218479&postcount=158. After you do that, you can use GooManager to update TWRP or ROM Manager to switch to CWM as you please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
I747ucdlk3

any chance of updating with the new I747UCDLK3 update , with tether add on ?http://www.sammobile.com/firmware/?page=3&model=SGH-I747&pcode=ATT&os=1&type=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtcarey:
I can confirm that you need CWM 5.8.4.5... the 5.5.0.4 (V4-5) version doesn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Which apps? I haven't noticed any problems yet, but I've spent most of the day in recovery. :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Yes. I definitely do NOT want to trip any counters.

Also, I've been trying to find out what the OTA today did, and only thing I've been able to find so far is that it takes away universal search, and updates some apps, whatever that is.

Among my considerations:

Like to keep universal search

I feel that typically a person should have updated apps as they come out

I want to be sure that having root, and possibly installing one of the kernels here is not a problem for LG1

Maybe I need to watch the threads for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Then use Odin to get rooted UCALEM, but install the recovery.img from the recovery zip linked to in the OP instead of the Team Epic recovery mentioned in the Odin/stock thread.

Then apply the OTA zip in the OP.

I removed the updated Google Search app from the OTA, so you will keep universal search. You will still have root, too. I am currently running the Sammy KT747 custom kernel with LG1 without problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Does flashing the bootloader from the update reset the flash counter? Also any differences noticed with the modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Then after that, I should use CWM only for any ROMs , right? I think I"ve read several times that is the case. It is interesting that we can put a 'rooted' rom on, albeit original ROM, and not trip the counter.

Sounds good.

Having done the above, would I need to search for one of the things to install that doesn't wipe out root if anoather OTA comes down? I suspect I could figure out what to freeze with TIBU once rooted so that I can be picky about getting OTAs.

(Applying ROMS will be a bit of less concern if/when Chainfire gets Triangle Away working on US SGS's).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Yeah, it's interesting that they left that loophole. You can't flash a modified recovery or kernel without tripping the counter, but /system is fine.

For the record, the new bootloader in LG1 is the same way. I flashed back to LEM using the rooted image and my flash counter is still 0.

OTA Rootkeeper was reported to preserve root for the LG1 OTA.

AT&T Software update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Ugh...I just shifted to second gear, and realize based on above, I'd be installing a ROM, effectively removing all my apps, and worse, data. No TIBU yet. It's been time consuming getting it all on the phone w/o TIBU to bring it over from my original phone. For some reason, Play did NOT have my app list to bring them down.

Been planning all along to try to ROOT only and then the Kernel. I'm more interested in a Kernel to improve battery (speed is already good).

I'll have to rattle around and think about it a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
LG1 mods added to OP

I rebuilt a few mods that I have applied against UCALG1. The download links are at the bottom of the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Any performance gains to be had from doing this update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Anyone know what the baseband file would be called? I'll be more than happy to flash it with ODIN...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Neither Odin rooted UCALEM image nor the OTA zip update in the OP will mess with /data, so you should be able to root and go to LG1 (if you want) without losing any of your apps or data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Play should have your apps... Menu key => My Apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zaisaroni:
I believe the radio got a new version as well.

Sent from my AT&T Galaxy SIII (SGH-i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Really! Cool. I thought any time you install a ROM, you lost apps. I suppose that's because I've always read you should clear data, etc.

---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------

Yes, absolutely, But when I got this phone, it didn't.

Actually, right after writing that, I thought a bit, and realize I have them in AppBrain, and it will get my apps back. The Screen setups, home screen, widgets never seem to survive, even with restore. The data is the other issue. I have several apps that do have data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lgkahn:
Can we get a patch with just kernel and modem... don't give a crap about the other bloatware updated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gadgetz:
Thats what im talking about!

via Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I'll take a look at it, but it may not be until tonight or tomorrow since it looks like I have a full day of paying work to do today. :( I'm a little uncomfortable making those kinds of changes, though. There are lots of patches to APKs, but also patches to some libraries and configuration files (e.g., some files in /system/etc/wifi) and some files in /system/framework.

I suppose I can put together a file that just does the flashing. This is the flashing that it does:

ui_print("Update sbl2 ota");
assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p3"));

ui_print("Update sbl3 ota");
assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p4"));

ui_print("Update aboot ota");
assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p5"));

ui_print("Update rpmfw ota");
assert(package_extract_file("rpm.mbn", "/dev/block/mmcblk0p6"));

ui_print("Update tz ota");
assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));

It also applies a patch to /dev/block/mmcblk0p1 ("NON-HLOS") which I think is the modem and /dev/block/mmcblk0p7 which I think is the kernel.

I'm pretty sure "aboot" is the bootloader and that's what I left out in the "no bootloader" updater. I really don't have a clear idea what sbl2, sbl3, rpmfw, and tz are.

I guess what I'm trying to say is that while I could understand the Edify enough to modify it to avoid patching Google Search and losing root, that's about all I know. I can strip out some of these other things and just leave the block device flashing in, but I really don't know if it will work or not. I won't test it myself. If someone is willing to give it a shot, I'll be happy to make it available, though. Or you can just try editing it yourself. Edify is not too hard to understand.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
I'm not positive on the recovery you say I should use. I am presuming you mean the OP of mrRobinson's Thread, but the way you wrote that it sounds a bit like you meant the recovery in the OP of this thread. But I"m not recognizing any of the files in this thread's OP as recoveries. (Sorry to be so anal. Just so many different things floating around, I want to do it right.).

He does have this in that thread:

and I'm presuming I in fact can use either of those. You have any reason to recommend one over the other?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
You have to use the 5.8.4.5 version of the recovery from clockworkmod.com to apply the OTA zips in this thread. Team Epic made a recovery for SGS3 as well, but that one won't work because it reports the phone as a Sprint SGS3, not AT&T. I have a link to the 5.8.4.5 recovery as CWM-flashable zip file in this thread's OP. But the part you quoted from myRobinson's thread is linking to the same recoveries (in .img form, which you need to use for the dd command).

So, follow the instructions in mrRobinson's thread and use one of the clockworkmod.com recoveries. That will get you a rooted UCALEM installation. After you do that, make a nandroid backup. Then you can flash whichever OTA zip file from this thread's OP that you want (with or without bootloader). After you do that, I suggest you make another nandroid backup.

Hope that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m.a.s.e:
Hey,

thank you for a great thread.

i do have a question.

in my situation i had the stock but i have de-bloated it.

in which method can i re-add all the bloatware i have removed using ashaham method for auto debloate provided in XDA?

is it possible doing so without going back to stock from scratch? so i wont have to lose all my settings and apps?

please let me know. thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Personally I wouldn't risk trying to modify this OTA updater for just the kernel and modem, because as you pointed out it's a patching mechanism, not the raw modem/kernel files and something could go south in a hurry.

May be just easier for someone who has completed the update fully and is rooted to do a dd pull of the fully patched modem and kernels, take those and put them in a CWM-flashable file (or manually flash back via dd, with all the craziness on the IMEI side I would probably do myself these days) if one were to really want those files.

Just my $0.02 :D

---------- Post added at 01:02 PM ---------- Previous post was at 12:56 PM ----------

I believe MrR's utility you used actually removed the bloatware as opposed to just freezing it, so you are pretty much out of luck. You'll either have to find each bloatware piece and re-add it, or start over from scratch.

I haven't seen anything really compelling about this new update to go through the trouble myself -- but if you are dead set on it, if you haven't already, invest in Titanium Backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Thanks. It definitely helped.

I am now rooted, and have just installed the recovery. This one doesn't recognize my external SD card. I'm about to try appllying your things from the OP.

AFter I've done this, I presume it is OK to find a recovery that will recognize my external card, and apply it.

Only thing a bugging me a bit is I may end up with a concoction of various things. I need to keep track of what I"m doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Neither flashing back to rooted stock with mrRobinson's instructions nor applying the patch in this thread will mess with your /data partition, you shouldn't lose any apps or settings. I think you'd be safe doing this:

Flash back to rooted stock UCALEM

Apply the patch in this thread

Rerun the auto debloat mechanism you used

I would personally make a nandroid before proceeding. If something went wrong, you could always try an advanced restore of /data to get back your apps and settings. That's what I did and it worked fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The 5.8.4.5 version of the clockworkmod.com recovery will be able to access the external SD card, but it won't be able to use it if it's formatted as exFAT (as most cards come). You'll need to reformat it to FAT32 before any recovery will be able to use it.

See here for the reason why recovery won't support FAT32 and this thread (among others) for help doing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Well, the OTA Edify script checks the SHA1 of the unpatched modem and kernel before applying the patch, so I think it's pretty safe. My concern is mainly that I don't know why files to flash to update the "baseband". Is that just the "model" or also the sbl2 and sbl3 partitions. What is the "rpmfw" partition.

I personally don't care about just flashing kernel and baseband. I still have some of the "bloatware" installed and I want that updated. I definitely want the library and wifi patches installed. And since I froze all the bloatware I don't want with TiBu, it will automatically refreeze it after I install the OTA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Ah, OK. Thank you sir.

JFYI...I just tried to download the Tether file you created. Not sure where it is hosted. My Trend Micro blocks it saying the site 'can' download malicious software. I didn't get that when downloaded the UCALG1 update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The tether file is hosted at mediafire.com, just like the LG1 zip files. The file itself is not malicious; virustotal confirms this.

I don't know how mediafire works, but maybe you got sent to a mirror that Trend Micro didn't like. I PM'd you another link you can try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
Are you still using the Sammy Kernel? I'm interested in the Sammy Kernel, mainly for if it improves battery life. I've read that it does, maybe15%. I'm not really sure if all that I've done has involved flashing a kernel of some type anyway. Learning curve.

I'm guessing that if I want to get back to complete stock, I'd flash the Stock Rom, and it includes the stock kernel. But if I'm unhappy with Sammy Kernel for some reason, do you know if a stock Kernel is around? I've only found stock/rooted kernels.

When I was on my Captivate, there was a nice app out that would install and backup kernels. So a person could backup their stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I am using the Sammy KT747 kernel, but not OCd. I can't say for sure whether it is improving my battery life or not.

If you wanted to go back to completely stock, you'd just restore the nandroid backup you made after updating to LG1. :) There are some CWM-flashable zips of rooted UCALEM kernels, but none for LG1 (since I don't think source was released for that one yet). I'm sure I could pull the LG1 stock kernel from my LG1 nandroid and make a zip file for it if that was required.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayFReaZy:
Quick question. I know this update removes the universal search option, but if I were to flash a ROM in the future such as CM10; will that universal search feature be enabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
The OTA in this thread has the update to Google Search removed, so you won't lose the universal search option. I suspect most custom ROMs will also use the older Google Search, at least for now. Even if they don't, you can always install the old one yourself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
In the Sammy Kernel thread, one of the users created and posted a CWM-flashable "revert" that puts the original drivers files and stock kernel back if you want to try the Sammy Kernel and then go back.

---------- Post added at 03:55 PM ---------- Previous post was at 03:53 PM ----------

Now that's the first reason I've seen that makes sense for someone wanting the OTA :D

I've been curious as to what has changed (esp the lib patches). I am wondering how different the wifi patches are from the ones that the Sammy kernel flashes - since they updated those as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
That would take you back to a stock rooted UCALEM kernel, not the LG1 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pinoymutt:
Correct -- sorry I thought that's what he wanted :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gpino001:
ok I Flashed v]back to stock root...using the op recovery method..when i try to install update..i get the following error

E:failed to verify whole-file signature

E:signature verification failed

please advise what i am missing..thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
When you say you flashed back to stock, do you mean you followed mrRobinson's thread? If so, which recovery did you install? You should use the ones he mentions towards the bottom:

However if you have the ATT model (not sure if this will work on Bell, Telus, Rogers, etc.), this recovery will see the extSdCard and seems better for our devices: For ATT models use either this recovery or this touch recovery.​

The zip file I produced doesn't have any signature. So I would guess from your error that you didn't install any version of the CWM recovery and are trying to flash this with the stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gpino001:
yes, I used the recovery link had which contained the file "recovery-clockwork-5.8.4.5-d2att.img and followed the install instructions. Everything seem to install correctly

i admit i am new to this whole thing. how can i verify that the recovery installed correctly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Does it say "ClockworkMod Recovery v5.8.4.5" at the top of the screen in recovery? The only other thing I can think to try is to press "toggle signature verification" until it says it's disabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gpino001:
no, it says android recovery [3e]

hmm..ive tried reinstalling cmw recovery but still says the same..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sabre31:
Ok just flashed this from clockwork recovery and all worked fine however I lost root. Anybody else have this problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gpino001:
ahh finally got it working, thx for pointing me in the right direction
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
This happened to me the first time I tried this and it was because the permissions for the "su" binary got messed up. I added a fix to the updater, but it assumes your su is in /system/xbin. If it is in /system/bin in might be messed up.

You could try "fix permissions" from recovery. If that doesn't work, you should be able to boot into recovery, get a shell using adb, find the su binary and do "chmod 06755 su" in the directory containing su. You might have to do "mount /system" first.

If that doesn't work, you could try flashing one of the root zip files from one of the rooting threads that use the method of flashing recovery through Odin first (don't flash recovery, just flash the rooting zip through recovery).

Don't worry though. As long as you have CWM recovery, you can easily get root back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sabre31:
Thank you so much I tried setting permissions and didn't work however I flashed and the su zip as you suggested from recovery and that worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Just used the upgrade without bootloader and it workrd like a charm following the OP instuctions! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Updated OP with kernel and modem from LG1

I updated the OP with a few more options for partial updates, including a zip without the kernel for those that are already on a custom kernel.

I also added zips for the kernel, the UCALG1 modem, and the UCALEM modem, in case people want to try just those with UCALEM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Anyone give just the modem a try yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
drothenberger...You have been very helpful. I've done some thanks over the posts. I am not rooted, and on G1 with your help.

Your responses have been friendly, and very professional: including links, and plenty of detail. You seem to have a lot of knowledge, but have been on the forum for a very short time (not that many posts).

When you get to the point of putting up a Coffee Button (donation ;) ), I'll participate.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cirusnb:
I'm gonna try the modem on my BELL phone, i'll let you know if it works.

No go, Baseband Version - Unknown

No service at ALL

DON'T FLASH ON BELL PHONEs - altho, if you have a AT&T rom with the same Firmware, it may work.

does not work with VLLE8

Edit: I'm a Dumb Dumb, feel like such a NOOB. lol.. didn't even think of the OP, "make sure you have the right firmware"