I just got the OTA ICS update sent to my phone. As of now it is rooted but on stock rom. My question is I have team Rogue custom recovery. Is that the same as clockwork mod and do I need to restore it back to stock recovery before I accept the ota update? thanks!
You can use sfhub's auto root tool to check if your ROM is compliant. If it isn't, it will fail the update.
http://forum.xda-developers.com/showthread.php?t=1342728
Why don't you just use sfhub's one click FF18 with root. You need to be on stock el29 to accept the update. If not it will fail.
Sent from my SPH-D710 using xda app-developers app
Stuck on triangle
cphil99 said:
I just got the OTA ICS update sent to my phone. As of now it is rooted but on stock rom. My question is I have team Rogue custom recovery. Is that the same as clockwork mod and do I need to restore it back to stock recovery before I accept the ota update? thanks!
Click to expand...
Click to collapse
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
cphil99 said:
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
Click to expand...
Click to collapse
I'm having the same issue.
Edit: I got it. I installed it in the folder not the root of the sd card.
Sent from my SPH-D710 using xda app-developers app
cphil99 said:
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
Click to expand...
Click to collapse
If you get the the triangle, press the "Menu" capacitative button and it will show the log.
Most likely you modified or removed some ROM file or your update.zip is corrupt.
Usually folks remove some bloat way back when and forgot they did it.
If you are still rooted, you could run Auto Root Option E, OTA Compliance Check EL29->FF18 and it will tell you everything that will cause the OTA update to fail.
As an aside, the previous posters are correct and it is probably easier if you just use the FF18 ODIN OneClick.
http://forum.xda-developers.com/showthread.php?t=1721229
The Official FF18 OTA will not run under CWM or CWM-Rogue because when it goes to verify the integrity of the kernel, it will find it is different than what it was expecting.
I have a rooted FF18 OTA that will install from CWM if you want to go that route:
http://forum.xda-developers.com/showthread.php?t=1771799
I got it!
sfhub said:
If you get the the triangle, press the "Menu" capacitative button and it will show the log.
Most likely you modified or removed some ROM file or your update.zip is corrupt.
Usually folks remove some bloat way back when and forgot they did it.
If you are still rooted, you could run Auto Root Option E, OTA Compliance Check EL29->FF18 and it will tell you everything that will cause the OTA update to fail.
As an aside, the previous posters are correct and it is probably easier if you just use the FF18 ODIN OneClick.
http://forum.xda-developers.com/showthread.php?t=1721229
The Official FF18 OTA will not run under CWM or CWM-Rogue because when it goes to verify the integrity of the kernel, it will find it is different than what it was expecting.
I have a rooted FF18 OTA that will install from CWM if you want to go that route:
http://forum.xda-developers.com/showthread.php?t=1771799
Click to expand...
Click to collapse
That did it! I just downloaded and ran the new Odin file and it worked like a charm with no loss of data. Thank you so much for you help!
Related
I searched and didn't get exact answer to easy my mind.
If I want to upgrade to EL29 I am rooted on stock EK02, I need to unroot and then re-root correct?
I have read some are seeing better wifi strength with EL29.
So my questions are:
(1) Is it worth it to go to EL29?
(2) Is it a simple process to unroot, do the update, then root again with the EL29 root one click? Is is the same steps as EK02
You don't need to unroot, if that is all you did. If, using your root powers, you installed CWM, uninstalled bloat, otherwise made changes to your ROM, then those would need to be undone *if* you wanted to apply an OTA patch-style update to get EL29.
EL29 plugged the exploit that was being used by Auto Root to root your phone, so EL29 cannot be directly rooted right now. However there are alternatives:
1) you could use the pre-rooted EL29 ODIN One-Click in my signature. After it is installed, use Option C in Auto Root to install CWM if you want it
2) you could use the rooted EL29 OTA udpate, also in my signature. Instructions are in the thread
3) you could flash the rooted EL29 update.zip that Calkulin put out, then flash the modem by hand. I don't have the link handy. Search the dev section.
sfhub said:
You don't need to unroot, if that is all you did. If, using your root powers, you installed CWM, uninstalled bloat, otherwise made changes to your ROM, then those would need to be undone *if* you wanted to apply an OTA patch-style update to get EL29.
EL29 plugged the exploit that was being used by Auto Root to root your phone, so EL29 cannot be directly rooted right now. However there are alternatives:
1) you could use the pre-rooted EL29 ODIN One-Click in my signature. After it is installed, use Option C in Auto Root to install CWM if you want it
2) you could use the rooted EL29 OTA udpate, also in my signature. Instructions are in the thread
3) you could flash the rooted EL29 update.zip that Calkulin put out, then flash the modem by hand. I don't have the link handy. Search the dev section.
Click to expand...
Click to collapse
I was about to respond.. but man sfhub, you are always on top of these type of posts! I've learned a lot from reading your posts. You're always very clear on instructions and don't assume everyone knows everything.
Am I clear that if I am stock rooted and accept the OTA, in order to root again I wud need a modified ROM... I wud not be able to root for just wifi tether??
sfhub said:
You don't need to unroot, if that is all you did. If, using your root powers, you installed CWM, uninstalled bloat, otherwise made changes to your ROM, then those would need to be undone *if* you wanted to apply an OTA patch-style update to get EL29.
EL29 plugged the exploit that was being used by Auto Root to root your phone, so EL29 cannot be directly rooted right now. However there are alternatives:
1) you could use the pre-rooted EL29 ODIN One-Click in my signature. After it is installed, use Option C in Auto Root to install CWM if you want it
2) you could use the rooted EL29 OTA udpate, also in my signature. Instructions are in the thread
3) you could flash the rooted EL29 update.zip that Calkulin put out, then flash the modem by hand. I don't have the link handy. Search the dev section.
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App
dw0d said:
Am I clear that if I am stock rooted and accept the OTA, in order to root again I wud need a modified ROM... I wud not be able to root for just wifi tether??
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
There's no sense in accepting OTA updates anymore if you are rooted. We get it here on xda faster than sprint pushes them out. It will just break root anyway (assuming you haven't modified any system files, delete bloatware, ect). If you modified some stuff, the update would fail. I wouldn't bother with it. The easiest way would be to ODIN the pre-rooted EL29 stock in sfhub's signature. It'll update the modem, rom and stuff to EL29. Use the 'no-data' version if you want to keep all your data intact. That's what I did, coming from a stock EK02, only rooted.
Thx I will give a shot... XDA rocks
Sent from my SPH-D710 using XDA App
dw0d said:
Am I clear that if I am stock rooted and accept the OTA, in order to root again I wud need a modified ROM... I wud not be able to root for just wifi tether??
Click to expand...
Click to collapse
If you use the pre-rooted EL29 ODIN One-Click in my signature "modified ROM" is really just the addition of 3 files to the ROM to root it. Everything else is stock. It is exactly the same as if you ran Option A on your own ROM. It is just done for you. In fact, you could actually use Option B in Auto Root to unroot your phone and it would be 100% stock.
Same goes for the rooted EL29 OTA in my signature.
sfhub....Thanks for the tips. You showed me how to root a couple weeks ago and it has been great. I'm still cautious and didn't do many tweaks. I did freeze a few apps including voice command so I didn't have to use that every time I wanted to bluetooth dial.
So if I haven't made any major changes to the stock rooted EK02 I can just use the option #2 you said, right? And just pull it from your sig?
dw0d said:
Thx I will give a shot... XDA rocks
Click to expand...
Click to collapse
And this is why I love XDA.
Sent from my calculator watch.
jkhawk said:
I did freeze a few apps including voice command so I didn't have to use that every time I wanted to bluetooth dial.
So if I haven't made any major changes to the stock rooted EK02 I can just use the option #2 you said, right? And just pull it from your sig?
Click to expand...
Click to collapse
Yes, freezing is fine. Only uninstalling or modifying would cause the OTA to fail.
In the instructions for the EL29 OTA there will be an optional step to run the EK02->EL29 OTA Compliance Check. Just run that and it will tell you if anything is missing or changed. Takes around a minute. SHA1FAIL for kernel/zImage is expected. Any other MISSING or SHA1FAIL would need to be addressed.
Hello All,
FYI: This is stock Not rooted.
I got the prompt this morning on my Sprint Galaxy S2 Epic Touch 4g for a system update to ICS It had a full charge I clicked to reboot it started counting down and all it did was reboot, it didn't update I checked the about section and the build and everything is the same and if I go to the system update area now it just says your phone is up to date. Any ideas on what happened?
Thanks in Advance.
Ryan B.l
Something probably went wrong and it didn't boot into recovery or if it did, it is possible the update had some issues.
There is probably a log file in the /cache directory somewhere.
If you really want FF18, IMO the simplest way is just download the pre-rooted FF18 ODIN OneClick here;
http://forum.xda-developers.com/showthread.php?t=1721229
sfhub said:
Something probably went wrong and it didn't boot into recovery or if it did, it is possible the update had some issues.
There is probably a log file in the /cache directory somewhere.
If you really want FF18, IMO the simplest way is just download the pre-rooted FF18 ODIN OneClick here;
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
Thanks for the prompt reply, I appreciate it. I just booted into recovery and wiped the partition cache and rebooted to see if that would help at all. If not then I may just have to manually update as suggested.
I've been using one of Calkulin's ROMs - If I want to try out the stock ICS update, should I flash back to a stock GB ROM first or would I still get a notification to update?
If you are on a custom ROM, you might get the notification, but it won't pass the verification stage when it tries to install.
I would just use the pre-rooted FF18 ODIN OneClick (Full Version) available here:
http://forum.xda-developers.com/showthread.php?t=1721229
sfhub said:
If you are on a custom ROM, you might get the notification, but it won't pass the verification stage when it tries to install.
I would just use the pre-rooted FF18 ODIN OneClick (Full Version) available here:
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
I found the firmware update at the link below and downloaded it and renamed it to update.zip and rebooted to recovery and ran the update from sd and it updated fine
http://community.sprint.com/baw/thread/89419?start=105&tstart=0
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
With all this OTA talk, I've been getting many questions about accepting and OTA while stock rooted.
IF you are stock rooted, you can't get an OTA update because you most likely have a custom recovery installed (Clockworkmod).
To accept this OTA, you will need to install the STOCK recovery.
Please see this video to flash the stock recovery:
http://www.youtube.com/watch?v=1KeZx65twLk
The video linked above also shows how to manually update your phone with the appropriate update zip file.
Once you have accepted the OTA update while stock rooted with stock recovery, you will most likely need to re root. Re root with this video:
http://www.youtube.com/watch?v=XoEVDgjTTdg
qbking77 said:
With all this OTA talk, I've been getting many questions about accepting and OTA while stock rooted.
IF you are stock rooted, you can't get an OTA update because you most likely have a custom recovery installed (Clockworkmod).
To accept this OTA, you will need to install the STOCK recovery.
Please see this video to flash the stock recovery:
http://www.youtube.com/watch?v=1KeZx65twLk
The video linked above also shows how to manually update your phone with the appropriate update zip file.
Once you have accepted the OTA update while stock rooted with stock recovery, you will most likely need to re root. Re root with this video:
http://www.youtube.com/watch?v=XoEVDgjTTdg
Click to expand...
Click to collapse
What I have done in the past is use OTA Rootkeeper. Backup root, then uninstall root. After the update use it to reroot with one tap.
poit said:
What I have done in the past is use OTA Rootkeeper. Backup root, then uninstall root. After the update use it to reroot with one tap.
Click to expand...
Click to collapse
thanks man
Can anyone else confirm the ease of use with this "OTA rootkeeper"???
meccadon123 said:
thanks man
Can anyone else confirm the ease of use with this "OTA rootkeeper"???
Click to expand...
Click to collapse
OTA rootkeeper worked for me. If you have mobile odin that works great too. newest one will patch the ota so you can install it.
meccadon123 said:
thanks man
Can anyone else confirm the ease of use with this "OTA rootkeeper"???
Click to expand...
Click to collapse
billard412 said:
OTA rootkeeper worked for me. If you have mobile odin that works great too. newest one will patch the ota so you can install it.
Click to expand...
Click to collapse
Both have worked super easily for me with no problems!!!
Sent from my SPH-L710 using xda app-developers app
qbking77 said:
With all this OTA talk, I've been getting many questions about accepting and OTA while stock rooted.
IF you are stock rooted, you can't get an OTA update because you most likely have a custom recovery installed (Clockworkmod).
To accept this OTA, you will need to install the STOCK recovery.
Please see this video to flash the stock recovery:
http://www.youtube.com/watch?v=1KeZx65twLk
The video linked above also shows how to manually update your phone with the appropriate update zip file.
Once you have accepted the OTA update while stock rooted with stock recovery, you will most likely need to re root. Re root with this video:
http://www.youtube.com/watch?v=XoEVDgjTTdg
Click to expand...
Click to collapse
will this work for the new update as well?
Sent from my SPH-L710 using xda app-developers app
Hello,
I have Galaxy S3 running 4.1.1, i have perviously
rooted it. After that i done a Factory Rest to the Device,
then tried to UpDate it to the latest Version!
But it always tells me that this device is modified!
What i want is to Completely REMOVE the Root,
then UPDATE it to the latest version? Please HELP!
DaYiM said:
Hello,
I have Galaxy S3 running 4.1.1, i have perviously
rooted it. After that i done a Factory Rest to the Device,
then tried to UpDate it to the latest Version!
But it always tells me that this device is modified!
What i want is to Completely REMOVE the Root,
then UPDATE it to the latest version? Please HELP!
Click to expand...
Click to collapse
As long as you have a custom recovery (either CWM or TWRP), you will not be able to update. You could go back to 100% stock unrooted and then update, but this is not necessary and you'll be doing a lot more steps. More steps means more chances to mess something up.
Good news is that you can just install the stock Rom. Freeza always updates his thread with the most recent Stock Rooted Rom. A lot of times he comes out with it even before I get the OTA from Sprint. All you have to do is flash it in TWRP or CWM. In case you're not familiar with the procedure for doing this, please see this linked post.
Finally, OTAs are fairly common, so check out CNexus' thread on OTAs.
DaYiM said:
Hello,
I have Galaxy S3 running 4.1.1, i have perviously
rooted it. After that i done a Factory Rest to the Device,
then tried to UpDate it to the latest Version!
But it always tells me that this device is modified!
What i want is to Completely REMOVE the Root,
then UPDATE it to the latest version? Please HELP!
Click to expand...
Click to collapse
If you want to go back to stock completely, you will need to odin the tar file and the latest triangle away. This will set your binary and get you back to normal and then odin the stock tar. This will put you back to completely stock with a stick recovery. You should be able to update from there. There are several links to the info you need.
Sent from my SPH-L710 using Tapatalk 2
4_Weasel said:
If you want to go back to stock completely, you will need to odin the tar file and the latest triangle away. This will set your binary and get you back to normal and then odin the stock tar. This will put you back to completely stock with a stick recovery. You should be able to update from there. There are several links to the info you need.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
They don't necessarily have to use Odin and Triangle Away. Here is a thread for a recovery-flashable zip which will reset their counter and restore them back to unrooted stock.
That being said, if the only reason they want to go back to stock is to take the update, it's entirely unnecessary. Like I said before, the more steps they have to take, the more chances they have to mess something up (especially when it comes to Odin and Download mode, in my opinion). If they want to return to stock unrooted for another reason, the easiest way is to use the flashable zip.
Thanks alot for all of your help