Hello,
Right now I am running Juggernaut, but I am definitely wanting to upgrade to the new stock ICS. What do I need to do if I want to use the OTA update? Right now, I've followed some instructions to disable OTA updates to ensure I didn't get accidental corruption. So, what should I do?
Option A:
1) Restore to GB stock using the thread in the dev section.
2) Wait for the OTA update.
Option B:
1) Enable OTA updates and go from Juggs to ICS. (?)
Option C:
1) Wait for an Odin-flashable upgrade to ICS directly, posted here?
Option D:
1) Wait for something else?
Just curious what you all are doing to get to ICS, and curious about my specific situation. It seems like the safest bet it to go to GB stock and use Kies. Although it seems like it might be cleaner to just wait for an Odin package. Thoughts?
There is no ICS OTA stock update
apparently now there is a stock ICS. I tried to downgrade to previous stock and upgrade to last weeks firmware update from kies. Bad move. now my odin flashes fail at mdm.bin. I found my way back to juggernaut and I am waiting for a better ics rom before I try to mess with kies again.
Related
Hi i currently have stock rom but have it rooted. Can someone provide me with a link to update my phone to the new update w/root or let me know what I need to do? Thanks!
Also I am not sure if I am running ext or rfs can some tell me how to figure that out?
A great place to start learning about modding the Epic are the QBKing77 videos on youtube. Just search for them or check out the links to his videos in most of the OPs in the development section. There are a ton of custom roms to play with right now, as well as the stock EI22 Gingerbread rom that came out OTA.
Thanks as I said though I am already rooted but unsure if its ext 4 or RFS I need help figuring that out and then I think I can just odin it from their.
I wish to stay on stock.
Might I suggest taking a look at the MostlyStockROM: http://forum.xda-developers.com/showthread.php?t=1339579
You can even go to the "old links" and choose to download the deodexed only first release which is Stock + doedexed + root. Or choose one of the newer releases which has the fixes/features you want.
If you want EI22 Fully Stock then I believe you will need to unroot your existing install and install the OWA. I haven't seen a stock ODIN method but may have missed it.
I see. How do I unroot my phone?
odin back to stock ec05.
ok so then how do I root my phone after going back to stock updating then what?
Or couldn't I just do a factory reset then update?
newguy0804 said:
ok so then how do I root my phone after going back to stock updating then what?
Or couldn't I just do a factory reset then update?
Click to expand...
Click to collapse
Once you odin back to stock ec05, it'll do the OTA update onto ei22. That's how I did my phone. Warning, once you odin back, you'll lose all your app and data.
I'm not worried about that I have titanium back up pro. their has got to be a easier way to do this though. Before All I had to do was Odin to the next update and that was it (eco5) now I have to odin back to stock remove root then update and then reroot...... thats a lot of work.
Is their a way to do this without un-rooting my phone?
Also can someone shoot me a link to a tutorial on going back to stock?
Also once root is removed I take it I would have to re root it. (this is ridiculous un root, update, reroot)
So what DO i do to re-root it?
newguy0804 said:
Im not worried about that I have titanium back up pro. their has got to be a easier way to do this though. Before All I had to do was Odin to the next update and that was it (eco5) now I have to odin then update and do it agian...... thats a lot of work.
Click to expand...
Click to collapse
you can just download the file and install it using CWM but i'm 0 for 2 with this method.
http://www.youtube.com/watch?v=FB956i_KEp4
Follow the video that babystewie posted. I've used it twice, both succeeding with no issues what so ever. It will allow you to update to GB with root, but will give you a stock version of GB. If you're interested in rooting GB as well, check the video description and there's some more videos.
There are a lot of mostly stock roms or even just a cwm flashable ei22 in the development section. You'll keep root and won't have to go through using odin so many times.
what do you mean a stock version of gingerbread? also I already have clockwork if that helps does it mean i have ti do anything different if i want to keep root?
There really is no completely stock Gingerbread ROMs because we don't have the tar file for the Odin flash. There are several ROMs in the Development thread (where the ROMs are) that are mostly stock. You can simply flash one of those, and if you want the EI22 modem, you can flash the EC05 to EI22 modem updater found in the stickies in development. I recommend you start here:
http://forum.xda-developers.com/showthread.php?t=1337453
I'm on T-Mobile USA, and have stock rom (2.3.6, Baseband T989UVKL1, Kernel 2.6.35.11, Build: GINGERBREAD.UVKL1). This phone is completely stock right now.
I just got the notification about the OTA, which I assume will be to ICS.
Questions before I accept the OTA update:
1. Will I be able to root after installing the official stock ICS update?
2. If so, would I use the ODIN method, or some other method?
3. Other than bloat, are there any known issues with the stock ICS rom.
4. Should I install CWM before accepting the OTA update?
Basically, I've tried looking but there doesn't seem to be much information about the official stock ICS update, probably because it is just starting to be rolled out.
Never mind. Just re-saw this http://www.tmonews.com/2012/05/t-mobile-rolling-out-galaxy-s-ii-maintenance-update-no-ice-cream-sandwich-yet/ and realized this update likely isn't ICS yet.
so i rooted my Sprint galaxy s3, Currently i have clockworkmod with a phantom "blazer". My question is why cant i update my phone? i have baseband version ending in lg2, when the update came out already which ends in lg4? my phone tried giving me the update but when i started the update it wouldnt go through? am i suppose to change the recovery back to stock? I just dont want to miss out on the jellybean update. Will i have to go back to factory?
ps. the "blazer" rom is super fast!!!!
mandosgs3 said:
so i rooted my Sprint galaxy s3, Currently i have clockworkmod with a phantom "blazer". My question is why cant i update my phone? i have baseband version ending in lg2, when the update came out already which ends in lg4? my phone tried giving me the update but when i started the update it wouldnt go through? am i suppose to change the recovery back to stock? I just dont want to miss out on the jellybean update. Will i have to go back to factory?
ps. the "blazer" rom is super fast!!!!
Click to expand...
Click to collapse
Baseband only refers to the modem. If you search the development threads, you will find zips to update the modem in clockwork.
As for stock updates, they require the stock recovery to work so if you have clockwork or twrp recovery installed, you will have to go back to stock to receive the ota updates.
Finally on the Jellybean update, you won't miss it. When released, I'm sure the awesome Devs here will pick it up and it would only be a matter of time before a custom rom is released. The benefits of running 'custom' far outweigh anything that releases 'stock'.
Hi. I have rooted EL29 right now and ICS OTA download notification is up on my phone.
I'm guessing I can't just OTA as is.
What is the best way to update? Unroot it to stock EL29 then get OTA then root it afterwards?
I haven't looked at this site since EL29 release so I'm kind of behind about new stuff and forgetting lots of what to do and NOT to do....
I just want well functioned device. I have no intention to try out new ROM or anything.
The reason I rooted was to use tether. That is the only reason.
So what is the best way to go for me?
If you rooted and did nothing but tether you can take the OTA, if you removed system files etc it will fail.
You lose root taking the OTA, No root exploit available. Rooted FF18 is achieved the same way you can get to it from el29 - http://forum.xda-developers.com/showthread.php?t=1721229
No Data is the same effect as the OTA. There are problems with not wiping the phone. Swype data for example needs to be deleted for swype to work. This is one of many things that OTA users needed to do to make their life work normal.
Well I'm no expert but I flashed my phone back and forth between ICS and GB more times in the past week then I want to think about. I went from EL29 rooted stock to the ICS OTA without problems. If you want to flash to a custom ICS I would suggest using Odin to go back to EL29 rooted and then flash from there. For what I read the risk of bricking occurs when performing a factory reset on ICS OTA.
So I'm on CM9 now and here is what I did.
1) one click Odin to EL29 rooted stock.
2) D/L most recent CM9 build and gapps
3) Flash through CWM
4) Enjoy!
Hey Guys Running CWM on Stock, Rooted ROM.
Looks like the AT&T JB update is probably coming down the pipe soon. What do you plan to do for the OTA? I'm considering flashing stock recovery so the JB OTA will go via the normal OTA process and then try to reroot with Voodoo.
Are others doing the same or are you guys just going to wait for a CWM flashable stock JB update? I'm new to the S3 so not sure what the best strategy for a clean update with root is.
zenaxe said:
Hey Guys Running CWM on Stock, Rooted ROM.
Looks like the AT&T JB update is probably coming down the pipe soon. What do you plan to do for the OTA? I'm considering flashing stock recovery so the JB OTA will go via the normal OTA process and then try to reroot with Voodoo.
Are others doing the same or are you guys just going to wait for a CWM flashable stock JB update? I'm new to the S3 so not sure what the best strategy for a clean update with root is.
Click to expand...
Click to collapse
I have the SGH-I747M in Canada and got the OTA on Dec. 2nd automatically. I postponed the install so I could first do a nandroid backup.
When I tried the OTA install, CWM was unable to handle it and gave me Status 7 errors. I have seen a post on how to get around that, but essentially it does not allow you to run the OTA as an OTA. If you would like to see the OTA proceed normally, the simplest way would be to revert to Stock first.