Develop Bugs

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search
I've put together a zip file with the I747UCLG1 AT&T OTA update that can be flashed using CWM. This file
does not trip the flash counter
preserves root
does not include the Google search update to remove universal search
does not wipe /data
does require removing all themes and modifications
Standard disclaimer: I am not responsible if this bricks your phone, destroys your IMEI or kills your kids.
Prerequisites: You have to be on stock I747UCALEM for this to work. It may be rooted, but all the standard AT&T and Samsung bloatware must be there with no modifications. It's okay if some of the apps are frozen with Titanium Backup. You must not have any other mods or themes applied. The updater will check this stuff and abort if anything is wrong. I personally restored a nandroid backup I made right after rooting. If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
Boot into recovery and make a nandroid backup.
Go back to AT&T UCALEM rooted stock if necessary (see above). If you're already on stock UCALEM but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALEM stock.
Make sure CWM recovery from clockworkmod.com is installed. The recovery from Team Epic will not work. You can get a zip file to flash in your current recovery to install v5.8.4.5 from here. Use one of the first two files; the ones that start with "recovery-clockwork". After you flash the zip, restart recovery through the "advanced" menu. Your recovery should say "ClockworkMod Recovery" at the top and not "CWM-based Recovery".
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Wipe cache and dalvik cache (optional?)
Flash the attached zip
(Optional) Go to Backup and Restore, Advanced Restore and restore the /data from the nandroid backup you made in step 1. If you used a nadroid backup in step 2, this should restore your data and apps. If you used Odin to flash the rooted UCALEM image, this step isn't necessary.
Reboot
Open Settings / Application Manager. Choose All tab. Click on AT&T Software update. Clear "Clear data". If you were getting OTA notifications before, this will prevent them from recurring. After doing this, your phone will know it's up-to-date.
This worked for me. I checked that my flash counter is still at 0 and Google search is still finding local stuff like apps. I still have root.
DOWNLOADS:
I747UCALG1_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALEM kernel for this to work.
I747UCALG1_OTA_No_Bootloader.zip: This is the full OTA without the bootloader.
I747UCALG1_OTA_No_Bootloader_No_Kernel.zip: This is the OTA without the bootloader or the kernel. You can use this if you're already running a non-stock kernel.
I747UCALG1_OTA_Bootloader.zip: This is just the bootloader. You can apply this along with the "no kernel no bootloader" zip above in case you want everything but the kernel.
MODS:
This process requires the stock framework-res.apk, so at this point you'll need to reapply any mods you already applied. Here are some mods that I've rebuilt against LG1. Both are zip files you can apply through recovery.
Tether and Cell Standby Fix: This includes the mod to enable native Bluetooth and WiFi tethering from here and the fix for the incorrect reporting of Cell Standby time from here.
Tether, Cell Standby Fix, Increase Autobrightness: The same as above, but also with a mod to bump up autobrightness levels from here.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
OTHER PIECES:
Kernel: The UCALG1 kernel and kernel modules.
UCLG1 Modem: Just the modem from the OTA.
UCLEM Modem: The modem from the stock UCALEM firmware.
UCALG1 Bootloader
UCALG1 Bootloader (no checks): This is the LG1 bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
UCALEM Bootloader
UCALEM Bootloader (no checks): This is the LEM bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
LIST OF CHANGES IN OTA:
A full list of the files and partitions changed by the OTA is attached to this post.

Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL
Let us know if it's a lockdown flash...

B-Naughty said:
Let us know if it's a lockdown flash...
Click to expand...
Click to collapse
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.

drothenberger said:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
Click to expand...
Click to collapse
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP

when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip

dave1977nj said:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
Click to expand...
Click to collapse
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.

drothenberger said:
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
Click to expand...
Click to collapse
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks

dave1977nj said:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
Click to expand...
Click to collapse
Here you go.

drothenberger said:
Here you go.
Click to expand...
Click to collapse
tried that still the same error message need some help please....

Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT

dave1977nj said:
tried that still the same error message need some help please....
Click to expand...
Click to collapse
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.

pinoymutt said:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
Click to expand...
Click to collapse
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.

drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

mobilehavoc said:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip?
Click to expand...
Click to collapse
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?
If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.
Does your update include the baseband update ?
Click to expand...
Click to collapse
Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.

I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.

Odin back to pure stock working fine.. some of my apps fore close though

drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!

ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.

ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.

Anyone wanna pull just the baseband for cwm zip?

Clockwork Mod won't stick

