Just a quick question... My epic is rooted and i got the EI22 ota notice today. if I attempt to accept the ota update what will happen? Currently running 2.2.1 Froyo DK28. Thanks!
I personally would unroot first. Never take an OTA update on a rooted phone. Best case you lose root, worst case, bricked device. Not worth the risk, at least for me.
Unrooting and rerooting is easy enough. Do you have a custom ROM installed? If so the OTA update likely would fail anyway.
chzeckmate said:
Just a quick question... My epic is rooted and i got the EI22 ota notice today. if I attempt to accept the ota update what will happen? Currently running 2.2.1 Froyo DK28. Thanks!
Click to expand...
Click to collapse
why would u want to do so? there is stock system dump that u can just use restore from cwm. thats what i did and it stayed rooted.
Sent from my SPH-D700 using Tapatalk
balagyi said:
why would u want to do so? there is stock system dump that u can just use restore from cwm. thats what i did and it stayed rooted.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Can you please elaborate? What is the procedure?
You are rooted, do you have Clockwork Mod installed? If so you can just grab the factory image from here when it shows up - http://forum.xda-developers.com/wiki/SPH-D700-Official_Roms
Probably worth buying Titanium backup from the market to backup your apps and data first, then you could even just Odin the new version if you had to and restore.
chzeckmate said:
Can you please elaborate? What is the procedure?
Click to expand...
Click to collapse
go to this thread:
http://forum.xda-developers.com/showthread.php?t=1337222
this is instructions from OP
- download system dump file
- unzip the whole folder to /sdcard/clockworkmod/backup/ (assuming you have CWM)
- if you are on EXT4, install the gotorfs.zip through CWM first
- and from CWM, do a Back Up/Restore, and select restore
from there do a restore.
** this will wipe off everything. so make TB for apps and Go SMS for sms backup which I did.
EDIT:
if you want EI22 modem:
- Odin modem to EC05
- and flash the zip (http://forum.xda-developers.com/showthread.php?t=1339401) through CWM
*** make sure you Odin EC05 before flashing EI22 modem. otherwise, it won't work.
enjoy
Related
I'd like to uninstall a ROM (or is it just re-flashing stock?) so that I can do the normal update process to EL30 from EI22, and then apply a different ROM later.
What's the best method of doing this? I was able to apply the ROM without losing data, so getting back to stock should preserve it as well I hope. Pretty sure that on top of reverting to stock image I'll have to drop CWM but I'm cool with that. Just not sure of which steps to take to get from point A to point B.
TIA
Easiest way to get back to stock EL30 would be to flash the EL30 tar with Odin. You would however lose your data if it wasn't backed up first.
Go to Development section and in the stickies click the Roll Up sticky thread. Click on How to restore a semi-bricked Epic. Follow the first post exactly to install the latest Sprint firmware EL30. Make sure to backup first with Titanium Backup if you plan on rooting and restoring apps and data.
Sent from my SPH-D700 using xda premium
tigerknight said:
I'd like to uninstall a ROM (or is it just re-flashing stock?) so that I can do the normal update process to EL30 from EI22, and then apply a different ROM later.
What's the best method of doing this? I was able to apply the ROM without losing data, so getting back to stock should preserve it as well I hope. Pretty sure that on top of reverting to stock image I'll have to drop CWM but I'm cool with that. Just not sure of which steps to take to get from point A to point B.
TIA
Click to expand...
Click to collapse
no need to...just flash this
http://forum.xda-developers.com/showthread.php?t=1461377
[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?
Hi All,
I searched the forums and couldn't find anything, so if I missed it, my apologies.. But I'm trying to OTA update my Captivate. The OTA update always failed, so I found out I needed to unroot. So I unrooted, but now when the update downloads and reboots, it reboots into CWRM. Is there a way to then install the update? If I simply select reboot, it reboots back but then says update failed.
Any ideas?
Thanks
Bumpity ... Anyone?
U can't do OTA when ur rooted and CWM u have to resign the zip file or something like that
phatryan69 said:
U can't do OTA when ur rooted and CWM u have to resign the zip file or something like that
Click to expand...
Click to collapse
Yeah I unrooted... What do you mean by resign the zip file?
If you're on 2.3.5 stock and wanting to get to 2.3.6, the following thread has instructions that work perfectly:
http://forum.xda-developers.com/showthread.php?t=1800847
The stock recovery is also available in Odin format in this thread http://forum.xda-developers.com/showthread.php?t=1762209
Nardholio said:
The stock recovery is also available in Odin format in this thread http://forum.xda-developers.com/showthread.php?t=1762209
Click to expand...
Click to collapse
Flashed back to stock recovery, ran update, update still fails Phone is unrooted...
R u an att or Rogers customer???
phatryan69 said:
R u an att or Rogers customer???
Click to expand...
Click to collapse
AT&T.. Currently on 2.3.5.
"Unrooting" doesn't restore the original untouched file system or any other modifications you may have made with Titanium. Download the stock firmware from samfirmware.com and reflash. If that doesn't work, do a factory reset from settings or recovery or with Kies. The Kies restore will most definitely fix whatever your problem is. Kies doesn't recognize modded devices though, so you may have to flash stock first AND THEN do a restore with Kies.
Sent from my SAMSUNG-SGH-I927 using xda premium
If my S3 is stock rom but rooted with cwm recovery loaded, will I be able to get the AT&T OTA JB update once it rolls out with no issues? I understand I might lose root, but is that it? I know it will be a couple more months, just want to be sure the phone will be able to get this with no issues when the time comes.
wiz4769 said:
If my S3 is stock rom but rooted with cwm recovery loaded, will I be able to get the AT&T OTA JB update once it rolls out with no issues? I understand I might lose root, but is that it? I know it will be a couple more months, just want to be sure the phone will be able to get this with no issues when the time comes.
Click to expand...
Click to collapse
From what I understand, you need the stock recovery in place for OTA updates, otherwise they will fail. Which makes sense.
Ok that makes since, so closer to go time I can just put the stock recovery.img on there right?? Is it that simple?
wiz4769 said:
Ok that makes since, so closer to go time I can just put the stock recovery.img on there right?? Is it that simple?
Click to expand...
Click to collapse
flash to stock via Odin, so yes...
-Ryan
Or you could just wait until the update drops and somebody posts a stock rooted version and update it through Odin.
Ok so have to flash the stock rom itself and not just the recovery. I have only really used an older Galaxy S1 to mess with flashing and stuff and never cared about the apps and everything, just would put a rom on there and when needed put it back to stock(borrowed it for a couple months). So if I do a titanium backup of apps+system data I can flash the stock rom, I assume root again and then restore the apps? let it update and Im done, or assuming the stock At&T JB rom is available on XDA I can just flash it on there, root and restore from titanium? Those are the 2 options if I want to stick with stock right?
wiz4769 said:
Ok so have to flash the stock rom itself and not just the recovery. I have only really used an older Galaxy S1 to mess with flashing and stuff and never cared about the apps and everything, just would put a rom on there and when needed put it back to stock(borrowed it for a couple months). So if I do a titanium backup of apps+system data I can flash the stock rom, I assume root again and then restore the apps? let it update and Im done, or assuming the stock At&T JB rom is available on XDA I can just flash it on there, root and restore from titanium? Those are the 2 options if I want to stick with stock right?
Click to expand...
Click to collapse
Right, but it's not usually recommended that you install apps+data with TiBu; better to just install apps only.
-Ryan
Got ya, I do a backup with apps and data to be safe, but you can just restore apps only from that right?
wiz4769 said:
Got ya, I do a backup with apps and data to be safe, but you can just restore apps only from that right?
Click to expand...
Click to collapse
You can. Though could also just let the Play Store redownload your apps for you.
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