I'm trying to flash Clockwork Mod onto a friend's TMO S3 with Odin. I was able to do this successfully with my TMO S3, both are running UVALH2.
Odin says the flash was successful, I restart the phone and try to boot into the custom recovery but it keeps taking me to the stock recovery. I tried a few more times with the same results.
Am I missing something?

Try the no tripping the flash counter method found in the stickies found in the dev section.
You should be able to get around your problem with this method.
Sent from my SGH-T999 using xda premium

kpizzle said:
I'm trying to flash Clockwork Mod onto a friend's TMO S3 with Odin. I was able to do this successfully with my TMO S3, both are running UVALH2.
Odin says the flash was successful, I restart the phone and try to boot into the custom recovery but it keeps taking me to the stock recovery. I tried a few more times with the same results.
Am I missing something?
Click to expand...
Click to collapse
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick

ingenious247 said:
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
Click to expand...
Click to collapse
You are the man!!!

there's a little "thanks" button on my post.. feel free to click it
and no problem, glad to help!

ingenious247 said:
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
Click to expand...
Click to collapse
So I just realized something. I can't even attain root access, how can I edit these files?

Can flash mrRobinson's LH2 w/root and you will have full LH2 stock with root. It is an Odin package and only flashes /system partition so no /data loss.

kpizzle said:
So I just realized something. I can't even attain root access, how can I edit these files?
Click to expand...
Click to collapse
Flash CWM through Odin, but turn off the auto reboot in Odin
That way it won't overwrite it
Then power down when it's done, and boot into recovery, Flash Superuser

Will i still be able to receive JB OTA update when the time comes, if i rename these two files and flash CWM through ROM manager?

arthaz28 said:
Will i still be able to receive JB OTA update when the time comes, if i rename these two files and flash CWM through ROM manager?
Click to expand...
Click to collapse
No, you cannot receive OTA updates unless you are on stock recovery.
So you would have to Odin back to stock before accepting the update, which is simple enough.
Or just wait for someone to take the update and make a flashable zip file which will happen pretty quickly once the OTA comes out

ingenious247 said:
No, you cannot receive OTA updates unless you are on stock recovery.
So you would have to Odin back to stock before accepting the update, which is simple enough.
Or just wait for someone to take the update and make a flashable zip file which will happen pretty quickly once the OTA comes out
Click to expand...
Click to collapse
You don't need stock recovery for any reason at all. Not anymore.

I never said you needed it. I was answering the question that was asked.
And if you don't want to flash a modified version of a stock ROM, then yes, you do need stock recovery. Some of us don't like deodexed ROMs and care to choose what we debloat.

ingenious247 said:
I never said you needed it. I was answering the question that was asked.
And if you don't want to flash a modified version of a stock ROM, then yes, you do need stock recovery. Some of us don't like deodexed ROMs and care to choose what we debloat.
Click to expand...
Click to collapse
Thank you sir!
After I was rooted, I created a backup using CWM. So, if the update comes out, I can just flash my backup stock ROM again using CWM rand I should be able to receive the OTA update, right?
(sorry I am a noob and still learning about this whole rooting, custom ROM, etc stuff)

arthaz28 said:
Thank you sir!
After I was rooted, I created a backup using CWM. So, if the update comes out, I can just flash my backup stock ROM again using CWM rand I should be able to receive the OTA update, right?
(sorry I am a noob and still learning about this whole rooting, custom ROM, etc stuff)
Click to expand...
Click to collapse
No, you would have to Odin back to stock which would overwrite CWM with stock recovery. If you're not familiar with Odin read up on it, it's really easy to use. Just make sure you get it from the correct thread for your phone model and you'll be fine.
Sent from my SGH-T999 using xda premium

Going back to rooted stock jellybean ROM from CM10.1

I wish to return to a rooted stock JB ROM from CM10.1 . CM10.1 is too buggy for me, and CM10 had one bluetooth bug in the final release that was kind of a game killer for me. I'd like to go back to stock JB but keep my custom recovery. The only files I've found for stock jellybean are full stock in that they'll flash over my recovery as well as my system. Does anyone know where I can find a root stock image that will let me flash just the system and keep my recovery like any other rom, so that I can flash back to CM10.1 when it is more stable. PS I am also on Linux and do not regularly have access to a windows machine so I do not have access to Odin, or Kies.

after you flash to stock just flash a recovery, that's what i've done.
also, this is the wrong section and you should search first.
sent from my I747

I searched and found only "One click" stock roms, and the "Fully Stock" roms. Neither of which solve my problem. Did you even read the portion of my post where I say I don't have access to Odin, or Kies or any of that? My only option for flashing is CWM. And I'm not sure how well overwritting CWM while CWM is flashing would work, but I don't think it would go well.
cehf said:
after you flash to stock just flash a recovery, that's what i've done.
also, this is the wrong section and you should search first.
sent from my I747
Click to expand...
Click to collapse

find a cwm flashable zip of a stock rom. it doesn't need to be a current version. flash that. then find the cwm flashable ota zips and flash those. you've retained root, and cwm. i have done this process as well.
i'd link you to the threads you need but i'm on my phone and it's difficult to find this way.
edit: one of the otas is here. i haven't found anything about updating to jelly bean, though. i know there's a tutorial somewhere about making cwm flashable zips, i might try making one for you after i get my sister to sleep.
sent from my I747

go to this link:
http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1
find the appropriate version for your carrier and flash via your recovery. its pre-rooted and cwm/twrp flashable, no odin or PC needed.

Russ77 said:
go to this link:
http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1
find the appropriate version for your carrier and flash via your recovery. its pre-rooted and cwm/twrp flashable, no odin or PC needed.
Click to expand...
Click to collapse
i don't see anything about cwm, only odin?
op, here is a full stock rom. here is the ota that comes after.
sent from my I747

When you're back to rooted TW, flash the recovery you want with Mobile ODIN.
Sent from my SGH-I747M

cehf said:
i don't see anything about cwm, only odin?
op, here is a full stock rom. here is the ota that comes after.
sent from my I747
Click to expand...
Click to collapse
my mistake. OP, grab mobile-odin and do that since you're already rooted

[Q] Is there official ODIN flashable 4.2.2 ROM?

As subj says, looking for stock 4.2.2 ROM

obender said:
As subj says, looking for stock 4.2.2 ROM
Click to expand...
Click to collapse
No such ROM exists, as the Sprint GS3 has only gotten updates up to 4.1.2 (and without the Premium Suite). The International GS3 has also only gotten updates to 4.1.2, but it did include the Premium Suite. A lot of developers around these parts were able to create mods for various features of the Premium Suite, but the "official" stock Rom has not gotten them (obviously).
Here is a link to the latest Stock Rom (rooted) from Freeza. It is flashable in Custom Recoveries. I don't have the link to the Odin flashable stock 4.1.2, but I'm sure CNexus will be by shortly with the answer.

topherk said:
No such ROM exists, as the Sprint GS3 has only gotten updates up to 4.1.2 (and without the Premium Suite). The International GS3 has also only gotten updates to 4.1.2, but it did include the Premium Suite. A lot of developers around these parts were able to create mods for various features of the Premium Suite, but the "official" stock Rom has not gotten them (obviously).
Here is a link to the latest Stock Rom (rooted) from Freeza. It is flashable in Custom Recoveries. I don't have the link to the Odin flashable stock 4.1.2, but I'm sure CNexus will be by shortly with the answer.
Click to expand...
Click to collapse
Thanks a lot for the detailed answer, I'd be interested in the latest stock 4.1.2 (ODIN) as well, meanwhile I'll try the one you provided a link to.

obender said:
Thanks a lot for the detailed answer, I'd be interested in the latest stock 4.1.2 (ODIN) as well, meanwhile I'll try the one you provided a link to.
Click to expand...
Click to collapse
If you want to return to 100% stock (no root, stock recovery, etc.) you can follow qbking's tutorial on his website. He also has the links to the "official" Odin files. I think, though, that they only go up to LJ7, so you'd have to run the OTAs in order to have the most updated "stock" experience.
If you have a custom recovery installed and want to go back to unrooted, stock MB1, you can also check out this billard412's thread on the matter. He has recovery-flashable files that will return you to 100% stock. Just be sure to read all of the instructions before you flash anything.
I have a quick question, though... Why are you so insistent on using Odin? Did you keep the stock recovery? And if you did, I'd like to hear your reasoning behind it. I'm quite intrigued by those who root but don't want the custom recoveries.

topherk said:
If you want to return to 100% stock (no root, stock recovery, etc.) you can follow qbking's tutorial on his website. He also has the links to the "official" Odin files. I think, though, that they only go up to LJ7, so you'd have to run the OTAs in order to have the most updated "stock" experience.
If you have a custom recovery installed and want to go back to unrooted, stock MB1, you can also check out this billard412's thread on the matter. He has recovery-flashable files that will return you to 100% stock. Just be sure to read all of the instructions before you flash anything.
I have a quick question, though... Why are you so insistent on using Odin? Did you keep the stock recovery? And if you did, I'd like to hear your reasoning behind it. I'm quite intrigued by those who root but don't want the custom recoveries.
Click to expand...
Click to collapse
The answer is simple, even with custom recovery I always had problems with installing custom recovery roms and never had issues with Odin roms. It is just me I guess.

So I used stock ROMs from the link above and flashed them with CWM, I had to patch them a bit since I removed some system apps and it would not flash without patching the update_script.
Funny thing, the android version and build version didn't change but kernel and baseband versions changed as expected.
Since I've observed both MA6 and MB1 updates going through and (for MA6) even updating apps, I assume not only kernel and baseband got updated but for some reason that part of system info didn't change.

That info is stored in the /system/build.prop file. Check the contents with a root explorer, could be a bad download

CNexus said:
That info is stored in the /system/build.prop file. Check the contents with a root explorer, could be a bad download
Click to expand...
Click to collapse
On the phone that file indicates old android and build versions.
How do I view the build.prop.p file that is in the update itself?

obender said:
On the phone that file indicates old android and build versions.
How do I view the build.prop.p file that is in the update itself?
Click to expand...
Click to collapse
Extract the zip you flashed and open the zip_extracted/system/build.prop

CNexus said:
Extract the zip you flashed and open the zip_extracted/system/build.prop
Click to expand...
Click to collapse
If you mean the one that is on sdcard that I used for flashing then that one has only /patch/system/build.prop.p which is a binary patch I assume and the /system of the zip has only CSCVersion.txt and then a bunch of subdirectories.

Ok then, at this point it doesn't really matter. Did you want to stay on plain stock rooted or flash a custom rom? Flash your custom rom now, or stay on stock rooted and edit all instances of the build number to show "MB1" instead of what its showing right now

Maybe you could attach the portion of the correct build.prop MB1? That would make my life a bit easier thanks!

obender said:
Maybe you could attach the portion of the correct build.prop MB1? That would make my life a bit easier thanks!
Click to expand...
Click to collapse
Haha no problem, the lines you need to change are quoted here in my guide (its in my sig as well): http://forum.xda-developers.com/showthread.php?t=2209418

Thank you!

obender said:
[Q] Is there official ODIN flashable 4.2.2 ROM?
Click to expand...
Click to collapse
I wish there was.
What? I am using my OG Evo 4G? My S3 must be dead... Good thing I love CM7!

[Q] Unsure how to get to latest update - Rooted Stock

I currently have Stock 4.2.2 Rom - S-Off - Rooted - TWRP
How can I get to the newest Stock 4.3 (Radios, etc) ?
Is it easier to just flash stock recovery, then take the update, then flash TWRP and superuser back?
Or has someone made the update into a root-friendly flash-able zip yet?
Thanks in advance if this is a dumb question, but I wanted to ask so I get it right the first time.

sdlucky7 said:
I currently have Stock 4.2.2 Rom - S-Off - Rooted - TWRP
How can I get to the newest Stock 4.3 (Radios, etc) ?
Is it easier to just flash stock recovery, then take the update, then flash TWRP and superuser back?
Or has someone made the update into a root-friendly flash-able zip yet?
Thanks in advance if this is a dumb question, but I wanted to ask so I get it right the first time.
Click to expand...
Click to collapse
Look here >>>>

santod040 said:
Look here >>>>
Click to expand...
Click to collapse
Thanks for the info...
So I can just flash these with no loss of data? Or do will I need to restore data after I flash the rom?
My plan would be:
1) flash "Odexed Full ROM"
2) flash "2.10.605.1 firmware"
That should put me latest update stock right? (I might need to re-flash superuser)
I can flash all of this through TWRP?

sdlucky7 said:
Thanks for the info...
So I can just flash these with no loss of data? Or do will I need to restore data after I flash the rom?
My plan would be:
1) flash "Odexed Full ROM"
2) flash "2.10.605.1 firmware"
That should put me latest update stock right? (I might need to re-flash superuser)
I can flash all of this through TWRP?
Click to expand...
Click to collapse
You cannot flash the firmware in twrp.
It has to be done following the instructions in the post.
I would do firmware and then the rom.
Put the rom on your internal storage before flashing the rom.
Flash the firmware as instructed, then in recovery flash the rom, reboot.
Do not try to reboot in between, it wont work.
If you do it in that order you won't have to wipe, you will be on the latest OTA and have a rooted boot.img.
Supersu is installed already. You can prevent it from updating or flash the newest one here.
Read the OP and post#2 and follow it you should be fine.
Yes you want odex coming from full stock...

Thank you for all of the help santod040 !!
Your files and instructions worked perfectly.
I'll make sure to check in on your threads when the 4.4 update comes around.